Memory corruption via unchecked recorder filename copy
Published Feb 16, 2022 · Updated Nov 4, 2025
Stack buffer overflow in Teluu PJSIP 2.11.1 and earlier allows context-dependent attackers to corrupt memory via a recorder filename. The pjsua_recorder_create function copies the filename into a fixed-size stack buffer without validating its length against PJ_MAXPATH. Exploitation requires a calling application to pass attacker-controlled input to this API, corrupting stack memory within the consuming process.
Summary
What happened
Stack buffer overflow in Teluu PJSIP 2.11.1 and earlier allows context-dependent attackers to corrupt memory via a recorder filename. The pjsua_recorder_create function copies the filename into a fixed-size stack buffer without validating its length against PJ_MAXPATH. Exploitation requires a calling application to pass attacker-controlled input to this API, corrupting stack memory within the consuming process.
The record
- CVE
- CVE-2021-43300
- Published
- Feb 16, 2022
- Updated
- Nov 4, 2025
- Vendor
- Teluu
- Product
- PJSIP
- Classifications
- CWE-787, CWE-121
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 16, 2022CVE publishedPublication date reported by the CVE source.
- Nov 4, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <=2.11.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo