This page was not yet optimized for use on mobile devices.
CVE-2017-3138
Data ?
Vulnerability ID | CVE-2017-3138 |
---|---|
Published on | 16.01.2019 20:29 |
Severity | MEDIUM |
Vulnerable configurations ?
-
cpe:2.3:a:isc:bind:9.9.9:*:*:*:*:*:*:*,
cpe:2.3:a:isc:bind:9.9.9:-:*:*:*:*:*:*,
cpe:2.3:a:isc:bind:9.9.9:b1:*:*:*:*:*:*,
cpe:2.3:a:isc:bind:9.9.9:b2:*:*:*:*:*:*,
cpe:2.3:a:isc:bind:9.9.9:beta1:*:*:*:*:*:*,
cpe:2.3:a:isc:bind:9.9.9:beta2:*:*:*:*:*:*,
cpe:2.3:a:isc:bind:9.9.9:p1:*:*:*:*:*:*,
cpe:2.3:a:isc:bind:9.9.9:p2:*:*:*:*:*:*,
cpe:2.3:a:isc:bind:9.9.9:p3:*:*:*:*:*:*,
cpe:2.3:a:isc:bind:9.9.9:p4:*:*:*:*:*:*,
…
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.