Skip to content

Fix: SSRF and Stack Trace Exposure in S3 Storage Configuration #156

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
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

pravinkumar-exe
Copy link

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

…23#58)

This commit introduces a minimal placeholder file corresponding to Issue AIxBlock-2023#58, where an authenticated user can delete another user’s account using the /api/users/{user_id} endpoint.



Signed-off-by: pravinkumar-exe <52107447+pravinkumar-exe@users.noreply.github.com>
This commit adds a placeholder file as part of the bug submission process for issue AIxBlock-2023#116.

The file references the exposure of internal infrastructure details to normal users via the endpoint 'https://app.aixblock.io//api/settings/installation-service/'.

This is made from my forked branch to meet the required PR workflow. Looking forward to feedback.


Signed-off-by: pravinkumar-exe <52107447+pravinkumar-exe@users.noreply.github.com>
This commit adds a security fix for a critical SSRF vulnerability in the S3 storage configuration endpoint (PUT /api/storages/s3-server/{id}).

The patch introduces:

Validation to allow only trusted AWS S3 endpoints.

Filtering of internal/private IP addresses via DNS resolution.

Input validation for the bucket name.

Suppressed verbose stack traces to avoid backend logic disclosure.

Signed-off-by: pravinkumar-exe <52107447+pravinkumar-exe@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant