dbcve.org
JavafxApplication · Oracle

CVE-2013-0402

HIGH · 10.0 CVSS v2.0 Published 2013-03-08
Fix available
A fix is available. Upgrade to after 2.2.7 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Heap-based buffer overflow in the Java Runtime Environment (JRE) component in Oracle Java SE 7 Update 17 and earlier and JavaFX 2.2.7 and earlier allows remote attackers to execute arbitrary code via unspecified vectors related to JavaFX, as demonstrated by VUPEN during a Pwn2Own competition at CanSecWest 2013.

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 · high confidence

Heap-based buffer overflow vulnerability in Oracle Java SE 7 (Update 17 and earlier) and JavaFX 2.2.7 and earlier allows remote attackers to execute arbitrary code via unspecified vectors in the JavaFX component. The flaw was demonstrated at CanSecWest 2013 Pwn2Own.

MitigationUpgrade to Java SE 7 Update 21 or later and JavaFX 2.2.7 or later to resolve this vulnerability. Remove or disable older Java installations if upgrades are not feasible.

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
JavafxApplication
Affected:<= 2.2.7
JdkApplication
Affected:= 1.7.0
JreApplication
Affected:= 1.7.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. Check installed Java JRE version
    Open command prompt or terminal and run: java -version. Look for version string showing 1.7.0 followed by update number (e.g., 1.7.0_17 or earlier)
    Affected if Version displays as 1.7.0 with update number 17 or lower (such as 1.7.0_15, 1.7.0_10, etc.)
  2. Check installed Java JDK version
    Open command prompt or terminal and run: javac -version. Compare output to affected version range
    Affected if Version displays as 1.7.0 with update number 17 or lower
  3. Check JavaFX runtime version
    On Windows, check for JavaFX installation in Program Files or verify via command: java -version and examine if JavaFX is listed. Check for javafx.properties file in the Java installation directory
    Affected if JavaFX version is 2.2.7 or earlier, or version cannot be determined but JavaFX is present with Java 7
  4. Verify Java and JavaFX are used together
    Confirm that JavaFX applications or plugins are in use, as the vulnerability exists specifically within the JavaFX component. Check browser Java plugins or JavaFX application deployments
    Affected if JavaFX is installed and enabled as a plugin or runtime component alongside Java SE 7 Update 17 or earlier

User is affected if Java SE 7 (any update up to and including 17) or JavaFX 2.2.7 or earlier is installed and the JavaFX component is present and enabled in the environment.

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
Upgrade available Upgrade to a release after 2.2.7
Interim mitigation

Upgrade to Java SE 7 Update 21 or later and JavaFX 2.2.7 or later to resolve this vulnerability. Remove or disable older Java installations if upgrades are not feasible.

Recommended fix High confidence

Java SE 7 Update 21 or later (or Java 8 for extended support)

  1. 1. Identify the current Java version installed by running 'java -version' in the terminal
  2. 2. Download Java SE 7 Update 21 or later from the Oracle official archive (oracle.com/java/technologies/downloads/)
  3. 3. Uninstall the vulnerable Java version via system package manager or manual removal
  4. 4. Install the fixed Java version (JDK/JRE 7u21 or later, or migrate to Java 8 for longer term support
  5. 5. Verify the installation by running 'java -version' and confirm it shows version 7u21 or higher
  6. 6. Update any JAVA_HOME environment variables to point to the new installation path
  7. 7. Update any build tools (Maven, Gradle) to use the new Java version if necessary
Caveat Upgrading from Java 7 to Java 8 may introduce compatibility issues with existing code; test thoroughly before production deployment

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

Fix this in Javafx Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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