Question 1

Is there a bug in github.com/golang-jwt/jwt 5.0.0-rc.1?

Accepted Answer

jwt-go allows excessive memory allocation during header parsing ### 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 Fixed in github.com/golang-jwt/jwt 5.2.2.

Question 2

Is there a bug in github.com/golang-jwt/jwt?

Accepted Answer

Excessive memory allocation during header parsing in github.com/golang-jwt/jwt Excessive memory allocation during header parsing in github.com/golang-jwt/jwt Fixed in github.com/golang-jwt/jwt 4.5.2.

github.com/golang-jwt/jwt known bugs