Asterisk data exposure via LDAP filter injection in SIP usernames
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, the LDAP realtime driver `res_config_ldap` may permit `LDAP filter injection` through a `SIP username`, allowing an unauthenticated attacker to make arbitrary LDAP queries using carefully crafted SIP packets and disclose information. The `res_config_ldap` module must be loaded and configured to access an LDAP server, which is not the default. 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
The Asterisk LDAP realtime driver may allow LDAP filter injection through a SIP username. An unauthenticated attacker can send crafted SIP packets to make arbitrary LDAP queries and disclose information, but only when res_config_ldap is loaded and configured to access an LDAP server; this is not the default.
Operators of Asterisk versions before 20.20.1, 21.12.3, 22.10.1, or 23.4.1, and Certified Asterisk versions before 20.7-cert11 or 22.8-cert3, should check whether they use res_config_ldap.