fix: Escape special characters in regex pattern#1122
Open
odaysec wants to merge 2 commits intoGoogleChrome:mainfrom
Open
fix: Escape special characters in regex pattern#1122odaysec wants to merge 2 commits intoGoogleChrome:mainfrom
odaysec wants to merge 2 commits intoGoogleChrome:mainfrom
Conversation
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
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.
lighthouse-ci/packages/cli/src/collect/collect.js
Line 162 in ebee453
Constructing a regular expression with unsanitized user input is dangerous as a malicious user may be able to modify the meaning of the expression. In particular, such a user may be able to provide a regular expression fragment that takes exponential time in the worst case, and use that to perform a Denial of Service attack.
General approach: Avoid constructing a
RegExpdirectly from unsanitized user input or, if regular expressions must be user‑supplied, validate or constrain them to prevent pathological behavior. Common options are: escaping meta‑characters (turning input into a literal pattern), whitelisting simple allowed constructs, or rejecting patterns that exceed size/complexity limits.Best fix here without changing intended functionality too much:
startServerReadyPatternis meant to be “a pattern the server prints when it is ready.” In practice, users usually specify a literal string likeListening on 8080. Treating this as a literal substring search is sufficient and simpler than exposing full regex power.RegExp, but we should escape all regex metacharacters in the user input so it’s interpreted literally. This preserves user expectations for simple patterns and removes the ability to inject complex or catastrophic regexes.escapeRegExpincollect.js(rather than adding new dependencies) and apply it tooptions.startServerReadyPatternbefore constructing theRegExp.Concretely:
In
packages/cli/src/collect/collect.js, define a localescapeRegExputility near the top of the file.In
startServerAndDetermineUrls, replace the line:with:
This:
undefined/null.