Contact us
← Article questionsDoes this affect us?

CVEHit Business Advisory by IntegrityLab.ai

Does this affect us?

Synology NAS flaw lets attackers with no login take control, now exploited — CVE-2024-10441: Business Triage

Check these three things.

  1. System owner: confirm each Synology NAS runs DSM 7.2.2-72806-1 or another fixed DSM or BeeStation OS build.
    Affected versions and fixes
    • DiskStation Manager (DSM), from Synology's advisory and the CVE record:
      • 7.2.2 before 7.2.2-72806-1.
      • 7.2.1 before 7.2.1-69057-6.
      • 7.2 before 7.2-64570-4.
      • 7.1 before 7.1.1-42962-7.
    • BeeStation OS (BSM) 1.0 and 1.1 before 1.1-65374.
    • Compare the full installed version, including the build and update suffix, with the listed fix for that release. A device on 7.2.2 is fixed only at 7.2.2-72806-1 or later.
    • Synology's DSM advisory lists no mitigation other than the update.
    • Record for each device:
      • Model, installed version and build.
      • Source of that record.
      • Date checked.
  2. Network owner: check whether each NAS sign-in page can be reached from the Internet.
    When the risk applies
    • No login or user action is needed (CVSS 3.1 AV:N/PR:N/UI:N).
    • Rapid7 researcher Ryan Emmons (@the_emmons on X), credited by Synology, showed the flaw is reached through the DSM web sign-in on port 80, 443, 5000, 5001, 6600 or 6601, depending on the device.
    • Rapid7 found every DiskStation it tested vulnerable in the default configuration, and BeeStation vulnerable in its non-default Local Access setting.
    • Check router port forwarding, firewall rules and any service that publishes the NAS sign-in page.
    • AV:N also covers internal networks. A device not on the Internet can still be reached from inside.
  3. Security owner: check each NAS for unknown accounts, scheduled tasks, packages and file changes.
    What the records can show
    • CISA's KEV entry asks for forensic triage on affected devices.
    • Rapid7's demonstration on DSM ran code as root.
    • Records to review:
      • Unexpected scheduled tasks.
      • Unknown user accounts or packages.
      • Unexpected outbound connections.
      • Changed, deleted or encrypted files.
    • Limits:
      • Clean records do not prove no attack happened.
      • Missing records leave the question open.
      • An existing compromise can persist after an update. Complete the compromise check even after patching.

If records show a break-in, start incident response now. Update every affected NAS today. CISA gave US federal agencies until November 21, 2026.

← Back to article questions

How can we help?

Initial enquiries only. Omit passwords, access tokens, security reports or other sensitive information. We’ll arrange secure sharing if needed.

Privacy & data handling ↗. Submitting this form does not authorise an assessment.

Checking enquiry availability…