dbcve.org
Surveillance StationApplication · Synology

CVE-2024-29228

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 GetStmUrlPath 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

A missing authorization vulnerability in the GetStmUrlPath webapi component of Synology Surveillance Station allows authenticated users to access sensitive information they are not authorized to view, without proper authorization checks on specific API calls.

MitigationApply the vendor patch by updating Synology Surveillance Station to version 9.2.0-9289 (or later 9.x versions) or 9.2.0-11289 to remediate the missing authorization check in the GetStmUrlPath 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
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. Check installed Synology Surveillance Station version
    Access the Surveillance Station web interface, go to Help > About, or check the version via the package center in Synology DSM. The version number is displayed as something like 9.x.x-xxxx.
    Affected if The version is lower than 9.2.0-9289 or lower than 9.2.0-11289 (for 9.2.0 builds)
  2. Verify the GetStmUrlPath API endpoint is accessible
    Make an authenticated API request to the GetStmUrlPath endpoint via the Surveillance Station webapi. This is typically accessed at /webapi/SurveillanceStation/api and includes the GetStmUrlPath method.
    Affected if The API endpoint responds to authenticated requests without returning an authorization error
  3. Confirm the installation is vulnerable based on version
    Compare your installed version number against the affected ranges: any version below 9.2.0-9289 (for builds before 9.2.0) or below 9.2.0-11289 (for the 9.2.0 branch) is within the vulnerable range.
    Affected if The installed version falls below both 9.2.0-9289 and 9.2.0-11289 thresholds

You are affected if your Synology Surveillance Station version is below 9.2.0-9289 or below 9.2.0-11289, and the GetStmUrlPath API is accessible to authenticated users without proper authorization enforcement.

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

Apply the vendor patch by updating Synology Surveillance Station to version 9.2.0-9289 (or later 9.x versions) or 9.2.0-11289 to remediate the missing authorization check in the GetStmUrlPath component.

Recommended fix High confidence

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

  1. 1. Check current Synology Surveillance Station version in DSM > Package Center > Surveillance Station
  2. 2. Determine which version branch you are on (9.2.0-9289 or 9.2.0-11289) based on your current version
  3. 3. Go to DSM > Package Center > Surveillance Station > Update
  4. 4. Update to version 9.2.0-9289 or higher, or 9.2.0-11289 or higher (whichever applies to your current version branch)
  5. 5. Verify the update was successful by checking the version in Package Center

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-29228 — 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-29228 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