dbcve.org
Surveillance StationApplication · Synology

CVE-2024-29237

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 ActionRule.Delete webapi component in Synology Surveillance Station before 9.2.0-11289 and 9.2.0-9289 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 · moderate confidence

SQL injection vulnerability in the ActionRule.Delete 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-11289 or 9.2.0-9289 or later to patch the vulnerability; until then, restrict access to the webapi to only trusted authenticated users.

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
    Log into Synology DSM and open Package Center to verify Surveillance Station is installed, or run 'pkginfo' via SSH to list installed packages
    Affected if Surveillance Station is not installed (not affected)
  2. Check installed Surveillance Station version
    In DSM Package Center, click Surveillance Station and view the version number; or via SSH run 'pkginfo -i synology-surveillance-station' to get the exact version
    Affected if Version is below 9.2.0-9289 OR below 9.2.0-11289 (vulnerable)
  3. Verify webapi component accessibility
    Check if the Surveillance Station webapi is exposed to untrusted networks by reviewing router port forwarding rules or firewall settings for ports 554 (default) or custom configured ports
    Affected if Webapi port is accessible from untrusted/external networks (potentially exposed)
  4. Confirm webapi authentication is required
    In Surveillance Station Web GUI, go to Settings > General > Security and verify that authentication is enabled for webapi access; or check that unauthenticated access is not permitted
    Affected if Webapi allows unauthenticated access or uses weak authentication (exploitable condition present)

User is affected if Synology Surveillance Station is installed with a version below 9.2.0-9289 (or 9.2.0-11289 depending on build) AND the webapi is accessible to untrusted authenticated users.

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-11289 or 9.2.0-9289 or later to patch the vulnerability; until then, restrict access to the webapi to only trusted authenticated users.

Recommended fix High confidence

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

  1. 1. Check the current version of Synology Surveillance Station installed on your system
  2. 2. Ensure you have a backup of your Surveillance Station configuration and recordings
  3. 3. Access the Synology DSM web interface and open Package Center
  4. 4. Find Surveillance Station in the installed packages list
  5. 5. Click on Surveillance Station and select 'Update' to install the latest available version
  6. 6. Alternatively, manually download the updated Surveillance Station package from Synology's download center
  7. 7. After updating, verify that the installed version is either 9.2.0-9289 or 9.2.0-11289 or higher
  8. 8. Test that the Surveillance Station web interface and all cameras are functioning properly
Caveat Standard upgrade risk applies - always backup configuration before updating; minor UI changes may exist in new version

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
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,440
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,304.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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