decode-uri-component: Denial of service via quadratic replacement of percent-encoded runs
What fixes it
No source in this snapshot names a fixed version. The vendor advisories under References are the place to check.
Description
decode-uri-component provides a more robust alternative to decodeURIComponent. Prior to 0.5.1, decodeUriComponent in index.js falls back to customDecodeURIComponent after native decoding throws, and the fallback collects every distinct percent-encoded run before performing a full-string regular-expression replacement for each entry. Malformed input containing many distinct runs can therefore make both the number of replacements and the scanned input length grow together, causing quadratic CPU consumption and blocking the Node.js event loop; request-body inputs can reach the demonstrated size, while ordinary URL header limits reduce the practical delay. This issue is fixed in version 0.5.1.
Text from CVE List
Affected versions 1
- decode-uri-componentaffected: < 0.5.1CVE List