This page was not yet optimized for use on mobile devices.
CVE-2016-4303
Data ?
Vulnerability ID | CVE-2016-4303 |
---|---|
Published on | 26.09.2016 14:59 |
Severity | CRITICAL |
Vulnerable configurations ?
-
cpe:2.3:a:iperf3_project:iperf3:3.0:alpha1:*:*:*:*:*:*,
cpe:2.3:a:iperf3_project:iperf3:3.0:beta1:*:*:*:*:*:*,
cpe:2.3:a:iperf3_project:iperf3:3.0:beta2:*:*:*:*:*:*,
cpe:2.3:a:iperf3_project:iperf3:3.0:beta3:*:*:*:*:*:*,
cpe:2.3:a:iperf3_project:iperf3:3.0:beta4:*:*:*:*:*:*,
cpe:2.3:a:iperf3_project:iperf3:3.0:beta5:*:*:*:*:*:*,
cpe:2.3:a:iperf3_project:iperf3:3.0.1:*:*:*:*:*:*:*,
cpe:2.3:a:iperf3_project:iperf3:3.0.2:*:*:*:*:*:*:*,
cpe:2.3:a:iperf3_project:iperf3:3.0.3:*:*:*:*:*:*:*,
cpe:2.3:a:iperf3_project:iperf3:3.0.4:*:*:*:*:*:*:*,
…
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.