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

> Attackers can cause crashes or execute arbitrary code via crafted GZIP archives due to an out-of-bounds write in the LZH decompression component.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **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:** Yes
- **Published:** 19 Sep 2006
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2006-4335, GHSA-fvj4-6gc6-xj65

## What is CVE-2006-4335?

CVE-2006-4335 is a high-severity memory corruption vulnerability in n/a, published on 19 Sep 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

Array index error in the make_table function in unlzh.c in the LZH decompression component in gzip 1.3.5, when running on certain platforms, allows context-dependent attackers to cause a denial of service (crash) and possibly execute arbitrary code via a crafted GZIP archive that triggers an out-of-bounds write, aka a "stack modification vulnerability."

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

It affects 1 product.


Products: Gzip Gzip.

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

Upgrade to a fixed version.

## Is CVE-2006-4335 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-4336](https://insights.sbomify.com/CVE-2006-4336/): Memory corruption in n/a (high 7.5)
- [CVE-2006-4337](https://insights.sbomify.com/CVE-2006-4337/): Memory corruption in n/a (high 7.5)
- [CVE-2006-4334](https://insights.sbomify.com/CVE-2006-4334/): Null dereference in n/a (medium 5.0)
- [CVE-2006-4338](https://insights.sbomify.com/CVE-2006-4338/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-4335 is a high-severity memory corruption vulnerability in n/a, published on 19 Sep 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-4335 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-4335/ (Markdown: https://insights.sbomify.com/CVE-2006-4335/index.md)
```

## Sources

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

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