First published: Mon Jan 14 2013(Updated: )
Description of problem: When run with "-vv", on receipt of a binary-protocol deletion request, memcached prints out the key to be deleted in a way that can lead to a buffer overrun and crash. Version-Release number of selected component (if applicable): 1.4.4, although this currently affects all later versions. How reproducible: Run memcached with "-vv", use memrm to send deletion requests and observe output. Steps to Reproduce: 1. memcached -p 12345 -vv 2>&1 | grep '^Deleting' 2. memrm --servers localhost:12345 --binary ABCDEF xyz 3. Check the output from memcached. Actual results: [jsowden:~] $ memcached -p 2300 -m 64 -c 1024 -r -vv 2>&1 | grep 'Deleting' Deleting ABCDEF Deleting xyzDEF Expected results: [jsowden:~] $ memcached -p 2300 -m 64 -c 1024 -r -vv 2>&1 | grep 'Deleting' Deleting ABCDEF Deleting xyz Additional info: I've opened a bug report upstream: <a href="https://code.google.com/p/memcached/issues/detail?id=306">https://code.google.com/p/memcached/issues/detail?id=306</a>
Affected Software | Affected Version | How to fix |
---|---|---|
Php Memcached | >=1.4.4 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of REDHAT-BUG-895054 is high due to the potential for a buffer overrun leading to service crashes.
To fix REDHAT-BUG-895054, upgrade to the latest version of Memcached that addresses this buffer overrun issue.
Versions of Memcached starting from 1.4.4 are affected by REDHAT-BUG-895054.
The impact of REDHAT-BUG-895054 on your system can include unexpected crashes and service interruptions.
Yes, a patch addressing the issue in REDHAT-BUG-895054 is available for implementation.