Asterisk unauthorized file writes via ARI setChannelVar
asterisk · asterisk certified-asterisk
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| asterisk asterisk |
| No fix yet |
| asterisk certified-asterisk |
| No fix yet |
asterisk · asterisk certified-asterisk
| Product | Affected | Fixed in |
|---|---|---|
| asterisk asterisk |
| No fix yet |
| 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 20.7-cert11, 22.8-cert3, an authenticated Asterisk REST Interface (ARI) attacker with read-only privileges may use `setChannelVar` to execute write dialplan functions, including `FILE()` writes, even when `live_dangerously` in `asterisk.conf` is set to no. 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 20.7-cert11, 22.8-cert3.
From the CVE record · GitHub_M
An authenticated attacker with read-only Asterisk REST Interface (ARI) credentials can use `setChannelVar` to run write dialplan functions, including `FILE()` writes, even when `live_dangerously` is set to no. The Asterisk HTTP web server must be enabled and reachable; it is disabled by default and, when enabled, binds only to 127.0.0.1 by default.
Operators running Asterisk before 20.20.1, 21.12.3, 22.10.1, or 23.4.1, or Certified Asterisk before 20.7-cert11 or 22.8-cert3, should check their installations.