This page was not yet optimized for use on mobile devices.
CVE-2018-20167
Data ?
Vulnerability ID | CVE-2018-20167 |
---|---|
Published on | 17.12.2018 05:29 |
Severity | HIGH |
Vulnerable configurations ?
-
cpe:2.3:a:enlightenment:terminology:0.1.0:*:*:*:*:*:*:*,
cpe:2.3:a:enlightenment:terminology:0.2.0:*:*:*:*:*:*:*,
cpe:2.3:a:enlightenment:terminology:0.3.0:*:*:*:*:*:*:*,
cpe:2.3:a:enlightenment:terminology:0.4.0:-:*:*:*:*:*:*,
cpe:2.3:a:enlightenment:terminology:0.4.0:alpha1:*:*:*:*:*:*,
cpe:2.3:a:enlightenment:terminology:0.4.0:alpha3:*:*:*:*:*:*,
cpe:2.3:a:enlightenment:terminology:0.4.0:alpha4:*:*:*:*:*:*,
cpe:2.3:a:enlightenment:terminology:0.5.0:*:*:*:*:*:*:*,
cpe:2.3:a:enlightenment:terminology:0.5.1:*:*:*:*:*:*:*,
cpe:2.3:a:enlightenment:terminology:0.6.0:*:*:*:*:*:*:*,
…
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.