# CVE-2025-47780: cli_permissions.conf: deny option does not work for disallowing shell commands

> Asterisk fails to enforce CLI permission restrictions, allowing attackers to execute shell commands if administrators rely on specific deny configurations.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 May 2025
- **Updated:** 3 Nov 2025
- **Also known as:** DEBIAN-CVE-2025-47780, GHSA-c7p6-7mvq-8jq2, UBUNTU-CVE-2025-47780

## What is CVE-2025-47780?

CVE-2025-47780 is a medium-severity command injection vulnerability in asterisk, published on 22 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Asterisk is an open-source private branch exchange (PBX). Prior to versions 18.26.2, 20.14.1, 21.9.1, and 22.4.1 of Asterisk and versions 18.9-cert14 and 20.7-cert5 of certified-asterisk, trying to disallow shell commands to be run via the Asterisk command line interface (CLI) by configuring `cli_permissions.conf` (e.g. with the config line `deny=!*`) does not work which could lead to a security risk. If an administrator running an Asterisk instance relies on the `cli_permissions.conf` file to work and expects it to deny all attempts to execute shell commands, then this could lead to a security vulnerability. Versions 18.26.2, 20.14.1, 21.9.1, and 22.4.1 of Asterisk and versions 18.9-cert14 and 20.7-cert5 of certified-asterisk fix the issue.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

It affects 2 products.


Products: Sangoma Asterisk, Sangoma Certified Asterisk.

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

Upgrade to a fixed version.

## Is CVE-2025-47780 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-47780 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-47780 and fix it if it is affected.

What it is: CVE-2025-47780 is a medium-severity command injection vulnerability in asterisk, published on 22 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-47780 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-47780/ (Markdown: https://insights.sbomify.com/CVE-2025-47780/index.md)
```

## Sources

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

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