Memory leak due to server DDOS

Open
#714 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
csharp
Domain
backend, networking

Research direction

Start by reproducing the reported attack condition against the WebSocket server and observe repeated "Cannot determine the frame size or a corrupted frame was received" exceptions. Trace the server's receive and exception-handling path to identify retained memory, then verify that memory remains stable during repeated malformed requests.

Written by the indexing model from the issue text.

Description

Server Sharp have a big memory leak when someone attacked server via DDos, when a lot of exceptions like this received
<>c__DisplayClass70_0.b__0 Cannot determine the frame size or a corrupted frame was received.

Dominant language
C#
Stars
6.1k
Forks
1.7k
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from sta/websocket-sharp

All issues in sta/websocket-sharp

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.