GHSA-mh63-6h87-95cp
jwt-go allows excessive memory allocation during header parsing
At a glance
- Published
- Updated
- CVE
- CVE-2025-30204
- Aliases
- GO-2025-3553
- CVSS_V3
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- CVSS_V4
- CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
Description
### 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
Affected packages
| Package | Versions |
|---|---|
| Go · github.com/golang-jwt/jwt/v5 | introduced 5.0.0-rc.1, fixed 5.2.2 |
| Go · github.com/golang-jwt/jwt/v4 | introduced 0, fixed 4.5.2 |
| Go · github.com/golang-jwt/jwt | introduced 3.2.0, last affected 3.2.2 |
References
- https://github.com/golang-jwt/jwt/security/advisories/GHSA-mh63-6h87-95cp WEB
- https://nvd.nist.gov/vuln/detail/CVE-2025-30204 ADVISORY
- https://github.com/golang-jwt/jwt/commit/0951d184286dece21f73c85673fd308786ffe9c3 WEB
- https://github.com/golang-jwt/jwt/commit/bf316c48137a1212f8d0af9288cc9ce8e59f1afb WEB
- https://github.com/golang-jwt/jwt PACKAGE
- https://security.netapp.com/advisory/ntap-20250404-0002 WEB
Sources
| Source | Licence |
|---|---|
| OSV.dev | CC-BY 4.0 — GitHub Advisory Database |