Entrust Instant Financial Issuance (IFI) On Premise software (formerly referred to as CardWizard) versions 5.x, prior to 6.10.5, and prior to 6.11.1 contain an insecure .NET Remoting exposure in the SmartCardController service (DCG.SmartCardControllerService.exe). The service registers a TCP remoting channel with unsafe formatter/settings that permit untrusted remoting object invocation. A remote, unauthenticated attacker who can reach the remoting port can invoke exposed remoting objects to read arbitrary files from the server and coerce outbound authentication, and may achieve arbitrary file write and remote code execution via known .NET Remoting exploitation techniques. This can lead to disclosure of sensitive installation and service-account data and compromise of the affected host.
Security readout for executives and security teams
Plain-English summary
Entrust IFI On Premise systems can expose a SmartCardController service that accepts unsafe remote calls. If attackers can reach that service, they may read sensitive files, trigger outbound authentication, and potentially take over the host. This is critical for organizations issuing financial cards on affected on-premise versions.
Executive priority
Treat this as urgent for any card issuance environment using affected on-premise Entrust IFI software. The business risk is server compromise and disclosure of sensitive service or installation data.
Technical view
The issue is insecure .NET Remoting in DCG.SmartCardControllerService.exe. A TCP remoting channel uses unsafe formatter/settings and permits unauthenticated invocation of exposed objects. The CVE maps to missing authentication and unsafe deserialization, with possible arbitrary file read, authentication coercion, file write, and remote code execution.
Likely exposure
Exposure is likely limited to Entrust Instant Financial Issuance On Premise, formerly CardWizard, versions 5.x before 6.10.5 and versions before 6.11.1 where the remoting port is reachable over a network.
Exploitation context
The source bundle does not show CISA KEV listing or cited evidence of active exploitation. Exploitation requires network reachability to the remoting service and no authentication, making internal exposure still significant.
Researcher notes
Evidence supports unauthenticated network attack surface through unsafe .NET Remoting. Do not assume internet exposure or exploitation without local telemetry. Focus validation on version, service presence, reachability, and vendor advisory alignment.
Mitigation direction
Upgrade affected IFI On Premise installations to vendor-fixed versions 6.10.5 or 6.11.1 as applicable.
Review the Entrust advisory for branch-specific patch guidance.
Restrict network access to the SmartCardController remoting service until patched.
Limit service reachability to trusted administrative networks only.
Review affected hosts for signs of file access or unexpected outbound authentication attempts.
Validation and detection
Inventory Entrust IFI or CardWizard on-premise servers and record installed versions.
Confirm whether DCG.SmartCardControllerService.exe is present and running.
Determine whether the remoting service is reachable from untrusted networks.
Validate patched status against Entrust guidance for 6.10.5 and 6.11.1.
Check logs for unusual service activity, file access, or outbound authentication behavior.
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 · medium confidence lookup
CWE-306: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. 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.
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. 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.
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.
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
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.
1CVSS vectors
3Timeline events
1ADP providers
4Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-306 · source CWE mapping
Missing Authentication for Critical Function
Missing Authentication for Critical Function represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.