Microsoft released its pre-announcement for the upcoming patch Tuesday. The summary indicates a total of 8 bulletins, 2 are critical with remote code execution and 6 Important with a mix of remote code execution, elevation of privileges, denial of service and security bypass features. The announcement is available here.

[1] https://technet.microsoft.com/library/security/ms14-may


Guy Bruneau IPSS Inc. gbruneau at isc dot sans dot edu

(c) SANS Internet Storm Center. http://isc.sans.edu Creative Commons Attribution-Noncommercial 3.0 United States License.
Facebook has removed its standalone Poke app, an early clone of Snapchat, as well as its Camera app, from Apple's iTunes app store.

Posted by InfoSec News on May 09


By Andrea Peterson
The Washington Post
May 9, 2014

Bitly, a popular service that allows users to create shortened or even
customized URLs, and track how that shortened link is shared over time,
issued a mysterious security update Thursday evening.

In a blog post, CEO Mark Josephson...

Posted by InfoSec News on May 09


Premium Times
8 MAY 2014

The Nigerian National Petroleum Corporation, NNPC, has cautioned
contractors and other stakeholders in the oil and gas industry against
falling victims of phantom contract proposals by some fraudsters.

This is contained in a statement issued on Thursday in Abuja by the Group
General Manager, Group Public Affairs Division, NNPC, Ohi Alegbe.

The statement said that some...

Posted by InfoSec News on May 09


By Jaikumar Vijayan
May 8, 2014

An inadvertent data leak that stemmed from a physician's attempt to
reconfigure a server cost New York Presbyterian (NYP) Hospital and
Columbia University (CU) Medical Center $4.8 million to settle with the
U.S. Department of Health and Human Services (HHS).

The hospitals and HHS...

Posted by InfoSec News on May 09


By Jeffrey Roman
Bank Info Security
May 8, 2014

The Federal Financial Institutions Examination Council is planning
cybersecurity vulnerability and risk-mitigation assessments to help
smaller banking institutions address potential gaps. The effort is
expected to begin later this year.

The assessments will help FFIEC member agencies, such as the Office of the...

Posted by InfoSec News on May 09


By Dan Chenok
May 09, 2014

In recent years, federal agencies have made significant strides
incorporating cloud computing into their IT portfolios. From the OMB
“Cloud First” strategy, to GSA’s Federal Risk and Authorization Management
Program (FedRAMP), the government is following commercial best practices
to leverage the cloud.

Cloud capabilities can be...
Last month's leaking of an FCC plan for new net neutrality rules promptly elicited a firestorm of criticism from all sides of the political spectrum for its inclusion of two words -- "commercially reasonable."
In a second report this week on scientists' use of nanotechnology to battle cancer, researchers at MIT announced a new way to use nanoparticles to give cancerous cells a one-two punch.
Whatever your primary OS, Linux distro Tails 1.0 offers a plethora of security features to help you work online without worrying about privacy issues.
The U.S. Department of Justice wants new authority to hack and search remote computers during investigations, saying the new rules are needed because of complex criminal schemes sometimes using millions of machines spread across the country.
Analysts today struggled to explain why Apple might acquire Beats Electronics, the headphone maker and music subscription service operator, for $3.2 billion.
Google was dealt a blow Friday in the multibillion dollar lawsuit alleging its Android operating system infringes on intellectual property owned by Oracle.
[security bulletin] HPSBHF02946 rev.1 - HP Servers with NVIDIA GPU Computing Driver, Elevation of Privilege
[security bulletin] HPSBST03038 rev.1 - HP H-series Fibre Channel Switches, Remote Disclosure of Information
Rogue cloud services are ripping gaping holes in the security fabric of most companies, putting the CIO in a tough spot. But as the fallout from the Target attack shows, IT and business leaders will go down together if the breach hits the fan.
Nvidia's upcoming 64-bit Tegra K1 chip could wind up in microservers, which would lead the company into competition with ARM processor makers in that space.

