Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Bump github.com/lestrrat-go/jwx/v2 from 2.0.16 to 2.0.19 (#635)
Bumps [github.com/lestrrat-go/jwx/v2](https://github.com/lestrrat-go/jwx) from 2.0.16 to 2.0.19. <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>v2.0.19</h2> <pre><code>v2.0.19 09 Jan 2024 [New Features] * [jws] Added jws.IsVerificationError to check if the error returned by `jws.Verify` was caused by actual verification step or something else, for example, while fetching a key from datasource <p>[Security Fixes]</p> <ul> <li> <p>[jws] JWS messages formated in full JSON format (i.e. not the compact format, which consists of three base64 strings concatenated with a '.') with missing "protected" headers could cause a panic, thereby introducing a possiblity of a DoS.</p> <p>This has been fixed so that the <code>jws.Parse</code> function succeeds in parsing a JWS message lacking a protected header. Calling <code>jws.Verify</code> on this same JWS message will result in a failed verification attempt. Note that this behavior will differ slightly when parsing JWS messages in compact form, which result in an error. </code></pre></p> </li> </ul> <h2>v2.0.18</h2> <pre><code>v2.0.18 03 Dec 2023 [Security Fixes] * [jwe] A large number in p2c parameter for PBKDF2 based encryptions could cause a DoS attack, similar to https://nvd.nist.gov/vuln/detail/CVE-2022-36083. All users who use JWE via this package should upgrade. While the JOSE spec allows for encryption using JWE on JWTs, users of the `jwt` package are not immediately susceptible unless they explicitly try to decrypt JWTs -- by default the `jwt` package verifies signatures, but does not decrypt messages. [GHSA-7f9x-gw85-8grf] </code></pre> <h2>v2.0.17</h2> <pre><code>v2.0.17 20 Nov 2023 [Bug Fixes] * [jws] Previously, `jws.UnregisterSigner` did not remove the previous signer instance when the signer was registered and unregistered multiple times ([#1016](lestrrat-go/jwx#1016)). This has been fixed. <p>[New Features]</p> <ul> <li>[jwe] (EXPERIMENTAL) <code>jwe.WithCEK</code> has been added to extract the content encryption key (CEK) from the Decrypt operation.</li> <li>[jwe] (EXPERIMENTAL) <code>jwe.EncryptStatic</code> has been added to encrypt content using a static CEK. Using static CEKs has serious security implications, and you should not use this unless you completely understand the risks involved. </code></pre></li> </ul> </blockquote> </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.19 09 Jan 2024 [New Features]</p> <ul> <li>[jws] Added jws.IsVerificationError to check if the error returned by <code>jws.Verify</code> was caused by actual verification step or something else, for example, while fetching a key from datasource</li> </ul> <p>[Security Fixes]</p> <ul> <li> <p>[jws] JWS messages formated in full JSON format (i.e. not the compact format, which consists of three base64 strings concatenated with a '.') with missing "protected" headers could cause a panic, thereby introducing a possiblity of a DoS.</p> <p>This has been fixed so that the <code>jws.Parse</code> function succeeds in parsing a JWS message lacking a protected header. Calling <code>jws.Verify</code> on this same JWS message will result in a failed verification attempt. Note that this behavior will differ slightly when parsing JWS messages in compact form, which result in an error.</p> </li> </ul> <p>v2.0.18 03 Dec 2023 [Security Fixes]</p> <ul> <li>[jwe] A large number in p2c parameter for PBKDF2 based encryptions could cause a DoS attack, similar to <a href="https://nvd.nist.gov/vuln/detail/CVE-2022-36083">https://nvd.nist.gov/vuln/detail/CVE-2022-36083</a>. All users who use JWE via this package should upgrade. While the JOSE spec allows for encryption using JWE on JWTs, users of the <code>jwt</code> package are not immediately susceptible unless they explicitly try to decrypt JWTs -- by default the <code>jwt</code> package verifies signatures, but does not decrypt messages. [GHSA-7f9x-gw85-8grf]</li> </ul> <p>v2.0.17 20 Nov 2023 [Bug Fixes]</p> <ul> <li>[jws] Previously, <code>jws.UnregisterSigner</code> did not remove the previous signer instance when the signer was registered and unregistered multiple times (<a href="https://redirect.github.com/lestrrat-go/jwx/issues/1016">#1016</a>). This has been fixed.</li> </ul> <p>[New Features]</p> <ul> <li>[jwe] (EXPERIMENTAL) <code>jwe.WithCEK</code> has been added to extract the content encryption key (CEK) from the Decrypt operation.</li> <li>[jwe] (EXPERIMENTAL) <code>jwe.EncryptStatic</code> has been added to encrypt content using a static CEK. Using static CEKs has serious security implications, and you should not use this unless you completely understand the risks involved.</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/lestrrat-go/jwx/commit/d69a721931a5c48b9850a42404f18e143704adcd"><code>d69a721</code></a> v2.0.19 (<a href="https://redirect.github.com/lestrrat-go/jwx/issues/1051">#1051</a>)</li> <li><a href="https://github.com/lestrrat-go/jwx/commit/e75b7c8dcbf8e56ecfbeb17b8b3ffaa81a96914f"><code>e75b7c8</code></a> v2.0.18 (<a href="https://redirect.github.com/lestrrat-go/jwx/issues/1022">#1022</a>)</li> <li><a href="https://github.com/lestrrat-go/jwx/commit/c02af3ecf9f8248181ce98056d90cd96605dd658"><code>c02af3e</code></a> v2.0.17 (<a href="https://redirect.github.com/lestrrat-go/jwx/issues/1019">#1019</a>)</li> <li>See full diff in <a href="https://github.com/lestrrat-go/jwx/compare/v2.0.16...v2.0.19">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 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/open-component-model/ocm/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
2ddf3fe
commit e73ce3a