CVE-2020-10126
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 · uneditedNCR SelfServ ATMs running APTRA XFS 05.01.00 do not properly validate softare updates for the bunch note acceptor (BNA), enabling an attacker with physical access to internal ATM components to restart the host computer and execute arbitrary code with SYSTEM privileges because while booting, the update process looks for CAB archives on removable media and executes a specific file without first validating the signature of the CAB archive.
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 confidenceNCR SelfServ ATMs running APTRA XFS 05.01.00 contain a vulnerable BNA (bunch note acceptor) software update mechanism. During system boot, the update process searches for CAB archives on removable media and executes a specific file without validating the cryptographic signature of the archive. An attacker with physical access to internal ATM components can restart the host, insert malicious removable media, and achieve arbitrary code execution with SYSTEM privileges.
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= 05.01.00CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify APTRA XFS versionLocate and inspect the installed version of NCR APTRA XFS software on the ATM system. This is typically found in the application properties, system information, or the software inventory. Use system management tools or check the software's about/version panel.Affected if The installed version is exactly 05.01.00 (the only affected version listed)
-
Confirm BNA module presenceVerify whether the BNA (bunch note acceptor) software module is installed and enabled on the ATM. Check the APTRA XFS module configuration or hardware peripheral settings to see if BNA is listed as an active component.Affected if BNA module is installed and listed as an active peripheral driver
-
Check removable media auto-execution policyInspect the ATM operating system configuration for policies governing automatic execution of files from removable media. Look for settings that allow automatic CAB archive processing or script execution from USB/removable drives during boot.Affected if Auto-execution from removable media is enabled or allowed for CAB files
-
Examine BNA update mechanism configurationReview the BNA software update configuration within the APTRA XFS settings. Look for any parameters controlling the update process, particularly those specifying CAB archive handling and whether signature validation is enabled or mentioned in the configuration.Affected if The update mechanism is configured to accept CAB archives without signature validation or no signature validation flag is present
A system is affected if it runs APTRA XFS version 05.01.00 with the BNA module enabled and the removable media auto-execution update mechanism present and active.
Generated from the published advisory. Verify against your own configuration.
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 dataRestrict physical access to ATM internal components and implement cryptographic signature validation for all BNA software updates before execution to prevent execution of unauthorized CAB archives.
- Consultation8.0 h
- Implementation24.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-10126 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-10126 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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