Further DoS fixes needed
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 752
- Forks
- 307
- Avg merge
- 15h 48m
- Merged PRs (30d)
- 7
Description
Hello there.
The recent DoS fixes did not really do much (at least in my case). I have a sample of the java application used for sending attacks. For security reasons, I uploaded it here with a password. A developer/staff member can request me to remove the password should you wish for everyone to be able to grab this tool. Otherwise, you can contact me on Discord (OpenSource#2021) to get the file password.
Launch attack command: java -jar jarname.jar host=127.0.0.1 port=25577 proxiesFile=socks4.txt threads=10000 attackTime=320 exploit=utf16_join (it's important to keep exploit method utf16_join, all else is optional).
I hope there is something more you can do about it. This tool is able to overload any network, no matter the Bot/DDoS protection being used.
Thanks!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is named. Start by reviewing the recent DoS fixes and the reported utf16_join reproduction, then determine whether the behavior is addressed and document a validated mitigation or the remaining limitation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- networking, security
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100