# CVE-2023-52266: Use after free in n/a

> A use-after-free vulnerability in the ehttp library allows attackers to cause denial of service or potentially execute code by triggering rapid connections.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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:** 30 Dec 2023
- **Updated:** 9 Sep 2024
- **Also known as:** GHSA-5fq8-x84x-j269

## What is CVE-2023-52266?

CVE-2023-52266 is a high-severity use after free vulnerability in n/a, published on 30 Dec 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ehttp 1.0.6 before 17405b9 has an epoll_socket.cpp read_func use-after-free. An attacker can make many connections over a short time to trigger this.

Weakness: CWE-416 (Use After Free)

## Which versions are affected by CVE-2023-52266?

It affects 1 product.


Products: Hongliuliao Ehttp.

## How do I fix CVE-2023-52266?

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

## Is CVE-2023-52266 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-52267](https://insights.sbomify.com/CVE-2023-52267/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-52266 and fix it if it is affected.

What it is: CVE-2023-52266 is a high-severity use after free vulnerability in n/a, published on 30 Dec 2023. 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-2023-52266 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-2023-52266/ (Markdown: https://insights.sbomify.com/CVE-2023-52266/index.md)
```

## Sources

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

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