dbcve.org
Surveillance StationApplication · Synology

CVE-2024-29236

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 AudioPattern.Delete 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 AudioPattern.Delete webapi component of Synology Surveillance Station allows remote authenticated users to inject malicious SQL commands through unspecified vectors, enabling limited disclosure of non-sensitive database contents and denial-of-service conditions.

MitigationUpgrade Synology Surveillance Station to version 9.2.0-9289 or 9.2.0-11289 or later to remediate the SQL injection in the AudioPattern.Delete 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. Identify installed Synology Surveillance Station version
    Access the Synology NAS web interface, open Package Center, locate Surveillance Station, and note the installed version number. Alternatively, run: cat /var/packages/SurveillanceStation/info.json on the NAS via SSH.
    Affected if The version is below 9.2.0-9289 or below 9.2.0-11289 (the exact threshold depends on your specific DSM/Surveillance Station build). Compare your version against these two fixed releases.
  2. Verify AudioPattern webapi endpoint exists
    Check if the webapi component is present by inspecting the Surveillance Station webapi directory structure via SSH at /usr/syno/synoman/webapi/ or through the DSM package filesystem.
    Affected if The AudioPattern.Delete endpoint exists and is accessible in the webapi, which is the case in all standard installations of vulnerable versions.
  3. Confirm webapi authentication is enabled
    In DSM, go to Surveillance Station > Settings > General > Security and verify that 'Enable HTTP authentication' or equivalent authentication settings are configured. The vulnerability requires an authenticated user.
    Affected if Authentication is not properly enforced on the webapi, allowing unauthenticated access to the AudioPattern.Delete endpoint (though the CVE states authenticated users are required, misconfigurations may expose it more broadly).

You are affected if your installed Surveillance Station version is below 9.2.0-9289 or 9.2.0-11289 and the AudioPattern webapi endpoint 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

Upgrade Synology Surveillance Station to version 9.2.0-9289 or 9.2.0-11289 or later to remediate the SQL injection in the AudioPattern.Delete endpoint.

Recommended fix High confidence

Surveillance Station 9.2.0-9289 or later (or 9.2.0-11289 or later for applicable builds)

  1. 1. Log in to the Synology NAS administrative interface
  2. 2. Navigate to Package Center or Surveillance Station application management
  3. 3. Check current Surveillance Station version installed
  4. 4. Update Surveillance Station to version 9.2.0-9289 or higher (or 9.2.0-11289 or higher depending on your model/build)
  5. 5. After upgrade, verify the AudioPattern.Delete API endpoint is no longer vulnerable to SQL injection
Caveat Standard upgrade risk - test in staging environment before production deployment

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

Fix this in Surveillance Station Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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