dbcve.org
Missing AuthenticationWeakness · CWE-306

CVE-2025-34414

CRITICAL · 9.3 CVSS v4.0 Published 2025-12-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable 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
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 Legacy Remoting Service that is enabled by default. The service registers a TCP remoting channel with SOAP and binary formatters configured at TypeFilterLevel=Full and exposes default ObjectURI endpoints such as logfile.rem, photo.rem, cwPhoto.rem, and reports.rem on a network-reachable remoting port. 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.

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

Entrust Instant Financial Issuance (IFI) versions prior to 6.10.5/6.11.1 expose an insecure .NET Remoting service with TypeFilterLevel=Full on a network-reachable TCP port. This enables remote unauthenticated attackers to read arbitrary files, coerce outbound authentication, and achieve remote code execution via well-documented .NET Remoting exploitation techniques.

MitigationDisable the Legacy Remoting Service or block access to its TCP port, or upgrade to version 6.10.5 or 6.11.1 or later which addresses this vulnerability.

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

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
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 installed Entrust IFI version
    Locate the Entrust Instant Financial Issuance installation directory and check the version information, typically found in the application executable, installer logs, or version file within the program folder. On Windows, this may also be visible in Add/Remove Programs.
    Affected if The installed version is earlier than 6.10.5 or 6.11.1 (for example, 6.9.x, 6.10.0-6.10.4, or 6.11.0)
  2. Verify Legacy Remoting Service status
    Check if the Legacy Remoting Service is running on the system. On Windows, open Services (services.msc) and look for a service related to 'Remoting', 'Legacy Remoting', or the IFI application remoting component. Alternatively, use the command 'sc query' or review the application configuration files for remoting-enabled settings.
    Affected if The Legacy Remoting Service is installed and currently running
  3. Identify and test remoting TCP port exposure
    Identify the TCP port used by the .NET Remoting service (common default ports include 8080, 8090, or custom ports configured in the application's remoting configuration). Use 'netstat -an' or 'Get-NetTCPConnection' to find listening ports, then determine if the port binds to 0.0.0.0 or a network-accessible IP rather than localhost only.
    Affected if The remoting TCP port is listening on an IP address accessible from other systems on the network
  4. Confirm TypeFilterLevel configuration
    Locate the .NET Remoting configuration file for the IFI application (typically named app.config or an XML configuration file in the application directory). Open it and search for '<server>' or '<channel>' elements that define the remoting endpoint. Look for the 'typeFilterLevel' attribute and verify if it is set to 'Full'.
    Affected if The typeFilterLevel attribute is set to 'Full' in the remoting configuration

A user is affected if their installed Entrust IFI version is prior to 6.10.5 or 6.11.1 AND the Legacy Remoting Service is running with a network-exposed TCP port and TypeFilterLevel set to Full.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Disable the Legacy Remoting Service or block access to its TCP port, or upgrade to version 6.10.5 or 6.11.1 or later which addresses this vulnerability.

Recommended fix High confidence

Upgrade to Entrust IFI version 6.11.1 or later

  1. 1. Obtain the latest version of Entrust Instant Financial Issuance (IFI) from the official vendor (Entrust) - version 6.11.1 or later contains the security fix
  2. 2. Review the Entrust upgrade documentation and release notes for version 6.11.1 before proceeding
  3. 3. Create a full backup of the current IFI installation, including configuration files and database
  4. 4. Schedule a maintenance window for the upgrade
  5. 5. Stop all IFI services before starting the upgrade
  6. 6. Install version 6.11.1 (or latest available) following the vendor's installation instructions
  7. 7. Verify that the Legacy Remoting Service is either disabled or properly secured after upgrade
  8. 8. Start the IFI services and verify normal operation
Caveat Review release notes for any configuration changes or compatibility considerations before upgrading

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,330
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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