AMD Ryzen 3 3100 Firmware vulnerabilities

38 CVEs affecting AMD Ryzen 3 3100 Firmware, 0 known to be exploited (CISA KEV), with EPSS scores. Latest: CVE-2023-20533, published 2023-11-14.

More from AMD.

Highest priority

Known exploited (CISA KEV) first, then by EPSS exploit probability.

• CVE-2023-20593, published 2023-07-24. Medium severity, CVSS 5.5. EPSS: 5.2% chance of exploitation in the next 30 days. An issue in “Zen 2” CPUs, under specific microarchitectural circumstances, may allow an attacker to potentially access sensitive information.
• CVE-2022-29900, published 2022-07-12. Medium severity, CVSS 6.5. EPSS: 3.9% chance of exploitation in the next 30 days. Mis-trained branch predictions for return instructions may allow arbitrary speculative code execution under certain microarchitecture-dependent conditions.
• CVE-2022-23823, published 2022-06-15. Medium severity, CVSS 6.5. EPSS: 1.2% chance of exploitation in the next 30 days. A potential vulnerability in some AMD processors using frequency scaling may allow an authenticated attacker to execute a timing attack to potentially enable information disclosure.
• CVE-2022-23821, published 2023-11-14. Critical severity, CVSS 9.8. EPSS: 1% chance of exploitation in the next 30 days. Improper access control in System Management Mode (SMM) may allow an attacker to write to SPI ROM potentially leading to arbitrary code execution.
• CVE-2022-23825, published 2022-07-14. Medium severity, CVSS 6.5. EPSS: 0.8% chance of exploitation in the next 30 days. Aliases in the branch predictor may cause some AMD processors to predict the wrong branch type potentially leading to information disclosure.
• CVE-2022-23820, published 2023-11-14. Critical severity, CVSS 9.8. EPSS: 0.7% chance of exploitation in the next 30 days. Failure to validate the AMD SMM communication buffer may allow an attacker to corrupt the SMRAM potentially leading to arbitrary code execution.
• CVE-2022-23824, published 2022-11-09. Medium severity, CVSS 5.5. EPSS: 0.6% chance of exploitation in the next 30 days. IBPB may not prevent return branch predictions from being specified by pre-IBPB branch targets leading to a potential information disclosure.
• CVE-2023-20589, published 2023-08-08. Medium severity, CVSS 6.8. EPSS: 0.6% chance of exploitation in the next 30 days. An attacker with specialized hardware and physical access to an impacted device may be able to perform a voltage fault injection attack resulting in compromise of the ASP secure boot potentially…
• CVE-2021-46774, published 2023-11-14. High severity, CVSS 7.5. EPSS: 0.5% chance of exploitation in the next 30 days. Insufficient DRAM address validation in System Management Unit (SMU) may allow an attacker to read/write from/to an invalid DRAM address, potentially resulting in denial-of-service.
• CVE-2023-20533, published 2023-11-14. High severity, CVSS 7.5. EPSS: 0.5% chance of exploitation in the next 30 days. Insufficient DRAM address validation in System Management Unit (SMU) may allow an attacker to read/write from/to an invalid DRAM address, potentially resulting in denial-of-service.

Latest

• CVE-2023-20597, published 2023-09-20. Medium severity, CVSS 5.5. EPSS: 0.2% chance of exploitation in the next 30 days. Improper initialization of variables in the DXE driver may allow a privileged user to leak sensitive information via local access.
• CVE-2023-20594, published 2023-09-20. Medium severity, CVSS 4.4. EPSS: 0.2% chance of exploitation in the next 30 days. Improper initialization of variables in the DXE driver may allow a privileged user to leak sensitive information via local access.
• CVE-2021-26371, published 2023-05-09. Medium severity, CVSS 5.5. EPSS: 0.2% chance of exploitation in the next 30 days. A compromised or malicious ABL or UApp could send a SHA256 system call to the bootloader, which may result in exposure of ASP memory to userspace, potentially leading to information…
• CVE-2021-26356, published 2023-05-09. High severity, CVSS 7.4. EPSS: 0.4% chance of exploitation in the next 30 days. A TOCTOU in ASP bootloader may allow an attacker to tamper with the SPI ROM following data read to memory potentially resulting in S3 data corruption and information disclosure.