dbcve.org
Surveillance StationApplication · Synology

CVE-2024-29238

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 Log.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 · moderate confidence

SQL injection vulnerability in the Log.CountByCategory webapi component of Synology Surveillance Station allows authenticated remote attackers to inject malicious SQL commands. The vulnerability exists before versions 9.2.0-9289 and 9.2.0-11289, enabling unauthorized database reads of non-sensitive information and limited denial-of-service conditions.

MitigationApply vendor-supplied patches (version 9.2.0-9289 or 9.2.0-11289 and later) to Synology Surveillance Station. As a defense-in-depth measure, enforce least-privilege database accounts and validate user authentication tokens strictly.

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
    Access Synology DSM and navigate to Package Center to verify Surveillance Station is installed, or query the Synology API for installed packages.
    Affected if Surveillance Station is installed and the version falls below 9.2.0-9289 or 9.2.0-11289
  2. Identify the installed Surveillance Station version
    In DSM Package Center, click on Surveillance Station and view the version number. Alternatively, use the Synology API endpoint to query the package version.
    Affected if The installed version is earlier than 9.2.0-9289 or earlier than 9.2.0-11289
  3. Verify the Log.CountByCategory webapi endpoint is reachable
    Attempt to access the Surveillance Station webapi endpoint at /api/plog/Log.CountByCategory or similar path using the Synology web interface or API documentation.
    Affected if The endpoint responds and accepts parameters without requiring additional authentication beyond basic Surveillance Station login
  4. Confirm authentication configuration for webapi
    In Surveillance Station settings, review the web API authentication settings and verify whether the Log.CountByCategory endpoint can be accessed with any valid user account.
    Affected if Any authenticated user account can access the Log.CountByCategory endpoint without additional privilege restrictions

A user is affected if Synology Surveillance Station is installed with a version lower than 9.2.0-9289 or 9.2.0-11289 and the Log.CountByCategory webapi endpoint is accessible to 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

Apply vendor-supplied patches (version 9.2.0-9289 or 9.2.0-11289 and later) to Synology Surveillance Station. As a defense-in-depth measure, enforce least-privilege database accounts and validate user authentication tokens strictly.

Recommended fix High confidence

Synology Surveillance Station 9.2.0-9289 (or 9.2.0-11289 depending on build branch) or later

  1. 1. Identify the current version of Synology Surveillance Station installed on your system via the DSM package center orSurveillance Station interface.
  2. 2. Determine which build branch your device is on (9.2.0-9289 or 9.2.0-11289 series) to select the appropriate fixed version.
  3. 3. Download the fixed version of Surveillance Station (9.2.0-9289 or later for the 9.2.0-9289 branch; 9.2.0-11289 or later for the 9.2.0-11289 branch) from the Synology Download Center.
  4. 4. Install the update via the DSM Package Center or Surveillance Station's built-in update mechanism.
  5. 5. Verify the installed version reflects the patched release (9.2.0-9289 or 9.2.0-11289 or higher).

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
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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