CVE-2017-17850
For those messages, if the header was not present and the PJSIP channel driver was used, Asterisk would crash.
Does this matter?
EPSS puts the probability of exploitation in the next 30 days at 75.4%, higher than 100% of all known CVEs. Patch or mitigate before the next change window.
Description
An issue was discovered in Asterisk 13.18.4 and older, 14.7.4 and older, 15.1.4 and older, and 13.18-cert1 and older. A select set of SIP messages create a dialog in Asterisk. Those SIP messages must contain a contact header. For those messages, if the header was not present and the PJSIP channel driver was used, Asterisk would crash. The severity of this vulnerability is somewhat mitigated if authentication is enabled. If authentication is enabled, a user would have to first be authorized before reaching the crash point.
- CVSS 3.0
- 7.5 HIGHCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- EPSS
- 75.35% probability · 100th percentile
- Public exploits
- None in Exploit-DB
- CISA KEV
- Not listed
- Weakness
- CWE-20
- Affected
- digium/asterisk · digium/certified asterisk
- Source
- cve@mitre.org
EPSS moved from 65.8% on 21 September 2026 to 75.4% on 27 October 2026. The dashed line is the ten per cent mark our analysts treat as “patch before the next change window”.
References
- http://downloads.asterisk.org/pub/security/AST-2017-014.htmlVendor Advisory
- http://www.securitytracker.com/id/1040056Third Party Advisory, VDB Entry
- https://issues.asterisk.org/jira/browse/ASTERISK-27480Issue Tracking, Vendor Advisory
- https://security.gentoo.org/glsa/201811-11
- http://downloads.asterisk.org/pub/security/AST-2017-014.htmlVendor Advisory
- http://www.securitytracker.com/id/1040056Third Party Advisory, VDB Entry
- https://issues.asterisk.org/jira/browse/ASTERISK-27480Issue Tracking, Vendor Advisory
- https://security.gentoo.org/glsa/201811-11
Source: NVD record, EPSS from FIRST.org, KEV from CISA, exploits from Exploit-DB. Refreshed daily. Download this record as JSON.