CVE-2022-24772 Improper Verification of Cryptographic Signature in `node-forge`

High 7.5 Published Updated

Attackers can forge RSA signatures by exploiting improper verification of cryptographic signatures in the node-forge library, bypassing security 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-24772?

CVE-2022-24772 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 does not check for tailing garbage bytes after decoding a `DigestInfo` ASN.1 structure. This can allow padding bytes to be removed and garbage data added 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-24772?

2 open source packages ship an affected version, including node-forge. It affects 1 product.

PackageAffectedFixed in
node-forge npmAll versions1.3.0
node-forge npmAll versions1.3.0

Products include Digitalbazaar Forge.

How do I fix CVE-2022-24772?

Upgrade node-forge to 1.3.0 or later.

Is CVE-2022-24772 being exploited?

There is no known exploitation of CVE-2022-24772 in the wild and no public exploit code.

Sources

Also known as DEBIAN-CVE-2022-24772, GHSA-x4jg-mjrx-434g, ROOT-APP-NPM-CVE-2022-24772, UBUNTU-CVE-2022-24772.

Is CVE-2022-24772 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free