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

> Local attackers can execute arbitrary code via a stack-based buffer overflow in Pads when processing long report file names.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Jul 2005
- **Updated:** 8 Aug 2024
- **Also known as:** DEBIAN-CVE-2004-2269, GHSA-h3pw-hrvp-5hmj

## What is CVE-2004-2269?

CVE-2004-2269 is a high-severity memory corruption vulnerability in n/a, published on 19 Jul 2005. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Stack-based buffer overflow in pads.c in Passive Asset Detection System (Pads) might allow local users to execute arbitrary code via a long report file name argument. NOTE: since Pads is not normally installed setuid, this may not be a vulnerability.

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


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

Apply the vendor's patch.

## Is CVE-2004-2269 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2004-2269 is a high-severity memory corruption vulnerability in n/a, published on 19 Jul 2005. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2004-2269 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-2004-2269/ (Markdown: https://insights.sbomify.com/CVE-2004-2269/index.md)
```

## Sources

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

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