CVE-2020-35652 : Vulnerability Insights and Analysis
Discover the impact of CVE-2020-35652 in Sangoma Asterisk versions before 13.38.0, 14.x through 16.x before 16.15.0, 17.x before 17.9.0, and 18.x before 18.1.0. Learn about the exploitation mechanism and mitigation steps.
An issue was discovered in res_pjsip_diversion.c in Sangoma Asterisk before 13.38.0, 14.x through 16.x before 16.15.0, 17.x before 17.9.0, and 18.x before 18.1.0. A crash can occur when a SIP message is received with a History-Info header that contains a tel-uri, or when a SIP 181 response is received that contains a tel-uri in the Diversion header.
Understanding CVE-2020-35652
This CVE identifies a vulnerability in Sangoma Asterisk versions that can lead to a crash under specific conditions.
What is CVE-2020-35652?
The CVE-2020-35652 vulnerability is related to the handling of SIP messages in Sangoma Asterisk, potentially resulting in a crash when certain types of SIP messages are received.
The Impact of CVE-2020-35652
The vulnerability can be exploited to cause a crash in the affected versions of Sangoma Asterisk, potentially leading to service disruption or denial of service.
Technical Details of CVE-2020-35652
This section provides more technical insights into the vulnerability.
Vulnerability Description
The issue occurs in res_pjsip_diversion.c in Sangoma Asterisk versions before 13.38.0, 14.x through 16.x before 16.15.0, 17.x before 17.9.0, and 18.x before 18.1.0, specifically when handling SIP messages with certain headers.
Affected Systems and Versions
- Sangoma Asterisk versions before 13.38.0, 14.x through 16.x before 16.15.0, 17.x before 17.9.0, and 18.x before 18.1.0
Exploitation Mechanism
The crash can be triggered by receiving a SIP message with a History-Info header containing a tel-uri or a SIP 181 response with a tel-uri in the Diversion header.
Mitigation and Prevention
To address CVE-2020-35652, follow these mitigation strategies:
Immediate Steps to Take
- Update Sangoma Asterisk to versions 13.38.0, 16.15.0, 17.9.0, or 18.1.0, which contain fixes for the vulnerability.
- Monitor network traffic for any suspicious SIP messages.
Long-Term Security Practices
- Regularly update and patch Sangoma Asterisk to ensure the latest security fixes are applied.
- Implement network segmentation and access controls to limit exposure to potential attacks.
Patching and Updates
- Apply the recommended updates provided by Sangoma to address the vulnerability and enhance system security.