-
Notifications
You must be signed in to change notification settings - Fork 247
⛏️ Write test to detect Rate limit bypass on GraphQL APIs #110
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
Comments
@Ankita28g - could you please assign this to me. |
I've assigned it to you, @rashmibharambe . Happy hacking! Feel free to join our Discord if you need assistance. |
@avneesh-akto - I have raised PR, also tested on tests editor before raising PR. |
@rashmibharambe Thanks for trying out Akto, such as "mutation { query1, query2, query3 .... } " multiple mutations needs to be wrapped inside single mutation query, |
@shivam-rawat-akto I have made the changes to append multiple queries. Also referred hasura graphql playground, query is working with append as you suggested - |
@shivam-rawat-akto Can you please review this |
Hey @rashmibharambe, saw your changes, |
💭 Introduction:
https://0xn3va.gitbook.io/cheat-sheets/web-application/graphql-vulnerabilities#bypass-of-rate-limits
📚 Reading
You can find a detailed documentation of test editor rules here
Find 100+ examples of YAML tests here
✅ Task summary:
Attempt
tab, if the payload changes, then task is done.✌🏻 Hints:
You can build the yaml template by referring this link
🙋🏼♂️ Questions:
If you have questions, need any help, or just want to hang out, make sure to join us on our Discord server.
The text was updated successfully, but these errors were encountered: