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

4/23/2019
02:45 PM
Connect Directly
Twitter
LinkedIn
RSS
E-Mail
100%
0%

Exploits for Adobe Vulnerabilities Spiked in 2018

With Flash Player on way out, attackers are renewing their focus on Acrobat Reader, RiskSense found.

Malware authors weaponized more Adobe software vulnerabilities in 2018 than any previous year while the actual number of newly disclosed security flaws in the company's products dropped significantly since reaching an all-time-high in 2016.

Security vendor RiskSense recently analyzed over 20 years of Adobe vulnerability data gathered from Adobe's own security bulletins and numerous third-party sources, including bug bounty programs and the national vulnerability database.

The analysis showed that of the 374 new Adobe vulnerabilities disclosed in 2018, exploits or malware became available for 177—or 47%—of them. Fifty of the vulnerabilities were weaponized even before a patch was available.

The numbers are significantly higher than previous years both in terms of the percentage of new vulnerabilities that were weaponized, and in terms of the number of Adobe flaws that were exploitable before patch availability. In 2017, for instance, just 21% of the vulnerabilities disclosed had associated exploits and malware. Similarly, the rate of exploits in the wild before patch availability was some three times higher last year than the previous high set in 2010, RiskSense said.

Ironically, the increased and accelerated weaponization of Adobe vulnerabilities happened during a year in which the overall number of new vulnerabilities disclosed was 31% lower than the record 538 vulnerabilities reported in 2016.

"2018 was definitely exceptional in terms of the weaponization of [Adobe] vulnerabilities," says Anand Paturi, manager of product research for RiskSense. What's not clear is whether the numbers are an anomaly or are indicative of a new trend, he says.

Paturi says that while malware authors were responsible for weaponizing some vulnerabilities, security researchers contributed to the situation as well by releasing proof-of-exploit code for Adobe flaws, sometimes before patch availability.  

"While this code is often very important for helping to understand the vulnerability and demonstrate its severity, this information can also sometimes accelerate the development of threats by attackers," Paturi says.

Acrobat Reader, Flash Player Most Vunlerable

RiskSense's study found that a total of 2,891 vulnerabilities were reported in Adobe products between 1996 and the end of 2018—a vast majority of them in Acrobat Reader and Flash Player. Reader accounted for 1,338 vulnerabilities, while Flash Player had 1,083.

Adobe's cloud-hosted Acrobat DC was another big contributor to the overall vulnerability count, with 300 since the product's 2015 launch. Nearly four-in-ten (38%) of the reported vulnerabilities in Adobe's products over the past 20 years were buffer overflows.

Exploits and malware are currently available for 721 of the vulnerabilities, of which 152 are either remotely exploitable, enable privilege escalation, or are associated with Web apps.

Security experts in recent years have considered Flash Player in particular as a major security threat because of the number of vulnerabilities—including numerous zero-days—that have been discovered in the product over the years. Attackers have frequently exploited Flash vulnerabilities to attack users across multiple platforms, and exploits for these flaws have been a staple in exploit kits such as Neutrino and Angler for years.

However, Adobe's decision to kill off Flash Player by 2020 has resulted in an overall decline in attacker interest in the technology - and a renewed focus on Acrobat Reader instead, Paturi says. Last year, there were just 24 reported Flash Player vulnerabilities.

This was a result of both Flash Player becoming less popular and of browser vendors adding security improvements to address Flash-related threats. "This has shifted attention to Adobe Acrobat Reader," Paturi note. "As the browser-based exploits of Flash have dried up, attackers are having to work a bit harder and are shifting attention back to attacking Reader," he says.

"Specifically, we are seeing a spike in remote code execution (RCE) exploits in Acrobat Reader and we expect to see that continue to rise."

Related Content:

 

 

 

Join Dark Reading LIVE for two cybersecurity summits at Interop 2019. Learn from the industry's most knowledgeable IT security experts. Check out the Interop agenda here.

Jai Vijayan is a seasoned technology reporter with over 20 years of experience in IT trade journalism. He was most recently a Senior Editor at Computerworld, where he covered information security and data privacy issues for the publication. Over the course of his 20-year ... 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 9/25/2020
Hacking Yourself: Marie Moe and Pacemaker Security
Gary McGraw Ph.D., Co-founder Berryville Institute of Machine Learning,  9/21/2020
Startup Aims to Map and Track All the IT and Security Things
Kelly Jackson Higgins, Executive Editor at Dark Reading,  9/22/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
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
CVE-2020-15208
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, when determining the common dimension size of two tensors, TFLite uses a `DCHECK` which is no-op outside of debug compilation modes. Since the function always returns the dimension of the first tensor, malicious attackers can ...
CVE-2020-15209
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, a crafted TFLite model can force a node to have as input a tensor backed by a `nullptr` buffer. This can be achieved by changing a buffer index in the flatbuffer serialization to convert a read-only tensor to a read-write one....
CVE-2020-15210
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, if a TFLite saved model uses the same tensor as both input and output of an operator, then, depending on the operator, we can observe a segmentation fault or just memory corruption. We have patched the issue in d58c96946b and ...
CVE-2020-15211
PUBLISHED: 2020-09-25
In TensorFlow Lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, saved models in the flatbuffer format use a double indexing scheme: a model has a set of subgraphs, each subgraph has a set of operators and each operator has a set of input/output tensors. The flatbuffer format uses indices f...
CVE-2020-15212
PUBLISHED: 2020-09-25
In TensorFlow Lite before versions 2.2.1 and 2.3.1, models using segment sum can trigger writes outside of bounds of heap allocated buffers by inserting negative elements in the segment ids tensor. Users having access to `segment_ids_data` can alter `output_index` and then write to outside of `outpu...