Skip to content
Fencer Intel
critical 10.0

CVE-2014-6513 json

Unspecified vulnerability in Oracle Java SE 6u81, 7u67, and 8u20, and Java SE Embedded 7u60, allows remote attackers to affect confidential…

published 2014-10-15 12 y ago modified 2026-06-17 4 mo ago also EUVD-2014-6392

cvss
10.0
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
5.6%
EPSS 5.6% chance of exploitation in 30 days, percentile 93%
public exploits
0
none known

Summary

Unspecified vulnerability in Oracle Java SE 6u81, 7u67, and 8u20, and Java SE Embedded 7u60, allows remote attackers to affect confidentiality, integrity, and availability via vectors related to AWT.

Patch / fix

  • java-1_7_0-openjdk openSUSE Tumbleweed 1.7.0.121-1.1

opensuse advisories openSUSE-SU-2024:10534-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2014-6513 updated cvss 6.8

OpenJDK: splash image handling memory corruption (AWT, 8042609)

  • Red Hat Enterprise Linux 5 java-1.6.0-ibm, java-1.6.0-sun, java-1.7.0-ibm, java-1.7.0-oracle, java-1.6.0-openjdk, java-1.6.0-sun-src, +10 more Red Hat Enterprise Linux 6 java-1.6.0-ibm, java-1.6.0-sun, java-1.7.1-ibm, java-1.7.0-oracle, java-1.6.0-ibm-src, java-1.6.0-openjdk, +28 more Red Hat Enterprise Linux 7 java-1.6.0-sun, java-1.7.1-ibm, java-1.7.0-oracle, java-1.6.0-openjdk, java-1.6.0-sun-src, java-1.7.0-openjdk, +21 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

5.64% chance of exploitation in the next 30 days, higher than 93% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 10.0 AV:N/AC:L/Au:N/C:C/I:C/A:C

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.