dbcve.org
ProbaseApplication · Dieboldnixdorf

CVE-2020-9062

MEDIUM · 5.3 CVSS v3.1 Published 2020-08-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
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 ProCash 2100xe USB ATMs running Wincor Probase version 1.1.30 do not encrypt, authenticate, or verify the integrity of messages between the CCDM and the host computer, allowing an attacker with physical access to internal ATM components to commit deposit forgery by intercepting and modifying messages to the host computer, such as the amount and value of currency being deposited.

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 · high confidence

The Diebold Nixdorf ProCash 2100xe USB ATMs running Wincor Probase 1.1.30 lack encryption, authentication, and integrity verification on messages between the Cash Deposit Module (CDDM) and the host computer. An attacker with physical access to internal ATM components can intercept and modify deposit messages (amount and currency value), enabling deposit forgery.

MitigationImplement physical security controls to restrict access to internal ATM components, and coordinate with Diebold Nixdorf for a vendor patch that adds encryption, authentication, and message integrity verification to the CCDM-host protocol.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
ProbaseApplication
Affected:= 1.1.30

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
Changed
Confidentiality
None
Integrity
High
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the ATM hardware model
    Locate the ATM terminal and verify the model number on the physical hardware or system inventory. Confirm it is a Diebold Nixdorf ProCash 2100xe.
    Affected if The ATM is NOT a ProCash 2100xe model, as this vulnerability is specific to that hardware.
  2. Check Wincor Probase software installation and version
    Access the ATM terminal or connected management system and query the installed software for Wincor Probase. Verify the exact version number installed.
    Affected if Probase is NOT installed, or the installed version is NOT 1.1.30. The vulnerability applies ONLY to version 1.1.30.
  3. Verify Cash Deposit Module connectivity
    Inspect the ATM internal components or system configuration to determine if a Cash Deposit Module (CDDM) is connected and operational. Check USB device listings or hardware manifests for CDDM presence.
    Affected if No Cash Deposit Module is connected or configured. The vulnerability only applies when the CDDM is present and active.
  4. Inspect CDDM-to-host communication protocol settings
    Examine the communication configuration between the Cash Deposit Module and the host computer. Look for protocol settings, encryption parameters, or authentication flags in the Probase configuration files or management interface.
    Affected if Encryption, authentication, or integrity verification is DISABLED or NOT CONFIGURED on the CDDM-host communication. The vulnerability exists precisely when these security measures are absent.

You are affected if you have a ProCash 2100xe ATM running Wincor Probase version 1.1.30 with an active Cash Deposit Module that lacks encryption, authentication, and message integrity controls on its communication channel.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement physical security controls to restrict access to internal ATM components, and coordinate with Diebold Nixdorf for a vendor patch that adds encryption, authentication, and message integrity verification to the CCDM-host protocol.

Fix this in Probase Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-9062 — 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-2020-9062 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