# CVE-2025-57767: Asterisk can crash from a specifically malformed Authorization header in an incoming SIP request

> A remote attacker can crash Asterisk by sending a SIP request with a malformed Authorization header, causing a null pointer dereference.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Aug 2025
- **Updated:** 28 Aug 2025
- **Also known as:** DEBIAN-CVE-2025-57767, GHSA-64qc-9x89-rx5j, UBUNTU-CVE-2025-57767

## What is CVE-2025-57767?

CVE-2025-57767 is a high-severity vulnerability in asterisk, published on 28 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-253 (Incorrect Check of Function Return Value)

## Which versions are affected by CVE-2025-57767?

It affects 1 product.


Products: Sangoma Asterisk.

## How do I fix CVE-2025-57767?

Upgrade to a fixed version.

## Is CVE-2025-57767 being exploited?

There is no known exploitation of CVE-2025-57767 in the wild and no public exploit code.

## Other vulnerabilities in asterisk

- [CVE-2024-57520](https://insights.sbomify.com/CVE-2024-57520/): Path traversal in n/a (critical 9.8)
- [CVE-2025-47779](https://insights.sbomify.com/CVE-2025-47779/): Using malformed From header can forge identity with ";" or NULL in name portion (high 7.7)
- [CVE-2022-37325](https://insights.sbomify.com/CVE-2022-37325/): Memory corruption in n/a (high 7.5)
- [CVE-2025-1131](https://insights.sbomify.com/CVE-2025-1131/): Asterisk Unsafe Shell Sourcing in safe_asterisk Leads to Local Privilege Escalation (high 7.0)
- [CVE-2025-54995](https://insights.sbomify.com/CVE-2025-54995/): Asterisk remotely exploitable leak of RTP UDP ports and internal resources (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-57767 and fix it if it is affected.

What it is: CVE-2025-57767 is a high-severity vulnerability in asterisk, published on 28 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-57767 in the wild and no public exploit code.

Affected product: asterisk. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-57767/ (Markdown: https://insights.sbomify.com/CVE-2025-57767/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-57767
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-57767
- OSV: https://osv.dev/vulnerability/CVE-2025-57767

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-57767/
Summaries are generated and may contain mistakes; the official description above is the record.