This page was not yet optimized for use on mobile devices.
CVE-2013-5016
Data ?
Vulnerability ID | CVE-2013-5016 |
---|---|
Published on | 08.05.2014 10:55 |
Severity | HIGH |
Vulnerable configurations ?
-
cpe:2.3:a:broadcom:symantec_critical_system_protection:4.5:*:*:*:*:*:*:*,
cpe:2.3:a:broadcom:symantec_critical_system_protection:5.0:*:*:*:*:*:*:*,
cpe:2.3:a:broadcom:symantec_critical_system_protection:5.1:*:*:*:*:*:*:*,
cpe:2.3:a:broadcom:symantec_critical_system_protection:5.1.1:*:*:*:*:*:*:*,
cpe:2.3:a:broadcom:symantec_critical_system_protection:5.1.2:*:*:*:*:*:*:*,
cpe:2.3:a:broadcom:symantec_critical_system_protection:5.1.3:*:*:*:*:*:*:*,
cpe:2.3:a:broadcom:symantec_critical_system_protection:5.2:*:*:*:*:*:*:*,
cpe:2.3:a:broadcom:symantec_critical_system_protection:5.2.1:*:*:*:*:*:*:*,
cpe:2.3:a:broadcom:symantec_critical_system_protection:5.2.2:*:*:*:*:*:*:*,
cpe:2.3:a:broadcom:symantec_critical_system_protection:5.2.3:*:*:*:*:*:*:*,
…
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.