Memory corruption or service interruption via ASP input
Published Jan 10, 2023 · Updated Apr 9, 2025
Improper input validation in AMD EPYC 7002 and 7003 ASP firmware allows physically proximate attackers to write unauthorized memory. The ASP accepts insufficiently validated input and permits the memory write; AMD has not disclosed the affected interface or validation rule. Physical access is required, and successful exploitation can corrupt protected state or interrupt service.
Summary
What happened
Improper input validation in AMD EPYC 7002 and 7003 ASP firmware allows physically proximate attackers to write unauthorized memory. The ASP accepts insufficiently validated input and permits the memory write; AMD has not disclosed the affected interface or validation rule. Physical access is required, and successful exploitation can corrupt protected state or interrupt service.
The record
- CVE
- CVE-2021-46767
- Published
- Jan 10, 2023
- Updated
- Apr 9, 2025
- Vendor
- AMD
- Product
- AMD EPYC 7002 Series Processors
- Classifications
- CWE-20
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 10, 2023CVE publishedPublication date reported by the CVE source.
- Apr 9, 2025Record 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?
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