This page was not yet optimized for use on mobile devices.
CVE-2018-1000168
Data ?
Vulnerability ID | CVE-2018-1000168 |
---|---|
Published on | 08.05.2018 15:29 |
Severity | HIGH |
Vulnerable configurations ?
-
cpe:2.3:a:nghttp2:nghttp2:1.10.0:*:*:*:*:*:*:*,
cpe:2.3:a:nghttp2:nghttp2:1.11.0:*:*:*:*:*:*:*,
cpe:2.3:a:nghttp2:nghttp2:1.11.1:*:*:*:*:*:*:*,
cpe:2.3:a:nghttp2:nghttp2:1.12.0:*:*:*:*:*:*:*,
cpe:2.3:a:nghttp2:nghttp2:1.13.0:*:*:*:*:*:*:*,
cpe:2.3:a:nghttp2:nghttp2:1.14.0:*:*:*:*:*:*:*,
cpe:2.3:a:nghttp2:nghttp2:1.14.1:*:*:*:*:*:*:*,
cpe:2.3:a:nghttp2:nghttp2:1.15.0:*:*:*:*:*:*:*,
cpe:2.3:a:nghttp2:nghttp2:1.16.0:*:*:*:*:*:*:*,
cpe:2.3:a:nghttp2:nghttp2:1.16.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.