Guest integrity loss via incorrect Secure TSC
Published Feb 13, 2024 · Updated Mar 17, 2025
Incorrect calculation in AMD SEV firmware on affected EPYC processors allows remote authenticated users to compromise guest integrity. Secure_TSC supplies an incorrect time-stamp counter value to a guest when enabled; AMD has not published the underlying calculation error. Exploitation requires high privileges and Secure TSC configuration, and the reported consequence is limited to loss of guest integrity.
Summary
What happened
Incorrect calculation in AMD SEV firmware on affected EPYC processors allows remote authenticated users to compromise guest integrity. Secure_TSC supplies an incorrect time-stamp counter value to a guest when enabled; AMD has not published the underlying calculation error. Exploitation requires high privileges and Secure TSC configuration, and the reported consequence is limited to loss of guest integrity.
The record
- CVE
- CVE-2023-31347
- Published
- Feb 13, 2024
- Updated
- Mar 17, 2025
- Vendor
- Advanced Micro Devices, Inc.
- Product
- AMD EPYC 4th Gen Processors
- Classifications
- CWE-682, T1565.003
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Feb 13, 2024CVE publishedPublication date reported by the CVE source.
- Mar 17, 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.
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