dbcve.org
Drive ServerApplication · Synology

CVE-2024-50630

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
Missing authentication for critical function vulnerability in the webapi component 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 obtain administrator credentials 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

Missing authentication vulnerability in Synology Drive Server's webapi component allows unauthenticated remote attackers to obtain administrator credentials. The flaw affects multiple version branches (3.0.x before 3.0.4-12699, 3.2.x before 3.2.1-23280, and 3.5.x before 3.5.1-26102) and enables credential theft via unspecified vectors without requiring valid authentication.

MitigationUpdate Synology Drive Server to version 3.0.4-12699, 3.2.1-23280, 3.5.0-26085, or 3.5.1-26102 or later. As temporary mitigation, restrict network access to the webapi interface using firewall rules or VPN until the patch can be applied.

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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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. Verify Synology Drive Server is installed
    Access Synology Package Center or run `synopkg list` via SSH to confirm Synology Drive Server package is installed
    Affected if Package is not installed or not applicable
  2. Check installed version of Synology Drive Server
    In Package Center, click on Synology Drive Server to view version details, or run `synopkg info SynologyDriveServer` via SSH
    Affected if Version is 3.0.x before 3.0.4-12699, 3.2.x before 3.2.1-23280, or 3.5.x before 3.5.1-26102
  3. Confirm webapi component is exposed
    Check if the webapi endpoint is accessible externally by attempting to reach https://[your-synology-ip]/webapi/ or the Synology Drive web interface path
    Affected if Webapi interface is reachable from untrusted networks (internet or unauthorized LAN)
  4. Review firewall or access rules for Drive Server
    In Synology Control Panel under Security > Firewall, verify if rules restrict access to the Drive Server webapi ports (typically 6690 for Synology Drive) to trusted IPs only
    Affected if No firewall rule restricts webapi access to authorized networks or IPs

User is affected if Synology Drive Server is installed with a version below 3.0.4-12699, 3.2.1-23280, or 3.5.1-26102 AND the webapi interface is accessible to untrusted networks.

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

Update Synology Drive Server to version 3.0.4-12699, 3.2.1-23280, 3.5.0-26085, or 3.5.1-26102 or later. As temporary mitigation, restrict network access to the webapi interface using firewall rules or VPN until the patch can be applied.

Recommended fix High confidence

3.0.4-12699 (for 3.0.x branch), 3.2.1-23280 (for 3.2.x branch), or 3.5.1-26102 (for 3.5.x branch)

  1. 1. Identify the current installed version of Synology Drive Server via the DSM Package Center or command line
  2. 2. Determine which version branch is currently installed (3.0.x, 3.2.x, or 3.5.x)
  3. 3. For version 3.0.x: Upgrade to version 3.0.4-12699 or later
  4. 4. For version 3.2.x: Upgrade to version 3.2.1-23280 or later
  5. 5. For version 3.5.x: Upgrade to version 3.5.1-26102 (or 3.5.0-26085 as minimum)
  6. 6. Perform the upgrade via Synology DSM Package Center or manually download the .spk from Synology's download center
  7. 7. After upgrade, verify the new version is installed and test that Synology Drive functionality is working correctly
  8. 8. Review Synology's release notes for any additional post-upgrade configuration requirements
Caveat Review Synology release notes for version-specific breaking changes; ensure backups exist before upgrading

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-50630 — 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-50630 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