In memcached before 1.6.42, username data for SASL password database authentication has a timing side channel because a loop exits as soon as a valid username is found by sasl_server_userdb_checkpass.
Weakness
Two separate operations in a product require different amounts of time to complete, in a way that is observable to an actor and reveals security-relevant information about the state of the product, such as whether a particular operation was successful or not.
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Memcached | Memcached | * | 1.6.42 (excluding) |
| Memcached | Ubuntu | devel | * |
| Memcached | Ubuntu | jammy | * |
| Memcached | Ubuntu | noble | * |
| Memcached | Ubuntu | questing | * |
| Memcached | Ubuntu | resolute | * |
| Memcached | Ubuntu | upstream | * |
Related Attack Patterns
- https://cwe.mitre.org/data/definitions/462.html
- https://cwe.mitre.org/data/definitions/541.html
- https://cwe.mitre.org/data/definitions/580.html