CVE-2013-2439
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 the Java Runtime Environment (JRE) component in Oracle Java SE 7 Update 17 and earlier, 6 Update 43 and earlier, 5.0 Update 41 and earlier, and JavaFX 2.2.7 and earlier allows local users to affect confidentiality, integrity, and availability via unknown vectors related to Install.
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 confidenceA local privilege escalation vulnerability in the Java Runtime Environment's Install component allows local users to affect confidentiality, integrity, and availability through unspecified vectors. The vulnerability affects multiple Java SE versions up to the specified update levels.
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<= 1.7.0= 1.7.0<= 1.6.0= 1.6.0<= 1.5.0= 1.5.0<= 1.7.0= 1.7.0<= 1.6.0= 1.6.0<= 1.5.0= 1.5.0= 1.6.0= 1.5.0= 1.6.0= 1.5.0<= 2.2.7= 2.0= 2.0.2= 2.0.3= 2.1= 2.2= 2.2.3= 2.2.4= 2.2.5CVSS 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
- Local
- Complexity
- M
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/AC:M/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.
-
Identify installed Java runtime versionRun 'java -version' in command prompt or terminal to display the JRE/JDK version informationAffected if The displayed version is 1.5.x, 1.6.x, or 1.7.0 (any subversion)
-
Check Java installation directoriesInspect directories where Java is commonly installed (e.g., C:\Program Files\Java\ on Windows, /usr/lib/jvm/ on Linux) for multiple installed Java versionsAffected if Directories contain Java installations with version folders named 1.5, 1.6, or 1.7
-
Identify Java installer executablesLocate Java installer files (e.g., jre-*.exe, jdk-*.exe on Windows, or RPM/DEB packages) on the system using file system searchAffected if Found installers correspond to vulnerable Java versions 1.5, 1.6, or 1.7.0
-
Check JavaFX installationsIf JavaFX is installed, identify its version by checking installation directories or running 'java -version' for JavaFX-specific runtimeAffected 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, or <= 2.2.7
-
Enumerate all Java-related packagesUse system package manager (dpkg, rpm, yum) or Windows Programs and Features to list all installed Java-related packages with their exact version numbersAffected if Any installed package is Oracle JRE, JDK, Sun JRE, Sun JDK, or JavaFX with versions matching the affected ranges
A user is affected if any Java installation (JRE, JDK, or JavaFX) with version 1.5.x, 1.6.x, 1.7.0.x, or JavaFX 2.x up to 2.2.7 is present on the system, particularly if the Java installer component can be executed.
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.
From vendor dataUpdate affected Java installations to patched versions. Apply principle of least privilege to restrict who can run Java installers and ensure proper file system permissions on Java installation directories.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-2439 — 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-2439 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