CVE-2024-33223
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA privilege escalation vulnerability exists in the IOMap64.sys kernel driver component of ASUS GPU Tweak II v1.4.5.2. Attackers can send specially crafted IOCTL (I/O Control) requests to the driver to execute arbitrary code with elevated SYSTEM-level privileges.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if ASUS GPU Tweak II is installedOpen Programs and Features (appwiz.cpl) or check for the installation directory under Program Files or Program Files (x86). Look for an entry named ASUS GPU Tweak II.Affected if The software is installed and shows version 1.4.5.2 or an earlier version
-
Locate the IOMap64.sys driver fileCheck for the driver file at C:\Windows\System32\drivers\IOMap64.sys using File Explorer or by running 'dir C:\Windows\System32\drivers\IOMap64.sys' in Command Prompt.Affected if The IOMap64.sys file exists in the drivers directory
-
Determine if the driver is loadedOpen Command Prompt as Administrator and run 'sc query IOMap64' to query the driver service status, or use 'driverquery /v | findstr IOMap64' to check if the driver is loaded.Affected if The driver service exists and shows a status of RUNNING or the driver appears in the loaded drivers list
-
Compare installed version to vulnerable releaseIn Programs and Features, find the ASUS GPU Tweak II entry and note the version column. If the version is 1.4.5.2 or if no version is shown but the software and driver are present, treat it as potentially affected.Affected if The installed version is 1.4.5.2 or the version cannot be determined but the vulnerable software and driver are confirmed present
A system is affected if ASUS GPU Tweak II version 1.4.5.2 is installed and the IOMap64.sys driver file is present, regardless of whether the driver is currently loaded.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate to a patched version of ASUS GPU Tweak II if available; otherwise uninstall the software to remove the vulnerable driver. Deploy application control policies to block execution of unauthorized drivers.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-33223 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-33223 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data