Source: cryptojs Version: 3.1.2+dfsg-3 Severity: grave Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team <t...@security.debian.org>
Hi, The following vulnerability was published for cryptojs. CVE-2023-46233[0]: | 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. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2023-46233 https://www.cve.org/CVERecord?id=CVE-2023-46233 [1] https://github.com/brix/crypto-js/security/advisories/GHSA-xwcq-pm8m-c4vf [2] https://github.com/brix/crypto-js/commit/421dd538b2d34e7c24a5b72cc64dc2b9167db40a Regards, Salvatore
