This page was not yet optimized for use on mobile devices.
CVE-2018-20969
Data ?
Vulnerability ID | CVE-2018-20969 |
---|---|
Published on | 16.08.2019 04:15 |
Severity | HIGH |
Vulnerable configurations ?
-
cpe:2.3:a:gnu:patch:2.5:*:*:*:*:*:*:*,
cpe:2.3:a:gnu:patch:2.5.4:*:*:*:*:*:*:*,
cpe:2.3:a:gnu:patch:2.5.9:*:*:*:*:*:*:*,
cpe:2.3:a:gnu:patch:2.6:*:*:*:*:*:*:*,
cpe:2.3:a:gnu:patch:2.6.1:*:*:*:*:*:*:*,
cpe:2.3:a:gnu:patch:2.7:*:*:*:*:*:*:*,
cpe:2.3:a:gnu:patch:2.7.1:*:*:*:*:*:*:*,
cpe:2.3:a:gnu:patch:2.7.2:*:*:*:*:*:*:*,
cpe:2.3:a:gnu:patch:2.7.3:*:*:*:*:*:*:*,
cpe:2.3:a:gnu:patch:2.7.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.