# CVE-2022-38161: Other in n/a

> Attackers can remap NOR flash memory to modify FPGA bitstreams, potentially executing arbitrary code or escalating privileges on affected embedded systems.

- **Severity:** High 7.5 (`CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Aug 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-pc4c-22w8-h8vw

## What is CVE-2022-38161?

CVE-2022-38161 is a high-severity vulnerability in n/a, published on 11 Aug 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Gumstix Overo SBC on the VSKS board through 2022-08-09, as used on the Orlan-10 and other platforms, allows unrestricted remapping of the NOR flash memory containing the bitstream for the FPGA.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Gumstix Overo Sbc.

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

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

## Is CVE-2022-38161 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-38161 is a high-severity vulnerability in n/a, published on 11 Aug 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-38161 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-38161/ (Markdown: https://insights.sbomify.com/CVE-2022-38161/index.md)
```

## Sources

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

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