CVE-2024-36333: A DLL hijacking vulnerability in the AMD Cleanup Utility could allow an attacker to achieve privilege escal...
A DLL hijacking vulnerability in the AMD Cleanup Utility could allow an attacker to achieve privilege escalation potentially resulting in arbitrary code execution.
Security readout for executives and security teams
Plain-English summary
AMD reports a DLL hijacking issue in AMD Cleanup Utility that could let a local attacker raise privileges and run arbitrary code. It is high severity, but the source bundle does not show active exploitation or a public exploit. Exposure is mainly Windows systems where affected AMD cleanup or graphics software is installed.
Executive priority
Treat as a high-priority endpoint hardening and patching item, especially for privileged-user workstations. It is not described as remotely exploitable, but successful abuse could turn limited local access into arbitrary code execution with elevated impact.
Technical view
CVE-2024-36333 is CWE-427, untrusted search path / DLL hijacking, in AMD Cleanup Utility. CVSS 4.0 is 7.0 high: local attack vector, low complexity, low privileges required, and user interaction present, with high confidentiality, integrity, and availability impact on the vulnerable system.
Likely exposure
Organizations are likely exposed on Windows endpoints, workstations, and admin support systems using AMD Cleanup Utility or the listed AMD Radeon Adrenalin and PRO software lines. Evidence is incomplete for exact deployment prevalence, supported platforms, and fixed-versus-affected build boundaries beyond the supplied AMD/CVE entries.
Exploitation context
The provided sources do not claim active exploitation, and KEV status is false. This is a post-access privilege escalation path: an attacker already on the local system with low privileges may be able to abuse DLL loading behavior if conditions and user interaction align.
Researcher notes
The bundle identifies CWE-427 and CVSS 4.0 local privilege escalation characteristics. It does not provide exploit mechanics, proof of exploitation, or detailed fixed build semantics. Researchers should validate exposure through installed AMD utility/software versions and AMD’s bulletin rather than inferring unsupported affected products.
Mitigation direction
Review AMD bulletin AMD-SB-6027 for vendor remediation guidance.
Update affected AMD Cleanup Utility and AMD Software packages per AMD guidance.
Restrict local administrative workflows on systems with AMD utility software installed.
Limit execution of cleanup utilities to trusted paths and trusted administrators.
Prioritize endpoints used by IT, engineering, and privileged users.
Validation and detection
Inventory endpoints for AMD Cleanup Utility and listed AMD Radeon software versions.
Compare installed AMD packages against AMD-SB-6027 and CVE records.
Check whether vulnerable utility versions are present on high-value workstations.
Confirm patch or replacement status through endpoint management reporting.
Review local privilege escalation alerts involving AMD utility execution.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-427: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
2Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-427 · source CWE mapping
Uncontrolled Search Path Element
Uncontrolled Search Path Element represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.