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

> Remote attackers can crash the Apache server by sending multiple X-Forwarded-For headers when the mod_rpaf module is enabled.

- **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:** 5 Sep 2012
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2012-3526, DSA-2532-1, GHSA-9mf9-j4hx-8j6j

## What is CVE-2012-3526?

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

### Official description

The reverse proxy add forward module (mod_rpaf) 0.5 and 0.6 for the Apache HTTP Server allows remote attackers to cause a denial of service (server or application crash) via multiple X-Forwarded-For headers in a request.

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

It affects 1 product.


Products: Thomas Eibner Mod Rpaf.

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

Apply the vendor's patch.

## Is CVE-2012-3526 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2012-3526 is a medium-severity denial of service vulnerability in n/a, published on 5 Sep 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-3526 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-3526/ (Markdown: https://insights.sbomify.com/CVE-2012-3526/index.md)
```

## Sources

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

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