# CVE-2006-7205: Denial of service in n/a

> Attackers can cause denial of service via memory consumption in PHP's array_fill function by supplying a large number value.

- **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 stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 May 2007
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-6m79-37j9-r59p

## What is CVE-2006-7205?

CVE-2006-7205 is a medium-severity denial of service vulnerability in n/a, published on 24 May 2007. It can be exploited over the network, with no action from the victim.

### Official description

The array_fill function in ext/standard/array.c in PHP 4.4.2 and 5.1.2 allows context-dependent attackers to cause a denial of service (memory consumption) via a large num value.

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

It affects 1 product.


Products: Php Group Php.

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

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

## Is CVE-2006-7205 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-3016](https://insights.sbomify.com/CVE-2006-3016/): Other in n/a (critical 9.3)
- [CVE-2006-3018](https://insights.sbomify.com/CVE-2006-3018/): Unspecified vulnerability in the session extension functionality in PHP before 5.1.3 has unknown impact and attack vectors related to heap corruption. (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-7205 is a medium-severity denial of service vulnerability in n/a, published on 24 May 2007. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-7205 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-2006-7205/ (Markdown: https://insights.sbomify.com/CVE-2006-7205/index.md)
```

## Sources

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

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