Fix code scanning alert no. 1: Regular expression injection #6
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.
Fixes https://github.com/sede-open/github-tag-action/security/code-scanning/1
To fix the problem, we need to sanitize the
tagPrefix
input before using it in the regular expression. The best way to do this is by using a sanitization function such as_.escapeRegExp
from the lodash library. This function escapes special characters in the input that have special meaning in regular expressions, thus preventing injection attacks._.escapeRegExp
function from lodash._.escapeRegExp
to sanitize thetagPrefix
input before constructing the regular expression.Suggested fixes powered by Copilot Autofix. Review carefully before merging.