CVE-2022-24771 Improper Verification of Cryptographic Signature in node-forge
Attackers can forge RSA signatures in node-forge due to lenient PKCS#1 v1.5 verification, bypassing cryptographic integrity checks.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2022-24771?
CVE-2022-24771 is a high-severity vulnerability in digitalbazaar forge, published on 18 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. Prior to version 1.3.0, RSA PKCS#1 v1.5 signature verification code is lenient in checking the digest algorithm structure. This can allow a crafted structure that steals padding bytes and uses unchecked portion of the PKCS#1 encoded message to forge a signature when a low public exponent is being used. The issue has been addressed in `node-forge` version 1.3.0. There are currently no known workarounds.
Weakness: CWE-347
Which versions are affected by CVE-2022-24771?
2 open source packages ship an affected version, including node-forge. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
node-forge npm | All versions | 1.3.0 |
node-forge npm | All versions | 1.3.0 |
Products include Digitalbazaar Forge.
How do I fix CVE-2022-24771?
Upgrade node-forge to 1.3.0 or later.
Is CVE-2022-24771 being exploited?
There is no known exploitation of CVE-2022-24771 in the wild and no public exploit code.
Other vulnerabilities in digitalbazaar forge
Sources
Also known as DEBIAN-CVE-2022-24771, GHSA-cfm4-qjh2-4765, ROOT-APP-NPM-CVE-2022-24771, UBUNTU-CVE-2022-24771.