CVE-2013-0179: Buffer Overflow

Published 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: https://code.google.com/p/memcached/issues/detail?id=306

Other sources

The processbindelete function in memcached.c in memcached 1.4.4 and other versions before 1.4.17, when running in verbose mode, allows remote attackers to cause a denial of service (segmentation fault) via a request to delete a key, which does not account for the lack of a null terminator in the key and triggers a buffer over-read when printing to stderr.

MITRE

Affected Software

13 affected components
Memcached Memcached=1.4.4
Memcached Memcached=1.4.5
Memcached Memcached=1.4.6
Memcached Memcached=1.4.7
Memcached Memcached=1.4.8
Memcached Memcached=1.4.9
Memcached Memcached=1.4.10
Memcached Memcached=1.4.11
Memcached Memcached=1.4.12
Memcached Memcached=1.4.13
Memcached Memcached=1.4.14
Memcached Memcached=1.4.15
Memcached Memcached=1.4.16

Event History

Jan 14, 2013
Data Sourced
12:10 PM
DescriptionSeverityAffected Software
Jan 13, 2014
CVE Published
via MITRE·09:00 PM
Data Sourced
via MITRE·09:00 PM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2013-0179?

The severity of CVE-2013-0179 is classified as moderate due to the potential for a buffer overrun and crash.

2

How do I fix CVE-2013-0179?

To fix CVE-2013-0179, upgrade to a patched version of Memcached beyond 1.4.16.

3

Which versions are affected by CVE-2013-0179?

CVE-2013-0179 affects Memcached versions 1.4.4 through 1.4.16.

4

What kind of vulnerability is CVE-2013-0179?

CVE-2013-0179 is a buffer overrun vulnerability related to logging binary-protocol deletion requests.

5

What are the potential consequences of CVE-2013-0179?

The potential consequences of CVE-2013-0179 include a denial of service due to application crashes.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203