Attacks/Breaches
10/26/2016
05:00 PM
Connect Directly
Twitter
LinkedIn
RSS
E-Mail
50%
50%

Adobe Rushes Out Emergency Patch For Critical Flash Player Vulnerability

Exploit, available in the wild, is being used in attacks against Windows users, company warns.

As it has numerous times in the past, Adobe this week rushed out an emergency patch to fix a critical vulnerability in its Flash Player software that would have let attackers take complete control of a vulnerable system.

An exploit for the vulnerability is available in the wild and is already being used in attacks against users running Windows versions 7, 8.1 and 10, Adobe warned in an advisory Wednesday.

The company has released updates addressing the flaw in Adobe Flash Player for Windows, Linux, Macintosh and Chrome OS. 

The vulnerability exists in Adobe Flash Player versions 23.0.0.185 and earlier for Windows, Macintosh, Linux and Chrome OS. Also affected are versions 11.2.202.637 and earlier of Adobe Flash Player for Linux.

Adobe defines a critical vulnerability as any security flaw that if exploited would allow an attacker to run arbitrary code on a system without the user’s knowledge. In this case, the company described the flaw as a use-after-free vulnerability that could lead to remote code execution.

Use-after-free errors, according to the Open Web Application Security Project  (OWASP), are a class of security vulnerabilities involving the use of heap allocated memory space after it has been freed or deleted.

The use of such memory can result in error conditions and other unexpected behavior, ranging from data corruption to system crashes to arbitrary code execution, according to the OWASP.

Adobe credited Neel Mehta and Billy Leonard, two security researchers belonging to Google’s Threat Analysis Group, for discovering and reporting the flaw.

Emergency patch releases are not unusual at all for Adobe. At numerous times in the past few years, the company has been forced to rush out critical fixes for flaws and exploits in its products. Many of them have involved Flash Player, a product that over the years has acquired the unfortunate reputation of being one of the buggiest products currently in use.

Since October 2015, Adobe has issued 16 updates for multiple critical Flash Player vulnerabilities, several of which were out-of-cycle releases. The company’s security bulletins and advisories page shows that no other Adobe product has been patched quite as often as Flash Player.

In its Internet Security Threat Report released earlier this year Symantec noted how four of the five most widely exploited zero-day vulnerabilities last year were in Adobe Flash. In 2015, about 17 percent of all zero-days vulnerabilities that were discovered were in Adobe Flash and that was actually lower than the 50 percent of similar flaws it accounted for in 2014 and 22 percent in 2013, according to Symantec.

More than 30 of the 260 vulnerability advisories that are pending disclosure from Tipping Point’s Zero Day Initiative involve Adobe, though it is not clear how many of them are specific to Flash.

As Symantec noted in the report, multiple organizations including Google, Mozilla and Apple have voiced serious concerns over Adobe Flash, with Google saying it will drop native support for the technology in Chrome this year.

Related stories:

 

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

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Security Operations and IT Operations: Finding the Path to Collaboration
A wide gulf has emerged between SOC and NOC teams that's keeping both of them from assuring the confidentiality, integrity, and availability of IT systems. Here's how experts think it should be bridged.
Flash Poll
New Best Practices for Secure App Development
New Best Practices for Secure App Development
The transition from DevOps to SecDevOps is combining with the move toward cloud computing to create new challenges - and new opportunities - for the information security team. Download this report, to learn about the new best practices for secure application development.
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-7445
Published: 2015-10-15
The Direct Rendering Manager (DRM) subsystem in the Linux kernel through 4.x mishandles requests for Graphics Execution Manager (GEM) objects, which allows context-dependent attackers to cause a denial of service (memory consumption) via an application that processes graphics data, as demonstrated b...

CVE-2015-4948
Published: 2015-10-15
netstat in IBM AIX 5.3, 6.1, and 7.1 and VIOS 2.2.x, when a fibre channel adapter is used, allows local users to gain privileges via unspecified vectors.

CVE-2015-5660
Published: 2015-10-15
Cross-site request forgery (CSRF) vulnerability in eXtplorer before 2.1.8 allows remote attackers to hijack the authentication of arbitrary users for requests that execute PHP code.

CVE-2015-6003
Published: 2015-10-15
Directory traversal vulnerability in QNAP QTS before 4.1.4 build 0910 and 4.2.x before 4.2.0 RC2 build 0910, when AFP is enabled, allows remote attackers to read or write to arbitrary files by leveraging access to an OS X (1) user or (2) guest account.

CVE-2015-6333
Published: 2015-10-15
Cisco Application Policy Infrastructure Controller (APIC) 1.1j allows local users to gain privileges via vectors involving addition of an SSH key, aka Bug ID CSCuw46076.

Dark Reading Radio