Asterisk authorization bypass in ARI REST-over-WebSocket
asterisk · certified-asterisk
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| asterisk asterisk |
| No fix yet |
| certified-asterisk certified-asterisk |
| No fix yet |
asterisk · certified-asterisk
| Product | Affected | Fixed in |
|---|---|---|
| asterisk asterisk |
| No fix yet |
| certified-asterisk certified-asterisk |
| No fix yet |
Asterisk is an open source private branch exchange and telephony toolkit. Prior to Asterisk 20.20.1, 21.12.3, 22.10.1, 23.4.1 and Certified Asterisk 22.8-cert3, an authenticated attacker with read-only permissions for the `Asterisk REST Interface (ARI)` may, under certain conditions, execute write operations through `REST-over-WebSocket`. The authorization bypass permits `arbitrary module path` loading and conditional remote code execution. The Asterisk HTTP web server must be enabled and reachable, and the attacker must already have valid `read-only ARI credentials`. HTTP is disabled by default and binds only to 127.0.0.1 by default even when enabled. This issue is fixed in Asterisk 20.20.1, 21.12.3, 22.10.1, 23.4.1 and Certified Asterisk 22.8-cert3.
From the CVE record · GitHub_M
In affected Asterisk and Certified Asterisk releases, an authenticated attacker with read-only ARI credentials may execute write operations through REST-over-WebSocket. This can permit arbitrary module path loading and, under certain conditions, remote code execution. The Asterisk HTTP web server must be enabled and reachable; it is disabled by default and, when enabled, binds to 127.0.0.1 by default.
Operators of Asterisk before 20.20.1, 21.12.3, 22.10.1, or 23.4.1, and Certified Asterisk before 22.8-cert3, should check their deployments.