This page was not yet optimized for use on mobile devices.
CVE-2016-3062
Data ?
Vulnerability ID | CVE-2016-3062 |
---|---|
Published on | 16.06.2016 18:59 |
Severity | HIGH |
Vulnerable configurations ?
-
cpe:2.3:a:libav:libav:0.3:*:*:*:*:*:*:*,
cpe:2.3:a:libav:libav:0.3.1:*:*:*:*:*:*:*,
cpe:2.3:a:libav:libav:0.3.2:*:*:*:*:*:*:*,
cpe:2.3:a:libav:libav:0.3.3:*:*:*:*:*:*:*,
cpe:2.3:a:libav:libav:0.3.4:*:*:*:*:*:*:*,
cpe:2.3:a:libav:libav:0.4.0:*:*:*:*:*:*:*,
cpe:2.3:a:libav:libav:0.4.1:*:*:*:*:*:*:*,
cpe:2.3:a:libav:libav:0.4.2:*:*:*:*:*:*:*,
cpe:2.3:a:libav:libav:0.4.3:*:*:*:*:*:*:*,
cpe:2.3:a:libav:libav:0.4.4:*:*:*:*:*:*:*,
…
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.