dbcve.org
Surveillance StationApplication · Synology

CVE-2024-29227

MEDIUM · 5.4 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 →
60/100
Remediation priority · Elevated
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
Improper neutralization of special elements used in an SQL command ('SQL Injection') vulnerability in Layout.LayoutSave webapi component in Synology Surveillance Station before 9.2.0-9289 and 9.2.0-11289 allows remote authenticated users to read database containing non-sensitive information and conduct limited denial-of-service attacks 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

SQL Injection vulnerability in the Layout.LayoutSave webapi component of Synology Surveillance Station allows authenticated remote attackers to inject malicious SQL commands. This enables reading non-sensitive database information and conducting limited denial-of-service attacks.

MitigationUpgrade Synology Surveillance Station to version 9.2.0-9289 (or later) for versions before 9.2.0-11289, or version 9.2.0-11289 (or later) for other distributions. Restrict webapi access to trusted authenticated users as an interim measure.

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
Unchanged
Confidentiality
Low
Integrity
None
Availability
Low

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

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 the Surveillance Station service is running on the Synology device. This can be done via DSM package manager or by checking running processes via SSH with 'ps' or similar commands.
    Affected if Surveillance Station is not installed or not running - not affected. If running, continue to next check.
  2. Identify the installed Surveillance Station version
    Access the DSM package manager or check the installed package version through the Synology web interface. Alternatively, check via command line if you have SSH access to the device.
    Affected if The version number returned is less than 9.2.0-9289 OR less than 9.2.0-11289 (depending on your distribution) - potentially affected. If version is 9.2.0-9289 or higher, or 9.2.0-11289 or higher, you are not affected.
  3. Verify the webapi component is accessible
    The vulnerability exists in the Layout.LayoutSave webapi endpoint. Determine if the webapi interface is exposed to network access. Check if remote access to Surveillance Station is enabled via DSM orSurveillance Station settings.
    Affected if Webapi access is enabled and the device is network-accessible - the vulnerable endpoint could be reached. Combined with affected version, this confirms exposure.
  4. Confirm authentication requirements for the webapi
    Review the authentication configuration for Surveillance Station webapi access. The vulnerability requires an authenticated user, so check if user authentication is properly enforced for webapi calls.
    Affected if Webapi is accessible without proper authentication or with weak access controls - the SQL injection could be exploited by any authenticated user. Proper authentication is required for exploitation.

You are affected if Synology Surveillance Station is running a version lower than 9.2.0-9289 (or lower than 9.2.0-11289 for your distribution) AND the webapi component is network-accessible with authenticated user access.

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 (or later) for versions before 9.2.0-11289, or version 9.2.0-11289 (or later) for other distributions. Restrict webapi access to trusted authenticated users as an interim measure.

Recommended fix Moderate confidence

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

  1. 1. Back up your Surveillance Station configuration and any critical data.
  2. 2. Identify your current Surveillance Station version in the application or DSM package center.
  3. 3. Download and install Surveillance Station version 9.2.0-9289 or later, or version 9.2.0-11289 or later, depending on your Synology model and DSM version.
  4. 4. Verify the installation was successful and the version matches the target fixed release.
  5. 5. Test that camera feeds, recording, and core surveillance functionality are operational after the update.

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
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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