CVE-2019-3728

7.5 HIGH

📋 TL;DR

This CVE describes an out-of-bounds read vulnerability in RSA BSAFE cryptographic libraries when processing DSA signatures. A remote attacker could exploit this to cause a denial-of-service crash in affected systems. Organizations using RSA BSAFE Crypto-C Micro Edition, Micro Edition Suite, or Crypto-C versions within specified ranges are vulnerable.

💻 Affected Systems

Products:
  • RSA BSAFE Crypto-C Micro Edition
  • RSA BSAFE Micro Edition Suite
  • RSA Crypto-C
Versions: Crypto-C Micro Edition: 4.0.0.0-4.0.5.3, 4.1.0-4.1.3; Micro Edition Suite: 4.0.0-4.0.12, 4.1.0-4.3; Crypto-C: 6.0.0-6.4.*
Operating Systems: All platforms where affected RSA BSAFE libraries are deployed
Default Config Vulnerable: ⚠️ Yes
Notes: Systems using DSA signature verification with affected RSA BSAFE libraries are vulnerable.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Remote code execution leading to complete system compromise, though this is not explicitly stated in the CVE description.

🟠

Likely Case

Denial-of-service through application/library crash, potentially disrupting cryptographic operations.

🟢

If Mitigated

Limited impact if proper network segmentation and access controls prevent malicious actors from reaching vulnerable systems.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ⚠️ Yes
Complexity: MEDIUM

Exploitation requires sending specially crafted DSA signatures to trigger the out-of-bounds read.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Crypto-C Micro Edition: 4.0.5.4+, 4.1.4+; Micro Edition Suite: 4.0.13+, 4.4+; Crypto-C: 6.5+

Vendor Advisory: https://www.dell.com/support/kbdoc/000194054

Restart Required: Yes

Instructions:

1. Identify affected RSA BSAFE library versions. 2. Obtain updated libraries from Dell/RSA. 3. Replace vulnerable libraries with patched versions. 4. Restart applications/services using the libraries.

🔧 Temporary Workarounds

Disable DSA Signature Processing

all

If DSA signatures are not required, disable DSA signature verification in applications using affected libraries.

🧯 If You Can't Patch

  • Implement network segmentation to isolate systems using vulnerable libraries from untrusted networks.
  • Deploy web application firewalls (WAFs) or intrusion prevention systems (IPS) to detect and block malicious DSA signature traffic.

🔍 How to Verify

Check if Vulnerable:

Check application/library dependencies for RSA BSAFE library versions within affected ranges.

Check Version:

Platform-specific commands vary; check application documentation or use system package managers (e.g., rpm -qa | grep -i rsa, dpkg -l | grep -i rsa).

Verify Fix Applied:

Verify installed RSA BSAFE library versions are at or above patched versions: Crypto-C Micro Edition 4.0.5.4/4.1.4+, Micro Edition Suite 4.0.13/4.4+, Crypto-C 6.5+.

📡 Detection & Monitoring

Log Indicators:

  • Application crashes or abnormal terminations related to cryptographic operations
  • Error logs mentioning RSA BSAFE libraries or DSA signature failures

Network Indicators:

  • Unusual network traffic patterns to systems using RSA BSAFE libraries, especially involving DSA signature exchanges

SIEM Query:

Example: 'application:(rsa OR bsafe) AND (crash OR error OR termination)'

🔗 References

📤 Share & Export