The Latest Vulnerability in AMD Zen 5 Processors: Risks for Banking Infrastructure and How to Protect Yourself

In a recent development that raises serious concerns for the banking sector and organizations using servers powered by AMD processors, a critical vulnerability has been identified as CVE-2024-36347. This flaw, which affects the latest generation of AMD Zen 5 processors, could allow unauthorized microcode injection into the CPU, exposing systems to advanced security risks.

What is CVE-2024-36347?

The vulnerability stems from a weak implementation of the AES-CMAC hashing algorithm, which is used in the microcode signature verification process. In practice, this can allow an attacker with elevated privileges (kernel-level access) to load modified microcode into the CPU. Although the unauthorized microcode does not persist after a system reboot, the risk remains high in scenarios where attackers gain such access, especially via insecure kernel drivers.

Which devices are affected?

The vulnerability impacts the entire line of Zen 5 processors, including:

  • Granite Ridge

  • Turin (EPYC 9005)

  • Strix Point

  • Kraken Point

  • Strix Halo

Notably, the EPYC 9005 (Turin) processors are widely used in data centers and servers that support financial and banking systems, due to advanced features like SEV and SEV-SNP (capabilities for VM isolation and encryption).

How to protect yourself?

AMD has released a firmware update, AGESA 1.2.0.3C, that addresses this vulnerability. Major motherboard manufacturers, such as MSI and others, have started distributing BIOS updates that include this firmware version.

For organizations—especially banks—it is recommended to:

  1. Verify if their servers and systems are using AMD Zen 5 processors.

  2. Immediately apply BIOS updates that contain AGESA 1.2.0.3C.

  3. Conduct audits of kernel drivers to identify insecure components.

  4. Continuously monitor systems for abnormal behavior that could indicate microcode injection attempts.

Why is this critical for banks?

Banks and financial institutions rely on highly secure infrastructure to protect sensitive data and transactions. A compromise at the CPU level could have severe consequences, including leakage of encrypted data, increased risk of hypervisor escape attacks, and failures in the integrity of critical systems.

Conclusion

As technologies advance, so does the threat landscape. CVE-2024-36347 serves as a strong reminder that security must be addressed at all levels—from software to hardware. Applying updates and maintaining continuous monitoring are key to safeguarding banking infrastructure from such threats.

References: AMD Security Bulletin (CVE-2024-36347) National Vulnerability Database (NVD); Motherboard vendor BIOS release notes (MSI, ASUS, Gigabyte)

Comments

Popular posts from this blog

Critical Vulnerability in Veeam Backup & Replication Exposes Enterprises to Remote Code Execution

CISA and ENISA enhance their Cooperation

New Diicot Threat Group Targets SSH Servers with Brute-Force Malware