# CVE-2023-40296: Memory corruption in n/a

> A stack-based buffer overflow in the async-sockets-cpp library allows attackers to execute arbitrary code or cause denial of service via malformed UDP packets.

- **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:** 14 Aug 2023
- **Updated:** 9 Oct 2024
- **Also known as:** GHSA-jjxp-37fv-3j67

## What is CVE-2023-40296?

CVE-2023-40296 is a high-severity memory corruption vulnerability in n/a, published on 14 Aug 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

async-sockets-cpp through 0.3.1 has a stack-based buffer overflow in ReceiveFrom and Receive in udpsocket.hpp when processing malformed UDP packets.

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

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

It affects 1 product.


Products: Eminfedar Async-Sockets-Cpp.

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

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

## Is CVE-2023-40296 being exploited?

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

Public exploit code:

- Proof of Concept for CVE-2023-40296 (github_poc): https://github.com/Halcy0nic/CVE-2023-40296

## Fix prompt for AI coding agents

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

What it is: CVE-2023-40296 is a high-severity memory corruption vulnerability in n/a, published on 14 Aug 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-40296 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-40296/ (Markdown: https://insights.sbomify.com/CVE-2023-40296/index.md)
```

## Sources

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

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