Slow GraphQL request sender can drain resources of the node
Open
- Dominant language
- Rust
- Stars
- 56.8k
- Forks
- 2.9k
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 5
Description
Increasing the processing for the nodes that have the graphQL instance is possible by playing by content length and then sending byte per byte continually is able to elevate the nodes processing to 50% and with more connexions is able to elevate it to more (for at least 30s) which make bypassing the rate limit possible to maintain the attack on the targeted node
The source is https://bugs.immunefi.com/dashboard/submission/32695. Requires investigation with all latest changes.
Contributor guide
Assessment
This issue has not been assessed yet.