More information
#### Details
Improper error handling in ParseWithClaims and bad documentation may cause dangerous situations in github.com/golang-jwt/jwt
#### Severity
Unknown
#### References
- [https://github.com/golang-jwt/jwt/security/advisories/GHSA-29wx-vh33-7x7r](https://redirect.github.com/golang-jwt/jwt/security/advisories/GHSA-29wx-vh33-7x7r)
- [https://github.com/golang-jwt/jwt/commit/7b1c1c00a171c6c79bbdb40e4ce7d197060c1c2c](https://redirect.github.com/golang-jwt/jwt/commit/7b1c1c00a171c6c79bbdb40e4ce7d197060c1c2c)
This data is provided by [OSV](https://osv.dev/vulnerability/GO-2024-3250) and the [Go Vulnerability Database](https://redirect.github.com/golang/vulndb) ([CC-BY 4.0](https://redirect.github.com/golang/vulndb#license)).
Bad documentation of error handling in ParseWithClaims can lead to potentially dangerous situations
More information
#### Details
##### Summary
Unclear documentation of the error behavior in `ParseWithClaims` can lead to situation where users are potentially not checking errors in the way they should be. Especially, if a token is both expired and invalid, the errors returned by `ParseWithClaims` return both error codes. If users only check for the `jwt.ErrTokenExpired ` using `error.Is`, they will ignore the embedded `jwt.ErrTokenSignatureInvalid` and thus potentially accept invalid tokens.
##### Fix
We have back-ported the error handling logic from the `v5` branch to the `v4` branch. In this logic, the `ParseWithClaims` function will immediately return in "dangerous" situations (e.g., an invalid signature), limiting the combined errors only to situations where the signature is valid, but further validation failed (e.g., if the signature is valid, but is expired AND has the wrong audience). This fix is part of the 4.5.1 release.
##### Workaround
We are aware that this changes the behaviour of an established function and is not 100 % backwards compatible, so updating to 4.5.1 might break your code. In case you cannot update to 4.5.0, please make sure that you are properly checking for all errors ("dangerous" ones first), so that you are not running in the case detailed above.
```Go
token, err := /* jwt.Parse or similar */
if token.Valid {
fmt.Println("You look nice today")
} else if errors.Is(err, jwt.ErrTokenMalformed) {
fmt.Println("That's not even a token")
} else if errors.Is(err, jwt.ErrTokenUnverifiable) {
fmt.Println("We could not verify this token")
} else if errors.Is(err, jwt.ErrTokenSignatureInvalid) {
fmt.Println("This token has an invalid signature")
} else if errors.Is(err, jwt.ErrTokenExpired) || errors.Is(err, jwt.ErrTokenNotValidYet) {
// Token is either expired or not active yet
fmt.Println("Timing is everything")
} else {
fmt.Println("Couldn't handle this token:", err)
}
```
#### Severity
- CVSS Score: 3.1 / 10 (Low)
- Vector String: `CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N`
#### References
- [https://github.com/golang-jwt/jwt/security/advisories/GHSA-29wx-vh33-7x7r](https://redirect.github.com/golang-jwt/jwt/security/advisories/GHSA-29wx-vh33-7x7r)
- [https://nvd.nist.gov/vuln/detail/CVE-2024-51744](https://nvd.nist.gov/vuln/detail/CVE-2024-51744)
- [https://github.com/golang-jwt/jwt/commit/7b1c1c00a171c6c79bbdb40e4ce7d197060c1c2c](https://redirect.github.com/golang-jwt/jwt/commit/7b1c1c00a171c6c79bbdb40e4ce7d197060c1c2c)
- [https://github.com/golang-jwt/jwt](https://redirect.github.com/golang-jwt/jwt)
This data is provided by [OSV](https://osv.dev/vulnerability/GHSA-29wx-vh33-7x7r) and the [GitHub Advisory Database](https://redirect.github.com/github/advisory-database) ([CC-BY 4.0](https://redirect.github.com/github/advisory-database/blob/main/LICENSE.md)).
Release Notes
golang-jwt/jwt (github.com/golang-jwt/jwt/v4)
### [`v4.5.1`](https://redirect.github.com/golang-jwt/jwt/releases/tag/v4.5.1)
[Compare Source](https://redirect.github.com/golang-jwt/jwt/compare/v4.5.0...v4.5.1)
### Security
Unclear documentation of the error behavior in `ParseWithClaims` in <= 4.5.0 could lead to situation where users are potentially not checking errors in the way they should be. Especially, if a token is both expired and invalid, the errors returned by `ParseWithClaims` return both error codes. If users only check for the ` jwt.ErrTokenExpired ` using `error.Is`, they will ignore the embedded `jwt.ErrTokenSignatureInvalid` and thus potentially accept invalid tokens.
This issue was documented in https://github.com/golang-jwt/jwt/security/advisories/GHSA-29wx-vh33-7x7r and fixed in this release.
Note: `v5` was not affected by this issue. So upgrading to this release version is also recommended.
### What's Changed
- Back-ported error-handling logic in `ParseWithClaims` from `v5` branch. This fixes https://github.com/golang-jwt/jwt/security/advisories/GHSA-29wx-vh33-7x7r.
**Full Changelog**: https://github.com/golang-jwt/jwt/compare/v4.5.0...v4.5.1
Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
[ ] If you want to rebase/retry this PR, check this box
This PR contains the following updates:
v4.5.0->v4.5.1Improper error handling in ParseWithClaims and bad documentation may cause dangerous situations in github.com/golang-jwt/jwt
CVE-2024-51744 / GHSA-29wx-vh33-7x7r / GO-2024-3250
More information
#### Details Improper error handling in ParseWithClaims and bad documentation may cause dangerous situations in github.com/golang-jwt/jwt #### Severity Unknown #### References - [https://github.com/golang-jwt/jwt/security/advisories/GHSA-29wx-vh33-7x7r](https://redirect.github.com/golang-jwt/jwt/security/advisories/GHSA-29wx-vh33-7x7r) - [https://github.com/golang-jwt/jwt/commit/7b1c1c00a171c6c79bbdb40e4ce7d197060c1c2c](https://redirect.github.com/golang-jwt/jwt/commit/7b1c1c00a171c6c79bbdb40e4ce7d197060c1c2c) This data is provided by [OSV](https://osv.dev/vulnerability/GO-2024-3250) and the [Go Vulnerability Database](https://redirect.github.com/golang/vulndb) ([CC-BY 4.0](https://redirect.github.com/golang/vulndb#license)).Bad documentation of error handling in ParseWithClaims can lead to potentially dangerous situations
CVE-2024-51744 / GHSA-29wx-vh33-7x7r / GO-2024-3250
More information
#### Details ##### Summary Unclear documentation of the error behavior in `ParseWithClaims` can lead to situation where users are potentially not checking errors in the way they should be. Especially, if a token is both expired and invalid, the errors returned by `ParseWithClaims` return both error codes. If users only check for the `jwt.ErrTokenExpired ` using `error.Is`, they will ignore the embedded `jwt.ErrTokenSignatureInvalid` and thus potentially accept invalid tokens. ##### Fix We have back-ported the error handling logic from the `v5` branch to the `v4` branch. In this logic, the `ParseWithClaims` function will immediately return in "dangerous" situations (e.g., an invalid signature), limiting the combined errors only to situations where the signature is valid, but further validation failed (e.g., if the signature is valid, but is expired AND has the wrong audience). This fix is part of the 4.5.1 release. ##### Workaround We are aware that this changes the behaviour of an established function and is not 100 % backwards compatible, so updating to 4.5.1 might break your code. In case you cannot update to 4.5.0, please make sure that you are properly checking for all errors ("dangerous" ones first), so that you are not running in the case detailed above. ```Go token, err := /* jwt.Parse or similar */ if token.Valid { fmt.Println("You look nice today") } else if errors.Is(err, jwt.ErrTokenMalformed) { fmt.Println("That's not even a token") } else if errors.Is(err, jwt.ErrTokenUnverifiable) { fmt.Println("We could not verify this token") } else if errors.Is(err, jwt.ErrTokenSignatureInvalid) { fmt.Println("This token has an invalid signature") } else if errors.Is(err, jwt.ErrTokenExpired) || errors.Is(err, jwt.ErrTokenNotValidYet) { // Token is either expired or not active yet fmt.Println("Timing is everything") } else { fmt.Println("Couldn't handle this token:", err) } ``` #### Severity - CVSS Score: 3.1 / 10 (Low) - Vector String: `CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N` #### References - [https://github.com/golang-jwt/jwt/security/advisories/GHSA-29wx-vh33-7x7r](https://redirect.github.com/golang-jwt/jwt/security/advisories/GHSA-29wx-vh33-7x7r) - [https://nvd.nist.gov/vuln/detail/CVE-2024-51744](https://nvd.nist.gov/vuln/detail/CVE-2024-51744) - [https://github.com/golang-jwt/jwt/commit/7b1c1c00a171c6c79bbdb40e4ce7d197060c1c2c](https://redirect.github.com/golang-jwt/jwt/commit/7b1c1c00a171c6c79bbdb40e4ce7d197060c1c2c) - [https://github.com/golang-jwt/jwt](https://redirect.github.com/golang-jwt/jwt) This data is provided by [OSV](https://osv.dev/vulnerability/GHSA-29wx-vh33-7x7r) and the [GitHub Advisory Database](https://redirect.github.com/github/advisory-database) ([CC-BY 4.0](https://redirect.github.com/github/advisory-database/blob/main/LICENSE.md)).Release Notes
golang-jwt/jwt (github.com/golang-jwt/jwt/v4)
### [`v4.5.1`](https://redirect.github.com/golang-jwt/jwt/releases/tag/v4.5.1) [Compare Source](https://redirect.github.com/golang-jwt/jwt/compare/v4.5.0...v4.5.1) ### Security Unclear documentation of the error behavior in `ParseWithClaims` in <= 4.5.0 could lead to situation where users are potentially not checking errors in the way they should be. Especially, if a token is both expired and invalid, the errors returned by `ParseWithClaims` return both error codes. If users only check for the ` jwt.ErrTokenExpired ` using `error.Is`, they will ignore the embedded `jwt.ErrTokenSignatureInvalid` and thus potentially accept invalid tokens. This issue was documented in https://github.com/golang-jwt/jwt/security/advisories/GHSA-29wx-vh33-7x7r and fixed in this release. Note: `v5` was not affected by this issue. So upgrading to this release version is also recommended. ### What's Changed - Back-ported error-handling logic in `ParseWithClaims` from `v5` branch. This fixes https://github.com/golang-jwt/jwt/security/advisories/GHSA-29wx-vh33-7x7r. **Full Changelog**: https://github.com/golang-jwt/jwt/compare/v4.5.0...v4.5.1Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.