dbcve.org
JdkApplication · Oracle

CVE-2014-6513

HIGH · 10.0 CVSS v2.0 Published 2014-10-15
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A critical vulnerability in the Abstract Window Toolkit (AWT) component of Oracle Java SE versions 6u81, 7u67, 8u20 and Java SE Embedded 7u60 allows remote unauthenticated attackers to execute arbitrary code with the privileges of the Java process, achieving complete compromise of confidentiality, integrity, and availability.

MitigationUpgrade to Oracle's patched Java SE versions (post-8u20) or apply the relevant CPU patch. Given the CVSS 10 severity and network-exploitable nature, prioritize immediate patching of all affected Java installations.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
JdkApplication
Affected:= 1.6.0= 1.7.0
JreApplication
Affected:= 1.6.0= 1.7.0= 1.8.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Java SE version
    Run 'java -version' from command line or check registry at HKLM\SOFTWARE\JavaSoft\Java Development Kit\CurrentVersion (Windows) or /Library/Java/JavaVirtualMachines/ (Mac)
    Affected if Version matches 1.6.0_81, 1.7.0_67, or 1.8.0_20 specifically
  2. Check Java vendor and update number
    Run 'java -fullversion' or 'java -version -verbose' to get the full update version string including the build number
    Affected if The update version is exactly 6u81, 7u67, or 8u20 (these specific patch levels contain the vulnerability)
  3. Determine if Java Web Start or browser plugin is enabled
    Check browser configuration for Java plugin (usually at Control Panel > Java > Security > Enable Java content in browser) or look for javaws.exe process
    Affected if Java browser plugin or Web Start is enabled, as this vulnerability can be exploited via malicious web pages
  4. Verify AWT component is present
    Check for awt.jar in the JRE lib directory (such as $JAVA_HOME/jre/lib/rt.jar or the awt module in Java 9+)
    Affected if AWT libraries are present in the installation, which is default for standard Java SE installations

The environment is affected if Java SE versions 6u81, 7u67, or 8u20 are installed with AWT component present and network-facing Java applications or browser plugin enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch www.oracle.com →
Interim mitigation

Upgrade to Oracle's patched Java SE versions (post-8u20) or apply the relevant CPU patch. Given the CVSS 10 severity and network-exploitable nature, prioritize immediate patching of all affected Java installations.

Recommended fix High confidence

Java 6u85+/Java 7u75+/Java 8u25+ (upgrade to the latest available JDK/JRE version within your major version line or migrate to Java 11+ LTS for better security support)

  1. Check the current Java version by running 'java -version' in the terminal
  2. Identify which Java version (1.6, 1.7, or 1.8) is currently installed
  3. Download the latest Java update from the official Oracle Java SE Downloads page: https://www.oracle.com/java/technologies/downloads/
  4. For Java 1.6 (Java 6): Upgrade to Java 6u85 or later
  5. For Java 1.7 (Java 7): Upgrade to Java 7u75 or later
  6. For Java 1.8 (Java 8): Upgrade to Java 8u25 or later
  7. Run the installer for the chosen version, following the on-screen prompts
  8. Verify the installation by running 'java -version' again to confirm the new version is active
Caveat Security upgrades within the same major version typically have minimal breaking changes; however, some deprecated APIs or behavioral changes may affect legacy applications

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Jdk Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the patch applied

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-6513 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2014-6513 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data