This page was not yet optimized for use on mobile devices.
CVE-2018-5737
Data ?
Vulnerability ID | CVE-2018-5737 |
---|---|
Published on | 16.01.2019 20:29 |
Severity | HIGH |
Vulnerable configurations ?
-
cpe:2.3:a:isc:bind:9.12.0:*:*:*:*:*:*:*,
cpe:2.3:a:isc:bind:9.12.0:*:*:*:-:*:*:*,
cpe:2.3:a:isc:bind:9.12.0:-:*:*:*:*:*:*,
cpe:2.3:a:isc:bind:9.12.0:a1:*:*:*:*:*:*,
cpe:2.3:a:isc:bind:9.12.0:alpha0:*:*:*:*:*:*,
cpe:2.3:a:isc:bind:9.12.0:alpha1:*:*:*:*:*:*,
cpe:2.3:a:isc:bind:9.12.0:b1:*:*:*:*:*:*,
cpe:2.3:a:isc:bind:9.12.0:b2:*:*:*:*:*:*,
cpe:2.3:a:isc:bind:9.12.0:beta1:*:*:*:*:*:*,
cpe:2.3:a:isc:bind:9.12.0:beta2:*:*:*:*:*:*,
…
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.