CVE-2022-21722 | Potential out-of-bound read during RTP/RTCP parsing in PJSIP

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 version 2.11.1 and prior, there are various cases where it is possible that certain incoming RTP/RTCP packets can potentially cause out-of-bound read access. This issue affects all users that use PJMEDIA and accept incoming RTP/RTCP. A patch is available as a commit in the `master` branch. There are no known workarounds.

Published: 2022-01-27 Last update: 2025-11-04 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2022-21722 is rated Moderate Risk (58.9/100): CVSS Critical severity, with medium exploitation likelihood (EPSS 0.46%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2022-21722

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-01-24 0.29% 0.46% +0.17%
2 2026-01-16 0.50% 0.29% -0.21%
3 2026-01-09 — 0.50% —

Full EPSS history (20 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2022-21722

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
9.1 3.1 CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 5.2 [email protected]
9.1 3.1 CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 5.2 [email protected]
6.4 2.0 MEDIUM
AV:N/AC:L/Au:N/C:P/I:N/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:N)
No integrity impact.
Availability impact (A:P)
Partial availability impact.
 10.0 4.9 [email protected]

Weakness enumeration for CVE-2022-21722

OS Trackers for CVE-2022-21722

vendor priority summary link
alpine critical CVE-2022-21722: 1 source package rows (pjproject); 17 state rows across 7 repos (3.17-main, 3.18-main, 3.19-main, 3.20-main, 3.21-main, 3.22-main, edge-main); fixed 7, open 10. https://security.alpinelinux.org/vuln/CVE-2022-21722
debian not yet assigned CVE-2022-21722 not yet assigned priority: Debian including 2 source packages (asterisk, ring), 4 status rows across 3 suites (bookworm, bullseye, sid): resolved 4. https://security-tracker.debian.org/tracker/CVE-2022-21722
gentoo normal CVE-2022-21722: 1 GLSA(s) (202210-37), 1 atom(s) (net-libs/pjproject); latest impact normal. https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2022-21722
ubuntu medium CVE-2022-21722 medium priority: Ubuntu including 2 source packages (pjproject, ring), 16 status rows across 12 suites (bionic, focal, impish, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): DNE 4, ignored 4, not-affected 3, needed 2, released 2, needs-triage 1. https://ubuntu.com/security/CVE-2022-21722

Affected software / configurations for CVE-2022-21722

Vendor Product Version Raw CPE
teluu pjsip <= 2.11.1 cpe:2.3:a:teluu:pjsip:*:*:*:*:*:*:*:*
debian debian_linux 9.0 cpe:2.3:o:debian:debian_linux:9.0:*:*:*:*:*:*:*
debian debian_linux 10.0 cpe:2.3:o:debian:debian_linux:10.0:*:*:*:*:*:*:*

References for CVE-2022-21722

cvelogic Threat Intelligence