dbcve.org
JreApplication · Oracle

CVE-2013-2428

HIGH · 10.0 CVSS v2.0 Published 2013-04-17
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
Unspecified vulnerability 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 affect confidentiality, integrity, and availability via unknown vectors related to JavaFX, a different vulnerability than CVE-2013-0402, CVE-2013-2414, and CVE-2013-2427.

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

Unspecified vulnerability in JavaFX (part of Java SE 7) that allows remote attackers to achieve full compromise (confidentiality, integrity, availability) via unknown vectors in JavaFX. This is a critical remote code execution vulnerability affecting Java 7 Update 17 and earlier, and JavaFX 2.2.7 and earlier.

MitigationUpdate Java SE to version 7 Update 21 or later and JavaFX to version 2.2.8 or later. If the JavaFX applet plugin is in use, consider disabling it in browser settings until patches are applied.

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
JdkApplication
Affected:<= 1.7.0= 1.7.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
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 SE version
    Open command prompt and run: java -version. Alternatively, check the Java Control Panel (Windows: Control Panel > Programs > Java, macOS: System Preferences > Java) to see the version under the General tab.
    Affected if The version shows 1.7.0 or any version below 1.7.0 (such as 1.7.0_17 or earlier)
  2. Check installed JavaFX version
    On Windows, check the JavaFX runtime location typically at C:\Program Files\Oracle\JavaFX Runtime\ or look in the installed programs list. On Linux, check /usr/share/javafx or the user's application data. Run: java -version also displays JavaFX version in some installations, or check the Java deployment configuration files.
    Affected if JavaFX version is 2.2.7 or earlier, or specifically 2.0, 2.0.2, 2.0.3, 2.1, 2.2, 2.2.3, 2.2.4, or 2.2.5
  3. Verify JavaFX browser plugin status
    In Internet Explorer, go to Tools > Manage Add-ons > JavaFX. In Firefox, go to Add-ons > Plugins. In Chrome, go to chrome://plugins. Check if the JavaFX plugin is listed as Enabled.
    Affected if The JavaFX plugin is enabled in any web browser, allowing JavaFX applets to execute in the browser context
  4. Identify running Java processes with JavaFX loaded
    On Windows, open Task Manager and look for javaw.exe or java.exe processes. On Linux, run: ps aux | grep java. Use process monitoring tools to see which Java deployments are active, particularly in browser contexts.
    Affected if A Java 7 process (version 1.7.0 or earlier) is running, especially if associated with a web browser

You are affected if you have Java SE 7 Update 17 or earlier, or JavaFX 2.2.7 or earlier, installed with the JavaFX browser plugin enabled and in use.

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

Update Java SE to version 7 Update 21 or later and JavaFX to version 2.2.8 or later. If the JavaFX applet plugin is in use, consider disabling it in browser settings until patches are applied.

Recommended fix High confidence

Java SE 7 Update 21 or later (or Java SE 8), JavaFX 2.2.8 or later

  1. 1. Identify all systems running Java 7 Update 17 or earlier, or JavaFX 2.2.7 or earlier
  2. 2. Download Java SE 7 Update 21 or later from the official Oracle website (.oracle.com) or your organization's Java distribution channel
  3. 3. For JavaFX applications, ensure JavaFX is updated to version 2.2.8 or later
  4. 4. Uninstall or remove older vulnerable Java versions from affected systems
  5. 5. Install the updated Java 7u21+ (or Java 8 which also contains the fix) on all affected systems
  6. 6. Update JAVA_HOME environment variable if necessary to point to the new installation
  7. 7. Verify the installed version by running 'java -version' command
  8. 8. Restart any running Java applications to ensure they use the updated runtime
Caveat Java 7u21 introduced new security prompts for applets and signed applications which may affect user experience; some legacy applications may behave differently

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

Fix this in Jre Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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