dbcve.org
Drive ServerApplication · Synology

CVE-2024-50631

HIGH · 7.5 CVSS v3.1 Published 2025-03-19
Fix available
A fix is available. Upgrade to 3.0.4-12699 / 3.2.1-23280 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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 the system syncing daemon in Synology Drive Server before 3.0.4-12699, 3.2.1-23280, 3.5.0-26085 and 3.5.1-26102 allows remote attackers to inject SQL commands, limited to write operations, 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 Synology Drive Server's system syncing daemon allows remote attackers to inject arbitrary SQL commands, limited to write operations (INSERT/UPDATE/DELETE), due to improper neutralization of special elements in SQL commands. The attack vector is via unspecified network vectors.

MitigationUpgrade Synology Drive Server to version 3.0.4-12699, 3.2.1-23280, 3.5.0-26085, 3.5.1-26102 or later. As an additional defense-in-depth measure, restrict network access to the Synology management interfaces and ensure the system is not directly exposed to untrusted networks.

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
Drive ServerApplication
Affected:< 3.0.4-12699< 3.2.1-23280< 3.5.0-26085< 3.5.1-26102

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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

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 Synology Drive Server version via web interface
    Log into Synology DSM, open Package Center, find Synology Drive Server, and view the version number in the package details
    Affected if The displayed version is below 3.0.4-12699, 3.2.1-23280, 3.5.0-26085, or 3.5.1-26102 (whichever threshold applies to your installed branch)
  2. Check Synology Drive Server version via command line
    SSH into the Synology NAS and run: cat /var/packages/SynologyDrive/INFO
    Affected if The version shown is below any of the following: 3.0.4-12699, 3.2.1-23280, 3.5.0-26085, or 3.5.1-26102
  3. Confirm the specific version string format
    Examine the full version string from the INFO file, noting both the major.minor.patch format and the build number (e.g., 3.5.0-26085)
    Affected if The build number portion is lower than 12699 (for 3.0.x), 23280 (for 3.2.x), 26085 (for 3.5.0), or 26102 (for 3.5.1)

You are affected if your installed Synology Drive Server version is lower than any of the fixed versions (3.0.4-12699, 3.2.1-23280, 3.5.0-26085, or 3.5.1-26102) in your release branch.

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 3.0.4-12699 / 3.2.1-23280 / 3.5.0-26085 or later
Fixed in 3.0.4-126993.2.1-232803.5.0-26085
Interim mitigation

Upgrade Synology Drive Server to version 3.0.4-12699, 3.2.1-23280, 3.5.0-26085, 3.5.1-26102 or later. As an additional defense-in-depth measure, restrict network access to the Synology management interfaces and ensure the system is not directly exposed to untrusted networks.

Recommended fix High confidence

Upgrade to Synology Drive Server 3.0.4-12699, 3.2.1-23280, 3.5.0-26085, or 3.5.1-26102 (recommended)

  1. 1. Identify the current version of Synology Drive Server installed on your system via Package Center or the DSM dashboard
  2. 2. Determine which version branch you are running (3.0.x, 3.2.x, or 3.5.x) to select the appropriate upgrade path
  3. 3. In Package Center, check for available updates for Synology Drive Server
  4. 4. If automatic updates are not available, manually download the appropriate package from Synology's download center for your specific DSM version
  5. 5. Stop any running services using Synology Drive Server if prompted during the upgrade process
  6. 6. Apply the update to upgrade Drive Server to version 3.0.4-12699 (or higher in 3.0.x), 3.2.1-23280 (or higher in 3.2.x), 3.5.0-26085 (or higher in 3.5.x), or preferably 3.5.1-26102
  7. 7. After upgrade completes, verify the new version is installed via Package Center
  8. 8. Confirm Synology Drive Server services are running properly and accessible

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

Fix this in Drive Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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