# CVE-2005-0596: Denial of service in n/a

> Attackers can crash the PHP daemon by calling readfile on files with sizes that are multiples of the page size.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Mar 2005
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-mg8x-vg6r-cj96

## What is CVE-2005-0596?

CVE-2005-0596 is a low-severity denial of service vulnerability in Php Php, published on 1 Mar 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

PHP 4 (PHP4) allows attackers to cause a denial of service (daemon crash) by using the readfile function on a file whose size is a multiple of the page size.

## Which versions are affected by CVE-2005-0596?

It affects 1 product.


Products: Php Php.

## How do I fix CVE-2005-0596?

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

## Is CVE-2005-0596 being exploited?

There is no known exploitation of CVE-2005-0596 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-2005-0596 and fix it if it is affected.

What it is: CVE-2005-0596 is a low-severity denial of service vulnerability in Php Php, published on 1 Mar 2005. 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-2005-0596 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-2005-0596/ (Markdown: https://insights.sbomify.com/CVE-2005-0596/index.md)
```

## Sources

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

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