Bug 2246369 (CVE-2023-46233) - CVE-2023-46233 crypto-js: PBKDF2 1,000 times weaker than specified in 1993 and 1.3M times weaker than current standard
Summary: CVE-2023-46233 crypto-js: PBKDF2 1,000 times weaker than specified in 1993 an...
Keywords:
Status: NEW
Alias: CVE-2023-46233
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 2246371
Blocks: 2246373
TreeView+ depends on / blocked
 
Reported: 2023-10-26 12:42 UTC by TEJ RATHI
Modified: 2024-02-26 05:49 UTC (History)
15 users (show)

Fixed In Version: crypto-js 4.2.0
Doc Type: If docs needed, set a value
Doc Text:
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.
Clone Of:
Environment:
Last Closed:
Embargoed:

Attachments (Terms of Use)

Description TEJ RATHI 2023-10-26 12:42:40 UTC 
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.

https://github.com/brix/crypto-js/security/advisories/GHSA-xwcq-pm8m-c4vf
https://github.com/brix/crypto-js/commit/421dd538b2d34e7c24a5b72cc64dc2b9167db40a
Note You need to log in before you can comment on or make changes to this bug.