« November 2008 · May 2009 · September 2010 »
|
|
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
- 31.03.2009: Conficker Working Group
- 02.03.2009: Waledac Coupon Campaign & Updated Domain List
- 21.02.2009: See below.
- 19.02.2009: When PDFs Attack - Acrobat [Reader] 0-Day On the Loose
- 16.02.2009: Shadowserver - ASN & Netblock Alerting & Reporting Service
- 12.02.2009: Joint Effort at Conficker Disruption
- 02.02.2009: Reports and Data
- 29.01.2009: Asprox Goes Phishing Again
- 24.01.2009: More Waledac Domains to Block
- 22.01.2009: Asprox - It's Baaaaaaack
- 19.01.2009: Inauguration Themed Waledac - New Tactics & New Domains
- 09.01.2009: Waledac Domains - Updated List
Saturday, 21 February 2009
More on the Adobe Acrobat 0-Day
Adobe Advisory Issued
First we are a glad to see that Adobe issued Adobe Product Security Advisory 09-01 (APSA09-01) within a few hours of our initial posting on this issue on Thursday. The advisory is more of an acknowledgment of an issue and relatively light on any details. However, a few items of interested can be extracted from this advisory.
Work Arounds & Windows Group Policy Object (GPO)
As we mentioned the main work around for this is to disable JavaScript. Acrobat will still crash but the exploit should fail. While all platforms are reportedly affected, we should note that we have only seen active exploits for Windows and not Linux or OS X platforms. Once again to disable JavaScript in Acrobat [Reader], take the following steps:
Elazar Broad also wrote into us the other day and provided a GPO that can be used to disable JavaScript for Adobe Acrobat [Reader]. We have not tested it but you can grab it by clicking here. Basically these are the keys of interest (from HKEY_CURRENT_USER):
Setting the DWORD "bEnableJS" to 0 will disable JavaScript.
Not so New After All?
We are also seeing more evidence that this exploit may not be so new after all. Various write-ups from different vendors, Symantec, McAfee, and Sophos, may possibly indicate this exploit has been around since mid-January and potentially in December. We have not been able to validate any of this yet, but we are thinking this exploit was likely in the wild since some time in January. Unfortunately we do not have a comprehensive list of command and control servers that we can share.
Details Released
We knew it would not take too long -- the details of the vulnerable function and enough information to potentially recreate the exploit have now been published publicly. While we intentionally did not release these details, they are out there now. Expect that a wider set of attackers will now start using this exploit in the near future before the patch is released. In other words...DISABLE JAVASCRIPT and patch as soon as it becomes available!
=>Posted February 21, 2009, at 10:24 AM by Steven Adair
