Function parse.ParseUnverified
currently 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(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)
Excessive memory allocation
{ "nvd_published_at": "2025-03-21T22:15:26Z", "cwe_ids": [ "CWE-405" ], "severity": "HIGH", "github_reviewed": true, "github_reviewed_at": "2025-03-21T22:04:00Z" }