Key Takeaways
- Security researcher Matt Burch identified nine vulnerabilities in CryptoPro Secure Disk, a full‑disk encryption product used by Diebold Nixdorf’s Vynamic Security Suite.
- The flaws could allow an attacker to force plaintext mounting of the disk, extract encryption keys, and run arbitrary code during the pre‑boot phase of an ATM.
- Diebold Nixdorf disputes the relevance of the findings, stating it does not use BitLocker‑based CryptoPro and that any risk to its ATMs is minimal; however, it acknowledges two of the issues are theoretically applicable under specific conditions and have been patched.
- Even if the impact on Diebold machines is limited, CryptoPro is deployed in over 500,000 licenses across multiple industries, meaning the weaknesses pose a broader risk to Windows‑based fleets that rely on the product for data protection.
- The case highlights a common ATM attack vector: exploiting the less‑protected “head unit” (top) of the machine to inject malware that reaches the XFS middleware and triggers cash‑dispensing jackpotting.
- Organizations using CryptoPro should verify that encryption keys and configuration material are stored separately from the encrypted volume and ensure pre‑boot authentication mechanisms resist tampering.
Overview of the Discovery
At Black Hat USA 2026, Matt Burch, principal security researcher for Atredis Partners, presented nine newly discovered vulnerabilities in CryptoPro Secure Disk (often abbreviated CryptoPro). CryptoPro is a full‑disk encryption (FDE) and pre‑boot authentication solution for Windows that is marketed both to general corporate customers and to ATM manufacturers. While the technical details of the bugs are not contested, the security community is split on whether they translate into a realistic avenue for stealing cash from ATMs. Burch argues that the flaws could enable an attacker to hijack the pre‑boot process, recover decryption keys, and dispense money via a standard jackpotting flow. Diebold Nixdorf, the world’s largest ATM maker, maintains that its devices do not rely on the specific CryptoPro configuration examined by Burch, thereby limiting the practical impact of the findings.
CryptoPro Secure Disk and Its Role
CryptoPro Secure Disk provides hardware‑independent encryption for Windows drives, handling key management, pre‑boot authentication, and integration with technologies such as BitLocker and Trusted Platform Module (TPM). In the context of ATMs, Diebold incorporates CryptoPro as the hard‑disk encryption (HDE) component of its Vynamic Security Suite (VSS). The product is advertised as having been licensed more than 500,000 times across five continents and twenty industries, indicating a sizable installed base beyond the ATM sector. Because CryptoPro sits beneath the operating system, any weakness that compromises its pre‑boot state can give an attacker persistent control before Windows even loads, a privileged position that is highly valuable for malware deployment.
Physical ATM Attack Surface
ATMs are mechanically divided into a heavily reinforced lower vault that stores cash and a lighter “head unit” that houses the PC, networking gear, and peripherals. The vault’s steel construction makes direct cash extraction difficult, whereas the head unit is often built with lower‑grade steel or even plastic, and its locking mechanism is actuated by a simple cable‑driven solenoid. By damaging the casing or inserting tools, an attacker can expose internal cables and gain physical access to the motherboard and storage drives. Once inside, the attacker can bypass the BIOS/UEFI, inject malicious code, or manipulate the boot sequence—steps that are far easier than trying to crack the vault itself. This architectural weakness underpins many jackpotting attacks, where malware targets the XFS (extensions for financial services) middleware that drives cash dispensers.
Technical Details of the Nine Vulnerabilities
Burch’s analysis revealed several interrelated issues:
- Fail‑open decryption – When CryptoPro encounters a decryption error during pre‑boot, it defaults to mounting the volume in plaintext rather than halting the boot process.
- Superficial LUKS check – The product relies on a weak heuristic to detect LUKS‑encrypted disks, allowing an attacker to craft a disk that appears encrypted and trigger the plaintext mount.
- Key material stored on disk – Encryption keys and configuration values are saved alongside the encrypted data, making them recoverable once the disk is mounted in plaintext.
- Insecure Secure Boot configuration – The Secure Boot implementation permits loading of unsigned or arbitrary Linux kernels, enabling an attacker to replace the trusted pre‑boot environment.
- Lack of integrity verification for bootloaders – No cryptographic signatures are enforced on the bootloader, facilitating substitution with a malicious version.
- Weak entropy in key generation – Certain keys are derived from predictable sources, reducing the effort required to brute‑force them.
- Exposed debug interfaces – JTAG and serial ports remain active in production firmware, providing a conduit for code execution.
- Improper handling of TPM seals – TPM‑sealed secrets can be unsealed without proper authorization when the system is in a fail‑open state.
- Insufficient rollback protection – Older, vulnerable firmware versions can be reinstalled without detection, allowing downgrade attacks.
Chaining these flaws, an attacker can force the ATM to boot into a controlled Linux environment, retrieve the CryptoPro keys, decrypt the Windows partition, and deploy jackpotting malware such as Ploutus to command the cash dispenser.
Potential Impact on Cash Theft
If successfully exploited, the attack chain enables a thief to dispense cash without needing to physically breach the vault. The attacker merely needs brief physical access to the head unit—achievable through panel removal, cable tampering, or even social engineering of service personnel. Once the malware is installed, it can trigger the XFS interface to dispense notes, mimicking legitimate withdrawal transactions. Historical data shows a rising trend in jackpotting: over 2,000 incidents reported to the FBI since 2020, with more than 700 occurring in 2025 alone, resulting in roughly $20 million stolen. The vulnerabilities Burch uncovered could lower the barrier to entry for such attacks, especially if attackers can automate the process using readily available hardware tools.
Diebold Nixdorf’s Position and Rebuttal
Diebold Nixdorf’s senior director of corporate communications, Mike Jacobsen, told Dark Reading that the company does not use BitLocker‑based CryptoPro Secure Disk in its ATMs, and therefore the findings are not directly applicable. He acknowledged, however, that Diebold’s Vynamic Security Suite does incorporate “some components of CryptoPro” for its hard‑disk encryption feature. When pressed for specifics, Jacobsen declined to elaborate, though Burch speculates that Diebold may rely on an alternative cryptographic module within CryptoPro rather than the BitLocker‑linked path examined. Diebold’s internal assessment, conducted with CryptoPro’s developers, concluded that the vulnerabilities pose “little to no additional risk” in real‑world ATM deployments, although it admitted that two of the nine issues are theoretically applicable under certain conditions and have been addressed in a December 2025 firmware update.
Response from CryptoPro Vendors and Patch Actions
CryptWare and CPSD, the firms behind CryptoPro, did not respond to Dark Reading’s request for comment. Nevertheless, Diebold’s statement that it worked with the vendors to evaluate the impact suggests that a dialogue occurred behind the scenes. The December 2025 update referenced by Jacobsen likely includes mitigations such as stricter decryption‑failure handling, enhanced LUKS verification, removal of plaintext key storage, hardened Secure Boot policies, and disabled debug interfaces. Whether these patches have been propagated to all CryptoPro licensees—particularly those outside the ATM niche—remains unclear, leaving a potential exposure window for non‑ATM enterprises that rely on the product for data protection.
Broader Implications for Enterprises Using CryptoPro
Beyond ATMs, CryptoPro’s claim of over 500,000 licenses across diverse sectors means that any organization using the product for endpoint or server encryption could be similarly affected if they have not applied the latest mitigations. The core lesson is that encryption must protect not only the data at rest but also the keys and boot process that unlock it. Storing encryption keys on the same medium they protect, relying on superficial integrity checks, and allowing fail‑open behaviors defeat the purpose of full‑disk encryption. Enterprises should audit their CryptoPro deployments, verify that keys are stored in a separate secure element (e.g., TPM or HSM), enforce strict pre‑boot authentication, disable unnecessary debug ports, and ensure that firmware cannot be rolled back to vulnerable versions. Additionally, monitoring for anomalous boot behavior—such as unexpected Linux kernels or plaintext mounts—can help detect early signs of compromise.
Conclusion
The disclosure of nine vulnerabilities in CryptoPro Secure Disk highlights a classic tension between theoretical risk and real‑world exploitability. While Diebold Nixdorf downplays the immediate danger to its ATMs, the technical feasibility of chaining the flaws to achieve pre‑boot code execution, key recovery, and subsequent jackpotting is demonstrable. The broader concern lies in the product’s widespread adoption across industries; any lapse in applying mitigations could expose a substantial number of Windows‑based systems to similar attacks. Organizations must treat encryption holistically, safeguarding keys, boot integrity, and firmware against tampering, lest the very mechanisms meant to protect data become the avenue for theft. The incident underscores the importance of continuous security scrutiny, timely patching, and defense‑in‑depth strategies—especially for devices like ATMs where the physical and cyber domains intersect.