
Let's look at how our expression runs into this problem, using a shorter string: "ACCCX". If it goes too far down the rabbit hole only to find out the string doesn’t match in the end, and if many characters have multiple valid regex paths, the number of backtracking steps can become very large, resulting in what is known as catastrophic backtracking. If it then fails to match the next one, it will backtrack and see if there was another way to digest the previous character.


The engine will match the first possible way to accept the current character and proceed to the next one. Most Regex engines will work very similarly (with minor differences). The dramatic difference is due to the way regular expressions get evaluated. But when given an invalid string, it takes nearly two seconds to complete the test, over ten times as long as it took to test a valid string. The entire process of testing it against a 30 characters long string takes around ~52ms. $ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCX")'ġ.79s user 0.02s system 99% cpu 1.812 total It most cases, it doesn't take very long for a regex engine to find a match: $ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCD")'Ġ.04s user 0.01s system 95% cpu 0.052 total The expression would match inputs such as ABBD, ABCCCCD, ABCBCCCD and ACCCCCD

Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) when parsing crafted invalid CSS nth-checks, due to the sub-pattern \s*(?:(?)\s*(\d+))? in RE_NTH_ELEMENT with quantified overlapping adjacency.
