dbcve.org
BsafeApplication · Dell

CVE-2015-0535

HIGH · 7.5 CVSS v3.1 Published 2015-08-20
Fix available
A fix is available. Upgrade to 4.0.8 / 4.1.3 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 conduct cipher-downgrade attacks to EXPORT_RSA ciphers via crafted TLS traffic, related to the "FREAK" issue, a similar issue to CVE-2015-0204.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

RSA BSAFE MES and SSL-C libraries fail to properly restrict TLS state transitions, allowing remote attackers to force cipher-suite downgrades to weak EXPORT_RSA ciphers through crafted TLS traffic. This enables man-in-the-middle attackers to exploit export-grade RSA keys, similar to the FREAK vulnerability (CVE-2015-0204).

MitigationUpgrade RSA BSAFE MES to version 4.0.8/4.1.3 or later and SSL-C to 2.8.9.1 or later, or explicitly disable EXPORT_RSA cipher suites in the TLS configuration.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
BsafeApplication
Affected:>= 4.0.0, < 4.0.8>= 4.1.0, < 4.1.3
Bsafe Ssl CApplication
Affected:<= 2.8.9

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify RSA BSAFE library presence
    Search for RSA BSAFE MES or SSL-C library files in the system (common paths include /usr/lib, /opt, or application-specific directories). Look for files named libbsafe, libssl-c, or similar. Also check application dependencies or software manifests that may reference RSA BSAFE.
    Affected if The RSA BSAFE library (MES or SSL-C) is found in the environment and its version falls within 4.0.0 to <4.0.8, 4.1.0 to <4.1.3, or SSL-C version <=2.8.9.
  2. Determine installed BSAFE version
    If the library is found, query its version using methods appropriate to the deployment: check version strings in library binaries, review software inventory or package management records, or use any provided version-query functions in the application using the library.
    Affected if The installed version is less than 4.0.8 for 4.x versions, less than 4.1.3 for 4.1.x versions, or SSL-C version 2.8.9 or earlier.
  3. Inspect TLS configuration for EXPORT_RSA ciphers
    Examine the TLS/SSL configuration of applications using the RSA BSAFE library. Look for enabled cipher suites in configuration files, application settings, or runtime parameters. Specifically search for EXPORT, EXPORT_RSA, or weak export-grade cipher identifiers.
    Affected if EXPORT_RSA cipher suites (such as EXP1024 or other export-grade ciphers) are enabled in the TLS configuration.
  4. Verify cipher preference order allows downgrades
    Review the TLS handshake behavior and cipher preference settings. Check if the server accepts client-proposed cipher suites without proper validation, allowing a MITM to force downgrade to weaker export ciphers.
    Affected if The TLS implementation accepts cipher-suite recommendations from the client without adequate validation, enabling forced downgrade to EXPORT_RSA ciphers.

You are affected if your environment contains RSA BSAFE MES versions <4.0.8 or <4.1.3, or SSL-C version <=2.8.9, AND EXPORT_RSA cipher suites are enabled in the TLS configuration.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to 4.0.8 / 4.1.3 or later
Fixed in 4.0.84.1.3
Interim mitigation

Upgrade RSA BSAFE MES to version 4.0.8/4.1.3 or later and SSL-C to 2.8.9.1 or later, or explicitly disable EXPORT_RSA cipher suites in the TLS configuration.

Fix this in Bsafe Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-0535 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-0535 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data