Bug 704368 (APSB11-12, CVE-2011-0579, CVE-2011-0618, CVE-2011-0619, CVE-2011-0620, CVE-2011-0621, CVE-2011-0622, CVE-2011-0623, CVE-2011-0624, CVE-2011-0625, CVE-2011-0626, CVE-2011-0627, CVE-2011-0628) - CVE-2011-0579 CVE-2011-0618 CVE-2011-0619 CVE-2011-0620 CVE-2011-0621 CVE-2011-0622 CVE-2011-0623 CVE-2011-0624 CVE-2011-0625 CVE-2011-0626 CVE-2011-0627 CVE-2011-0628 flash-plugin: crash and potential arbitrary code execution (APSB11-12)
Summary: CVE-2011-0579 CVE-2011-0618 CVE-2011-0619 CVE-2011-0620 CVE-2011-0621 CVE-201...
Keywords:
Status: CLOSED ERRATA
Alias: APSB11-12, CVE-2011-0579, CVE-2011-0618, CVE-2011-0619, CVE-2011-0620, CVE-2011-0621, CVE-2011-0622, CVE-2011-0623, CVE-2011-0624, CVE-2011-0625, CVE-2011-0626, CVE-2011-0627, CVE-2011-0628
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
urgent
urgent
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 704369 704370
Blocks: 720636
TreeView+ depends on / blocked
 
Reported: 2011-05-12 22:24 UTC by Vincent Danen
Modified: 2019-09-29 12:45 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-11-14 23:15:09 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2011:0511 0 normal SHIPPED_LIVE Critical: flash-plugin security update 2011-05-13 09:06:15 UTC

Description Vincent Danen 2011-05-12 22:24:03 UTC
Adobe has released APSB11-12 [1] along with Flash Player 10.3.181.14 to correct a number of critical flaws.  The flaws are described as:

Critical vulnerabilities have been identified in Adobe Flash Player 10.2.159.1 and earlier versions (Adobe Flash Player 10.2.154.28 and earlier for Chrome users) for Windows, Macintosh, Linux and Solaris, and Adobe Flash Player 10.2.157.51 and earlier versions for Android. These vulnerabilities could cause the application to crash and could potentially allow an attacker to take control of the affected system. There are reports of malware attempting to exploit one of the vulnerabilities, CVE-2011-0627, in the wild via a Flash (.swf) file embedded in a Microsoft Word (.doc) or Microsoft Excel (.xls) file delivered as an email attachment targeting the Windows platform. However, to date, Adobe has not obtained a sample that successfully completes an attack.

This update resolves a design flaw that could lead to information disclosure (CVE-2011-0579).

This update resolves an integer overflow vulnerability that could lead to code execution (CVE-2011-0618).

This update resolves a memory corruption vulnerability that could lead to code execution (CVE-2011-0619).

This update resolves a memory corruption vulnerability that could lead to code execution (CVE-2011-0620).

This update resolves a memory corruption vulnerability that could lead to code execution (CVE-2011-0621).

This update resolves a memory corruption vulnerability that could lead to code execution (CVE-2011-0622).

This update resolves a bounds checking vulnerability that could lead to code execution (CVE-2011-0623).

This update resolves a bounds checking vulnerability that could lead to code execution (CVE-2011-0624).

This update resolves a bounds checking vulnerability that could lead to code execution (CVE-2011-0625).

This update resolves a bounds checking vulnerability that could lead to code execution (CVE-2011-0626).

This update resolves a memory corruption vulnerability that could lead to code execution (CVE-2011-0627).

Comment 3 errata-xmlrpc 2011-05-13 09:06:20 UTC
This issue has been addressed in following products:

  Supplementary for Red Hat Enterprise Linux 5
  Supplementary for Red Hat Enterprise Linux 6

Via RHSA-2011:0511 https://rhn.redhat.com/errata/RHSA-2011-0511.html

Comment 4 Vincent Danen 2011-05-25 09:04:22 UTC
The upstream advisory added an additional CVE:

This update resolves an integer overflow vulnerability that could lead to code execution (CVE-2011-0628).


Note You need to log in before you can comment on or make changes to this bug.