dbcve.org
JreApplication · Oracle

CVE-2013-2394

HIGH · 7.6 CVSS v2.0 Published 2013-04-17
Fix available
A fix is available. Upgrade to after 2.2.7 or later.
See remediation →
85/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 the Java Runtime Environment (JRE) component in Oracle Java SE 7 Update 17 and earlier, 6 Update 43 and earlier, 5.0 Update 41 and earlier, and JavaFX 2.2.7 and earlier allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors related to 2D, a different vulnerability than CVE-2013-2432 and CVE-2013-1491.

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

CVE-2013-2394 is an unspecified vulnerability in the Java 2D component affecting Java SE 7u17 and earlier, 6u43 and earlier, 5.0u41 and earlier, and JavaFX 2.2.7 and earlier. The vulnerability allows remote attackers to impact confidentiality, integrity, and availability through unknown vectors in the 2D graphics subsystem.

MitigationApply the appropriate CPU (Critical Patch Update) from Oracle that addresses this vulnerability, or upgrade to a supported Java version (Java 8 or later) as the affected versions are End-of-Life. For legacy systems requiring older Java, apply compensating controls such as disabling Java browser plugins and restricting network access to Java applications.

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
JreApplication
Affected:<= 1.7.0= 1.7.0<= 1.6.0= 1.6.0<= 1.5.0= 1.5.0
JdkApplication
Affected:<= 1.7.0= 1.7.0<= 1.6.0= 1.6.0<= 1.5.0= 1.5.0
JreApplication
Affected:= 1.6.0= 1.5.0
JdkApplication
Affected:= 1.6.0= 1.5.0
JavafxApplication
Affected:<= 2.2.7= 2.0= 2.0.2= 2.0.3= 2.1= 2.2= 2.2.3= 2.2.4= 2.2.5

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
High
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:H/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 JRE/JDK version
    Run 'java -version' or 'java -fullversion' from command line to get the exact version string. On Windows, also check via 'java -verbose' or look in Control Panel > Java > Java Runtime Environment Settings.
    Affected if Version shows 1.5.x, 1.6.0 through 1.6.0_43, 1.7.0 through 1.7.0_17, or any earlier release of these major versions (1.5, 1.6, 1.7)
  2. Identify installed JavaFX version
    Check for JavaFX runtime installations. Look in JAVA_HOME/lib/javafx*.jar, or run 'java -jar javafx.jar' if present, or check installation directories like Program Files/Oracle/JavaFX on Windows or /Library/Java/JavaFX on Mac.
    Affected if JavaFX version is 2.0, 2.0.2, 2.0.3, 2.1, 2.2, 2.2.3, 2.2.4, 2.2.5, or any version 2.2.7 and earlier
  3. Verify if Java browser plugin is enabled
    Check browser settings for Java plugin status. In Internet Explorer, go to Manage Add-ons > Java Plug-ins. In Firefox, go to Add-ons > Plugins. In Chrome, go to chrome://plugins. Look for 'Java' plugin entries.
    Affected if Java browser plugin is enabled and running Java 5, 6, or 7 versions (as identified in step 1) - this is the primary attack vector for remote exploitation
  4. Check for Java applets in use
    Inventory web applications that use Java applets. Look for <applet> or <object> tags with 'java.applet' in HTML source, or check application logs for applet initialization messages.
    Affected if Any internal or external web applications load Java applets, combined with vulnerable Java version from step 1

User is affected if they have Java 5, 6 (up to 43), or 7 (up to 17) installed OR JavaFX 2.2.7 or earlier installed, and the Java 2D component is accessible via browser plugin or applet execution.

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.

From vendor data
Upgrade available Upgrade to a release after 2.2.7
Interim mitigation

Apply the appropriate CPU (Critical Patch Update) from Oracle that addresses this vulnerability, or upgrade to a supported Java version (Java 8 or later) as the affected versions are End-of-Life. For legacy systems requiring older Java, apply compensating controls such as disabling Java browser plugins and restricting network access to Java applications.

Fix this in Jre Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-2394 — 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-2013-2394 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