AMD Alveo Card Configuration State Machine state issue

Summaryinfo

A vulnerability was found in AMD Alveo Card, Kintex UltraScale FPGA, Virtex UltraScale FPGA, KintexUltraScale+ FPGA, Virtex UltraScale+FPGA and Artix UltraScale+ FPGA. It has been rated as problematic. The affected element is an unknown function of the component Configuration State Machine. The manipulation leads to state issue. This vulnerability is traded as CVE-2023-20570. An attack has to be approached locally. There is no exploit available.

Detailsinfo

A vulnerability was found in AMD Alveo Card, Kintex UltraScale FPGA, Virtex UltraScale FPGA, KintexUltraScale+ FPGA, Virtex UltraScale+FPGA and Artix UltraScale+ FPGA and classified as problematic. This issue affects an unknown function of the component Configuration State Machine. The manipulation with an unknown input leads to a state issue vulnerability. Using CWE to declare the problem leads to CWE-371. The impact remains unknown. The summary by CVE is:

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

The weakness was shared 02/13/2024. The advisory is shared at amd.com. The identification of this vulnerability is CVE-2023-20570 since 10/27/2022. Neither technical details nor an exploit are publicly available.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• AMD

Name

• Alveo Card
• Artix UltraScale+ FPGA
• KintexUltraScale+ FPGA
• Kintex UltraScale FPGA
• Virtex UltraScale+FPGA
• Virtex UltraScale FPGA

License

• commercial

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion