cve.bz

CVE-2023-46233 crypto-js project crypto-js: Use of Weak Hash

9.1 criticalEPSS 0.6%Fix available

Critical (9.1) in crypto-js project crypto-js. EPSS 0.6% estimated probability of exploitation activity in the next 30 days. Fixed in crypto-js 4.2.0.

On this page
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.

Severity

CVSS 3.1

9.1 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS
0.6% (unchanged from 0.6% a week ago; 0.6% 30 days ago) estimated probability of exploitation activity in the next 30 days; 52nd percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: total, assessed 2025-06-03. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-327 Use of a Broken or Risky Cryptographic Algorithm
CWE-328 Use of Weak Hash
CWE-916 Use of Password Hash With Insufficient Computational Effort
OWASP Top 10
A04:2025 Cryptographic Failures
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2023-46233 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2023-46233?via=ask-ai-copy and https://cve.bz/cve/CVE-2023-46233?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2023-46233 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
crypto-js_project:crypto-jsbefore 4.2.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-xwcq-pm8m-c4vfnpmcrypto-js<4.2.04.2.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian10cryptojs3.1.2+dfsg-2+deb10u1DLA-3669-1
Debian12cryptojsno fix listedDEBIAN-CVE-2023-46233
Ubuntu20.04:LTScryptojs3.1.2+dfsg-2ubuntu0.20.04.1UBUNTU-CVE-2023-46233 USN-6753-1
UbuntuPro:16.04:LTScryptojs3.1.2+dfsg-2ubuntu0.16.04.1~esm1UBUNTU-CVE-2023-46233 USN-6753-1
UbuntuPro:18.04:LTScryptojs3.1.2+dfsg-2ubuntu0.18.04.1~esm1UBUNTU-CVE-2023-46233 USN-6753-1
UbuntuPro:22.04:LTScryptojs3.1.2+dfsg-3ubuntu0.22.04.1~esm1UBUNTU-CVE-2023-46233 USN-6753-1
Red Hatenterprise_linux:8::appstreamdotnet-hostfxr-6.0, dotnet-runtime-6.0, aspnetcore-runtime-6.0 and 6 more0:6.0.26-1.el8_9RHSA-2024:0158
Red Hatenterprise_linux:8::appstreamdotnet-hostfxr-7.0, dotnet-runtime-7.0, aspnetcore-runtime-7.0 and 6 more0:7.0.15-1.el8_9RHSA-2024:0157
Red Hatenterprise_linux:8::appstreamdotnet-hostfxr-7.0, dotnet-runtime-7.0, aspnetcore-runtime-7.0 and 6 more0:7.0.16-1.el8_9RHSA-2024:0806
Red Hatenterprise_linux:8::appstreamdotnet6.0, dotnet-sdk-6.0, dotnet6.0-debuginfo and 3 more0:6.0.126-1.el8_9RHSA-2024:0158
Red Hatenterprise_linux:8::appstreamdotnet7.0, dotnet-sdk-7.0, dotnet7.0-debuginfo and 3 more0:7.0.115-1.el8_9RHSA-2024:0157
Red Hatenterprise_linux:8::appstreamdotnet7.0, dotnet-sdk-7.0, dotnet7.0-debuginfo and 3 more0:7.0.116-1.el8_9RHSA-2024:0806
Red Hatenterprise_linux:8::crbdotnet-hostfxr-6.0-debuginfo, dotnet-runtime-6.0-debuginfo, dotnet-apphost-pack-6.0-debuginfo0:6.0.26-1.el8_9RHSA-2024:0158
Red Hatenterprise_linux:8::crbdotnet-hostfxr-7.0-debuginfo, dotnet-runtime-7.0-debuginfo, dotnet-apphost-pack-7.0-debuginfo0:7.0.15-1.el8_9RHSA-2024:0157
Red Hatenterprise_linux:8::crbdotnet-hostfxr-7.0-debuginfo, dotnet-runtime-7.0-debuginfo, dotnet-apphost-pack-7.0-debuginfo0:7.0.16-1.el8_9RHSA-2024:0806
Red Hatenterprise_linux:8::crbdotnet6.0-debuginfo, dotnet6.0-debugsource, dotnet-sdk-6.0-debuginfo and 1 more0:6.0.126-1.el8_9RHSA-2024:0158
Red Hatenterprise_linux:8::crbdotnet7.0-debuginfo, dotnet7.0-debugsource, dotnet-sdk-7.0-debuginfo and 1 more0:7.0.115-1.el8_9RHSA-2024:0157
Red Hatenterprise_linux:8::crbdotnet7.0-debuginfo, dotnet7.0-debugsource, dotnet-sdk-7.0-debuginfo and 1 more0:7.0.116-1.el8_9RHSA-2024:0806
12 more for Red Hat in the JSON and on Red Hat's page.

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat.

