# CVE-2022-36234: Use after free in n/a

> A double free vulnerability in SimpleNetwork TCP Server allows attackers to cause denial of service or execute arbitrary code via crafted TCP 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:** 28 Jul 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-qgc6-g85m-p5fg

## What is CVE-2022-36234?

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

### Official description

SimpleNetwork TCP Server commit 29bc615f0d9910eb2f59aa8dff1f54f0e3af4496 was discovered to contain a double free vulnerability which is exploited via crafted TCP packets.

Weakness: CWE-415 (Double Free)

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

It affects 1 product.


Products: Simplenetwork Project Simplenetwork.

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

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

## Is CVE-2022-36234 being exploited?

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

Public exploit code:

- Proof of concept for CVE-2022-36234 (github_poc): https://github.com/Halcy0nic/CVE-2022-36234

## Fix prompt for AI coding agents

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

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

## Sources

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

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