LiveActive security incident?Get immediate response
CVE Record

CVE-2021-43299: Stack overflow in PJSUA API when calling pjsua_player_create.

Stack overflow in PJSUA API when calling pjsua_player_create. An attacker-controlled 'filename' argument may cause a buffer overflow since it is copied to a fixed-size stack buffer without any size validation.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2021-43299 is a memory-safety flaw in PJSIP/PJSUA. If software passes an attacker-controlled filename to pjsua_player_create, an overly long value can overflow a stack buffer. Business urgency depends on whether deployed communications software exposes that API path to untrusted input.

Executive priority

Treat as a targeted remediation item for communications platforms, not a broad emergency from the supplied evidence. Prioritize systems where external users can influence media filenames or where pjproject is embedded in exposed VoIP services.

Technical view

The issue is CWE-121 stack-based buffer overflow in the PJSUA API. The filename argument is copied into a fixed-size stack buffer without size validation. Public sources do not provide CVSS, affected version ranges, or confirmed exploitability details.

Likely exposure

Likely exposure is systems using pjproject/PJSIP, especially packaged or embedded VoIP and communications software. Debian published security updates for pjproject and downstream packages including asterisk and ring, but the provided sources do not define precise upstream affected versions.

Exploitation context

The provided sources do not show CISA KEV listing or confirmed active exploitation. Exploitation would require attacker influence over the filename value passed into pjsua_player_create by an affected application.

Researcher notes

Key gaps are missing CVSS, unspecified affected versions, and no confirmed exploit status in the supplied bundle. Validation should focus on API reachability and whether filename input can cross a trust boundary before reaching pjsua_player_create.

Mitigation direction

  • Apply vendor or distribution security updates for pjproject/PJSIP packages.
  • Review Debian advisories if using Debian-packaged pjproject, asterisk, or ring.
  • Check Teluu/PJSIP advisory for fixed versions and maintainer guidance.
  • Reduce exposure of workflows that accept untrusted media filename input.
  • Rebuild or update applications statically embedding vulnerable pjproject code.

Validation and detection

  • Inventory systems and applications using pjproject or PJSIP.
  • Identify code paths calling pjsua_player_create with external input.
  • Compare installed package versions against vendor and distribution advisories.
  • Confirm updated packages are deployed across runtime and build environments.
  • Check whether downstream products statically bundle pjproject.
Prepared
Confidence
medium
Sources
7

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

CWE-121: 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 lookup
cve · low confidence lookup

CVE-2021-43299 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

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.

0CVSS vectors
0Timeline events
0ADP providers
7Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
teluupjsipunspecifiedListed
Weakness

CWE details

CWE-121

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-121 · source CWE mapping

Stack-based Buffer Overflow

Stack-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs