Potential fix for code scanning alert no. 3: Reflected cross-site scripting - #15
Closed
aramprice wants to merge 1 commit into
Closed
Potential fix for code scanning alert no. 3: Reflected cross-site scripting#15aramprice wants to merge 1 commit into
aramprice wants to merge 1 commit into
Conversation
aramprice
marked this pull request as ready for review
August 6, 2026 17:06
Member
Author
|
GitHub workers are currently having issues, which is causing the PR checks to timeout: |
winkingturtle-vmw
previously approved these changes
Aug 13, 2026
…ipting Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
aramprice
force-pushed
the
alert-autofix-3
branch
from
August 13, 2026 15:46
fa20a1a to
12113b9
Compare
Member
Author
|
obsolete |
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
2 participants
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/cloudfoundry/go-fetcher/security/code-scanning/3
To fix this safely, apply HTML escaping to any user-influenced string before inserting it into generated HTML markup, especially attribute values.
Best minimal fix (without changing intended behavior): in
handlers/handler.go, import Go’s standardhtmlpackage and escaperepoPathright before it is used in the meta refresh output. Specifically:htmlto the existing import block.escapedRepoPath := html.EscapeString(repoPath)) before thefmt.Fprintfcall in thego-get=1branch.escapedRepoPathinstead ofrepoPathin the meta refresh format arguments.This preserves current response structure and redirect target semantics while neutralizing characters that can break HTML attribute context.
Suggested fixes powered by Copilot Autofix. Review carefully before merging.