github.com/Azure/go-autorest/autorest/adal-v0.9.16: 1 vulnerabilities (highest severity is: 3.1)

[ibm-mend-app]

Vulnerable Library - github.com/Azure/go-autorest/autorest/adal-v0.9.16

Path to dependency file: /go.mod

Path to vulnerable library: /home/wss-scanner/go/pkg/mod/cache/download/github.com/golang-jwt/jwt/v4/@v/v4.4.2.mod

Found in HEAD commit: a38d6324242b44e86f4799b7caed176ba9620b92

Vulnerabilities

CVE	Severity	CVSS	Dependency	Type	Fixed in (github.com/Azure/go-autorest/autorest/adal-v0.9.16 version)	Remediation Possible**
CVE-2024-51744	Low	3.1	github.com/golang-JWT/jwt/v4-v4.4.2	Transitive	N/A*	❌

*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the "Details" section below to see if there is a version of transitive dependency where vulnerability is fixed.

**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation

Details

CVE-2024-51744

Vulnerable Library - github.com/golang-JWT/jwt/v4-v4.4.2

Community maintained clone of https://github.com/dgrijalva/jwt-go

Library home page: https://proxy.golang.org/github.com/golang-!j!w!t/jwt/v4/@v/v4.4.2.zip

Path to dependency file: /go.mod

Path to vulnerable library: /home/wss-scanner/go/pkg/mod/cache/download/github.com/golang-jwt/jwt/v4/@v/v4.4.2.mod

Dependency Hierarchy:

• github.com/Azure/go-autorest/autorest/adal-v0.9.16 (Root Library)
  • ❌ github.com/golang-JWT/jwt/v4-v4.4.2 (Vulnerable Library)

Found in HEAD commit: a38d6324242b44e86f4799b7caed176ba9620b92

Found in base branch: master

Vulnerability Details

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.

Publish Date: 2024-11-04

URL: CVE-2024-51744

CVSS 3 Score Details (3.1)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: High
  • Privileges Required: None
  • User Interaction: Required
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: Low
  • Integrity Impact: None
  • Availability Impact: None

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: GHSA-29wx-vh33-7x7r

Release Date: 2024-11-04

Fix Resolution: github.com/golang-jwt/jwt-v4.5.1