This page was not yet optimized for use on mobile devices.
CVE-2018-19278
Data ?
Vulnerability ID | CVE-2018-19278 |
---|---|
Published on | 14.11.2018 20:29 |
Severity | HIGH |
Vulnerable configurations ?
- cpe:2.3:a:digium:asterisk:15.0.0:*:*:*:*:*:*:*, cpe:2.3:a:digium:asterisk:15.0.0:*:*:*:standard:*:*:*, cpe:2.3:a:digium:asterisk:15.0.0:-:*:*:*:*:*:*, cpe:2.3:a:digium:asterisk:15.0.0:beta1:*:*:*:*:*:*, cpe:2.3:a:digium:asterisk:15.0.0:rc1:*:*:*:*:*:*
- cpe:2.3:a:digium:asterisk:15.0.0:rc1:*:*:*:*:*:*
- cpe:2.3:a:digium:asterisk:15.1.0:*:*:*:*:*:*:*, cpe:2.3:a:digium:asterisk:15.1.0:*:*:*:standard:*:*:*, cpe:2.3:a:digium:asterisk:15.1.0:rc1:*:*:*:*:*:*, cpe:2.3:a:digium:asterisk:15.1.0:rc2:*:*:*:*:*:*
-
…
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.