CVE-2020-36732: crypto-js uses insecure random numbers
(updated )
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.
References
- github.com/advisories/GHSA-3w3w-pxmm-2w2j
- github.com/brix/crypto-js
- github.com/brix/crypto-js/commit/b405ff597fb3ac76a7bdfbc72dca10ba1079b1d5
- github.com/brix/crypto-js/commit/e4ac157d8b75b962d6538fc0b996e5d4d5a9466b
- github.com/brix/crypto-js/compare/3.2.0...3.2.1
- github.com/brix/crypto-js/issues/254
- github.com/brix/crypto-js/issues/256
- github.com/brix/crypto-js/pull/257/commits/e4ac157d8b75b962d6538fc0b996e5d4d5a9466b
- nvd.nist.gov/vuln/detail/CVE-2020-36732
- security.netapp.com/advisory/ntap-20230706-0003
- security.snyk.io/vuln/SNYK-JS-CRYPTOJS-548472
Code Behaviors & Features
Detect and mitigate CVE-2020-36732 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Dependency Scanning using SBOM also detects vulnerabilities from proprietary advisories that this site does not include. Learn more about Dependency Scanning using SBOM →