dbcve.org
JreApplication · Oracle

CVE-2013-2444

MEDIUM · 5.0 CVSS v2.0 Published 2013-06-18
Fix available
A fix is available. Upgrade to after 2.2.21 or later.
See remediation →
59/100
Remediation priority · Elevated
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 21 and earlier, 6 Update 45 and earlier, and 5.0 Update 45 and earlier; JavaFX 2.2.21 and earlier; and OpenJDK 7 allows remote attackers to affect availability via vectors related to AWT. NOTE: the previous information is from the June 2013 CPU. Oracle has not commented on claims from another vendor that this issue does not "properly manage and restrict certain resources related to the processing of fonts," possibly involving temporary files.

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 vulnerability in Java's Abstract Window Toolkit (AWT) allows remote attackers to cause a denial of service via improper management and restriction of resources related to font processing, possibly involving temporary files. The issue affects multiple Java SE, JavaFX, and OpenJDK versions.

MitigationApply the appropriate Java Critical Patch Update (CPU) that addresses CVE-2013-2444 by updating to Java 7 Update 25 or later, Java 6 Update 45 or later, or the equivalent fixed versions for JavaFX and OpenJDK.

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<= 1.6.0= 1.6.0<= 1.5.0= 1.5.0
JdkApplication
Affected:<= 1.7.0= 1.7.0<= 1.6.0= 1.6.0<= 1.5.0= 1.5.0
JreApplication
Affected:= 1.6.0= 1.5.0
JdkApplication
Affected:= 1.6.0= 1.5.0
JavafxApplication
Affected:<= 2.2.21= 2.0= 2.0.2= 2.0.3= 2.1= 2.2= 2.2.3= 2.2.4= 2.2.5= 2.2.7

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
None
Integrity
None
Availability
Partial

AV:N/AC:L/Au:N/C:N/I:N/A:P

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. Determine installed Java version
    Run 'java -version' or 'java -fullversion' from command line to obtain the version string (for JDK, also try 'javac -version')
    Affected if Version shows 1.5.0.x, 1.6.0.x, or 1.7.0.x (any update) and falls within the ranges listed in the CVE
  2. Identify Java product type
    Check whether the installation is Oracle JRE, Oracle JDK, Sun JRE, Sun JDK, or JavaFX by examining the vendor string from 'java -version' output and the installed package name
    Affected if The product is Oracle or Sun JRE/JDK version 1.5.0, 1.6.0, or 1.7.0, or JavaFX versions 2.0 through 2.2.21
  3. Check JavaFX version if applicable
    For JavaFX applications, run 'java -version' or check the JavaFX runtime version through the application's about or system properties, as JavaFX has its own version separate from the JRE/JDK
    Affected if JavaFX version is 2.0, 2.0.2, 2.0.3, 2.1, 2.2, 2.2.3, 2.2.4, 2.2.5, 2.2.7, or any version up to and including 2.2.21

You are affected if your Java installation is any Oracle or Sun JRE/JDK version 1.5.0, 1.6.0, or 1.7.0, or any JavaFX version up to 2.2.21, as these versions contain the vulnerable AWT font processing code.

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

Apply the appropriate Java Critical Patch Update (CPU) that addresses CVE-2013-2444 by updating to Java 7 Update 25 or later, Java 6 Update 45 or later, or the equivalent fixed versions for JavaFX and OpenJDK.

Fix this in Jre 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-2444 — 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-2444 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