Skip to content
Fencer Intel
medium 5.0

CVE-2012-5643 json

Multiple memory leaks in tools/cachemgr.cc in cachemgr.cgi in Squid 2.x and 3.x before 3.1.22, 3.2.x before 3.2.4, and 3.3.x before 3.3.0.2…

published 2012-12-20 13 y ago modified 2026-06-16 4 mo ago also EUVD-2012-5527

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

Summary

Multiple memory leaks in tools/cachemgr.cc in cachemgr.cgi in Squid 2.x and 3.x before 3.1.22, 3.2.x before 3.2.4, and 3.3.x before 3.3.0.2 allow remote attackers to cause a denial of service (memory consumption) via (1) invalid Content-Length headers, (2) long POST requests, or (3) crafted authentication credentials.

Patch / fix

  • squid Debian 14, Debian 13, Debian 12 2.7.STABLE9-2

debian advisories DEBIAN-CVE-2012-5643

  • squid RHEL 6 7:3.1.10-16.el6

red hat advisories RHSA-2013:0505

  • squid3 SLES for SAP 11 SP4, SLES 11 SP4 3.1.23-8.16.30.1

suse advisories SUSE-SU-2016:2089-1

  • squid openSUSE Tumbleweed 3.5.22-1.1

opensuse advisories openSUSE-SU-2024:10307-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-2012-5643 updated cvss 5.0

squid: cachemgr.cgi memory usage DoS and memory leaks

  • Red Hat Enterprise Linux 5 squid
    affected: no fix planned “Will not fix”
  • Red Hat Enterprise Linux Server (v. 6) squid 3.1.10-16.el6 Red Hat Enterprise Linux Workstation (v. 6) squid 3.1.10-16.el6
    fixed: vendor fix RHSA-2013:0505

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

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

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
  • CWE-20 Improper Input Validation

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.