How severe is CVE-2009-2030?

CVE-2009-2030 has a CVSS 2.0 base score of 10.0, rated critical severity.

Is CVE-2009-2030 being actively exploited?

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

What products are affected by CVE-2009-2030?

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

How do I fix CVE-2009-2030?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

When was CVE-2009-2030 published?

CVE-2009-2030 was published on 2009-06-11 and last updated on 2026-06-16.

CVE-2009-2030

CVE-2009-2030 is a critical-severity vulnerability in Sun Jdk with a CVSS 2.0 base score of 10.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: Critical (CVSS 2.0 base score 10.0)
EPSS exploit prediction: 2% (76th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Sun Jdk
Published: 2009-06-11
Last modified: 2026-06-16

Description

Unspecified vulnerability in the XML Digital Signature verification functionality in JVA-RUN in JDK 6.0 in IBM OS/400 i5/OS V5R4M0 and V6R1M0 has unknown impact and attack vectors related to "XML SECURITY PATCH."

Frequently asked questions

What is CVE-2009-2030?: Unspecified vulnerability in the XML Digital Signature verification functionality in JVA-RUN in JDK 6.0 in IBM OS/400 i5/OS V5R4M0 and V6R1M0 has unknown impact and attack vectors related to "XML SECURITY PATCH."
How severe is CVE-2009-2030?: CVE-2009-2030 has a CVSS 2.0 base score of 10.0, rated critical severity.
Is CVE-2009-2030 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (76th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2009-2030?: CVE-2009-2030 primarily affects Sun Jdk. In total, 3 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2009-2030?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2009-2030 published?: CVE-2009-2030 was published on 2009-06-11 and last updated on 2026-06-16.

References

Affected products (3)

cpe:2.3:a:sun:jdk:6:*:*:*:*:*:*:*
cpe:2.3:o:ibm:os\/400:v5r4m0:*:*:*:*:*:*:*
cpe:2.3:o:ibm:os\/400:v6r1m0:*:*:*:*:*:*:*

More vulnerabilities in Sun Jdk

CVE-2013-5824 — Critical (CVSS 10.0): Unspecified vulnerability in Oracle Java SE 7u40 and earlier, Java SE 6u60 and earlier, and Java SE Embedded 7u40 and…
CVE-2013-5817 — Critical (CVSS 10.0): Unspecified vulnerability in Oracle Java SE 7u40 and earlier, Java SE 6u60 and earlier, Java SE 5.0u51 and earlier, and…
CVE-2013-5814 — Critical (CVSS 10.0): Unspecified vulnerability in Oracle Java SE 7u40 and earlier, Java SE 6u60 and earlier, Java SE 5.0u51 and earlier, and…
CVE-2013-5809 — Critical (CVSS 10.0): Unspecified vulnerability in Oracle Java SE 7u40 and earlier, Java SE 6u60 and earlier, Java SE 5.0u51 and earlier, and…
CVE-2013-5789 — Critical (CVSS 10.0): Unspecified vulnerability in Oracle Java SE 7u40 and earlier, Java SE 6u60 and earlier, and Java SE Embedded 7u40 and…
CVE-2013-5787 — Critical (CVSS 10.0): Unspecified vulnerability in Oracle Java SE 7u40 and earlier, Java SE 6u60 and earlier, and Java SE Embedded 7u40 and…

All CVEs affecting Sun Jdk →