CVE-2025-47780

cli_permissions.conf: deny option does not work for disallowing shell commands

HIGH
7.8
CVSS Score
Published: May 22, 2025 at 04:56 PM UTC
Updated: June 17, 2026 at 09:28 AM UTC
3 products affected across 2 vendorsAsteriskCertified AsteriskAsterisk

Using asterisk by asterisk?

Get instant alerts when new vulnerabilities affect asterisk - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.3%
SSVC
PoC

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 18.26.220.0.0 ≤ v < 20.14.121.0.0 ≤ v < 21.9.122.0.0 ≤ v < 22.4.1
Affected range stops below 18.26.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 20.14.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 21.9.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.4.1, so it looks safe — our inference, not a vendor statement
v < 18.26.2v < 18.9-cert14v < 20.14.1v < 20.7-cert5v < 21.9.1v < 22.4.1
Affected range stops below 18.26.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 18.9-cert14, so it looks safe — our inference, not a vendor statement
Affected range stops below 20.14.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 20.7-cert5, so it looks safe — our inference, not a vendor statement
Affected range stops below 21.9.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.4.1, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (2)

SSVC — Action Prioritization

SSVCPoCNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-78

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card