Physical code execution via unchecked root directories
Published Aug 8, 2024 · Updated Mar 18, 2025
Improper root-filesystem validation in Diebold Nixdorf Vynamic Security Suite permits physically proximate attackers to execute pre-boot code. The first PBA phase uses an EFI index to hash only selected Linux files, leaving unindexed content and the root directory structure unchecked. Affected releases precede 3.3.0 SR12, 4.0.0 SR04, 4.1.0 SR02, or 4.2.0 SR01; exploitation requires physical hard-disk access.
Summary
What happened
Improper root-filesystem validation in Diebold Nixdorf Vynamic Security Suite permits physically proximate attackers to execute pre-boot code. The first PBA phase uses an EFI index to hash only selected Linux files, leaving unindexed content and the root directory structure unchecked. Affected releases precede 3.3.0 SR12, 4.0.0 SR04, 4.1.0 SR02, or 4.2.0 SR01; exploitation requires physical hard-disk access.
The record
- CVE
- CVE-2023-24062
- Published
- Aug 8, 2024
- Updated
- Mar 18, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-20, T1562.001
- Attack vector
- physical
- Privileges
- Unavailable
Timeline
How it unfolded
- Aug 8, 2024CVE publishedPublication date reported by the CVE source.
- Mar 18, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Where’s the Money: Defeating ATM Disk Encryptionfunctional · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo