cve.bz

CVE-2023-20523 amd

5.7 mediumEPSS 0.2%

Medium (5.7) in amd. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
TOCTOU in the ASP may allow a physical attacker to write beyond the buffer bounds, potentially leading to a loss of integrity or denial of service.

Severity

CVSS 3.1

5.7 medium
CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:H
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 8th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2025-04-07. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-367 Time-of-check Time-of-use (TOCTOU) Race Condition
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2023-20523 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2023-20523?via=ask-ai-copy and https://cve.bz/cve/CVE-2023-20523?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2023-20523 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
amd:epyc_7h12_firmwarebefore romepi_1.0.0.c
amd:epyc_7f72_firmwarebefore romepi_1.0.0.c
amd:epyc_7f52_firmwarebefore romepi_1.0.0.c
amd:epyc_7f32_firmwarebefore romepi_1.0.0.c
amd:epyc_7742_firmwarebefore romepi_1.0.0.c
amd:epyc_7702p_firmwarebefore romepi_1.0.0.c
amd:epyc_7702_firmwarebefore romepi_1.0.0.c
amd:epyc_7662_firmwarebefore romepi_1.0.0.c
amd:epyc_7642_firmwarebefore romepi_1.0.0.c
amd:epyc_7552_firmwarebefore romepi_1.0.0.c
amd:epyc_7542_firmwarebefore romepi_1.0.0.c
amd:epyc_7532_firmwarebefore romepi_1.0.0.c
amd:epyc_7502p_firmwarebefore romepi_1.0.0.c
amd:epyc_7502_firmwarebefore romepi_1.0.0.c
amd:epyc_7452_firmwarebefore romepi_1.0.0.c
amd:epyc_7402_firmwarebefore romepi_1.0.0.c
amd:epyc_7402p_firmwarebefore romepi_1.0.0.c
amd:epyc_7352_firmwarebefore romepi_1.0.0.c
amd:epyc_7302p_firmwarebefore romepi_1.0.0.c
amd:epyc_7302_firmwarebefore romepi_1.0.0.c
amd:epyc_7282_firmwarebefore romepi_1.0.0.c
amd:epyc_7272_firmwarebefore romepi_1.0.0.c
amd:epyc_7262_firmwarebefore romepi_1.0.0.c
amd:epyc_7252_firmwarebefore romepi_1.0.0.c
amd:epyc_7232p_firmwarebefore romepi_1.0.0.c
amd:epyc_7002_firmwarebefore romepi_1.0.0.c
amd:epyc_7003_firmwarebefore milanpi_1.0.0.5
amd:epyc_72f3_firmwarebefore milanpi_1.0.0.5
amd:epyc_7313_firmwarebefore milanpi_1.0.0.5
amd:epyc_7313p_firmwarebefore milanpi_1.0.0.5
amd:epyc_7343_firmwarebefore milanpi_1.0.0.5
amd:epyc_7373x_firmwarebefore milanpi_1.0.0.5
amd:epyc_73f3_firmwarebefore milanpi_1.0.0.5
amd:epyc_7413_firmwarebefore milanpi_1.0.0.5
amd:epyc_7443_firmwarebefore milanpi_1.0.0.5
amd:epyc_7443p_firmwarebefore milanpi_1.0.0.5
amd:epyc_7453_firmwarebefore milanpi_1.0.0.5
amd:epyc_74f3_firmwarebefore milanpi_1.0.0.5
amd:epyc_7513_firmwarebefore milanpi_1.0.0.5
amd:epyc_7543_firmwarebefore milanpi_1.0.0.5
amd:epyc_7543p_firmwarebefore milanpi_1.0.0.5
amd:epyc_7573x_firmwarebefore milanpi_1.0.0.5
amd:epyc_75f3_firmwarebefore milanpi_1.0.0.5
amd:epyc_7643_firmwarebefore milanpi_1.0.0.5
amd:epyc_7663_firmwarebefore milanpi_1.0.0.5
amd:epyc_7713_firmwarebefore milanpi_1.0.0.5
amd:epyc_7713p_firmwarebefore milanpi_1.0.0.5
amd:epyc_7743_firmwarebefore milanpi_1.0.0.5
amd:epyc_7763_firmwarebefore milanpi_1.0.0.5
amd:epyc_7773x_firmwarebefore milanpi_1.0.0.5

Attack patterns (CAPEC)

  • CAPEC-27 Leveraging Race Conditions via Symbolic Links Likelihood: Medium · Severity: High
  • CAPEC-29 Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON