CVE-2020-35169

9.1 CRITICAL

📋 TL;DR

CVE-2020-35169 is an improper input validation vulnerability in Dell BSAFE cryptographic libraries that could allow attackers to execute arbitrary code or cause denial of service. Affected systems include those using Dell BSAFE Crypto-C Micro Edition before 4.1.5 or Dell BSAFE Micro Edition Suite before 4.5.2. This vulnerability is particularly concerning as it affects cryptographic libraries used by various applications.

💻 Affected Systems

Products:
  • Dell BSAFE Crypto-C Micro Edition
  • Dell BSAFE Micro Edition Suite
Versions: Crypto-C Micro Edition: before 4.1.5; Micro Edition Suite: before 4.5.2
Operating Systems: All operating systems using these libraries
Default Config Vulnerable: ⚠️ Yes
Notes: These libraries may be embedded in various applications including Oracle products and other third-party software

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Remote code execution leading to complete system compromise, data theft, or persistent backdoor installation

🟠

Likely Case

Denial of service through application crashes or cryptographic failures

🟢

If Mitigated

Limited impact if proper network segmentation and least privilege principles are implemented

🌐 Internet-Facing: HIGH - Cryptographic libraries are often used in network-facing services and could be exploited remotely
🏢 Internal Only: MEDIUM - Internal systems using affected libraries remain vulnerable to insider threats or lateral movement

🎯 Exploit Status

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

CVSS 9.1 indicates critical severity with high impact and low attack complexity, though no public exploits are confirmed

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Crypto-C Micro Edition: 4.1.5 or later; Micro Edition Suite: 4.5.2 or later

Vendor Advisory: https://www.dell.com/support/kbdoc/en-us/000181115/dsa-2020-286-dell-bsafe-crypto-c-micro-edition-4-1-5-and-dell-bsafe-micro-edition-suite-4-6-multiple-security-vulnerabilities

Restart Required: Yes

Instructions:

1. Identify applications using affected BSAFE libraries. 2. Update to patched versions: Crypto-C Micro Edition 4.1.5+ or Micro Edition Suite 4.5.2+. 3. Restart affected applications/services. 4. Test functionality after patching.

🔧 Temporary Workarounds

Network segmentation

all

Isolate systems using vulnerable libraries from untrusted networks

Application whitelisting

all

Restrict execution of applications using vulnerable libraries

🧯 If You Can't Patch

  • Implement strict network access controls to limit exposure
  • Monitor for abnormal behavior in applications using BSAFE libraries

🔍 How to Verify

Check if Vulnerable:

Check application documentation or use dependency scanning tools to identify BSAFE library versions

Check Version:

Check library files or application documentation; specific commands vary by implementation

Verify Fix Applied:

Verify library files show version 4.1.5+ for Crypto-C or 4.5.2+ for Micro Edition Suite

📡 Detection & Monitoring

Log Indicators:

  • Application crashes related to cryptographic operations
  • Unexpected process terminations

Network Indicators:

  • Unusual network traffic to/from applications using BSAFE libraries

SIEM Query:

search for process crashes containing 'BSAFE', 'Crypto-C', or cryptographic error messages

🔗 References

📤 Share & Export