Potential fix for code scanning alert no. 1: Incomplete multi-character sanitization #5
+15,148
−10,392
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/github/rollup-and-away/security/code-scanning/1
General approach: Ensure that after
stripHtmlruns, no residual<script,<style, generic tags, or HTML comments can remain due to overlapping or nested matches. Following the recommended pattern, we can repeatedly apply the same replacement until the string stabilizes (no further changes), which guarantees that any new dangerous substrings created by prior replacements are also removed. This preserves existing behavior for typical inputs but closes the multi-character sanitization gap.Concrete fix for
src/util/string.ts:stripHtmlso it does not calls.replacejust once. Instead:do { … } while (…)orwhile (true)with a break) that repeatedly applies.replace(regex, "")to the current string.stripHtml.This single change in
stripHtmladdresses all 4 alert variants, as the loop guarantees that any residual<script,<style,<-tags, or<!--resulting from overlapping matches will be removed in subsequent iterations.Suggested fixes powered by Copilot Autofix. Review carefully before merging.