CVE-2025-34500
Deck Mate 2's firmware update mechanism accepts packages without …
Deck Mate 2's firmware update mechanism accepts packages without cryptographic signature verification, encrypts them with a single hard-coded AES key shared across devices, and uses a truncated HMAC for integrity validation. Attackers with access to the update interface - typically via the unit's USB update port - can craft or modify firmware packages to execute arbitrary code as root, allowing persistent compromise of the device's integrity and deck randomization process. Physical or on-premises access remains the most likely attack path, though network-exposed or telemetry-enabled deployments could theoretically allow remote exploitation if misconfigured. The vendor confirmed that firmware updates have been issued to correct these update-chain weaknesses and that USB update access has been disabled on affected units.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- www.ioactive.com/wp-content/uploads/2025/05/IOActive-card-shuffler-security.pdf
- www.vulncheck.com/advisories/shuffle-master-deck-mate-2-insecure-update-chain
- www.wired.com/story/card-shuffler-hack/
- www.wired.com/story/how-hacked-card-shufflers-allegedly-enabled-a-mob-fueled-poker-scam-th
- nvd.nist.gov/vuln/detail/CVE-2025-34500
- cve.org/CVERecord?id=CVE-2025-34500
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.