dbcve.org
JreApplication · Oracle

CVE-2013-2414

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-2427, and CVE-2013-2428.

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 component of Oracle Java SE 7 Update 17 and earlier allowing remote attackers to achieve full compromise (confidentiality, integrity, availability) through unknown attack vectors. This is a remote code execution vulnerability in the Java client plugin.

MitigationUpdate to patched Java versions beyond Update 17, or disable Java browser plugins and remove old Java installations if updates 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
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 if Java JRE/JDK is installed
    Run 'java -version' in command prompt or terminal
    Affected if If Java responds with a version number, Java is installed. If version shows 1.7.x (such as 1.7.0_xx) or earlier, it is in the affected range.
  2. Confirm Java version details
    Run 'java -fullversion' or check the JRE/JDK installation directory for the version string (usually in the filename or release file)
    Affected if If the full version shows 1.7.0_17 or earlier, the installation is within the affected version range.
  3. Check if JavaFX is installed
    Look for javafx runtime files in the Java installation directory, typically under lib/javafx.jar or similar paths, or run 'java -version' and check for JavaFX in the runtime
    Affected if If JavaFX runtime is present and its version is 2.0, 2.0.2, 2.0.3, 2.1, 2.2, 2.2.3, 2.2.4, 2.2.5, or <= 2.2.7, the component is affected.
  4. Check if Java browser plugin is enabled
    Inspect browser plugin configuration: in Windows check Java Control Panel > Security tab > 'Enable Java content in the browser'; in browsers check for enabled Java plugin in add-on settings
    Affected if If the Java browser plugin is enabled, the vulnerability can be exploited remotely via malicious web pages or applets.

A user is affected if they have Java or JDK/JRE version 1.7.0_17 or earlier with JavaFX installed, and the Java browser plugin is enabled for running applets in browsers.

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 to patched Java versions beyond Update 17, or disable Java browser plugins and remove old Java installations if updates are not feasible.

Recommended fix High confidence

Java SE 7 Update 21 or later (or Java SE 8.x)

  1. Identify all systems running affected Java versions (JRE/JDK <= 1.7.0 or JavaFX <= 2.2.7)
  2. Download Java SE 7 Update 21 or later from Oracle's official Java SE download page (https://www.oracle.com/java/technologies/downloads/)
  3. Remove or uninstall older vulnerable Java installations
  4. Install the updated Java SE 7 Update 21 or later (or migrate to Java SE 8 which also contains the fix)
  5. Verify the new Java version by running 'java -version' in command line
  6. Ensure JAVA_HOME environment variable points to the new installation
  7. Restart any applications or services using Java to ensure they use the patched version
Caveat Applications may require testing for compatibility with newer Java versions; some deprecated APIs or behaviors may differ

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

Fix this in Jre Scoped from the published advisory
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,730
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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