dependabot[bot] opened a new pull request, #76100: URL: https://github.com/apache/airflow/pull/76100
Bumps the core-ui-security-updates group with 2 updates in the /airflow-core/src/airflow/ui directory: [i18next-http-backend](https://github.com/i18next/i18next-http-backend) and [happy-dom](https://github.com/capricorn86/happy-dom). Updates `i18next-http-backend` from 4.0.2 to 4.0.4 <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/i18next/i18next-http-backend/blob/master/CHANGELOG.md";>i18next-http-backend's changelog</a>.</em></p> <blockquote> <h3>4.0.4</h3> <p>Security release. See advisory <a href="https://github.com/i18next/i18next-http-backend/security/advisories/GHSA-3cmx-xjww-583x";>GHSA-3cmx-xjww-583x</a>.</p> <ul> <li>security: also reject <code>&</code>, <code>=</code> and <code>;</code> in <code>lng</code> and <code>ns</code> values. With a query-shaped <code>loadPath</code> / <code>addPath</code> template such as <code>/locales/resources.json?lng={{lng}}&ns={{ns}}</code> (the multiload shape the README documents), a value like <code>de&ns=private&admin=true</code> added or overrode query parameters on the request (HTTP parameter pollution). The 3.0.5 fix only rejected <code>?</code>, which covers the path position. The default <code>/locales/{{lng}}/{{ns}}.json</code> and other path-only templates were not affected. No language code or usable namespace name contains these characters, and <code>+</code>-joined multiload values such as <code>de+en</code> keep working.</li> </ul> <h3>4.0.3</h3> <p>Security release. See advisory <a href="https://github.com/i18next/i18next-http-backend/security/advisories/GHSA-9jhj-wvmw-cfx5";>GHSA-9jhj-wvmw-cfx5</a>.</p> <ul> <li>security: refuse a request URL that starts with <code>//</code> (or <code>\</code>) when the <code>loadPath</code> / <code>addPath</code> template does not. With a template that puts <code>{{ns}}</code> directly after a leading <code>/</code> (e.g. <code>/{{ns}}/{{lng}}.json</code>), an <code>ns</code> value of <code>/evil.example</code> passed the per-value checks, because a single <code>/</code> is allowed for nested namespaces, but it joined the template's own <code>/</code> into <code>//evil.example/en.json</code>, a protocol-relative URL that browsers send to another origin. The 4.0.2 <code>//</code> check looked at the value only, so it missed this. The interpolated URL is now checked as a whole. The default <code>/locales/{{lng}}/{{ns}}.json</code>, templates with an origin, and protocol-relative CDN templates such as <code>//cdn.example/{{lng}}/{{ns}}.json</code> are not affected and keep working.</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/i18next/i18next-http-backend/commit/c201e7f095d5f92df723bdc9f4c2bd4aed9439d3";><code>c201e7f</code></a> 4.0.4</li> <li><a href="https://github.com/i18next/i18next-http-backend/commit/b0eef9efd425055c554787cef7f878de33bbf510";><code>b0eef9e</code></a> security: reject <code>&</code>, <code>=</code> and <code>;</code> in lng/ns to close query-parameter injectio...</li> <li><a href="https://github.com/i18next/i18next-http-backend/commit/8eb66469e3a2123f25574bb454c0c2ebc7ab6ab2";><code>8eb6646</code></a> Bump i18next-http-backend from 3.0.5 to 4.0.2 in /example/fallback (<a href="https://redirect.github.com/i18next/i18next-http-backend/issues/199";>#199</a>)</li> <li><a href="https://github.com/i18next/i18next-http-backend/commit/5d3fd6c470fb8124506091ce4daaf342d24185a0";><code>5d3fd6c</code></a> Bump i18next-http-backend from 3.0.5 to 4.0.2 in /example/node (<a href="https://redirect.github.com/i18next/i18next-http-backend/issues/198";>#198</a>)</li> <li><a href="https://github.com/i18next/i18next-http-backend/commit/e48caf252143a65312aba9efa784de27aa06bb15";><code>e48caf2</code></a> Bump next from 16.3.6 to 16.3.8 in /example/next (<a href="https://redirect.github.com/i18next/i18next-http-backend/issues/197";>#197</a>)</li> <li><a href="https://github.com/i18next/i18next-http-backend/commit/772900cd65e786c3f410f2e2705f84aa81c426af";><code>772900c</code></a> Bump i18next-http-backend from 3.0.5 to 4.0.2 in /example/i18next-vue (<a href="https://redirect.github.com/i18next/i18next-http-backend/issues/196";>#196</a>)</li> <li><a href="https://github.com/i18next/i18next-http-backend/commit/42e86393fd4b8d2fc34f2ddadfa6c3097bf87238";><code>42e8639</code></a> 4.0.3</li> <li><a href="https://github.com/i18next/i18next-http-backend/commit/042c3d4e4e9d73b2ae3aa76b22cb45d48f1e35b7";><code>042c3d4</code></a> security: reject interpolated URLs that turn into <code>//host</code> (GHSA-9jhj-wvmw-cfx5)</li> <li><a href="https://github.com/i18next/i18next-http-backend/commit/9b5f1e2f65365d958f9e6459c6e51d0ac9a028fa";><code>9b5f1e2</code></a> Bump i18next-http-backend from 1.2.6 to 4.0.2 in /example/angular (<a href="https://redirect.github.com/i18next/i18next-http-backend/issues/194";>#194</a>)</li> <li><a href="https://github.com/i18next/i18next-http-backend/commit/be8b9a4962a09b4833e630b3cdbd7a380a5b2aff";><code>be8b9a4</code></a> Bump next from 16.3.3 to 16.3.6 in /example/next (<a href="https://redirect.github.com/i18next/i18next-http-backend/issues/193";>#193</a>)</li> <li>Additional commits viewable in <a href="https://github.com/i18next/i18next-http-backend/compare/v4.0.2...v4.0.4";>compare view</a></li> </ul> </details> <br /> Updates `happy-dom` from 21.0.1 to 21.0.4 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/capricorn86/happy-dom/releases";>happy-dom's releases</a>.</em></p> <blockquote> <h2>v21.0.4</h2> <h3>:construction_worker_man: Patch fixes</h3> <ul> <li>Fixed a code injection vulnerability in the ESM compiler - By <strong><a href="https://github.com/capricorn86";><code>@capricorn86</code></a></strong></li> <li>Fixed cross-origin isolation so opaque-origin <code>data:</code> iframes cannot access their parent or top window - By <strong><a href="https://github.com/capricorn86";><code>@capricorn86</code></a></strong></li> </ul> <h2>v21.0.3</h2> <h3>:construction_worker_man: Patch fixes</h3> <ul> <li>Fixes security vulnerability where authorization header was forwarded when redirecting - By <strong><a href="https://github.com/capricorn86";><code>@capricorn86</code></a></strong></li> </ul> <h2>v21.0.2</h2> <h3>:construction_worker_man: Patch fixes</h3> <ul> <li>Fixes SSRF security vulnerability by doing a target-origin bypass in the proxy server in <a href="https://github.com/capricorn86/happy-dom/wiki/Server-Renderer";>@happy-dom/server-renderer</a> - By <strong><a href="https://github.com/capricorn86";><code>@capricorn86</code></a></strong></li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/capricorn86/happy-dom/commit/fd163520b74d9fa146be91f7b4e4f46d6cccbe13";><code>fd16352</code></a> fix: Fixed a code injection vulnerability in the ESM compiler (<a href="https://redirect.github.com/capricorn86/happy-dom/issues/2537";>#2537</a>)</li> <li><a href="https://github.com/capricorn86/happy-dom/commit/75ab0fb732faf7b801cf644d4338b663f1a8cae7";><code>75ab0fb</code></a> fix: Fixed cross-origin isolation so opaque-origin data: iframes cannot acces...</li> <li><a href="https://github.com/capricorn86/happy-dom/commit/875ef5c647b336cc933c82426c9d780a5aab84f9";><code>875ef5c</code></a> fix: Fixes security vulnerability where authorization header was forwarded wh...</li> <li><a href="https://github.com/capricorn86/happy-dom/commit/1f3ffdf634231361de1a2acb629b4fe8ee1bd85d";><code>1f3ffdf</code></a> fix: Fixes SSRF security vulnerability by doing a target-origin bypass in the...</li> <li><a href="https://github.com/capricorn86/happy-dom/commit/f55c7e0852a3ecf33252d4955f260a5246f3f63e";><code>f55c7e0</code></a> chore: Update security documentation (<a href="https://redirect.github.com/capricorn86/happy-dom/issues/2509";>#2509</a>)</li> <li>See full diff in <a href="https://github.com/capricorn86/happy-dom/compare/v21.0.1...v21.0.4";>compare view</a></li> </ul> </details> <br /> 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 <dependency name> major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore <dependency name> minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore <dependency name>` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore <dependency name>` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore <dependency name> <ignore condition>` will remove the ignore condition of the specified dependency and ignore conditions You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/apache/airflow/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]
