# CVE-2019-20800: Memory corruption in n/a

> Remote attackers can trigger an out-of-bounds write in the Cherokee web server by sending excessive request headers, potentially leading to code execution or crashes.

- **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
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 May 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-jwp6-5rr6-m93v

## What is CVE-2019-20800?

CVE-2019-20800 is a critical memory corruption vulnerability in n/a, published on 17 May 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In Cherokee through 1.2.104, remote attackers can trigger an out-of-bounds write in cherokee_handler_cgi_add_env_pair in handler_cgi.c by sending many request headers, as demonstrated by a GET request with many "Host: 127.0.0.1" headers.

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

## Which versions are affected by CVE-2019-20800?

It affects 1 product.


Products: Cherokee-Project Cherokee.

## How do I fix CVE-2019-20800?

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

## Is CVE-2019-20800 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-20798](https://insights.sbomify.com/CVE-2019-20798/): Cross-site scripting in n/a (high 8.4)
- [CVE-2020-12845](https://insights.sbomify.com/CVE-2020-12845/): Null dereference in n/a (high 7.5)
- [CVE-2019-20799](https://insights.sbomify.com/CVE-2019-20799/): Memory corruption in n/a (high 7.5)
- [CVE-2014-4668](https://insights.sbomify.com/CVE-2014-4668/): Auth bypass in n/a (medium 6.8)
- [CVE-2011-2191](https://insights.sbomify.com/CVE-2011-2191/): Cross-site request forgery in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-20800 and fix it if it is affected.

What it is: CVE-2019-20800 is a critical memory corruption vulnerability in n/a, published on 17 May 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-20800 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-2019-20800/ (Markdown: https://insights.sbomify.com/CVE-2019-20800/index.md)
```

## Sources

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

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