CISA added an exploited Synology code-execution flaw, CVE-2024-10441, to its Known Exploited Vulnerabilities catalog on November 18. It affects DiskStation Manager (DSM) and BeeStation OS (BSM), the software behind Synology storage appliances. A remote attacker can run arbitrary code through improper output encoding or escaping in the system plugin daemon. CISA set November 21 as the federal remediation due date.

The vulnerability dates to the 2024 Pwn2Own disclosures, but the KEV addition changes the priority for storage operators now. CISA labels the catalog product DSM while its description names BeeStation OS; Synology’s CVE record lists both products. Inventory both rather than using the catalog’s product column as the whole affected-device list.

Code execution in the plugin daemon

Synology assigns the flaw a CVSS:3.1 score of 9.8 and describes network access, low attack complexity, no privileges and no user interaction. Its DSM advisory says the ZDI-CAN-25403 issue “allows remote attackers to execute arbitrary code.” The advisory groups three distinct flaws: CVE-2024-10441 is the code-execution issue; the other entries concern limited file reading and writing. Prioritize reachable appliances without assuming a particular URL or request pattern.

Code running on the appliance can put the data and services it hosts at risk; how far an intruder could go in a particular installation depends on the appliance’s configuration and access. CISA’s KEV listing establishes exploitation of this CVE, while its ransomware-use field reads “Unknown.” The described attack vector is unspecified, so use version and exposure evidence to drive the first response rather than waiting for a matching alert.

Map DSM and BeeStation builds

For DSM, Synology lists these fixed releases in its advisory: 7.2.2-72806-1, 7.2.1-69057-6 and 7.2-64570-4. The vendor’s CVE record also marks DSM 7.1 as affected below 7.1.1-42962-7; that release is listed in the advisory’s product table. For BeeStation OS, the CVE record lists 1.1-65374 as the fix. Compare the installed version and build on each reachable NAS or BeeStation with the fixed release for its own branch, then install the applicable vendor update.

Synology’s advisory includes a DSM 6.2.4-25556-8 update for its multi-flaw bulletin, while its CVE record marks DSM versions below 7.0 as unknown for this CVE. If your fleet still runs DSM 6.2, use the vendor’s branch-specific update guidance rather than treating the 7.x thresholds as a verdict about that branch. Synology lists the advisory’s mitigation as “None,” so upgrading is the documented way to address the affected builds.

Update exposed storage and verify

Start with the inventory of DSM and BeeStation OS devices, including ones reachable from the internet or other untrusted networks. Record the installed build and access path for each device; restrict unnecessary access to its management interface while arranging the branch-matched update. CISA also calls for evaluation of every asset’s internet exposure and marks forensic triage “Yes” in the KEV entry. If a device has been reachable and remains on an affected build, preserve relevant appliance and network records and follow your incident-response triage process alongside patching.

After the update, read the installed version on each appliance again and compare it with the appropriate fixed build above. Recheck the intended network access from an external or untrusted segment. A completed update is useful only when the running device shows the corrected build and its exposure matches your access policy.