CVE-2017-9951
HighSummary
The try_read_command function in memcached before version 1.4.39 allows remote attackers to cause a denial of service (segmentation fault) via a request to add/set a key, which makes a comparison between signed and unsigned int and triggers a heap-based buffer over-read.
Risk Assessment
This vulnerability may lead to service outages of memcached, affecting the availability of applications relying on this service. Attackers can exploit this flaw to disrupt system operations.
Recommendation
It is recommended to upgrade memcached to version 1.4.39 or later to mitigate this vulnerability. Additionally, monitoring and restricting access to the memcached server is advisable.
Other vulnerabilities in memcached
See all- CVE-2016-8706High
An integer overflow in the process_bin_sasl_auth function in Memcached can be exploited to cause heap overflow and lead to remote code execution.
- CVE-2016-8705Critical
Multiple integer overflows in the process_bin_update function in Memcached can be exploited to cause heap overflow and lead to remote code execution.
- CVE-2016-8704Critical
An integer overflow in the process_bin_append_prepend function in Memcached can be exploited to cause heap overflow and lead to remote code execution.
- CVE-2026-47784High
Memcached before version 1.6.42 uses the memcmp function for password comparison in SASL authentication, causing a timing side-channel vulnerability. An attacker can read passwords by measuring response times.
- CVE-2026-47783High
In memcached before version 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.
Original NVD description (English source)
The try_read_command function in memcached.c in memcached before 1.4.39 allows remote attackers to cause a denial of service (segmentation fault) via a request to add/set a key, which makes a comparison between signed and unsigned int and triggers a heap-based buffer over-read. NOTE: this vulnerability exists because of an incomplete fix for CVE-2016-8705.