# CVE-2023-46233: crypto-js PBKDF2 1,000 times weaker than specified in 1993 and 1.3M times weaker than current standard

> The crypto-js library uses weak PBKDF2 defaults, allowing attackers to easily crack protected passwords or forge signatures.

- **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:** Yes
- **Published:** 25 Oct 2023
- **Updated:** 23 Jun 2026
- **Also known as:** CLSA-2026-1773965917, DEBIAN-CVE-2023-46233, DLA-3669-1, GHSA-xwcq-pm8m-c4vf, MINI-2hqg-prvv-4g83, ROOT-APP-NPM-CVE-2023-46233, UBUNTU-CVE-2023-46233, USN-6753-1

## What is CVE-2023-46233?

CVE-2023-46233 is a critical vulnerability in brix crypto-js, published on 25 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

crypto-js is a JavaScript library of crypto standards. Prior to version 4.2.0, crypto-js PBKDF2 is 1,000 times weaker than originally specified in 1993, and at least 1,300,000 times weaker than current industry standard. This is because it both defaults to SHA1, a cryptographic hash algorithm considered insecure since at least 2005, and defaults to one single iteration, a 'strength' or 'difficulty' value specified at 1,000 when specified in 1993. PBKDF2 relies on iteration count as a countermeasure to preimage and collision attacks. If used to protect passwords, the impact is high. If used to generate signatures, the impact is high. Version 4.2.0 contains a patch for this issue. As a workaround, configure crypto-js to use SHA256 with at least 250,000 iterations.

Weakness: CWE-327 (Use of a Broken or Risky Cryptographic Algorithm), CWE-916 (Use of Password Hash With Insufficient Computational Effort), CWE-328 (Use of Weak Hash)

## Which versions are affected by CVE-2023-46233?

2 open source packages ship an affected version, including crypto-js. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `crypto-js` | npm | All versions | 4.2.0 |
| `crypto-js` | npm | All versions | 4.2.0 |

Products: Crypto-Js Project Crypto-Js.

## How do I fix CVE-2023-46233?

Upgrade crypto-js to 4.2.0 or later.

## Is CVE-2023-46233 being exploited?

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

## Other vulnerabilities in brix crypto-js

- [CVE-2020-36732](https://insights.sbomify.com/CVE-2020-36732/): crypto-js uses insecure random numbers (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-46233 and fix it if it is affected.

What it is: CVE-2023-46233 is a critical vulnerability in brix crypto-js, published on 25 Oct 2023. 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-2023-46233 in the wild and no public exploit code.

Affected packages and fixed versions:
- crypto-js (npm): affected all versions; fixed in 4.2.0
- crypto-js (npm): affected all versions; fixed in 4.2.0

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-2023-46233/ (Markdown: https://insights.sbomify.com/CVE-2023-46233/index.md)
```

## Sources

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

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