CVE-2023-46233
crypto-js: PBKDF2 1,000 times weaker than specified in 1993 and 1.3M times weaker than current standard
Severity
ImportantRed Hat Product Security
CVSS 3.1
Review impact separately from score.
Published · October 25, 2023
Updated · August 5, 2026
Description
A vulnerability was found in crypto-js in how PBKDF2 is 1,000 times weaker than originally specified in 1993 and at least 1,300,000 times weaker than the current industry standard. This issue is because both default to SHA1, a cryptographic hash algorithm considered insecure since at least 2005, and default to one single iteration, a 'strength' or 'difficulty' value specified at 1,000 when specified in 1993. PBKDF2 relies on the iteration count as a countermeasure to preimage and collision attacks.
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.
CVSS score applicability
The CVSS score(s) listed for this vulnerability do not reflect the associated product's status, and are included for informational purposes to better understand the severity of this vulnerability.
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.
CVSS / CWE
CVSS 3.1 · 9.1CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
CWE-916 · Use of Password Hash With Insufficient Computational Effort