Forge: TLS client crash when the server sends no certificate
- 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 TLS, is affected when its TLS client is used to connect to servers. A malicious server or on-path attacker can omit the server certificate, causing the client to crash and potentially terminate the process it runs in.
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 forge.tls.createConnection(), c.session.serverCertificate, RSA key exchange to process the relevant input or security decision. node-forge's TLS client checked the wrong property when deciding whether a server certificate was missing. A malicious TLS server or on-path peer could omit the Certificate message and reach code that dereferenced the absent certificate, causing an uncaught exception and terminating the connection or process. 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