Hello, welcome to the Thursday, November 4, 2021 edition of the Sansonet Storm Center's

Stormcast. My name is Johannes Ulrich. And I'm recording from Jacksonville, Florida.

If you're using GitLab, then please be aware that you should patch GitLab occasionally.

Rapid 7 took a look at a critical vulnerability in GitLab that was made public back in April.

This was a remote code execution vulnerability and apparently it is actively being exploited. Rapid 7 during its scanning found

that there apparently tens of thousands of unpatched GitLab installations still out there

that have not been updated and are open to attack.

Now, if you're using GitLab, GitLab is publishing security updates at the end of each month.

The last one was published last week, October 28th, so that's when you should take a look and probably update your install.

And according to Rapid Seven's scans,

21% of GitLab installs are fully patched for the issue that was released back in April,

and 50% of installs are not patched. Now there's another 30% where they weren't really sure

if it was vulnerable or not. But with 50% being definitely not patched, this is more than we

typically see for vulnerabilities that old and maybe related with GitLab, not necessarily

sort of being the software that makes the news a lot. So that's why I really want to emphasize

to patch it, double check that you're running it. Maybe you're not even aware that some developers

are so set it up in your environment. And if you need a little bit extra motivation to patch GitLab,

the patch released last week does also address the unicode issue

that made the news picktime.

So maybe that issue about the bidirectional characters making the news

may give you a little bit resource and such

to actually push out a patch.

...