Security readout for executives and security teams
PJSIP’s STUN handling can mishandle a malformed error message, creating memory-safety risk. A nearby network attacker could send a crafted UDP STUN packet and potentially run code on the victim system. Organizations using PJSIP/pjproject with STUN should treat this as a high-priority patching issue. Exposure is most likely where applications embed or package pjproject/PJSIP <= 2.11.1 and use STUN. The source bundle references pjproject directly and downstream advisories for Asterisk, Debian, Gentoo, and Ring packages. Prioritize remediation for voice, communications, or multimedia services using PJSIP with STUN. The issue is high severity because exploitation requires no credentials or user action, although the provided evidence limits the attacker position to the victim’s network. Mitigation focus: Upgrade pjproject/PJSIP beyond affected versions using vendor guidance.; Apply relevant Debian, Gentoo, Asterisk, or Ring security updates where packaged.; Prioritize systems using STUN on reachable network paths..
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-191: 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 lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2021-37706 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
- High
- CVSS
- 7.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
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:L/PR:N/UI:N/S:U/C:L/I:L/A:L3.93.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.3HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/pjsip/pjproject/security/advisories/GHSA-2qpg-f6wf-w984CVE reference
- https://github.com/pjsip/pjproject/commit/15663e3f37091069b8c98a7fce680dc04bc8e865CVE reference
- [debian-lts-announce] 20220328 [SECURITY] [DLA 2962-1] pjproject security updateCVE reference · mailing-list
- GLSA-202210-37CVE reference · vendor-advisory
- [debian-lts-announce] 20221117 [SECURITY] [DLA 3194-1] asterisk security updateCVE reference · mailing-list
- DSA-5285CVE reference · vendor-advisory
- [debian-lts-announce] 20230829 [SECURITY] [DLA 3549-1] ring security updateCVE reference · mailing-list
- 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.
Integer Underflow (Wrap or Wraparound)
Integer Underflow (Wrap or Wraparound) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.