Jump to content
  • EOS Epic Game DDOS attacks


    deadbolt

    Summary: We banned a player on our server for breaking rules. This player has now ddos'd our server over the last several weeks. We went ahead and upgraded our server with a company called OVH, however, this person is now attacking our server using repeated EOS queries causing the server to crash repeatedly.

     

    Game Version: 20.3

    Platform: PC

    OS/Version: Windows Server 2019 Standard

    CPU Model: AMD Ryzen 7 5800X 8-Core Processor  (cores: 16)

    System Memory: 64GB

    GPU Model and VRAM: N/A Dedicated Server

    Screen Resolution: N/A Dedicated Server

    Video Settings: N/A Dedicated Server

    Game mode: Dedicated Server

     

    Did you wipe old saves? Yes

    Did you start a new game? Yes

    Did you validate your files? Yes

    Are you using any mods? Yes

    EAC on or off? On

     

    Status: NEW

     

    Bug Description: EOS ddos attack taking down server

     

    Detailed steps to reproduce the bug:

     

    1) Ban someone who has something to prove.

    2) Person becomes upset.

    3) Person attacks server with repeated ddos attacks, attacking the server through EOS query system, brags about it openly on other Discords.

     

    Actual result:

     

    Server being taken down by an upset player who was banned for breaking rules. Below are some of the lines I see when the server crashes repeatedly:

     

    022-02-27T00:11:07 4888.148 INF Time: 80.97m FPS: 20.00 Heap: 2265.8MB Max: 2368.2MB Chunks: 0 CGO: 0 Ply: 0 Zom: 0 Ent: 0 (0) Items: 0 CO: 0 RSS: 3189.5MB
    2022-02-27T00:13:41 5043.045 WRN [EOS] [LogHttp - Warning] 000001D363C75AB0: invalid HTTP response code received. URL: https://api.epicgames.dev/datarouter/api/v1/public/data/clients?AppID=85fffb61212b491999cd7fc03eb09bf6&AppVersion=1.14.1-18059966&AppEnvironment=8a44365d5ccb43328b4df2f8ca199e43&UploadType=eteventstream&SessionID=799CC8A5474456D793336983DF559987, HTTP code: 0, content length: 0, actual payload size: 0
    2022-02-27T00:13:41 5043.045 WRN [EOS] [LogHttp - Warning] 000001D363C75AB0: request failed, libcurl error: 7 (Couldn't connect to server)
    2022-02-27T00:13:41 5043.045 WRN [EOS] [LogHttp - Warning] 000001D363C75AB0: libcurl info message cache 0 (Connection 33 seems to be dead!)
    2022-02-27T00:13:41 5043.045 WRN [EOS] [LogHttp - Warning] 000001D363C75AB0: libcurl info message cache 1 (Closing connection 33)
    2022-02-27T00:13:41 5043.046 WRN [EOS] [LogHttp - Warning] 000001D363C75AB0: libcurl info message cache 2 (TLSv1.2 (OUT), TLS alert, Client hello (1):)
    2022-02-27T00:13:41 5043.046 WRN [EOS] [LogHttp - Warning] 000001D363C75AB0: libcurl info message cache 3 (  Trying 35.170.121.150...)
    2022-02-27T00:13:41 5043.046 WRN [EOS] [LogHttp - Warning] 000001D363C75AB0: libcurl info message cache 4 (TCP_NODELAY set)
    2022-02-27T00:13:41 5043.046 WRN [EOS] [LogHttp - Warning] 000001D363C75AB0: libcurl info message cache 5 (connect to 35.170.121.150 port 443 failed: Bad access)
    2022-02-27T00:13:41 5043.046 WRN [EOS] [LogHttp - Warning] 000001D363C75AB0: libcurl info message cache 6 (  Trying 52.3.215.227...)
    2022-02-27T00:13:41 5043.046 WRN [EOS] [LogHttp - Warning] 000001D363C75AB0: libcurl info message cache 7 (TCP_NODELAY set)

     

    See logs here for more info: https://pastebin.com/ZJwDiZrv

     

    Expected result: Better network coding protection for servers by developers. Now that this information is publicly available on the 7daystodie.com forum, every person out there who gets banned for breaking a rule will now have an easy avenue to take down servers because they don't agree they should have been banned.

     

    I have screenshots, IP addresses and Steam ID's of the person doing this and openly admitting to it on public Discord channels.

     

    Any help is appreciated.


    User Feedback

    Recommended Comments

    Just to add to this. He is openly bragging about it on Discord. He says he is doing this by:

    "some ddos's can emulate packets that are used in game and = impossible to block"

    "a2s player query spam could be deadly, not not a lot of people know about it"

     

    He is using "a2s" to spam my server with queries, causing it to crash repeatedly. Eventually, it causes my port to get locked and I am forced to reboot the host machine.

     

    Link to comment
    Share on other sites

    I'd argue thats a bug topic, but why not to have a discussion here...

    You can't rely on devs on keeping up security notched up. You can't rely on them making any safety things whatsoever actually. Probably should expect patching of critical vulnerabilities though, but its not very likely they have security concepts integrated deeply, so unless someone reports it, it would be there...

     

    If you would have been using Linux and wished to just block his IP, I'd have suggested looking into iptables/ipset/eBPF. That doesn't offer quite enough protection to call game server safe, but thats an instrument to block sources of attacks at least.

    If you would like to lower amount of incoming requests - load balancers are probably a way to go (though its likely that Linux OS offers control over it, but Im not fluent with core functionality of it). I know that HAProxy and Nginx can be used as L3/L4 load balancers, but I have little idea on what options of flow control they offer for TCP. Like, both can limit/delay incoming HTTP messages well, but TCP (especially on ClientHello stage of TLS) - I possess no such knowledge. Proper rules will probably solve your problem or minimize risks to acceptable levels. Thats a big research topic though. Add processing (for the sake of filtering) of incoming packets for best results.

     

     

    Also, you can dump his TCP packets by using tcpdump or something alike, while filtering by attacker host ip which you know. I bet that would be of help to devs (a valid test case at least) if they ever decide to work on it.

    Link to comment
    Share on other sites

    Diablo said it well. I will be doing some research on it and see if there's anything the networking folks can do or not, but there are likely by now millions of ways to DOS a server, most of them not exploiting anything vulnerable in games.

    Link to comment
    Share on other sites



    Create an account or sign in to comment

    You need to be a member in order to leave a comment

    Create an account

    Sign up for a new account in our community. It's easy!

    Register a new account

    Sign in

    Already have an account? Sign in here.

    Sign In Now

×
×
  • Create New...