chore(deps): bump github.com/lestrrat-go/jwx/v2 from 2.0.12 to 2.0.20

[dependabot[bot]]

Bumps github.com/lestrrat-go/jwx/v2 from 2.0.12 to 2.0.20.

Release notes

Sourced from github.com/lestrrat-go/jwx/v2's releases.

v2.0.20 20 Feb 2024

[New Features]

• [jwe] Added jwe.Settings(WithMaxBufferSize(int64)) to set the maximum size of internal buffers. The default value is 256MB. Most users do not need to change this value.
• [jws] Allow jws.WithCompact() and jws.WithJSON() to be passed to jws.Parse() and jws.Verify(). These options control the expected serialization format for the JWS message.
• [jwt] Add jwt.WithCompactOnly() to specify that only compact serialization can be used for jwt.Parse(). Previously, by virtue of jws.Parse() allowing either JSON or Compact serialization format, jwt.Parse() also alloed JSON serialization where as RFC7519 explicitly states that only compact serialization should be used. For backward compatibility the default behavior is not changed, but you can set this global option for jwt: jwt.Settings(jwt.WithCompactOnly(true))

[Miscellaneous]

• Internal key conversions should now allow private keys to be used in place of public keys. This would allow you to pass private keys where public keys are expected.

v2.0.19

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
[Security Fixes]


[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.
This has been fixed so that the jws.Parse function succeeds in parsing a JWS message
lacking a protected header. Calling jws.Verify 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.

v2.0.18

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]

... (truncated)

Changelog

Sourced from github.com/lestrrat-go/jwx/v2's changelog.

v2.0.20 20 Feb 2024 [New Features]

• [jwe] Added jwe.Settings(WithMaxBufferSize(int64)) to set the maximum size of internal buffers. The default value is 256MB. Most users do not need to change this value.
• [jws] Allow jws.WithCompact() and jws.WithJSON() to be passed to jws.Parse() and jws.Verify(). These options control the expected serialization format for the JWS message.
• [jwt] Add jwt.WithCompactOnly() to specify that only compact serialization can be used for jwt.Parse(). Previously, by virtue of jws.Parse() allowing either JSON or Compact serialization format, jwt.Parse() also alloed JSON serialization where as RFC7519 explicitly states that only compact serialization should be used. For backward compatibility the default behavior is not changed, but you can set this global option for jwt: jwt.Settings(jwt.WithCompactOnly(true))

[Miscellaneous]

• Internal key conversions should now allow private keys to be used in place of public keys. This would allow you to pass private keys where public keys are expected.

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

[Security Fixes]

• [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.

  This has been fixed so that the jws.Parse function succeeds in parsing a JWS message lacking a protected header. Calling jws.Verify 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.

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]

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). This has been fixed.

... (truncated)

Commits

• c3b3a17 Merge branch 'develop/v2' into v2
• ace7a77 Update Changes
• cc1673d Bump golang.org/x/crypto from 0.18.0 to 0.19.0 (#1073)
• 73b6b6d [v2] jws: allow specifing parse format/jwt: disallow JSON (#1078)
• ab42020 Bump golangci/golangci-lint-action from 3 to 4 (#1075)
• 57af792 Bump codecov/codecov-action from 3 to 4 (#1070)
• a7dc5c0 Bump kentaro-m/auto-assign-action from 1.2.6 to 2.0.0 (#1069)
• 67edd3a Bump github.com/lestrrat-go/jwx/v2 from 2.0.18 to 2.0.19 in /cmd/jwx (#1063)
• 6dbd75b Bump github.com/lestrrat-go/jwx/v2 in /bench/performance (#1062)
• 3f14b8f Bump bazelbuild/setup-bazelisk from 2 to 3 (#1072)
• Additional commits viewable in compare view

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 commands and options

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 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)

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 96.26%. Comparing base (35a8d47) to head (d586ff8).

Additional details and impacted files

```diff @@ Coverage Diff @@ ## main #73 +/- ## ======================================= Coverage 96.26% 96.26% ======================================= Files 2 2 Lines 321 321 ======================================= Hits 309 309 Misses 10 10 Partials 2 2 ``` | [Flag](https://app.codecov.io/gh/ggicci/caddy-jwt/pull/73/flags?src=pr&el=flags&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=Ggicci) | Coverage Δ | | |---|---|---| | [unittests](https://app.codecov.io/gh/ggicci/caddy-jwt/pull/73/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=Ggicci) | `96.26% <ø> (ø)` | | Flags with carried forward coverage won't be shown. [Click here](https://docs.codecov.io/docs/carryforward-flags?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=Ggicci#carryforward-flags-in-the-pull-request-comment) to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

[lafriks]

@ggicci would be nice to update this as it has two CVE assigned