Asterisk denial of service in H.323 trace logging
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, a stack buffer overflow in the H.323 `ooTrace()` trace-logging function can occur when unbounded `vsprintf` writes into a fixed `2048-byte buffer`. A remote attacker may send a carefully crafted packet that causes the Asterisk process to crash. The `chan_ooh323` addon channel driver must be explicitly compiled and installed, which is not the default, and its port must be publicly reachable. 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
A stack buffer overflow in the H.323 ooTrace() function can crash the Asterisk process. A remote attacker can trigger it with a crafted packet if the chan_ooh323 addon channel driver has been explicitly compiled and installed and its port is publicly reachable.
Check installations of Asterisk before 20.20.1, 21.12.3, 22.10.1, or 23.4.1, and Certified Asterisk before 20.7-cert11 or 22.8-cert3, where chan_ooh323 is installed.