Potential fix for code scanning alert no. 15: Uncontrolled data used in path expression - #1
Merged
Merged
Conversation
…in path expression Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThe changes add path normalization and traversal checks to static-file routing and ETag generation. Static routing serves normalized existing files or ChangesStatic path safety
Estimated code review effort: 3 (Moderate) | ~20 minutes ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
bonheur15
marked this pull request as ready for review
August 16, 2026 11:32
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
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/hubfly-space/go-php/security/code-scanning/15
The best fix is to canonicalize and validate request paths before any filesystem operation, then only operate on a safe, relative path guaranteed to stay inside the intended root.
internal/filesystem/cache.goIn
setETag, replace directfilepath.Join(s.Root, filepath.Clean(path))with:strings.TrimPrefix(..., "/")),.., absolute, empty edge cases as needed),s.Root,os.Stat.This preserves functionality (ETag generation for valid static paths) while blocking traversal.
internal/ui/server.goIn the static handler, sanitize
r.URL.PathbeforestaticFS.Open(path[1:]):path.Cleanfrom stdlib’s slash-basedpathpackage),/,..traversal semantics,staticFS.Open,r.URL.Pathto sanitized absolute path before delegating tofileServer.This single sanitization flow addresses both additional variants where tainted
r.URLinfluences filesystem path handling.Suggested fixes powered by Copilot Autofix. Review carefully before merging.
Summary by CodeRabbit