dbcve.org
JdkApplication · Sun

CVE-2008-5343

HIGH · 9.0 CVSS v2.0 Published 2008-12-05
Fix available
A fix is available. Upgrade to after 6 or later.
See remediation →
99/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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
Java Web Start (JWS) and Java Plug-in with Sun JDK and JRE 6 Update 10 and earlier; JDK and JRE 5.0 Update 16 and earlier; and SDK and JRE 1.4.2_18 and earlier allows remote attackers to make unauthorized network connections and hijack HTTP sessions via a crafted file that validates as both a GIF and a Java JAR file, aka "GIFAR" and CR 6707535.

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

A detailed technical summary for this CVE is being prepared.

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
JdkApplication
Affected:<= 5.0<= 6= 5.0= 6
JreApplication
Affected:<= 1.4.2_18<= 5.0<= 6= 1.4.2_1= 1.4.2_2= 1.4.2_3= 1.4.2_4= 1.4.2_5= 1.4.2_6= 1.4.2_7= 1.4.2_8= 1.4.2_9
SdkApplication
Affected:<= 1.4.2_18= 1.4.2_1= 1.4.2_2= 1.4.2_3= 1.4.2_4= 1.4.2_5= 1.4.2_6= 1.4.2_7= 1.4.2_8= 1.4.2_9= 1.4.2_10= 1.4.2_11

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

AV:N/AC:L/Au:N/C:C/I:P/A:P

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
Upgrade available Upgrade to a release after 6
Vendor patch sunsolve.sun.com →
Recommended fix High confidence

JDK/JRE 6u10+, 5.0u16+, or 1.4.2_19+; or migrate to Java 8 LTS or later

  1. 1. Identify the currently installed Java version by running 'java -version'
  2. 2. For JDK/JRE 6: upgrade to version 6u10 or later
  3. 3. For JDK/JRE 5.0: upgrade to version 5u16 or later
  4. 4. For SDK/JRE 1.4.2: upgrade to version 1.4.2_19 or later
  5. 5. Alternatively, upgrade to the latest available JDK/JRE 8 LTS or later for the most comprehensive security fixes
  6. 6. Verify the upgrade was successful by running 'java -version' and confirming the updated version number
Caveat Legacy applications may have compatibility issues with newer Java versions; thoroughly test application functionality after upgrade

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

We can identify the exact fixed release, upgrade, and verify it in staging — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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