This page was not yet optimized for use on mobile devices.
CVE-2012-0501
Data ?
Vulnerability ID | CVE-2012-0501 |
---|---|
Published on | 15.02.2012 22:55 |
Severity | MEDIUM |
Vulnerable configurations ?
- cpe:2.3:a:sun:jre:1.5.0:update33:*:*:*:*:*:*
-
cpe:2.3:a:sun:jre:1.5.0:*:*:*:*:*:*:*,
cpe:2.3:a:sun:jre:1.5.0:-:*:*:*:*:*:*,
cpe:2.3:a:sun:jre:1.5.0:update1:*:*:*:*:*:*,
cpe:2.3:a:sun:jre:1.5.0:update10:*:*:*:*:*:*,
cpe:2.3:a:sun:jre:1.5.0:update11:*:*:*:*:*:*,
cpe:2.3:a:sun:jre:1.5.0:update12:*:*:*:*:*:*,
cpe:2.3:a:sun:jre:1.5.0:update13:*:*:*:*:*:*,
cpe:2.3:a:sun:jre:1.5.0:update14:*:*:*:*:*:*,
cpe:2.3:a:sun:jre:1.5.0:update15:*:*:*:*:*:*,
…
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.