# CVE-2021-33118: Privilege escalation in Intel(R) Serial IO driver for Intel(R) NUC 11 Gen

> An authenticated local user can escalate privileges via improper access control in the Intel Serial IO driver installer for Intel NUC 11 Gen.

- **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:** 17 Nov 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-f2fj-cj3g-rj2x

## What is CVE-2021-33118?

CVE-2021-33118 is a high-severity vulnerability in Intel(R) Serial IO driver for Intel(R) NUC 11 Gen, published on 17 Nov 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper access control in the software installer for the Intel(R) Serial IO driver for Intel(R) NUC 11 Gen before version 30.100.2104.1 may allow an authenticated user to potentially enable escalation of privilege via local access.

## Which versions are affected by CVE-2021-33118?

It affects 1 product.


Products: Intel Serial Io Driver for Intel Nuc 11 Gen.

## How do I fix CVE-2021-33118?

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

## Is CVE-2021-33118 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-33118 and fix it if it is affected.

What it is: CVE-2021-33118 is a high-severity vulnerability in Intel(R) Serial IO driver for Intel(R) NUC 11 Gen, published on 17 Nov 2021. 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-2021-33118 in the wild and no public exploit code.

Affected product: Intel(R) Serial IO driver for Intel(R) NUC 11 Gen. 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-2021-33118/ (Markdown: https://insights.sbomify.com/CVE-2021-33118/index.md)
```

## Sources

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

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