dbcve.org
Bsafe Ssl JApplication · Dell

CVE-2024-29171

HIGH · 7.5 CVSS v3.1 Published 2025-02-12
Fix available
A fix is available. Upgrade to 6.6 / 7.2.1 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
Dell BSAFE SSL-J, versions prior to 6.6 and versions 7.0 through 7.2, contains an Improper certificate verification vulnerability. A remote attacker could potentially exploit this vulnerability, leading to information disclosure.

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

Dell BSAFE SSL-J versions prior to 6.6 and versions 7.0 through 7.2 contain an improper certificate verification vulnerability. A remote unauthenticated attacker could exploit this SSL/TLS certificate validation flaw to perform man-in-the-middle attacks, potentially leading to information disclosure.

MitigationUpdate Dell BSAFE SSL-J to version 6.6 or later (for 6.x line) or obtain the patched version for the 7.x line. After updating, verify that certificate chain validation, hostname verification, and certificate revocation checking function correctly.

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
Bsafe Ssl JApplication
Affected:< 6.6>= 7.0, < 7.2.1

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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. Locate the BSAFE SSL-J library file
    Search for files named bsafessl.jar, ssj*.jar, or similar BSAFE-related JARs in your application deployment directories, lib folders, or classpath. Note the full path to each JAR found.
    Affected if The library file cannot be located (may indicate the library is not in use)
  2. Determine the installed version
    For each BSAFE JAR found, inspect the MANIFEST.MF file inside the JAR archive for the Implementation-Version or Specification-Version attribute. Alternatively, check the filename if the version is embedded (e.g., bsafessl-7.2.0.jar).
    Affected if No version information can be extracted from the library files
  3. Compare version against affected ranges
    Check if the installed version falls into: version < 6.6 OR version >= 7.0 but < 7.2.1. For example, versions 6.5.3, 7.0.0, 7.1.0, and 7.2.0 are vulnerable; versions 6.6.0 and above, or 7.2.1 and above, are not.
    Affected if The installed version is less than 6.6, or is 7.0.x through 7.2.0
  4. Verify SSL/TLS usage of the library
    Search application code, configuration files, or runtime dependencies for usage of BSAFE SSL-J APIs that establish SSL/TLS connections (e.g., SSLContext, KeyManager, TrustManager implementations provided by BSAFE). Check if the application performs HTTPS calls or other TLS-protected communications.
    Affected if The library is present but the application does not use it for SSL/TLS connections (lower risk)

You are affected if your deployed BSAFE SSL-J version is below 6.6 or between 7.0 and 7.2.0 inclusive, AND your application uses this library to establish SSL/TLS connections.

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 6.6 / 7.2.1 or later
Fixed in 6.67.2.1
Interim mitigation

Update Dell BSAFE SSL-J to version 6.6 or later (for 6.x line) or obtain the patched version for the 7.x line. After updating, verify that certificate chain validation, hostname verification, and certificate revocation checking function correctly.

Recommended fix Moderate confidence

Upgrade to BSAFE SSL-J 6.6 (for 6.x users) or 7.2.1 or later (for 7.x users)

  1. 1. Identify the current version of Dell BSAFE SSL-J in use by checking product documentation or runtime version information
  2. 2. If using version 6.x and the version is prior to 6.6, plan upgrade to version 6.6 or later in the 6.x line
  3. 3. If using version 7.0 through 7.2.x, plan upgrade to version 7.2.1 or later in the 7.x line
  4. 4. Before upgrading in production, test the new version in a staging environment to verify compatibility with dependent applications
  5. 5. Review release notes for the target version for any known compatibility issues
  6. 6. Perform the upgrade following the product's standard upgrade procedure
  7. 7. After upgrade, verify that SSL/TLS certificate validation is functioning correctly in dependent applications
Caveat Review release notes for compatibility notes; minor version upgrades typically have minimal breaking changes but certificate handling behavior may have changed

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

Fix this in Bsafe Ssl J Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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