# CVE-2020-12304: Privilege escalation in Intel(R) DAL SDK

> An authenticated local user can escalate privileges due to improper access control in the Intel DAL SDK installer.

- **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:** 12 Nov 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-m9pv-hc8w-j7pf

## What is CVE-2020-12304?

CVE-2020-12304 is a high-severity vulnerability in Intel(R) DAL SDK, published on 12 Nov 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper access control in Installer for Intel(R) DAL SDK before version 2.1 for Windows may allow an authenticated user to potentially enable escalation of privileges via local access.

## Which versions are affected by CVE-2020-12304?

It affects 1 product.


Products: Intel Dynamic Application Loader Software Developement Kit.

## How do I fix CVE-2020-12304?

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

## Is CVE-2020-12304 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-12304 and fix it if it is affected.

What it is: CVE-2020-12304 is a high-severity vulnerability in Intel(R) DAL SDK, published on 12 Nov 2020. 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-2020-12304 in the wild and no public exploit code.

Affected product: Intel(R) DAL SDK. 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-2020-12304/ (Markdown: https://insights.sbomify.com/CVE-2020-12304/index.md)
```

## Sources

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

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