Latest / Decrypted: The UK Cyber Briefing / SharePoint under active attack, and the header that trusted everyone
Transcript
- 0:03This is Decrypted. Thursday, the ninth of July.
- 0:06SharePoint under active attack, and the header that trusted everyone.
- 0:11This week's stories share a theme.
- 0:14What happens when the thing an organisation trusted by default turns out to be exactly what an attacker neede
- 0:21d? An actively exploited flaw in on-premises Microsoft SharePoint has been rushed onto Sisa's Known Exploited
- 0:29Vulnerabilities catalogue.
- 0:31A ransomware crew is using it to steal cryptographic keys, rather than simply extort a payment.
- 0:37A Docker image for the open-source Gitea code-hosting platform shipped a default that turned a single H T T P
- 0:45header into full administrator access.
- 0:48And on the ransomware leak sites, several more UK organisations have appeared over the past few days.
- 0:55Researchers keep tracing that pattern back to a Citrix flaw that clearly still isn't patched everywhere it ne
- 1:02eds to be.
- 1:07On 1 July, Sisa added C V E twenty twenty-six, four five six five nine to its Known Exploited Vulnerabilitie
- 1:17s catalogue. It's a deserialisation flaw in on-premises SharePoint Server, and it lets anyone with even basic
- 1:25Site Member access run code on the server.
- 1:28Deserialisation bugs are the software equivalent of a machine that reassembles flat-pack furniture from an u
- 1:35nmarked box. SharePoint takes a chunk of data sent by the user and rebuilds it into a working object.
- 1:42It just doesn't check closely enough what it actually is.
- 1:46Microsoft patched it in May.
- 1:48But exploitation only surfaced in numbers weeks later, once enough internet-facing servers had gone unpatched
- 1:55for someone to notice and start using it.
- 1:57The group behind it is tracked as Storm twenty-six three, and it has previous form.
- 2:03It used earlier SharePoint bugs in 2025 to deploy Warlock ransomware, and it appears to be running the same p
- 2:11laybook again.
- 2:15It also steals the server's A S P dot N E T machine keys, the cryptographic material SharePoint uses to sign
- 2:24and validate requests. Stolen keys let an attacker forge trusted requests long after the original hole is patc
- 2:31hed. The fix closes the door, but it doesn't invalidate the copied key.
- 2:36N H S England's cyber security operations centre assessed further exploitation as highly likely, and told tru
- 2:45sts to check their patch status.
- 2:46The Secure by Design lesson here is unglamorous but important.
- 2:51Patching closes a vulnerability, not necessarily the access it already handed over.
- 2:57So if you're a UK organisation running on-premises SharePoint that wasn't patched between May and July, treat
- 3:04the server as compromised rather than merely exposed.
- 3:08And rotate the machine keys, rather than assuming the update alone put things right.
- 3:13And also. One H T T P header, admin access.
- 3:18Gitea supports a legitimate pattern called reverse-proxy authentication.
- 3:24A front-end proxy like nginx confirms who a user is, then passes their username to the application in a heade
- 3:31r. That saves a second login.
- 3:33It only works safely if the application also checks that the header really did come from the trusted proxy,
- 3:41and not from the internet at large.
- 3:43Gitea's own source code defaults to trusting only the local machine.
- 3:48Its official Docker image, though, shipped with that trust setting widened to a wildcard.
- 3:53That meant it accepted the identity header from any address at all.
- 3:57Researcher Ali, whose handle is @rz1027, spotted it while auditing how packaged builds quietly diverge from
- 4:06source defaults. The practical result was confirmed once threat actors began probing it about a fortnight afte
- 4:13r disclosure. A single request with the header X-WEBAUTH-U S E R: admin, and no password, logged the sender in
- 4:23as an administrator.
- 4:2726.4, makes reverse-proxy authentication something an administrator must deliberately switch on.
- 4:33It no longer activates itself because of a proxy list nobody reviewed.
- 4:37The Secure by Design lesson is that a secure default only counts if it survives packaging.
- 4:43A vendor can get the source code right and still ship a Docker image, an installer or a cloud template that q
- 4:50uietly overrides it. So if you run self-hosted developer tooling, Gitea or otherwise, check what your containe
- 4:58r images actually shipped with.
- 5:00Don't just trust what the documentation says the defaults are.
- 5:05And finally. The leak sites keep naming UK firms.
- 5:10Over the past week, ransomware groups have claimed several more UK victims on their leak sites.
- 5:17There's the architecture and engineering firm Max Fordham, claimed by Qilin.
- 5:22Employee benefits specialist HIVE360, claimed by Dragonforce.
- 5:28And investment firm Roundshield Partners, claimed by Incransom.
- 5:33These are claims made by the criminals themselves, not confirmed breaches.
- 5:38Read them that way until the organisations involved say otherwise.
- 5:42What's more interesting than any single claim is the pattern.
- 5:47Researchers at Arctic Wolf have been documenting it behind a wave of Anubis ransomware intrusions since the s
- 5:54tart of the year. It starts with valid stolen V P N credentials, and exploitation of last year's CitrixBleed 2
- 6:02flaw in NetScaler devices, C V E twenty twenty-five, five seven seven seven.
- 6:09Then the attackers hide inside legitimate remote monitoring and management tools such as ScreenConnect and Me
- 6:16shAgent. That's instead of deploying custom malware that might trip an alert.
- 6:21None of this needs a zero-day.
- 6:24It needs one unpatched Citrix box, one set of credentials, and I T tooling nobody's kept an inventory of.
- 6:31So for UK organisations, the lesson isn't a new tool to buy.
- 6:37It's basic hygiene. Know which remote monitoring and management tools are authorised to run on your estate, a
- 6:44nd treat anything else as an incident.
- 6:46That was Decrypted. The written version and every source are linked in the show notes.
- 6:52Thanks for listening.