# CVE-2007-3205: Other in n/a

> Remote attackers can overwrite arbitrary variables via the parse_str function in PHP, Hardened-PHP, and Suhosin, potentially altering application state.

- **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:** 13 Jun 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-9j84-7rq9-w2fq

## What is CVE-2007-3205?

CVE-2007-3205 is a medium-severity vulnerability in Php Php, published on 13 Jun 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The parse_str function in (1) PHP, (2) Hardened-PHP, and (3) Suhosin, when called without a second parameter, might allow remote attackers to overwrite arbitrary variables by specifying variable names and values in the string to be parsed.  NOTE: it is not clear whether this is a design limitation of the function or a bug in PHP, although it is likely to be regarded as a bug in Hardened-PHP and Suhosin.

## Which versions are affected by CVE-2007-3205?

It affects 3 products.


Products: Hardened-Php Project Hardened-Php, Hardened-Php Project Subhosin, Php Php.

## How do I fix CVE-2007-3205?

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

## Is CVE-2007-3205 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-3205 and fix it if it is affected.

What it is: CVE-2007-3205 is a medium-severity vulnerability in Php Php, published on 13 Jun 2007. 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-2007-3205 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-2007-3205/ (Markdown: https://insights.sbomify.com/CVE-2007-3205/index.md)
```

## Sources

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

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