Asterisk is an open-source private branch exchange (PBX). Prior to versions 18.24.3, 20.9.3, and 21.4.3 of Asterisk and versions 18.9-cert12 and 20.7-cert2 of certified-asterisk, if Asterisk attempts to send a SIP request to a URI whose host portion starts with `.1` or `[.1]`, and res_resolver_unbound is loaded, Asterisk will crash with a SEGV. To receive a patch, users should upgrade to one of the following versions: 18.24.3, 20.9.3, 21.4.3, certified-18.9-cert12, certified-20.7-cert2. Two workarounds are available. Disable res_resolver_unbound by setting `noload = res_resolver_unbound.so` in modules.conf, or set `rewrite_contact = yes` on all PJSIP endpoints. NOTE: This may not be appropriate for all Asterisk configurations.
This vulnerability carries a MEDIUM severity rating with a CVSS v3.1 score of 5.7, indicating it can be exploited remotely over the network with relatively low complexity though user interaction is required requiring only low-level privileges . The vulnerability impacts and availability (service disruption) for affected systems. Impacting 2 products from sangoma, from sangoma organizations running these solutions should prioritize assessment and patching.
Reported in 2024, 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.
2024-09-05T18:15:05.707
2025-11-03T22:18:06.950
Modified
CVSSv3.1: 5.7 (MEDIUM)
| Type | Vendor | Product | Version/Range | Vulnerable? |
|---|---|---|---|---|
| Application | sangoma | asterisk | < 18.24.3 | Yes |
| Application | sangoma | asterisk | < 20.9.3 | Yes |
| Application | sangoma | asterisk | ≤ 21.4.3 | Yes |
| Application | sangoma | certified_asterisk | < 18.9 | Yes |
| Application | sangoma | certified_asterisk | 18.9 | Yes |
| Application | sangoma | certified_asterisk | 18.9 | Yes |
| Application | sangoma | certified_asterisk | 18.9 | Yes |
| Application | sangoma | certified_asterisk | 18.9 | Yes |
| Application | sangoma | certified_asterisk | 18.9 | Yes |
| Application | sangoma | certified_asterisk | 18.9 | Yes |
| Application | sangoma | certified_asterisk | 18.9 | Yes |
| Application | sangoma | certified_asterisk | 18.9 | Yes |
| Application | sangoma | certified_asterisk | 18.9 | Yes |
| Application | sangoma | certified_asterisk | 18.9 | Yes |
| Application | sangoma | certified_asterisk | 18.9 | Yes |
| Application | sangoma | certified_asterisk | 18.9 | Yes |
| Application | sangoma | certified_asterisk | 18.9 | Yes |
| Application | sangoma | certified_asterisk | 18.9 | Yes |
| Application | sangoma | certified_asterisk | 18.9 | Yes |
| Application | sangoma | certified_asterisk | 20.7 | Yes |
| Application | sangoma | certified_asterisk | 20.7 | Yes |
| Application | sangoma | certified_asterisk | 20.7 | Yes |
| Application | sangoma | certified_asterisk | 20.7 | 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 sangoma'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.