CVE-2023-28074 is an out-of-bounds read in Dell BSAFE Micro Edition Suite and Crypto-C Micro Edition that a local, unauthenticated attacker could use to expose information. NVD and Dell score it 6.2, Medium. Dell recommends upgrading to Micro Edition Suite 5.0.2.1.
What's affected
Dell advisory DSA-2023-120 lists:
- BSAFE Micro Edition Suite 5.0: fixed in 5.0.1 and 5.0.2.1.
- BSAFE Micro Edition Suite 4.0 through 4.6.1: fixed in 4.6.2.
- BSAFE Crypto-C Micro Edition 4.0 through 4.1.5: fixed in Micro Edition Suite 4.6.2 and 5.0.1.
Source conflict on versions: the NVD description names only Crypto-C Micro Edition 4.1.5, while Dell's table covers 4.0 through 4.1.5. Dell also says the FIPS module of Crypto-C Micro Edition is not affected, only the SDK, and warns that its table may not be complete.
Severity agrees: 6.2, Medium, vector CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.
How to check if you're exposed
BSAFE is a cryptography library that vendors embed in their own products, so you may not know you use it. Start with the software bills of materials and licence lists of any commercial product that mentions RSA BSAFE, Crypto-C or Micro Edition Suite. Ask the vendor which version it ships.
If you build with it yourself, check the version of the library in your build files against the ranges above. Dell asks customers to request downloads through its knowledge base article 000195213.
What to do now
- Upgrade to Micro Edition Suite 5.0.2.1, the version Dell recommends, or to the fixed version for your branch.
- Dell says a workaround exists for customers who cannot upgrade. Customers with an active maintenance contract should contact BSAFE Support for the details.
- Ask vendors whose products embed BSAFE whether they have shipped a fixed build.
- Rebuild and redeploy anything that statically links the library, since a new library on disk does not change an old binary.
- Check the Gold page for this CVE for later changes.
Why it matters
The record classes the flaw as CWE-125 (Out-of-bounds Read). An out-of-bounds read means the code reads memory beyond the intended buffer. The record says the impact is information exposure, and the vector in Dell's advisory shows an availability impact.
The context raises the stakes. This is a cryptographic library, and memory near key material is sensitive. Exploitation needs local access in this case, so the risk is smaller than a network flaw.
Libraries are the awkward part of this kind of issue. A fix in the library only reaches users after each product that embeds it is rebuilt and shipped. That is why a software inventory matters: you cannot update what you cannot find. Dependency scanning on your own source can show where a library enters your builds, and a bill of materials from your suppliers shows where it enters theirs.
Quick check
Is the FIPS module affected?
Dell says the FIPS module of Crypto-C Micro Edition is not affected, only the SDK. Check the advisory for your exact configuration.
Sources
Last reviewed: 19 October 2026.