Due to a code bug in Secure_TSC, SEV firmware may allow an attacker with high privileges to cause a guest to observe an incorrect TSC when S
Noroxi assessment
Priority: Monitor (action score 19/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.46% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Due to a code bug in Secure_TSC, SEV firmware may allow an attacker with high privileges to cause a guest to observe an incorrect TSC when Secure TSC is enabled potentially resulting in a loss of guest integrity.
- Published
- Feb 13, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.4% · 38th percentile
- CWE
- CWE-682
Report tools
Action score
19
Monitor
Low priority for now.
- CVSS
- 19 / 40 · 4.9 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| amd | epyc 7773x firmware | cpe:2.3:o:amd:epyc_7773x_firmware |
| amd | epyc 7773x | cpe:2.3:h:amd:epyc_7773x |
| amd | epyc 7763 firmware | cpe:2.3:o:amd:epyc_7763_firmware |
| amd | epyc 7763 | cpe:2.3:h:amd:epyc_7763 |
| amd | epyc 7713 firmware | cpe:2.3:o:amd:epyc_7713_firmware |
| amd | epyc 7713 | cpe:2.3:h:amd:epyc_7713 |
| amd | epyc 7713p firmware | cpe:2.3:o:amd:epyc_7713p_firmware |
| amd | epyc 7713p | cpe:2.3:h:amd:epyc_7713p |
| amd | epyc 7663 firmware | cpe:2.3:o:amd:epyc_7663_firmware |
| amd | epyc 7663 | cpe:2.3:h:amd:epyc_7663 |
| amd | epyc 7663p firmware | cpe:2.3:o:amd:epyc_7663p_firmware |
| amd | epyc 7663p | cpe:2.3:h:amd:epyc_7663p |
and 111 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- amd epyc 7203 firmwarebefore milanpi_1.0.0.c
- amd epyc 7203p firmwarebefore milanpi_1.0.0.c
- amd epyc 72f3 firmwarebefore milanpi_1.0.0.c
- amd epyc 7303 firmwarebefore milanpi_1.0.0.c
- amd epyc 7303p firmwarebefore milanpi_1.0.0.c
- amd epyc 7313 firmwarebefore milanpi_1.0.0.c
- amd epyc 7313p firmwarebefore milanpi_1.0.0.c
- amd epyc 7343 firmwarebefore milanpi_1.0.0.c
- amd epyc 7373x firmwarebefore milanpi_1.0.0.c
- amd epyc 73f3 firmwarebefore milanpi_1.0.0.c
- amd epyc 7413 firmwarebefore milanpi_1.0.0.c
- amd epyc 7443 firmwarebefore milanpi_1.0.0.c
- amd epyc 7443p firmwarebefore milanpi_1.0.0.c
- amd epyc 7453 firmwarebefore milanpi_1.0.0.c
- amd epyc 7473x firmwarebefore milanpi_1.0.0.c
- amd epyc 74f3 firmwarebefore milanpi_1.0.0.c
- amd epyc 7513 firmwarebefore milanpi_1.0.0.c
- amd epyc 7543 firmwarebefore milanpi_1.0.0.c
- amd epyc 7543p firmwarebefore milanpi_1.0.0.c
- amd epyc 7573x firmwarebefore milanpi_1.0.0.c
Versions reported by the vendor
Affected version ranges reported by the assigning authority (AMD). Independent of NVD's CPE analysis and usually ahead of it.
AMD 3rd Gen AMD EPYC™ Processors
- variousaffected
AMD 4th Gen AMD EPYC™ Processors
- variousaffected
Same product
amd: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-31346Failure to initialize
memory in SEV Firmware may allow a privileged attacker to access stale data
from other guests.24Monitor
- CVE-2021-26371A compromised or malicious ABL or UApp could
send a SHA256 system call to the bootloader, which may result in exposure of
ASP memory to user22Monitor
- CVE-2021-26354Insufficient bounds checking in ASP may allow an
attacker to issue a system call from a compromised ABL which may cause
arbitrary memory val22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- Administrator privileges are required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-682 · Incorrect CalculationCVSS vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.