CVE-2025-30204

ADVISORY - github

Summary

Summary

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)

Details

See parse.ParseUnverified

Impact

Excessive memory allocation

EPSS Score⁠: 0.00025 (0.053)

Common Weakness Enumeration (CWE)

ADVISORY - nist

CWE-405⁠

Asymmetric Resource Consumption (Amplification)

ADVISORY - github

CWE-405⁠

Asymmetric Resource Consumption (Amplification)

ADVISORY - gitlab

CWE-1035⁠

OWASP Top Ten 2017 Category A9 - Using Components with Known Vulnerabilities

CWE-405⁠

Asymmetric Resource Consumption (Amplification)

CWE-937⁠

OWASP Top Ten 2013 Category A9 - Using Components with Known Vulnerabilities

Impacted images

Sign in to Docker Scout

See which of your images are affected by this CVE and how to fix them by signing into Docker Scout.