ryzen 5 3600 firmware · threatengine.sh

Home/Product/amd ryzen 5 3600 firmware

Product

amd ryzen 5 3600 firmware

36 known vulnerabilities across versions

Vulnerabilities are listed by affected version. Select any CVE for the full briefing and its intelligence graph.

Sort Min CVSS Published since

Insufficient DRAM address validation in System Management Unit (SMU) may allow an attacker to read/write from/to an invalid DRAM a

Improper access control in System Management Mode (SMM) may allow an attacker to write to SPI ROM potentially leading to arbitrary

Failure to validate the AMD SMM communication buffer may allow an attacker to corrupt the SMRAM potentially leading to arbitrary c

Insufficient DRAM address validation in System Management Unit (SMU) may allow an attacker to read/write from/to an invalid DRAM a

An attacker with specialized hardware and physical access to an impacted device may be able to perform a voltage fault injection a

< comboam4_pi_v1_1.0.0.a

Insufficient input validation in CpmDisplayFeatureSmm may allow an attacker to corrupt SMM memory by overwriting an arbitrary bit

An issue in “Zen 2” CPUs, under specific microarchitectural circumstances, may allow an attacker to potentially access sensiti

A compromised or malicious ABL or UApp could send a SHA256 system call to the bootloader, which may result in exposure of ASP memo

A TOCTOU in ASP bootloader may allow an attacker to tamper with the SPI ROM following data read to memory potentially resulting in

Insufficient bounds checking in ASP may allow an attacker to issue a system call from a compromised ABL which may cause arbitrary

< comboam4_v2_pi_1.2.0.6c

Insufficient control flow management in AmdCpmGpioInitSmm may allow a privileged attacker to tamper with the SMM handler potential

< comboam4_v2_pi_1.2.0.6c

Insufficient control flow management in AmdCpmOemSmm may allow a privileged attacker to tamper with the SMM handler potentially le

When SMT is enabled, certain AMD processors may speculatively execute instructions using a target from the sibling thread after an

Failure to validate the integer operand in ASP (AMD Secure Processor) bootloader may allow an attacker to introduce an integer ove

IBPB may not prevent return branch predictions from being specified by pre-IBPB branch targets leading to a potential information

Insufficient verification of missing size check in 'LoadModule' may lead to an out-of-bounds write potentially allowing an attacke

Improper parameters handling in the AMD Secure Processor (ASP) kernel may allow a privileged attacker to elevate their privileges

Improper parameters handling in AMD Secure Processor (ASP) drivers may allow a privileged attacker to elevate their privileges pot

Execution unit scheduler contention may lead to a side channel vulnerability found on AMD CPU microarchitectures codenamed “Zen

Aliases in the branch predictor may cause some AMD processors to predict the wrong branch type potentially leading to information

Mis-trained branch predictions for return instructions may allow arbitrary speculative code execution under certain microarchitect

A potential vulnerability in some AMD processors using frequency scaling may allow an authenticated attacker to execute a timing a

A malicious or compromised UApp or ABL may be used by an attacker to issue a malformed system call to the Stage 2 Bootloader poten

Insufficient check of the process type in Trusted OS (TOS) may allow an attacker with privileges to enable a lesser privileged pro

A malicious or compromised UApp or ABL could potentially change the value that the ASP uses for its reserved DRAM, to one outside

Failure to verify the protocol in SMM may allow an attacker to control the protocol and modify SPI flash resulting in a potential

A malicious or compromised UApp or ABL may be used by an attacker to send a malformed system call to the bootloader, resulting in

An attacker, who gained elevated privileges via some other vulnerability, may be able to read data from Boot ROM resulting in a lo

Insufficient DRAM address validation in System Management Unit (SMU) may result in a DMA (Direct Memory Access) read/write from/to

A bug in AMD CPU’s core logic may allow for an attacker, using specific code from an unprivileged VM, to trigger a CPU core hang

A malicious or compromised UApp or ABL may coerce the bootloader into corrupting arbitrary memory potentially leading to loss of i

Insufficient bound checks in System Management Unit (SMU) PCIe Hot Plug table may result in access/updates from/to invalid address

LFENCE/JMP (mitigation V2-2) may not sufficiently mitigate CVE-2017-5715 on some AMD CPUs.

Some AMD CPUs may transiently execute beyond unconditional direct branches, which may potentially result in data leakage.

Insufficient DRAM address validation in System Management Unit (SMU) may result in a DMA read from invalid DRAM address to SRAM re

Insufficient bounds checking in System Management Unit (SMU) may cause invalid memory accesses/updates that could result in SMU ha

Vulnerabilities
CISA KEV catalog
CWE weaknesses
CAPEC attack patterns
Package vulnerabilities

Threat intelligence
Threat actors
Tools & malware
ATT&CK techniques
IOCs

Detection & defense
Sigma rules
YARA rules
Atomic Red Team tests
D3FEND countermeasures

Compliance
NIST 800-53
ISO 27001:2022
SOC 2 TSC
PCI-DSS v4.0
CIS Controls v8.1

About
All capabilities
Live statistics
Data sources
Privacy policy
Terms of service

threatengine.sh · Open-source threat intelligence platform · 100+ authoritative sources · Every fact traces to its origin