# CVE-2021-0109: Privilege escalation in Intel(R) SOC driver package for STK1A32SC

> An authenticated local user can escalate privileges due to insecure inherited permissions in the Intel SOC driver package.

- **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 Feb 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-r6ch-fqq9-2j8m

## What is CVE-2021-0109?

CVE-2021-0109 is a high-severity vulnerability in Intel(R) SOC driver package for STK1A32SC, published on 17 Feb 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Insecure inherited permissions for the Intel(R) SOC driver package for STK1A32SC before version 604 may allow an authenticated user to potentially enable escalation of privilege via local access.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

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

It affects 1 product.


Products: Intel Compute Stick Stk1a32sc Firmware.

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

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

## Is CVE-2021-0109 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2021-0109 is a high-severity vulnerability in Intel(R) SOC driver package for STK1A32SC, published on 17 Feb 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-0109 in the wild and no public exploit code.

Affected product: Intel(R) SOC driver package for STK1A32SC. 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-0109/ (Markdown: https://insights.sbomify.com/CVE-2021-0109/index.md)
```

## Sources

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

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