Cryptographic key extraction via improper usage control
Published Aug 13, 2024 · Updated Aug 15, 2024
Improper key usage control in the AMD Secure Processor on affected AMD processors allows local users to extract ASP cryptographic keys. The ASP fails to constrain key-material use after arbitrary code execution has already been obtained inside its privileged environment. Exploitation therefore requires local access and preexisting ASP code execution, and exposes cryptographic secrets protecting confidentiality and integrity.
Summary
What happened
Improper key usage control in the AMD Secure Processor on affected AMD processors allows local users to extract ASP cryptographic keys. The ASP fails to constrain key-material use after arbitrary code execution has already been obtained inside its privileged environment. Exploitation therefore requires local access and preexisting ASP code execution, and exposes cryptographic secrets protecting confidentiality and integrity.
The record
- CVE
- CVE-2024-21981
- Published
- Aug 13, 2024
- Updated
- Aug 15, 2024
- Vendor
- Advanced Micro Devices, Inc.
- Product
- AMD Ryzen™ Embedded V1000 Series Processors
- Classifications
- CWE-639, T1552.004
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Aug 13, 2024CVE publishedPublication date reported by the CVE source.
- Aug 15, 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
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