This page was not yet optimized for use on mobile devices.
CVE-2017-16671
Data ?
Vulnerability ID | CVE-2017-16671 |
---|---|
Published on | 09.11.2017 00:29 |
Severity | HIGH |
Vulnerable configurations ?
-
cpe:2.3:a:digium:asterisk:13.0.0:*:*:*:*:*:*:*,
cpe:2.3:a:digium:asterisk:13.0.0:*:*:*:lts:*:*:*,
cpe:2.3:a:digium:asterisk:13.0.0:beta1:*:*:*:*:*:*,
cpe:2.3:a:digium:asterisk:13.0.0:beta2:*:*:*:*:*:*,
cpe:2.3:a:digium:asterisk:13.0.0:beta3:*:*:*:*:*:*,
cpe:2.3:a:digium:asterisk:13.0.1:*:*:*:*:*:*:*,
cpe:2.3:a:digium:asterisk:13.0.2:*:*:*:*:*:*:*,
cpe:2.3:a:digium:asterisk:13.1.0:*:*:*:*:*:*:*,
cpe:2.3:a:digium:asterisk:13.1.0:*:*:*:lts:*:*:*,
cpe:2.3:a:digium:asterisk:13.1.0:rc1:*:*:*:*:*:*,
…
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.