LiveActive security incident?Get immediate response
CVE Record

CVE-2021-43301: Stack overflow in PJSUA API when calling pjsua_playlist_create.

Stack overflow in PJSUA API when calling pjsua_playlist_create. An attacker-controlled 'file_names' 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 analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2021-43301 is a memory safety flaw in PJSIP/PJProject’s PJSUA playlist creation API. If attacker-controlled playlist file names reach this API, they may overflow a fixed-size stack buffer. Business risk depends on whether applications expose that argument to untrusted users or media/session data.

Executive priority

Treat this as a targeted dependency remediation item, not a confirmed emergency. Prioritize systems using PJSIP in internet-facing or user-driven VoIP workflows, especially where playlist or media file names can come from outside trusted administrators.

Technical view

The issue is a CWE-121 stack-based buffer overflow in pjsua_playlist_create. The file_names argument is copied into a fixed-size stack buffer without size validation. The source bundle names teluu pjsip with unspecified affected versions and lists Debian security updates for pjproject and downstream packages.

Likely exposure

Exposure is most likely in VoIP, SIP, or media applications that use PJSIP/PJProject and call pjsua_playlist_create with untrusted or externally influenced file name input. The bundle does not identify exact affected versions or deployment patterns.

Exploitation context

The provided sources do not show active exploitation, and KEV is false. The vulnerability is plausibly serious because stack overflows can cause crashes or code execution, but exploitability depends on application control of file_names, build protections, and runtime context.

Researcher notes

Evidence is strong for the bug class and affected API, but incomplete for affected version ranges, CVSS, exploit status, and exact fixed releases in the supplied bundle. Avoid broad claims beyond PJSIP/PJProject and referenced distribution security updates.

Mitigation direction

  • Check the PJProject GitHub advisory for fixed versions and upgrade guidance.
  • Apply relevant Debian security updates for pjproject and dependent packages.
  • Audit applications for pjsua_playlist_create usage with untrusted file_names input.
  • Restrict or validate playlist file names before they reach PJSUA APIs.
  • Track downstream vendor guidance for Asterisk, Ring, or bundled PJProject copies.

Validation and detection

  • Inventory installed pjsip, pjproject, and bundled PJProject library versions.
  • Search code for pjsua_playlist_create and review file_names data origins.
  • Confirm patched distribution packages or vendor-fixed builds are installed.
  • Review SBOMs for applications embedding PJProject rather than using system packages.
  • Check whether external users can influence playlist file names.
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-43301 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