Improper Verification of Cryptographic Signature in node-forge

Description

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.

Recommendation

Update the node-forge package to the latest compatible version. Followings are version details:

• Affected version(s): < 1.3.0
• Patched version(s): 1.3.0

References

• GHSA-x4jg-mjrx-434g
• CVE-2022-24772
• CWE-347
• CAPEC-310
• OWASP 2021-A2
• OWASP 2021-A6

Related Issues

• node-forge has ASN.1 Unbounded Recursion - CVE-2025-66031
• node-forge has an Interpretation Conflict vulnerability via its ASN.1 Validator Desynchronization - CVE-2025-12816
• angular vulnerable to super-linear runtime due to backtracking - CVE-2024-21490
• Happy DOM: VM Context Escape can lead to Remote Code Execution - CVE-2025-61927

Tags:

npm

node-forge