Skip to content
Fencer Intel
medium 5.0

CVE-2011-4971 json

Multiple integer signedness errors in the (1) process_bin_sasl_auth, (2) process_bin_complete_sasl_auth, (3) process_bin_update, and (4) pr…

published 2013-12-12 12 y ago modified 2026-06-16 4 mo ago also EUVD-2011-4876

cvss
5.0
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
22.3%
EPSS 22.3% chance of exploitation in 30 days, percentile 97%
public exploits
1
Metasploit

Summary

Multiple integer signedness errors in the (1) process_bin_sasl_auth, (2) process_bin_complete_sasl_auth, (3) process_bin_update, and (4) process_bin_append_prepend functions in Memcached 1.4.5 and earlier allow remote attackers to cause a denial of service (crash) via a large body length value in a packet.

Patch / fix

  • memcached Debian 14, Debian 13, Debian 12 1.4.13-0.3

debian advisories DEBIAN-CVE-2011-4971

  • memcached OpenStack Cloud 6 1.4.39-3.3.1
  • memcached OpenStack Cloud 7, Enterprise Storage 4 1.4.39-3.3.2

suse advisories SUSE-SU-2018:0807-1SUSE-SU-2018:0778-1

  • memcached openSUSE Tumbleweed 1.4.33-1.1

opensuse advisories openSUSE-SU-2024:10021-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2011-4971 updated cvss 3.3

memcached: specially crafted packet segmentation fault

  • Red Hat CloudForms Management Engine 5 memcached Red Hat Enterprise Linux 6 memcached
    affected: no fix planned “Will not fix”
  • Red Hat Enterprise Linux 7 memcached
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

22.32% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

CVSS scores

assigned by version score vector
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:N/A:P

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.