As Synology explains in security advisories published two days after the flaws were demoed at Pwn2Own Ireland 2024 to hijack a Synology BeeStation BST150-4T device, the security flaws enable remote attackers to gain remote code execution as root on vulnerable NAS appliances exposed online.
"The vulnerability was initially discovered, within just a few hours, as a replacement for another Pwn2Own submission. The issue was disclosed to Synology immediately after demonstration, and within 48 hours a patch was made available which resolves the vulnerability," Midnight Blue said.
From a different source:
Synology proactively sponsors and works with security researchers as part of product security initiatives. At this year's Pwn2Own Ireland 2024 event, which took place in late October, we successfully discovered and resolved multiple security vulnerabilities.
While these vulnerabilities are not being exploited, we recommend all Synology device administrators immediately take action to secure their systems by updating due to the scope and severity of specific issues.
Was it that the talk was a last minute change (replacing another scheduled talk) so the responsible disclosure was made in a rush without giving synology more time to provide the patch before the talk was presented?
If so, who decided it was a good idea to present something regarding a vulnerability without the fix being available yet?
There's a give-and-take here, where disclosing the vulnerable should be done soon enough to be responsible to affected users, but not so late that it's seen as pandering to the vendor.
We've already seen how much vendors drag their feet when they are given time to fix a vuln before the disclosure, and almost all the major vendors have tried to pull this move where they keep delaying fix unless it becomes public.
Synology hasn't been very reactive to fixing CVEs unless they're very public. One nasty vulnerability in the old DSM 6 was found at a hackathon by a researcher (I'll edit and post the number later), but the fix wasn't included in the main update stream, you had to go get the patch manually and apply it.
Vendors must have their feet held to the fire on vulns, or they don't bother doing anything.
This was one of the rare times I installed a firmware update without waiting. They even sent an email telling me how urgent it was to get my NAS patched.
To that note, anyone have any idea how to get Hyper Backup to stop telling me that my backups are "partial" because Video Station is no longer found? It's not even on the list of apps, but tells me that it's been disabled as an option to back up because it's not available. Annoying!
If someone knows how to apply security updates to ancient NAS from the brand I'm interested. Sadly mine is out of the loop, I guess I'll have to harden it like hell then
Don't make it available from internet. This will solve the issue.
If it is not possible, once the cve is published and properly described, perhaps there is another way to secure it via an external proxy or even a waf.
If you have unsupported Sw, it is always a pain in the ass to keep them secure so try to figure out always the first point