A former sailor assigned to a US nuclear aircraft carrier and another man have been charged with hacking the computer systems of 30 public and private organizations, including the US Navy, the Department of Homeland Security, AT&T, and Harvard University.

Nicholas Paul Knight, 27, of Chantilly, VA, and Daniel Trenton Krueger, 20, of Salem, IL, were members of a crew that hacked protected computers as part of a scheme to steal personal identities and obstruct justice, according to a criminal complaint unsealed earlier this week in a US District Court in Tulsa, Oklahoma. The gang, which went by the name Team Digi7al, allegedly took to Twitter to boast of the intrusions and publicly disclose sensitive data that was taken. The hacking spree lasted from April 2012 to June 2013, prosecutors said.

At the time of the alleged hacks, Knight was an active duty enlisted member of the Navy assigned to the nuclear aircraft carrier USS Harry S. Truman, prosecutors said. He worked as a systems administrator in the carrier's nuclear reactor department. He is accused of conducting some of his unlawful hacking while aboard. The "self-professed leader of Team Digi7al [and] the primary publicist and Twitter poster," Knight was discharged after trying to hack into a Navy database while at sea, according to court documents. There are no allegations that he hacked any of the carrier's systems. Krueger, meanwhile, was a student studying network administration at an Illinois community college. The two men were allegedly aided by three unnamed minors who were not charged in the complaint.

Read 2 remaining paragraphs | Comments

The Uptime Institute estimates that 20% of all racked IT equipment has no use other than to warm the planet. But for data center operators that do manage to unplug equipment, savings can be significant.
Despite taking prompt action to defend against the Heartbleed attack, some sites are no better off than before -- and in some cases, they are much worse off.
LinuxSecurity.com: Several security issues were fixed in cups-filters.
LinuxSecurity.com: Security Report Summary
LinuxSecurity.com: Updated mediawiki packages fix security vulnerabilities: Login CSRF issue in MediaWiki before 1.22.5 in Special:ChangePassword, whereby a user can be logged into an attackers account without being aware of it, allowing the attacker to track the user's activity [More...]
LinuxSecurity.com: Updated apache-mod_security packages fix security vulnerability: Martin Holst Swende discovered a flaw in the way mod_security handled chunked requests. A remote attacker could use this flaw to bypass intended mod_security restrictions, allowing them to send requests [More...]
LinuxSecurity.com: Updated python-imaging packages fix security vulnerabilities: Jakub Wilk discovered that temporary files were insecurely created (via mktemp()) in the IptcImagePlugin.py, Image.py, JpegImagePlugin.py, and EpsImagePlugin.py files of Python Imaging Library. A local attacker [More...]
LinuxSecurity.com: Updated openssl packages fix security vulnerability: A null pointer dereference bug in OpenSSL 1.0.1g and earlier in so_ssl3_write() could possibly allow an attacker to cause generate an SSL alert which would cause OpenSSL to crash, resulting in a denial [More...]
LinuxSecurity.com: Updated kernel packages that fix three security issues and several bugs are now available for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having [More...]
LinuxSecurity.com: Updated kernel packages that fix two security issues and one bug are now available for Red Hat Enterprise Linux 5.9 Extended Update Support. The Red Hat Security Response Team has rated this update as having [More...]
LinuxSecurity.com: Several security issues were fixed in libvirt.
SAP Solution Manager Remote Information Disclosure Vulnerability
FTC takes it to task for misleading privacy policy, other transgressions. You should take another look at your company's privacy policy.
A managed service approach to application development and maintenance seems like a win-win for outsourcing customers and providers. But how do you make it work? Steven Kirz, principal with outsourcing consultancy Pace Harmon, talks about what a successful managed service deal looks like.
Hiring developers is a lot like sales: You must build and engage a pipeline of qualified candidates to accelerate time-to-hire. Some hiring companies are using voluntary coding challenges to do just that.
Perl libwww-perl (LWP) Module Peer Certificate Validation Security Bypass Vulnerability
SSH key cloning problem in OnApp templates
[security bulletin] HPSBMU03035 rev.1 - HP Network Node Manager I (NNMi) for HP-UX, Linux, Solaris, and Windows, Remote Cross-Site Scripting (XSS)
[security bulletin] HPSBGN03008 rev.2 - HP Software Service Manager, "HeartBleed" OpenSSL Vulnerability, Remote Disclosure of Information

