CVE-2023-27478: libmemcached-awesome - Previously Requested Key Data Leakage
Summary
CVE-2023-27478: Disclosure of unrelated data in libmemcached-awesome. Affects libmemcached versions >= 1.0.18, < 1.1.4. Fixed in 1.1.4. How to fix ↓
Also tracked for
- memcached · Bitnami
- libmemcached · Debian:12
The same CVE-2023-27478 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
libmemcached-awesome is an open source C/C++ client library and tools for the memcached server. It provides a convenient interface for interacting with the memcached server, allowing users to store and retrieve data efficiently. However, a vulnerability has been discovered in libmemcached versions prior to 1.1.4 that could lead to data leakage. This vulnerability arises when a previous request times out due to a low POLL_TIMEOUT, and libmemcached returns data for that previously requested key. This issue can have serious implications for the confidentiality and integrity of the data stored in memcached.
Vulnerability Detail
The vulnerability in libmemcached-awesome allows an attacker to obtain data for a previously requested key if the previous request timed out due to a low POLL_TIMEOUT. This means that an attacker could potentially access sensitive information that was intended for another user or session. The impact of this vulnerability depends on the nature of the data stored in memcached and the sensitivity of that data. It is important to note that this vulnerability has been addressed in version 1.1.4 of libmemcached, and users are strongly advised to upgrade to this version to mitigate the risk.
How To Fix
Minimum fixed version
1.1.4
This is the first release that contains the fix.
Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
There are several ways to lower the probability of this vulnerability affecting a deployment:
- Use a reasonably high POLL_TIMEOUT setting, such as the default value.
- Use separate libmemcached connections for unrelated data.
- Do not re-use libmemcached connections in an unknown state.
These workarounds can help reduce the likelihood of a timeout occurring and minimize the impact of the vulnerability. However, upgrading to version 1.1.4 is still the recommended solution.
Conclusion
In conclusion, the libmemcached-awesome library is vulnerable to a data leakage issue when a previous request times out due to a low POLL_TIMEOUT. This vulnerability can lead to unauthorized access to sensitive information stored in memcached. Users are strongly advised to upgrade to version 1.1.4 of libmemcached to mitigate the risk. Additionally, implementing the recommended workarounds can further reduce the likelihood of exploitation. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for libmemcached →
FAQ
libmemcached-awesome is an open source C/C++ client library and tools for the memcached server. It provides a convenient interface for interacting with memcached and is widely used in various applications.
The vulnerability occurs when a previous request to libmemcached times out due to a low POLL_TIMEOUT. In such cases, libmemcached may return data for the previously requested key, potentially exposing sensitive information to an attacker.
The impact of this vulnerability depends on the nature of the data stored in memcached and its sensitivity. An attacker could potentially access data intended for another user or session, compromising confidentiality and integrity.
Yes, this vulnerability has been addressed in version 1.1.4 of libmemcached. Users are strongly advised to upgrade to this version to mitigate the risk.
Yes, there are several workarounds that can lower the probability of this vulnerability affecting a deployment. These include using a high POLL_TIMEOUT setting, using separate libmemcached connections for unrelated data, and avoiding re-use of libmemcached connections in an unknown state. However, upgrading to version 1.1.4 is still recommended.
References
Related vulnerabilities
Recent vulnerabilities recorded for libmemcached.
