Asterisk denial of service in MWI NOTIFY Message-Account parsing
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 unbounded `sscanf` in `res_pjsip_pubsub` when parsing the `MWI NOTIFY` `Message-Account` field may allow an unauthenticated attacker to send a carefully crafted packet that causes a stack buffer overflow and corrupts the underlying transport, permanently disabling all SIP functionality. An Asterisk restart is required to restore full operation. 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 unbounded sscanf in res_pjsip_pubsub can overflow a stack buffer while parsing the Message-Account field of an MWI NOTIFY. An unauthenticated attacker can send a crafted packet that corrupts the underlying transport and permanently disables SIP functionality until Asterisk is restarted. No user interaction is described.
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.