With the recent headlines, we've seen heartbleed (which was not exclusive to Linux, but was predominately there), an IE zero day that had folks over-reacting with headlines of "stop using IE", but Firefox and Safari vulnerabilities where not that far back in the news either.

So what is "safe"?  And as an System Administrator or CSO  what should you be doing to protect your organization?

It's great to say "Defense in Depth" and "The 20 Critical Controls", but that's easy to say and not so easy to do when you are faced with a zero day in the browser that your business application must have to run.  What can you do that's quick and easy, that offers some concrete protection for your community of 20, 200, 2,000 or 20,000 workstations?

I'm starting a list here, but this is by no means a well-researched, exhaustive and complete list, just a starting point:
Inventory your hosts and the software that you run.  Know your network, and know what's running on your servers and workstations.  (if this sounds like another way of saying "read the 20 controls, start implementing at #1 and work your way down the list", then you get my point).  After you inventory, read the list.  Expect a story on this in the next week or so.

Deploy EMET.  In the hype of "don't run IE" headlines, many of the folks who recommended this missed the fact that if you installed EMET, you were nicely protected against last week's 0-day.  Expect a story on this later today (yes, I'm on a bit of a tear).

Read your logs.  In every incident that I've worked, there's been *some* indication of the attack or compromise in logs somewhere - this is why you log after all.  This also holds true for system crashes and problems of any kind.  Troubleshooting always starts with your logs, but if you monitor logs for unusual things, you can expect less trouble to troubleshoot, because you'll see it before it gets to be a problem.  If there are too many logs (yes, log volumes are insane), deploy a tool (there are tons of free ones) that will help you with this.  ELSA (https://code.google.com/p/enterprise-log-search-and-archive/) is a decent starting point for log consolidation and prioritizing, but it's by no means the only solution - find what works for you and use it.

Control your network perimeter (if you can define a perimeter).  Put an egress filter that allows what you need, then has a deny any/any/log statement at the bottom.  The "log" part makes it simpler to add new list entries to satisfy new business requirements as they come up.

Also at your perimeter, have the ability to block some of the "problem" applictions when you know that things have gone particularly bad.  For instance, if there is a Flash zero-day, there's no shame in sending a note to your users to say "we have to block flash at the firewall for a few days until there's a fix".  Ditto that for ActiveX, Java, PDF files and whatever else you'd care to add to the list.  

Many of these settings are simple tick-boxes at the firewall, some are IPS signatures or some might need a proxy or web content filter product.  The key to all of these is to be prepared, know where the knobs are that you need to tweak, and know what you can and can't do both technically and within your organization.  If you're caught by surprise and put a "fix" together in a hurry, document what you did so you can re-use that next time, or improve it when you have an hour to spare.

Talk to your users.  Keep a steady flow of communication going, let them know what's going on.  Call this "Security Awareness Training" if that scores you points, but the object of the game is to keep your user community in the loop - the more they know about what they should do or not do (and why), the fewer problems will come your way from that direction.  Also, the more that IT and the Security Team is seen as helping and advising (in a good way), the more slack they'll cut you when you need it - for instance when you need to block Flash, PDF files or their favourite website for a day or three.

We've been saying this for years, but I still have clients who say "we trust our people, why would we do any of that".  My answer remains "so you trust their malware too?".

