CVE-2008-5354: n/a vulnerability

CVE-2008-5354: Stack-based buffer overflow in Java Runtime Environment (JRE) for Sun JDK and JRE 6 Update 10 and earlier;...

Stack-based buffer overflow in 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 allows locally-launched and possibly remote untrusted Java applications to execute arbitrary code via a JAR file with a long Main-Class manifest entry.

UnknownCVSS not scoredNot KEV-listedUpdatedAug 7, 2024, 10:49 UTC (UTC+00:00)

Security readout for executives and security teams

This vulnerability affects very old Sun Java runtimes and development kits. A specially crafted JAR manifest with an overly long Main-Class value can trigger a stack buffer overflow, potentially allowing arbitrary code execution. Business risk is concentrated in legacy endpoints, servers, or bundled products still running these Java versions. Exposure is most likely where legacy Sun Java runtimes remain installed, where applications launch untrusted JAR files, or where old browser/plugin Java execution is still possible. Modern supported Java estates are less likely to be affected, but bundled Java inside legacy products needs checking. Prioritize remediation if legacy Java is still present on user workstations, internet-facing workflows, or business-critical systems. If inventory confirms these versions are absent, risk is mainly historical and should be closed through asset evidence. Mitigation focus: Inventory all Sun JDK, JRE, SDK, and bundled Java installations.; Remove affected Java versions where no business dependency remains.; Upgrade beyond the affected versions using applicable vendor advisories..

Prepared: Jun 28, 2026, 11:41 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup

cve · low confidence lookup

CVE-2008-5354 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup

Vulnerability profileCVE Program record

Severity: Unknown
CVSS: Not scored
Known Exploited: No
Published: Dec 5, 2008, 11:00 UTC (UTC+00:00)

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors

0Timeline events

0ADP providers

4Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

CVE List V5 sourceCVE List V5
oval:org.mitre.oval:def:6537CVE reference · vdb-entry, signature
RHSA-2009:0466CVE reference · vendor-advisory, x_refsource_REDHAT
jre-commandline-privilege-escalation(47060)CVE reference · vdb-entry, x_refsource_XF

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus

n/an/an/aListed

Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.