Skip to content

Improper Verification of Cryptographic Signature in node-forge

High severity GitHub Reviewed Published Mar 17, 2022 in digitalbazaar/forge • Updated Nov 29, 2023

Package

npm node-forge (npm)

Affected versions

< 1.3.0

Patched versions

1.3.0

Description

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:

References

@davidlehn davidlehn published to digitalbazaar/forge Mar 17, 2022
Published by the National Vulnerability Database Mar 18, 2022
Published to the GitHub Advisory Database Mar 18, 2022
Reviewed Mar 18, 2022
Last updated Nov 29, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

EPSS score

0.098%
(42nd percentile)

Weaknesses

CVE ID

CVE-2022-24772

GHSA ID

GHSA-x4jg-mjrx-434g

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.