CVE-2020-367325.3MediumCWE-331
CVE-2020-36732: Crypto-Js Project vulnerability
Crypto-Js Project · Crypto-Js
Affected: Crypto-Js Project · Exploitation: possible (1 to 10%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
1.1%probability of exploitation in the next 30 days
65th percentile
050100
Higher than 65% of scored CVEs
5.3MediumCVSS 3.1
LowMediumHighCrit.
DescriptionCVE.org
The crypto-js package before 3.2.1 for Node.js generates random numbers by concatenating the string "0." with an integer, which makes the output more predictable than necessary.
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Possible (1 to 10%). EPSS between 1% and 10%.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Published
- June 2023
CoverageNo articles yet
No CyberSIXT article names CVE-2020-36732 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.
References
- NVD entrynvd.nist.gov
- CVE recordcve.org
- Weakness CWE-331cwe.mitre.org
- security.snyk.io/vuln/SNYK-JS-CRYPTOJS-548472security.snyk.io
- github.com/brix/crypto-js/pull/257/commits/e4ac157d8b75b962d6538github.com
- github.com/brix/crypto-js/issues/254github.com
- github.com/brix/crypto-js/issues/256github.com
- github.com/brix/crypto-js/compare/3.2.0...3.2.1github.com
- security.netapp.com/advisory/ntap-20230706-0003security.netapp.com