Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
build(deps): bump github.com/lestrrat-go/jwx/v2 from 2.0.8 to 2.0.11 (#…
…40) Bumps [github.com/lestrrat-go/jwx/v2](https://github.com/lestrrat-go/jwx) from 2.0.8 to 2.0.11. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/lestrrat-go/jwx/releases">github.com/lestrrat-go/jwx/v2's releases</a>.</em></p> <blockquote> <h2>[SECURITY] v2.0.11</h2> <pre><code>v2.0.11 - 14 Jun 2023 [Security] * Potential Padding Oracle Attack Vulnerability and Timing Attack Vulnerability for JWE AES-CBC encrypted payloads affecting all v2 releases up to v2.0.10, all v1 releases up to v1.2.25, and all v0 releases up to v0.9.2 have been reported by @shogo82148. <pre><code>Please note that v0 versions will NOT receive fixes. This release fixes these vulnerabilities for the v2 series. </code></pre> <p></code></pre></p> <h2>v2.0.10</h2> <pre><code>v2.0.10 - 12 Jun 2023 [New Features] * [jwe] (EXPERIMENTAL) Added `jwe.KeyEncrypter` and `jwe.KeyDecrypter` interfaces that works in similar ways as how `crypto.Signer` works for signature generation and verification. It can act as the interface for your encryption/decryption keys that are for example stored in an hardware device. <pre><code>This feature is labeled experimental because the API for the above interfaces have not been battle tested, and may need to changed yet. Please be aware that until the API is deemed stable, you may have to adapat our code to these possible changes, _even_ during minor version upgrades of this library. </code></pre> <p>[Bug fixes]</p> <ul> <li> <p>Registering JWS signers/verifiers did not work since v2.0.0, because the way we handle algorithm names changed in 2aa98ce6884187180a7145b73da78c859dd46c84. (We previously thought that this would be checked by the example code, but it apparently failed to flag us properly)</p> <p>The logic behind managing the internal database has been fixed, and <code>jws.RegisterSigner</code> and <code>jws.RegisterVerifier</code> now properly hooks into the new <code>jwa.RegisterSignatureAlgorithm</code> to automatically register new algorithm names (<a href="https://redirect.github.com/lestrrat-go/jwx/issues/910">#910</a>, <a href="https://redirect.github.com/lestrrat-go/jwx/issues/911">#911</a>) [Miscellaneous]</p> </li> <li> <p>Added limited support for github.com/segmentio/asm/base64. Compile your code with the <code>jwx_asmbase64</code> build tag. This feature is EXPERIMENTAL.</p> <p>Through limited testing, the use of a faster base64 library provide 1~5% increase in throughput on average. It might make more difference if the input/output is large. If you care about this performance improvement, you should probably enable <code>goccy</code> JSON parser as well, by specifying <code>jwx_goccy,jwx_asmbase64</code> in your build call.</p> </li> <li> <p>Slightly changed the way global variables underneath <code>jwk.Fetch</code> are initialized and configured. <code>jwk.Fetch</code> creates an object that spawns wokers to fetch JWKS when it's first called. You can now also use <code>jwk.SetGlobalFetcher()</code> to set a fetcher object which you can control. </tr></table> </code></pre></p> </li> </ul> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/lestrrat-go/jwx/blob/develop/v2/Changes">github.com/lestrrat-go/jwx/v2's changelog</a>.</em></p> <blockquote> <p>v2.0.11 - 14 Jun 2023 [Security]</p> <ul> <li> <p>Potential Padding Oracle Attack Vulnerability and Timing Attack Vulnerability for JWE AES-CBC encrypted payloads affecting all v2 releases up to v2.0.10, all v1 releases up to v1.2.25, and all v0 releases up to v0.9.2 have been reported by <a href="https://github.com/shogo82148"><code>@shogo82148</code></a>.</p> <p>Please note that v0 versions will NOT receive fixes. This release fixes these vulnerabilities for the v2 series.</p> </li> </ul> <p>v2.0.10 - 12 Jun 2023 [New Features]</p> <ul> <li> <p>[jwe] (EXPERIMENTAL) Added <code>jwe.KeyEncrypter</code> and <code>jwe.KeyDecrypter</code> interfaces that works in similar ways as how <code>crypto.Signer</code> works for signature generation and verification. It can act as the interface for your encryption/decryption keys that are for example stored in an hardware device.</p> <p>This feature is labeled experimental because the API for the above interfaces have not been battle tested, and may need to changed yet. Please be aware that until the API is deemed stable, you may have to adapat our code to these possible changes, <em>even</em> during minor version upgrades of this library.</p> </li> </ul> <p>[Bug fixes]</p> <ul> <li> <p>Registering JWS signers/verifiers did not work since v2.0.0, because the way we handle algorithm names changed in 2aa98ce6884187180a7145b73da78c859dd46c84. (We previously thought that this would be checked by the example code, but it apparently failed to flag us properly)</p> <p>The logic behind managing the internal database has been fixed, and <code>jws.RegisterSigner</code> and <code>jws.RegisterVerifier</code> now properly hooks into the new <code>jwa.RegisterSignatureAlgorithm</code> to automatically register new algorithm names (<a href="https://redirect.github.com/lestrrat-go/jwx/issues/910">#910</a>, <a href="https://redirect.github.com/lestrrat-go/jwx/issues/911">#911</a>) [Miscellaneous]</p> </li> <li> <p>Added limited support for github.com/segmentio/asm/base64. Compile your code with the <code>jwx_asmbase64</code> build tag. This feature is EXPERIMENTAL.</p> <p>Through limited testing, the use of a faster base64 library provide 1~5% increase in throughput on average. It might make more difference if the input/output is large. If you care about this performance improvement, you should probably enable <code>goccy</code> JSON parser as well, by specifying <code>jwx_goccy,jwx_asmbase64</code> in your build call.</p> </li> <li> <p>Slightly changed the way global variables underneath <code>jwk.Fetch</code> are initialized and configured. <code>jwk.Fetch</code> creates an object that spawns wokers to fetch JWKS when it's first called. You can now also use <code>jwk.SetGlobalFetcher()</code> to set a fetcher object which you can control.</p> </li> </ul> <p>v2.0.9 - 21 Mar 2023 [Security Fixes]</p> <ul> <li>Updated use of golang.org/x/crypto to v0.7.0 [Bug fixes]</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/lestrrat-go/jwx/commit/6c41e3822485fc7e11dd70b4b0524b075d66b103"><code>6c41e38</code></a> merge for v2 (<a href="https://redirect.github.com/lestrrat-go/jwx/issues/939">#939</a>)</li> <li><a href="https://github.com/lestrrat-go/jwx/commit/8840ffd4afc5839f591ff0e9ba9034af52b1643e"><code>8840ffd</code></a> merge for v2.0.10 (<a href="https://redirect.github.com/lestrrat-go/jwx/issues/932">#932</a>)</li> <li><a href="https://github.com/lestrrat-go/jwx/commit/fccc52457a90ce00d625c3ed8d5d3443e903a91b"><code>fccc524</code></a> Update v2 (<a href="https://redirect.github.com/lestrrat-go/jwx/issues/894">#894</a>)</li> <li>See full diff in <a href="https://github.com/lestrrat-go/jwx/compare/v2.0.8...v2.0.11">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 merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@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/abcxyz/access-on-demand/network/alerts). </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
- Loading branch information
1 parent
c9b62d4
commit c2c109c