# CVE-2007-0158: thttpd 2007 has buffer underflow.


- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 27 Dec 2019
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-527h-2vjc-488r

## What is CVE-2007-0158?

CVE-2007-0158 is a critical vulnerability in n/a, published on 27 Dec 2019. 

### Official description

thttpd 2007 has buffer underflow.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2007-0158?

It affects 1 product.


Products: Acme Thttpd.

## How do I fix CVE-2007-0158?

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

## Is CVE-2007-0158 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-4491](https://insights.sbomify.com/CVE-2009-4491/): Code injection in n/a (critical 9.8)
- [CVE-2001-1496](https://insights.sbomify.com/CVE-2001-1496/): Memory corruption in n/a (critical 9.8)
- [CVE-2003-0899](https://insights.sbomify.com/CVE-2003-0899/): Memory corruption in n/a (critical 9.8)
- [CVE-2012-5640](https://insights.sbomify.com/CVE-2012-5640/): Null dereference in thttpd (medium 5.5)
- [CVE-2001-0892](https://insights.sbomify.com/CVE-2001-0892/): Path traversal in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-0158 and fix it if it is affected.

What it is: CVE-2007-0158 is a critical vulnerability in n/a, published on 27 Dec 2019. 
Exploitation: There is no known exploitation of CVE-2007-0158 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-2007-0158/ (Markdown: https://insights.sbomify.com/CVE-2007-0158/index.md)
```

## Sources

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

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