Risk
7/20/2010
04:16 PM
Connect Directly
LinkedIn
Twitter
Google+
RSS
E-Mail
50%
50%

Adobe Plans Security Sandbox For Reader

Windows users can look forward to improved malware protection in Adobe's Reader software.

Continuing the security initiative launched last year to deal with rising attacks on its products, Adobe on Tuesday previewed forthcoming security technology in the next major release of its Reader software, which should debut before the end of the year.

Adobe Reader and Acrobat are widely installed applications for reading and creating PDF files. Because one or both are present on most personal computers, they've become targets for malware writers, along with Adobe's Flash software.

Adobe has struggled to keep up and the company's reputation has suffered. In March, security company F-Secure said that Acrobat/Reader was the most targeted application in 2009.

The security initiative that Adobe launched last year represents an attempt to turn things around.

As an example of what the company has been doing, Adobe in April introduced a new software updater that can be set to update Reader and other Adobe software automatically for Windows users (Mac OS requires a password for updates, so automatic updating isn't possible at the moment for Mac users).

Automatic updating is considered to promote better security than manual updating because it applies patches consistently.

Adobe's security rebound continues with the introduction of a sandboxing technology called Protected Mode in the next Reader release.

Brad Arkin, Adobe's senior director of product security and privacy, likens it to the Google Chrome sandbox and Microsoft Office 2010 Protected Viewing Mode.

"With Adobe Reader Protected Mode enabled (it will be by default), all operations required by Adobe Reader to display the PDF file to the user are run in a very restricted manner inside a confined environment, the 'sandbox,'" said Arkin in a blog post. "Should Adobe Reader need to perform an action that is not permitted in the sandboxed environment, such as writing to the user’s temporary folder or launching an attachment inside a PDF file using an external application (e.g. Microsoft Word), those requests are funneled through a 'broker process,' which has a strict set of policies for what is allowed and disallowed to prevent access to dangerous functionality."

Adobe's sandbox is Windows-only and will initially be limited to blocking write operations. Later iterations will block read-only activities, such as accessing sensitive information.

While past neglect of Mac development is believed to be one of the reasons that Apple CEO Steve Jobs has taken such a hard line against Adobe's Flash technology, Adobe's focus on Windows need not be taken as a slight. It could be said to be a vote of confidence in the security situation on other platforms. Adobe's rationale for coming to the defense of Windows is that Windows users face the most risk from malware.

"Today, Adobe Reader for Windows represents the overwhelming majority of Adobe Reader downloads," an Adobe spokesperson said in an e-mail. "Adobe is always carefully evaluating the threat landscape to determine the priorities and next steps in the security roadmap for our products."

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Dark Reading, September 16, 2014
Malicious software is morphing to be more targeted, stealthy, and destructive. Are you prepared to stop it?
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-2942
Published: 2014-09-22
Cobham Aviator 700D and 700E satellite terminals use an improper algorithm for PIN codes, which makes it easier for attackers to obtain a privileged terminal session by calculating the superuser code, and then leveraging physical access or terminal access to enter this code.

CVE-2014-5522
Published: 2014-09-22
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2014-6025. Reason: This candidate is a reservation duplicate of CVE-2014-6025. Notes: All CVE users should reference CVE-2014-6025 instead of this candidate. All references and descriptions in this candidate have been removed to pre...

CVE-2014-5523
Published: 2014-09-22
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2014-5524. Reason: This candidate is a duplicate of CVE-2014-5524. Notes: All CVE users should reference CVE-2014-5524 instead of this candidate. All references and descriptions in this candidate have been removed to prevent acciden...

CVE-2014-5575
Published: 2014-09-22
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none.

CVE-2014-5665
Published: 2014-09-22
The Mzone Login (aka com.mr384.MzoneLogin) application 1.2.0 for Android does not verify X.509 certificates from SSL servers, which allows man-in-the-middle attackers to spoof servers and obtain sensitive information via a crafted certificate.

Best of the Web
Dark Reading Radio