Service interruption via corruptible TEE return address
Published Aug 13, 2024 · Updated Oct 31, 2024
Stack-based buffer overrun in AMD ASP Secure OS TEE allows privileged local attackers with AMD signing keys to interrupt affected systems. The TEE lacks stack-protection mechanisms, allowing signed privileged code to corrupt a return address during a stack overrun. Exploitation requires high privileges and AMD signing keys; successful corruption can stop service on the affected platform.
Summary
What happened
Stack-based buffer overrun in AMD ASP Secure OS TEE allows privileged local attackers with AMD signing keys to interrupt affected systems. The TEE lacks stack-protection mechanisms, allowing signed privileged code to corrupt a return address during a stack overrun. Exploitation requires high privileges and AMD signing keys; successful corruption can stop service on the affected platform.
The record
- CVE
- CVE-2021-46746
- Published
- Aug 13, 2024
- Updated
- Oct 31, 2024
- Vendor
- Advanced Micro Devices, Inc.
- Product
- AMD Ryzen™ 7000 Series Desktop Processors
- Classifications
- CWE-121
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Aug 13, 2024CVE publishedPublication date reported by the CVE source.
- Oct 31, 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=ComboAM5 1.0.8.0
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