dependabot[bot] opened a new pull request, #11915: URL: https://github.com/apache/nifi/pull/11915
Bumps [@hono/node-server](https://github.com/honojs/node-server) from 2.1.3 to 2.1.8. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/honojs/node-server/releases";>@​hono/node-server's releases</a>.</em></p> <blockquote> <h2>v2.1.8</h2> <h2>What's Changed</h2> <ul> <li>fix(request): forward duplex to the native request in <a href="https://redirect.github.com/honojs/node-server/pull/409";>honojs/node-server#409</a></li> <li>fix(utils): do not chain a promise per chunk while streaming a response in <a href="https://redirect.github.com/honojs/node-server/pull/417";>honojs/node-server#417</a></li> <li>fix(listener): cancel the response body when the client has already disconnected in <a href="https://redirect.github.com/honojs/node-server/pull/412";>honojs/node-server#412</a></li> <li>fix(utils): cancel late HTTP/2 response bodies in <a href="https://redirect.github.com/honojs/node-server/pull/419";>honojs/node-server#419</a></li> <li>fix(listener): do not send a complete response when the body fails during the early read in <a href="https://redirect.github.com/honojs/node-server/pull/420";>honojs/node-server#420</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/honojs/node-server/compare/v2.1.7...v2.1.8";>https://github.com/honojs/node-server/compare/v2.1.7...v2.1.8</a></p> <h2>v2.1.7</h2> <h2>Security fixes</h2> <p>This release includes a fix for the following security issue:</p> <h3><code>serveStatic</code> with <code>allowPercentInPath</code> still allows the double-decode middleware bypass</h3> <p>Affects: <code>serveStatic</code> with <code>allowPercentInPath: true</code>. The fix for <a href="https://github.com/honojs/node-server/security/advisories/GHSA-rmxm-3fg6-px4f";>GHSA-rmxm-3fg6-px4f</a> rejects a path containing <code>%</code>, but the <code>allowPercentInPath</code> option skipped that check entirely. A malformed percent sequence such as <code>/static/%%36%31dmin/secret.txt</code> was routed as <code>/static/%61dmin/secret.txt</code>, so middleware on <code>/static/admin/*</code> did not run, and <code>serveStatic</code> then decoded <code>%61</code> to <code>a</code> and served <code>static/admin/secret.txt</code>. The default configuration was already fixed in 2.1.3. <a href="https://github.com/honojs/node-server/security/advisories/GHSA-fj57-4f93-cfw6";>GHSA-fj57-4f93-cfw6</a></p> <p><code>serveStatic</code> now accepts the second decode only when its result equals the routed path with <code>%25</code> replaced by <code>%</code>. File names containing a literal <code>%</code>, requested as <code>%25</code>, are served as before.</p> <hr /> <p>The same fix ships in <code>hono</code> v4.13.18 (<a href="https://github.com/honojs/hono/security/advisories/GHSA-74fm-fwc7-3fwp";>GHSA-74fm-fwc7-3fwp</a>).</p> <p><strong>Full Changelog</strong>: <a href="https://github.com/honojs/node-server/compare/v2.1.6...v2.1.7";>https://github.com/honojs/node-server/compare/v2.1.6...v2.1.7</a></p> <h2>v2.1.6</h2> <h2>Security fixes</h2> <p>This release includes fixes for the following security issues:</p> <h3>Backslash in the request path is parsed as a path separator, bypassing path-based access control at a reverse proxy</h3> <p>Affects: all requests. The raw request-target was passed to the WHATWG URL parser, which treats a backslash in the path as <code>/</code> and resolves <code>..</code> segments, so <code>/admin\secret</code> reached the application as <code>/admin/secret</code>. A reverse proxy that forwards the backslash unchanged applied its path-based rules to the original path. <a href="https://github.com/honojs/node-server/security/advisories/GHSA-jpvv-r467-5p4w";>GHSA-jpvv-r467-5p4w</a></p> <p>A request whose path contains a raw backslash is now rejected with <code>400 Bad Request</code>, for HTTP/1.1, HTTP/2 and WebSocket upgrades. A percent-encoded backslash (<code>%5C</code>) and a backslash in the query string are still accepted.</p> <h3>WebSocket upgrade request-target starting with <code>//</code> replaces the host in <code>c.req.url</code>, bypassing <code>Origin</code> checks</h3> <p>Affects: <code>upgradeWebSocket</code>. The URL of an upgrade request was built by resolving the request-target against the <code>Host</code> header, so a request-target such as <code>//attacker.example/ws</code> set the host of <code>c.req.url</code> to a client-chosen value while routing still saw <code>/ws</code>. An application that compared <code>Origin</code> with the origin of <code>c.req.url</code> could be bypassed by a page on another site. <a href="https://github.com/honojs/node-server/security/advisories/GHSA-7v5p-43qr-wch5";>GHSA-7v5p-43qr-wch5</a></p> <p>The host of upgrade requests now comes from the <code>Host</code> header, as for ordinary requests.</p> <h3>Unhandled <code>ECONNRESET</code> on the socket during an asynchronous WebSocket upgrade crashes the process</h3> <p>Affects: <code>upgradeWebSocket</code>. While the application handled an upgrade request, the socket had no error listener. A client that reset the connection during asynchronous middleware caused an unhandled <code>'error'</code> event and terminated the process. <a href="https://github.com/honojs/node-server/security/advisories/GHSA-qv5m-9pm6-hqp3";>GHSA-qv5m-9pm6-hqp3</a></p> <p>Error and close events on the socket are now handled while the application runs, and a pending upgrade is released when the socket closes.</p> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/honojs/node-server/commit/1fc1dfc6c5c6c40c49618f3e21d97554e74acddf";><code>1fc1dfc</code></a> 2.1.8</li> <li><a href="https://github.com/honojs/node-server/commit/3463817b49c6546c635f5eca867ad78289512679";><code>3463817</code></a> fix(listener): do not send a complete response when the body fails during the...</li> <li><a href="https://github.com/honojs/node-server/commit/f22b99c954783365d357bc1dbb19dcd5924e06e3";><code>f22b99c</code></a> fix(utils): cancel late HTTP/2 response bodies (<a href="https://redirect.github.com/honojs/node-server/issues/419";>#419</a>)</li> <li><a href="https://github.com/honojs/node-server/commit/4b885d3d8fcd8d018bdec5e493c37650a38d6b5b";><code>4b885d3</code></a> fix(listener): cancel the response body when the client has already disconnec...</li> <li><a href="https://github.com/honojs/node-server/commit/653ec79f3ba17d1677b449bae41d820f14ad3a81";><code>653ec79</code></a> fix(utils): do not chain a promise per chunk while streaming a response (<a href="https://redirect.github.com/honojs/node-server/issues/417";>#417</a>)</li> <li><a href="https://github.com/honojs/node-server/commit/7da431bc779938a844dc89e480217c347753bf1b";><code>7da431b</code></a> fix(request): forward duplex to the native request (<a href="https://redirect.github.com/honojs/node-server/issues/409";>#409</a>)</li> <li><a href="https://github.com/honojs/node-server/commit/abe63c84bd72107fd954717a70a0bf68029ce267";><code>abe63c8</code></a> 2.1.7</li> <li><a href="https://github.com/honojs/node-server/commit/cc4298606df1be70948854e9cefa63d019035f63";><code>cc42986</code></a> Merge commit from fork</li> <li><a href="https://github.com/honojs/node-server/commit/123f78269626704eb7f4d85a9529e357315ba051";><code>123f782</code></a> 2.1.6</li> <li><a href="https://github.com/honojs/node-server/commit/cfaa79f76dbb0fe9f539438c0c585d94ed7cd01f";><code>cfaa79f</code></a> Merge commit from fork</li> <li>Additional commits viewable in <a href="https://github.com/honojs/node-server/compare/v2.1.3...v2.1.8";>compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/apache/nifi/network/alerts). </details> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
