Authenticated Windows crash via arbitrary IOCTL address
Published Aug 8, 2023 · Updated Oct 10, 2024
Improper input validation in AMD uProf before 4.1.396 allows local users to crash Windows through a crafted IOCTL request. The IOCTL input-buffer handler accepts an attacker-supplied address without sufficient validation and passes it into driver processing. A local authenticated account that can reach the uProf driver is required, and the documented consequence is a Windows system crash rather than data access or code execution.
Summary
What happened
Improper input validation in AMD uProf before 4.1.396 allows local users to crash Windows through a crafted IOCTL request. The IOCTL input-buffer handler accepts an attacker-supplied address without sufficient validation and passes it into driver processing. A local authenticated account that can reach the uProf driver is required, and the documented consequence is a Windows system crash rather than data access or code execution.
The record
- CVE
- CVE-2023-20561
- Published
- Aug 8, 2023
- Updated
- Oct 10, 2024
- Vendor
- Advanced Micro Devices, Inc.
- Product
- AMD uProf
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 8, 2023CVE publishedPublication date reported by the CVE source.
- Oct 10, 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=various <4.1.396
- Affected versionversion=various <4.1-424
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