The cryptocurrency landscape continues to evolve with new security challenges emerging from unexpected places. Recent research has uncovered a critical vulnerability in AMD’s Zen processor microcode that could impact the security of crypto transactions and wallet management systems.
The Exploit Mechanics
Researchers at Google have discovered a fundamental flaw in AMD’s microcode verification process. The vulnerability centers around the use of AES-CMAC (Cipher Message Authentication Code) algorithm for verifying microcode updates. AMD Zen processors use this algorithm to ensure that only signed microcode from the vendor is executed, but the implementation contains a critical weakness.
Each microcode patch includes a 2048-bit RSA public key and signature that the CPU verifies by comparing the hash of this public key to a 128-bit value burned into the CPU during manufacturing. The problem lies in the collision resistance of the AES-CMAC algorithm. When the secret key is known, AES-CMAC fails to provide effective collision resistance, making it possible to generate different public keys that produce the same hash value.
Affected Systems
This vulnerability directly impacts any system running AMD Zen processors that relies on cryptographic security for cryptocurrency operations. This includes:
- Crypto mining operations
- Crypto trading platforms
- Crypto wallet software
- Blockchain node infrastructure
- DeFi protocols
The exploit is particularly concerning because it allows an attacker to create malicious microcode updates that appear legitimate to the CPU. This could enable attackers to compromise the security of systems at the hardware level, potentially bypassing higher-level security measures.
The Mitigation Strategy
AMD has responded to this discovery by replacing the problematic AES-CMAC algorithm with an appropriate cryptographic hash function in their latest microcode updates. Organizations running crypto infrastructure on AMD Zen processors should:
- Update Microcode: Apply the latest microcode updates from AMD that patch this vulnerability
- Monitor Systems: Implement enhanced monitoring for unusual CPU behavior
- Hardware Diversity: Consider diversifying hardware infrastructure to include non-AMD processors
- Multi-Layer Security: Implement additional security measures at the application and network levels
Lessons Learned
This incident highlights several important lessons for the cryptocurrency ecosystem:
- Hardware Security Matters: Cryptographic security doesn’t stop at the application level—hardware integrity is crucial
- Algorithm Selection: The choice of cryptographic algorithms must consider collision resistance and known key scenarios
- Vendor Transparency: Clear communication about security vulnerabilities and fixes is essential
- Defense in Depth: Multiple layers of security are necessary to protect crypto assets
User Action Required
Crypto users and organizations should take immediate action to protect their systems:
- Check if your hardware uses AMD Zen processors
- Apply available microcode updates promptly
- Monitor system performance and security logs for anomalies
- Contact your hardware vendor for specific guidance
- Consider implementing additional security measures for high-value crypto operations
The discovery of this microcode vulnerability serves as a reminder that security in the crypto space requires vigilance at all levels—from the hardware that runs the software to the applications themselves. As crypto adoption grows, so does the sophistication of potential attacks, making comprehensive security practices more important than ever.
Disclaimer: This article is for informational purposes only. Always consult with security professionals before making changes to your crypto infrastructure. The authors and publisher are not responsible for any decisions made based on this information.
per CPU family key means my Zen 2 desktop from 2020 and a brand new Zen 4 chip share the same attack surface. AMD needs to disclose which silicon revs got fresh keys
fw_update_chaos_ at least Intel gave us per chip microcode keys after Spectre. AMD using a family wide AES CMAC key in 2024 is indefensible
Google found this and AMD still took 4 months to coordinate disclosure. how many three letter agencies already knew
15% bios update rate among crypto users running AMD Zen. your hardware wallet is useless if the host CPU is running forged microcode
AES-CMAC collision attack on microcode signing is genuinely terrifying. if you can forge a valid patch you basically own the CPU at the lowest possible level
silicon_ghost_ right, and the worst part is microcode updates flash on every boot. you would never even know a malicious patch ran transiently
google finding this is a reminder that nation state level threat actors have probably known about AES-CMAC weaknesses for years. the public disclosure is always lagging
running a btc node on AMD zen hardware right now. not great timing for this disclosure. patching microcode requires a bios update that most people never install
bios updates for microcode patches have like a 15% install rate among regular users. the disclosure is good but the actual fix wont reach most affected machines
15% BIOS update rate is generous. half the AMD laptops running crypto wallets will never see a microcode patch. hardware persistence means this lives forever
the key is per CPU family not per chip, so one leak compromises millions of processors. this is worse than Intel ME ever was and nobody talks about it
Pavel J. per CPU family not per chip is the worst detail here. one leaked AES-CMAC key and every Zen 1 through Zen 4 processor in the wild is compromised simultaneously. no recall possible
Pavel J. per CPU family not per chip means one leaked key compromises millions of Zens. thats worse than anything Intel ever shipped
sigverify_ 15% bios update install rate is generous. among crypto users running nodes in datacenters maybe higher, but consumer wallets on AMD laptops are basically sitting ducks
AES-CMAC collision weakness means someone who knows the key can forge microcode updates. if that key leaks its game over for every Zen CPU ever shipped
aes-cmac collision when the key is known is like putting a padlock on a glass door. google security team keeps finding wild stuff in silicon
kepler_42 AES-CMAC collision with known key is putting a padlock on a glass door. google finding this in production silicon is wild
kepler the padlock analogy is perfect. aes-cmac with a known secret key means you can forge valid microcode signatures. hardware level persistence is a nightmare to detect
hardware level persistence is the scariest phrase in infosec. once compromised microcode is loaded its game over. no software fix can detect it
the 2048-bit RSA key part is what gets me. even with strong keys, if the hash comparison itself is broken, the whole chain falls apart
kepler_42 the forged microcode persists below the OS layer. reinstalling your OS, swapping drives, none of it matters if the CPU microcode is compromised. hardware root of trust is everything
anyone running a node or validator on AMD Zen hardware should be paying attention to this. wallet ops on compromised silicon is a nightmare scenario
Google researchers finding an AES-CMAC collision weakness in AMD microcode verification is terrifying for anyone running wallet software on Zen chips. your hardware wallet doesnt help if the host CPU is compromised
silicon_ghost_ exactly. your trezor or ledger does cold storage but if the PC you use to sign transactions has compromised AMD microcode, the private key gets exfiltrated before it ever reaches the hardware wallet
the 128-bit hash burned into the CPU at manufacturing sounds secure until you realize AES-CMAC collision resistance fails completely when the secret key is known. fundamental crypto design flaw