Red Hat

Red Hat rates this Important.

Red Hat's statement

The vulnerability in crypto-js's PBKDF2 implementation represents a important CVE issue due to its fundamental impact on cryptographic security. PBKDF2 is widely used for password protection and signature generation, making it a core component of many security-critical systems. However, the default settings in crypto-js result in significantly weaker security than industry standards, with the algorithm being 1,000 times weaker than originally specified in 1993 and millions of times weaker than current recommendations. This weakness stems from the use of the insecure SHA1 hash algorithm and the default of only one iteration, both of which greatly diminish the resistance against various attacks. Consequently, attackers can exploit this vulnerability to create identical cryptographic signatures, potentially gaining unauthorized access to sensitive information or compromising system integrity. Given the widespread use of crypto-js and the important role of PBKDF2 in cryptographic operations, addressing this vulnerability is paramount to safeguarding against security breaches and maintaining trust in digital systems.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 8dotnet7.0-0:7.0.115-1.el8_9Fixed 2024-01-10RHSA-2024:0157
Red Hat Enterprise Linux 8dotnet6.0-0:6.0.126-1.el8_9Fixed 2024-01-10RHSA-2024:0158
Red Hat Enterprise Linux 8dotnet7.0-0:7.0.116-1.el8_9Fixed 2024-02-13RHSA-2024:0806
Red Hat Enterprise Linux 9dotnet7.0-0:7.0.115-1.el9_3Fixed 2024-01-10RHSA-2024:0151
Red Hat Enterprise Linux 9dotnet6.0-0:6.0.126-1.el9_3Fixed 2024-01-10RHSA-2024:0156
Red Hat Enterprise Linux 9dotnet7.0-0:7.0.116-1.el9_3Fixed 2024-02-13RHSA-2024:0805
.NET 6.0 on Red Hat Enterprise Linuxrh-dotnet60-dotnetOut of support scope
Red Hat build of Apicurio Registry 2crypto-jsAffected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2023-46233.

Attack patterns (CAPEC)

  • CAPEC-55 Rainbow Table Password Cracking Likelihood: Medium · Severity: Medium
  • CAPEC-68 Subvert Code-signing Facilities Likelihood: Low · Severity: Very High
  • CAPEC-461 Web Services API Signature Forgery Leveraging Hash Function Extension Weakness Severity: High
  • CAPEC-20 Encryption Brute Forcing Likelihood: Low · Severity: Low
  • CAPEC-97 Cryptanalysis Likelihood: Low · Severity: Very High
  • CAPEC-459 Creating a Rogue Certification Authority Certificate Likelihood: Medium · Severity: Very High
  • CAPEC-473 Signature Spoof
  • CAPEC-475 Signature Spoofing by Improper Validation Likelihood: Low · Severity: High
  • CAPEC-608 Cryptanalysis of Cellular Encryption Severity: High
  • CAPEC-614 Rooting SIM Cards Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON