dbcve.org
Debian LinuxOperating system · Debian

CVE-2022-21723

CRITICAL · 9.1 CVSS v3.1 Published 2022-01-27
Fix available
A fix is available. Upgrade to 16.24.1 / 18.10.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis
How this class of weakness works · CWE-125

The code reads past the end (or before the start) of a buffer, returning memory that was never meant to be exposed. Attackers use it to leak secrets like keys or to defeat memory-protection defences. Remediation is validating indices and lengths before every read.

General guidance for the out-of-bounds read class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Debian LinuxOperating system
Affected:= 9.0= 10.0
PjsipApplication
Affected:<= 2.11.1
Certified AsteriskApplication
Affected:= 16.8.0
AsteriskApplication
Affected:>= 16.0.0, < 16.24.1>= 18.0.0, < 18.10.1>= 19.0.0, < 19.2.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
High

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

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 16.24.1 / 18.10.1 / 19.2.1 or later
Fixed in 16.24.118.10.119.2.1
Vendor patch seclists.org →
Recommended fix High confidence

PJSIP: upgrade to 2.12 or later; Asterisk 16.x: upgrade to 16.24.1+; Asterisk 18.x: upgrade to 18.10.1+; Asterisk 19.x: upgrade to 19.2.1+; Debian: apply security updates

  1. For PJSIP users: Upgrade to PJSIP version 2.12 or later (the fixed version containing the patch for this vulnerability)
  2. For Asterisk 16.x users: Upgrade to Asterisk 16.24.1 or later
  3. For Asterisk 18.x users: Upgrade to Asterisk 18.10.1 or later
  4. For Asterisk 19.x users: Upgrade to Asterisk 19.2.1 or later
  5. For Debian users: Apply vendor security updates for Debian 9 (stretch) and Debian 10 (buster) via apt-get update && apt-get upgrade
  6. After upgrading, verify the SIP multipart parser handles malformed messages correctly by testing with intentionally malformed SIP content
Caveat Asterisk major version upgrades may introduce API changes; review Asterisk changelog before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $3,550. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-21723 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-21723 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data