This page was not yet optimized for use on mobile devices.
CVE-2017-13039
Data ?
Vulnerability ID | CVE-2017-13039 |
---|---|
Published on | 14.09.2017 06:29 |
Severity | CRITICAL |
Vulnerable configurations ?
-
cpe:2.3:a:tcpdump:tcpdump:3.5.1:*:*:*:*:*:*:*,
cpe:2.3:a:tcpdump:tcpdump:3.5.2:*:*:*:*:*:*:*,
cpe:2.3:a:tcpdump:tcpdump:3.6.1:*:*:*:*:*:*:*,
cpe:2.3:a:tcpdump:tcpdump:3.6.2:*:*:*:*:*:*:*,
cpe:2.3:a:tcpdump:tcpdump:3.6.3:*:*:*:*:*:*:*,
cpe:2.3:a:tcpdump:tcpdump:3.7.1:*:*:*:*:*:*:*,
cpe:2.3:a:tcpdump:tcpdump:3.7.2:*:*:*:*:*:*:*,
cpe:2.3:a:tcpdump:tcpdump:3.8.1:*:*:*:*:*:*:*,
cpe:2.3:a:tcpdump:tcpdump:3.8.2:*:*:*:*:*:*:*,
cpe:2.3:a:tcpdump:tcpdump:3.8.3:*:*:*:*:*:*:*,
…
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.