dbcve.org
JdkApplication · Sun

CVE-2008-5353

HIGH · 10.0 CVSS v2.0 Published 2008-12-05
Fix available
A fix is available. Upgrade to after 6 or later.
See remediation →
100/100
Remediation priority · Urgent
High EPSS 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
The Java Runtime Environment (JRE) for 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 does not properly enforce context of ZoneInfo objects during deserialization, which allows remote attackers to run untrusted applets and applications in a privileged context, as demonstrated by "deserializing Calendar objects".

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

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

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

Java 6 Update 11+, Java 5.0 Update 17+, Java 1.4.2_19+, or migrate to a supported LTS release such as Java 11 or Java 17

  1. 1. Identify all systems running affected Java versions (JDK/JRE <= 5.0 Update 16, <= 6 Update 10, or <= 1.4.2_18)
  2. 2. Determine the specific Java version in use by running 'java -version' on each system
  3. 3. For Java 6 Update 10 and earlier: Upgrade to Java 6 Update 11 or later (or migrate to a supported Java 8/11/17 LTS release)
  4. 4. For Java 5.0 Update 16 and earlier: Upgrade to Java 5.0 Update 17 or later (or migrate to a supported Java 8/11/17 LTS release)
  5. 5. For Java 1.4.2_18 and earlier: Upgrade to Java 1.4.2_19 or later (or migrate to a supported Java 8/11/17 LTS release)
  6. 6. Download the updated Java version from Oracle's official Java SE archive page or adopt OpenJDK alternatives
  7. 7. Install the updated Java version on all affected systems
  8. 8. Verify the new version is correctly installed by running 'java -version'
Caveat Applications written for older Java versions may have compatibility issues with newer Java versions; thorough testing is recommended before production deployment

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-5353 — 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-5353 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