Fix: SSRF and Stack Trace Exposure in S3 Storage Configuration #156
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.
This fix addresses a critical SSRF vulnerability in the PUT /api/storages/s3-server/{id} endpoint by:
Blocking internal/private IPs via DNS resolution.
Allowing only valid AWS S3 endpoints.
Validating the bucket name format.
Preventing verbose stack trace leaks on connection failures.
Issue: #155