This page was not yet optimized for use on mobile devices.
CVE-2016-4606
Data ?
Vulnerability ID | CVE-2016-4606 |
---|---|
Published on | 21.02.2020 02:15 |
Severity | CRITICAL |
Vulnerable configurations ?
-
cpe:2.3:a:haxx:curl:-:*:*:*:*:*:*:*,
cpe:2.3:a:haxx:curl:4.9:*:*:*:*:*:*:*,
cpe:2.3:a:haxx:curl:6.0:*:*:*:*:*:*:*,
cpe:2.3:a:haxx:curl:6.1:*:*:*:*:*:*:*,
cpe:2.3:a:haxx:curl:6.1:beta:*:*:*:*:*:*,
cpe:2.3:a:haxx:curl:6.2:*:*:*:*:*:*:*,
cpe:2.3:a:haxx:curl:6.3:*:*:*:*:*:*:*,
cpe:2.3:a:haxx:curl:6.3.1:*:*:*:*:*:*:*,
cpe:2.3:a:haxx:curl:6.4:*:*:*:*:*:*:*,
cpe:2.3:a:haxx:curl:6.5:*:*:*:*:*:*:*,
…
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.