Happy Valentines Day everyone. Our vendors are bringing us the gifts of security vulnerability patches. Lots of them. Yes, it’s extra work for our IT teams, but removing these vulnerabilities could mean that we all get to keep our jobs, and remain in business. I was hearing on the news today that Nortel is now coming clean regarding the fact that hackers 0wn3d their network for roughly 10 years, with full and complete access to everything.
Wonder how they got that?
Where is Nortel today? Something to think about…
Microsoft released the expected batch of 9 patches:
MS12-008: Critical Remote Code Execution Vulnerabilities in Windows Kernel-Mode Drivers
MS12-009: Important Elevation of Privilege Vulnerabilities in Ancillary Function Driver
MS12-010: Critical Cumulative Security Update for Internet Explorer
MS12-011: Important Elevation of Privilege Vulnerabilities in Microsoft SharePoint
MS12-012: Important Remote Code Execution Vulnerability in Color Control Panel
MS12-013: Critical Remote Code Execution Vulnerability in C Run-Time Library
MS12-014: Important Remote Code Execution Vulnerability in Indeo Codec
MS12-015: Important Remote Code Execution Vulnerabilities in Microsoft Visio Viewer 2010
MS12-016: Critical Remote Code Execution Vulnerabilities in .NET Framework and Silverlight (This one I would recommend holding off on, as Microsoft is expected to re-release after identifying a “metadata (logic) error”.)
APSB12-02: Critical Security update available for Adobe Shockwave Player. This update addresses critical vulnerabilities in Adobe Shockwave Player 18.104.22.1683 and earlier versions on the Windows and Macintosh operating systems. These vulnerabilities could allow an attacker, who successfully exploits these vulnerabilities, to run malicious code on the affected system.
APSB12-04: Important Security update available for RoboHelp for Word. This update addresses an important vulnerability in RoboHelp 9 (or 8) for Word on Windows. A specially crafted URL could be used to create a cross-site scripting attack on Web-based output generated using RoboHelp for Word.
I am happy to post that Adobe has released beta code for sandboxing Flash content within Firefox. Sandboxing is an excellent way to isolate ancillary code from the operating system and other applications. I have been using it for years to keep my browser and its myriad vulnerabilities isolated after experimenting with it in malware analysis. It just makes sense to contain the raft of cruft that tends to come in from an uncontroled, but necessary network, like the Internet.
It is not a foolproof method for containing all malware or avoiding malicious content, but it cuts down significantly on the impact of what mal-content can do by restricting its reach, and it increases the cost, package size, and effort required on the part of the bad guys to get through an additional layer of defense. Every defensive layer that they have to identify and circumvent presents another opportunity to discover and analyze their attack code…
Adobe used elements of Google’s Chrome sandboxing technology in its Reader code after a flurry of vulnerability announcements and high profile attacks targeting the application. Adobe says that since its launch in November 2010, they have not seen a single successful exploit in the wild against Adobe Reader X, where they initially offered sandboxing technology.
The new code currently supports Firefox 4.0 or later running on Windows 7 or Vista. Adobe promises wider browser protection soon. More details will be given at the CanSecWest security conference in Vancouver, BC next month. I sure would like to attend this conference. Maybe I will meet some of you there?!
UPDATE: ComputerWorld reports that IE is next on Adobe’s list to “sandbox” its popular Flash Player within browsers, Adobe’s head of security said today.
A Security Bulletin (APSB12-01) has been posted in regards to this quarter’s security updates for Adobe Reader and Acrobat. The updates address critical security issues, including CVE-2011-2462 and CVE-2011-4369, previously addressed in Adobe Reader and Acrobat 9.x for Windows as referenced in Security Bulletin APSB11-30.
Adobe recommends that users apply the updates for their product installations. Mark adds ASAP.
The next quarterly security updates for Adobe Reader and Acrobat are currently scheduled for April 10, 2012.
There have been reports of two critical vulnerabilities being actively exploited in targeted attacks against Adobe Reader 9.x on Windows. These vulnerabilities could cause a crash and may allow an attacker to take control of the affected system.
Today’s updates address these vulnerabilities in Adobe Reader and Acrobat 9.x for Windows. Version X has protected mode available that prevents this type of attack. Adobe recommends users of Adobe Reader 9.4.6 and earlier 9.x versions for Windows update to Adobe Reader 9.4.7. Adobe recommends users of Adobe Acrobat 9.4.6 and earlier 9.x versions for Windows update to Adobe Acrobat 9.4.7.
On December 6, Adobe announced that a zero-day vulnerability in all supported versions of Adobe Acrobat and Reader is being exploited in the wild. No patch is currently available. Apparently, Lockheed Martin reported the issue, indicating this may have been used in an attack on the defense technology company. Targeted attacks were reported in the first week of November, so this one has been active a while.
The vulnerability is being exploited in the wild through PDF attachments to e-mails containing what Symantec is calling “Pidief“, listed as a family of Trojans that drop or download additional malware on to a compromised computer. The malware agent is reportedly dropping “Sykipot” once initially compromised, providing a backdoor into the system for remote control.
Adobe expects to have a patch released for Reader and Acrobat 9 by the week of December 12, and will update Reader/Acrobat X as part of its regular quarterly patch cycle January 10th, 2012. Adobe recommneds that in the meantime, use Reader and Acrobat X’s protected mode or sand-box capabilities to protect users.
Exercise extreme caution when handling PDF files. Any PDF email attachments should be treated suspiciously. Email attachments are a common vector for targeted attacks withg this kind of vulnerability.
Instruct users to use extreme caution when opening PDF files from unknown or untrusted sources, especially email attachments.
Upgrade to Adobe Reader X and Adobe Acrobat X, which provide a built in sand-box enabled by default.
Apply the patch from Adobe as soon as it becomes available.
Microsoft will issue 16 security updates next week to patch 34 vulnerabilities in Windows, Internet Explorer, Office, SQL Server, and other products. 9 of the 16 updates will be rated critical, the remainder rated important. 2 updates will target vulnerabilities in IE, 10 target Windows, 2 will address Office components (Excel, InfoPath, Visual Studio, and SQL). 8 of the 10 Windows updates affect Microsoft’s newest operating system, Windows 7.
Adobe has also announced that it will ship updates for Reader and Acrobat on Tuesday. Adobe did not specify how many vuilnerabilities will be fixed in the update.
Adobe has issued a patch for Flash after 0-day cross site scripting (XSS) attacks were detected in the wild using email as the primary attack vector.
Anyone with Flash Player 10.3.181.16 or earlier for Windows, Mac, or Linux should update to 10.3.181.22 (10.3.181.23 for ActiveX) ASAP. Flash running on Android devices is also affected, and will be addressed in a separate fix this week.
CVE-2011-2107 is rated as “important” by the vendor, rather than the expected critical. The patch was considered serious enough for Adobe to fix it outside of its normal monthly cycle, all part of the company’s reformed ‘beter safe than sorry’ attitude in the wake of repeated attacks on its products and add-ons during 2008, 2009, and 2010.