First published: Thu Feb 18 2021(Updated: )
An issue was discovered in Sangoma Asterisk 16.x before 16.16.1, 17.x before 17.9.2, and 18.x before 18.2.1 and Certified Asterisk before 16.8-cert6. When re-negotiating for T.38, if the initial remote response was delayed just enough, Asterisk would send both audio and T.38 in the SDP. If this happened, and the remote responded with a declined T.38 stream, then Asterisk would crash.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Digium Asterisk | >=16.0.0<16.16.1 | |
Digium Asterisk | >=17.0.0<17.9.2 | |
Digium Asterisk | >=18.0<18.2.1 | |
Digium Certified Asterisk | =16.8 | |
Digium Certified Asterisk | =16.8-cert1-rc1 | |
Digium Certified Asterisk | =16.8-cert1-rc2 | |
Digium Certified Asterisk | =16.8-cert1-rc3 | |
Digium Certified Asterisk | =16.8-cert1-rc4 | |
Digium Certified Asterisk | =16.8-cert2 | |
Digium Certified Asterisk | =16.8-cert3 | |
Digium Certified Asterisk | =16.8-cert4 | |
Digium Certified Asterisk | =16.8-cert4-rc1 | |
Digium Certified Asterisk | =16.8-cert4-rc2 | |
Digium Certified Asterisk | =16.8-cert4-rc3 | |
Digium Certified Asterisk | =16.8-cert4-rc4 | |
Digium Certified Asterisk | =16.8-cert5 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2021-26717 is high with a severity value of 7.5.
CVE-2021-26717 affects Sangoma Asterisk versions 16.x before 16.16.1, 17.x before 17.9.2, and 18.x before 18.2.1, as well as Certified Asterisk versions before 16.8-cert6.
The impact of CVE-2021-26717 is that when re-negotiating for T.38, if the initial remote response is delayed just enough, Asterisk may send both audio and T.38 in the SDP.
To check if your Sangoma Asterisk installation is affected, verify the version number and compare it to the affected versions mentioned in the advisory.
To mitigate the vulnerability, upgrade your Sangoma Asterisk installation to version 16.16.1, 17.9.2, 18.2.1, or a later version.