My GitLab Server Has Been Acting Strange / Was Ticketed for Outbound Denial of Service — What Should I Do?

Linode Staff

I received a ticket titled, "ToS Violation - Outbound DoS" on a Linode that I have GitLab installed on. My Linode has also been sending traffic to IP addresses that I'm not familiar with. For reference, I have GitLab version 11.9 installed.

What's going on? What should I do?

1 Reply

Linode Staff

We have recently observed an increase in ToS Violation tickets opened on Linodes with GitLab installed, specifically regarding GitLab versions that were affected by a critical vulnerability. We wanted to make our Community Questions members aware, and provide guidance for next steps.

GitLab Vulnerability (CVE-2021-22205)

On April 14, 2021, GitLab published a Security Release to address CVE-2021-22205, indicating a critical remote code execution (RCE) vulnerability within the service’s web interface. CVE-2021-22205 affects both GitLab Enterprise Edition (EE) and GitLab Community Edition (CE), starting from version 11.9. The vulnerability was patched in the following versions:

  • 13.10.3
  • 13.9.6
  • 13.8.8

For some background, remote code execution consists of exploiting a vulnerability within a service installed on a server to remotely execute code without being properly authenticated, typically under the service’s specific user (in this case, the user being git).

Next Steps

According to AttackerKB, when the attack was simulated, you can determine if you’ve been affected by this vulnerability by examining the gitlab-workhorse log. On Ubuntu, that’s located in /var/log/syslog/gitlab/gitlab-workhorse/. Here is example output that their reverse shell generated:

{"command":["exiftool","-all=","--IPTC:all","--XMP-iptcExt:all","-tagsFromFile","@","-ResolutionUnit","-XResolution","-YResolution","-YCbCrSubSampling","-YCbCrPositioning","-BitsPerSample","-ImageHeight","-ImageWidth","-ImageSize","-Copyright","-CopyrightNotice","-Orientation","-"],"correlation_id":"01FKBH8HB3A5YR8S7PYYB5A8SN","error":"signal: killed","level":"info","msg":"exiftool command failed","stderr":"sh: 1: Trying: not found\nsh: 2: Connected: not found\nsh: 3: Escape: not found\nConnection closed by foreign host.\n","time":"2021-10-31T11:07:18-07:00"}
{"correlation_id":"01FKBH8HB3A5YR8S7PYYB5A8SN","error":"error while removing EXIF","level":"error","method":"POST","msg":"","time":"2021-10-31T11:07:18-07:00","uri":"/e7c6305189bc5bd5"}
{"content_type":"text/html; charset=utf-8","correlation_id":"01FKBH8HB3A5YR8S7PYYB5A8SN","duration_ms":7636442,"host":"","level":"info","method":"POST","msg":"access","proto":"HTTP/1.1","referrer":"","remote_addr":"","remote_ip":"","route":"","status":422,"system":"http","time":"2021-10-31T11:07:18-07:00","ttfb_ms":7636436,"uri":"/e7c6305189bc5bd5","user_agent":"curl/7.47.0","written_bytes":2936}

While the general recommendation would be to simply update your GitLab version to patched versions, it wouldn’t mitigate further exploitation of your Linode, apart from the initial access. The best thing to do is to clone your Linode to transfer your known critical data over to a fresh new Linode. The reason for this is that with an RCE exploit, there could be malicious services and files that were remotely installed on your Linode, allowing for further exploitation. As for your Linode account, please monitor your Outbound Network Transfer to prepare for any overage fees (please see Resources for more information).

As always, please be sure to keep your applications and distributions updated and secured.



Please enter an answer

You can mention users to notify them: @username

You can use Markdown to format your question. For more examples see the Markdown Cheatsheet.

> I’m a blockquote.

I’m a blockquote.

[I'm a link] (

I'm a link

**I am bold** I am bold

*I am italicized* I am italicized

Community Code of Conduct