feat(JS rules): add express rule against server side request forgery #636
Conversation
This file contains 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
elsapet
force-pushed
the
feat/js-express-ssrf-rule
branch
from
62be990
to
35d0548
Compare
vjerci
approved these changes
Feb 21, 2023
elsapet
force-pushed
the
feat/js-express-ssrf-rule
branch
from
35d0548
to
aa86edb
Compare
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.
Description
Match on a few libraries (axios, node-fetch, puppeteer) that may expose an express application to SSRF attacks if e.g. request data is passed to the library methods
Relates to #606
Checklist