CRITICAL: SSRF to Cloud Metadata Exfiltration & Internal Network Takeover (CVSS 9.1)#401
Open
emmanuelkings949-pixel wants to merge 1 commit intoAIxBlock-2023:mainfrom
Open
CRITICAL: SSRF to Cloud Metadata Exfiltration & Internal Network Takeover (CVSS 9.1)#401emmanuelkings949-pixel wants to merge 1 commit intoAIxBlock-2023:mainfrom
emmanuelkings949-pixel wants to merge 1 commit intoAIxBlock-2023:mainfrom
Conversation
Signed-off-by: emmanuelkings949-pixel <emmanuelkings949@gmail.com>
Author
|
Hi @AIxBlock Team, I'm checking in on this Critical SSRF (9.1) fix. It has been over a week since submission, and I wanted to ensure the validation is proceeding okay or if you need any further info from me! Thanks. |
Author
|
Official report logged in Discussions here:#409 |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
💥 High-Stakes Impact (CVSS 9.1)
This is a Full-Read SSRF. An attacker can bypass the intended AI proxy to:
Exfiltrate Cloud Credentials: Accessing http://169.254.169.254/latest/meta-data/iam/security-credentials/ to steal AWS/GCP service tokens.
Internal Network Takeover: Scan and interact with internal databases, Redis instances, or K8s management APIs that are not exposed to the internet.
Bypass Firewalls: Use the server as a "pivot point" to launch attacks deeper into the AIxBlock infrastructure.
Successful exploitation allows for the complete compromise of the AIxBlock cloud environment, equivalent in impact to remote code execution (RCE) at the infrastructure level.
The following screenshots confirm the data flow from the untrusted user parameter to the dangerous internal request:
The Entry Point: The request.params['*'] parameter is taken directly from the URL without validation.
The Execution Point: This unvalidated data is used to construct the url variable and passed into the fetch() function.
