dbcve.org
Bsafe Ssl JApplication · Dell

CVE-2022-34381

CRITICAL · 9.8 CVSS v3.1 Published 2024-02-02
Fix available
A fix is available. Upgrade to 6.2.6.1 / 6.5 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
Dell BSAFE SSL-J version 7.0 and all versions prior to 6.5, and Dell BSAFE Crypto-J versions prior to 6.2.6.1 contain an unmaintained third-party component vulnerability. An unauthenticated remote attacker could potentially exploit this vulnerability, leading to the compromise of the impacted system. This is a Critical vulnerability and Dell recommends customers to upgrade at the earliest opportunity.

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

Dell BSAFE SSL-J and Crypto-J libraries contain a vulnerable unmaintained third-party component. An unauthenticated remote attacker could exploit this to compromise the affected system due to known vulnerabilities in the deprecated dependency.

MitigationUpgrade Dell BSAFE SSL-J to version 6.5 or later, and Dell BSAFE Crypto-J to version 6.2.6.1 or later.

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.5= 7.0
Bsafe Crypto JApplication
Affected:< 6.2.6.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
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. Locate Dell BSAFE libraries in your environment
    Search for JAR files named bsafessl*.jar, bsafecrypto*.jar, or similar patterns in your application directories, lib folders, and dependency repositories. Also check Maven/Gradle dependency declarations for com.dell.* or BSAFE references.
    Affected if Dell BSAFE SSL-J or Crypto-J libraries are present in your environment
  2. Determine the installed version of Dell BSAFE SSL-J
    Check the JAR file name for version numbers, inspect the MANIFEST.MF file inside the JAR for Implementation-Version or Bundle-Version attributes, or query the library programmatically via its version API if available.
    Affected if The version is less than 6.5 or equals exactly 7.0
  3. Determine the installed version of Dell BSAFE Crypto-J
    Check the JAR file name for version numbers, inspect the MANIFEST.MF file inside the JAR for Implementation-Version or Bundle-Version attributes, or query the library programmatically via its version API if available.
    Affected if The version is less than 6.2.6.1
  4. Review dependency manifests and build configurations
    Examine pom.xml, build.gradle, or other dependency management files for explicit version declarations of com.dell.bsafe or related artifact IDs.
    Affected if A vulnerable version is declared in your dependencies

Your environment is affected if Dell BSAFE SSL-J version is below 6.5 or equals 7.0, OR if Dell BSAFE Crypto-J version is below 6.2.6.1, and these libraries are used in your application.

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.2.6.1 / 6.5 or later
Fixed in 6.2.6.16.5
Interim mitigation

Upgrade Dell BSAFE SSL-J to version 6.5 or later, and Dell BSAFE Crypto-J to version 6.2.6.1 or later.

Recommended fix High confidence

BSAFE SSL-J: version 6.5 or later/latest 7.x; BSAFE Crypto-J: version 6.2.6.1 or later

  1. 1. Identify the specific Dell BSAFE product and version currently deployed in your environment (SSL-J or Crypto-J)
  2. 2. For BSAFE SSL-J: Upgrade to version 6.5 or later (or the latest 7.x release that includes the security fix)
  3. 3. For BSAFE Crypto-J: Upgrade to version 6.2.6.1 or later
  4. 4. Verify the upgrade by checking the product version post-installation
  5. 5. Test that dependent applications function correctly after the upgrade
  6. 6. Monitor for any unusual behavior and confirm the vulnerability is no longer present
Caveat Review Dell release notes for any compatibility changes or deprecated features in the new version

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

Fix this in Bsafe Ssl J Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing20.0 h
  • Review / QA8.0 h
46.0 hours of engineering $7,800
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,480.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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