fix(security): add SSRF protection to URL validation #991
+217
−5
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.
Summary
Adds SSRF (Server-Side Request Forgery) protection to URL validation by blocking requests to private/internal IP addresses.
Changes
isPrivateHostname()helper with comprehensive private IP detection:validateRedirectUrl()to block private IPs by defaultallowPrivateIPsoption for backward compatibilityisPrivateUrl()utility function for checking without throwingSecurity Impact
Test plan
npm run build)allowPrivateIPs: trueallows private IPs for backward compatibility🤖 Generated with Claude Code