HIGH: X.509 certificate chain verification ignores name constraints.
pki.verifyCertificateChain() does not check the nameConstraints
extension (RFC 5280 4.2.1.10). A non-critical nameConstraints extension
in a CA certificate is ignored, so a name-constrained intermediate CA can
issue certificates for names outside its permitted subtrees, or inside
its excluded subtrees, and the chain verifies. Exploitation requires the
private key of a name-constrained CA that chains to a trusted root. A
critical nameConstraints extension is rejected as an unsupported critical
extension.
MODERATE: TLS client crash on a handshake record without a session.
A TLS client throws an uncaught TypeError from process() when it
receives a ServerHello while it has no session: after a close_notify
alert or a call to close(), or before handshake() is called. A
malicious server, or an on-path attacker, can terminate a Node.js process
that passes socket data to process() without catching exceptions.
Servers are not affected.
MODERATE: ReDoS in forge.http response header parsing.
forge.http trims response header and Set-Cookie values with a
regular expression that takes quadratic time on a long run of whitespace
followed by another character. A server, or an on-path attacker, can
block a forge.http client for minutes with one large header.
MODERATE: TLS client crash on an unsupported ServerHello compression
method.
A TLS client accepts any compression method in the ServerHello,
although it only offers no compression. An unknown method makes process() throw an uncaught Error at ServerHelloDone, before the
server is authenticated. A malicious server, or an on-path attacker, can
terminate a Node.js process that passes socket data to process()
without catching exceptions, including through forge.tls.wrapSocket.
Servers are not affected.
LOW: Ed25519 signature verification accepts small-order public keys.
ed25519.verify() does not reject public keys of small order, such as
the identity point. Under such a key, a signature with S = 0 and a
small-order R verifies for many or, with the identity key, all
messages, without any private key. Applications are affected only if
they verify signatures against a public key an attacker can choose and
rely on the signature being bound to the message. Signatures made with
keys from ed25519.generateKeyPair() or other honest key generation are
not affected.
[x509] Parse the nameConstraints extension (2.5.29.30) into permittedSubtrees, excludedSubtrees and unsupportedSubtreeRange. An
invalid value is left unparsed.
Fixed
[ed25519] Reject small-order public keys in ed25519.verify().
[x509] Enforce nameConstraints in verifyCertificateChain() for the
subject and subjectAltName rfc822Name, dNSName, directoryName,
uniformResourceIdentifier and iPAddress names of each certificate, using
the constraints of the CA certificates above it and of the trust anchor.
Violations fail with bad_certificate, and the error has nameType and nameValue. Critical nameConstraints are no longer rejected as
unsupported. As in OpenSSL:
The commonName values of an end-entity certificate without a dNSName
subjectAltName are checked as dNSNames when they look like host names.
directoryName values are compared ignoring ASCII case and extra
whitespace.
Constraints that can't be evaluated for a name of the same type, names
that can't be checked against a constraint of the same type, and more
than 2^20 name and subtree comparisons for a chain fail with unsupported_certificate.
NOTE: Chains with a non-critical nameConstraints extension that the
names below it violate now fail verification. Chains with a critical
nameConstraints extension now verify when the names are within the
constraints, instead of always failing. A verify callback can still
override any error.
[tls] Ignore handshake messages received by a client without a session
instead of throwing a TypeError.
[http] Trim header and cookie values in linear time.
[tls] Fail a client handshake with an illegal_parameter alert when the
ServerHello selects a compression method other than none.
[pem] Convert non-string input to a string in pem.decode() as before
1.4.1. The 1.4.1 PEM ReDoS fix (GHSA-7wch-p9px-956x) caused a TypeError
for Buffer input, which is used by node-jose.
(#1165)
Configuration
📅Schedule: (UTC)
Branch creation
At any time (no schedule defined)
Automerge
At any time (no schedule defined)
🚦Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕Ignore: Close this PR and you won't be reminded about this update again.
If you want to rebase/retry this PR, check this box
This PR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| [node-forge](https://github.com/digitalbazaar/forge) | pnpm-workspace.overrides | patch | [`1.4.1` → `1.4.3`](https://renovatebot.com/diffs/npm/node-forge/1.4.1/1.4.3) |
---
### Release Notes
<details>
<summary>digitalbazaar/forge (node-forge)</summary>
### [`v1.4.3`](https://github.com/digitalbazaar/forge/blob/HEAD/CHANGELOG.md#143---2026-11-03)
[Compare Source](https://github.com/digitalbazaar/forge/compare/v1.4.2...v1.4.3)
##### Security
- **HIGH**: X.509 certificate chain verification ignores name constraints.
- `pki.verifyCertificateChain()` does not check the nameConstraints
extension (RFC 5280 4.2.1.10). A non-critical nameConstraints extension
in a CA certificate is ignored, so a name-constrained intermediate CA can
issue certificates for names outside its permitted subtrees, or inside
its excluded subtrees, and the chain verifies. Exploitation requires the
private key of a name-constrained CA that chains to a trusted root. A
critical nameConstraints extension is rejected as an unsupported critical
extension.
- Reported by [@​bhaswanthc](https://github.com/bhaswanthc).
- CVE ID: [CVE-TBD]()
- GHSA ID: [GHSA-3cc4-3294-vgjf](https://github.com/digitalbazaar/forge/security/advisories/GHSA-3cc4-3294-vgjf)
- **MODERATE**: TLS client crash on a handshake record without a session.
- A TLS client throws an uncaught `TypeError` from `process()` when it
receives a ServerHello while it has no session: after a `close_notify`
alert or a call to `close()`, or before `handshake()` is called. A
malicious server, or an on-path attacker, can terminate a Node.js process
that passes socket data to `process()` without catching exceptions.
Servers are not affected.
- Reported by [@​manus-use](https://github.com/manus-use).
- CVE ID: [CVE-TBD]()
- GHSA ID: [GHSA-j8rw-jp99-435v](https://github.com/digitalbazaar/forge/security/advisories/GHSA-j8rw-jp99-435v)
- **MODERATE**: ReDoS in `forge.http` response header parsing.
- `forge.http` trims response header and `Set-Cookie` values with a
regular expression that takes quadratic time on a long run of whitespace
followed by another character. A server, or an on-path attacker, can
block a `forge.http` client for minutes with one large header.
- Reported by [@​manus-pi](https://github.com/manus-pi).
- CVE ID: [CVE-TBD]()
- GHSA ID: [GHSA-6cv4-p8m7-4r25](https://github.com/digitalbazaar/forge/security/advisories/GHSA-6cv4-p8m7-4r25)
- **MODERATE**: TLS client crash on an unsupported ServerHello compression
method.
- A TLS client accepts any compression method in the ServerHello,
although it only offers no compression. An unknown method makes
`process()` throw an uncaught `Error` at ServerHelloDone, before the
server is authenticated. A malicious server, or an on-path attacker, can
terminate a Node.js process that passes socket data to `process()`
without catching exceptions, including through `forge.tls.wrapSocket`.
Servers are not affected.
- Reported by [@​alienkeric](https://github.com/alienkeric).
- CVE ID: [CVE-TBD]()
- GHSA ID: [GHSA-w4xr-hqv8-ch44](https://github.com/digitalbazaar/forge/security/advisories/GHSA-w4xr-hqv8-ch44)
- **LOW**: [`Ed25519`](https://github.com/digitalbazaar/forge/commit/Ed25519) signature verification accepts small-order public keys.
- `ed25519.verify()` does not reject public keys of small order, such as
the identity point. Under such a key, a signature with `S = 0` and a
small-order `R` verifies for many or, with the identity key, all
messages, without any private key. Applications are affected only if
they verify signatures against a public key an attacker can choose and
rely on the signature being bound to the message. Signatures made with
keys from `ed25519.generateKeyPair()` or other honest key generation are
not affected.
- Reported by [@​analisaperlengkapan](https://github.com/analisaperlengkapan).
- CVE ID: [CVE-TBD]()
- GHSA ID: [GHSA-6889-vf6x-f3g5](https://github.com/digitalbazaar/forge/security/advisories/GHSA-6889-vf6x-f3g5)
##### Added
- \[x509] Parse the nameConstraints extension (`2.5.29.30`) into
`permittedSubtrees`, `excludedSubtrees` and `unsupportedSubtreeRange`. An
invalid value is left unparsed.
##### Fixed
- \[[`ed25519`](https://github.com/digitalbazaar/forge/commit/ed25519)] Reject small-order public keys in `ed25519.verify()`.
- \[x509] Enforce nameConstraints in `verifyCertificateChain()` for the
subject and subjectAltName rfc822Name, dNSName, directoryName,
uniformResourceIdentifier and iPAddress names of each certificate, using
the constraints of the CA certificates above it and of the trust anchor.
Violations fail with `bad_certificate`, and the error has `nameType` and
`nameValue`. Critical nameConstraints are no longer rejected as
unsupported. As in OpenSSL:
- The commonName values of an end-entity certificate without a dNSName
subjectAltName are checked as dNSNames when they look like host names.
- directoryName values are compared ignoring ASCII case and extra
whitespace.
- Constraints that can't be evaluated for a name of the same type, names
that can't be checked against a constraint of the same type, and more
than 2^20 name and subtree comparisons for a chain fail with
`unsupported_certificate`.
- **NOTE**: Chains with a non-critical nameConstraints extension that the
names below it violate now fail verification. Chains with a critical
nameConstraints extension now verify when the names are within the
constraints, instead of always failing. A `verify` callback can still
override any error.
- \[tls] Ignore handshake messages received by a client without a session
instead of throwing a `TypeError`.
- \[http] Trim header and cookie values in linear time.
- \[tls] Fail a client handshake with an `illegal_parameter` alert when the
ServerHello selects a compression method other than none.
### [`v1.4.2`](https://github.com/digitalbazaar/forge/blob/HEAD/CHANGELOG.md#142---2026-10-27)
[Compare Source](https://github.com/digitalbazaar/forge/compare/v1.4.1...v1.4.2)
##### Fixed
- \[pem] Convert non-string input to a string in `pem.decode()` as before
1.4.1. The 1.4.1 PEM ReDoS fix (GHSA-7wch-p9px-956x) caused a `TypeError`
for `Buffer` input, which is used by `node-jose`.
([#​1165](https://github.com/digitalbazaar/forge/issues/1165))
</details>
---
### Configuration
📅 **Schedule**: (UTC)
- Branch creation
- At any time (no schedule defined)
- Automerge
- At any time (no schedule defined)
🚦 **Automerge**: Enabled.
♻ **Rebasing**: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 **Ignore**: Close this PR and you won't be reminded about this update again.
---
- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box
---
This PR has been generated by [Mend Renovate CLI](https://github.com/renovatebot/renovate).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0NC4xOTguMiIsInVwZGF0ZWRJblZlciI6IjQ0LjE5OC4yIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->
Here are some key observations to aid the review process:
⏱️Estimated effort to review: 1 🔵⚪⚪⚪⚪
🧪No relevant tests
🔒No security concerns identified
⚡No major issues detected
## PR Reviewer Guide 🔍
<!-- pr-agent:review:full -->
Here are some key observations to aid the review process:
<table>
<tr><td>⏱️ <strong>Estimated effort to review</strong>: 1 🔵⚪⚪⚪⚪</td></tr>
<tr><td>🧪 <strong>No relevant tests</strong></td></tr>
<tr><td>🔒 <strong>No security concerns identified</strong></td></tr>
<tr><td>⚡ <strong>No major issues detected</strong></td></tr>
</table>
Noel
changed title from chore(deps): update dependency node-forge to v1.4.2 to chore(deps): update dependency node-forge to v1.4.32026-11-04 04:01:55 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
This PR contains the following updates:
1.4.1→1.4.3Release Notes
digitalbazaar/forge (node-forge)
v1.4.3Compare Source
Security
pki.verifyCertificateChain()does not check the nameConstraintsextension (RFC 5280 4.2.1.10). A non-critical nameConstraints extension
in a CA certificate is ignored, so a name-constrained intermediate CA can
issue certificates for names outside its permitted subtrees, or inside
its excluded subtrees, and the chain verifies. Exploitation requires the
private key of a name-constrained CA that chains to a trusted root. A
critical nameConstraints extension is rejected as an unsupported critical
extension.
TypeErrorfromprocess()when itreceives a ServerHello while it has no session: after a
close_notifyalert or a call to
close(), or beforehandshake()is called. Amalicious server, or an on-path attacker, can terminate a Node.js process
that passes socket data to
process()without catching exceptions.Servers are not affected.
forge.httpresponse header parsing.forge.httptrims response header andSet-Cookievalues with aregular expression that takes quadratic time on a long run of whitespace
followed by another character. A server, or an on-path attacker, can
block a
forge.httpclient for minutes with one large header.method.
although it only offers no compression. An unknown method makes
process()throw an uncaughtErrorat ServerHelloDone, before theserver is authenticated. A malicious server, or an on-path attacker, can
terminate a Node.js process that passes socket data to
process()without catching exceptions, including through
forge.tls.wrapSocket.Servers are not affected.
Ed25519signature verification accepts small-order public keys.ed25519.verify()does not reject public keys of small order, such asthe identity point. Under such a key, a signature with
S = 0and asmall-order
Rverifies for many or, with the identity key, allmessages, without any private key. Applications are affected only if
they verify signatures against a public key an attacker can choose and
rely on the signature being bound to the message. Signatures made with
keys from
ed25519.generateKeyPair()or other honest key generation arenot affected.
Added
2.5.29.30) intopermittedSubtrees,excludedSubtreesandunsupportedSubtreeRange. Aninvalid value is left unparsed.
Fixed
ed25519] Reject small-order public keys ined25519.verify().verifyCertificateChain()for thesubject and subjectAltName rfc822Name, dNSName, directoryName,
uniformResourceIdentifier and iPAddress names of each certificate, using
the constraints of the CA certificates above it and of the trust anchor.
Violations fail with
bad_certificate, and the error hasnameTypeandnameValue. Critical nameConstraints are no longer rejected asunsupported. As in OpenSSL:
subjectAltName are checked as dNSNames when they look like host names.
whitespace.
that can't be checked against a constraint of the same type, and more
than 2^20 name and subtree comparisons for a chain fail with
unsupported_certificate.names below it violate now fail verification. Chains with a critical
nameConstraints extension now verify when the names are within the
constraints, instead of always failing. A
verifycallback can stilloverride any error.
instead of throwing a
TypeError.illegal_parameteralert when theServerHello selects a compression method other than none.
v1.4.2Compare Source
Fixed
pem.decode()as before1.4.1. The 1.4.1 PEM ReDoS fix (GHSA-7wch-p9px-956x) caused a
TypeErrorfor
Bufferinput, which is used bynode-jose.(#1165)
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate CLI.
Failed to update PR description
PR Reviewer Guide 🔍
Here are some key observations to aid the review process:
90a3bf3f38to6295e721bf6295e721bfto43b7e7f24d43b7e7f24dtobb86944ebbchore(deps): update dependency node-forge to v1.4.2to chore(deps): update dependency node-forge to v1.4.3bb86944ebbtob9922a1d20b9922a1d20toe2ab002d06e2ab002d06to6451e1105a6451e1105atof56400a3f7f56400a3f7to93305efc2393305efc23to8f612712838f61271283to230cf28676230cf28676to5edb9a10135edb9a1013to6a02b27ca46a02b27ca4to7d622ed2257d622ed225to9a3cb038759a3cb03875to8451b7bd758451b7bd75to673962422cView command line instructions
Checkout
From your project repository, check out a new branch and test the changes.