This repository has been archived by the owner on Dec 19, 2023. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
馃搳 Metadata *
Bounty URL: https://www.huntr.dev/bounties/1-maven-url-regex
鈿欙笍 Description *
The project
url-regex
was validating URLs with a regex vulnerable to ReDoS (Regex Denial of Service) withRegExp()
.馃捇 Technical Description *
The implemented Regex patterns to validate URLs are vulnerable to ReDoS:
Using a long string to make it pass through this regex will lead to Denial of Service.
馃悰 Proof of Concept (PoC) *
馃敟 Proof of Fix (PoF) *
As the used Regex is perfect to validate URLs but just vulnerable to ReDoS, I implemented
node-re2
instead of the JavaScriptRegExp()
function asre2
can convert a vulnerable Regex pattern to a safe one preventing any backtracking regular expressions/attacks.馃摎 Reference:
String.test
will never finish聽kevva/url-regex#70 (comment)馃憤 User Acceptance Testing (UAT)
Replaced the usage of
RegExp()
function with a safer regex bindingnode-re2
.