Latest / Decrypted: The UK Cyber Briefing / Node2Shell reaches .NET: Microsoft's emergency Brotli patches
Transcript
- 0:03This is Decrypted. Monday, the twenty-sixth of October, twenty twenty-six.
- 0:07This is the evening edition.
- 0:10Node2Shell reaches.net: Microsoft's emergency Brotli patches.
- 0:16Node2Shell, the Node.js flaw we covered on Sunday, now reaches beyond one runtime.
- 0:23Today Microsoft released emergency out-of-band updates for the same identifier, C V E twenty twenty-six, one
- 0:32one one four nine seven, the public reference number for this vulnerability, in.
- 0:37net, the framework behind many UK line-of-business applications.
- 0:42Imperva's Red Team found the flaw, and proof-of-concept code is public.
- 0:47BleepingComputer reports no malicious exploitation in the wild yet, which is precisely when to act.
- 0:54So, what actually broke? Brotli is a compression format that shrinks web traffic.
- 1:02Think of a vacuum-packed parcel.
- 1:04The sender seals it flat, and the receiver's software unpacks it into a box sized in advance.
- 1:11The decoder has to trust the packing instructions.
- 1:14In Imperva's analysis of the Node.
- 1:17js copy, the decoder met an instruction the stream's structure made impossible.
- 1:22It treated that as a request for more data, and carried on in a broken internal state.
- 1:29It then wrote past the end of its box, which Imperva says can permit remote code execution.
- 1:35Microsoft calls its flaw a buffer overflow in.
- 1:39net's Brotli decompression, which an unauthenticated attacker may use to read or corrupt memory.
- 1:45Now, are you exposed? Fewer than you might fear, but more than you'll guess.
- 1:51Microsoft says request and automatic response decompression are off by default, and.
- 1:57net Framework is not affected.
- 1:59You're at risk if an application uses A S P dot net Core request decompression, HttpClient automatic response
- 2:08decompression or the Brotli compression A P Is, the ways programs call it.
- 2:13Fixed releases are 8.0.33, 9.
- 2:180.22 and 10.0.14, with.net 11 users moving to Release Candidate 3.
- 2:25For Node.js, Imperva lists 22.
- 2:3023.4, 24.22.1 and 26.12.1.
- 2:35It notes that Express and body-parser can route untrusted request bodies into the decoder, as can the built-i
- 2:43n fetch when it reads a compressed response.
- 2:46Imperva also says its exploit did not work on every attempt.
- 2:50So, what should defenders check?
- 2:53Patching the server doesn't patch the application.
- 2:56Microsoft says self-contained apps must be rebuilt and republished, because a newer host runtime doesn't upda
- 3:03te the one bundled inside them.
- 3:04Containers need rebuilding from updated images.
- 3:08Imperva warns that package inventories can miss bundled runtimes, so check what's actually deployed.
- 3:14If you can't patch today, block incoming Brotli-compressed requests at a proxy or firewall, or disable Brotl
- 3:22i decoding until you can. And what's the Secure by Design lesson here?
- 3:26The default saved people. Decompression ships switched off, so many UK estates are exposed only if someone o
- 3:34nce enabled it for speed. Code that decodes untrusted input is among the riskiest in any application.
- 3:42It should stay off until a person chooses otherwise, and ideally be written in a memory-safe language.
- 3:47The cost of the fix is an inventory, not a patch.
- 3:51If you can't say which runtimes sit inside which apps and containers, a director's question like "are we expo
- 3:58sed?" takes days to answer, and attackers need less time than that.
- 4:02Ask your suppliers for that list this week, in writing.
- 4:06As always, this is opinion, not advice.
- 4:09That was Decrypted. The written version and every source are linked in the show notes.
- 4:15Thanks for listening.