dbcve.org
Surveillance StationApplication · Synology

CVE-2024-29229

HIGH · 7.7 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 →
83/100
Remediation priority · High
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 GetLiveViewPath webapi component in Synology Surveillance Station before 9.2.0-9289 and 9.2.0-11289 allows remote authenticated users to obtain sensitive information 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

This is an authorization bypass vulnerability in the GetLiveViewPath webapi component of Synology Surveillance Station. The missing authorization check allows any remote authenticated user (not just privileged ones) to access sensitive information through this API endpoint, despite not having proper permissions.

MitigationUpgrade Synology Surveillance Station to version 9.2.0-9289, 9.2.0-11289, or later. If immediate upgrade is not possible, restrict access to the webapi interface via network segmentation or VPN.

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
High
Integrity
None
Availability
None

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

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. Identify installed Synology Surveillance Station version
    Access the Surveillance Station web interface, go to Main Menu > About, or check the version via the Synology DSM package center. Record the exact version number including build number (e.g., 9.2.0-XXXX).
    Affected if The installed version is below 9.2.0-9289 or below 9.2.0-11289 (compare your version string to these affected ranges).
  2. Confirm webapi component is accessible
    Verify that the Surveillance Station webapi interface is reachable from your network. This is typically accessible via /webapi/ path on the Synology device's IP or hostname.
    Affected if The webapi interface is exposed and reachable from network segments where untrusted users could connect.
  3. Check user authentication configuration
    Review which user accounts have access to Surveillance Station and confirm whether standard (non-privileged) user accounts exist in the system.
    Affected if There are authenticated users in Surveillance Station who do not have full administrator privileges.
  4. Assess network exposure of the webapi
    Determine if the Surveillance Station webapi is accessible from untrusted networks or if it is restricted to trusted internal networks only.
    Affected if The webapi can be reached by remote or untrusted users beyond the trusted internal network.

You are affected if your Surveillance Station version is below 9.2.0-9289 or 9.2.0-11289 AND the webapi interface is accessible to authenticated users who should not have access to the GetLiveViewPath endpoint.

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

Upgrade Synology Surveillance Station to version 9.2.0-9289, 9.2.0-11289, or later. If immediate upgrade is not possible, restrict access to the webapi interface via network segmentation or VPN.

Recommended fix High confidence

Surveillance Station 9.2.0-9289 or 9.2.0-11289 (or later)

  1. Open DSM and navigate to Main Menu > Package Center
  2. Find Surveillance Station in the package list
  3. Click on Surveillance Station and select 'Update'
  4. Ensure the update installs version 9.2.0-9289 or 9.2.0-11289 or later
  5. After updating, verify the installed version by going to Surveillance Station > Main Menu > Help > About
Caveat Security patch with no significant breaking changes expected; standard update testing recommended

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

Fix this in Surveillance Station Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-29229 — 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-29229 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