This page was not yet optimized for use on mobile devices.
CVE-2017-6519
Data ?
Vulnerability ID | CVE-2017-6519 |
---|---|
Published on | 01.05.2017 01:59 |
Severity | CRITICAL |
Vulnerable configurations ?
-
cpe:2.3:a:avahi:avahi:0.1:*:*:*:*:*:*:*,
cpe:2.3:a:avahi:avahi:0.2:*:*:*:*:*:*:*,
cpe:2.3:a:avahi:avahi:0.3:*:*:*:*:*:*:*,
cpe:2.3:a:avahi:avahi:0.4:*:*:*:*:*:*:*,
cpe:2.3:a:avahi:avahi:0.5:*:*:*:*:*:*:*,
cpe:2.3:a:avahi:avahi:0.5.1:*:*:*:*:*:*:*,
cpe:2.3:a:avahi:avahi:0.5.2:*:*:*:*:*:*:*,
cpe:2.3:a:avahi:avahi:0.6:*:*:*:*:*:*:*,
cpe:2.3:a:avahi:avahi:0.6.1:*:*:*:*:*:*:*,
cpe:2.3:a:avahi:avahi:0.6.2:*:*:*:*:*:*:*,
…
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.