[LEGIT] Fix - js/request-forgery#103
Open
liorn-test-app[bot] wants to merge 1 commit into
Open
Conversation
|
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.




🔍 The problem
Server-side request forgery
See issue in Legit
🔒 Fix Details
Server-Side Request Forgery (SSRF) Fix
The original code constructed a URL from user-controlled query parameters (
req.query.urlandreq.query.symbol) and passed it directly toneedle.get()without validation. This allowed attackers to make the server send HTTP requests to arbitrary destinations, including internal services, cloud metadata endpoints (e.g., AWS EC2 metadata at169.254.169.254), or localhost resources.Fix applied: Added comprehensive URL validation before the outbound request:
Note: The
allowedHostsarray contains placeholder domains and must be configured with actual legitimate stock data API domains before deployment.