Latest / Decrypted: The UK Cyber Briefing / GitLab's perfect-ten flaw is being exploited, and the fix hid in the runtime
Transcript
- 0:03Good evening, and welcome to Decrypted.
- 0:05I'm Belinder. It's Friday, the thirtieth of October, twenty twenty-six, and this is the evening edition.
- 0:12GitLab's perfect-ten flaw is being exploited, and the fix hid in the runtime.
- 0:18A maximum-severity flaw in GitLab is now being exploited.
- 0:24GitLab is the platform many UK firms use to hold source code and run their build pipelines.
- 0:29The clearest account of it comes from a victim that chose to publish.
- 0:33Sisa, America's national cyber security agency, put C V E twenty twenty-six, nine seven two two nine, the pu
- 0:40blic reference number for this vulnerability, on its Kev list, the catalogue of flaws known to be exploited in
- 0:46real attacks, on 29 October.
- 0:49GitLab shipped fixes on 12 October.
- 0:51So for most of this month, the gap was a patching problem, not a zero-day, a flaw attackers use before a fix
- 0:58exists. So, what does this flaw actually do?
- 1:03GitLab scores it 10.0 on C V S S, the zero-to-ten severity scale.
- 1:08The fault is in the code that checks regular expressions.
- 1:11Those are the pattern-matching rules found in C I and C D files, the automated pipeline that builds and ships
- 1:18code. GitLab's advisory says an unauthenticated user could execute arbitrary code on the server by sending a
- 1:24crafted pattern. Picture a post room where a clerk reads every address label aloud.
- 1:29This is a label that, once read, makes the clerk hand over the keys to the building.
- 1:35Now, what did Alpine Linux see when it was hit?
- 1:38The project published its own account.
- 1:40On 20 and 21 October, a newly registered account sent crafted configurations to its GitLab server, which was
- 1:47still running 19.3.4. The worker processes crashed eight times.
- 1:53In four of them, the attacker got partway through the exploit before failing.
- 1:57The attacker also downloaded Alpine's GitLab container image.
- 2:01Alpine found no evidence of code execution but could not rule it out, so it rebuilt the server from scratch.
- 2:07It says its packages and the 21 October releases were not tampered with.
- 2:12So why didn't Alpine's update protect it?
- 2:15Because the fix wasn't in GitLab.
- 2:17Here's the trap. The bug sits in Onigmo, the regular expression engine inside Ruby.
- 2:23GitLab's fix is a set of patches to the Ruby it bundles, not a change to its own code.
- 2:29Alpine moved to 19.3.6 on 22 October, but its image used standard Ruby, so the update changed nothing.
- 2:37Anyone running GitLab on their own Ruby needs 3.
- 2:403.13, 3.4.12, 4.0.9 or later.
- 2:46GitLab's fixed releases are 19.
- 2:482.8, 19.3.5 and 19.4.2. Alpine had stepped to 19.
- 2:553.4 on 13 October. One release short.
- 2:59So, what's the Secure by Design lesson here?
- 3:03Two decisions would have changed this.
- 3:05First, a build server that accepts configuration from any newly registered account is exposed by design.
- 3:12Close open self-registration, and keep the server behind a V P N or an allow-list.
- 3:17Second, prove patch status rather than assuming it.
- 3:21A version label told Alpine it was safe when it was not.
- 3:24Ask your platform team or supplier which runtime ships inside the product, and check for the fixed Ruby, not
- 3:31just the release number. The cost is an afternoon and some friction for outside contributors.
- 3:35Skipping it risks what a GitLab server holds.
- 3:39Alpine lists password hashes, two F A secrets, the seeds behind second-check codes, C I and C D variables, ru
- 3:47nner tokens and private repositories.
- 3:50Alpine also warns that a successful exploit leaves no crash and no web log trace, so absence of evidence is
- 3:57weak. As always, this is opinion, not advice.
- 4:01That was Decrypted, with me, Belinder.
- 4:05The written version and every source are linked in the show notes.
- 4:09Thanks for listening. Stay patched, and stay sceptical.