# CVE-2012-4001: Server-side request forgery in n/a

> Remote attackers can trigger HTTP requests to arbitrary hosts, including intranet servers, due to improper host name verification in the mod_pagespeed module.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Sep 2012
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-2j72-xfgv-gj26

## What is CVE-2012-4001?

CVE-2012-4001 is a medium-severity server-side request forgery vulnerability in n/a, published on 15 Sep 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The mod_pagespeed module before 0.10.22.6 for the Apache HTTP Server does not properly verify its host name, which allows remote attackers to trigger HTTP requests to arbitrary hosts via unspecified vectors, as demonstrated by requests to intranet servers.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Google Mod Pagespeed.

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

No fix has been published for CVE-2012-4001 yet. Limit exposure of the affected software until one is available.

## Is CVE-2012-4001 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-4360](https://insights.sbomify.com/CVE-2012-4360/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2012-4001 is a medium-severity server-side request forgery vulnerability in n/a, published on 15 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-4001 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-4001/ (Markdown: https://insights.sbomify.com/CVE-2012-4001/index.md)
```

## Sources

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

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