# CVE-2012-5526: Other in n/a

> Remote attackers can inject arbitrary HTTP headers into responses from Perl applications using the CGI.pm module due to improper newline escaping.

- **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:** Yes
- **Published:** 21 Nov 2012
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2012-5526, DSA-2587-1, GHSA-9x3m-wmpr-vc58

## What is CVE-2012-5526?

CVE-2012-5526 is a medium-severity vulnerability in n/a, published on 21 Nov 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

CGI.pm module before 3.63 for Perl does not properly escape newlines in (1) Set-Cookie or (2) P3P headers, which might allow remote attackers to inject arbitrary headers into responses from applications that use CGI.pm.

Weakness: CWE-16

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

It affects 1 product.


Products: Andy Armstrong Cgi.pm.

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

Upgrade to a fixed version.

## Is CVE-2012-5526 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2010-4411](https://insights.sbomify.com/CVE-2010-4411/): Other in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2012-5526 is a medium-severity vulnerability in n/a, published on 21 Nov 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-5526 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-5526/ (Markdown: https://insights.sbomify.com/CVE-2012-5526/index.md)
```

## Sources

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

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