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.
π‘οΈ Sentinel: [MEDIUM] Fix path handling in SafeStaticFiles #94
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Uh oh!
There was an error while loading. Please reload this page.
π‘οΈ Sentinel: [MEDIUM] Fix path handling in SafeStaticFiles #94
Changes from all commits
c823327File filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
Check failure
Code scanning / CodeQL
Uncontrolled data used in path expression High
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The exception is caught and swallowed without logging. This contradicts the PR's stated objective to improve debuggability by logging errors before returning HTTP responses. Even when returning a 400 error, the underlying cause (such as a
TypeErrorif input is malformed) should be recorded in the server logs to aid in troubleshooting.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The log message "Failed to create upload directory" is incorrect here. This block handles the file writing process (
openandshutil.copyfileobj), whereas the directory creation was already handled and logged in the preceding block (lines 212-216).There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The exception is swallowed without logging. Consistent with the PR's goal of improving observability, any failure during path construction should be logged before raising an
HTTPException.Check failure
Code scanning / CodeQL
Uncontrolled data used in path expression High
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The exception is swallowed without logging. Path resolution (
.resolve()) can fail due to various system-level issues (e.g., permission errors or filesystem constraints), and logging the specific error is essential for debugging.Uh oh!
There was an error while loading. Please reload this page.