Skip to content
Fencer Intel
high 7.5

CVE-2025-57767 json

Asterisk can crash from a specifically malformed Authorization header in an incoming SIP request

published last yr. modified 4mo ago also EUVD-2025-26117

cvss
7.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 37%
public exploits
0
none known

Summary

Asterisk is an open source private branch exchange and telephony toolkit. Prior to versions 20.15.2, 21.10.2, and 22.5.2, if a SIP request is received with an Authorization header that contains a realm that wasn't in a previous 401 response's WWW-Authenticate header, or an Authorization header with an incorrect realm was received without a previous 401 response being sent, the get_authorization_header() function in res_pjsip_authenticator_digest will return a NULL. This wasn't being checked before attempting to get the digest algorithm from the header which causes a SEGV. This issue has been patched in versions 20.15.2, 21.10.2, and 22.5.2. There are no workarounds.

Patch / fix

  • asterisk certified_asterisk 20.15.2, 21.10.2, 22.5.2
  • asterisk open_source 20.15.2, 21.10.2, 22.5.2
  • digium asterisk 20.15.2, 21.10.2, 22.5.2
  • digium certified_asterisk 20.15.2, 21.10.2, 22.5.2
  • sangoma certified_asterisk 20.15.2, 21.10.2, 22.5.2
  • asterisk Debian 14 1:22.5.2~dfsg+~cs6.15.60671435-1

debian advisories DEBIAN-CVE-2025-57767

Is CVE-2025-57767 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2025-57767 updated cvss 5.3

asterisk: Asterisk denial of service via malformed SIP request

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.43% chance of exploitation in the next 30 days, higher than 37% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected products

  • asterisk asterisk

Classification

Weakness
  • CWE-253 Incorrect Check of Function Return Value

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.