golang-jwt up to 4.5.0 JSON Web Token exceptional condition

Summaryinfo

A vulnerability identified as problematic has been detected in golang-jwt jwt up to 4.5.0. This impacts an unknown function of the component JSON Web Token Handler. The manipulation leads to exceptional condition. This vulnerability is documented as CVE-2024-51744. The attack can be initiated remotely. There is not any exploit available. You should upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in golang-jwt jwt up to 4.5.0. This issue affects some unknown functionality of the component JSON Web Token Handler. The manipulation with an unknown input leads to a exceptional condition vulnerability. Using CWE to declare the problem leads to CWE-755. The product does not handle or incorrectly handles an exceptional condition. Impacted is confidentiality. The summary by CVE is:

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.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2024-51744 since 10/31/2024. The exploitation is known to be difficult. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available.

The vulnerability scanner Nessus provides a plugin with the ID 212587 (SUSE SLES15 / openSUSE 15 Security Update : govulncheck-vulndb (SUSE-SU-2024:4042-1)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 4.5.1 eliminates this vulnerability. Applying the patch 7b1c1c00a171c6c79bbdb40e4ce7d197060c1c2c is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the vulnerability database at Tenable (212587). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• golang-jwt

Name

• jwt

Version

• 4.0
• 4.1
• 4.2
• 4.3
• 4.4
• 4.5.0

License

• open-source

Website

• Product: https://github.com/golang-jwt/jwt/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion