© 2026 vulntracker.io

CVE-2023-31347

MEDIUM

4.9

CVSS Score

Published: February 13, 2024 at 07:18 PM UTC

Updated: June 17, 2026 at 05:56 AM UTC

125 products affected across 1 vendorEpyc 7663 FirmwareEpyc 7713P FirmwareEpyc 7413 Firmware

Using 3rd Gen AMD EPYC™ Processors by AMD?

Get instant alerts when new vulnerabilities affect 3rd Gen AMD EPYC™ Processors - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM4.9

Exploit prediction

EPSS 0.5%

SSVC

No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Epyc 7203 Firmware · AMD

95%

v < milanpi_1.0.0.c

Affected range stops below milanpi_1.0.0.c, so it looks safe — our inference, not a vendor statement

amd-epyc-72f3 (environment)

Epyc 7203P Firmware · AMD

95%

v < milanpi_1.0.0.c

Affected range stops below milanpi_1.0.0.c, so it looks safe — our inference, not a vendor statement

amd-epyc-7203p (same device)

Epyc 72F3 Firmware · AMD

95%

v < milanpi_1.0.0.c

Affected range stops below milanpi_1.0.0.c, so it looks safe — our inference, not a vendor statement

amd-epyc-72f3 (same device)

Epyc 7303 Firmware · AMD

95%

v < milanpi_1.0.0.c

Affected range stops below milanpi_1.0.0.c, so it looks safe — our inference, not a vendor statement

amd-epyc-7303 (same device)

Epyc 7303P Firmware · AMD

95%

v < milanpi_1.0.0.c

Affected range stops below milanpi_1.0.0.c, so it looks safe — our inference, not a vendor statement

amd-epyc-7303p (same device)

Epyc 7313 Firmware · AMD

95%

v < milanpi_1.0.0.c

Affected range stops below milanpi_1.0.0.c, so it looks safe — our inference, not a vendor statement

amd-epyc-7313 (same device)

Epyc 7313P Firmware · AMD

95%

v < milanpi_1.0.0.c

Affected range stops below milanpi_1.0.0.c, so it looks safe — our inference, not a vendor statement

amd-epyc-7313p (same device)

Epyc 7343 Firmware · AMD

95%

v < milanpi_1.0.0.c

Affected range stops below milanpi_1.0.0.c, so it looks safe — our inference, not a vendor statement

amd-epyc-7343 (same device)

Epyc 7373X Firmware · AMD

95%

v < milanpi_1.0.0.c

Affected range stops below milanpi_1.0.0.c, so it looks safe — our inference, not a vendor statement

amd-epyc-7373x (same device)

Epyc 73F3 Firmware · AMD

95%

v < milanpi_1.0.0.c

Affected range stops below milanpi_1.0.0.c, so it looks safe — our inference, not a vendor statement

amd-epyc-73f3 (same device)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

https://www.amd.com/en/corporate/product-security/bulletin/AMD-SB-3007

References (1)

Vendor AdvisoryBroken Link

Source: [email protected]

https://www.amd.com/en/corporate/product-security/bulletin/AMD-SB-3007

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

4.9MEDIUMCISA-ADP

Attack Vector: NETWORK
Complexity: LOW
Privileges: HIGH
User Interaction: NONE
Scope: UNCHANGED
Confidentiality: NONE
Integrity: HIGH
Availability: NONE

Vector?

Quick Info

StatusMODIFIED

CWE

NVD-CWE-noinfoCWE-682

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Create account Sign in

Free plan, no card