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

> A stack buffer overflow in the InsydeH2O SetupUtility driver allows attackers to execute arbitrary code and modify UEFI variables on Intel platforms.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Nov 2022
- **Updated:** 29 Apr 2025
- **Also known as:** GHSA-mm4m-cr9x-9m5h

## What is CVE-2022-35407?

CVE-2022-35407 is a high-severity memory corruption vulnerability in n/a, published on 22 Nov 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue was discovered in Insyde InsydeH2O with kernel 5.0 through 5.5. A stack buffer overflow leads to arbitrary code execution in the SetupUtility driver on Intel platforms. An attacker can change the values of certain UEFI variables. If the size of the second variable exceeds the size of the first, then the buffer will be overwritten. This issue affects the SetupUtility driver of InsydeH2O.

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

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

It affects 1 product.


Products: Insyde Kernel.

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

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

## Is CVE-2022-35407 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-36337](https://insights.sbomify.com/CVE-2022-36337/): Memory corruption in n/a (high 8.2)
- [CVE-2022-29275](https://insights.sbomify.com/CVE-2022-29275/): Privilege escalation in n/a (high 8.2)
- [CVE-2022-29276](https://insights.sbomify.com/CVE-2022-29276/): Memory corruption in n/a (high 8.2)
- [CVE-2022-29278](https://insights.sbomify.com/CVE-2022-29278/): Memory corruption in n/a (high 8.2)
- [CVE-2022-29279](https://insights.sbomify.com/CVE-2022-29279/): Memory corruption in n/a (high 8.2)

## Fix prompt for AI coding agents

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

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

## Sources

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

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