# CVE-2022-34381: Supply chain in Dell BSAFE Crypto-J

> Unauthenticated remote attackers can compromise systems using Dell BSAFE libraries due to vulnerabilities in unmaintained third-party components.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Feb 2024
- **Updated:** 16 Dec 2025
- **Also known as:** GHSA-fp29-pg6r-vvr7

## What is CVE-2022-34381?

CVE-2022-34381 is a critical vulnerability in Dell BSAFE Crypto-J, published on 2 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-1329 (Reliance on Component That is Not Updateable)

## Which versions are affected by CVE-2022-34381?

It affects 2 products.


Products: Dell Bsafe Crypto-J, Dell Bsafe Ssl-J.

## How do I fix CVE-2022-34381?

No fix has been published for CVE-2022-34381 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-34381 being exploited?

There is no known exploitation of CVE-2022-34381 in the wild and no public exploit code.

## Other vulnerabilities in Dell BSAFE Crypto-J

- [CVE-2016-8212](https://insights.sbomify.com/CVE-2016-8212/): Security feature bypass in RSA BSAFE Crypto-J RSA BSAFE Crypto-J versions prior to 6.2.2 (high 7.5)
- [CVE-2025-26333](https://insights.sbomify.com/CVE-2025-26333/): Information disclosure in BSAFE Crypto-J (medium 5.9)
- [CVE-2018-11070](https://insights.sbomify.com/CVE-2018-11070/): Weak cryptography in RSA BSAFE Crypto-J (medium 5.9)
- [CVE-2016-8217](https://insights.sbomify.com/CVE-2016-8217/): Information disclosure in RSA BSAFE Crypto-J RSA BSAFE Crypto-J versions prior to 6.2.2 (low 3.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-34381 and fix it if it is affected.

What it is: CVE-2022-34381 is a critical vulnerability in Dell BSAFE Crypto-J, published on 2 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-34381 in the wild and no public exploit code.

Affected product: Dell BSAFE Crypto-J. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-34381/ (Markdown: https://insights.sbomify.com/CVE-2022-34381/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-34381
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-34381
- OSV: https://osv.dev/vulnerability/CVE-2022-34381

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-34381/
Summaries are generated and may contain mistakes; the official description above is the record.