dbcve.org
BsafeApplication · Dell

CVE-2015-0537

CRITICAL · 9.8 CVSS v3.1 Published 2015-08-20
Fix available
A fix is available. Upgrade to 4.0.4 / 4.0.8 or later.
See remediation →
100/100
Remediation priority · Urgent
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
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 RSA BSAFE SSL-C 2.8.9 and earlier allows remote attackers to cause a denial of service (memory corruption or segmentation fault) or possibly have unspecified other impact via crafted base64 data, a similar issue to CVE-2015-0292.

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 · moderate confidence

Integer underflow vulnerability in RSA BSAFE library base64 decoding allows crafted base64 data to cause memory corruption or segmentation faults. The flaw occurs when the decoder miscalculates buffer sizes due to the underflow, potentially enabling arbitrary memory writes. This affects multiple RSA BSAFE products including Micro Edition Suite, Crypto-C Micro Edition, and SSL-C.

MitigationUpdate RSA BSAFE libraries to versions 4.0.8+, 4.1.3+, 4.0.4+, or patched SSL-C versions as specified in vendor advisories. Alternatively, implement input validation on base64 data before passing to the library.

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 Crypto CApplication
Affected:< 4.0.4
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
High
Integrity
High
Availability
High

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

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 files in the environment
    Search for library files with names containing 'bsafe', 'crypto-c', 'ssl-c', or RSA BSAFE-related DLLs/SOs across the system. Check application dependencies and packaging metadata.
    Affected if Any RSA BSAFE library files are present in the environment
  2. Determine the specific BSAFE product name
    Examine the library file metadata, manifest, or associated documentation to identify whether it is Dell Bsafe, Dell Bsafe Crypto C, or Dell Bsafe SSL C.
    Affected if The product is one of these three RSA BSAFE variants
  3. Locate the installed version number
    Read the version resource of the library file (version info, file properties), check accompanying version files, or query the library API if accessible. Common locations: file properties, version.h headers, or runtime version queries.
    Affected if A version number is found that matches the affected ranges: Bsafe >=4.0.0 and <4.0.8, or >=4.1.0 and <4.1.3; Crypto C <4.0.4; SSL C <=2.8.9
  4. Verify base64 decoding is in use
    Review application code or configuration to confirm that base64 decoding functions from the BSAFE library are being called. Check for usage of functions related to base64, B64, or binary data decoding.
    Affected if Base64 decoding functionality from the RSA BSAFE library is actively used by the application

The environment is affected if RSA BSAFE library files are present, the installed version falls within the affected ranges, and base64 decoding from that library is being invoked.

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.

dbcve · scoped
Upgrade available Upgrade to 4.0.4 / 4.0.8 / 4.1.3 or later
Fixed in 4.0.44.0.84.1.3
Interim mitigation

Update RSA BSAFE libraries to versions 4.0.8+, 4.1.3+, 4.0.4+, or patched SSL-C versions as specified in vendor advisories. Alternatively, implement input validation on base64 data before passing to the library.

Recommended fix High confidence

Bsafe 4.0.8+, Bsafe 4.1.3+, Bsafe Crypto C 4.0.4+, Bsafe SSL C >2.8.9

  1. 1. Identify the currently installed Bsafe/Bsafe Crypto C/Bsafe SSL C version by checking product documentation or version files
  2. 2. For Bsafe 4.0.x users: Upgrade to version 4.0.8 or later
  3. 3. For Bsafe 4.1.x users: Upgrade to version 4.1.3 or later
  4. 4. For Bsafe Crypto C users: Upgrade to version 4.0.4 or later (or 4.1.x)
  5. 5. For Bsafe SSL C users: Upgrade to a version newer than 2.8.9
  6. 6. After upgrading, test the integration to ensure base64-encoded data is processed correctly and the application functions as expected
  7. 7. Verify the fix by confirming the CVE is no longer present in the updated version
Caveat As this is a low-level crypto library upgrade, regression testing of all functionality that uses base64 encoding/decoding is recommended to ensure compatibility with existing integrations

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Bsafe Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-0537 — 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-0537 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