Forge
Forge: RSA PKCS#1 v1.5 signature forgery via non-canonical DigestInfo encoding
Forge, also called node-forge, is a native implementation of Transport Layer Security in JavaScript. Prior to 1.4.1, publicKey.verify() with the default RSASSA-PKCS1-V1_5 scheme in lib/rsa.js parses the recovered DigestInfo with the lenient BER parser asn1.fromDer() and validates its structure with digestInfoValidator without requiring canonical DER bytes. Non-minimal or indefinite lengths, malformed parameter values, and non-canonical object identifier encodings with padded subidentifiers or trailing bytes can leave attacker-controlled data inside an accepted DigestInfo. When the verifying RSA public key uses a low exponent such as e=3, an attacker can use that encoding slack to forge a signature without the private key. The same path is used by X.509 certificate and PKCS#7 signature verification. This issue is fixed in version 1.4.1.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 1.4.1
Fixed in 1.4.1
Mitigation
Upgrade forge to 1.4.1 or later.
References
- Vendor advisory github.com/digitalbazaar/forge/security/adviso…
- Patch github.com/digitalbazaar/forge/commit/2bce9d47…
- Release notes github.com/digitalbazaar/forge/releases/tag/v1…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.