Search for packages
| purl | pkg:npm/crypto-js@3.2.0 |
| Vulnerability | Summary | Fixed by |
|---|---|---|
|
VCID-asxw-e1d3-ckau
Aliases: CVE-2023-46233 GHSA-xwcq-pm8m-c4vf |
crypto-js PBKDF2 1,000 times weaker than specified in 1993 and 1.3M times weaker than current standard 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. |
Affected by 0 other vulnerabilities. |
|
VCID-ej8z-tdd9-ubhg
Aliases: CVE-2020-36732 GHSA-3w3w-pxmm-2w2j |
crypto-js uses insecure random numbers The crypto-js package 3.2.0 for Node.js generates random numbers by concatenating the string "0." with an integer, which makes the output more predictable than necessary. |
Affected by 1 other vulnerability. |
|
VCID-grhg-jqy6-xff2
Aliases: GMS-2020-4 |
Insufficient Entropy An attacker is able to guess generated digits due to insufficient entropy. |
Affected by 1 other vulnerability. Affected by 1 other vulnerability. |
| Vulnerability | Summary | Aliases |
|---|---|---|
| This package is not known to fix vulnerabilities. | ||