# CVE-2024-32044: Privilege escalation in Intel(R) Arc(TM) Pro Graphics for Windows drivers

> An authenticated user can escalate privileges via adjacent access due to improper access control in Intel Arc Pro Graphics drivers.

- **Severity:** Medium 5.4 (`CVSS:4.0/AV:A/AC:H/AT:P/PR:L/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 13 Nov 2024
- **Updated:** 14 Nov 2024
- **Also known as:** GHSA-xhgh-m73w-g9xm

## What is CVE-2024-32044?

CVE-2024-32044 is a medium-severity vulnerability in Intel(R) Arc(TM) Pro Graphics for Windows drivers, published on 13 Nov 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Improper access control for some Intel(R) Arc(TM) Pro Graphics for Windows drivers before version 31.0.101.5319 may allow an authenticated user to potentially enable escalation of privilege via adjacent access.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2024-32044?


## How do I fix CVE-2024-32044?

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

## Is CVE-2024-32044 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-32044 and fix it if it is affected.

What it is: CVE-2024-32044 is a medium-severity vulnerability in Intel(R) Arc(TM) Pro Graphics for Windows drivers, published on 13 Nov 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-32044 in the wild and no public exploit code.

Affected product: Intel(R) Arc(TM) Pro Graphics for Windows drivers. 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-2024-32044/ (Markdown: https://insights.sbomify.com/CVE-2024-32044/index.md)
```

## Sources

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

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