-
Notifications
You must be signed in to change notification settings - Fork 0
Potential fix for code scanning alert no. 2: DOM text reinterpreted as HTML #34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
niyazialpay
wants to merge
1
commit into
main
Choose a base branch
from
alert-autofix-2
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
Check failure
Code scanning / CodeQL
DOM text reinterpreted as HTML High
Copilot Autofix
AI about 1 month ago
In general, the fix is to ensure that untrusted text taken from the DOM (here,
data-target/href) is not passed directly toa(...)(jQuery) in a way that could be interpreted as HTML. Instead, we should either (1) validate that it is a safe, restricted selector pattern before using it in$(), or (2) use APIs that only ever interpret it as a selector and never as HTML, or (3) fall back to a safe default (like the closest.alert) when the selector is unsafe.The best fix, preserving existing behavior, is to validate
fagainst a strict pattern for allowed selectors and discard it when it doesn’t match. You already have a helperd._isSafeSelector(lines 67–71) that allows only simple ID selectors like#my-alert. The minimal, targeted change is to ensure that any unsafe selector results in no element being selected (so jQuery is never invoked with potentially HTML-looking strings). Currently we already have:However, this still uses the slightly odd
"#" === f ? [] : fexpression, which is unnecessary whenfis eithernullor a validated ID selector (it will always start with#and have more than one character if valid). We can simplify and make the intent clearer by:d._isSafeSelector(f)as the gatekeeper.f ? a(f) : a();instead of"#" === f ? [] : f, sincefwill benullfor unsafe or empty values and a valid#idstring for safe ones.#idselectors reach it.Concretely, in
public/themes/Default/js/bootstrap.jswithind.prototype.close, we will:_isSafeSelectorhelper as-is."#" === f ? [] : fternary and rely solely on the safe/unsafe guard on line 81.No new methods or imports are required; we only adjust the use of
fwhen constructing the jQuery object.