dbcve.org
Vynamic Security SuiteApplication · Dieboldnixdorf

CVE-2023-33206

MEDIUM · 6.8 CVSS v3.1 Published 2024-08-08
Fix available
A fix is available. Upgrade to 3.3.0sr16 / 4.0.0sr06 or later.
See remediation →
73/100
Remediation priority · Elevated
Public exploit No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Diebold Nixdorf Vynamic Security Suite (VSS) before 3.3.0 SR16, 4.0.0 SR06, 4.1.0 SR04, 4.2.0 SR03, and 4.3.0 SR01 fails to validate symlinks during the Pre-Boot Authorization (PBA) process. This can be exploited by a physical attacker who is able to manipulate the contents of the system's hard disk.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Vynamic Security SuiteApplication
Affected:< 3.3.0sr16>= 4.0.0, < 4.0.0sr06>= 4.1.0, < 4.1.0sr04>= 4.2.0, < 4.2.0sr03>= 4.3.0, < 4.3.0sr01

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Physical
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.3.0sr16 / 4.0.0sr06 / 4.1.0sr04 or later
Fixed in 3.3.0sr164.0.0sr064.1.0sr04
Recommended fix High confidence

Upgrade to 3.3.0sr16 (for v3.x) or 4.0.0sr06/4.1.0sr04/4.2.0sr03 (for v4.x lines) - or latest available version including 4.3.0sr01 and beyond

  1. 1. Identify the currently installed Vynamic Security Suite version by accessing the system management interface or checking the installed package version.
  2. 2. Determine which upgrade path applies based on current version: if on 3.x line, upgrade to 3.3.0sr16; if on 4.0.x, upgrade to 4.0.0sr06; if on 4.1.x, upgrade to 4.1.0sr04; if on 4.2.x, upgrade to 4.2.0sr03.
  3. 3. Obtain the appropriate service release (SR) update package from Diebold Nixdorf official support channels (media.defcon.org or official vendor portal).
  4. 4. Apply the upgrade following Diebold Nixdorf standard software update procedures for Vynamic Security Suite, ensuring proper backup of configuration data first.
  5. 5. After upgrade, verify the new version is correctly installed and the PBA process properly validates symlinks as part of the integrity check.
Caveat Standard service release upgrades typically preserve configuration; verify compatibility with other Vynamic platform components

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-33206 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-33206 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data