# CVE-2006-1269: Memory corruption in n/a

> Local attackers can execute arbitrary code via buffer overflow in zoo archive utility when processing long filenames during archive creation.

- **Severity:** Medium 6.2 (`AV:L/AC:H/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 19 Mar 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-wmgc-376w-w47j

## What is CVE-2006-1269?

CVE-2006-1269 is a medium-severity memory corruption vulnerability in n/a, published on 19 Mar 2006. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Buffer overflow in the parse function in parse.c in zoo 2.10 might allow local users to execute arbitrary code via long filename command line arguments, which are not properly handled during archive creation.  NOTE: since this issue is local and not setuid, the set of attack scenarios is limited, although is reasonable to expect that there are some situations in which the zoo user might automatically list attacker-controlled filenames to add to the zoo archive.

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

It affects 1 product.


Products: Rahul Dhesi Zoo.

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

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

## Is CVE-2006-1269 being exploited?

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

Public exploit code:

- Zoo 2.10 - Parse.c Local Buffer Overflow (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2006-0855](https://insights.sbomify.com/CVE-2006-0855/): Memory corruption in n/a (medium 5.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-1269 is a medium-severity memory corruption vulnerability in n/a, published on 19 Mar 2006. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2006-1269 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-1269/ (Markdown: https://insights.sbomify.com/CVE-2006-1269/index.md)
```

## Sources

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

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