# CVE-2022-38934: Memory corruption in n/a

> An attacker can cause arbitrary address reads or crashes in ToaruOS by providing a crafted ELF file to the readelf utility.

- **Severity:** Low 3.3 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 28 Sep 2022
- **Updated:** 21 May 2025
- **Also known as:** GHSA-49x8-xrpp-pg4g

## What is CVE-2022-38934?

CVE-2022-38934 is a low-severity memory corruption vulnerability in n/a, published on 28 Sep 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

readelf in ToaruOS 2.0.1 has some arbitrary address read vulnerabilities when parsing a crafted ELF file.

Weakness: CWE-125 (Out-of-bounds Read)

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

It affects 1 product.


Products: Toaruos Toaruos.

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

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

## Is CVE-2022-38934 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-36710](https://insights.sbomify.com/CVE-2021-36710/): Privilege escalation in n/a (high 8.8)
- [CVE-2022-38932](https://insights.sbomify.com/CVE-2022-38932/): Memory corruption in n/a (high 8.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-38934 is a low-severity memory corruption vulnerability in n/a, published on 28 Sep 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-38934 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-2022-38934/ (Markdown: https://insights.sbomify.com/CVE-2022-38934/index.md)
```

## Sources

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

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