Repository navigation
Validate hash, version, and share parameters in server requests. - #1804
Merged
Merged
Conversation
Server endpoints previously decoded request identifiers with partial UTF-8 conversion and passed raw parameter values directly into filesystem lookups. Malformed or missing parameters could trigger unhandled pattern-match, UTF-8 decoding, or filesystem exceptions instead of returning a 404 response. Check that hash and version parameters match the expected ASCII identifier format and that resolved deploy and share targets refer to valid program and project paths before accessing the filesystem, falling back to a 404 response on invalid input.
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.
Server endpoints previously decoded request identifiers with partial UTF-8 conversion and passed raw parameter values directly into filesystem lookups. Malformed or missing parameters could trigger unhandled pattern-match, UTF-8 decoding, or filesystem exceptions instead of returning a 404 response.
Check that hash and version parameters match the expected ASCII identifier format and that resolved deploy and share targets refer to valid program and project paths before accessing the filesystem, falling back to a 404 response on invalid input.