Potential fix for code scanning alert no. 25: DOM text reinterpreted as HTML #734
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/GSA/eoc/security/code-scanning/25
To fix this vulnerability, we need to ensure that the value retrieved from the
data-lazyattribute (imageSource) is safe before using it as thesrcattribute of an image. The best way is to validate thatimageSourceis a URL with an allowed protocol (e.g.,http:,https:, or maybedata:), and does not start with dangerous schemes likejavascript:orvbscript:.The change should be applied in the
loadImagesfunction, specifically before settingimageToLoad.srcand/orimage.attr('src', imageSource). If the value is invalid, we should skip loading the image and mark it as an error.To implement this, we need a helper function to validate image URLs. We can define a simple validator within the same file, above the
loadImagesfunction.Suggested fixes powered by Copilot Autofix. Review carefully before merging.