Forge: TLS client crash when the server sends no certificate

[ Why it matters ]Priority signals

• Public proof-of-concept exploit exists (CISA SSVC)

[ Description ]Official 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.

[ Fixes ]Fixes and patches

• node-forge 1.4.1Fixed version · GitHub Advisories · npm package node-forge: upgrade to 1.4.1 or later (affected <= 1.4.0)

[ Packages ]Affected open-source packages

• node-forge npmAffected <= 1.4.0 · fixed in 1.4.1 · GHSA-525v-9gp9-w22h

[ References ]References

• github.com/digitalbazaar/forge/commit/7be9fbd40df2e2f15f29fea2846b1c87d58f6888
• github.com/digitalbazaar/forge/releases/tag/v1.4.1
• github.com/digitalbazaar/forge/security/advisories/GHSA-525v-9gp9-w22h