Forge: Denial of service in TLS record processing via call stack exhaustion

Ö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(), TLS record processing, process() to process the relevant input or security decision. node-forge processed received TLS records recursively, consuming one JavaScript stack frame per record in a single input chunk. A remote peer could send thousands of small records together and exhaust the call stack, causing an uncaught exception and denial of service. 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-hqq3-7jhf-c5jx Diğer
• github.com/…ommit/817e2ce0d0f6d8a25bc9c2670615c38a9ffdc51c Diğer
• github.com/digitalbazaar/forge/releases/tag/v1.4.1 Diğer

Kayıt geçmişi

1. 29 Eki 2026 22:19Yayı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
• 5,9 CVE-2026-119186Forge (node-forge) AES-GCM tagLength doğrulanmadığı için kimlik doğrulama atlatma açığı
• 7,5 CVE-2026-118782Forge: PKCS#12 MAC forgery and constant-key PBE via zero iteration count