CVE-2024-39342

6.6 MEDIUM

📋 TL;DR

This vulnerability in Entrust Instant Financial Issuance (formerly Cardwizard) allows attackers to decrypt passwords using static hard-coded AES keys, potentially leading to privilege escalation on Windows systems. Organizations using affected versions of this financial card issuance software are at risk.

💻 Affected Systems

Products:
  • Entrust Instant Financial Issuance (formerly Cardwizard)
Versions: 6.10.0, 6.9.0, 6.9.1, 6.9.2, 6.8.x and earlier
Operating Systems: Windows
Default Config Vulnerable: ⚠️ Yes
Notes: Requires access to WebAPI.cfg.xml file from CVE-2024-39341 to obtain encrypted password for decryption.

⚠️ Manual Verification Required

This CVE does not have specific version information in our database, so automatic vulnerability detection cannot determine if your system is affected.

Why? The CVE database entry doesn't specify which versions are vulnerable (no version ranges provided by the vendor/NVD).

🔒 Custom verification scripts are available for registered users. Sign up free to download automated test scripts.

Recommended Actions:
  1. Review the CVE details at NVD
  2. Check vendor security advisories for your specific version
  3. Test if the vulnerability is exploitable in your environment
  4. Consider updating to the latest version as a precaution

⚠️ Risk & Real-World Impact

🔴

Worst Case

Full system compromise through privilege escalation to administrative rights, enabling complete control over the Windows host and access to sensitive financial card issuance systems.

🟠

Likely Case

Unauthorized access to the Entrust application with elevated privileges, potentially allowing manipulation of financial card issuance processes or data exfiltration.

🟢

If Mitigated

Limited impact if proper network segmentation, least privilege access controls, and monitoring are in place to detect unauthorized access attempts.

🌐 Internet-Facing: MEDIUM
🏢 Internal Only: HIGH

🎯 Exploit Status

Public PoC: ⚠️ Yes
Weaponized: LIKELY
Unauthenticated Exploit: ✅ No
Complexity: LOW

Exploitation requires access to the encrypted password from WebAPI.cfg.xml and knowledge of the static AES keys. The GitHub gist provides technical details.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: https://trustedcare.entrust.com/login

Restart Required: No

Instructions:

1. Contact Entrust support through TrustedCare portal for guidance. 2. Monitor vendor communications for patches or updates. 3. Consider upgrading to unaffected versions if available.

🔧 Temporary Workarounds

Restrict File Access

windows

Limit access to WebAPI.cfg.xml file to prevent attackers from obtaining the encrypted password needed for exploitation.

icacls "C:\Path\To\WebAPI.cfg.xml" /deny Everyone:(R)

Network Segmentation

all

Isolate Entrust Instant Financial Issuance systems from untrusted networks and implement strict firewall rules.

🧯 If You Can't Patch

  • Implement strict access controls and monitoring on systems running vulnerable versions
  • Consider temporary suspension of affected systems if risk is unacceptable

🔍 How to Verify

Check if Vulnerable:

Check installed version of Entrust Instant Financial Issuance against affected versions list. Verify presence of DCG.Security.dll and WebAPI.cfg.xml files.

Check Version:

Check application properties or installation directory for version information

Verify Fix Applied:

Confirm with vendor that updated version no longer uses static hard-coded AES keys in DCG.Security.dll.

📡 Detection & Monitoring

Log Indicators:

  • Unauthorized access attempts to WebAPI.cfg.xml
  • Unusual privilege escalation events
  • Suspicious DLL loading patterns

Network Indicators:

  • Unusual outbound connections from Entrust systems
  • Traffic patterns indicating data exfiltration

SIEM Query:

source="windows-security" AND (event_id=4688 OR event_id=4624) AND process_name="*entrust*" AND user_name_changed=true

🔗 References

📤 Share & Export