# CVE-2004-1065: Memory corruption in n/a

> Remote attackers can execute arbitrary code by tricking users into opening a malicious image file with a long section name in vulnerable PHP versions.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 22 Dec 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-vhmx-6whg-m8hv

## What is CVE-2004-1065?

CVE-2004-1065 is a critical memory corruption vulnerability in Php Php, published on 22 Dec 2004. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Buffer overflow in the exif_read_data function in PHP before 4.3.10 and PHP 5.x up to 5.0.2 allows remote attackers to execute arbitrary code via a long section name in an image file.

## Which versions are affected by CVE-2004-1065?

It affects 4 products.


Products: Openpkg Openpkg, Php Php, Trustix Secure Linux, Ubuntu Ubuntu Linux.

## How do I fix CVE-2004-1065?

Upgrade to a fixed version.

## Is CVE-2004-1065 being exploited?

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

## Other vulnerabilities in Php Php

- [CVE-2004-1019](https://insights.sbomify.com/CVE-2004-1019/): Deserialization in n/a (critical 10.0)
- [CVE-2004-0413](https://insights.sbomify.com/CVE-2004-0413/): Integer overflow in n/a (critical 10.0)
- [CVE-2002-0985](https://insights.sbomify.com/CVE-2002-0985/): Command injection in n/a (high 7.5)
- [CVE-2004-0957](https://insights.sbomify.com/CVE-2004-0957/): Privilege escalation in n/a (medium 6.8)
- [CVE-2003-0147](https://insights.sbomify.com/CVE-2003-0147/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-1065 and fix it if it is affected.

What it is: CVE-2004-1065 is a critical memory corruption vulnerability in Php Php, published on 22 Dec 2004. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2004-1065 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-2004-1065/ (Markdown: https://insights.sbomify.com/CVE-2004-1065/index.md)
```

## Sources

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

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