This page was not yet optimized for use on mobile devices.
CVE-2018-14626
Data ?
Vulnerability ID | CVE-2018-14626 |
---|---|
Published on | 29.11.2018 18:29 |
Severity | HIGH |
Vulnerable configurations ?
- cpe:2.3:a:powerdns:authoritative:4.1.0:*:*:*:*:*:*:*, cpe:2.3:a:powerdns:authoritative:4.1.0:-:*:*:*:*:*:*, cpe:2.3:a:powerdns:authoritative:4.1.0:alpha1:*:*:*:*:*:*, cpe:2.3:a:powerdns:authoritative:4.1.0:rc1:*:*:*:*:*:*, cpe:2.3:a:powerdns:authoritative:4.1.0:rc2:*:*:*:*:*:*, cpe:2.3:a:powerdns:authoritative:4.1.0:rc3:*:*:*:*:*:*, cpe:2.3:a:powerdns:authoritative:4.1.1:*:*:*:*:*:*:*, cpe:2.3:a:powerdns:authoritative:4.1.2:*:*:*:*:*:*:*, cpe:2.3:a:powerdns:authoritative:4.1.3:*:*:*:*:*:*:*, cpe:2.3:a:powerdns:authoritative:4.1.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.