CVE-2020-36732

crypto-js uses insecure random numbers

5.3 MediumFix available

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.

Attack profile

How easy it is to exploit

Attack vector: Network
Complexity: Low
Privileges needed: None
User interaction: None

What an attacker can affect

Confidentiality: Low
Integrity: None
Availability: None

Exploit likelihood

1.07%Up 1.0 points since Jun 12, 2023

What each source reports

NVD Score used 5.3

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.

Record: CVE-2020-36732
CVSS 3.1: 5.3 MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Weakness: CWE-330, CWE-331
Updated: 2026-11-02

CVE List 5.3

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.

Record: CVE-2020-36732
CVSS 3.1: 5.3 MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Weakness: CWE-331
Updated: 2026-11-02

EUVDEUVD-2023-1673 5.3

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.

Record: EUVD-2023-1673
CVSS 3.1: 5.3 MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Updated: 2026-11-03

GitHub AdvisoriesGHSA-3w3w-pxmm-2w2j 5.3

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.

Record: GHSA-3w3w-pxmm-2w2j
CVSS 3.1: 5.3 MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Weakness: CWE-330, CWE-331
Updated: 2026-11-02

OSV 5.3

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.

Record: CVE-2020-36732
CVSS 3.1: 5.3 MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Updated: 2026-11-02

OSVDEBIAN-CVE-2020-36732 5.3

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.

Record: DEBIAN-CVE-2020-36732
CVSS 3.1: 5.3 MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Updated: 2026-11-02

OSVGHSA-3w3w-pxmm-2w2j 5.3

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.

Record: GHSA-3w3w-pxmm-2w2j
CVSS 3.1: 5.3 MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Weakness: CWE-330, CWE-331
Updated: 2026-11-02

Affected products

crypto-js project crypto-js

Affected packages

Affected packages
Package	Affected	Fixed
`crypto-js` npm	3.2.0 to 3.2.0	3.2.1
`cryptojs` Debian:12	All versions, plus listed versions 3.1.2+dfsg-33.1.2+dfsg-4	None known
`crypto-js` npm	3.2.0 up to 3.2.1	3.2.1

History

History
Recorded	Changed	Sources
Nov 3, 2026	aliases	EUVD
Nov 2, 2026	first indexed	CVE List, GitHub Advisories, NVD, OSV

Dates are when Every CVE recorded each change. Upstream dates may differ.

In short

CVE-2020-36732 is a medium vulnerability (CVSS 5.3) in Crypto-js Project Crypto-js, published June 12, 2023. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 1.07%, the 65th percentile. Fixed in crypto-js 3.2.1.

References

Show 6 moreShow less