Latest / Decrypted: The UK Cyber Briefing / A GitLab flaw was exploited a day after the patch landed
Transcript
- 0:03This is Decrypted. Saturday, the twelfth of September.
- 0:06A GitLab flaw was exploited a day after the patch landed.
- 0:11GitLab shipped a fix for a maximum severity flaw in its self-hosted software on Friday.
- 0:18By Saturday, the attack surface firm watchTowr was already logging internet-wide scans for exactly the reques
- 0:25t pattern that exploits it.
- 0:26They warned that mass exploitation would likely follow within days.
- 0:31For once, "patch available" and "problem solved" weren't even close to the same sentence.
- 0:37And the gap between them fell over a weekend, when fewer admins are watching.
- 0:41An A P I that never checked who was asking.
- 0:45C V E twenty twenty-six, eight five seven zero six is rated C V S S ten point zero.
- 0:53It sits in the repository commits A P I of GitLab Community and Enterprise editions.
- 0:58Send one H T T P P O S T request naming a file path, and thanks to what GitLab describes as improper path con
- 1:07finement and missing authentication enforcement, the server hands back the contents of any file it can read.
- 1:13No login required. Think of a records office where asking for "the file in cabinet three" just gets you the f
- 1:20ile, because nobody thought to check whether you actually work there.
- 1:24Researcher s3ntago reported it through GitLab's bug bounty programme.
- 1:29GitLab patched it on 11 September, in versions 19.
- 1:333.2, 19.2.6 and 19.1.8. Sisa added it to its Known Exploited Vulnerabilities catalogue that same day.
- 1:43Every self-managed instance running a version from 18.
- 1:477 up to, but not including, those fixes is exposed.
- 1:51GitLab dot com itself was already updated.
- 1:54Why a GitLab server is worth more than it looks.
- 1:58A self-hosted GitLab instance is rarely just code storage.
- 2:02It holds C I and C D pipeline definitions, deployment scripts, access tokens and secrets.
- 2:08Those are the exact ingredients an attacker needs to go from reading one file to controlling the software sup
- 2:14ply chain of everything that server builds.
- 2:16For many UK software teams, that server is the single most sensitive machine on the network.
- 2:22Which is exactly why watchTowr is telling defenders to hunt their logs now, for P O S T requests to the commi
- 2:28ts A P I containing a file.
- 2:30path parameter, rather than waiting for a scanner to tell them.
- 2:33The Secure by Design lesson.
- 2:36This is the kind of failure Secure by Design exists to catch before release: an endpoint that takes a file p
- 2:43ath from user input and trusts it, instead of independently checking who is allowed to read what.
- 2:48That's not an exotic edge case.
- 2:50It's the first question a threat model for a "read a file" feature should answer, and somewhere in GitLab's r
- 2:56eview process, it wasn't asked loudly enough.
- 2:58For UK organisations building or buying developer tooling, the practical takeaway is this: treat "does every
- 3:05endpoint enforce its own authorisation, rather than inheriting it from the ones nearby" as a procurement quest
- 3:12ion, not just a code review one.
- 3:13Attackers only need the one endpoint the reviewers missed.
- 3:17That was Decrypted. The written version and every source are linked in the show notes.
- 3:22Thanks for listening.