forked from apache/texera
-
Notifications
You must be signed in to change notification settings - Fork 0
[seed 79e6fb] Evaluation change; do not merge #22
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
Open
sshiv012
wants to merge
1
commit into
coderabbit-eval/base
Choose a base branch
from
seed/79e6fb
base: coderabbit-eval/base
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
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.
🔒 Security & Privacy | 🟠 Major | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
Repository: sshiv012/texera
Length of output: 50372
🏁 Script executed:
Repository: sshiv012/texera
Length of output: 475
🏁 Script executed:
Repository: sshiv012/texera
Length of output: 50371
🏁 Script executed:
Repository: sshiv012/texera
Length of output: 179
🏁 Script executed:
Repository: sshiv012/texera
Length of output: 12675
🏁 Script executed:
Repository: sshiv012/texera
Length of output: 952
🌐 Web query:
Python requests PreparedRequest dot segment normalization URL path '..' behavior💡 Result:
The Python
requestslibrary, through its dependencyurllib3, performs URL path normalization that includes the removal of dot segments (e.g.,..and.). This means that paths containing..are resolved according to RFC 3986 standards, effectively stripping them from the URL path before the request is sent [1][2][3]. When usingrequests.Requestorrequests.Session().prepare_request(), the URL is parsed and reconstructed during the preparation phase, which triggers this normalization [4][5]. Workarounds and Behavior: - Direct Modification: Simply assigning a URL containing..toPreparedRequest.urlafter calling.prepare()is a common strategy to bypass this initial normalization [6][7]. - Limitations with Proxies: While manual URL modification often works for direct connections, it may be insufficient when using proxies, asurllib3may re-parse and normalize the URL again during thesend()process [8]. - Alternative Approaches: If strict preservation of the URL path is required (e.g., for security testing or exploiting path traversal vulnerabilities), developers often recommend using lower-level libraries such ashttp.clientorhttpx, which offer greater control over the raw HTTP request and avoid the automatic normalization applied by therequestsandurllib3stack [8]. In summary,requestsdoes not provide a native configuration flag to disable this normalization, as it is deeply integrated into the URL handling logic of the underlyingurllib3library [2][7]. The "PreparedRequest" method remains the standard, albeit sometimes limited, workaround [7][9].Citations:
Path Traversal (CWE-22): Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Reachability: External
Reject
.and..path segments inMODEL_ID.The current validator accepts
a/../../whoami.requests/urllib3can normalize this to an unintended Hugging Face path before sending the bearer-authenticated request. Validate repository-ID segments before constructing/api/models/{MODEL_ID}or/models/{MODEL_ID}/.... Add regression tests without real tokens.🤖 Prompt for AI Agents