CVE 9.3 CRITICAL

Entrust Instant Financial Issuance (IFI) Unauthenticated .NET Remoting Exposure_CVE-2025-34414

9.3 / 10
CRITICAL
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

Description

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. A remote, unauthenticated attacker who can reach the remoting port can invoke the 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.

AI Analysis

Unauthenticated .NET Remoting Exposure in Entrust Instant Financial Issuance (IFI) allowing remote file read, authentication coercion, and potential arbitrary file write and code execution

Basic Information

ID CVE-2025-34414
Source VulnCheck
Published Dec 9, 2025 at 18:11
Modified Dec 9, 2025 at 19:19

Affected Product

Vendor Entrust Corporation
Product Instant Financial Issuance (IF)
Version 5.x, 6.0, 6.10.x prior to 6.10.5, 6.11.x prior to 6.11.1
Affected Versions Entrust Corporation Instant Financial Issuance (IF) 5.x
Entrust Corporation Instant Financial Issuance (IF) 6.0
Entrust Corporation Instant Financial Issuance (IF) 6.0

CWE Classification

AI Assessment

AI Score 9.3 / 10
AI Severity Critical
Vendor Entrust Corporation
Product Instant Financial Issuance (IFI)
Version 5.x, 6.0, 6.10.x prior to 6.10.5, 6.11.x prior to 6.11.1

References

💭 Join the Security Discussion

🔒 Your email address will not be published. Required fields are marked *

⚠️ Please be respectful and constructive in your comments. Security discussions should remain professional.