-
Notifications
You must be signed in to change notification settings - Fork 464
Fix SSRF violations in Django test views #14673
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
Closed
datadog-datadog-prod-us1
wants to merge
3
commits into
main
from
dd/prevent-ssrf-validate-encode-redirect-targets
+18
−6
Closed
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
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
4 changes: 4 additions & 0 deletions
4
releasenotes/notes/tests-appsec-django-ssrf-fix-9f2a1c0c5c.yaml
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,4 @@ | ||
| --- | ||
| other: | ||
| - | | ||
| tests(appsec-django): Sanitize redirect targets and encode path segments in Django test views to address SSRF/open-redirect static analysis findings; no user-facing behavior changes. |
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
Oops, something went wrong.
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.
Check warning
Code scanning / CodeQL
URL redirection from remote source Medium test
Copilot Autofix
AI about 1 month ago
To address the vulnerability, we must ensure that any redirect target constructed from user-controlled HTTP headers is properly sanitized. In this case, we are already applying
quote(value, safe="")to percent-encode all potentially unsafe characters in the header value, preventing breaking out of the path component or tampering with the redirect URL structure.However, there are two improvements that can further reinforce security and robustness:
valueis not empty). Ifvalueis missing or empty, default to redirecting to a safe, well-known local path (e.g.,/).Given the test semantics provided and the instruction to percent-encode the header-derived path component, we should update the function to check if a value is present before performing the redirect. If not, use
/as a safe fallback.File/region/lines to change:
tests/appsec/integrations/django_tests/django_app/views.py, lines 547-560 (unvalidated_redirect_safe_source_cookieandunvalidated_redirect_safe_source_headerfunctions).Required imports/methods:
quoteis already imported.