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.
CVE-2023-46233
This critical-severity CVE scores 9.1 under NVD CVSS v3. EPSS exploit probability: 0.6%, top 53% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 9.1
- EG Score
- 9.1(medium)
- EG Risk
- 46(Track)EG Risk 46/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity91% × 45%Exploitation1% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 1%
- EPSS %ILE
- 48%
- KEV
- Not listed
Published
October 25, 2023
Last Modified
June 23, 2026
Advisory Details (3)
Auto-updated Sep 8, 2026[SECURITY] [DLA 3669-1] cryptojs security update
https://lists.debian.org/debian-lts-announce/2023/11/msg00025.htmlcrypto-js PBKDF2 1,000 times weaker than specified in 1993 and 1.3M times weaker than current standard · Advisory · brix/crypto-js · GitHub
https://github.com/brix/crypto-js/security/advisories/GHSA-xwcq-pm8m-c4vfcommit 421dd538b2d3 (brix/crypto-js)
Fix landed in brix/crypto-js commit 421dd538b2d3 — awaiting tagged release
https://github.com/brix/crypto-js/commit/421dd538b2d34e7c24a5b72cc64dc2b9167db40aVendor Advisories for CVE-2023-46233(6)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- RHSA-2024:0806Red Hat Product SecurityHigh
Red Hat Security Advisory: dotnet7.0 security update
- RHSA-2024:0805Red Hat Product SecurityHigh
Red Hat Security Advisory: dotnet7.0 security update
- RHSA-2024:0157Red Hat Product SecurityHigh
Red Hat Security Advisory: .NET 7.0 security update
- RHSA-2024:0158Red Hat Product SecurityHigh
Red Hat Security Advisory: .NET 6.0 security update
- RHSA-2024:0156Red Hat Product SecurityHigh
Red Hat Security Advisory: .NET 6.0 security update
- RHSA-2024:0151Red Hat Product SecurityHigh
Red Hat Security Advisory: .NET 7.0 security update
Patch Availability(7)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| ubuntu | libjs-cryptojs (3.1.2+dfsg-3ubuntu0.22.04.1~esm1) @ jammy | 2026-05-24 | ubuntu |
| redhat | dotnet7.0-0:7.0.116-1.el8_9 | 2024-02-13 | redhat |
| redhat | dotnet7.0-0:7.0.116-1.el9_3 | 2024-02-13 | redhat |
| redhat | dotnet7.0-0:7.0.115-1.el8_9 | 2024-01-10 | redhat |
| redhat | dotnet6.0-0:6.0.126-1.el9_3 | 2024-01-10 | redhat |
| redhat | dotnet7.0-0:7.0.115-1.el9_3 | 2024-01-10 | redhat |
| redhat | dotnet6.0-0:6.0.126-1.el8_9 | 2024-01-10 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(4 across 4 ecosystems)
Debian:10(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| cryptojs | 3.1.2+dfsg-2 | 3.1.2+dfsg-2+deb10u1 | — |
Debian:11(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| cryptojs | 3.1.2+dfsg-3, 3.1.2+dfsg-4 | — | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| cryptojs | 3.1.2+dfsg-3, 3.1.2+dfsg-4 | — | — |
npm(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| crypto-js | — | 4.2.0 | — |
Weakness Classification(3)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Additional Vendor Advisories
(1)
Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.
Data Freshness Timeline
(refreshed 10× in last 7d / 35× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 162 total refreshes for this CVE.
- 2026-09-07 15:59 UTCEPSS rescore
- 2026-09-06 13:46 UTCEPSS rescore
- 2026-09-06 13:45 UTCEPSS rescore
- 2026-09-05 15:26 UTCEPSS rescore
- 2026-09-04 13:58 UTCEPSS rescore
- 2026-09-04 05:04 UTCEPSS rescore
- 2026-09-03 14:29 UTCOSV refresh
- 2026-09-02 14:10 UTCEPSS rescore
- 2026-09-02 14:09 UTCEPSS rescore
- 2026-09-01 13:51 UTCEPSS rescore
- 2026-09-01 04:35 UTCEPSS rescore
- 2026-08-30 19:15 UTCEPSS rescore
- 2026-08-30 01:20 UTCEPSS rescore
- 2026-08-28 21:39 UTCEPSS rescore
- 2026-08-27 14:23 UTCEPSS rescore
- 2026-08-26 14:44 UTCEPSS rescore
- 2026-08-25 13:46 UTCEPSS rescore
- 2026-08-24 14:14 UTCEPSS rescore
- 2026-08-23 00:17 UTCEPSS rescore
- 2026-08-21 23:47 UTCEPSS rescore
- 2026-08-20 22:53 UTCEPSS rescore
- 2026-08-19 17:02 UTCEPSS rescore
- 2026-08-19 17:02 UTCEPSS rescore
- 2026-08-18 13:46 UTCEPSS rescore
- 2026-08-17 13:45 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-08-17 03:53 UTCOSV refresh
- 2026-08-16 14:54 UTCEPSS rescore
- 2026-08-16 02:12 UTCEPSS rescore
- 2026-08-15 01:28 UTCEPSS rescore
- 2026-08-13 21:58 UTCEPSS rescore
- 2026-08-12 13:49 UTCEPSS rescore
- 2026-08-11 13:40 UTCEPSS rescore
- 2026-08-10 23:57 UTCEPSS rescore
- 2026-08-09 13:44 UTCEPSS rescore
- 2026-08-09 13:44 UTCEPSS rescore
- 2026-08-08 16:35 UTCEPSS rescore
- 2026-08-07 16:25 UTCEPSS rescore
- 2026-08-06 13:45 UTCEPSS rescore
- 2026-08-05 19:15 UTCEPSS rescore
- 2026-08-04 15:07 UTCEPSS rescore
- 2026-08-04 10:35 UTCEPSS rescore
- 2026-08-03 10:34 UTCEPSS rescore
- 2026-08-03 10:34 UTCEPSS rescore
- 2026-08-02 02:25 UTCEPSS rescore
- 2026-08-02 02:25 UTCEPSS rescore
- 2026-08-01 22:36 UTCOSV refresh
- 2026-08-01 04:14 UTCEPSS rescore
- 2026-07-30 16:26 UTCEPSS rescore
- 2026-07-30 16:26 UTCEPSS rescore
- 2026-07-30 01:28 UTCEPSS rescore
- 2026-07-28 15:34 UTCEPSS rescore
- 2026-07-28 15:34 UTCEPSS rescore
- 2026-07-27 14:10 UTCEPSS rescore
- 2026-07-26 14:52 UTCEPSS rescore
- 2026-07-25 14:16 UTCEPSS rescore
- 2026-07-24 14:16 UTCEPSS rescore
- 2026-07-24 14:16 UTCEPSS rescore
- 2026-07-23 14:16 UTCEPSS rescore
- 2026-07-23 02:27 UTCEG score recompute
- 2026-07-22 23:14 UTCEG score recompute
- 2026-07-22 14:06 UTCEPSS rescore
- 2026-07-21 15:23 UTCEPSS rescore
- 2026-07-21 15:23 UTCEPSS rescore
- 2026-07-20 17:06 UTCEPSS rescore
- 2026-07-19 14:29 UTCEPSS rescore
- 2026-07-19 14:29 UTCEPSS rescore
- 2026-07-19 02:27 UTCEPSS rescore
- 2026-07-18 10:03 UTCEPSS rescore
- 2026-07-18 10:03 UTCEPSS rescore
- 2026-07-16 17:01 UTCEPSS rescore
- 2026-07-15 16:56 UTCEPSS rescore
- 2026-07-15 16:56 UTCEPSS rescore
- 2026-07-15 05:49 UTCOSV refresh
- 2026-07-15 01:59 UTCEPSS rescore
- 2026-07-15 01:59 UTCEPSS rescore
- 2026-07-13 22:28 UTCEPSS rescore
- 2026-07-13 22:28 UTCEPSS rescore
- 2026-07-13 06:11 UTCEPSS rescore
- 2026-07-13 06:11 UTCEPSS rescore
- 2026-07-12 05:45 UTCEPSS rescore
- 2026-07-11 08:26 UTCEPSS rescore
- 2026-07-09 19:08 UTCEPSS rescore
- 2026-07-08 15:13 UTCEPSS rescore
- 2026-07-07 13:44 UTCEPSS rescore
- 2026-07-07 13:44 UTCEPSS rescore
- 2026-07-06 16:26 UTCEPSS rescore
- 2026-07-06 16:26 UTCEPSS rescore
- 2026-07-06 02:22 UTCEPSS rescore
- 2026-07-05 02:29 UTCEPSS rescore
- 2026-07-04 06:29 UTCEPSS rescore
- 2026-07-04 06:29 UTCEPSS rescore
- 2026-07-02 16:59 UTCEPSS rescore
- 2026-07-01 15:05 UTCEPSS rescore
- 2026-06-30 23:21 UTCEPSS rescore
- 2026-06-30 23:21 UTCEPSS rescore
- 2026-06-29 14:05 UTCEPSS rescore
- 2026-06-28 14:06 UTCEPSS rescore
- 2026-06-28 14:06 UTCEPSS rescore
- 2026-06-28 04:55 UTCEPSS rescore
- 2026-06-27 06:04 UTCOSV refresh
Frequently asked(5)
What is CVE-2023-46233?
When was CVE-2023-46233 disclosed?
Is CVE-2023-46233 actively exploited?
What is the CVSS score of CVE-2023-46233?
How do I remediate CVE-2023-46233?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2023-46233
Is Your Infrastructure Affected by CVE-2023-46233?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.