Skip to main content

CVE-2022-21723: CWE-125: Out-of-bounds Read in pjsip pjproject

Medium
Published: Thu Jan 27 2022 (01/27/2022, 00:00:00 UTC)
Source: CVE
Vendor/Project: pjsip
Product: pjproject

Description

PJSIP is a free and open source multimedia communication library written in C language implementing standard based protocols such as SIP, SDP, RTP, STUN, TURN, and ICE. In versions 2.11.1 and prior, parsing an incoming SIP message that contains a malformed multipart can potentially cause out-of-bound read access. This issue affects all PJSIP users that accept SIP multipart. The patch is available as commit in the `master` branch. There are no known workarounds.

AI-Powered Analysis

AILast updated: 06/23/2025, 18:01:58 UTC

Technical Analysis

CVE-2022-21723 is a medium-severity vulnerability classified under CWE-125 (Out-of-bounds Read) affecting the pjproject component of the PJSIP multimedia communication library. PJSIP is an open-source library written in C that implements widely used communication protocols such as SIP (Session Initiation Protocol), SDP, RTP, STUN, TURN, and ICE. The vulnerability exists in versions 2.11.1 and earlier. It arises when the library parses incoming SIP messages containing malformed multipart content. Specifically, the malformed multipart causes the parser to read memory beyond the intended buffer boundaries, leading to an out-of-bounds read condition. This can result in the exposure of sensitive memory contents or cause application instability or crashes due to invalid memory access. The vulnerability affects all users of PJSIP that accept SIP multipart messages, which is common in VoIP and multimedia communication applications. No known workarounds exist, but a patch addressing the issue has been committed to the master branch of the pjproject repository. There are no known exploits in the wild at the time of this analysis. The vulnerability does not require authentication or user interaction to be triggered, as it is exploitable by sending a crafted SIP message to a vulnerable endpoint. The root cause is improper input validation and boundary checking during multipart parsing in the SIP message processing code.

Potential Impact

For European organizations, the impact of this vulnerability primarily concerns entities relying on PJSIP-based communication infrastructure, such as VoIP providers, telephony systems, unified communications platforms, and multimedia conferencing solutions. Exploitation could lead to information disclosure by reading sensitive memory contents, potentially exposing credentials, session tokens, or other confidential data. Additionally, the out-of-bounds read may cause service instability or crashes, resulting in denial of service conditions that disrupt communication services. This can affect critical business operations, especially in sectors like finance, healthcare, government, and telecommunications where reliable and secure communication is essential. Since PJSIP is widely used in embedded devices and softphones, the vulnerability could also impact Internet of Things (IoT) devices and network equipment deployed across European networks. The lack of known exploits reduces immediate risk, but the ease of exploitation by sending crafted SIP messages means attackers could develop exploits, increasing future risk. The vulnerability's impact on confidentiality and availability makes it a concern for organizations handling sensitive communications and requiring high service uptime.

Mitigation Recommendations

European organizations should prioritize upgrading all PJSIP deployments to versions later than 2.11.1 where the patch is applied. Since no workarounds exist, patching is the primary mitigation strategy. Network administrators should implement SIP message filtering and deep packet inspection to detect and block malformed multipart SIP messages at the perimeter or session border controllers (SBCs). Deploying anomaly detection systems that monitor SIP traffic for unusual multipart structures can help identify exploitation attempts. Organizations should also conduct an inventory of all systems using PJSIP, including embedded devices and softphones, to ensure comprehensive patch coverage. Where immediate patching is not feasible, isolating vulnerable systems in segmented network zones with strict access controls can reduce exposure. Logging and monitoring SIP traffic for crashes or unusual behavior can provide early warning of exploitation attempts. Finally, organizations should engage with vendors of PJSIP-based products to confirm patch availability and deployment timelines.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
GitHub_M
Date Reserved
2021-11-16T00:00:00.000Z
Cisa Enriched
true

Threat ID: 682d9842c4522896dcbf238b

Added to database: 5/21/2025, 9:09:22 AM

Last enriched: 6/23/2025, 6:01:58 PM

Last updated: 7/25/2025, 8:58:35 PM

Views: 14

Actions

PRO

Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats