Описание
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.
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.
Ссылки
- https://nvd.nist.gov/vuln/detail/CVE-2026-47783
- https://github.com/memcached/memcached/commit/d13f282b4bce33a9c33b8a1bbf07f12114160fed
- https://access.redhat.com/errata/RHSA-2026:27842
- https://access.redhat.com/errata/RHSA-2026:27862
- https://access.redhat.com/security/cve/CVE-2026-47783
- https://bugzilla.redhat.com/show_bug.cgi?id=2480089
- https://github.com/memcached/memcached/compare/1.6.41...1.6.42
- https://github.com/memcached/memcached/wiki/ReleaseNotes1642
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-47783.json
Связанные уязвимости
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.
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.
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.
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.
In memcached before 1.6.42, username data for SASL password database a ...