Forge: RSA PKCS#1 v1.5 signature forgery via non-canonical DigestInfo encoding
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| digitalbazaar | forge | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Digitalbazaar | Forge |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-6qrw-m8cv-hcxf | Forge: RSA PKCS#1 v1.5 signature forgery via non-canonical DigestInfo encoding |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
No EPSS score available.
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Digitalbazaar
Digitalbazaar forge |
|
| Vendors & Products |
Digitalbazaar
Digitalbazaar forge |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Forge: RSA PKCS#1 v1.5 signature forgery via non-canonical DigestInfo encoding | |
| Weaknesses | CWE-347 | |
| References |
| |
| Metrics |
cvssV3_1
|