Bug 2449443 (CVE-2026-32945)

Summary: CVE-2026-32945 PJSIP: pjproject: PJSUA: PJSUA2: PJSIP: Heap-based buffer overflow in DNS parser may lead to arbitrary code execution or denial of service.
Product: [Other] Security Response Reporter: OSIDB Bzimport <bzimport>
Component: vulnerabilityAssignee: Product Security DevOps Team <prodsec-dev>
Status: NEW --- QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: unspecifiedKeywords: Security
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
A flaw was found in PJSIP, a multimedia communication library. This heap-based buffer overflow vulnerability exists in the DNS parser's name length handler. A remote attacker could exploit this by sending a specially crafted DNS response, potentially leading to information disclosure, denial of service, or arbitrary code execution in applications that use PJSIP's built-in DNS resolver, such as PJSUA and PJSUA2.
 Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 2450663, 2450664    
Bug Blocks:    

Description OSIDB Bzimport 2026-03-20 05:02:41 UTC 
PJSIP is a free and open source multimedia communication library written in C. Versions 2.16 and below have a Heap-based Buffer Overflowvulnerability in the DNS parser's name length handler. Thisimpacts applications using PJSIP's built-in DNS resolver, such as those configured with pjsua_config.nameserver or UaConfig.nameserver in PJSUA/PJSUA2. It does not affect users who rely on the OS resolver (e.g., getaddrinfo()) by not configuring a nameserver, or those using an external resolver via pjsip_resolver_set_ext_resolver(). This issue is fixed in version 2.17. For users unable to upgrade, a workaround is to disable DNS resolution in the PJSIP config (by setting nameserver_count to zero) or to use an external resolver implementation instead.