This page was not yet optimized for use on mobile devices.
CVE-2009-3875
Data ?
Vulnerability ID | CVE-2009-3875 |
---|---|
Published on | 05.11.2009 16:30 |
Severity | MEDIUM |
Vulnerable configurations ?
-
cpe:2.3:a:sun:jdk:1.5.0:update1:*:*:*:*:*:*,
cpe:2.3:a:sun:jdk:1.5.0:update10:*:*:*:*:*:*,
cpe:2.3:a:sun:jdk:1.5.0:update11:*:*:*:*:*:*,
cpe:2.3:a:sun:jdk:1.5.0:update11_b03:*:*:*:*:*:*,
cpe:2.3:a:sun:jdk:1.5.0:update12:*:*:*:*:*:*,
cpe:2.3:a:sun:jdk:1.5.0:update13:*:*:*:*:*:*,
cpe:2.3:a:sun:jdk:1.5.0:update14:*:*:*:*:*:*,
cpe:2.3:a:sun:jdk:1.5.0:update15:*:*:*:*:*:*,
cpe:2.3:a:sun:jdk:1.5.0:update16:*:*:*:*:*:*,
cpe:2.3:a:sun:jdk:1.5.0:update17:*:*:*:*:*:*,
…
running on/with
Vulnerable certificates ?
This CVE has no assigned vulnerable CC or FIPS certificates.
Looking for more?
Explore the landscape of Common Criteria and FIPS 140 certificates.