Latest / Decrypted: The UK Cyber Briefing / Nextcloud's built-in Collabora server was exploited for a month before the advisory
Transcript
- 0:03This is Decrypted. Saturday, the twenty-fourth of October, twenty twenty-six.
- 0:09This is the morning edition.
- 0:13Nextcloud's built-in Collabora server was exploited for a month before the advisory.
- 0:21A fix for a critical Nextcloud flaw shipped on 11 September.
- 0:26The advisory didn't arrive until 14 October, and in between, attackers were already using it.
- 0:34On 23 October Sisa, America's national cyber security agency, added C V E twenty twenty-six, one one zero fou
- 0:45r four seven, the public reference number for the flaw, to its Kev list, the catalogue of flaws known to be ex
- 0:53ploited in real attacks. The bug sits in the built-in Collabora Online server that many self-hosted Nextcloud
- 1:00installs use for editing documents.
- 1:02If your organisation runs Nextcloud to keep files under its own roof, check nobody else has been let in.
- 1:10So, what does this flaw actually do?
- 1:15The vendor advisory rates it critical, 9.
- 1:192 on the C V S S v4 scale, the zero-to-ten severity score.
- 1:25An unauthenticated request to the app's proxy can make the server run an operating system command as the web
- 1:33server user. Versions before 26.
- 1:374.303 are affected. Standalone Collabora Online, Docker and R P M and deb installs and Nextcloud All-in-One ar
- 1:48e reported unaffected. Think of a building whose side door unlocks only when the night porter is off shift.
- 1:57The attack works only while the bundled server isn't running, which happens after a restart, an upgrade or a
- 2:03crash. Nobody needs to log in.
- 2:05So, what did the attackers do with it?
- 2:10BleepingComputer reports administrator logs showing attacks from 10 September.
- 2:15The intruders planted P H P webshells, small scripts that give remote control through an ordinary web page, a
- 2:23nd searched for password databases, password manager files and cryptocurrency wallets.
- 2:29Reports of ransomware are unconfirmed.
- 2:31What should you look for? Files named shx*.
- 2:36php inside apps/richdocumentscode/.
- 2:41Requests to proxy.php?status containing "$(" or "${I F S}".
- 2:49And failed sudo attempts by the web server account.
- 2:52Check logs back to at least 10 September.
- 2:55Disabling the app doesn't close the hole, so update it or remove it.
- 3:00And patching doesn't remove a webshell already planted.
- 3:03If you find one, treat everything the web server account could read as exposed, and consider a rebuild.
- 3:10Why did the paperwork lag behind the fix?
- 3:15Nextcloud said Collabora reported the flaw in mid-September, that an update went out through the app store,
- 3:21and that it had not seen widespread exploitation.
- 3:24Collabora blamed C V E processing backlogs at GitHub.
- 3:29BleepingComputer cites a Second Security study putting the median gap between a public fix and a C V E at 39
- 3:37days in August, up from 5.
- 3:401 in January. My inference: a scanner keyed to C V E numbers had nothing to flag for a month.
- 3:46So, what's the Secure by Design lesson here?
- 3:51Request data should never get near a shell command, and a component that can be left stopped should fail clo
- 3:58sed, not open. For UK organisations, the remedies are unglamorous.
- 4:03Inventory every self-hosted service, including add-ons bundled inside them.
- 4:09Turn on automatic updates for internet-facing apps.
- 4:12Follow vendor release notes, not just C V E feeds.
- 4:16And run document servers with the least access they can function on.
- 4:20I found no UK-specific victim figures.
- 4:23Self-hosting buys control over your data, but control includes noticing when a vendor fixes something quietly
- 4:30. As always, this is opinion, not advice.
- 4:35That was Decrypted. The written version and every source are linked in the show notes.
- 4:41Thanks for listening.