golang-github-golang-jwt-jwt
Affected
- introduced
0(ecosystem)
Fixed versions
None listed
Fix
No fixed version is listed.
Advisory
Also known as: CVE-2024-51744
The record has no summary.
golang-jwt is a Go implementation of JSON Web Tokens. 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. A fix has been back-ported with 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. 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.
Low Basis: CVSS v3 score 3.1, vector CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N
0 (ecosystem)None listed
No fixed version is listed.
0, fixed 5.0.0+really4.5.2-1 (ecosystem)5.0.0+really4.5.2-1
5.0.0+really4.5.2-1sudo apt-get update && sudo apt-get upgradeThis command upgrades the distribution's packages. Compare the fixed version with the version you have installed.
0, fixed 5.0.0+really4.5.2-1 (ecosystem)5.0.0+really4.5.2-1
5.0.0+really4.5.2-1sudo apt-get update && sudo apt-get upgradeThis command upgrades the distribution's packages. Compare the fixed version with the version you have installed.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: Debian Security Tracker (converted by OSV.dev)
Debian Security Tracker, converted to OSV by OSV.dev.