Latest / Decrypted: The UK Cyber Briefing / The GitLab flaw exploited within minutes of disclosure, and the check that came too late
Transcript
- 0:03This is Decrypted. Friday, the twenty-first of August.
- 0:07The GitLab flaw exploited within minutes of disclosure, and the check that came too late.
- 0:13A critical flaw in GitLab was being probed by real attackers within 48 hours of being disclosed on 17 August
- 0:23. The security firm watchTowr says it reproduced the exploit "within minutes" of the advisory going public.
- 0:30Two days later, it caught the first hits on its honeypots.
- 0:35The bug is tracked as C V E twenty twenty-six, one nine four seven eight, with a maximum-severity C V S S of
- 0:449.4. An attacker with no account and no credentials can delete a public GitLab repository.
- 0:52Or worse, they can forge a merge record, so it looks as though a fix landed when it never did.
- 0:59If you're a UK team that self-hosts GitLab precisely to keep control of your code, this is a sharp lesson.
- 1:08A convenience feature can hand that control straight to a stranger.
- 1:12Next. How a compatibility shim became a backdoor.
- 1:18GitLab's GraphQL A P I uses a directive called @gl_introduced to handle rolling upgrades.
- 1:28It lets a client ask for a field that might not exist yet on an older server, without the whole query failing
- 1:35.
- 1:43And it used the attacker-supplied field name as a method to call on the server.
- 1:48Feed it the name of a real, state-changing method instead of a made-up one, and the server just runs it.
- 1:55Public projects can be queried without logging in.
- 1:59And GitLab's authorisation checks ran after the field had already resolved.
- 2:04So the check arrived too late to stop anything.
- 2:07And finally. Check first, act second.
- 2:12GitLab's fix is in versions 19.
- 2:162.4, 19.1.6, 19.0.8 and 18.
- 2:2211.11. It replaces the guesswork with a resolver that always returns null, whatever name it's handed.
- 2:30There's a companion flaw too, C V E twenty twenty-six, one nine six five zero.
- 2:37It let attackers smuggle state-changing requests past GitLab's cross-site protections, by hiding them inside
- 2:44a batch of otherwise harmless queries.
- 2:46Both trace back to the same root cause.
- 2:49Code that acts first and checks permissions second.
- 2:53That ordering is the whole lesson.
- 2:55Any system that resolves, computes or executes before it authorises is one clever field name away from doing
- 3:03something it shouldn't.
- 3:11ot a maybe. watchTowr's advice is to search your web logs for @gl_introduced.
- 3:18Treat any hit as a live incident.
- 3:20That was Decrypted. The written version and every source are linked in the show notes.
- 3:26Thanks for listening.