# CVE-2006-0207: Multiple HTTP response splitting vulnerabilities in PHP 5.1.1 allow remote attackers to inject arbitrary HTTP headers via a crafted Set-Cook


- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 13 Jan 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-6fcg-qj92-43ff

## What is CVE-2006-0207?

CVE-2006-0207 is a medium-severity vulnerability in Php Php, published on 13 Jan 2006. 

### Official description

Multiple HTTP response splitting vulnerabilities in PHP 5.1.1 allow remote attackers to inject arbitrary HTTP headers via a crafted Set-Cookie header, related to the (1) session extension (aka ext/session) and the (2) header function.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2006-0207?

It affects 1 product.


Products: Php Php.

## How do I fix CVE-2006-0207?

Upgrade to a fixed version.

## Is CVE-2006-0207 being exploited?

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

## Other vulnerabilities in Php Php

- [CVE-2012-2688](https://insights.sbomify.com/CVE-2012-2688/): Integer overflow in n/a (critical 10.0)
- [CVE-2012-2376](https://insights.sbomify.com/CVE-2012-2376/): Memory corruption in n/a (critical 10.0)
- [CVE-2011-3268](https://insights.sbomify.com/CVE-2011-3268/): Memory corruption in n/a (critical 10.0)
- [CVE-2009-4143](https://insights.sbomify.com/CVE-2009-4143/): Other in n/a (critical 10.0)
- [CVE-2008-5557](https://insights.sbomify.com/CVE-2008-5557/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-0207 and fix it if it is affected.

What it is: CVE-2006-0207 is a medium-severity vulnerability in Php Php, published on 13 Jan 2006. 
Exploitation: There is no known exploitation of CVE-2006-0207 in the wild and no public exploit code.

Affected product: Php Php. 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-2006-0207/ (Markdown: https://insights.sbomify.com/CVE-2006-0207/index.md)
```

## Sources

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

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