VDB
Sign up
HIGH7.5

GHSA-mh63-6h87-95cp

jwt-go allows excessive memory allocation during header parsing

Quick fix

GHSA-mh63-6h87-95cp — github.com/golang-jwt/jwt/v5: upgrade to the fixed version with the command below.

go get github.com/golang-jwt/jwt/v5@v5.2.2

Details

### Summary

Function [`parse.ParseUnverified`](https://github.com/golang-jwt/jwt/blob/c035977d9e11c351f4c05dfeae193923cbab49ee/parser.go#L138-L139) currently splits (via a call to [strings.Split](https://pkg.go.dev/strings#Split)) its argument (which is untrusted data) on periods.

As a result, in the face of a malicious request whose _Authorization_ header consists of `Bearer ` followed by many period characters, a call to that function incurs allocations to the tune of O(n) bytes (where n stands for the length of the function's argument), with a constant factor of about 16. Relevant weakness: [CWE-405: Asymmetric Resource Consumption (Amplification)](https://cwe.mitre.org/data/definitions/405.html)

### Details

See [`parse.ParseUnverified`](https://github.com/golang-jwt/jwt/blob/c035977d9e11c351f4c05dfeae193923cbab49ee/parser.go#L138-L139)

### Impact

Excessive memory allocation

Are you affected?

Enter the version of the package you're using.

Affected packages

Go/github.com/golang-jwt/jwt/v5
Introduced in: 5.0.0-rc.1Fixed in: 5.2.2
Fixgo get github.com/golang-jwt/jwt/v5@v5.2.2
Go/github.com/golang-jwt/jwt/v4
Introduced in: 0Fixed in: 4.5.2
Fixgo get github.com/golang-jwt/jwt/v4@v4.5.2
Go/github.com/golang-jwt/jwt
Introduced in: 3.2.0

No fixed version published yet for github.com/golang-jwt/jwt (go modules). Pin to a known-safe version or switch to an alternative.

References