# CVE-2022-37410: Privilege escalation in Intel(R) Thunderbolt driver software

> An authenticated local user can escalate privileges due to improper access control in Intel Thunderbolt driver software.

- **Severity:** High 7.0 (`CVSS:3.1/AV:L/AC:H/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:** 16 May 2024
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-mpcv-8v8m-h3jc

## What is CVE-2022-37410?

CVE-2022-37410 is a high-severity vulnerability in Intel(R) Thunderbolt driver software, published on 16 May 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper access control for some Intel(R) Thunderbolt driver software before version 89 may allow an authenticated user to potentially enable escalation of privilege via local access.

Weakness: CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2022-37410 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-37410 is a high-severity vulnerability in Intel(R) Thunderbolt driver software, published on 16 May 2024. 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-37410 in the wild and no public exploit code.

Affected product: Intel(R) Thunderbolt driver software. 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-37410/ (Markdown: https://insights.sbomify.com/CVE-2022-37410/index.md)
```

## Sources

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

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