dbcve.org
Surveillance StationApplication · Synology

CVE-2024-29230

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 SnapShot.CountByCategory 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 SnapShot.CountByCategory webapi component of Synology Surveillance Station allows authenticated remote users to inject malicious SQL commands, potentially reading non-sensitive database information and causing limited denial-of-service conditions.

MitigationUpdate Synology Surveillance Station to version 9.2.0-9289 or 9.2.0-11289 (or later) to patch the SQL injection vulnerability in the SnapShot.CountByCategory 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
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 Surveillance Station is running on the Synology NAS by accessing the DSM main menu or checking running packages via SSH with 'sudo synopkg list -i'
    Affected if Surveillance Station is not installed - not affected; if installed, proceed to version check
  2. Identify the installed Surveillance Station version
    In DSM, open Surveillance Station, go to Main Menu > Help > About, or use SSH with 'sudo synopkg getpkgattr SurveillanceStation version'
    Affected if Version is < 9.2.0-9289 OR < 9.2.0-11289 - vulnerable to SQL injection in SnapShot.CountByCategory webapi
  3. Verify webapi access is enabled
    In Surveillance Station, go to Settings > General > Service and confirm Web API is enabled, or check via SSH in /etc/synoSSPI/surveillance station/ configuration files
    Affected if Web API is disabled - the SnapShot.CountByCategory endpoint is not accessible, reducing exposure
  4. Confirm remote authentication is configured
    In Surveillance Station, go to Settings > General > User and verify if remote users or external authentication sources are configured and enabled
    Affected if Only local users exist and remote authentication is disabled - attackers would need valid credentials which may not be readily available, though the vulnerability still exists in the code

User is affected if Synology Surveillance Station is installed AND version is below 9.2.0-9289 (or below 9.2.0-11289 depending on build) AND the SnapShot.CountByCategory webapi is accessible with authentication.

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 patch the SQL injection vulnerability in the SnapShot.CountByCategory webapi component.

Recommended fix High confidence

Surveillance Station 9.2.0-9289 or 9.2.0-11289 (depending on Synology model)

  1. 1. Log in to the Synology NAS with administrator privileges
  2. 2. Open Package Center and locate Surveillance Station
  3. 3. Check the current installed version of Surveillance Station
  4. 4. If the installed version is before 9.2.0-9289 (or before 9.2.0-11289 depending on your model), click 'Update' to install the latest version
  5. 5. Alternatively, manually download the Surveillance Station package from Synology's download center and reinstall to ensure the fixed version is applied
  6. 6. Verify the version after update confirms 9.2.0-9289 or 9.2.0-11289 or later is installed

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
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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