dbcve.org
Debian LinuxOperating system · Debian

CVE-2022-26498

HIGH · 7.5 CVSS v3.1 Published 2022-04-15
Fix available
A fix is available. Upgrade to 18.11.2 or later.
See remediation →
84/100
Remediation priority · High
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
An issue was discovered in Asterisk through 19.x. When using STIR/SHAKEN, it is possible to download files that are not certificates. These files could be much larger than what one would expect to download, leading to Resource Exhaustion. This is fixed in 16.25.2, 18.11.2, and 19.3.2.

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-400

A single request can consume unbounded CPU, memory, or connections, so a modest amount of malicious traffic exhausts the service. The result is denial of service for everyone else. Remediation is enforcing limits, quotas, and timeouts on what any one request can use.

General guidance for the uncontrolled resource consumption 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:= 10.0= 11.0
AsteriskApplication
Affected:>= 16.15.0, <= 16.25.1>= 18.0, < 18.11.2>= 19.0.0, <= 19.3.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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 18.11.2 or later
Fixed in 18.11.2
Vendor patch packetstormsecurity.com →
Recommended fix High confidence

Upgrade to Asterisk 16.25.2, 18.11.2, or 19.3.2 depending on your current branch (16.x, 18.x, or 19.x)

  1. 1. Identify the currently installed Asterisk version by running 'asterisk -V' or 'apt-cache policy asterisk'
  2. 2. Determine which Asterisk branch (16, 18, or 19) is currently in use
  3. 3. For Debian systems: run 'apt update' followed by 'apt list --upgradable' to check for available security updates
  4. 4. If Debian security updates are available, apply them with 'apt upgrade asterisk'
  5. 5. If upgrading manually, download the appropriate fixed version (16.25.2 for branch 16.x, 18.11.2 for branch 18.x, or 19.3.2 for branch 19.x) from downloads.asterisk.org
  6. 6. Install the new package using your distribution's package manager (e.g., dpkg -i for Debian)
  7. 7. After installation, restart the Asterisk service with 'systemctl restart asterisk' or 'service asterisk restart'
  8. 8. Verify the fix by running 'asterisk -V' to confirm the installed version matches the expected fixed release

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 $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-26498 — 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-26498 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