Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2022-34381: 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

52
This month
CRITICAL 9.1REMOTEUPGRADEUPGRADE

CVE-2022-34381 is a critical-severity flaw (CVSS 9.1) affecting bsafe ssl-j, bsafe crypto-j. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

  • Critical severity
  • Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score9.1 (Critical)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance1.0% (top 38%)
CISA exploited listNo
WeaknessCWE-1329
Published2024-02-02
Last modified2026-06-17
Publisher (CNA): Dell · Vendor: dell

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

dell bsafe ssl-j UPGRADE
Affected: < 6.5 · 7.0
Fixed in: 6.5
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy bsafe-ssl-j || rpm -q bsafe-ssl-j || bsafe-ssl-j --version
2. UPGRADE to 6.5 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade bsafe-ssl-j
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade bsafe-ssl-j
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
dell bsafe crypto-j UPGRADE
Affected: < 6.2.6.1
Fixed in: 6.2.6.1
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy bsafe-crypto-j || rpm -q bsafe-crypto-j || bsafe-crypto-j --version
2. UPGRADE to 6.2.6.1 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade bsafe-crypto-j
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade bsafe-crypto-j
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-34381?

bsafe ssl-j: upgrade to 6.5; bsafe crypto-j: upgrade to 6.2.6.1. Exact commands for each OS are on this page.

Is CVE-2022-34381 being exploited?

CVE-2022-34381 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-34381 affect?

CVE-2022-34381 affects bsafe ssl-j, bsafe crypto-j. Severity is critical (CVSS 9.1). 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 vu

How urgent is CVE-2022-34381?

Priority 52/100. Critical severity; Remotely exploitable, no login, no user action

Software pages

Dell vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.