LiveActive security incident?Get immediate response
CVE Record

CVE-2023-20570: Insufficient verification of data authenticity in the configuration state machine may allow a local attacke...

Insufficient verification of data authenticity in the configuration state machine may allow a local attacker to potentially load arbitrary bitstreams.

LowCVSS 3.3Not KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

This is a low-severity AMD FPGA configuration issue. A local, already-authorized attacker might be able to load an arbitrary bitstream, affecting device configuration integrity. The source bundle does not show remote exposure, data theft, service outage, or confirmed active exploitation.

Executive priority

Treat as targeted, low urgency unless these FPGA products support sensitive workloads or untrusted local users. Prioritize inventory and vendor confirmation over emergency response.

Technical view

CVE-2023-20570 is CWE-345: insufficient verification of data authenticity in the configuration state machine. CVSS 3.1 is 3.3 with local access, low attack complexity, low privileges, no user interaction, unchanged scope, and low integrity impact only.

Likely exposure

Exposure is most relevant where AMD Alveo UltraScale/UltraScale+ cards or listed AMD UltraScale/UltraScale+ FPGAs are locally configurable. The affected-status data is incomplete or inconsistent, so confirm applicability against AMD SB-8002.

Exploitation context

No KEV listing or cited source indicates active exploitation. The described attacker must be local and have low privileges. The likely impact is unauthorized bitstream loading, not remote compromise based on the provided evidence.

Researcher notes

Key uncertainty is affected-product status: the bundle lists products and “all” versions while also showing defaultStatus as unaffected. Do not infer exploitability beyond local arbitrary bitstream loading without AMD guidance.

Mitigation direction

  • Review AMD SB-8002 for product-specific guidance and updates.
  • Limit local access to FPGA configuration workflows to trusted administrators.
  • Monitor configuration changes and bitstream loads where telemetry exists.
  • Prioritize any AMD-recommended update if the bulletin names one.

Validation and detection

  • Inventory systems using the listed AMD Alveo and UltraScale FPGA products.
  • Confirm product applicability against AMD SB-8002 and CVE records.
  • Map which users can initiate FPGA configuration or bitstream loading.
  • Check monitoring records for unexpected configuration changes.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-345: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-20570 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Low
CVSS
3.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
3.3CVSS 3.1LowCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N1.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

3.3Low
CVSS 3.1 vector shape for CVE-2023-20570Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
AMDAlveo™ Card (UltraScale™and UltraScale+™ based)allunaffected
AMDKintex™ UltraScale™ FPGAallunaffected
AMDVirtex™ UltraScale™ FPGAallunaffected
AMDKintex™UltraScale+™ FPGAallunaffected
AMDVirtex™ UltraScale+™FPGAallunaffected
AMDArtix™ UltraScale+™ FPGAallunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-345 · source CWE mapping

Insufficient Verification of Data Authenticity

Insufficient Verification of Data Authenticity represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.