LiveActive security incident?Get immediate response
CVE Record

CVE-2020-10125: NCR SelfServ ATMs running APTRA XFS 04.02.01 and 05.01.00 implement 512-bit RSA certificates to validate bu...

NCR SelfServ ATMs running APTRA XFS 04.02.01 and 05.01.00 implement 512-bit RSA certificates to validate bunch note acceptor (BNA) software updates, which can be broken by an attacker with physical access in a sufficiently short period of time, thereby enabling the attacker to sign arbitrary files and CAB archives used to update BNA software, as well as bypass application whitelisting, resulting in the ability to execute arbitrary code.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Some NCR SelfServ ATMs used very weak 512-bit RSA certificates to trust BNA software updates. A person with physical access could potentially forge trusted update files and run unauthorized code. This is a serious operational risk for affected ATM fleets, but the provided sources do not show active exploitation.

Executive priority

Prioritize if your organization operates affected NCR SelfServ ATMs. The business concern is unauthorized code execution on cash-handling infrastructure after physical access, which can create fraud, outage, and incident-response costs. Treat as high priority for fleet inventory and vendor-led remediation.

Technical view

CVE-2020-10125 affects NCR SelfServ ATMs running APTRA XFS 04.02.01 and 05.01.00. The issue is use of insufficient cryptographic strength, CWE-326, in certificates validating BNA software updates. Breaking that trust can allow signing arbitrary files or CAB archives, bypassing application whitelisting, and executing arbitrary code with physical access.

Likely exposure

Exposure appears limited to NCR SelfServ ATMs running APTRA XFS 04.02.01 or 05.01.00 with the described BNA update validation design. The source bundle does not identify other NCR products, later APTRA versions, or remote exposure.

Exploitation context

The cited CVE description requires physical access and enough time to break 512-bit RSA trust material. The source bundle does not include exploit code, observed exploitation, KEV listing, public scanning evidence, or a CVSS score.

Researcher notes

Evidence is concise and centered on weak cryptographic trust for BNA updates. The public bundle names affected versions and impact, but does not provide CVSS, patch details, exploit prevalence, or technical internals beyond the certificate-strength weakness and physical-access condition.

Mitigation direction

  • Inventory NCR SelfServ ATMs for APTRA XFS 04.02.01 and 05.01.00.
  • Obtain NCR Security Alert 2018-13 and follow NCR-approved remediation guidance.
  • Restrict physical access to ATM internals, service interfaces, and update media.
  • Strengthen maintenance authorization, chain-of-custody, and tamper monitoring for affected ATMs.
  • Review application whitelisting controls with NCR for compensating protections.

Validation and detection

  • Confirm APTRA XFS versions across the ATM fleet.
  • Verify whether affected ATMs use 512-bit RSA certificates for BNA update validation.
  • Check maintenance records for unexpected BNA software updates or CAB archive changes.
  • Validate physical security controls around ATM service access points.
  • Ask NCR support to confirm patched or unaffected configurations.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-326: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-10125 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
NCRSelfServ ATMAPTRA XFS 04.02.01, APTRA XFS 05.01.00Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-326 · source CWE mapping

Inadequate Encryption Strength

Inadequate Encryption Strength represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.