dbcve.org
JavafxApplication · Oracle

CVE-2013-0436

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 remote code execution vulnerability in JavaFX 2.2.4 and earlier allows attackers to compromise confidentiality, integrity, and availability through unknown attack vectors. The flaw resides in the JavaFX component of Oracle Java SE and was addressed in the February 2013 Critical Patch Update.

MitigationApply the relevant CPU patch or upgrade Java/JDK to a version that includes the fixed JavaFX component. Prioritize this critical (CVSS 10) update given the remote attack vector and full CIA impact.

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. Locate JavaFX installation directory
    Search for jfxrt.jar file, which is the JavaFX runtime library. Common paths include: Windows: %JAVA_HOME%\lib\jfxrt.jar or %JRE_HOME%\lib\jfxrt.jar; Linux: $JAVA_HOME/jre/lib/jfxrt.jar or /usr/share/java/jfxrt.jar. Use file search or check your Java installation path.
    Affected if JavaFX is present on the system (jfxrt.jar exists)
  2. Determine JavaFX version from JAR manifest
    Navigate to the jfxrt.jar location and extract version information. On Windows command line: jar tf "path\to\jfxrt.jar" META-INF\MANIFEST.MF | findstr VERSION. Or open the manifest file directly to read the Implementation-Version attribute.
    Affected if The manifest shows version 2.2.4 or earlier, or shows one of the specific affected versions (2.0, 2.0.2, 2.0.3, 2.1, 2.2, 2.2.3)
  3. Check Java version that ships JavaFX
    Run java -version from command line to identify the Java SE version. Note that JavaFX is bundled with certain Java SE distributions. Check if your Java version corresponds to a release that included the vulnerable JavaFX versions.
    Affected if Java version is 7u10 through 7u15, or earlier versions that bundled JavaFX 2.2.4 or earlier (JavaFX was bundled starting roughly Java SE 7u2)
  4. Verify JavaFX is loaded in running applications
    Check application configurations, deployment descriptors, or startup scripts for references to JavaFX classes (javafx.* packages) or the jfxrt.jar in classpath. On Linux, also check: ls -la /usr/lib/jvm/ | grep java to list installed Java versions.
    Affected if Applications explicitly load or reference JavaFX classes or have jfxrt.jar in their runtime classpath

If jfxrt.jar exists and its version is 2.2.4 or any of the listed affected versions (2.0, 2.0.2, 2.0.3, 2.1, 2.2, 2.2.3), or if your Java SE version bundled a vulnerable JavaFX version, your environment is affected by CVE-2013-0436.

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

Apply the relevant CPU patch or upgrade Java/JDK to a version that includes the fixed JavaFX component. Prioritize this critical (CVSS 10) update given the remote attack vector and full CIA impact.

Recommended fix Moderate confidence

JavaFX 2.2.5 or later (Java SE 7u15/7u17 or later which includes bundled JavaFX fixes from February 2013 CPU)

  1. 1. Identify all JavaFX installations in the environment using the affected versions (<=2.2.4, 2.0, 2.0.2, 2.0.3)
  2. 2. Verify the current JavaFX version by checking the installed Java runtime components
  3. 3. Download and install JavaFX 2.2.5 or later from the official Oracle Java download page
  4. 4. Ensure the updated JavaFX runtime is deployed to all systems and applications using the affected component
  5. 5. Restart any Java applications or services that use JavaFX to load the updated libraries
  6. 6. Verify the patch was applied successfully by checking the JavaFX version after installation
Caveat JavaFX 2.2.5 was a patch update; minimal breaking changes expected but test applications using JavaFX functionality before production deployment

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

Fix this in Javafx Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA2.0 h
17.0 hours of engineering $2,880
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,608.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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