This page was not yet optimized for use on mobile devices.
CVE-2018-14599
Data ?
Vulnerability ID | CVE-2018-14599 |
---|---|
Published on | 24.08.2018 19:29 |
Severity | CRITICAL |
Vulnerable configurations ?
-
cpe:2.3:a:x.org:libx11:-:*:*:*:*:*:*:*,
cpe:2.3:a:x.org:libx11:1.0.1:*:*:*:*:*:*:*,
cpe:2.3:a:x.org:libx11:1.0.2:*:*:*:*:*:*:*,
cpe:2.3:a:x.org:libx11:1.0.3:*:*:*:*:*:*:*,
cpe:2.3:a:x.org:libx11:1.0.99.1:*:*:*:*:*:*:*,
cpe:2.3:a:x.org:libx11:1.0.99.2:*:*:*:*:*:*:*,
cpe:2.3:a:x.org:libx11:1.1:*:*:*:*:*:*:*,
cpe:2.3:a:x.org:libx11:1.1:-:*:*:*:*:*:*,
cpe:2.3:a:x.org:libx11:1.1:rc1:*:*:*:*:*:*,
cpe:2.3:a:x.org:libx11:1.1:rc2:*:*:*:*:*:*,
…
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.