A res_pjsip_session crash was discovered in Asterisk Open Source 13.x before 13.37.1, 16.x before 16.14.1, 17.x before 17.8.1, and 18.x before 18.0.1. and Certified Asterisk before 16.8-cert5. Upon receiving a new SIP Invite, Asterisk did not return the created dialog locked or referenced. This caused a gap between the creation of the dialog object, and its next use by the thread that created it. Depending on some off-nominal circumstances and timing, it was possible for another thread to free said dialog in this gap. Asterisk could then crash when the dialog object, or any of its dependent objects, were dereferenced or accessed next by the initial-creation thread. Note, however, that this crash can only occur when using a connection-oriented protocol (e.g., TCP or TLS, but not UDP) for SIP transport. Also, the remote client must be authenticated, or Asterisk must be configured for anonymous calling.
This vulnerability carries a MEDIUM severity rating with a CVSS v3.1 score of 5.3, indicating it can be exploited remotely over the network but requires specific conditions to be met without requiring user interaction requiring only low-level privileges . The vulnerability impacts and availability (service disruption) for affected systems. Impacting 2 products from digium, from sangoma organizations running these solutions should prioritize assessment and patching.
Reported in 2020, this vulnerability emerged during an era marked by increased sophistication in supply chain attacks, cloud infrastructure vulnerabilities, and software-as-a-service (SaaS) security challenges. Security practices during this period emphasized zero-trust architectures, container security, and API protection.
2020-11-06T19:15:14.080
2024-11-21T05:22:33.987
Modified
CVSSv3.1: 5.3 (MEDIUM)
AV:N/AC:H/Au:S/C:N/I:N/A:P
3.9
2.9
| Type | Vendor | Product | Version/Range | Vulnerable? |
|---|---|---|---|---|
| Application | digium | certified_asterisk | 16.8 | Yes |
| Application | digium | certified_asterisk | 16.8 | Yes |
| Application | digium | certified_asterisk | 16.8 | Yes |
| Application | digium | certified_asterisk | 16.8 | Yes |
| Application | digium | certified_asterisk | 16.8 | Yes |
| Application | digium | certified_asterisk | 16.8 | Yes |
| Application | digium | certified_asterisk | 16.8 | Yes |
| Application | digium | certified_asterisk | 16.8 | Yes |
| Application | digium | certified_asterisk | 16.8 | Yes |
| Application | digium | certified_asterisk | 16.8 | Yes |
| Application | digium | certified_asterisk | 16.8 | Yes |
| Application | digium | certified_asterisk | 16.8 | Yes |
| Application | sangoma | asterisk | < 13.37.1 | Yes |
| Application | sangoma | asterisk | < 16.14.1 | Yes |
| Application | sangoma | asterisk | < 17.8.1 | Yes |
| Application | sangoma | asterisk | < 18.0.1 | Yes |
SecUtils normalizes and enriches National Vulnerability Database (NVD) records by standardizing vendor and product identifiers, aggregating vulnerability metadata from both NVD and MITRE sources, and providing structured context for security teams. For digium's affected products, we extract Common Platform Enumeration (CPE) data, Common Weakness Enumeration (CWE) classifications, CVSS severity metrics, and reference data to enable rapid vulnerability prioritization and asset correlation. This record contains no exploit code, proof-of-concept instructions, or attack methodologies—only defensive intelligence necessary for patch management, risk assessment, and security operations.