This page was not yet optimized for use on mobile devices.
CVE-2017-9358
Data ?
Vulnerability ID | CVE-2017-9358 |
---|---|
Published on | 02.06.2017 05:29 |
Severity | HIGH |
Vulnerable configurations ?
- cpe:2.3:a:sangoma:asterisk:13.0.0:*:*:*:*:*:*:*
- cpe:2.3:a:sangoma:asterisk:13.1.0:-:*:*:*:*:*:*, cpe:2.3:a:sangoma:asterisk:13.1.0:rc1:*:*:*:*:*:*, cpe:2.3:a:sangoma:asterisk:13.1.0:rc2:*:*:*:*:*:*
- cpe:2.3:a:sangoma:asterisk:13.1.0:rc1:*:*:*:*:*:*
- cpe:2.3:a:sangoma:asterisk:13.1.0:rc2:*:*:*:*:*:*
- cpe:2.3:a:sangoma:asterisk:13.2.0:-:*:*:*:*:*:*, cpe:2.3:a:sangoma:asterisk:13.2.0:rc1:*:*:*:*:*:*
- cpe:2.3:a:sangoma:asterisk:13.2.0:rc1:*:*:*:*:*:*
- cpe:2.3:a:sangoma:asterisk:13.3.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.