dbcve.org
Enterprise Linux DesktopOperating system · Redhat

CVE-2013-5830

HIGH · 10.0 CVSS v2.0 Published 2013-10-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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 Oracle Java SE 7u40 and earlier, Java SE 6u60 and earlier, Java SE 5.0u51 and earlier, JRockit R28.2.8 and earlier, JRockit R27.7.6 and earlier, and Java SE Embedded 7u40 and earlier allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors related to Libraries.

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

Critical remote code execution vulnerability in Oracle Java SE/JRockit's Libraries component affecting versions 5u51, 6u60, 7u40 and earlier. The CVSS 10 rating indicates trivial remote exploitation with complete compromise of confidentiality, integrity, and availability, likely a zero-day at disclosure.

MitigationApply Oracle Critical Patch Update October 2013 or later to upgrade to patched Java versions. If immediate patching is not feasible, disable Java browser plugins and restrict network access to untrusted Java applets to reduce attack surface.

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 DesktopOperating system
Affected:= 5.0= 6.0
Enterprise Linux EusOperating system
Affected:= 6.4
Enterprise Linux ServerOperating system
Affected:= 5.0= 6.0
Enterprise Linux Server AusOperating system
Affected:= 6.4
Enterprise Linux WorkstationOperating system
Affected:= 5.0= 6.0
Ubuntu LinuxOperating system
Affected:= 10.04= 12.04= 12.10= 13.04= 13.10
JdkApplication
Affected:= 1.5.0= 1.6.0= 1.7.0
JreApplication
Affected:= 1.5.0= 1.6.0= 1.7.0

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Java runtime version
    Run 'java -version' from command line or check package manager (dpkg -l | grep -i java for Ubuntu, rpm -qa | grep -i java for RHEL)
    Affected if Version reported is 1.5.0, 1.6.0, 1.7.0 or earlier, or specifically 5u51, 6u60, 7u40 or earlier updates
  2. Confirm Java/JDK package vendor and version
    For RHEL check 'rpm -qa | grep -E "java|jdk|jre"' and review version strings. For Ubuntu check installed packages via dpkg or check /usr/lib/jvm/ directory contents
    Affected if Package version matches Oracle JDK/JRE 1.5.0, 1.6.0, 1.7.0 or earlier (including 5u51, 6u60, 7u40) or unpatched RHEL/Ubuntu Java packages from affected releases
  3. Determine if Java Web Start or applets are in use
    Check for javaws binary presence ('which javaws') and browser plugin directories ( ~/.mozilla/plugins/ or /usr/lib/mozilla/plugins/) for Java plugin files (libnpjp2.so or npjava*.dll)
    Affected if Java Web Start (javaws) or browser Java plugin is installed and enabled - this is the primary attack vector for remote code execution via the Libraries component flaw

Your environment is affected if you run any unpatched Oracle Java JDK/JRE version 1.5.0, 1.6.0, or 1.7.0 at update levels 51, 60, 40 or earlier respectively, particularly if Java browser plugins or Web Start are enabled.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Oracle Critical Patch Update October 2013 or later to upgrade to patched Java versions. If immediate patching is not feasible, disable Java browser plugins and restrict network access to untrusted Java applets to reduce attack surface.

Recommended fix Moderate confidence

Java SE 7u45 or later (Java 8 recommended for better security support)

  1. 1. Identify the current Java version installed by running 'java -version' or checking the system package manager
  2. 2. For Red Hat Enterprise Linux systems, run 'yum update java-1.7.0-oracle' or 'yum update java-1.6.0-oracle' to apply available security updates
  3. 3. For Ubuntu systems, run 'apt-get update' followed by 'apt-get install openjdk-7-jdk' or 'openjdk-6-jdk' to install the latest available version
  4. 4. Verify the new Java version by running 'java -version' after the update
  5. 5. Ensure any applications using Java are restarted to use the updated runtime
Caveat Applications may require testing for compatibility with newer Java versions; Java 5 and 6 are end-of-life and no longer receive security updates

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Enterprise Linux Desktop Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing16.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,360
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,576.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-5830 — 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-5830 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