dbcve.org
JavafxApplication · Oracle

CVE-2013-0447

HIGH · 10.0 CVSS v2.0 Published 2013-02-02
Fix available
A fix is available. Upgrade to after 2.2.4 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 JavaFX component in Oracle Java SE JavaFX 2.2.4 and earlier allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors, a different vulnerability than other CVEs listed in the February 2013 CPU.

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 severity (CVSS 10) unspecified vulnerability in JavaFX 2.2.4 and earlier allows remote attackers to fully impact confidentiality, integrity, and availability via unknown vectors. This vulnerability is distinct from other CVEs in the February 2013 Oracle Critical Patch Update but specific exploitation details are not provided.

MitigationUpdate JavaFX to a patched version (apply February 2013 CPU or later) to remediate this critical vulnerability.

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.4= 2.0= 2.0.2= 2.0.3= 2.1= 2.2= 2.2.3

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 if JavaFX is installed
    Locate JavaFX runtime or SDK on the system. Common indicators include the jfxrt.jar file in the JDK/JRE lib directory, or a JavaFX SDK installation folder. Check both standalone installations and bundled JavaFX distributions.
    Affected if JavaFX runtime or SDK is present on the system
  2. Determine the installed JavaFX version
    Query the version of the installed JavaFX component. This can be done by examining the JavaFX jar manifest, version properties, or using command-line tools if available (such as 'java -version' output if JavaFX version is reported, or inspecting the jar file metadata).
    Affected if The installed version cannot be determined or is one of the known affected versions
  3. Compare version against affected range
    Match the discovered version number against the affected versions: 2.0, 2.0.2, 2.0.3, 2.1, 2.2, 2.2.3, or any version up to and including 2.2.4.
    Affected if The installed version is 2.0, 2.0.2, 2.0.3, 2.1, 2.2, 2.2.3, or any version <= 2.2.4

If JavaFX is installed and its version falls within 2.0 through 2.2.4 (inclusive), the environment is affected by this vulnerability.

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.4
Interim mitigation

Update JavaFX to a patched version (apply February 2013 CPU or later) to remediate this critical vulnerability.

Fix this in Javafx Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
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,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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