Bsafe vulnerabilitiesRanked by how likely they are to be used.

Product35 versions
The short answer

Bsafe is made by Dell. We track 12 published vulnerabilities listed under that exact name, across 35 versions. None of them is on the list of flaws known to be exploited today. Dell lists newer releases under their own names, such as Bsafe Micro-Edition-Suite, so check those pages too.

See the riskiest flaws

We keep watching the known-exploited list.

Other names

Is Bsafe listed under other names? Yes.

Dell also lists Bsafe under more specific names, such as Bsafe Micro-Edition-Suite and Bsafe SSL-J. Flaws listed only under those names are counted on their own pages, not here. If you run one of these, open its page for its own exploited flaws.

Known exploited

Which Bsafe vulnerabilities are being exploited?

This is the list that matters most: flaws criminals are using now.

None of Bsafe's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.

Exploit likelihood

Which Bsafe flaws are most likely to be used?

Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.

50% or more10% to 49%Under 10%
  1. 4.0%

    RSA BSAFE Micro Edition Suite, versions prior to 4.0.11 (in 4.0.x) and prior to 4.1.6 (in 4.1.x), and RSA BSAFE Crypto-C Micro Edition, version prior to 4.0.5.3 (in 4.0.x) contain a Buffer Over-Read vulnerability...

    CVSS9.8Published14 Sep 2018
  2. 3.2%

    RSA BSAFE Micro Edition Suite, version 4.1.6, contains an integer overflow vulnerability.

    CVSS7.5Published31 Aug 2018
  3. 2.6%

    RSA BSAFE Micro Edition Suite versions prior to 4.0.11 (in 4.0.x series) and versions prior to 4.1.6.2 (in 4.1.x series) contain a key management error issue.

    CVSS7.5Published16 Nov 2018
  4. 2.6%

    Integer underflow in the base64-decoding implementation in EMC RSA BSAFE Micro Edition Suite (MES) 4.0.x before 4.0.8 and 4.1.x before 4.1.3, RSA BSAFE Crypto-C Micro Edition (Crypto-C ME) before 4.0.4 and 4.1, and...

    CVSS9.8Published20 Aug 2015
  5. 2.0%

    EMC RSA BSAFE Micro Edition Suite (MES) 4.0.x before 4.0.8 and 4.1.x before 4.1.3 and RSA BSAFE SSL-C 2.8.9 and earlier, when client authentication and an ephemeral Diffie-Hellman ciphersuite are enabled, allow...

    CVSS7.5Published20 Aug 2015
  6. 1.9%

    RSA BSAFE Micro Edition Suite, prior to 4.1.6.1 (in 4.1.x), and RSA BSAFE Crypto-C Micro Edition versions prior to 4.0.5.3 (in 4.0.x) contain an Uncontrolled Resource Consumption ('Resource Exhaustion') vulnerability...

    CVSS6.5Published31 Aug 2018
  7. 1.7%

    RSA BSAFE Micro Edition Suite, versions prior to 4.0.11 (in 4.0.x) and prior to 4.1.6.1 (in 4.1.x) contains a Covert Timing Channel vulnerability during RSA decryption, also known as a Bleichenbacher attack on RSA...

    CVSS5.9Published31 Aug 2018
  8. 1.6%

    The client in EMC RSA BSAFE Micro Edition Suite (MES) 4.0.x before 4.0.9 and 4.1.x before 4.1.5 places the weakest algorithms first in a signature-algorithm list transmitted to a server, which makes it easier for...

    CVSS7.5Published18 Sep 2016
  9. 1.4%

    EMC RSA BSAFE Micro Edition Suite (MES) 4.0.x before 4.0.8 and 4.1.x before 4.1.3, RSA BSAFE Crypto-J before 6.2, RSA BSAFE SSL-J before 6.2, and RSA BSAFE SSL-C 2.8.9 and earlier do not enforce certain constraints...

    CVSS7.5Published20 Aug 2015
  10. 1.1%

    EMC RSA BSAFE Micro Edition Suite (MES) 4.0.x before 4.0.8 and 4.1.x before 4.1.3 and RSA BSAFE SSL-C 2.8.9 and earlier do not properly restrict TLS state transitions, which makes it easier for remote attackers to...

    CVSS7.5Published20 Aug 2015
Precursor Intelligence

Running Bsafe? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

We track 12 published vulnerabilities listed under the name Bsafe, across 35 versions.

None of Bsafe's vulnerabilities is on the list of flaws known to be exploited today.

Dell also lists Bsafe under more specific names, such as Bsafe Micro-Edition-Suite and Bsafe SSL-J. Flaws listed only under those names are counted on their own pages, not here. Open the release you run to see its own list.

Create a Precursor Intelligence account and track Bsafe. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.