Enterprise Linux Desktop SupplementaryOperating system · Redhat
CVE-2013-5906
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 5.0u55, 6u65, and 7u45 allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors related to Install, a different vulnerability than CVE-2013-5905.
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 confidenceUnspecified vulnerability in Oracle Java SE 5.0u55, 6u65, and 7u45 in the Install component allows remote attackers to affect confidentiality, integrity, and availability via unknown attack vectors. This is distinct from CVE-2013-5905.
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
Enterprise Linux Desktop SupplementaryOperating system
= 5.0= 6.0
Enterprise Linux Hpc Node SupplementaryOperating system
= 6.0
Enterprise Linux Server SupplementaryOperating system
= 5.0= 6.0
Enterprise Linux Server Supplementary AusOperating system
= 6.5
Enterprise Linux Server Supplementary EusOperating system
= 6.5.z
Enterprise Linux Workstation SupplementaryOperating system
= 6.0= 1.7.0= 1.6.0= 1.5.0= 1.6.0= 1.5.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
- High
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:H/Au:N/C:P/I:P/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Java versionRun 'java -version' from command line or check RPM packages with 'rpm -qa | grep -i jdk' and 'rpm -qa | grep -i jre'Affected if Version reported is 1.5.0_u55, 1.6.0_u65, or 1.7.0_u45
-
Confirm Java installation sourceList installed Java-related packages using your package manager (yum, rpm, or dpkg depending on distribution)Affected if Packages from Oracle JDK or JRE are installed at the vulnerable versions listed above
-
Check for Java Web StartLocate javaws binary with 'which javaws' or 'find /usr -name javaws 2>/dev/null'Affected if Java Web Start is present on a system running a vulnerable Java version (it uses the Install component)
-
Review Java deployment configurationCheck for Java deployment toolkit files in user home directories: ls -la ~/.java/deployment/ or /etc/.java/deployment/Affected if Deployment configuration exists on a system with a vulnerable Java version installed
A system is affected if Oracle Java SE 5.0u55, 6u65, or 7u45 (or equivalent JRE/JDK 1.5.0, 1.6.0, 1.7.0 packages) are installed, particularly if Java Web Start or the Java Plug-in is enabled.
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 dataApply the appropriate Oracle Java critical patch update or upgrade to a supported, patched Java version to remediate this vulnerability.
Fix this in Enterprise Linux Desktop Supplementary
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-5906 — 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-5906 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