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

> An off-by-one error in SimpleNetwork allows remote attackers to cause a buffer overflow via crafted TCP packets, potentially leading to code execution or denial of service.

- **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:** 4 May 2024
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-7mmj-92xq-hjg8

## What is CVE-2023-52729?

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

### Official description

TCPServer.cpp in SimpleNetwork through 29bc615 has an off-by-one error that causes a buffer overflow when trying to add '\0' to the end of long msg data. It can be exploited via crafted TCP packets.

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

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


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

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

## Is CVE-2023-52729 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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