golang-github-golang-jwt-jwt: golang-jwt is a Go implementation of JSON Web Tokens
CVE-2024-51744 is fixed in 14 products on 1 platform, first by DEBIAN-CVE-2024-51744, released November 4, 2024. It is not reported as exploited. Patch Radar priority: Routine.
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.
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| coredns · opensuse-leap 15.6 | 1.12.1-bp156.4.6.5 | OPENSUSE-SU-2025:0131-1 | Apr 19, 2025 |
| coredns · opensuse-leap 16.0 | 1.14.0-bp160.1.1 | OPENSUSE-SU-2026:20099-1 | Jan 24, 2026 |
| cosign · opensuse-leap 15.6 | 2.5.0-150400.3.27.1 | SUSE-SU-2025:1333-1 | Apr 17, 2025 |
| cosign · sles 15.6 | 2.5.0-150400.3.27.1 | SUSE-SU-2025:1333-1 | Apr 17, 2025 |
| docker · amzn 2023 | 25.0.8-1.amzn2023.0.1 | ALAS2023-2025-852 | Feb 12, 2025 |
| docker-debuginfo · amzn 2023 | 25.0.8-1.amzn2023.0.1 | ALAS2023-2025-852 | Feb 12, 2025 |
| docker-debugsource · amzn 2023 | 25.0.8-1.amzn2023.0.1 | ALAS2023-2025-852 | Feb 12, 2025 |
| dracut-saltboot · opensuse-leap 15.6 | 0.1.1728559936.c16d4fb-150000.1.56.1 | SUSE-SU-2025:0525-1 | Feb 14, 2025 |
| golang-github-golang-jwt-jwt · Debian 13.5 (trixie) | 5.0.0+really4.5.2-1 | DEBIAN-CVE-2024-51744 | Nov 4, 2024 |
| golang-github-golang-jwt-jwt · Debian 14 | 5.0.0+really4.5.2-1 | DEBIAN-CVE-2024-51744 | Nov 4, 2024 |
| golang-github-prometheus-prometheus · opensuse-leap 15.6 | 2.53.3-150100.4.23.1 | SUSE-SU-2025:0546-1 | Feb 14, 2025 |
| golang-github-prometheus-prometheus · sles 15.6 | 2.53.3-150100.4.23.1 | SUSE-SU-2025:0546-1 | Feb 14, 2025 |
| golang-github-prometheus-promu · opensuse-leap 15.6 | 0.17.0-150000.3.24.1 | SUSE-SU-2025:0525-1 | Feb 14, 2025 |
| golang-github-prometheus-promu · sles 15.6 | 0.17.0-150000.3.24.1 | SUSE-SU-2025:0525-1 | Feb 14, 2025 |
| govulncheck-vulndb · opensuse-leap 15.6 | 0.0.20241112T145010-150000.1.17.1 | SUSE-SU-2024:4042-1 | Nov 22, 2024 |
| govulncheck-vulndb · sles 15.6 | 0.0.20241112T145010-150000.1.17.1 | SUSE-SU-2024:4042-1 | Nov 22, 2024 |
| runfinch-finch · amzn 2023 | 1.6.0-1.amzn2023.0.1 | ALAS2023-2025-834 | Jan 30, 2025 |
| spacecmd · opensuse-leap 15.6 | 5.0.11-150000.3.130.1 | SUSE-SU-2025:0525-1 | Feb 14, 2025 |
| supportutils-plugin-salt · opensuse-leap 15.6 | 1.2.3-150000.3.16.1 | SUSE-SU-2025:0525-1 | Feb 14, 2025 |
| supportutils-plugin-salt · sles 15.6 | 1.2.3-150000.3.16.1 | SUSE-SU-2025:0525-1 | Feb 14, 2025 |
| supportutils-plugin-susemanager-client · opensuse-leap 15.6 | 5.0.4-150000.3.27.1 | SUSE-SU-2025:0525-1 | Feb 14, 2025 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.