# CVE-2024-33223: Privilege escalation in n/a

> Attackers can escalate privileges and execute arbitrary code by sending crafted IOCTL requests to the IOMap64.sys driver in ASUS GPU Tweak II.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 May 2024
- **Updated:** 13 Feb 2025
- **Also known as:** GHSA-r7mm-ccp4-9hc5

## What is CVE-2024-33223?

CVE-2024-33223 is a high-severity vulnerability in n/a, published on 22 May 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue in the component IOMap64.sys of ASUSTeK Computer Inc ASUS GPU TweakII v1.4.5.2 allows attackers to escalate privileges and execute arbitrary code via sending crafted IOCTL requests.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2024-33223 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-33223 is a high-severity vulnerability in n/a, published on 22 May 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-33223 in the wild and no public exploit code.

Affected product: n/a. 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-33223/ (Markdown: https://insights.sbomify.com/CVE-2024-33223/index.md)
```

## Sources

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

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