dbcve.org
Surveillance StationApplication · Synology

CVE-2024-29241

CRITICAL · 9.9 CVSS v3.1 Published 2024-03-28
Fix available
A fix is available. Upgrade to 9.2.0-9289 / 9.2.0-11289 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Missing authorization vulnerability in System webapi component in Synology Surveillance Station before 9.2.0-9289 and 9.2.0-11289 allows remote authenticated users to obtain non-sensitive information, write sensitive configurations in DSM, and reboot or shutdown NAS via unspecified vectors.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A missing authorization vulnerability in Synology Surveillance Station's System webapi component allows any authenticated user to access the API without proper permission checks. This enables unauthorized retrieval of information, modification of sensitive DSM system configurations, and remote power control (reboot/shutdown) of the NAS device.

MitigationUpdate Synology Surveillance Station to version 9.2.0-9289 or 9.2.0-11289 or later to remediate the missing authorization checks in the webapi component.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Surveillance StationApplication
Affected:< 9.2.0-9289< 9.2.0-11289

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Synology Surveillance Station is installed
    Check if Synology Surveillance Station is installed on the NAS device. This can be done via DSM Package Center or by checking for the Surveillance Station web portal (typically accessible at port 5001 or 5000).
    Affected if Surveillance Station is installed and accessible on the device.
  2. Identify the installed Surveillance Station version
    Log into the DSM interface, open Package Center, find Synology Surveillance Station, and note the version number displayed. Alternatively, access Surveillance Station directly and check the version in its 'About' or 'System Info' section.
    Affected if The installed version is below 9.2.0-9289 or below 9.2.0-11289.
  3. Verify the System webapi component is accessible
    Attempt to access the Surveillance Station webapi endpoint. The System webapi typically handles system-level operations. If unauthenticated or low-privilege access to the webapi URL returns a response (rather than an authorization error), the component may be exposed.
    Affected if The System webapi is reachable and responds to requests without enforcing proper permission checks.
  4. Test for unauthorized API access
    Using an authenticated user account with limited privileges (non-admin), attempt to call system-level API functions through Surveillance Station's webapi interface. Observe if operations such as retrieving system configuration or power control commands (reboot/shutdown) are executed without authorization errors.
    Affected if A low-privilege authenticated user can successfully access system configuration data or execute power control operations through the webapi without receiving permission-denied errors.

A user is affected if Synology Surveillance Station is installed with a version prior to 9.2.0-9289 or 9.2.0-11289 and the System webapi permits unauthenticated or low-privilege users to access sensitive system configurations or control power operations.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 9.2.0-9289 / 9.2.0-11289 or later
Fixed in 9.2.0-92899.2.0-11289
Interim mitigation

Update Synology Surveillance Station to version 9.2.0-9289 or 9.2.0-11289 or later to remediate the missing authorization checks in the webapi component.

Recommended fix High confidence

Surveillance Station 9.2.0-9289 or 9.2.0-11289 (depending on your version branch)

  1. Log into Synology DSM (DiskStation Manager) as an administrator
  2. Open Package Center
  3. Locate Surveillance Station in the list of installed packages
  4. Click on Surveillance Station and select 'Update' to install the latest available version
  5. Verify the updated version is 9.2.0-9289 or higher (for the 9.2.0.x branch) or 9.2.0-11289 or higher (for the 9.2.0-11289 branch)

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Surveillance Station Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-29241 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-29241 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data