Skip to content
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

Server Side Request Forgery #32

Open
l0s opened this issue Oct 12, 2019 · 0 comments
Open

Server Side Request Forgery #32

l0s opened this issue Oct 12, 2019 · 0 comments

Comments

@l0s
Copy link

l0s commented Oct 12, 2019

I think it would be a good idea to add some slides in the "for engineers" deck that talk about Server Side Request Forgery (SSRF). As more applications are built (or migrated) using public cloud providers like AWS, SSRF attacks on metadata APIs will become more prevalent.

These are some resources on SSRF:

Takeaways for engineers:

  • Follow the principle of least privilege to contain the blast radius.
  • Don't blindly trust URLs from the client. Exercise caution when implementing URL unfurling logic or the like.
  • Ensure any data retrieved from an API has the expected format before sending it to the client or clients. e.g. If an image is expected, ensure that an image was retrieved.
  • For code that is meant to access public URLs, ensure it cannot access internal endpoints.
    ** Don't rely on regular expressions alone to filter out "bad IP addresses".
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

No branches or pull requests

1 participant