No advisories yet.
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Tue, 24 Mar 2026 02:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Pjsip pjsip
|
|
| CPEs | cpe:2.3:a:pjsip:pjsip:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Pjsip pjsip
|
|
| Metrics |
cvssV3_1
|
Fri, 20 Mar 2026 15:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Fri, 20 Mar 2026 09:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Pjsip
Pjsip pjproject |
|
| Vendors & Products |
Pjsip
Pjsip pjproject |
Fri, 20 Mar 2026 04:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | PJSIP is vulnerable to Heap-based Buffer Overflow through DNS parser | |
| Weaknesses | CWE-122 | |
| References |
| |
| Metrics |
cvssV4_0
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-03-20T14:28:15.761Z
Reserved: 2026-03-17T00:05:53.283Z
Link: CVE-2026-32945
Updated: 2026-03-20T14:28:12.755Z
Status : Analyzed
Published: 2026-03-20T04:16:49.927
Modified: 2026-03-23T20:54:34.997
Link: CVE-2026-32945
No data.
OpenCVE Enrichment
Updated: 2026-03-20T10:37:26Z