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

Published Mar 18, 2022
·
Updated

Impact

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.

Patches

The issue has been addressed in node-forge 1.3.0.

References

For more information, please see "Bleichenbacher's RSA signature forgery based on implementation error" by Hal Finney.

For more information

If you have any questions or comments about this advisory: Open an issue in forge Email us at example email address

Other sources

A flaw was found in the node-forge package. This signature verification leniency allows an attacker to forge a signature.

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.

Affected Software

3 affected componentsFixes available
redhat/node-forge<1.3.0
1.3.0
npm/node-forge<1.3.0
1.3.0
digitalbazaar Forge Node.js<1.3.0

Event History

Mar 18, 2022
CVE Published
12:00 AM
Data Sourced
12:00 AM
RemedyDescriptionSeverityWeaknessAffected Software
CVE Published
via MITRE·01:30 PM
Data Sourced
via MITRE·01:30 PM
DescriptionSeverityWeakness
Advisory Published
via GitHub·11:10 PM
Mar 23, 2022
Data Sourced
via Red Hat·08:38 PM
DescriptionSeverityAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2022-24772?

CVE-2022-24772 is considered to have a high severity due to the potential for signature forgery.

2

How do I fix CVE-2022-24772?

To fix CVE-2022-24772, update the node-forge package to version 1.3.0 or later.

3

What software is affected by CVE-2022-24772?

CVE-2022-24772 affects node-forge versions prior to 1.3.0 across various sources including Red Hat and npm.

4

What type of vulnerability is CVE-2022-24772?

CVE-2022-24772 is a cryptographic vulnerability related to RSA PKCS#1 v1.5 signature verification.

5

Can CVE-2022-24772 be exploited remotely?

Yes, CVE-2022-24772 can be exploited remotely if an attacker can send crafted inputs to a vulnerable system.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203