# CVE-2022-28994: Memory corruption in n/a

> Remote attackers can trigger a buffer overflow in Small HTTP Server via long GET requests, potentially leading to code execution or service disruption.

- **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:** 29 Apr 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-52c4-mqqm-x3xx

## What is CVE-2022-28994?

CVE-2022-28994 is a critical memory corruption vulnerability in n/a, published on 29 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Small HTTP Server version 3.06 suffers from a remote buffer overflow vulnerability via long GET request.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

## Which versions are affected by CVE-2022-28994?

It affects 1 product.


Products: Smallsrv Small Http Server.

## How do I fix CVE-2022-28994?

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

## Is CVE-2022-28994 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-41368](https://insights.sbomify.com/CVE-2025-41368/): Multiple vulnerabilities in Small HTTP server by Smallsrv (high 8.7)
- [CVE-2025-41359](https://insights.sbomify.com/CVE-2025-41359/): Multiple vulnerabilities in Small HTTP server by Smallsrv (high 8.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-28994 and fix it if it is affected.

What it is: CVE-2022-28994 is a critical memory corruption vulnerability in n/a, published on 29 Apr 2022. 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-2022-28994 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-2022-28994/ (Markdown: https://insights.sbomify.com/CVE-2022-28994/index.md)
```

## Sources

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

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