fix: prevent path traversal in search path parameter#66
Open
Conversation
Prevent path traversal by validating that search paths resolve to locations within the current working directory (or allowed root). This affects both the HTTP server API and the core search engine logic. Fixes #201
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.
This PR fixes a path traversal vulnerability where the
pathparameter in search requests could be used to access files outside the intended directory.Changes:
src/server/api.rs) and the Core Search Engine (src/core/search.rs).Security Impact:
Prevents attackers from using
../sequences to search or enumerate files outside the indexed/server directory.