How severe is CVE-2003-1134?

CVE-2003-1134 has a CVSS 2.0 base score of 2.1, rated low severity.

Is CVE-2003-1134 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (52nd percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2003-1134?

CVE-2003-1134 primarily affects Sun Java. In total, 3 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2003-1134?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2003-1134 published?

CVE-2003-1134 was published on 2003-12-31 and last updated on 2026-06-16.

CVE-2003-1134

CVE-2003-1134 is a low-severity vulnerability in Sun Java with a CVSS 2.0 base score of 2.1. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: Low (CVSS 2.0 base score 2.1)
EPSS exploit prediction: 1% (52nd percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Sun Java
Published: 2003-12-31
Last modified: 2026-06-16

Description

Sun Java 1.3.1, 1.4.1, and 1.4.2 allows local users to cause a denial of service (JVM crash), possibly by calling the ClassDepth function with a null parameter, which causes a crash instead of generating a null pointer exception.

Frequently asked questions

What is CVE-2003-1134?: Sun Java 1.3.1, 1.4.1, and 1.4.2 allows local users to cause a denial of service (JVM crash), possibly by calling the ClassDepth function with a null parameter, which causes a crash instead of generating a null pointer exception.
How severe is CVE-2003-1134?: CVE-2003-1134 has a CVSS 2.0 base score of 2.1, rated low severity.
Is CVE-2003-1134 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (52nd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2003-1134?: CVE-2003-1134 primarily affects Sun Java. In total, 3 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2003-1134?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2003-1134 published?: CVE-2003-1134 was published on 2003-12-31 and last updated on 2026-06-16.

References

Affected products (3)

cpe:2.3:a:sun:java:1.3.1:*:*:*:*:*:*:*
cpe:2.3:a:sun:java:1.4.1:*:*:*:*:*:*:*
cpe:2.3:a:sun:java:1.4.2:*:*:*:*:*:*:*

More vulnerabilities in Sun Java

CVE-2010-0887 — Critical (CVSS 10.0): Unspecified vulnerability in the New Java Plug-in component in Oracle Java SE and Java for Business JDK and JRE 6…
CVE-2005-2530 — Critical (CVSS 10.0): Unspecified vulnerability in Java 1.3.1 before 1.3.1_16 on Apple Mac OS X allows an untrusted applet to gain…
CVE-2005-2529 — Critical (CVSS 10.0): Unspecified vulnerability in Java 1.4.2 before 1.4.2 Release 2 on Apple Mac OS X allows local users to gain privileges…
CVE-2009-1105 — High (CVSS 7.5): The Java Plug-in in Java SE Development Kit (JDK) and Java Runtime Environment (JRE) 6 Update 12, 11, and 10 allows…
CVE-2008-3440 — High (CVSS 7.5): Sun Java 1.6.0_03 and earlier versions, and possibly later versions, does not properly verify the authenticity of…
CVE-1999-0440 — High (CVSS 7.5): The byte code verifier component of the Java Virtual Machine (JVM) allows remote execution through malicious web pages.

All CVEs affecting Sun Java →