CVE-2024-29235
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 · uneditedImproper neutralization of special elements used in an SQL command ('SQL Injection') vulnerability in IOModule.EnumLog 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 confidenceSQL injection vulnerability in Synology Surveillance Station's IOModule.EnumLog webapi component allows remote authenticated users to inject malicious SQL commands. The flaw enables reading non-sensitive database information and conducting limited denial-of-service attacks against the system.
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< 9.2.0-9289< 9.2.0-11289CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Synology Surveillance Station is installedCheck if the Synology Surveillance Station package is installed on the Synology NAS. This can be done via the Synology Package Center interface, or by accessing the system via SSH and checking for the surveillance station package directory (typically under /var/packages/SurveillanceStation).Affected if The package is not installed or no surveillance station installation is found.
-
Identify installed Surveillance Station versionAccess the Surveillance Station web interface, go to Menu > System > General > About to view the exact version number. Alternatively, check via SSH by running: cat /var/packages/SurveillanceStation/etc/ssapp/version or checking the package info via Synology CLI.Affected if The installed version is lower than 9.2.0-9289 or lower than 9.2.0-11289.
-
Verify the IOModule webapi endpoint is accessibleTest access to the Surveillance Station webapi by attempting to reach an endpoint such as https://[nas-ip]:[port]/webapi/entry.cgi?api=SYNO.SurveillanceStation.IOModule.EnumLog&method=List. The exact path may vary based on DSM configuration.Affected if The webapi endpoint responds and accepts requests (even if authentication fails, the endpoint exists).
-
Confirm remote authentication is enabledCheck if remote users can authenticate to Surveillance Station by verifying that local user accounts or domain users have Surveillance Station access permissions. Go to Surveillance Station > Settings > User and Permission to review permitted users.Affected if Remote authentication is permitted for non-admin or non-local-only users who can access Surveillance Station.
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 depending on your specific build) AND the IOModule webapi is accessible with remote authentication enabled.
Generated from the published advisory. Verify against your own configuration.
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 · scoped9.2.0-92899.2.0-11289
Update Synology Surveillance Station to version 9.2.0-11289 or 9.2.0-9289 or later to remediate the SQL injection vulnerability.
Upgrade to Surveillance Station 9.2.0-9289 or later, or 9.2.0-11289 or later
- 1. Log into the Synology NAS via DSM (DiskStation Manager).
- 2. Open Package Center to view installed packages.
- 3. Locate Surveillance Station in the list of installed packages.
- 4. Check the current installed version of Surveillance Station under the package details.
- 5. If the installed version is below 9.2.0-9289 or below 9.2.0-11289, click 'Update' to install the latest available version.
- 6. Alternatively, manually download the updated Surveillance Station package from the Synology Download Center matching your NAS model.
- 7. Install the update and restart Surveillance Station services if prompted.
- 8. Verify the updated version reflects 9.2.0-9289 or later, or 9.2.0-11289 or later.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-29235 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-29235 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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