dbcve.org
Ds107 FirmwareOperating system · Synology

CVE-2016-6554

CRITICAL · 9.8 CVSS v3.0 Published 2018-07-13
Fix available
A fix is available. Upgrade to after 5.2-5644-1 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Synology NAS servers DS107, firmware version 3.1-1639 and prior, and DS116, DS213, firmware versions prior to 5.2-5644-1, use non-random default credentials of: guest:(blank) and admin:(blank) . A remote network attacker can gain privileged access to a vulnerable device.

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

Synology NAS servers (DS107, DS116, DS213) ship with non-random default credentials where both the guest and admin accounts have blank/empty passwords. A remote network attacker can leverage these known default credentials to gain administrative access to vulnerable devices.

MitigationImmediately change or disable the default guest and admin accounts with blank passwords, and update firmware to version 5.2-5644-1 or later for DS116/DS213, and beyond 3.1-1639 for DS107.

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
Ds107 FirmwareOperating system
Affected:<= 3.1-1639
Ds213 FirmwareOperating system
Affected:<= 5.2-5644-1
Ds116 FirmwareOperating system
Affected:<= 5.2-5644-1

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

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

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. Identify the Synology NAS model
    Access the DSM web interface and look at the top-right corner for the model name (DS107, DS116, or DS213), or run 'cat /proc/sys/kernel/syno_hw_version' via SSH if available
    Affected if The model is DS107, DS116, or DS213
  2. Check the installed firmware version
    In DSM, go to Control Panel > System > Update & Restore > DSM Update to view the current version, or run 'cat /etc/VERSION' via SSH
    Affected if The firmware version is <= 3.1-1639 for DS107, or <= 5.2-5644-1 for DS116 or DS213
  3. Verify the admin account password is not blank
    Log into DSM with the admin account. If you can access it without entering a password, or if the password field is empty, the account has a blank password. Also check via SSH: run 'sudo synouser --list' to list users and their password status
    Affected if The admin account has a blank/empty password (no password set)
  4. Verify the guest account status and password
    In DSM, go to Control Panel > User > Guest and check if the account is enabled and has no password set, or run 'sudo synouser --list' via SSH to inspect the guest account configuration
    Affected if The guest account is enabled with a blank/empty password

A user is affected if they have a DS107, DS116, or DS213 running firmware at or below the specified version limits AND the admin or guest account has a blank password, allowing remote attackers to gain administrative access using known default credentials.

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 a release after 5.2-5644-1
Interim mitigation

Immediately change or disable the default guest and admin accounts with blank passwords, and update firmware to version 5.2-5644-1 or later for DS116/DS213, and beyond 3.1-1639 for DS107.

Recommended fix High confidence

Firmware 5.2-5644-1 or later for DS116/DS213; any version after 3.1-1639 for DS107

  1. 1. Identify the exact model (DS107, DS213, or DS116) and current firmware version of your Synology NAS device
  2. 2. For DS213 and DS116: Navigate to Synology's download center and download firmware version 5.2-5644-1 or later
  3. 3. For DS107: Navigate to Synology's download center and download any firmware version newer than 3.1-1639
  4. 4. Log into the Synology DSM administrative interface
  5. 5. Go to Control Panel > System > DSM Update
  6. 6. Select Manual DSM Update and upload the downloaded firmware file
  7. 7. Allow the firmware update process to complete - the device will restart
  8. 8. After the device restarts, log into DSM with the default credentials
Caveat Firmware updates may temporarily disrupt services; ensure backups are current before updating

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

Fix this in Ds107 Firmware Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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