x/vulndb: potential Go vuln in go-jose

[mschwager]

Acknowledgement

• The maintainer(s) of the affected project have already been made aware of this vulnerability.

Description

The go-jose package is subject to a "billion hashes attack" causing denial-of-service when decrypting JWE inputs. This occurs when an attacker can provide a PBES2 encrypted JWE blob with a very large p2c value that, when decrypted, produces a denial-of-service.

Affected Modules, Packages, Versions and Symbols

Module: github.com/go-jose/go-jose
Package: github.com/go-jose/go-jose/v3
Versions:
  - Introduced: 3.0.0
  - Fixed: 3.0.1
Symbols:
  - JSONWebEncryption.Decrypt

Module: gopkg.in/square/go-jose.v2
Package: gopkg.in/square/go-jose.v2
Versions:
  - Introduced: 2.6.0
Symbols:
  - JSONWebEncryption.Decrypt

CVE/GHSA ID

No response

Fix Commit or Pull Request

go-jose/go-jose#66

References

• https://i.blackhat.com/BH-US-23/Presentations/US-23-Tervoort-Three-New-Attacks-Against-JSON-Web-Tokens.pdf
• https://nvd.nist.gov/vuln/detail/CVE-2022-36083
• https://auth0.com/blog/critical-vulnerabilities-in-json-web-token-libraries/

Additional information

Tracing vulnerable package/module versions backwards is a bit of a challenge since go-jose/go-jose is a fork of square/go-jose. The Square version is unmaintained and states: "No support, security fixes or updates will be delivered to the v1/v2 branches in the Square repository." This vulnerability may be a good opportunity to encourage users to move to the maintained package.

I've confirmed that the Square package at version 2.6.0 is vulnerable, but I haven't traced it all the way back to which version introduced the vulnerability. I suspect it's always been there. This library is provided by the following packages (which have considerable importedby size):

• https://pkg.go.dev/gopkg.in/square/go-jose.v2
• https://pkg.go.dev/github.com/square/go-jose

[gopherbot]

Change https://go.dev/cl/544075 mentions this issue: data/reports: add GO-2023-2334.yaml

[gopherbot]

Change https://go.dev/cl/545955 mentions this issue: data/reports/GO-2023-2334: add GHSA reference