This page was not yet optimized for use on mobile devices.
CVE-2018-19800
Data ?
Vulnerability ID | CVE-2018-19800 |
---|---|
Published on | 07.06.2019 17:29 |
Severity | CRITICAL |
Vulnerable configurations ?
-
cpe:2.3:a:aubio:aubio:0.4.0:*:*:*:*:*:*:*,
cpe:2.3:a:aubio:aubio:0.4.0:-:*:*:*:*:*:*,
cpe:2.3:a:aubio:aubio:0.4.0:beta1:*:*:*:*:*:*,
cpe:2.3:a:aubio:aubio:0.4.1:*:*:*:*:*:*:*,
cpe:2.3:a:aubio:aubio:0.4.2:*:*:*:*:*:*:*,
cpe:2.3:a:aubio:aubio:0.4.3:*:*:*:*:*:*:*,
cpe:2.3:a:aubio:aubio:0.4.4:*:*:*:*:*:*:*,
cpe:2.3:a:aubio:aubio:0.4.5:*:*:*:*:*:*:*,
cpe:2.3:a:aubio:aubio:0.4.6:*:*:*:*:*:*:*,
cpe:2.3:a:aubio:aubio:0.4.7:*:*:*:*:*:*:*,
…
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.