Latest / Decrypted: The UK Cyber Briefing / The SharePoint token flaw a researcher published today, and the servers still facing the internet
Transcript
- 0:03This is Decrypted. Wednesday, the twelfth of August.
- 0:06The SharePoint token flaw a researcher published today, and the servers still facing the internet.
- 0:13A researcher has published the full working detail of a SharePoint authentication bypass today.
- 0:20That's hours after Microsoft finished patching it, in two instalments, across July and this week's Patch Tues
- 0:27day. Attackers were already firing the proof of concept at honeypots before the day was out.
- 0:33Here's why that matters to you.
- 0:35On-premises SharePoint sits behind the login page of a lot of UK government and enterprise intranets.
- 0:42So this one is worth checking this evening, not at the next patch window.
- 0:46Next. A wristband nobody checked properly.
- 0:51The flaw is C V E twenty twenty-six, five five zero four zero.
- 0:57It's in SharePoint's J W T token validation pipeline, and it's rated 9.
- 1:031 out of 10. Rapid7's Stephen Fewer found it.
- 1:07He demonstrated it at Pwn2Own Berlin, and reported it to Microsoft on 18 May.
- 1:12Microsoft agreed to fix it across two update cycles.
- 1:17July closed the authentication bypass.
- 1:20August closed a second, chained flaw, one that turns a forged login into full remote code execution on the se
- 1:27rver.
- 1:31Think of a J W T as a wristband at a gated event.
- 1:35The door is supposed to check that the box office issued the wristband, using a signature only the box office
- 1:41can produce. But what the flawed validation pipeline actually checked was closer to the name written on the w
- 1:47ristband.
- 1:55l name. Both are easy to gather.
- 1:58They could write themselves a wristband marked "site administrator", and the door let them through.
- 2:04Rapid7 published its technical write-up and proof of concept on Tuesday.
- 2:09Within hours, the threat intelligence firm Defused reported the exploit running against its SharePoint honeyp
- 2:15ots.
- 2:20The interesting failure here isn't that a bug existed.
- 2:24It's what the bug reveals about the assumption underneath it.
- 2:27A token is only as trustworthy as the verification chain behind it.
- 2:32And that chain needs to check cryptographic proof of issuance, not identifiers an attacker can supply.
- 2:39So here's a genuine question for any product built on tokens, homegrown or vendor.
- 2:45Does the validator prove the token was issued to this identity?
- 2:49Or does it merely check that the token looks like one that could have been?
- 2:53There's a second, quieter lesson for UK organisations.
- 2:57On-premises SharePoint was designed for a trusted internal network.
- 3:02A lot of installations are now reachable from the internet, because hybrid working made that convenient.
- 3:07Sisa has been warning since the spring that this family of SharePoint flaws poses a standing risk to any inst
- 3:14ance facing outward.
- 3:18Apply both the July and August updates.
- 3:21Rotate your I I S machine keys.
- 3:24Review your logs for signs of deserialisation abuse.
- 3:27And, separately from patching, ask whether SharePoint Central Administration needs to be reachable from outs
- 3:34ide the network at all. A patched system that shouldn't have been exposed in the first place is still carrying
- 3:40risk the patch doesn't remove.
- 3:42That was Decrypted. The written version and every source are linked in the show notes.
- 3:47Thanks for listening.