# CVE-2024-46916: Privilege escalation in n/a

> Attackers can execute code and recover encryption keys by removing critical system files before filesystem mounting in Diebold Nixdorf Vynamic Security Suite.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Aug 2025
- **Updated:** 29 Aug 2025
- **Also known as:** GHSA-x3x4-rx6q-vgjr

## What is CVE-2024-46916?

CVE-2024-46916 is a high-severity vulnerability in n/a, published on 29 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Diebold Nixdorf Vynamic Security Suite through 4.3.0 SR06 contains functionality that allows the removal of critical system files before the filesystem is properly mounted (e.g., leveraging a delete call in /etc/rc.d/init.d/mountfs to remove the /etc/fstab file). This can allow code execution and, in some versions, enable recovery of TPM Disk Encryption keys and decryption of the Windows system partition.

Weakness: CWE-284 (Improper Access Control), CWE-276 (Incorrect Default Permissions), CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2024-46916?

It affects 1 product.


Products: Dieboldnixdorf Vynamic Security Suite.

## How do I fix CVE-2024-46916?

No fix has been published for CVE-2024-46916 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-46916 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-46916 exists.

## Other vulnerabilities in n/a

- [CVE-2024-46917](https://insights.sbomify.com/CVE-2024-46917/): Security feature bypass in n/a (high 8.1)
- [CVE-2023-33206](https://insights.sbomify.com/CVE-2023-33206/): Path traversal in n/a (high 7.5)
- [CVE-2023-24062](https://insights.sbomify.com/CVE-2023-24062/): Security feature bypass in n/a (medium 6.8)
- [CVE-2023-24063](https://insights.sbomify.com/CVE-2023-24063/): Security feature bypass in n/a (medium 6.8)
- [CVE-2023-24064](https://insights.sbomify.com/CVE-2023-24064/): Auth bypass in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-46916 and fix it if it is affected.

What it is: CVE-2024-46916 is a high-severity vulnerability in n/a, published on 29 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-46916 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-46916/ (Markdown: https://insights.sbomify.com/CVE-2024-46916/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-46916
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-46916
- OSV: https://osv.dev/vulnerability/CVE-2024-46916

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-46916/
Summaries are generated and may contain mistakes; the official description above is the record.