This page was not yet optimized for use on mobile devices.
CVE-2020-25219
Data ?
Vulnerability ID | CVE-2020-25219 |
---|---|
Published on | 09.09.2020 21:15 |
Severity | HIGH |
Vulnerable configurations ?
-
cpe:2.3:a:libproxy_project:libproxy:0.4.0:*:*:*:*:*:*:*,
cpe:2.3:a:libproxy_project:libproxy:0.4.1:*:*:*:*:*:*:*,
cpe:2.3:a:libproxy_project:libproxy:0.4.2:*:*:*:*:*:*:*,
cpe:2.3:a:libproxy_project:libproxy:0.4.3:*:*:*:*:*:*:*,
cpe:2.3:a:libproxy_project:libproxy:0.4.5:*:*:*:*:*:*:*,
cpe:2.3:a:libproxy_project:libproxy:0.4.6:*:*:*:*:*:*:*,
cpe:2.3:a:libproxy_project:libproxy:0.4.7:*:*:*:*:*:*:*,
cpe:2.3:a:libproxy_project:libproxy:0.4.8:*:*:*:*:*:*:*,
cpe:2.3:a:libproxy_project:libproxy:0.4.9:*:*:*:*:*:*:*,
cpe:2.3:a:libproxy_project:libproxy:0.4.10:*:*:*:*:*:*:*,
…
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.