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 1150118 - (CVE-2014-6513) CVE-2014-6513 OpenJDK: splash image handling memory corruption (AWT, 8042609)
CVE-2014-6513 OpenJDK: splash image handling memory corruption (AWT, 8042609)
Status: CLOSED NOTABUG
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=20141014,repor...
: Security
Depends On:
Blocks: 1148726
  Show dependency treegraph
 
Reported: 2014-10-07 09:18 EDT by Tomas Hoger
Modified: 2014-10-17 07:52 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2014-10-07 09:48:54 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 Tomas Hoger 2014-10-07 09:18:11 EDT
A flaw was found in the way the AWT component of OpenJDK handled splash screen images.  A specially crafted image could possibly cause JVM memory corruption.  A malicious Java application or applet could use this flaw to execute arbitrary code with JVM privileges, bypassing Java sandbox restrictions.

This issue affected native code for Windows platform.  Linux builds of OpenJDK do not use the affected code and are unaffected by this issue.
Comment 1 Tomas Hoger 2014-10-07 09:48:54 EDT
Statement:

Not vulnerable. This issue did not affect the versions of OpenJDK as shipped with Red Hat Enterprise Linux.
Comment 2 Tomas Hoger 2014-10-14 16:29:34 EDT
Public now via Oracle Critical Patch Update - October 2014.  Fixed in Oracle Java SE 6u85, 7u71, and 8u25.

External References:

http://www.oracle.com/technetwork/topics/security/cpuoct2014-1972960.html#AppendixJAVA

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