The vulnerability stems from regex patterns in s3ParseUrl that lack safeguards against pathological input:
- All four regex patterns use unanchored greedy/non-greedy quantifiers ([^/]+), (.*?), and alternations (s3-|s3.) that enable exponential backtracking.
- The provided PoC demonstrates this by crafting a URL with 199,999 colons, causing the regex engine to process permutations combinatorially.
- The CWE-400 mapping confirms this is a resource consumption issue, and the advisory explicitly attributes the vulnerability to the regexes component.
- While no specific function names beyond s3ParseUrl exist (regexes are inline), the function's entire parsing logic is vulnerable due to its dependency on these regex patterns.
Miggo AI