# CVE-2024-22087: Memory corruption in n/a

> A stack-based buffer overflow in Pico HTTP Server allows remote attackers to execute arbitrary code via a long URI.

- **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:** 5 Jan 2024
- **Updated:** 23 Jan 2026
- **Also known as:** GHSA-m892-r7q3-ww6c

## What is CVE-2024-22087?

CVE-2024-22087 is a critical memory corruption vulnerability in n/a, published on 5 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

route in main.c in Pico HTTP Server in C through f3b69a6 has an sprintf stack-based buffer overflow via a long URI, leading to remote code execution.

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

## Which versions are affected by CVE-2024-22087?

It affects 1 product.


Products: Alekseykurepin Pico Http Server in C.

## How do I fix CVE-2024-22087?

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

## Is CVE-2024-22087 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-22087 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-22087 and fix it if it is affected.

What it is: CVE-2024-22087 is a critical memory corruption vulnerability in n/a, published on 5 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-22087 exists.

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-2024-22087/ (Markdown: https://insights.sbomify.com/CVE-2024-22087/index.md)
```

## Sources

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

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