CVE Intelligence
Skip to main content
LOW

CVE-2023-20540

CVE-2023-20540 Vulnerability Analysis & Exploit Intelligence

An observable timing discrepancy in the ASP could allow a privileged attacker to perform a brute-force attack against the hash message authentication code, allowing arbitrary message input, potentially leading to a loss of data integrity.

Published Updated Sources: cvelistV5, AMD

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Unreported

no source claims exploitation

EPSS

0%

chance of exploitation in 30 days

Affects

amd

5 products listed

CVSS base

1.8

LOW

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

None

none · proof-of-concept · active

Automatable

No

can an attacker script all four kill-chain steps

Technical impact

Partial

partial · total control of the vulnerable component

Affected scope

The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.

Vendors (1)

amd

Products (5)

amd ryzen 3000 series desktop processorsamd ryzen 5000 series desktop processorsamd ryzen threadripper 3000 series processorsamd ryzen threadripper pro 3000wx series processorsamd ryzen threadripper pro 5000 wx series processors

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactSource
1.8CVSS 4.0LOW——cvelistV5

Weakness & attack patterns

  • CWE-208

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

  • T1592.002Gather Victim Host Information: Software
  • T1082System Information Discovery

References

1 on the record

Elsewhere on this site

  • amdevery CVE for this vendor
  • CWE-208other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.