sm-crypto: Predictable SM2 key generation in Node.js: default RNG uses Math.random + wall clock
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| JuneAndGreen | sm-crypto | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Juneandgreen | Sm-crypto |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-vh45-f885-3848 | sm-crypto: Predictable SM2 key generation in Node.js: default RNG uses Math.random + wall clock |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.444% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Juneandgreen
Juneandgreen sm-crypto |
|
| Vendors & Products |
Juneandgreen
Juneandgreen sm-crypto |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | sm-crypto provides JavaScript implementations of the Chinese cryptographic algorithms SM2, SM3, and SM4. Prior to 0.5.0, the default no-argument sm2.generateKeyPairHex() path in Node.js uses the module-wide SecureRandom instance in src/sm2/utils.js, supplied by jsbn@1.1.0, which seeds an ARC4 stream from Math.random() and new Date().getTime() because window.crypto.getRandomValues is unavailable even though globalThis.crypto exists. An attacker who can observe the process's Math.random() outputs and estimate the key-generation time can reconstruct the seed, recover generated SM2 private keys, and predict signing ephemeral scalars used to forge signatures. This issue is fixed in version 0.5.0. | |
| Title | sm-crypto: Predictable SM2 key generation in Node.js: default RNG uses Math.random + wall clock | |
| Weaknesses | CWE-338 | |
| References |
| |
| Metrics |
cvssV3_1
|