Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| 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 |
Thu, 13 Aug 2026 18:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Juneandgreen
Juneandgreen sm-crypto |
|
| Vendors & Products |
Juneandgreen
Juneandgreen sm-crypto |
Thu, 13 Aug 2026 17:45:00 +0000
| 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
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-08-13T17:40:54.016Z
Reserved: 2026-08-12T20:53:46.381Z
Link: CVE-2026-73567
No data.
Status : Received
Published: 2026-08-13T18:18:19.387
Modified: 2026-08-13T18:18:19.387
Link: CVE-2026-73567
No data.
OpenCVE Enrichment
Updated: 2026-08-13T18:30:16Z
Github GHSA