Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.


03:39 PM
Connect Directly

Adobe To 'Sandbox' PDF Files

Upcoming security feature for Adobe Reader puts PDFs in protected mode

In the latest move to lock down its applications from attack, Adobe announced today it will add a default sandboxing feature to the next version of the Adobe Reader software. The new "Protected Mode" for Reader, which it will roll out later this year, will quarantine any operations to a confined and restricted space.

Adobe apps have been in the bull's eye as one of the most popular attack vectors, especially in the form of malware-laden PDF files. Adobe has been beefing up its security posture during the past year, starting with its automatic updater feature for Reader and Acrobat and a regular patching schedule. Another big piece of Adobe's security strategy is hardening its code against attacks, says Brad Arkin, senior director of product security and privacy. "Sandboxing was one of the early technology candidates we looked at" for code-hardening, he says.

The new Protected Mode feature is based on the sandboxing technique used by Microsoft in Office 2010 and by Google in its Chrome browser. The first release of the sandboxing feature will keep all "write" calls inside the protected space so that if a PDF is infected with malware, the malicious code can't spread outside that file to the system itself or to other files. The second phase of the Protected Mode release for Reader will prevent attackers from reading information on the victim machine's system via an infected PDF. "It will be harder for the bad guys to install malicious software or anything persistent on a computer that could survive from one reboot to [the next]," Arkin says.

Sandboxing basically quarantines any malware that's embedded in a PDF. "Real-world attacks today are almost always some variant of a memory trespass vulnerability," Arkin says. Sandboxing, which restricts what an attacker is able to do with a PDF file, should eliminate many of those types of threats, he says.

But the cat-and-mouse game between security experts and attackers will likely just move to another vector, he says. "Once we put this out, attackers will either move to another application or they might look for creative ways to work around it," he says.

Security experts welcomed Adobe's adoption of sandboxing, but they don't expect it to dissuade attackers from continuing to hammer away at Adobe apps. "Reader will continue to be a really big target for a while, even with the sandbox environment," says Andrew Storms, director of security operations at nCircle. "But we need to congratulate Adobe for another tool to help protect ourselves and our users."

Storms says the true weakest link is still the user. "The idea is to use the tools the vendors are giving you, but you still have to apply your own risk assessment," he says.

Adobe's Arkin says Adobe worked with Microsoft Office's security team, the Google Chrome team, as well as other outside experts in implementing the sandboxing technology in Reader. It's based on Microsoft's practical Windows sandboxing technique, and works like this in Reader: when Reader needs to execute any action not allowed in the sandbox such as launching an attachment inside a PDF file from another app, for example, that action gets vetted by a broker process with specific policies that prevent access to any functions that could open the system up to attack.

The goal is to stop attackers from writing files, changing registry keys, or installing malicious code via PDFs -- but without the user noticing any difference in the Reader app, Arkin says. "There's no performance impact, no change to the interface, no dialog box – it's just happening in the background. And users don't change the way they interact with PDFs," he says.

Sandboxing does not, however, prevent phishing or clickjacking attacks, he notes. "There's nothing we can do to protect against users who follow" links in infected PDFs purportedly from their banks, for example, he says.

Just how long sandboxing techniques will stand up to attacks is unclear. nCircle's Storms says attackers probably will come up with ways to subvert sandboxing much the way researchers have done with Microsoft's Address Space Layout Randomization (ASLR) and Data Execution Protection (DEP) security features. "The question is how quickly Adobe, Microsoft, and Google react" to any challenges to the technique, he says.

Have a comment on this story? Please click "Discuss" below. If you'd like to contact Dark Reading's editors directly, send us a message.

Kelly Jackson Higgins is the Executive Editor of Dark Reading. She is an award-winning veteran technology and business journalist with more than two decades of experience in reporting and editing for various publications, including Network Computing, Secure Enterprise ... View Full Bio

Comment  | 
Print  | 
More Insights
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 9/17/2020
Cybersecurity Bounces Back, but Talent Still Absent
Simone Petrella, Chief Executive Officer, CyberVista,  9/16/2020
Meet the Computer Scientist Who Helped Push for Paper Ballots
Kelly Jackson Higgins, Executive Editor at Dark Reading,  9/16/2020
Register for Dark Reading Newsletters
White Papers
Current Issue
Special Report: Computing's New Normal
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2020-09-21
Affected versions of Atlassian Jira Service Desk Server and Data Center allow remote attackers authenticated as a non-administrator user to view Project Request-Types and Descriptions, via an Information Disclosure vulnerability in the editform request-type-fields resource. The affected versions are...
PUBLISHED: 2020-09-21
Affected versions of Atlassian Jira Server and Data Center allow remote attackers to impact the application's availability via a Regex-based Denial of Service (DoS) vulnerability in JQL version searching. The affected versions are before version 7.13.16; from version 7.14.0 before 8.5.7; from versio...
PUBLISHED: 2020-09-21
Affected versions of Atlassian Jira Server and Data Center allow remote, unauthenticated attackers to view custom field names and custom SLA names via an Information Disclosure vulnerability in the /secure/QueryComponent!Default.jspa endpoint. The affected versions are before version 8.5.8, and from...
PUBLISHED: 2020-09-19
An issue was discovered in Tiny Tiny RSS (aka tt-rss) before 2020-09-16. The cached_url feature mishandles JavaScript inside an SVG document.
PUBLISHED: 2020-09-19
** DISPUTED ** Typesetter CMS 5.x through 5.1 allows admins to upload and execute arbitrary PHP code via a .php file inside a ZIP archive. NOTE: the vendor disputes the significance of this report because "admins are considered trustworthy"; however, the behavior "contradicts our secu...