[LEGIT] Fix - js/polynomial-redos#110
Open
liorn-test-app[bot] wants to merge 1 commit into
Open
Conversation
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.



🔍 The problem
Polynomial regular expression used on uncontrolled data
See issue in Legit
🔒 Fix Details
Fixed a Regular Expression Denial of Service (ReDoS) vulnerability in email validation. The original code applied a potentially complex regular expression (
EMAIL_RE) to user-controlled input without any length limit, which could allow an attacker to submit a specially crafted email string that causes catastrophic backtracking and CPU exhaustion.The fix adds an explicit length check (254 characters, per RFC 5321) before the regex validation. This bounds the maximum time the regex engine can run, preventing denial of service attacks even if the regex pattern contains nested quantifiers or other backtracking-prone constructs.
Note: The plan also recommended replacing
EMAIL_REwith a simpler pattern like/^[^\s@]+@[^\s@]+\.[^\s@]+$/, but since the regex definition is not visible in the provided code window, that change must be applied separately whereEMAIL_REis defined.