Skip to content
Fencer Intel
medium 6.8

CVE-2011-3205 json

Buffer overflow in the gopherToHTML function in gopher.cc in the Gopher reply parser in Squid 3.0 before 3.0.STABLE26, 3.1 before 3.1.15, a…

published 2011-09-06 15 y ago modified 2026-06-16 4 mo ago also EUVD-2011-3169

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

Summary

Buffer overflow in the gopherToHTML function in gopher.cc in the Gopher reply parser in Squid 3.0 before 3.0.STABLE26, 3.1 before 3.1.15, and 3.2 before 3.2.0.11 allows remote Gopher servers to cause a denial of service (memory corruption and daemon restart) or possibly have unspecified other impact via a long line in a response. NOTE: This issue exists because of a CVE-2005-0094 regression.

Patch / fix

  • squid RHEL 6 7:3.1.10-1.el6_1.1

red hat advisories RHSA-2011:1293

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

suse advisories SUSE-SU-2016:2089-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-3205 updated cvss 5.4

squid: buffer overflow flaw in Squid's Gopher reply parser (SQUID-2011:3)

  • Red Hat Enterprise Linux Server (v. 6) squid 3.1.10-1.el6_1.1
    fixed: vendor fix RHSA-2011:1293
  • Red Hat Enterprise Linux 4 squid Red Hat Enterprise Linux 5 squid
    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

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

CVSS scores

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

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.