CVE-2022-24764· NVD / CVE Program· CNA GitHub_M

Stack buffer overflow in pjproject

Noroxi assessment

Priority: Monitor (action score 31/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 2.3% (FIRST EPSS); higher than 83.7% of all records.
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
According to CISA the attack is automatable: targets can be found by mass scanning.
Fixed version: pjproject (Alpine:v3.16) 2.12.1-r0; asterisk (Debian:10) 1:16.28.0~dfsg-0+deb10u1; ring (Debian:10) 20190215.1.f152c98~ds1-1+deb10u2.

Low priority for now. Upgrade to pjproject (Alpine:v3.16) 2.12.1-r0; asterisk (Debian:10) 1:16.28.0~dfsg-0+deb10u1; ring (Debian:10) 20190215.1.f152c98~ds1-1+deb10u2 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

PJSIP is a free and open source multimedia communication library written in C. Versions 2.12 and prior contain a stack buffer overflow vulnerability that affects PJSUA2 users or users that call the API `pjmedia_sdp_print(), pjmedia_sdp_media_print()`. Applications that do not use PJSUA2 and do not directly call `pjmedia_sdp_print()` or `pjmedia_sdp_media_print()` should not be affected. A patch is available on the `master` branch of the `pjsip/pjproject` GitHub repository. There are currently no known workarounds.

HighCVSS 7.5 · v3.1—No exploit Fix available

Published: Mar 22, 2022
Updated: Jun 17, 2026
EPSS: 2.3% · 83th percentile
CWE: CWE-120

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 30 / 40 · 7.5 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 1 / 30 · 2.3%

CISA SSVC decision

Exploitation: none
Automatable: yes
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: 7.5
CNA · GitHub_M: 7.5; agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
teluu	pjsip	cpe:2.3:a:teluu:pjsip
debian	debian linux	cpe:2.3:o:debian:debian_linux

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

debian debian linux10.0
debian debian linux9.0
teluu pjsipup to 2.12 inclusive

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

pjsip pjproject
- <= 2.12affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Alpine:v3.16	pjproject	before 2.12.1-r0	2.12.1-r0
Debian:10	asterisk	before 1:16.28.0~dfsg-0+deb10u1	1:16.28.0~dfsg-0+deb10u1
Debian:10	ring	before 20190215.1.f152c98~ds1-1+deb10u2	20190215.1.f152c98~ds1-1+deb10u2
Debian:11	asterisk	before 1:16.28.0~dfsg-0+deb11u1	1:16.28.0~dfsg-0+deb11u1
Debian:11	ring	before 20210112.2.b757bac~ds1-1+deb11u1	20210112.2.b757bac~ds1-1+deb11u1
Debian:12	ring	before 20230206.0~ds1-1	20230206.0~ds1-1
Debian:14	asterisk	before 1:18.14.0~~rc1~dfsg+~cs6.12.40431414-1	1:18.14.0~~rc1~dfsg+~cs6.12.40431414-1
Debian:9	pjproject	before 2.5.5~dfsg-6+deb9u3	2.5.5~dfsg-6+deb9u3

Same product

teluu: all records

Other highest-scoring records for the same primary product.

CVE-2022-31031Potential stack buffer overflow when parsing message as a STUN client
40Plan
CVE-2022-24754Buffer overflow in pjsip
40Plan
CVE-2022-23608Use after free in PJSIP
40Plan

Published before and after this one in the same product

← EarlierCVE-2021-43302Feb 16, 2022 · Read out-of-bounds in PJSUA API when calling pjsua_recorder_create.
37Monitor
← EarlierCVE-2021-43303Feb 16, 2022 · Buffer overflow in PJSUA API when calling pjsua_call_dump.
40Plan
Later →CVE-2022-24763Mar 30, 2022 · Infinite Loop in PJSIP
31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
alpine:pjproject	2.12.1-r0 · Alpine:v3.16	Package registry (OSV)
debian:asterisk	1:18.14.0~~rc1~dfsg+~cs6.12.40431414-1 · Debian:14	Package registry (OSV)
debian:pjproject	2.5.5~dfsg-6+deb9u3 · Debian:9	Package registry (OSV)
debian:ring	20230206.0~ds1-1 · Debian:12	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

pjsip/pjprojectcommit 560a134

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: none
Integrity: none
Availability: high · the service can be disrupted

Attack vector: Network
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality impact: None
Integrity impact: None
Availability impact: High

Weakness class (CWE)

CWE-120 · Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Root cause

When data is copied, the source length is not compared with the size of the destination buffer. Excess data overwrites adjacent memory.

The bug in code

The whole CWE-120 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1char buf[256];
2memcpy(buf, pkt->data, pkt->len);

Fixed

1char buf[256];
2if (pkt->len > sizeof(buf)) {
3  return -EINVAL;
4}
5memcpy(buf, pkt->data, pkt->len);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

—

Change log

Fix✗ → ✓Sep 28, 2026, 10:48 PM UTC

For records you follow, these changes also arrive as notifications. →

References

github.com/pjsip/pjproject/commit/560a1346f87aabe126509bb24930106dea292b00

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records