Bug 850529 (CVE-2012-4168) - CVE-2012-4168 flash-plugin: cross-domain information leak flaw (APSB12-19)
Summary: CVE-2012-4168 flash-plugin: cross-domain information leak flaw (APSB12-19)
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2012-4168
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 848191 848192 848634 848635
Blocks: 850534
TreeView+ depends on / blocked
 
Reported: 2012-08-21 18:49 UTC by Vincent Danen
Modified: 2021-02-23 14:03 UTC (History)
5 users (show)

Fixed In Version: flash-plugin 11.2.202.238
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-23 17:07:53 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2012:1203 0 normal SHIPPED_LIVE Critical: flash-plugin security update 2012-08-23 20:28:08 UTC

Description Vincent Danen 2012-08-21 18:49:09 UTC 
Adobe security bulletin APSB12-19 describes one security flaw that could cause Adobe Flash Player to leak confidential information:

These updates resolve a cross-domain information leak vulnerability (CVE-2012-4168).


External Reference:

http://www.adobe.com/support/security/bulletins/apsb12-19.html
Comment 1 Vincent Danen 2012-08-21 19:00:28 UTC 
According to the APSB12-19 advisory, these are fixed in 11.2.202.238 which was provided with RHSA-2012:1173 (and upstream APSB12-18).  Attempting to confirm this is not a typo or mistake.
Comment 2 Vincent Danen 2012-08-23 16:19:56 UTC 
This issue has been addressed in following products:

  Supplementary for Red Hat Enterprise Linux 6

Via RHSA-2012:1173 https://rhn.redhat.com/errata/RHSA-2012-1173.html
Comment 3 errata-xmlrpc 2012-08-23 16:29:22 UTC 
This issue has been addressed in following products:

  Supplementary for Red Hat Enterprise Linux 5

Via RHSA-2012:1203 https://rhn.redhat.com/errata/RHSA-2012-1203.html
Note You need to log in before you can comment on or make changes to this bug.