Security readout for executives and security teams
Plain-English summary
PJSIP/pjproject before the 2.13.1 patch can mishandle a crafted STUN message. For affected VoIP, SIP, or NAT traversal systems, the main business risk is service disruption, with limited possible information exposure. Exploitation requires a specific network message and is rated high complexity.
Executive priority
Prioritize remediation for externally reachable communications services or products that embed pjproject. This is not marked as actively exploited, but a remotely triggerable availability issue in VoIP infrastructure can still affect business continuity.
Technical view
Sources describe a STUN parsing memory-safety flaw in pjproject <=2.13. The title/CWE indicate heap buffer overflow, while the description says buffer overread when decoding unknown STUN attributes. Affected users include applications using STUN through PJNATH and PJSUA-LIB. CVSS 3.1 is 6.5: network, high complexity, no privileges, no user interaction, low confidentiality impact, high availability impact.
Likely exposure
Exposure is most likely in products or services embedding pjproject/PJSIP <=2.13 for SIP, VoIP, WebRTC-adjacent, STUN, TURN, ICE, or NAT traversal functions. Internet-reachable STUN handling increases concern, but the sources do not identify specific downstream products beyond pjproject components.
Exploitation context
The provided sources do not show CISA KEV listing or active exploitation evidence. The CVSS vector indicates remote unauthenticated attack surface, but high attack complexity. Treat this as a credible denial-of-service risk for exposed communications infrastructure rather than confirmed widespread exploitation.
Researcher notes
Evidence is sufficient for affected upstream versions and patch direction, but incomplete for downstream product exposure and real-world exploitation. Note the source wording inconsistency between heap overflow and buffer overread; analyze patched parser behavior before classifying impact further.
Mitigation direction
- Upgrade pjproject/PJSIP to a version containing the 2.13.1 patch.
- Apply Debian LTS pjproject updates where Debian packages are used.
- Identify bundled or statically linked pjproject copies in vendor applications.
- Reduce untrusted STUN exposure where operationally possible.
- Check vendor guidance for downstream products embedding pjproject.
Validation and detection
- Inventory pjproject/PJSIP versions and confirm none are <=2.13 without the patch.
- Confirm whether PJNATH, PJSUA-LIB, STUN, TURN, or ICE features are enabled.
- Verify patched builds include commit d8440f4d711a654b511f50f79c0445b26f9dd1e1 or vendor equivalent.
- Review service crash logs around STUN-processing components.
- Confirm Debian systems include the relevant LTS security update where applicable.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-122: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2022-23537 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:H2.24.2Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.5MediumVector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/pjsip/pjproject/security/advisories/GHSA-9pfh-r8x4-w26wCVE reference · x_refsource_CONFIRM
- https://github.com/pjsip/pjproject/commit/d8440f4d711a654b511f50f79c0445b26f9dd1e1CVE reference · x_refsource_MISC
- https://lists.debian.org/debian-lts-announce/2023/08/msg00038.htmlCVE reference
- https://lists.debian.org/debian-lts-announce/2024/09/msg00030.htmlCVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Heap-based Buffer Overflow
Heap-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.