-
Vulnerability
-
Resolution: Duplicate
-
Critical
-
4.18.z
golang-jwt is a Go implementation of JSON Web Tokens. Prior to 5.2.2 and 4.5.2, the function parse.ParseUnverified splits (via a call to 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 bytes (where n stands for the length of the function's argument), with a constant factor of about 16. This issue is fixed in 5.2.2 and 4.5.2.
This security tracking issue was filed based on manifesting data available to Product Security in https://deptopia.prodsec.redhat.com/ui/home. This data indicates that the component noted in the "pscomponent" label was found to be affected by this vulnerability. If you believe this issue is not actionable and was created erroneously, please fill out the following form and close this issue as Closed with a resolution of Obsolete. This will prompt Product Security to review what type of error caused this Jira issue to be created, and prevent further mistakes of this type in the future.
https://forms.gle/LnXaf5aCAHaV6g8T8
To better understand the distinction between a component being Affected vs Not Affected, please read the following article:
https://docs.engineering.redhat.com/pages/viewpage.action?spaceKey=PRODSEC&title=Understanding+Affected+and+Not+Affected
- depends on
-
OCPBUGS-54620 github.com/golang-jwt/jwt allows excessive memory allocation during header parsing
-
- Closed
-
- is cloned by
-
OCPBUGS-54750 CVE-2025-30204 golang-jwt: jwt-go allows excessive memory allocation during header parsing [openshift-4.17]
-
- Closed
-
- is depended on by
-
OCPBUGS-54750 CVE-2025-30204 golang-jwt: jwt-go allows excessive memory allocation during header parsing [openshift-4.17]
-
- Closed
-
- links to