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.

Vulnerabilities / Threats

Adobe Issues Emergency Patch Following December Miss

The company released an out-of-band update to head off vulnerabilities exposed in Acrobat and Reader, one of which had been patched by the company in December.

Adobe today issued an emergency security update, kicking off the new year with an out-of-band software fix to button up two critical flaws in Adobe Acrobat and Reader.

The advisory—Security Bulletin for Adobe Acrobat and Reader (APSB19-02)—outlines two vulnerabilities, but gives very little detail on the issues. In a more detailed advisory sent out to media, the company acknowledged two researchers, Abdul-Aziz Hariri and Sebastian Apelt, who regularly submit vulnerability research to Trend Micro's Zero Day Initiative, thanking Hariri for "his defense-in-depth contribution to hardening JavaScript API restriction bypasses."

While Adobe typically releases updates for its software on a schedule mimicking Microsoft's regular cadence of the second Tuesday of the month, the latest patch appears to be an emergency release. The company stated that its analysts are unaware of any exploitation of the vulnerabilities in the wild.

"These updates address critical vulnerabilities," the company wrote in the advisory. "Successful exploitation could lead to arbitrary code execution in the context of the current user."

The vulnerability (CVE-2018-19725) discovered by Hariri, an internal ZDI researcher, "addresses an incomplete fix from a previous security patch," Brian Gorenc, director of Trend Micro's Zero Day Initiative, told Dark Reading via an e-mail interview. "It allows overwriting JavaScript Read-Only variables, which is somewhat rare."

The second vulnerability (CVE-2018-16011) had apparently reached the 120-day disclosure deadline, after which ZDI would have released details of the issue. "By releasing a patch today, Adobe avoided the 0day disclosure and corrected the incomplete December patch," Gorenc said. Adobe had included the vulnerability as one of the issues fixed by its Dec. 11 patch, according to a previous Adobe advisory.

Adobe did not release details of the software components fixed by the update. The vulnerabilities, however, sound similar to previous vulnerabilities investigated by the two researchers into a dynamically linked library (DLL) that allows indexing of content in PDF documents. The 2014-era library, Onix.dll, creates indexes for searching, according to one 2018 blog post by Hariri. The two researchers credited with finding the vulnerabilities had both been working on auditing the library, according to a later blog post written by Hariri in December.

"[W]hen the Catalog bugs went public, Sebastian Apelt reached out and mentioned that he was also researching the indexing attack surface," Hariri wrote. "What was fascinating about Sebastian's research is figuring out a way to bypass the restrictions Adobe thought they had in place to prevent parsing the Indexing files from JavaScript."

The language almost exactly matches Adobe’s acknowledgement of Hariri's work. 

ZDI, however, denied that the current vulnerabilities are connected to that previous research. "These bugs are unrelated to the bugs discussed in that blog," Gorenc said.

Vulns on the Rise

In 2018, the number of overall vulnerabilities reported publicly increased by more than 13% to 16,518, according to the latest data from the National Vulnerability Database. The vulnerability count will continue to increase throughout 2019 as more issues are retroactively reported.

While software vendors usually find the best way to patch a vulnerability, failing to close off all avenues of exploitation is not an uncommon occurrence. Researchers often find ways to work around the fixes created by software firms. And, sometimes, the only way to fix the issues is to remove a feature, Hariri wrote in his December post.

"It's amazing how much individual research can expose. Even the vendor thought that the attack surface was mitigated," he said. "Anyway, Adobe finally figured out a scientific way to fix the bugs in this attack surface—killing the whole parsing code."

Related Content:

 

Veteran technology journalist of more than 20 years. Former research engineer. Written for more than two dozen publications, including CNET News.com, Dark Reading, MIT's Technology Review, Popular Science, and Wired News. Five awards for journalism, including Best Deadline ... View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 7/9/2020
Russian Cyber Gang 'Cosmic Lynx' Focuses on Email Fraud
Kelly Sheridan, Staff Editor, Dark Reading,  7/7/2020
Why Cybersecurity's Silence Matters to Black Lives
Tiffany Ricks, CEO, HacWare,  7/8/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal, a Dark Reading Perspective
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
The Threat from the Internetand What Your Organization Can Do About It
The Threat from the Internetand What Your Organization Can Do About It
This report describes some of the latest attacks and threats emanating from the Internet, as well as advice and tips on how your organization can mitigate those threats before they affect your business. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2012-6486
PUBLISHED: 2020-07-10
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was in a CNA pool that was not assigned to any issues during 2012. Notes: none.
CVE-2012-6487
PUBLISHED: 2020-07-10
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was in a CNA pool that was not assigned to any issues during 2012. Notes: none.
CVE-2012-6488
PUBLISHED: 2020-07-10
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was in a CNA pool that was not assigned to any issues during 2012. Notes: none.
CVE-2012-6489
PUBLISHED: 2020-07-10
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was in a CNA pool that was not assigned to any issues during 2012. Notes: none.
CVE-2012-6490
PUBLISHED: 2020-07-10
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was in a CNA pool that was not assigned to any issues during 2012. Notes: none.