This page was not yet optimized for use on mobile devices.
CVE-2017-16997
Data ?
Vulnerability ID | CVE-2017-16997 |
---|---|
Published on | 18.12.2017 01:29 |
Severity | HIGH |
Vulnerable configurations ?
- cpe:2.3:a:gnu:glibc:2.19:*:*:*:*:*:*:*
- cpe:2.3:a:gnu:glibc:2.20:*:*:*:*:*:*:*, cpe:2.3:a:gnu:glibc:2.20:*:*:*:*:*:x86:*
- cpe:2.3:a:gnu:glibc:2.21:*:*:*:*:*:*:*
- cpe:2.3:a:gnu:glibc:2.22:*:*:*:*:*:*:*, cpe:2.3:a:gnu:glibc:2.22:*:*:*:*:*:x86:*
- cpe:2.3:a:gnu:glibc:2.23:*:*:*:*:*:*:*, cpe:2.3:a:gnu:glibc:2.23:*:*:*:*:*:x86:*
- cpe:2.3:a:gnu:glibc:2.25:*:*:*:*:*:*:*
-
cpe:2.3:a:gnu:glibc:2.26:*:*:*:*:*:*:*,
…
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.