This page was not yet optimized for use on mobile devices.
CVE-2019-3699
Data
| Vulnerability ID | CVE-2019-3699 |
|---|---|
| Published on | 24.01.2020 13:15 |
| Severity | HIGH |
Vulnerable configurations
-
cpe:2.3:a:privoxy:privoxy:2.9.20:*:*:*:*:*:*:*,
cpe:2.3:a:privoxy:privoxy:3.0.0:*:*:*:*:*:*:*,
cpe:2.3:a:privoxy:privoxy:3.0.2:*:*:*:*:*:*:*,
cpe:2.3:a:privoxy:privoxy:3.0.3:*:*:*:*:*:*:*,
cpe:2.3:a:privoxy:privoxy:3.0.5:*:*:*:*:*:*:*,
cpe:2.3:a:privoxy:privoxy:3.0.6:*:*:*:*:*:*:*,
cpe:2.3:a:privoxy:privoxy:3.0.7:*:*:*:*:*:*:*,
cpe:2.3:a:privoxy:privoxy:3.0.8:*:*:*:*:*:*:*,
cpe:2.3:a:privoxy:privoxy:3.0.9:*:*:*:*:*:*:*,
cpe:2.3:a:privoxy:privoxy:3.0.10:*:*:*:*:*:*:*,
…
running on/with
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.