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 906450 - (CVE-2013-1490) CVE-2013-1490 JDK: complete Java security sandbox bypass (Issue 51)
CVE-2013-1490 JDK: complete Java security sandbox bypass (Issue 51)
Status: CLOSED DUPLICATE of bug 952646
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
urgent Severity urgent
: ---
: ---
Assigned To: Red Hat Product Security
impact=critical,public=20130127,repor...
: Security
Depends On:
Blocks: 906458
  Show dependency treegraph
 
Reported: 2013-01-31 11:29 EST by Jan Lieskovsky
Modified: 2014-02-28 08:25 EST (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2014-02-28 08:25:22 EST
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-01-31 11:29:49 EST
Common Vulnerabilities and Exposures assigned an identifier CVE-2013-1490 to the following vulnerability:

Unspecified vulnerability in Oracle Java SE 7 Update 11 (JRE 1.7.0_11-b21) allows user-assisted remote attackers to bypass the Java security sandbox via unspecified vectors, aka "Issue 51," a different vulnerability than CVE-2013-0431. NOTE: as of 20130130, this vulnerability does not contain any independently-verifiable details, and there is no vendor acknowledgement. A CVE identifier is being assigned because this vulnerability has received significant public attention, and the original researcher has an established history of releasing vulnerability reports that have been fixed by vendors. NOTE: this issue also exists in SE 6, but it cannot be exploited without a separate vulnerability.

References:
[1] http://www.securityfocus.com/archive/1/525387/30/0/threaded
[2] http://seclists.org/fulldisclosure/2013/Jan/142
[3] http://seclists.org/fulldisclosure/2013/Jan/195
[4] http://arstechnica.com/security/2013/01/critical-java-vulnerabilies-confirmed-in-latest-version/
[5] http://blogs.computerworld.com/malware-and-vulnerabilities/21693/yet-another-java-security-flaw-discovered-number-53
[6] http://www.informationweek.com/security/application-security/java-hacker-uncovers-two-flaws-in-latest/240146717
Comment 1 Tomas Hoger 2014-02-28 08:23:42 EST
According to the Security Explorations CVE map:

http://www.security-explorations.com/materials/SE-2012-01-CVE_Map.pdf

This public assignment of CVE-2013-1490 was ignored and different id CVE-2013-1518 was used for this issue when it was fixed in Oracle Apr 2013 CPU.  See bug 952646.
Comment 2 Tomas Hoger 2014-02-28 08:25:22 EST

*** This bug has been marked as a duplicate of bug 952646 ***

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