Technical impact
The vulnerability occurs when the node-forge library incorrectly applies the RSA padding and RSASSA-PSS parameters from the issuer certificate instead of the child certificate being verified. As a result, a child certificate that declares the RSASSA-PSS signature algorithm may be accepted with a PKCS#1 v1.5 signature if the issuer uses PKCS#1 v1.5. This flaw does not allow a malicious actor to forge certificate identities because the signature must still be produced with the issuer’s private key. However it circumvents policies or audit checks that require the certificate chain to declare the same signature algorithm throughout the chain, potentially enabling a certificate formed to evade security checks.
Affected Systems
This issue affects the digitalbazaar:forge package (node-forge) and applies to any version prior to 1.4.1. Software that relies on node-forge for Transport Layer Security or certificate validation, such as custom TLS implementations in JavaScript environments, would be subject to the flaw until the library is upgraded.
Risk and Exploitability
The CVSS score of 3.7 classifies the risk as low, and the EPSS score of 0.00103 indicates a very low but nonzero exploitation probability. It is not listed in the CISA KEV catalog. The likely attack vector requires an attacker to supply a certificate chain to an application that uses node-forge for validation, and to control the issuer and child certificates to have mismatched signature algorithms. Because a valid private key must still be used, the vulnerability cannot be leveraged for privilege escalation or remote code execution, but it can break compliance and policy enforcement.
Github GHSA