I'd invite you, our readers to add to this list in the comments.  This is meant as just a starting point - what have I missed?  What has worked for you?

Rob VandenBrink

(c) SANS Internet Storm Center. http://isc.sans.edu Creative Commons Attribution-Noncommercial 3.0 United States License.

=============== Rob VandenBrink Metafore

(c) SANS Internet Storm Center. http://isc.sans.edu Creative Commons Attribution-Noncommercial 3.0 United States License.
(c) SANS Internet Storm Center. http://isc.sans.edu Creative Commons Attribution-Noncommercial 3.0 United States License.

It started with DNS: Simple short DNS queries are easily spoofed and the replies can be much larger then the request, leading to an amplification of the attack by orders of magnitude. Next came NTP. Same game, different actors: NTP's "monlist" feature allows for small requests (again: UDP, so trivially spoofed) and large responses. 

Today, we received a packet capture from a reader showing yet another reflective DDoS mode: SNMP. The "reflector" in this case stands nicely in line for our "Internet of Things" theme. It was a video conferencing system. Firewalling these systems is often not practical as video conferencing systems do use a variety of UDP ports for video and audio streams which are dynamically negotiated. As a result, they are often left "wide open" . And of course, these systems not only let attackers spy on your meeting rooms, but the also make great SNMP reflectors as it turns out.

Here is an anonymized traffic capture (target anonymized with -> SNMP 87 getBulkRequest -> IPv4 1514 Fragmented IP protocol (proto=UDP 17, off=0, ID=1f48) -> IPv4 1514 Fragmented IP protocol (proto=UDP 17, off=1480, ID=1f48)
... [ additional fragments omitted ] ... -> IPv4 1514 Fragmented IP protocol (proto=UDP 17, off=54760, ID=1f48) -> IPv4 1514 Fragmented IP protocol (proto=UDP 17, off=56240, ID=1f48) -> SNMP 664 get-response    [... large response payload ...]

That is right! A simple 87 byte "getBulkRequest" leads to about 60k Bytes of fragmented data being sent back. We can only assume that poor is the victim of this DoS attack. The user reporting this saw about 5 MBit/sec of traffic. 

Similar to what we have seen with other reflective attacks like this, the fragmentation of the traffic is likely going to make filtering even harder. Prolexic posted a white paper about some of the different DrDOS attacks, including SNMP attacks [1]

So what to do:

- SNMP should probably not traverse your perimeter. Stop it at the firewall. (and I don't think video conferencing systems need it)
- proper egress/ingress control is a good idea.  But you already knew that.

[1] http://www.prolexic.com/kcresources/white-paper/white-paper-snmp-ntp-chargen-reflection-attacks-drdos/An_Analysis_of_DrDoS_SNMP-NTP-CHARGEN_Reflection_Attacks_White_Paper_A4_042913.pdf


Johannes B. Ullrich, Ph.D.
SANS Technology Institute

(c) SANS Internet Storm Center. http://isc.sans.edu Creative Commons Attribution-Noncommercial 3.0 United States License.
lxml 'clean_html' Function Security Bypass Vulnerability


Infosec sea change coming
Infosec sea change coming. By Tracy Burrows, ITWeb contributor. Johannesburg, 9 May 2014. Enterprises need a back-to-basics approach, says Guy Golan, CEO of the Performanta Group. Enterprises are on the verge of losing the cyber security battle in the ...

The U.S. Federal Election Commission appears to be warming to the idea of political donations in bitcoin, but left the larger question of the upper value limit of such donations unresolved.
Alcatel-Lucent's revenue remained flat during the first quarter, although the company made a smaller loss than a year earlier.
Linux users who want to avoid browser-based Twitter apps can try out these five local clients -- including one that still uses a command-line interface.
Venture capitalists and angel investors are unhappy with net neutrality rules proposed by the U.S. Federal Communications Commission, they said in an open letter published Thursday.
Internet Storm Center Infocon Status