Technical impact
The forge library contains a flaw where the verification routine can permanently delete trusted CA certificates from the store when certificates that share the same subject name are processed. The bug allows an attacker to supply a certificate chain that triggers this deletion, after which any subsequent verifications that rely on the removed CA will fail. The consequence is a persistent denial of service or availability degradation for applications that reuse the same CA store, though no direct information disclosure occurs.
Affected Systems
Digitalbazaar Forge (node-forge) is affected for all versions preceding 1.4.1 across platforms where the JavaScript TLS implementation is used. This includes any application that imports the forge library without specifying a later mandatory version.
Risk and Exploitability
The CVSS score of 3.7 indicates a low risk level, and the EPSS score is not available, providing no insight into current exploitation likelihood. The vulnerability is not listed in the CISA KEV catalog, so no confirmed exploit activity is known. Based on the description, the likely attack vector involves an attacker supplying a crafted certificate chain containing duplicate subject names to pki.verifyCertificateChain(), which could be done via a malicious TLS handshake or by imposing certificates onto a validation function. Because the deletion is permanent for that CA store instance, repeated or persistent use can lead to a denial of service for all future TLS operations that depend on the removed CA, resulting in a persistent availability degradation.
Github GHSA