Hackers have already been exploiting the bugs using rigged PDF documents sent as email attachments.
“Adobe plans to make available updates for Adobe Reader and Acrobat … during the week of February 18, 2013,” the company said in its security incident response team’s blog Saturday.
An associated security advisory, first issued last Wednesday, has also been updated to reflect the impending updates to Reader for Windows, OS X and Linux.
News of the Adobe Reader vulnerabilities surfaced Feb. 13 when researchers from security vendor FireEye reported that attackers were exploiting the bugs, which exist in the latest versions of the popular PDF-viewing software.
Adobe confirmed the vulnerabilities later that same day, acknowledging that attacks were sidestepping the anti-exploit “sandbox” defence baked into Reader 10 and Reader 11.
Some security experts concluded that the attacks are on the same level as the cyber-espionage Duqu threat of 2011, and claimed that that hints at a sophisticated operation beyond the skills of most hacker gangs.
Adobe will patch two vulnerabilities in its update this week; the pair have been used in combination by hackers to circumvent the sandbox and execute other malicious code.
In lieu of a patch, Adobe urged users to upgrade to Reader 11, then turn on “Protected View,” an enhancement to the sandbox that adds additional defensive features. Adobe debuted its original “Protected Mode” sandbox with Reader 10 in November 2010. It added Protected View to Reader 11 last October.
Both Protected Mode and Protected View are available only in the Windows editions.
Windows users running Adobe Reader 11 can block current attacks by turning on the “Protected View” sandbox.
The exploits now in circulation can break out of the Protected Mode sandbox – the first documented bypass of Adobe’s technology –but will be stymied if Protected View is enabled in Reader 11.
But as several security experts have pointed out, Protected View is not turned on by default in Reader 11.
Traditionally, Adobe has played it conservative with security features, either leaving them off by default or declining to immediately roll them out to users. It took the latter path in 2010 with Reader 10′s Protected Mode.
On Sunday, Adobe explained why it didn’t turn on Reader 11′s Protected View, essentially saying it opted to favour businesses – which rely on more advanced features of Reader and its for-a-fee Acrobat cousin – over consumers, who typically use the software only to view PDFs.
“We weighed the risk/benefit to customers with the impact on customers and their existing workflows,” said Adobe spokeswoman Heather Edell in an email reply to questions. “Adobe Reader Protected View will allow only one single function, which is to view a PDF document. Turning Adobe Reader Protected View on by default would break existing workflows customers rely on and result in unexpected impact on a very significant number of users.”
Edell did say that Protected View may be toggled on by default in the future. She did not commit to a timetable, however.
Windows users can turn on Protected View by opening Reader 11, selecting “Preferences” from the Edit menu, clicking the “Security (Enhanced)” item in the column on the left, then near the top of the ensuing dialog clicking “Files from potentially unsafe locations” or “All files” under the “Protected View” heading.
But customers running OS X are out of luck: Reader for Apple’s operating system lacks any sandboxing. Until Adobe patches Reader, Mac owners can protect themselves by viewing PDFs in OS X’s Preview application rather than Adobe Reader.
To make this change, users can right-click on any PDF document, select “Get Info” from the pop-up menu, choose “Preview” in the “Open with” field, and finally, click the “Change All” button.
The last time Adobe rushed out an emergency update to patch a Reader zero-day vulnerability was in December 2011.
Gregg Keizer covers Microsoft, security issues, Apple, Web browsers and general technology breaking news for Computerworld. Follow Gregg on Twitter at @gkeizer, on Google+ or subscribe to Gregg’s RSS feed. His email address is firstname.lastname@example.org.