dbcve.org
Surveillance StationApplication · Synology

CVE-2024-29231

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 validation of array index vulnerability in UserPrivilege.Enum webapi component in Synology Surveillance Station before 9.2.0-9289 and 9.2.0-11289 allows remote authenticated users to obtain 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

Improper array index validation in the UserPrivilege.Enum webapi component of Synology Surveillance Station allows authenticated remote users to access non-sensitive information and cause limited denial-of-service through unspecified vectors.

MitigationUpgrade Synology Surveillance Station to version 9.2.0-9289 or 9.2.0-11289 or later to address the improper array index validation vulnerability.

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. Verify Synology Surveillance Station is installed
    Check if the package exists on your Synology DSM system. On the NAS, run: cat /var/packages/SurveillanceStation/info.json 2>/dev/null || echo 'Not installed'
    Affected if The package is not installed or the info.json file does not exist
  2. Determine installed Surveillance Station version
    From the output of the previous command, locate the 'version' or 'version' field in the info.json file. Alternatively, open DSM > Package Center > Surveillance Station and note the displayed version number.
    Affected if The version displayed is lower than 9.2.0-9289 or 9.2.0-11289
  3. Confirm webapi component is accessible
    Verify the Surveillance Station web interface is accessible at https://[your-synology-ip]:5001/webapi/ or through the Surveillance Station client. The vulnerability exists in the UserPrivilege.Enum webapi endpoint.
    Affected if The webapi interface is reachable and the UserPrivilege.Enum endpoint responds to authenticated requests
  4. Compare version against affected ranges
    Check if your installed version is less than 9.2.0-9289 (for builds prior to 9289) or less than 9.2.0-11289 (for builds prior to 11289). Both thresholds indicate vulnerability.
    Affected if Your installed version is earlier than both 9.2.0-9289 and 9.2.0-11289

You are affected if Synology Surveillance Station is installed and the installed version is below 9.2.0-9289 or below 9.2.0-11289.

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 address the improper array index validation vulnerability.

Recommended fix High confidence

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

  1. 1. Open Synology DiskStation Manager (DSM) and log in with administrator privileges
  2. 2. Navigate to Package Center or directly open Surveillance Station
  3. 3. Check the current installed version of Surveillance Station in the application settings
  4. 4. If the installed version is below 9.2.0-9289 (or 9.2.0-11289 depending on your build), initiate an update
  5. 5. In Surveillance Station, go to Settings > General > System > Check for Updates, or use the Synology Package Center to update Surveillance Station
  6. 6. Apply the update and restart Surveillance Station services if prompted
  7. 7. Verify the version has been updated to 9.2.0-9289 or higher (or 9.2.0-11289 or higher for the applicable build)
Caveat Review Synology release notes for any behavioral changes or deprecated features in version 9.2.0; ensure compatibility with existing camera hardware and any third-party integrations before deploying to production

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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