Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 920181 - (CVE-2013-2550) CVE-2013-2550 acroread: Unspecified vulnerability allows attackers to bypass the sandbox protection mechanism (CanSecWest 2013)
CVE-2013-2550 acroread: Unspecified vulnerability allows attackers to bypass ...
Status: CLOSED NOTABUG
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
impact=moderate,public=20130307,repor...
: Security
Depends On:
Blocks: 920183
  Show dependency treegraph
 
Reported: 2013-03-11 10:09 EDT by Jan Lieskovsky
Modified: 2015-07-31 03:00 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-03-14 05:35:58 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Jan Lieskovsky 2013-03-11 10:09:06 EDT
Common Vulnerabilities and Exposures assigned an identifier CVE-2013-2550 to the following vulnerability:

Unspecified vulnerability in Adobe Reader 11.0.02 allows attackers to bypass the sandbox protection mechanism via unknown vectors, as demonstrated by George Hotz during a Pwn2Own competition at CanSecWest 2013.

References:
[1] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-2550
[2] http://h30499.www3.hp.com/t5/HP-Security-Research-Blog/Pwn2Own-2013/ba-p/5981157
[3] http://twitter.com/thezdi/statuses/309771882612281344
Comment 1 Huzaifa S. Sidhpurwala 2013-03-14 05:35:58 EDT
Adobe has indicated that this issue does not affect the version of Adobe Reader shipped with Linux.

Statement:

Not Vulnerable. This issue does not affect the version of acroread as shipped with Red Hat Enterprise Linux 5 and 6.

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