This page was not yet optimized for use on mobile devices.
CVE-2019-20454
Data ?
Vulnerability ID | CVE-2019-20454 |
---|---|
Published on | 14.02.2020 14:15 |
Severity | HIGH |
Vulnerable configurations ?
- cpe:2.3:a:pcre:pcre2:10.31:*:*:*:*:*:*:*, cpe:2.3:a:pcre:pcre2:10.32:*:*:*:*:*:*:*, cpe:2.3:a:pcre:pcre2:10.33:*:*:*:*:*:*:*
- cpe:2.3:a:splunk:universal_forwarder:8.2.0:*:*:*:*:*:*:*, cpe:2.3:a:splunk:universal_forwarder:8.2.6:*:*:*:*:*:*:*, cpe:2.3:a:splunk:universal_forwarder:8.2.7:*:*:*:*:*:*:*, cpe:2.3:a:splunk:universal_forwarder:8.2.8:*:*:*:*:*:*:*, cpe:2.3:a:splunk:universal_forwarder:8.2.9:*:*:*:*:*:*:*, cpe:2.3:a:splunk:universal_forwarder:8.2.10:*:*:*:*:*:*:*, cpe:2.3:a:splunk:universal_forwarder:8.2.11:*:*:*:*:*:*:*
-
…
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.