CVE-2023-46233
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.
Does this matter?
High impact if exploited, but EPSS currently rates exploitation as unlikely (0.64%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit.
Description
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.
- CVSS 3.1
- 9.1 CRITICALCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
- EPSS
- 0.64% probability · 48th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-328, CWE-916, CWE-327
- Affected
- crypto-js project/crypto-js
- Source
- security-advisories@github.com
References
- https://github.com/brix/crypto-js/commit/421dd538b2d34e7c24a5b72cc64dc2b9167db40aPatch
- https://github.com/brix/crypto-js/security/advisories/GHSA-xwcq-pm8m-c4vfVendor Advisory
- https://lists.debian.org/debian-lts-announce/2023/11/msg00025.html
- https://github.com/brix/crypto-js/commit/421dd538b2d34e7c24a5b72cc64dc2b9167db40aPatch
- https://github.com/brix/crypto-js/security/advisories/GHSA-xwcq-pm8m-c4vfVendor Advisory
- https://lists.debian.org/debian-lts-announce/2023/11/msg00025.html
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.