OpenjdkApplication · Oracle
CVE-2014-0462
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 OpenJDK 6 before 6b31 on Debian GNU/Linux and Ubuntu 12.04 LTS and 10.04 LTS has unknown impact and attack vectors, a different vulnerability than CVE-2014-2405.
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 confidenceOpenJDK 6 vulnerability (pre-6b31) on Debian/Ubuntu 10.04 and 12.04 LTS with CRITICAL severity (CVSS 10). The description is intentionally unspecific, but OpenJDK vulnerabilities at this severity level typically allow complete compromise via malicious Java applets or code execution through the Java runtime. This is distinct from CVE-2014-2405.
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
OpenjdkApplication
= 1.6.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.
-
Identify if OpenJDK 6 is installedRun 'java -version' or 'dpkg -l | grep openjdk' on Debian/Ubuntu systems to check for OpenJDK packagesAffected if No OpenJDK 6 package is found (not affected)
-
Confirm the exact OpenJDK 6 versionUse 'dpkg -l openjdk-6-jdk' or 'apt-cache policy openjdk-6-jdk' to retrieve the precise package version stringAffected if Version shows 1.6.0 and is present on the system
-
Verify the OS distribution and versionCheck /etc/lsb-release or run 'lsb_release -a' to confirm the system is Debian or Ubuntu 10.04 LTS or 12.04 LTSAffected if Running on Debian or Ubuntu 10.04/12.04 LTS with OpenJDK 6 installed
-
Compare installed version against the vulnerable rangeCompare your installed OpenJDK 6 version to the affected range (pre-6b31). If using package version numbering, check if it is earlier than the version containing the 6b31 security patchAffected if Installed version is before the patched 6b31 release on affected Debian/Ubuntu 10.04/12.04 LTS
A system is affected if OpenJDK 6 (1.6.0) is installed on Debian or Ubuntu 10.04/12.04 LTS and the installed version predates the 6b31 security update.
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 OpenJDK 6 to version 6b31 or later on affected Debian and Ubuntu 10.04/12.04 LTS systems, or apply vendor-supplied security patches.
OpenJDK 6b31 or later (recommended: migrate to OpenJDK 7 or 8 for longer term support)
- Update package repository lists: 'apt-get update'
- Upgrade OpenJDK 6 to version 6b31 or later: 'apt-get install openjdk-6-jdk'
- Verify the installed version matches or exceeds 6b31: 'java -version'
- If multiple Java versions are installed, set the correct one using 'update-alternatives --config java'
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Openjdk
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.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-2014-0462 — 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-2014-0462 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