šŸ”Simple Yet Crucial step to avoid security incidentsšŸ’”

Aidas Petryla - Apr 11 - - Dev Community

Recently Iā€™ve experienced a GitLab security incident.
Had a pretty new GitLab version (~2 months old), but there were a few security patches released. Apparently, I was missing one of them.

I noticed GitLab throwing 500 errors randomly and later 502 consistently. Looking at the server Iā€™ve noticed some processes run by ā€œgitā€ user, which shouldn't be running, consuming all CPU. Processes were restarting after killing them. Updating GitLab to the newest version resolved the issue.

Keeping software up-to-date can sometimes be a cumbersome process. But security incidents in sensitive systems can be very costly. Luckily, this time it wasnā€™t the case. I hope this reminder will save others from uncomfortable situations.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .