Critical Predictable Key Flaw in sm-crypto

A critical vulnerability, identified as GHSA-vh45-f885-3848, has been discovered in the sm-crypto npm package. The flaw stems from a predictable random number generation process, which allows an attacker to derive SM2 private keys and signing ephemeral scalars, effectively breaking the cryptographic security of the library.

This issue affects version 0.4.0 of the sm-crypto package. Because this is the default behavior of the library, no specific configuration or user error is required to trigger the vulnerability; any implementation relying on the default key generation path is inherently insecure.

What's at Risk

The vulnerability impacts any Node.js application utilizing sm-crypto version 0.4.0. Organizations and developers who have integrated this library into their backend services, authentication systems, or data signing pipelines are at risk. Because the key generation process is deterministic under certain conditions, any system relying on these keys for identity verification or data encryption may be compromised.

The risk is particularly high for internet-facing systems that expose cryptographic functions to user input or automated processes. If an attacker can observe the output of these functions, they may be able to reconstruct the private keys used by the application, leading to unauthorized access or the forging of digital signatures.

How the Flaw Works

In general, cryptographic libraries rely on a Cryptographically Secure Pseudo-Random Number Generator (CSPRNG) to ensure that keys are unique and impossible to guess. When a system fails to access a secure entropy source, it may fall back to predictable inputs, such as system timestamps or standard non-cryptographic random functions. This class of weakness is known as a PRNG flaw.

When a library uses predictable sources to seed its keys, it creates a limited search space for an attacker. By observing a small number of outputs from the system, an attacker can often calculate the internal state of the generator. Once the state is known, the attacker can predict future outputs, including private keys and ephemeral scalars, rendering the encryption or signature scheme useless.

How to Protect Your Systems

• Update the sm-crypto package to version 0.5.0 or later immediately to resolve the entropy source issue.
• Audit any existing keys generated by version 0.4.0, as these should be considered compromised and should be revoked or rotated.
• Ensure that your production environment properly exposes Web Crypto APIs if your dependencies rely on them for secure random number generation.
• Implement regular dependency scanning in your CI/CD pipelines to catch vulnerable versions of libraries before they reach production.
• Monitor application logs for unusual cryptographic errors or patterns that might indicate an attempt to exploit weak key generation.

The severity of this vulnerability, rated at 9.1 (Critical), highlights the necessity of using robust, well-vetted cryptographic primitives. Because the flaw exists in the default execution path, the potential for widespread impact is significant. Promptly updating to the patched version is the only effective way to mitigate this risk and ensure the integrity of your cryptographic operations.