GHSA-v2p6-4mp7-3r9v json
Regular Expression Denial of Service in underscore.string
published 7y ago modified 6y ago
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
Versions of `underscore.string` prior to *3.3.5* are vulnerable to Regular Expression Denial of Service (ReDoS).
The function `unescapeHTML` is vulnerable to ReDoS due to an overly-broad regex. The slowdown is approximately 2s for 50,000 characters but grows exponentially with larger inputs.
## Recommendation
Upgrade to version 3.3.5 or higher.
Patch / fix
- npm underscore.string 3.3.5
- github.com/epeli/underscore.string@f486cd6 commit
- github.com/epeli/underscore.string#517 pull request
Is GHSA-v2p6-4mp7-3r9v in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | underscore.string | <3.3.5 |
3.3.5 |
Classification
- Weakness
-
- CWE-400 Uncontrolled Resource Consumption
References
Sources
- GitHub Advisory GHSA-v2p6-4mp7-3r9v
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.