Vulnerability Note VU#918568
Adobe Flash ActionScript 3 BitmapData memory corruption vulnerability
Original Release date: 12 Jul 2015 | Last revised: 14 Jul 2015
Adobe Flash Player contains a vulnerability in the ActionScript 3 BitmapData object, which can allow a remote, unauthenticated attacker to execute arbitrary code on a vulnerable system.
Adobe Flash Player versions 9.0 through version 220.127.116.11 contain amemory corruption vulnerability in the AS3 BitmapData class. Proof-of-concept exploit code for this vulnerability is publicly available.
Please see Adobe Security Bulletin APSA15-04 for more details about affected Flash versions.
An attacker may be able to execute arbitrary code in the context of the user running Flash Player. Attacks typically involve enticing a user to visit a web site containing specially-crafted Flash content, or to open a specially-crafted Microsoft Office document.
Apply an update
This issue is addressed in Flash Player Desktop 18.104.22.168. See Adobe Security Bulletin APSB15-18 for more details. Please also consider the following workarounds:
Do not run untrusted Flash content
To defend against this and other, as yet unknown vulnerabilities, disable Flash in your browser or enable Click-to-Play features. Adobe has also provided instructions for how to uninstall Flash on Windows and Mac platforms.
Use the Microsoft Enhanced Mitigation Experience Toolkit
The Microsoft Enhanced Mitigation Experience Toolkit (EMET) can be used to help prevent exploitation of this vulnerability. In particular, Attack Surface Reduction (ASR) can be configured to help restrict Microsoft Office and Internet Explorer from loading the Flash ActiveX control.
Vendor Information (Learn More)
VendorStatusDate NotifiedDate UpdatedAdobeAffected-12 Jul 2015If you are a vendor and your product is affected, let
CVSS Metrics (Learn More)
This vulnerability was reported by TrendMicro, based on the HackingTeam leak.
This document was written by Will Dormann.
05 Jul 2015
Date First Published:
12 Jul 2015
Date Last Updated:
14 Jul 2015
FeedbackIf you have feedback, comments, or additional information about this vulnerability, please send us email.