Potential fix for code scanning alert no. 8: Inefficient regular expression#23
Draft
admin-it-jupiterone wants to merge 1 commit into
Draft
Potential fix for code scanning alert no. 8: Inefficient regular expression#23admin-it-jupiterone wants to merge 1 commit into
admin-it-jupiterone wants to merge 1 commit into
Conversation
…ession Testing GitHub code scanning using their AI to generate fixes, this may be old, stale, or not applicable. Please review and let me know. Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
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
1 participant
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.
Potential fix for https://github.com/JupiterOne/tinkerpop/security/code-scanning/8
General fix approach: remove ambiguity inside the repeated alternation by ensuring generic branches cannot consume prefixes of specific multi-character branches. Practically, exclude
<from the fallback character class so<<0>>is matched only by its dedicated alternative.Best minimal functional fix in
docs/site/home/js/prism.js:/(^|[^@\\])\$"(?:\\.|\{\{|<<0>>|[^\\"{])*"//(^|[^@\\])\$"(?:\\.|\{\{|<<0>>|[^\\"{<]|<(?!<0>>))*"/Why this preserves behavior:
<was consumed by[^\\"{].<is consumed either as part of<<0>>or as a single<when it is not the start of<<0>>(<(?!<0>>)).No imports, helper methods, or dependency changes are required.
Suggested fixes powered by Copilot Autofix. Review carefully before merging.