# CVE-2022-23092: Missing bounds check in 9p message handling

> A missing bounds check in lib9p allows a malicious guest kernel to overwrite host memory, potentially leading to code execution within the bhyve process.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 Feb 2024
- **Updated:** 13 Feb 2025
- **Also known as:** GHSA-gvf3-496w-8fm9

## What is CVE-2022-23092?

CVE-2022-23092 is a high-severity memory corruption vulnerability in Freebsd Freebsd, published on 15 Feb 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The implementation of lib9p's handling of RWALK messages was missing a bounds check needed when unpacking the message contents.  The missing check means that the receipt of a specially crafted message will cause lib9p to overwrite unrelated memory.

The bug can be triggered by a malicious bhyve guest kernel to overwrite memory in the bhyve(8) process.  This could potentially lead to user-mode code execution on the host, subject to bhyve's Capsicum sandbox.

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

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

It affects 1 product.


Products: Freebsd Freebsd.

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

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

## Is CVE-2022-23092 being exploited?

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

## Other vulnerabilities in Freebsd Freebsd

- [CVE-2018-17160](https://insights.sbomify.com/CVE-2018-17160/): Memory corruption in FreeBSD (critical 10.0)
- [CVE-2014-3954](https://insights.sbomify.com/CVE-2014-3954/): Memory corruption in n/a (critical 10.0)
- [CVE-2006-4304](https://insights.sbomify.com/CVE-2006-4304/): Memory corruption in n/a (critical 10.0)
- [CVE-2006-0226](https://insights.sbomify.com/CVE-2006-0226/): Integer overflow in n/a (critical 10.0)
- [CVE-2004-0002](https://insights.sbomify.com/CVE-2004-0002/): Denial of service in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-23092 is a high-severity memory corruption vulnerability in Freebsd Freebsd, published on 15 Feb 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-23092 in the wild and no public exploit code.

Affected product: Freebsd Freebsd. 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-23092/ (Markdown: https://insights.sbomify.com/CVE-2022-23092/index.md)
```

## Sources

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

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