# CVE-2011-3205: Memory corruption in n/a

> Remote Gopher servers can trigger a buffer overflow in Squid, causing denial of service or potential code execution via malicious responses.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Sep 2011
- **Updated:** 6 Aug 2024
- **Also known as:** DSA-2304-1, GHSA-xv7f-73w8-27qj, RHSA-2011:1293

## What is CVE-2011-3205?

CVE-2011-3205 is a medium-severity memory corruption vulnerability in Squid-Cache Squid, published on 6 Sep 2011. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

## Which versions are affected by CVE-2011-3205?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `squid` | Red Hat:enterprise_linux:6::server | All versions | 7:3.1.10-1.el6_1.1 |
| `squid-debuginfo` | Red Hat:enterprise_linux:6::server | All versions | 7:3.1.10-1.el6_1.1 |

Products: Squid-Cache Squid.

## How do I fix CVE-2011-3205?

Upgrade to a fixed version.

## Is CVE-2011-3205 being exploited?

There is no known exploitation of CVE-2011-3205 in the wild and no public exploit code.

## Other vulnerabilities in Squid-Cache Squid

- [CVE-2025-62168](https://insights.sbomify.com/CVE-2025-62168/): Squid vulnerable to information disclosure via authentication credential leakage in error handling (critical 10.0)
- [CVE-2025-54574](https://insights.sbomify.com/CVE-2025-54574/): Squid's URN Handling can lead to Buffer Overflow (critical 9.3)
- [CVE-2026-33526](https://insights.sbomify.com/CVE-2026-33526/): Squid vulnerable to Denial of Service in ICP Request handling (critical 9.2)
- [CVE-2026-32748](https://insights.sbomify.com/CVE-2026-32748/): Squid has Denial of Service in ICP Response handling (high 8.7)
- [CVE-2023-50269](https://insights.sbomify.com/CVE-2023-50269/): SQUID-2023:10 Denial of Service in HTTP Request parsing (high 8.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-3205 and fix it if it is affected.

What it is: CVE-2011-3205 is a medium-severity memory corruption vulnerability in Squid-Cache Squid, published on 6 Sep 2011. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2011-3205 in the wild and no public exploit code.

Affected product: Squid-Cache Squid. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2011-3205/ (Markdown: https://insights.sbomify.com/CVE-2011-3205/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2011-3205
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2011-3205
- OSV: https://osv.dev/vulnerability/CVE-2011-3205

---
From sbomify Insights: https://insights.sbomify.com/CVE-2011-3205/
Summaries are generated and may contain mistakes; the official description above is the record.