This page was not yet optimized for use on mobile devices.
CVE-2019-10050
Data ?
Vulnerability ID | CVE-2019-10050 |
---|---|
Published on | 13.05.2019 17:29 |
Severity | HIGH |
Vulnerable configurations ?
-
cpe:2.3:a:oisf:suricata:4.0.0:-:*:*:*:*:*:*,
cpe:2.3:a:oisf:suricata:4.0.0:beta1:*:*:*:*:*:*,
cpe:2.3:a:oisf:suricata:4.0.0:rc1:*:*:*:*:*:*,
cpe:2.3:a:oisf:suricata:4.0.0:rc2:*:*:*:*:*:*,
cpe:2.3:a:oisf:suricata:4.0.1:*:*:*:*:*:*:*,
cpe:2.3:a:oisf:suricata:4.0.2:*:*:*:*:*:*:*,
cpe:2.3:a:oisf:suricata:4.0.3:*:*:*:*:*:*:*,
cpe:2.3:a:oisf:suricata:4.0.4:*:*:*:*:*:*:*,
cpe:2.3:a:oisf:suricata:4.0.5:*:*:*:*:*:*:*,
cpe:2.3:a:oisf:suricata:4.0.6:*:*:*:*:*:*:*,
…
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.