Kernel-address disclosure via heap information leak
Published Jun 11, 2021 · Updated Sep 17, 2024
Information disclosure in AMD Radeon Software before 20.7.1 allows local users to obtain kernel pool addresses and bypass KASLR. AMD identifies a heap information leak in its Windows 10 graphics driver but has not disclosed the affected API, code path, or operation that returns kernel pool addresses. The issue also affects Radeon Pro Software for Enterprise before 21.Q1; low-privilege local access is required, and only address-layout data is reported exposed.
Summary
What happened
Information disclosure in AMD Radeon Software before 20.7.1 allows local users to obtain kernel pool addresses and bypass KASLR. AMD identifies a heap information leak in its Windows 10 graphics driver but has not disclosed the affected API, code path, or operation that returns kernel pool addresses. The issue also affects Radeon Pro Software for Enterprise before 21.Q1; low-privilege local access is required, and only address-layout data is reported exposed.
The record
- CVE
- CVE-2020-12987
- Published
- Jun 11, 2021
- Updated
- Sep 17, 2024
- Vendor
- AMD
- Product
- Radeon Software
- Classifications
- CWE-200
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 11, 2021CVE publishedPublication date reported by the CVE source.
- Sep 17, 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=Radeon Pro Software for Enterprise <21.Q2
- Affected versionversion=Radeon Software <20.7.1
What conditions does exploitation require?
What is affected?
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