Latest / Decrypted: The UK Cyber Briefing / CrowdStrike's macro clean-up tool turns into a SYSTEM shell
Transcript
- 0:03This is Decrypted. Saturday, the fifth of September.
- 0:06CrowdStrike's macro clean-up tool turns into a system shell.
- 0:11When your endpoint protection software can delete files as system, the real question isn't whether that powe
- 0:18r gets misused. It's how. This week, a researcher published exactly that answer for CrowdStrike's Falcon senso
- 0:26r. It's a working exploit, with no C V E yet.
- 0:30It turns a "clean up malicious macros" feature into a route to a system command prompt on a fully patched Win
- 0:37dows 11 machine.
- 0:41Falcon can automatically strip suspicious macros out of Office documents.
- 0:46To do that anywhere on disk, the process doing the stripping runs with system privileges.
- 0:52That's higher than the logged-in user who triggered it.
- 0:55The researcher publishes under the handle Nightmare Eclipse, and has a track record of releasing proof-of-co
- 1:02ncept exploits for Microsoft products.
- 1:05They found that a specially crafted file could persuade that system-level cleaner to spawn a command prompt.
- 1:12Instead of just doing its cleaning.
- 1:14The result is dubbed FalconFlank.
- 1:17It works against up to date Windows 11 25H2 and Windows Server 2025 machines.
- 1:24Those machines need to be running Falcon with CrowdStrike's own top protection tier switched on.
- 1:30CrowdStrike has not confirmed the flaw with a C V E, and hasn't shipped a fix.
- 1:36It has told customers to disable the "Microsoft Office File Suspicious Macro Removal" Windows policy setting.
- 1:43They should rely on its cloud anti-malware protection instead, while it investigates.
- 1:49So here's the one line UK I T teams should act on this morning.
- 1:53Check whether that policy setting is switched on.
- 1:56Then turn it off until CrowdStrike says otherwise.
- 1:59And finally. The Secure by Design lesson.
- 2:02This isn't really a coding bug story.
- 2:05It's a design pattern story.
- 2:07Any feature built to act on your behalf, with more privilege than you have, is a lever.
- 2:13Security software is full of these levers.
- 2:16It needs elevated access to do its job.
- 2:19Scanning files, quarantining processes, rewriting registry keys.
- 2:24The mistake is trusting the input that triggers the lever as much as the code that pulls it.
- 2:29A macro-removal routine that runs as system has to treat the file it's cleaning as hostile.
- 2:34Not as a passive target.
- 2:41roofs of concept against Kaspersky and Avast.
- 2:44They've also released a crash bug against Nvidia.
- 2:47None of that makes any single vendor careless.
- 2:50But it does mean UK organisations should stop treating "it is security software" as a reason to skip a questi
- 2:57on. It's the question every other vendor gets asked.
- 3:00What happens if the input this tool trusts is actually attacker controlled?
- 3:05And does it need system to answer that question at all?
- 3:08That was Decrypted. The written version and every source are linked in the show notes.
- 3:13Thanks for listening.