News

CISA Flags a Two-Year-Old Synology Flaw That Ransomware Gangs Are Still Using to Encrypt NAS Backups

CISA added CVE-2024-10441 to its Known Exploited Vulnerabilities catalog on November 18 with a November 21 deadline. The unauthenticated root flaw in Synology DSM was patched in 2024 and is behind the C3RB3R ransomware wave hitting unpatched NAS devices.

A vulnerability Synology fixed two years ago is still taking data off network attached storage in November 2026, and the devices hit are the ones nobody updated. CISA added CVE-2024-10441 to its Known Exploited Vulnerabilities catalog on November 18 with evidence of active exploitation and a federal remediation deadline of November 21.

The bug is an unauthenticated remote code execution flaw in the system plugin daemon, rated 9.8 in Synology's own advisory, published in November 2024. It affects DiskStation Manager before 7.2-64570-4, 7.2.1-69057-6 and 7.2.2-72806-1, and BeeStation Manager before 1.1-65374. Synology lists no mitigation other than upgrading.

Pre-auth, and root

Rapid7's analysis of the flaw, presented at DEF CON and published as a whitepaper on delimiter injection, describes what makes it dangerous: the DSM web login flow passes the account name into a plugin worker that runs as root before any credential is checked. Crafted input injects environment variables into that process, and a loader variable is enough to execute code.

At disclosure, a naive search for the DSM web service path returned roughly 950,000 internet-facing systems that may have been vulnerable. The population of unpatched devices has shrunk since, but it has clearly not gone to zero.

The campaign that forced the issue

Synology said on October 29 that its investigation into the PHP2Shell vulnerabilities led it to threat actors exploiting a flaw patched in December 2024, targeting end-of-life DSM versions to encrypt data and extort ransom. The company did not name the flaw in that statement, and pointed readers to the November 2024 advisory covering CVE-2024-10441 and two related bugs.

Customers had already been reporting the result for weeks: files renamed with a .L0CK3D extension and a note called read-me3.txt demanding payment for a decryptor sold as C3rb3r Decryptor. Coverage of the wave puts the first victim reports more than two weeks before Synology's statement, which is the usual gap between a device failing and the vendor naming the reason.

None of that changes the advice. A NAS holds the backups people assume will survive a ransomware incident on their laptops. When the NAS itself is the target, that assumption is the incident.

CISA's addition is a formal signal rather than new technical detail, and it comes with a forensic requirement: federal agencies must check whether attackers were inside before the patch landed. For everyone else the sequence is the same, and it is short. Upgrade to a fixed DSM release, stop exposing the management interface to the internet, and treat any NAS that ran an old firmware with internet exposure as compromised rather than merely outdated. The broader pattern of internet facing storage being farmed is not new, but encryption is a worse outcome than a hijacked connection.

Some offers on this page may be paid placements or contain affiliate links.

Cyberpresso: daily cyber & AI brief

Free daily newsletter, read in 5 minutes.

Subscribe free