Forge: TLS client crash when the server sends no certificate

Özet

Türkçe özeti henüz hazır değil; şimdilik kaynağın kendi açıklamasını gösteriyoruz.

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.

Etkilenen sürümler1 yazılım

Kaynaklar5 kaynak

• CVE.org kaydı
• NVD kaydı
• github.com/…/forge/security/advisories/GHSA-525v-9gp9-w22h Diğer
• github.com/…ommit/7be9fbd40df2e2f15f29fea2846b1c87d58f6888 Diğer
• github.com/digitalbazaar/forge/releases/tag/v1.4.1 Diğer

Kayıt geçmişi

1. 29 Eki 2026 21:44Yayımlandı

İlgili açıklar

• 7,5 CVE-2026-119191Forge: ASN.1 resource exhaustion via BIT STRING decoding in asn1.fromDer
• 7,4 CVE-2026-119190Forge (node-forge): verifyCertificateChain üzerinde basicConstraints atlatma açığı
• 5,9 CVE-2026-119189Forge: X.509 pathLenConstraint not enforced by verifyCertificateChain() for CA certificates without keyUsage
• 7,5 CVE-2026-119188Forge: Denial of service in TLS record processing via a record interleaved with a fragmented handshake message
• 7,5 CVE-2026-119187Forge: Denial of service in TLS record processing via call stack exhaustion
• 5,9 CVE-2026-119186Forge (node-forge) AES-GCM tagLength doğrulanmadığı için kimlik doğrulama atlatma açığı