build(deps): bump github.com/lestrrat-go/jwx/v2 from 2.0.13 to 2.0.15

[dependabot]

Bumps github.com/lestrrat-go/jwx/v2 from 2.0.13 to 2.0.15.

Release notes

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

v2.0.15

v2.0.15 19 20 Oct 2023
[Bug fixes]
  * [jws] jws.Sign() now properly check for valid algorithm / key type pair when
    the key implements crypto.Signer. This was caused by the fact that when 
    jws.WithKey() accepted keys that implemented crypto.Signer, there really
    is no way to robustly check what algorithm the crypto.Signer implements.
The code has now been modified to check for KNOWN key types, i.e. those
that are defined in Go standard library, and those that are defined in
this library. For example, now calling jws.Sign() with jws.WithKey(jwa.RS256, ecdsaKey)
where ecdsaKey is either an instance of *ecdsa.PrivateKey or jwk.ECDSAPrivateKey
will produce an error.
However, if you use a separate library that wraps some KMS library which implements

crypto.Signer, this same check will not be performed due to the fact that

it is an unknown library to us. And there's no way to query a crypto.Signer

for its algorithm family.

v2.0.14

v2.0.14 17 Oct 2023
  [New Features]
  * [jwk] jwk.IsPrivateKey(), as well as jwk.AsymmetricKey has been added.
    The function can be used to tell if a jwk.Key is a private key of an
    asymmetric key pair.
  [Security]
  * golang.org/x/crypto has been updated to 0.14.0. The update contains a fix for HTTP/2
    rapid reset DoS vulnerability, which some security scanning softwares may flag.
    However, do note that this library is NOT affected by the issue, as it does not have
    the capability to serve as an HTTP/2 server. This is included in this release
    document so that users will be able to tell why this library may be flagged
    when/if their scanning software do so.

Changelog

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

v2.0.15 19 20 Oct 2023 [Bug fixes]

• [jws] jws.Sign() now properly check for valid algorithm / key type pair when the key implements crypto.Signer. This was caused by the fact that when jws.WithKey() accepted keys that implemented crypto.Signer, there really is no way to robustly check what algorithm the crypto.Signer implements.

  The code has now been modified to check for KNOWN key types, i.e. those that are defined in Go standard library, and those that are defined in this library. For example, now calling jws.Sign() with jws.WithKey(jwa.RS256, ecdsaKey) where ecdsaKey is either an instance of *ecdsa.PrivateKey or jwk.ECDSAPrivateKey will produce an error.

  However, if you use a separate library that wraps some KMS library which implements crypto.Signer, this same check will not be performed due to the fact that it is an unknown library to us. And there's no way to query a crypto.Signer for its algorithm family.

v2.0.14 17 Oct 2023 [New Features]

• [jwk] jwk.IsPrivateKey(), as well as jwk.AsymmetricKey has been added. The function can be used to tell if a jwk.Key is a private key of an asymmetric key pair. [Security]
• golang.org/x/crypto has been updated to 0.14.0. The update contains a fix for HTTP/2 rapid reset DoS vulnerability, which some security scanning softwares may flag. However, do note that this library is NOT affected by the issue, as it does not have the capability to serve as an HTTP/2 server. This is included in this release document so that users will be able to tell why this library may be flagged when/if their scanning software do so.

Commits

• 8074e35 merge for v2.0.15 (#998)
• 42d47a7 Update Changes
• 2503747 Tweak 994 (#995)
• 2c061ee Fix typo from #994
• 051a1c6 Bump golang.org/x/crypto from 0.13.0 to 0.14.0 (#993)
• 7aa6fec add jwk.IsPrivate to check if an asymmetric key is public or private (#994)
• de6bd31 Merge commit '466c2774000a594f12a57dcf788be4e58e83ce04' into develop/v2
• d0e9b47 Update Changes
• c68c06c Upgrade golangci-lint to 1.54.2 (#986)
• c41f2a8 adapt to change in notation
• 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 <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)

[codecov-commenter]

Codecov Report

Merging #324 (a706bfd) into main (462c2a7) will not change coverage.
The diff coverage is n/a.

❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

@@           Coverage Diff           @@
##             main     #324   +/-   ##
=======================================
  Coverage   67.22%   67.22%           
=======================================
  Files          10       10           
  Lines        1605     1605           
=======================================
  Hits         1079     1079           
  Misses        489      489           
  Partials       37       37           

Flag	Coverage Δ
unittests	67.22% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more