CVE-2023-46233
CRITICALDescription
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.
How to fix
TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works
Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Exploit Intelligence
Moderate risk: more likely to be exploited than 47% of all known CVEs.
References
Related Vulnerabilities
Other CWE-328 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2004-2761 | Critical | 9.8 | 9.9% | - | - |
| CVE-2024-54143 | Unscored | - | 1.9% | - | - |
| CVE-2022-3433 | Medium | 6.5 | 0.7% | - | Fix |
| CVE-2022-29249 | High | 7.5 | 0.7% | - | - |
| CVE-2023-2900 | Low | 3.7 | 0.7% | - | - |
| CVE-2021-39182 | High | 7.5 | 0.5% | - | Fix |
Common questions
How do I fix CVE-2023-46233?
Published advisories record a fix for 66 affected products. The "How to fix" section on this page lists the fixed version and source advisory for each one, so apply the entry matching what you actually run.
Is CVE-2023-46233 being actively exploited?
Not that we know of. CVE-2023-46233 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.64% is the estimated probability that it will be exploited in the next 30 days. That is higher than 47% of all scored CVEs.
How severe is CVE-2023-46233?
CVE-2023-46233 has a CVSS v3 base score of 9.1, rated critical. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
What does CVE-2023-46233 affect?
Published advisories record a fix for aspnetcore-runtime-6.0 (Red Hat / RHEL), aspnetcore-runtime-6.0 (Rocky), aspnetcore-runtime-7.0 (Rocky), aspnetcore-runtime-7.0 (Red Hat / RHEL), and 62 more. Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.
Embed a live status badge for CVE-2023-46233
Markdown
[](https://tridentstack.com/cve/CVE-2023-46233)HTML
<a href="https://tridentstack.com/cve/CVE-2023-46233"><img src="https://tridentstack.com/cve/badge/CVE-2023-46233.svg" alt="CVE-2023-46233"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-06-23.