CVE-2024-36333
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 · uneditedA DLL hijacking vulnerability in the AMD Cleanup Utility could allow an attacker to achieve privilege escalation potentially resulting in arbitrary code execution.
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 DLL hijacking vulnerability exists in the AMD Cleanup Utility where the application insecurely loads Dynamic Link Libraries, potentially from locations writable by lower-privileged users. An attacker with local access could place a malicious DLL in a search path location, causing the elevated-privileged utility to execute arbitrary code upon its next run, achieving privilege escalation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 26.q1< 25.q3.1= 25.20.00.00CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/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.
-
Identify installed AMD Cleanup Utility versionOpen Programs and Features (appwiz.cpl) or the Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall to locate the version of AMD Cleanup UtilityAffected if Version equals 25.20.00.00 exactly
-
Identify installed AMD Radeon Software versionOpen AMD Radeon Software and navigate to Settings > About, or check the version in Programs and Features. The version format appears as XX.q1 or XX.q3.1Affected if Version is earlier than 26.q1 or earlier than 25.q3.1 (for example, 25.q2, 24.x, etc.)
-
Check application directory permissionsRight-click the AMD Cleanup Utility installation folder (typically C:\Program Files\AMD\CIM or C:\Program Files\AMD\Cleanup Utility), select Properties > Security, and verify which users have Write or Modify permissionsAffected if Users without administrative privileges have Write or Modify permissions to the application directory or subfolders
-
Inspect for unauthorized DLLs in application pathsBrowse to the AMD Cleanup Utility installation directory and any subfolders. Look for DLL files that were not part of a known AMD installation, especially DLLs with suspicious names or recent modification datesAffected if Unexpected DLL files exist in the application directory or directories in the DLL search path
The environment is affected if AMD Cleanup Utility version 25.20.00.00 or an AMD Radeon Software version earlier than 25.q3.1 (or 26.q1) is installed AND the application directory is writable by non-administrative users.
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 data25.q3.126.q1
Apply vendor-supplied patches for the AMD Cleanup Utility. As an interim measure, ensure the application directory and system directories are not writable by non-admin users, and verify that no untrusted DLLs exist in the utility's working directories.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.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 $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-36333 — 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-36333 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