BAU-27505 Fix Server-Side Request Forgery (SSRF) / Path Traversal issues #1
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-Side Request Forgery (SSRF) / Path Traversal
The fix involved adding strict validation to the getURL method in the S3 stream wrapper to enhance security. The changes ensure that only valid s3:// URLs, bucket names, and object paths are accepted, effectively preventing path traversal and SSRF attacks. These security checks do not alter existing functionality for valid inputs.
Following our changes, the vulnerabilities flagged by automated scanners (Path Traversal and SSRF) are considered false positives, as all user input is now validated before being used in sensitive operations. No exploitation is possible with the current implementation.