dbcve.org
Surveillance StationApplication · Synology

CVE-2024-29232

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 Alert.Enum 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 · high confidence

SQL injection vulnerability in the Alert.Enum webapi component of Synology Surveillance Station allows authenticated remote attackers to inject malicious SQL commands. This enables unauthorized reading of non-sensitive database contents and 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 SQL injection vulnerability in the Alert.Enum webapi endpoint.

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
    Locate the Synology Surveillance Station version in the DSM web interface under Main Menu > Surveillance Station > About, or query the system via SSH using 'cat /etc/syno/surveillance/config' or the API endpoint '/webapi/SurveillanceStation/version.cgi'
    Affected if Version is below 9.2.0-9289 or below 9.2.0-11289 (compare your exact version string to these thresholds)
  2. Verify webapi module is enabled
    Confirm the Surveillance Station webapi interface is enabled and accessible. Check in DSM under Main Menu > Surveillance Station > Settings > General > Web service, or attempt to reach the '/webapi/surveillance station/alert.cgi' endpoint locally
    Affected if The webapi component is exposed and reachable on the network
  3. Confirm authentication method for webapi
    Review the authentication configuration for Surveillance Station webapi in DSM under Main Menu > Surveillance Station > Settings > General > Authentication. Verify whether local accounts, domain accounts, or built-in admin accounts are configured for API access
    Affected if User authentication is configured for Surveillance Station (the vulnerability requires authenticated access to the Alert.Enum endpoint)
  4. Identify exposed webapi endpoints
    Review network exposure of Surveillance Station by checking DSM > Control Panel > Application Portal > Reverse Proxy rules, or by examining firewall rules that may allow external access to port 5000/5001 or the Surveillance Station web ports
    Affected if The Surveillance Station webapi is externally accessible or accessible from untrusted networks

Your environment is affected if Synology Surveillance Station is running a version below 9.2.0-9289 (or below 9.2.0-11289 depending on your release branch) AND the webapi component with the Alert.Enum endpoint is accessible to authenticated users on your network.

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 SQL injection vulnerability in the Alert.Enum webapi endpoint.

Recommended fix High confidence

Surveillance Station 9.2.0-9289 (or 9.2.0-11289 for builds requiring that version)

  1. Log into Synology DSM and open Package Center
  2. Locate Surveillance Station in the package list
  3. Check the current version installed (ensure it is not before 9.2.0-9289 or 9.2.0-11289)
  4. Click 'Update' to install the latest available version, or manually download the update from Synology's download center
  5. After update completes, verify the new version is 9.2.0-9289 or higher (or 9.2.0-11289 or higher, depending on your build)
Caveat Review Synology's release notes for any breaking changes between your current version and the new version before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Surveillance Station Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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