Skip to content

Product

AMD Ryzen™ Threadripper™ 3000 Processors vulnerabilities

12 published CVES affecting AMD Ryzen™ Threadripper™ 3000 Processors, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).

Total
12
Critical
0
High
4
Medium
7
Low
1
Unscored
0
CISA KEV
0

Latest AMD Ryzen™ Threadripper™ 3000 Processors CVEs

Newest publication first

  1. MediumCVSS 6.9 EPSS 0.16%

    Insufficient parameter sanitization in AMD Secure Processor (ASP) TEE DrvSys could allow an attacker with local access to the Trusted Execution Environment (TEE) interface or Trusted Application (TA) to cause an out-of-bounds write, potentially resulting in a loss of platform int...

  2. MediumCVSS 4.6 EPSS 0.14%

    Missing Lock Bit Protection in the Northbridge IO (NBIO) could allow a privileged attacker to use an intentionally disabled device as part of a remapping attack potentially impacting data confidentiality, integrity, or availability.

  3. MediumCVSS 6.9 EPSS 0.09%

    Insecure default configuration state of DDR5 memory module by AGESA Bootloader Firmware could allow an attacker with local user privilege to abuse the unprotected PMIC interface to create a permanent denial of service condition or affect the integrity of the memory module.

  4. HighCVSS 7.5 EPSS 0.17%

    Improper input validation for DIMM serial presence detect (SPD) metadata could allow an attacker with physical access, ring0 access on a system with a non-compliant DIMM, or control over the Root of Trust for BIOS update, to bypass SMM isolation potentially resulting in arbitrary...

  5. HighCVSS 7.9 EPSS 0.19%

    Improper register access control in ASP may allow a privileged attacker to perform unauthorized access to ASP’s Crypto Co-Processor (CCP) registers from x86 resulting in potential loss of control of cryptographic key pointer/index leading to loss of integrity or confidentiality.

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.