CVE-2022-24771
published 2022-03-18CVE-2022-24771: 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…
PriorityP338high7.5CVSS 3.1
AVNACLPRNUINSUCNIHAN
EPSS
0.72%
49.7th percentile
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.
Affected
4 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | node-node-forge | < node-node-forge 0.10.0~dfsg-3+deb11u1 (bullseye) | node-node-forge 0.10.0~dfsg-3+deb11u1 (bullseye) |
| digitalbazaar | forge | < 1.4.0 | 1.4.0 |
| digitalbazaar | forge | < 1.3.0 | 1.3.0 |
| digitalbazaar | forge | < 1.4.0 | 1.4.0 |
CVSS provenance
nvdv3.17.5HIGHCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
nvdv2.05.0MEDIUMAV:N/AC:L/Au:N/C:N/I:P/A:N
ghsa7.5HIGH
osv7.5HIGH
vendor_debian7.5HIGH
vendor_redhat7.5HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
node-forge: Forge: Signature Forgery via Weak RSASSA PKCS#1 v1.5 Verification
vendor_redhat·2026-03-27·CVSS 7.5
CVE-2026-33894 [HIGH] CWE-347 node-forge: Forge: Signature Forgery via Weak RSASSA PKCS#1 v1.5 Verification
node-forge: Forge: Signature Forgery via Weak RSASSA PKCS#1 v1.5 Verification
Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. Prior to version 1.4.0, RSASSA PKCS#1 v1.5 signature verification accepts forged signatures for low public exponent keys (e=3). Attackers can forge signatures by stuffing “garbage” bytes within the ASN structure in order to construct a signature that passes verification, enabling Bleichenbacher style forgery. This issue is similar to CVE-2022-24771, but adds bytes in an addition field within the ASN structure, rather than outside of it. Additionally, forge does not validate that signatures include a minimum of 8 bytes of padding as defined by the specification, providing attackers additional space to construct
Red Hat
node-forge: Signature verification leniency in checking `digestAlgorithm` structure can lead to signature forgery
vendor_redhat·2022-03-18·CVSS 7.5
CVE-2022-24771 [HIGH] CWE-347 node-forge: Signature verification leniency in checking `digestAlgorithm` structure can lead to signature forgery
node-forge: Signature verification leniency in checking `digestAlgorithm` structure can lead to signature forgery
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.
A flaw was found in the node-forge package. This signature verification leniency allows an attacker to forge a signature.
Statement: This flaw affects the DigestAlgorithm str
Debian
CVE-2022-24771: node-node-forge - Forge (also called `node-forge`) is a native implementation of Transport Layer S...
vendor_debian·2022·CVSS 7.5
CVE-2022-24771 [HIGH] CVE-2022-24771: node-node-forge - Forge (also called `node-forge`) is a native implementation of Transport Layer S...
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.
Scope: local
bullseye: resolved (fixed in 0.10.0~dfsg-3+deb11u1)
OSV
CVE-2026-33894: Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript
osv·2026-03-27·CVSS 7.5
CVE-2026-33894 [HIGH] CVE-2026-33894: Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript
Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. Prior to version 1.4.0, RSASSA PKCS#1 v1.5 signature verification accepts forged signatures for low public exponent keys (e=3). Attackers can forge signatures by stuffing “garbage” bytes within the ASN structure in order to construct a signature that passes verification, enabling Bleichenbacher style forgery. This issue is similar to CVE-2022-24771, but adds bytes in an addition field within the ASN structure, rather than outside of it. Additionally, forge does not validate that signatures include a minimum of 8 bytes of padding as defined by the specification, providing attackers additional space to construct Bleichenbacher forgeries. Version 1.4.0 patches the issue.
OSV
Forge has signature forgery in RSA-PKCS due to ASN.1 extra field
osv·2026-03-26·CVSS 7.5
CVE-2026-33894 [HIGH] Forge has signature forgery in RSA-PKCS due to ASN.1 extra field
Forge has signature forgery in RSA-PKCS due to ASN.1 extra field
## Summary
RSASSA PKCS#1 v1.5 signature verification accepts forged signatures for low public exponent keys (e=3). Attackers can forge signatures by stuffing “garbage” bytes within the ASN structure in order to construct a signature that passes verification, enabling [Bleichenbacher style forgery](https://mailarchive.ietf.org/arch/msg/openpgp/5rnE9ZRN1AokBVj3VqblGlP63QE/). This issue is similar to [CVE-2022-24771](https://github.com/digitalbazaar/forge/security/advisories/GHSA-cfm4-qjh2-4765), but adds bytes in an addition field within the ASN structure, rather than outside of it.
Additionally, forge does not validate that signatures include a minimum of 8 bytes of padding as [defined by the specification](https://datatrack
GHSA
Forge has signature forgery in RSA-PKCS due to ASN.1 extra field
ghsa·2026-03-26·CVSS 7.5
CVE-2026-33894 [HIGH] CWE-20 Forge has signature forgery in RSA-PKCS due to ASN.1 extra field
Forge has signature forgery in RSA-PKCS due to ASN.1 extra field
## Summary
RSASSA PKCS#1 v1.5 signature verification accepts forged signatures for low public exponent keys (e=3). Attackers can forge signatures by stuffing “garbage” bytes within the ASN structure in order to construct a signature that passes verification, enabling [Bleichenbacher style forgery](https://mailarchive.ietf.org/arch/msg/openpgp/5rnE9ZRN1AokBVj3VqblGlP63QE/). This issue is similar to [CVE-2022-24771](https://github.com/digitalbazaar/forge/security/advisories/GHSA-cfm4-qjh2-4765), but adds bytes in an addition field within the ASN structure, rather than outside of it.
Additionally, forge does not validate that signatures include a minimum of 8 bytes of padding as [defined by the specification](https://datatrack
GHSA
Improper Verification of Cryptographic Signature in node-forge
ghsa·2022-03-18
CVE-2022-24771 [HIGH] CWE-347 Improper Verification of Cryptographic Signature in node-forge
Improper Verification of Cryptographic Signature in node-forge
### Impact
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.
### 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"](https://mailarchive.ietf.org/arch/msg/openpgp/5rnE9ZRN1AokBVj3VqblGlP63QE/)
by Hal Finney.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [forge](https://github.com/digitalbazaar/forge)
* Email u
OSV
CVE-2022-24771: Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript
osv·2022-03-18·CVSS 7.5
CVE-2022-24771 [HIGH] CVE-2022-24771: Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript
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.
OSV
Improper Verification of Cryptographic Signature in node-forge
osv·2022-03-18
CVE-2022-24771 [HIGH] Improper Verification of Cryptographic Signature in node-forge
Improper Verification of Cryptographic Signature in node-forge
### Impact
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.
### 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"](https://mailarchive.ietf.org/arch/msg/openpgp/5rnE9ZRN1AokBVj3VqblGlP63QE/)
by Hal Finney.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [forge](https://github.com/digitalbazaar/forge)
* Email u
No detection rules found.
No public exploits indexed.
https://github.com/digitalbazaar/forge/commit/3f0b49a0573ef1bb7af7f5673c0cfebf00424df1https://github.com/digitalbazaar/forge/security/advisories/GHSA-cfm4-qjh2-4765https://github.com/digitalbazaar/forge/commit/3f0b49a0573ef1bb7af7f5673c0cfebf00424df1https://github.com/digitalbazaar/forge/security/advisories/GHSA-cfm4-qjh2-4765
2022-03-18
Published