CVE-2023-28074

6.2 MEDIUM

📋 TL;DR

This vulnerability allows an unauthenticated attacker with local access to read memory outside intended bounds in Dell BSAFE cryptographic libraries. This could expose sensitive information like cryptographic keys or application data. Organizations using affected Dell BSAFE Crypto-C Micro Edition or Micro Edition Suite versions are impacted.

💻 Affected Systems

Products:
  • Dell BSAFE Crypto-C Micro Edition
  • Dell BSAFE Micro Edition Suite
Versions: Crypto-C Micro Edition: 4.1.5; Micro Edition Suite: 4.0 through 4.6.1 and 5.0
Operating Systems: Any OS using these libraries
Default Config Vulnerable: ⚠️ Yes
Notes: Affects applications that incorporate these cryptographic libraries. Requires local access to the system.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attacker extracts cryptographic keys or sensitive application data, potentially compromising encryption or authentication mechanisms.

🟠

Likely Case

Information disclosure of adjacent memory contents, which could include application data or system information.

🟢

If Mitigated

Limited information exposure with minimal impact if proper access controls and isolation are implemented.

🌐 Internet-Facing: LOW - Requires local access, not remotely exploitable.
🏢 Internal Only: MEDIUM - Local attackers or malicious insiders could exploit this to gain sensitive information.

🎯 Exploit Status

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

Exploitation requires local access and knowledge of the application using the vulnerable library.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Crypto-C Micro Edition: 4.2.0; Micro Edition Suite: 4.7.0 and 5.1.0

Vendor Advisory: https://www.dell.com/support/kbdoc/en-us/000212325/dsa-2023-120-dell-bsafe-micro-edition-suite-security-update

Restart Required: Yes

Instructions:

1. Identify applications using affected BSAFE libraries. 2. Update to patched versions (4.2.0 for Crypto-C, 4.7.0/5.1.0 for Suite). 3. Rebuild and redeploy applications with updated libraries. 4. Restart affected services.

🔧 Temporary Workarounds

Restrict local access

all

Limit local access to systems running vulnerable applications to trusted users only.

Application isolation

all

Run vulnerable applications in isolated environments or containers with minimal privileges.

🧯 If You Can't Patch

  • Implement strict access controls to limit local user access to vulnerable systems.
  • Monitor for unusual local process activity or memory access patterns.

🔍 How to Verify

Check if Vulnerable:

Check application dependencies for BSAFE library versions. Use 'ldd' on Linux or dependency checkers to identify linked libraries.

Check Version:

On Linux: 'strings /path/to/library | grep -i version' or check package manager. On Windows: Check DLL properties or use dependency walker.

Verify Fix Applied:

Verify updated library versions are present (4.2.0 for Crypto-C, 4.7.0/5.1.0 for Suite) and applications are rebuilt with them.

📡 Detection & Monitoring

Log Indicators:

  • Unusual local process crashes or memory access errors in application logs

Network Indicators:

  • None - local vulnerability only

SIEM Query:

Process monitoring for abnormal memory reads or crashes in applications using BSAFE libraries.

🔗 References

📤 Share & Export