Amd

Epyc 7313p Firmware

96 vulnerabilities found.

Hinweis: Diese Liste kann unvollständig sein. Daten werden ohne Gewähr im Ursprungsformat bereitgestellt.
  • EPSS 0.23%
  • Published 13.08.2024 17:15:19
  • Last modified 13.03.2025 17:15:24

Improper re-initialization of IOMMU during the DRTM event may permit an untrusted platform configuration to persist, allowing an attacker to read or modify hypervisor memory, potentially resulting in loss of confidentiality, integrity, and availabili...

  • EPSS 0.02%
  • Published 13.08.2024 17:15:19
  • Last modified 12.12.2024 20:29:14

IOMMU improperly handles certain special address ranges with invalid device table entries (DTEs), which may allow an attacker with privileges and a compromised Hypervisor to induce DTE faults to bypass RMP checks in SEV-SNP, potentially leading to a ...

  • EPSS 0.05%
  • Published 13.08.2024 17:15:19
  • Last modified 18.03.2025 20:15:17

A TOCTOU (Time-Of-Check-Time-Of-Use) in SMM may allow an attacker with ring0 privileges and access to the BIOS menu or UEFI shell to modify the communications buffer potentially resulting in arbitrary code execution.

  • EPSS 0.05%
  • Published 13.08.2024 17:15:17
  • Last modified 18.03.2025 16:15:12

An out of bounds memory write when processing the AMD PSP1 Configuration Block (APCB) could allow an attacker with access the ability to modify the BIOS image, and the ability to sign the resulting image, to potentially modify the APCB block resultin...

  • EPSS 1.67%
  • Published 05.08.2024 16:15:35
  • Last modified 26.11.2024 19:13:55

Improper restriction of write operations in SNP firmware could allow a malicious hypervisor to potentially overwrite a guest's memory or UMC seed resulting in loss of confidentiality and integrity.

  • EPSS 1.43%
  • Published 05.08.2024 16:15:35
  • Last modified 26.11.2024 19:13:33

Improper input validation in SEV-SNP could allow a malicious hypervisor to read or overwrite guest memory potentially leading to data leakage or data corruption.

  • EPSS 0.93%
  • Published 05.08.2024 16:15:34
  • Last modified 26.11.2024 19:10:21

Improper restriction of write operations in SNP firmware could allow a malicious hypervisor to overwrite a guest's UMC seed potentially allowing reading of memory from a decommissioned guest.

  • EPSS 0.05%
  • Published 13.02.2024 20:15:52
  • Last modified 17.03.2025 18:15:15

Due to a code bug in Secure_TSC, SEV firmware may allow an attacker with high privileges to cause a guest to observe an incorrect TSC when Secure TSC is enabled potentially resulting in a loss of guest integrity.  

  • EPSS 0.04%
  • Published 13.02.2024 20:15:52
  • Last modified 20.03.2025 21:15:19

Failure to initialize memory in SEV Firmware may allow a privileged attacker to access stale data from other guests.

  • EPSS 0.09%
  • Published 11.01.2024 14:15:43
  • Last modified 21.11.2024 07:41:09

A privileged attacker can prevent delivery of debug exceptions to SEV-SNP guests potentially resulting in guests not receiving expected debug information.