Asterisk stack buffer overflow in XMPP namespace prefix 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. 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 attacker may cause a stack buffer overflow in `res_xmpp` `XMPP namespace prefix` handling using carefully crafted packets. The `res_xmpp` module must be loaded, an XMPP connection must be configured in `xmpp.conf`, and the attacker must have an XMPP account on the same or a federated server. 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
Asterisk and Certified Asterisk have a stack buffer overflow in res_xmpp XMPP namespace prefix handling. An attacker with an XMPP account on the same or a federated server can trigger it with crafted packets when res_xmpp is loaded and an XMPP connection is configured in xmpp.conf. No user interaction is described.
Check deployments 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.