# CVE-2012-3505: Denial of service in n/a

> Remote attackers can cause denial of service in Tinyproxy via hash collision attacks using numerous headers, requiring an upgrade to mitigate.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/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:** 9 Oct 2012
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2012-3505, DSA-2564-1, GHSA-h6wx-vrmp-rrjr, openSUSE-SU-2024:10460-1

## What is CVE-2012-3505?

CVE-2012-3505 is a medium-severity denial of service vulnerability in n/a, published on 9 Oct 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Tinyproxy 1.8.3 and earlier allows remote attackers to cause a denial of service (CPU and memory consumption) via (1) a large number of headers or (2) a large number of forged headers that trigger hash collisions predictably.  bucket.

Weakness: CWE-310

## Which versions are affected by CVE-2012-3505?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `tinyproxy` | openSUSE:Tumbleweed | All versions | 1.8.4-1.8 |

Products: Banu Tinyproxy.

## How do I fix CVE-2012-3505?

Upgrade to a fixed version.

## Is CVE-2012-3505 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2011-1843](https://insights.sbomify.com/CVE-2011-1843/): Integer overflow in conf.c in Tinyproxy before 1.8.3 might allow remote attackers to bypass intended access restrictions in opportunistic ci (medium 6.8)
- [CVE-2011-1499](https://insights.sbomify.com/CVE-2011-1499/): Misconfiguration in n/a (low 2.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-3505 and fix it if it is affected.

What it is: CVE-2012-3505 is a medium-severity denial of service vulnerability in n/a, published on 9 Oct 2012. 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-2012-3505 in the wild and no public exploit code.

Affected product: n/a. 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-2012-3505/ (Markdown: https://insights.sbomify.com/CVE-2012-3505/index.md)
```

## Sources

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

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