Privilege escalation via permissive installation-folder ACLs
Published Nov 12, 2024 · Updated Nov 13, 2024
Incorrect permissions in AMD Ryzen Master Monitoring SDK before 2.13.0.2915 allow local users to execute code with elevated privileges. The installation process leaves the SDK folder and its subfolders and files with ACL permissions that do not appropriately restrict lower-privileged accounts. Exploitation requires local low-privilege access and user interaction; successful abuse elevates code execution rather than exposing a network service.
Summary
What happened
Incorrect permissions in AMD Ryzen Master Monitoring SDK before 2.13.0.2915 allow local users to execute code with elevated privileges. The installation process leaves the SDK folder and its subfolders and files with ACL permissions that do not appropriately restrict lower-privileged accounts. Exploitation requires local low-privilege access and user interaction; successful abuse elevates code execution rather than exposing a network service.
The record
- CVE
- CVE-2024-21945
- Published
- Nov 12, 2024
- Updated
- Nov 13, 2024
- Vendor
- Advanced Micro Devices, Inc.
- Product
- AMD Ryzen Master
- Classifications
- CWE-276, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 12, 2024CVE publishedPublication date reported by the CVE source.
- Nov 13, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <2.13.0.2915
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo