Repository navigation
🚨 [security] Update node-forge 1.3.3 → 1.4.3 (minor) - #255
Open
depfu[bot] wants to merge 1 commit into
Open
depfu[bot] wants to merge 1 commit into
depfu[bot] wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🚨 Your current dependencies have known security vulnerabilities 🚨
This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ node-forge (1.3.3 → 1.4.3) · Repo · Changelog
Security Advisories 🚨
🚨 Forge: TLS client crash on an unsupported ServerHello compression method
🚨 Forge: TLS client crash on a handshake record received without a session
🚨 Forge: ReDoS in forge.http response header and cookie trimming
🚨 Forge: Ed25519 signature verification accepts small-order public keys
🚨 Forge: RSA PKCS#1 v1.5 signature forgery via non-canonical DigestInfo encoding
🚨 Forge: ASN.1 resource exhaustion via BIT STRING decoding in asn1.fromDer
🚨 Forge: X.509 pathLenConstraint not enforced by verifyCertificateChain() for CA certificates without keyUsage
🚨 Forge: Incomplete PKCS#7 padding validation in AES/DES CBC and ECB decryption
🚨 Forge: Certificate signature verified with the issuer's RSA signature scheme
🚨 Forge: Prototype Pollution in forge.http cookie handling via a malicious Set-Cookie
🚨 Forge: ASN.1 OID first arc truncation in asn1.oidToDer
🚨 Forge: TLS client crash when the server sends no certificate
🚨 Forge: X.509 basicConstraints bypass in verifyCertificateChain() via deprecated extension OIDs 2.5.29.10 and 2.5.29.13
🚨 Forge: Denial of service in TLS record processing via call stack exhaustion
🚨 Forge: Denial of service in TLS record processing via a record interleaved with a fragmented handshake message
🚨 Forge: PKCS#12 MAC forgery and constant-key PBE via zero iteration count
🚨 Forge: AES-GCM authentication bypass via unvalidated tagLength option
🚨 Forge: verifyCertificateChain() removes trusted CA certificates with the same subject from the CA store
🚨 Forge: Denial of Service via infinite loop in BigInteger.modInverse() with negative input (incomplete fix of CVE-2026-33891)
🚨 Forge: Regular expression denial of service in PEM decoding (pem.decode)
🚨 Forge has Denial of Service via Infinite Loop in BigInteger.modInverse() with Zero Input
🚨 Forge has a basicConstraints bypass in its certificate chain verification (RFC 5280 violation)
🚨 Forge has signature forgery in Ed25519 due to missing S > L check
🚨 Forge has signature forgery in RSA-PKCS due to ASN.1 extra field
Release Notes
1.4.3 (from changelog)
1.4.2 (from changelog)
1.4.1 (from changelog)
1.4.0 (from changelog)
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase.All Depfu comment commands