Vynamic Security Suite: Missing Support for Integrity Check
CVE-2024-46917 is a high-severity missing support for integrity check vulnerability in Vynamic Security Suite from Dieboldnixdorf, with a CVSS 3.1 base score of 8.1 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected Vynamic Security Suite versions: 4.3.0sr01 and earlier. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.25% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of Vynamic Security Suite you run against the affected versions below, and install the vendor's latest release.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Dieboldnixdorf | Vynamic Security Suite | 4.3.0sr01 and earlier | Not stated |
Version data comes from NVD's product matching. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- HighSuccess depends on conditions outside the attacker's control.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by CISA (ADP).
Official description
Diebold Nixdorf Vynamic Security Suite through 4.3.0 SR01 does not validate file attributes or the contents of /root during integrity validation. This allows code execution, recovery of TPM Disk Encryption keys, decryption of the Windows system partition, and full control of the Windows OS, e.g., through ~/.profile changes.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Missing Support for Integrity Check
The product uses a transmission protocol that does not include a mechanism for verifying the integrity of the data during transmission, such as a checksum.
How developers prevent this class of flaw
- Add an appropriately sized checksum to the protocol, ensuring that data received may be simply validated before it is parsed and used.
- Ensure that the checksums present in the protocol design are properly implemented and added to each message before it is sent.
More Missing Support for Integrity Check vulnerabilities (CWE-353)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: poc, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Technical write-ups (may include proof of concept)
- atredis.com/blog/2025/8/26/24nrgne4dqbwjxyip7txn8ep6zj057Exploit, Third Party Advisory
Other references
- github.com/emptynebuliNot Applicable
- dieboldnixdorf.com/en-us/banking/portfolio/software/security/Product
Other vulnerabilities in Vynamic Security Suite
- 8.1 High severity
Recent Missing Support for Integrity Check vulnerabilities
- 7.3 High severity
- 7.8 High severity
- 7.6 High severity
Spotted an error? Tell us.