CVE-2022-24754 [High] | Memory Corruption in Pjsip

PJSIP is a free and open source multimedia communication library written in C language. In versions prior to and including 2.12 PJSIP there is a stack-buffer overflow vulnerability which only impacts PJSIP users who accept hashed digest credentials (credentials with data_type `PJSIP_CRED_DATA_DIGEST`). This issue has been patched in the master branch of the PJSIP repository and will be included with the next release. Users unable to upgrade need to check that the hashed digest data length must be equal to `PJSIP_MD5STRLEN` before passing to PJSIP.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-05-22	0.47%	0.57%	+0.10%
2	2026-01-16	0.29%	0.47%	+0.18%
3	2025-11-21	—	0.29%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-05-22

0.47%

0.57%

+0.10%

2026-01-16

0.29%

0.47%

+0.18%

2025-11-21

—

0.29%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
8.5	3.1	HIGH	`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/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:H) Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:C) Breaking this can reach past the original component and bite other resources—bigger blast radius. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	1.8	6.0	[email protected]
9.8	3.1	CRITICAL	`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	3.9	5.9	[email protected]
7.5	2.0	HIGH	`AV:N/AC:L/Au:N/C:P/I:P/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:P) Partial integrity impact. Availability impact (A:P) Partial availability impact.	10.0	6.4	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

8.5

3.1

HIGH

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/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:H): Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:C): Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

1.8

6.0

[email protected]

9.8

3.1

CRITICAL

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

3.9

5.9

[email protected]

7.5

2.0

HIGH

AV:N/AC:L/Au:N/C:P/I:P/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:P): Partial integrity impact.
Availability impact (A:P): Partial availability impact.

10.0

6.4

[email protected]

OS Trackers for CVE-2022-24754

vendor	priority	summary	link
`alpine`	high	CVE-2022-24754: 1 source package rows (pjproject); 22 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 15.	https://security.alpinelinux.org/vuln/CVE-2022-24754
`debian`	unimportant	CVE-2022-24754 unimportant 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-24754
`gentoo`	normal	CVE-2022-24754: 1 GLSA(s) (202210-37), 1 atom(s) (net-libs/pjproject); latest impact normal.	https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2022-24754
`ubuntu`	medium	CVE-2022-24754 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, released 3, needed 2, not-affected 2, needs-triage 1.	https://ubuntu.com/security/CVE-2022-24754

Affected software / configurations for CVE-2022-24754

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

References for CVE-2022-24754

URL	Tags
https://github.com/pjsip/pjproject/commit/d27f79da11df7bc8bb56c2f291d71e54df8d2c47	Patch Third Party Advisory
https://github.com/pjsip/pjproject/security/advisories/GHSA-73f7-48m9-w662	Patch Third Party Advisory
https://lists.debian.org/debian-lts-announce/2022/03/msg00035.html	Mailing List Third Party Advisory
https://lists.debian.org/debian-lts-announce/2023/08/msg00038.html
https://security.gentoo.org/glsa/202210-37	Third Party Advisory
https://lists.debian.org/debian-lts-announce/2024/09/msg00030.html

URL

CVE-2022-24754 | Buffer overflow in pjsip

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

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

Weakness enumeration for CVE-2022-24754

OS Trackers for CVE-2022-24754

Affected software / configurations for CVE-2022-24754

References for CVE-2022-24754