dependabot[bot] opened a new pull request, #21089: URL: https://github.com/apache/datafusion/pull/21089
Bumps [rustls-webpki](https://github.com/rustls/webpki) from 0.103.9 to 0.103.10. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/rustls/webpki/releases";>rustls-webpki's releases</a>.</em></p> <blockquote> <h2>0.103.10</h2> <p><strong>Correct selection of candidate CRLs by Distribution Point and Issuing Distribution Point</strong>. If a certificate had more than one <code>distributionPoint</code>, then only the first <code>distributionPoint</code> would be considered against each CRL's <code>IssuingDistributionPoint</code> <code>distributionPoint</code>, and then the certificate's subsequent <code>distributionPoint</code>s would be ignored.</p> <p>The impact was that correct provided CRLs would not be consulted to check revocation. With <code>UnknownStatusPolicy::Deny</code> (the default) this would lead to incorrect but safe <code>Error::UnknownRevocationStatus</code>. With <code>UnknownStatusPolicy::Allow</code> this would lead to inappropriate acceptance of revoked certificates.</p> <p>This vulnerability is thought to be of limited impact. This is because both the certificate and CRL are signed -- an attacker would need to compromise a trusted issuing authority to trigger this bug. An attacker with such capabilities could likely bypass revocation checking through other more impactful means (such as publishing a valid, empty CRL.)</p> <p>More likely, this bug would be latent in normal use, and an attacker could leverage faulty revocation checking to continue using a revoked credential.</p> <p>This vulnerability is identified by <a href="https://github.com/rustls/webpki/security/advisories/GHSA-pwjx-qhcg-rvj4";>GHSA-pwjx-qhcg-rvj4</a>. Thank you to <a href="https://github.com/1seal";><code>@1seal</code></a> for the report.</p> <h2>What's Changed</h2> <ul> <li>Freshen up rel-0.103 by <a href="https://github.com/ctz";><code>@ctz</code></a> in <a href="https://redirect.github.com/rustls/webpki/pull/455";>rustls/webpki#455</a></li> <li>Prepare 0.103.10 by <a href="https://github.com/ctz";><code>@ctz</code></a> in <a href="https://redirect.github.com/rustls/webpki/pull/458";>rustls/webpki#458</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/rustls/webpki/compare/v/0.103.9...v/0.103.10";>https://github.com/rustls/webpki/compare/v/0.103.9...v/0.103.10</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/rustls/webpki/commit/348ce01c01cf8ce21199090c98853992c9c047a8";><code>348ce01</code></a> Prepare 0.103.10</li> <li><a href="https://github.com/rustls/webpki/commit/dbde5921164c6e3ea0928654de8cb7d5de8c2b33";><code>dbde592</code></a> crl: fix authoritative_for() support for multiple URIs</li> <li><a href="https://github.com/rustls/webpki/commit/9c4838e6129a544a0f7f5d26ac7517860a22992c";><code>9c4838e</code></a> avoid std::prelude imports</li> <li><a href="https://github.com/rustls/webpki/commit/009ef667e3bb0544808c39b64e9b6db0d626b117";><code>009ef66</code></a> fix rust 1.94 ambiguous panic macro warnings</li> <li><a href="https://github.com/rustls/webpki/commit/c41360d095f9f48e14679a078afd10c2d61716fe";><code>c41360d</code></a> build(deps): bump taiki-e/cache-cargo-install-action from 2 to 3</li> <li><a href="https://github.com/rustls/webpki/commit/e401d0083d9cf91d0209bae1db465267d7290233";><code>e401d00</code></a> generate.py: reformat for black 2026.1.0</li> <li><a href="https://github.com/rustls/webpki/commit/06cedecbf6af88cad40b2ae2cc4a474f1429ddb6";><code>06cedec</code></a> Take semver-compatible deps</li> <li>See full diff in <a href="https://github.com/rustls/webpki/compare/v/0.103.9...v/0.103.10";>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/datafusion/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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
