Asterisk code execution or denial of service in T.140 RED handling
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. In affected deployments, an authenticated attacker may cause a `T.140 RED` out-of-bounds write during `generation accumulation` using carefully crafted packets, potentially allowing remote code execution or causing Asterisk to crash. The `chan_sip` channel driver must be installed and configured, and its `textsupport` option must be enabled; `textsupport` defaults to no. `The chan_sip driver was deprecated in Asterisk 20 and completely removed in all later versions.` Repository comparisons verify patch containment in Asterisk 20.20.1, 21.12.3, 22.10.1 and 23.4.1, and Certified Asterisk 20.7-cert11 and 22.8-cert3. The affected release-track scope remains unresolved: structured metadata includes later release tracks even though the advisory says the required `chan_sip` driver was removed there.
From the CVE record · GitHub_M
An out-of-bounds write in T.140 RED generation accumulation can be triggered by carefully crafted packets from an authenticated remote attacker, potentially crashing Asterisk or allowing remote code execution. This requires the chan_sip driver to be installed and configured with textsupport enabled; textsupport is disabled by default. The affected release-track scope is unresolved because the advisory says chan_sip was removed after Asterisk 20, while structured metadata includes later tracks.
Operators of Asterisk or Certified Asterisk with chan_sip installed and textsupport enabled should check their deployments; the affected version ranges are unresolved.