dbcve.org
JreApplication · Sun

CVE-2008-5345

HIGH · 7.5 CVSS v2.0 Published 2008-12-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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 Java Runtime Environment (JRE) with Sun JDK and JRE 6 Update 10 and earlier; JDK and JRE 5.0 Update 16 and earlier; SDK and JRE 1.4.2_18 and earlier; and SDK and JRE 1.3.1_23 and earlier allows code that is loaded from a local filesystem to read arbitrary files and make unauthorized connections to localhost via unknown vectors.

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

This is a Java sandbox bypass vulnerability in older JDK/JRE versions (1.3.1_23 and earlier, 1.4.2_18 and earlier, 5.0 Update 16 and earlier, 6 Update 10 and earlier) that allows code loaded from the local filesystem to escape Java sandbox restrictions and read arbitrary files on the system as well as make unauthorized network connections to localhost.

MitigationUpgrade to a Java version beyond the affected versions listed (e.g., JDK/JRE 6 Update 11 or later, 5.0 Update 17 or later) or apply the relevant Oracle/Sun security patch to eliminate this sandbox bypass.

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
JreApplication
Affected:= 1.3.1= 1.3.1_2= 1.3.1_03= 1.3.1_04= 1.3.1_05= 1.3.1_06= 1.3.1_07= 1.3.1_08= 1.3.1_09= 1.3.1_10= 1.3.1_11= 1.3.1_12
JdkApplication
Affected:= 1.5.0= 1.6.0
SdkApplication
Affected:= 1.3.1= 1.3.1_01= 1.3.1_01a= 1.3.1_02= 1.3.1_03= 1.3.1_04= 1.3.1_05= 1.3.1_06= 1.3.1_07= 1.3.1_08= 1.3.1_09= 1.3.1_10

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
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/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 checks

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

  1. Identify installed Java version
    Run 'java -version' from command line or inspect the java.home system property via 'java -XshowSettings:properties -version'
    Affected if Version output shows 1.3.1_23 or earlier, 1.4.2_18 or earlier, 5.0 Update 16 or earlier, or 6 Update 10 or earlier
  2. Check for multiple Java installations
    Review all Java installations on the system by listing directories under /usr/lib/jvm (Linux), C:\Program Files\Java (Windows), or /Library/Java/JavaVirtualMachines (macOS)
    Affected if Any installed JDK/JRE version matches the affected ranges listed in step 1
  3. Determine Java usage context
    Identify if the system runs untrusted Java code from local filesystem, such as Java Web Start applications, untrusted applets, or third-party Java-based services
    Affected if Untrusted Java code execution from local filesystem is performed on an affected Java version
  4. Audit network-bound Java services
    Review running Java processes that accept network connections, particularly services that load code from local directories
    Affected if Java services that accept network connections run on an affected version and load code from local filesystem

The environment is affected if any installed JDK/JRE version falls within 1.3.1_23 and earlier, 1.4.2_18 and earlier, 5.0 Update 16 and earlier, or 6 Update 10 and earlier AND the system executes untrusted Java code from the local filesystem.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a Java version beyond the affected versions listed (e.g., JDK/JRE 6 Update 11 or later, 5.0 Update 17 or later) or apply the relevant Oracle/Sun security patch to eliminate this sandbox bypass.

Fix this in Jre Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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