JuneAndGreen sm-crypto up to 0.4.x SM2 src/sm2/utils.js sm2.generateKeyPairHex random values

Summaryinfo

A vulnerability, which was classified as problematic, has been found in JuneAndGreen sm-crypto up to 0.4.x. This vulnerability affects the function sm2.generateKeyPairHex of the file src/sm2/utils.js of the component SM2. Performing a manipulation results in random values. This vulnerability was named CVE-2026-73567. The attack may be initiated remotely. There is no available exploit.

Detailsinfo

A vulnerability was found in JuneAndGreen sm-crypto up to 0.4.x. It has been classified as problematic. This affects the function sm2.generateKeyPairHex of the file src/sm2/utils.js of the component SM2. The manipulation with an unknown input leads to a random values vulnerability. CWE is classifying the issue as CWE-330. The product uses insufficiently random numbers or values in a security context that depends on unpredictable numbers. This is going to have an impact on confidentiality. The summary by CVE is:

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 [email protected], 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.

The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-73567 since 08/12/2026. The exploitability is told to be difficult. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1600.001 for this issue.

Upgrading to version 0.5.0 eliminates this vulnerability.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• JuneAndGreen

Name

• sm-crypto

Version

• 0.1
• 0.2
• 0.3
• 0.4

Website

• Product: https://github.com/JuneAndGreen/sm-crypto/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion