CVE-2013-5843
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 · uneditedUnspecified vulnerability in Oracle Java SE 7u40 and earlier, Java SE 6u60 and earlier, Java SE 5.0u51 and earlier, JavaFX 2.2.40 and earlier, and Java SE Embedded 7u40 and earlier allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors related to 2D.
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 · high confidenceCritical vulnerability in Oracle Java SE's 2D graphics subsystem (affecting versions 7u40 and earlier, 6u60 and earlier, 5.0u51 and earlier, plus JavaFX 2.2.40 and earlier and Java SE Embedded 7u40 and earlier) allowing remote attackers complete compromise of confidentiality, integrity, and availability via unspecified vectors. The CVSS 10 score indicates trivial exploitability with total system compromise.
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= 5.0= 6.0= 6.4= 5.0= 6.0= 6.4= 5.0= 6.0<= 2.2.40= 1.5.0= 1.6.0= 1.7.0= 1.5.0= 1.6.0= 1.7.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check installed JDK versionRun `java -version` or `javac -version` to display the version string. On RHEL, also run `rpm -qa | grep jdk` to list installed JDK packages.Affected if The version shows 1.7.0 (any update number) or 1.7.0_u followed by a number 40 or lower, OR 1.6.0_u60 or lower, OR 1.5.0_u51 or lower.
-
Check installed JRE versionRun `java -version`. On RHEL, run `rpm -qa | grep jre` to list installed JRE packages.Affected if The version shows JRE 1.7.0 (any update) or 1.7.0_u40 or lower, OR 1.6.0_u60 or lower, OR 1.5.0_u51 or lower.
-
Check JavaFX versionIf JavaFX is installed, locate the javafx runtime jars (typically in the Java lib directory) and query its version metadata, or check the package version via `rpm -qa | grep javafx` on RHEL.Affected if JavaFX version is 2.2.40 or earlier.
-
Verify Java 2D graphics subsystem is in useThis vulnerability exists in the core 2D graphics code. Check if any Java applications that process graphical content (AWT, Swing, Java2D) are running or if the JDK/JRE is used for desktop applications.Affected if Java is used for any graphical applications or to run untrusted code - the 2D subsystem is part of standard Java SE.
If any installed JDK, JRE, or JavaFX version falls within 1.7.0_u40 or earlier, 1.6.0_u60 or earlier, 1.5.0_u51 or earlier, or JavaFX 2.2.40 or earlier, the environment is affected.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade Java to versions beyond 7u40 (7u45 or later for Java SE 7, or appropriate newer versions for other affected product lines). For systems where upgrade is not feasible, disable Java browser plugins and apply network-level restrictions to limit exposure.
Java SE 7u45 or later (for 1.7.x), Java SE 6u65 or later (for 1.6.x), Java SE 5.0u60 or later (for 1.5.x), or JavaFX 2.2.45 or later
- 1. Identify the installed Java/JRE/JDK version by running: java -version or checking /usr/lib/jvm/
- 2. For RHEL/CentOS systems, check available packages with: yum list installed | grep java
- 3. Remove vulnerable Java installations: yum remove java-1.5.0-* java-1.6.0-* java-1.7.0-*
- 4. Install the fixed Java version. For RHEL/CentOS 5/6, update to Java 7u45 or later using: yum install java-1.7.0-openjdk or yum install java-1.7.0-openjdk-devel
- 5. Verify the new version: java -version (should show 1.7.0_45 or later)
- 6. Set JAVA_HOME environment variable to point to the new installation if needed
- 7. Restart any services or applications using the old Java version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-5843 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2013-5843 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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