dependabot[bot] opened a new pull request, #3611:
URL: https://github.com/apache/tinkerpop/pull/3611

   Bumps [undici](https://github.com/nodejs/undici) from 6.27.0 to 6.28.0.
   <details>
   <summary>Release notes</summary>
   <p><em>Sourced from <a 
href="https://github.com/nodejs/undici/releases";>undici's releases</a>.</em></p>
   <blockquote>
   <h2>v6.28.0</h2>
   <h2>⚠️ Security fixes</h2>
   <ul>
   <li><a 
href="https://github.com/nodejs/undici/security/advisories/GHSA-m8rv-5g2x-5cg5";>GHSA-m8rv-5g2x-5cg5</a>:
 a malicious <code>type</code> property on a duck-typed blob-like HTTP/1.1 
request body could inject CRLF sequences into the generated 
<code>content-type</code> header. Undici now coerces and validates the value 
before adding it to the request. Fixed by <a 
href="https://github.com/nodejs/undici/commit/740a0b7c173cb4a83a5b693e96e8f3a116cfc400";>740a0b7c</a>.</li>
   <li><a 
href="https://github.com/nodejs/undici/security/advisories/GHSA-8xcm-r25x-g524";>GHSA-8xcm-r25x-g524</a>:
 the retry interceptor could expose a stale <code>Content-Length</code> after 
resuming a partial response, potentially causing downstream response 
desynchronization, hangs, or corruption. Undici now rejects partial responses 
whose <code>Content-Length</code> is inconsistent with 
<code>Content-Range</code>. Fixed by <a 
href="https://github.com/nodejs/undici/commit/cba3a52ac2e7abcc4e656d82af8579ea82c2bb9e";>cba3a52a</a>,
 with corrected fixtures in <a 
href="https://github.com/nodejs/undici/commit/4fd5a0c61e627f928b7003adc4ffe1e55ec63420";>4fd5a0c6</a>.</li>
   <li><a 
href="https://github.com/nodejs/undici/security/advisories/GHSA-v3r7-h72x-cjcm";>GHSA-v3r7-h72x-cjcm</a>:
 unsanitized <code>domain</code> and <code>unparsed</code> values passed to 
<code>setCookie()</code> could inject cookie attributes. Undici now validates 
cookie domains, paths, and unparsed attributes more strictly. Fixed by <a 
href="https://github.com/nodejs/undici/commit/af7484043ee075a6f216da0ad77e1dac55199235";>af748404</a>.</li>
   </ul>
   <p><a 
href="https://github.com/nodejs/undici/security/advisories/GHSA-4cwx-7wf7-3272";>GHSA-4cwx-7wf7-3272</a>
 and <a 
href="https://github.com/nodejs/undici/security/advisories/GHSA-jr45-8vmc-qm54";>GHSA-jr45-8vmc-qm54</a>
 affect the cache interceptor in Undici v7 and v8; Undici v6 is not in their 
affected version ranges.</p>
   <p><strong>Full Changelog</strong>: <a 
href="https://github.com/nodejs/undici/compare/v6.27.0...v6.28.0";>https://github.com/nodejs/undici/compare/v6.27.0...v6.28.0</a></p>
   </blockquote>
   </details>
   <details>
   <summary>Commits</summary>
   <ul>
   <li><a 
href="https://github.com/nodejs/undici/commit/01a912e49a50c48009ed2639d2a457a6ec26752a";><code>01a912e</code></a>
 Bumped v6.28.0 (<a 
href="https://redirect.github.com/nodejs/undici/issues/5591";>#5591</a>)</li>
   <li><a 
href="https://github.com/nodejs/undici/commit/481ecfc3280292ab7eb0abbc4d0139219126f15e";><code>481ecfc</code></a>
 Use Node 22 and npm 11 to release</li>
   <li><a 
href="https://github.com/nodejs/undici/commit/740a0b7c173cb4a83a5b693e96e8f3a116cfc400";><code>740a0b7</code></a>
 fix: validate blob body content type</li>
   <li><a 
href="https://github.com/nodejs/undici/commit/2698e492ed22c9ec704b5df573d612bdd03f6ca0";><code>2698e49</code></a>
 fix: validate coerced header values for CRLF (<a 
href="https://redirect.github.com/nodejs/undici/issues/5579";>#5579</a>)</li>
   <li><a 
href="https://github.com/nodejs/undici/commit/4fd5a0c61e627f928b7003adc4ffe1e55ec63420";><code>4fd5a0c</code></a>
 test(retry): correct broken content-range fixtures in retry-handler.js</li>
   <li><a 
href="https://github.com/nodejs/undici/commit/cba3a52ac2e7abcc4e656d82af8579ea82c2bb9e";><code>cba3a52</code></a>
 fix(retry): reject partial content length mismatch</li>
   <li><a 
href="https://github.com/nodejs/undici/commit/af7484043ee075a6f216da0ad77e1dac55199235";><code>af74840</code></a>
 fix: harden cookie domain, path, and unparsed attribute validation</li>
   <li>See full diff in <a 
href="https://github.com/nodejs/undici/compare/v6.27.0...v6.28.0";>compare 
view</a></li>
   </ul>
   </details>
   <br />
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=undici&package-manager=npm_and_yarn&previous-version=6.27.0&new-version=6.28.0)](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/tinkerpop/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]

Reply via email to