dbcve.org
Drive ServerApplication · Synology

CVE-2018-8922

MEDIUM · 6.5 CVSS v3.0 Published 2018-06-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/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 access control vulnerability in Synology Drive before 1.0.2-10275 allows remote authenticated users to access non-shared files or folders 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

An improper access control vulnerability in Synology Drive versions prior to 1.0.2-10275 allows authenticated users to bypass file/folder sharing restrictions and access resources that were not explicitly shared with them, representing a privilege escalation in data access.

MitigationUpgrade Synology Drive to version 1.0.2-10275 or later to remediate the access control bypass.

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:= 1.0.2-10275

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

CVSS:3.0/AV:N/AC:L/PR:L/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
    Check the Synology Package Center or run the command 'pkginfo' or check /var/packages/ for the Drive Server package
    Affected if Synology Drive Server package is present on the system
  2. Identify installed Synology Drive Server version
    Access Package Center UI and view the installed version of Synology Drive Server, or run 'cat /var/packages/SynologyDriveServer/info.json' to view version details
    Affected if The installed version number is lower than 1.0.2-10275
  3. Confirm user authentication is enabled
    Check that Synology Drive authentication is configured and users have accounts created in the Synology user management system
    Affected if User authentication is enabled and multiple user accounts exist in the system
  4. Verify file/folder sharing feature is active
    Check if any shared folders or files exist in Synology Drive by accessing the Drive web interface or checking /volume1/SynologyDrive/ for shared content
    Affected if Shared files or folders exist in Synology Drive that may have restricted access permissions

A user is affected if Synology Drive Server is installed with a version lower than 1.0.2-10275 and the file/folder sharing feature is in use with 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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Synology Drive to version 1.0.2-10275 or later to remediate the access control bypass.

Fix this in Drive Server 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 help mitigating

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-2018-8922 — 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-2018-8922 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