Forge: verifyCertificateChain() removes trusted CA certificates with the same subject from the CA store
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.4.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Forge (node-forge), a JavaScript implementation of Transport Layer Security, is affected when applications use its certificate chain verification with a CA store containing certificates that share a subject name. A failed verification can permanently remove trusted CA certificates from that store, so later valid certificate chains are rejected, causing a lasting availability problem for applications that reuse the store.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to 1.4.1, the affected implementation used pki.verifyCertificateChain(), pki.createCaStore(), duplicate subject names to process the relevant input or security decision. node-forge modified the CA store while trying certificates that shared a subject name during pki.verifyCertificateChain(). A failed chain verification could permanently remove trusted CA certificates from the store, causing later valid chains to fail and creating a persistent availability impact for applications that reused the store. This issue is fixed in version 1.4.1.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- digitalbazaar forge
fixed in 1.4.1