CVE-2021-21575 is a medium severity (CVSS 5.9) observable timing discrepancy in Dell BSAFE Micro Edition Suite versions before 4.5.2. It can leak information through timing differences. Upgrade to 4.5.2 or later, and read Dell advisory DSA-2021-131 for the other issues fixed in the same release.
What's affected
- Dell BSAFE Micro Edition Suite, versions before 4.5.2, per the NVD record.
- Dell advisory DSA-2021-131 covers several vulnerabilities in the suite. The page did not load in full for us, so read it for the complete list and the Dell guidance.
- The impact in the record is high confidentiality, with no integrity or availability impact, and high attack complexity.
- KEV status: false.
How to check if you're exposed
BSAFE is a cryptographic library that vendors embed in their own products, so you may use it without having installed it directly. Look in your product documentation and software bill of materials for Dell BSAFE or RSA BSAFE Micro Edition Suite, and note the version.
If a vendor product bundles it, ask that vendor whether the bundled copy is 4.5.2 or later.
What to do now
- Search your software inventory and vendor documentation for BSAFE Micro Edition Suite.
- Where you build against the library yourself, move to 4.5.2 or later and rebuild.
- Where a third party product bundles it, ask the vendor for the patched build and a date.
- Read DSA-2021-131 for the other fixes in the same release and apply them together.
- Record the result in your risk register if a vendor cannot patch quickly, with an owner and a review date.
- Do not treat the medium score as a reason to defer indefinitely. Cryptographic leaks can combine with other weaknesses, and a planned upgrade is cheaper than an urgent one later.
Why it matters
The class is CWE-208, observable timing discrepancy, with CWE-203 (observable discrepancy) alongside it. Cryptographic code is supposed to take the same time whatever the secret data is. When the time varies with the secret, an attacker who can measure it many times may infer parts of the secret.
These flaws are hard to exploit, which is why the record shows high attack complexity and a medium score. They still matter in crypto libraries, because the library sits underneath many products and the affected code often passes through your own software supply chain without anyone listing it.
Quick check
Why do I not see BSAFE in my package list?
It is commonly embedded inside vendor products. Check your SBOM and ask product vendors.
Is this exploitable over the network?
The record gives a network vector with high complexity. Practical exploitation needs precise timing measurements.
Sources
Last reviewed: 19 October 2026.