Repository navigation
fix(serve): resolve symlinks in path-traversal boundary check - #55
Merged
Merged
Conversation
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
1 participant
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.
Fixes #27
The lexical boundary check (
normalize().starts_with(serve_dir_abs)) does not resolve symlinks, so a symlink inside the served tree could point outside it.The served directory is canonicalized once at startup, and each request path is canonicalized before being served. Requests that resolve outside the served directory get a 403. The
index.htmlfallback is checked too, since it replaces the target path after the first check.Verified locally: symlinked directory and symlinked file both return 403 while normal files return 200.