Information disclosure via poisoned return predictions
Published Aug 8, 2023 · Updated Sep 23, 2024
A speculative side channel in affected AMD processors allows local users to read data by poisoning return-address predictions. Crafted prediction training wraps the circular return-address stack, replaces a correct return target, and directs transient execution to an attacker-chosen address. Exploitation requires code execution on the host, address-space knowledge, and control of sufficient registers; speculation remains within the current address space.
Summary
What happened
A speculative side channel in affected AMD processors allows local users to read data by poisoning return-address predictions. Crafted prediction training wraps the circular return-address stack, replaces a correct return target, and directs transient execution to an attacker-chosen address. Exploitation requires code execution on the host, address-space knowledge, and control of sufficient registers; speculation remains within the current address space.
The record
- CVE
- CVE-2023-20569
- Published
- Aug 8, 2023
- Updated
- Sep 23, 2024
- Vendor
- AMD
- Product
- Ryzen 5000 Series Processors with Radeon Graphics
- Classifications
- CWE-203, T1003.008
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 8, 2023CVE publishedPublication date reported by the CVE source.
- Sep 23, 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
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
- Inception research proof of conceptproof of concept · demonstrated
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