This page was not yet optimized for use on mobile devices.
CVE-2019-20024
Data ?
Vulnerability ID | CVE-2019-20024 |
---|---|
Published on | 27.12.2019 02:15 |
Severity | MEDIUM |
Vulnerable configurations ?
-
cpe:2.3:a:libsixel_project:libsixel:0.11.0:*:*:*:*:*:*:*,
cpe:2.3:a:libsixel_project:libsixel:0.12.0:*:*:*:*:*:*:*,
cpe:2.3:a:libsixel_project:libsixel:0.14.0:*:*:*:*:*:*:*,
cpe:2.3:a:libsixel_project:libsixel:0.15.0:*:*:*:*:*:*:*,
cpe:2.3:a:libsixel_project:libsixel:0.16.0:*:*:*:*:*:*:*,
cpe:2.3:a:libsixel_project:libsixel:0.16.1:*:*:*:*:*:*:*,
cpe:2.3:a:libsixel_project:libsixel:0.17.0:*:*:*:*:*:*:*,
cpe:2.3:a:libsixel_project:libsixel:0.17.1:*:*:*:*:*:*:*,
cpe:2.3:a:libsixel_project:libsixel:0.17.2:*:*:*:*:*:*:*,
cpe:2.3:a:libsixel_project:libsixel:0.18.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.