cve.bz

CVE-2025-57767 sangoma asterisk: Incorrect Check of Function Return Value

7.5 highEPSS 0.5%Fix available

High (7.5) in sangoma asterisk. EPSS 0.5% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.5% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 40th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2025-08-28. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-253 Incorrect Check of Function Return Value
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-57767 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-57767?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-57767?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-57767 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
sangoma:asteriskbefore 20.15.2
sangoma:asteriskfrom 21.0.0 before 21.10.2
sangoma:asteriskfrom 22.0.0 before 22.5.2

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian14asterisk1:22.5.2~dfsg+~cs6.15.60671435-1DEBIAN-CVE-2025-57767
Ubuntu18.04:LTS, 20.04:LTS, 22.04:LTS and 5 moreasteriskno fix listedUBUNTU-CVE-2025-57767

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

References

Check your stackJSON