dbcve.org
Surveillance StationApplication · Synology

CVE-2024-29234

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 Group.Save 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 Group.Save webapi component of Synology Surveillance Station allows remote authenticated users to inject malicious SQL commands through unspecified vectors, enabling limited database information disclosure and denial-of-service attacks.

MitigationUpgrade to Synology Surveillance Station version 9.2.0-11289 or 9.2.0-9289 or later. If immediate patching is not possible, restrict network access to the webapi to authenticated users only and monitor for suspicious SQL patterns in logs.

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. Check installed Surveillance Station version
    Open Synology DSM, go to Package Center, find Surveillance Station, and note the version number displayed. Alternatively, log into Surveillance Station web interface and go to About > Version.
    Affected if Version is lower than 9.2.0-9289 or 9.2.0-11289 (any version below these thresholds is affected)
  2. Identify webapi network exposure
    Determine if the Synology device's webapi endpoints are accessible from the network. This is typically accessed via https://[synology-ip]:[port]/webapi/ or through the Surveillance Station web interface URL.
    Affected if The webapi component is reachable over the network (this is the attack surface for the vulnerability)
  3. Verify webapi authentication configuration
    In Surveillance Station, go to Settings > General > Security and review authentication settings for API access. Check if anonymous or weak authentication is allowed for webapi endpoints.
    Affected if Webapi allows authentication from remote users without proper access controls (this enables the authenticated attacker to exploit the flaw)
  4. Review logs for suspicious SQL patterns
    In Surveillance Station, go to Log > System Logs and search for unusual SQL syntax, unexpected WHERE clauses, or UNION SELECT statements in API request logs. Also check DSM logs for similar patterns in webapi access logs.
    Affected if Logs contain SQL injection signatures such as 'UNION SELECT', single quotes in unexpected places, OR 1=1 patterns, or database error messages related to webapi calls

A user is affected if their Surveillance Station version is below 9.2.0-9289 or 9.2.0-11289 and the webapi component is accessible to remote 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

Upgrade to Synology Surveillance Station version 9.2.0-11289 or 9.2.0-9289 or later. If immediate patching is not possible, restrict network access to the webapi to authenticated users only and monitor for suspicious SQL patterns in logs.

Recommended fix High confidence

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

  1. Log into Synology Surveillance Station as an administrator
  2. Navigate to the Surveillance Station control panel or package center
  3. Check the current installed version of Surveillance Station
  4. Update Surveillance Station to version 9.2.0-9289 or higher, or version 9.2.0-11289 or higher depending on your release track
  5. Verify the update was successful and the version reflects the patched release
  6. Confirm the Group.Save webapi component is no longer vulnerable

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
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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