This page was not yet optimized for use on mobile devices.
CVE-2016-6172
Data ?
Vulnerability ID | CVE-2016-6172 |
---|---|
Published on | 26.09.2016 16:59 |
Severity | MEDIUM |
Vulnerable configurations ?
- cpe:2.3:a:powerdns:authoritative_server:2.9.22:*:*:*:*:*:*:*, cpe:2.3:a:powerdns:authoritative_server:3.0:*:*:*:*:*:*:*, cpe:2.3:a:powerdns:authoritative_server:4.0.0:*:*:*:*:*:*:*, cpe:2.3:a:powerdns:authoritative_server:4.0.0:-:*:*:*:*:*:*, cpe:2.3:a:powerdns:authoritative_server:4.0.0:alpha1:*:*:*:*:*:*, cpe:2.3:a:powerdns:authoritative_server:4.0.0:alpha2:*:*:*:*:*:*, cpe:2.3:a:powerdns:authoritative_server:4.0.0:alpha3:*:*:*:*:*:*, cpe:2.3:a:powerdns:authoritative_server:4.0.0:beta1:*:*:*:*:*:*, cpe:2.3:a:powerdns:authoritative_server:4.0.0:rc2:*:*:*:*:*:*
- cpe:2.3:o:opensuse:leap:42.1:*:*:*:*:*:*:*
-
…
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.