# CVE-2025-49832: Asterisk is Vulnerable to Remote DoS and possible RCE Attacks During Memory Allocation

> Remote attackers can cause denial of service or potentially execute code in Asterisk via crafted SIP headers when STIR/SHAKEN verification is enabled.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Aug 2025
- **Updated:** 1 Aug 2025
- **Also known as:** DEBIAN-CVE-2025-49832, GHSA-mrq5-74j5-f5cr, UBUNTU-CVE-2025-49832

## What is CVE-2025-49832?

CVE-2025-49832 is a medium-severity vulnerability in asterisk, published on 1 Aug 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Asterisk is an open source private branch exchange and telephony toolkit. In versions up to and including 18.26.2, between 20.00.0 and 20.15.0, 20.7-cert6, 21.00.0, 22.00.0 through 22.5.0, there is a remote DoS and possible RCE condition in `asterisk/res/res_stir_shaken /verification.c` that can be exploited when an attacker can set an arbitrary Identity header, or STIR/SHAKEN is enabled, with verification set in the SIP profile associated with the endpoint to be attacked. This is fixed in versions 18.26.3, 20.7-cert6, 20.15.1, 21.10.1 and 22.5.1.

Weakness: CWE-476 (NULL Pointer Dereference)

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

It affects 2 products.


Products: Sangoma Asterisk, Sangoma Certified Asterisk.

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

Upgrade to a fixed version.

## Is CVE-2025-49832 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-49832 exists.

## 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-2025-57767](https://insights.sbomify.com/CVE-2025-57767/): Asterisk can crash from a specifically malformed Authorization header in an incoming SIP request (high 7.5)
- [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)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-49832 is a medium-severity vulnerability in asterisk, published on 1 Aug 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-49832 exists.

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-49832/ (Markdown: https://insights.sbomify.com/CVE-2025-49832/index.md)
```

## Sources

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

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