This page was not yet optimized for use on mobile devices.
CVE-2017-9359
Data ?
Vulnerability ID | CVE-2017-9359 |
---|---|
Published on | 02.06.2017 05:29 |
Severity | HIGH |
Vulnerable configurations ?
-
cpe:2.3:a:digium:certified_asterisk:13.13.0:*:*:*:*:*:*:*,
cpe:2.3:a:digium:certified_asterisk:13.13.0:cert1:*:*:*:*:*:*,
cpe:2.3:a:digium:certified_asterisk:13.13.0:cert1_rc1:*:*:*:*:*:*,
cpe:2.3:a:digium:certified_asterisk:13.13.0:cert1_rc2:*:*:*:*:*:*,
cpe:2.3:a:digium:certified_asterisk:13.13.0:cert1_rc3:*:*:*:*:*:*,
cpe:2.3:a:digium:certified_asterisk:13.13.0:cert1_rc4:*:*:*:*:*:*,
cpe:2.3:a:digium:certified_asterisk:13.13.0:cert1-rc1:*:*:*:*:*:*,
cpe:2.3:a:digium:certified_asterisk:13.13.0:cert1-rc2:*:*:*:*:*:*,
cpe:2.3:a:digium:certified_asterisk:13.13.0:cert1-rc3:*:*:*:*:*:*,
cpe:2.3:a:digium:certified_asterisk:13.13.0:cert1-rc4:*:*:*:*:*:*,
…
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.