dbcve.org
Diskstation ManagerApplication · Synology

CVE-2022-22688

HIGH · 8.8 CVSS v3.1 Published 2022-03-25
Fix available
A fix is available. Upgrade to 6.2.4-25556-2 / 7.0.1-42214 or later.
See remediation →
94/100
Remediation priority · Urgent
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 neutralization of special elements used in a command ('Command Injection') vulnerability in File service functionality in Synology DiskStation Manager (DSM) before 6.2.4-25556-2 allows remote authenticated users to execute arbitrary commands 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 · moderate confidence

Command injection vulnerability in Synology DiskStation Manager's File service allows remote authenticated users to execute arbitrary OS commands by injecting special elements into service parameters. The vulnerability stems from improper neutralization of user input before passing it to system command execution functions.

MitigationUpgrade Synology DSM to version 6.2.4-25556-2 or later. Additionally, limit the number of authenticated users with file service access and apply network segmentation to reduce the attack surface.

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
Diskstation ManagerApplication
Affected:>= 7.0, < 7.0.1-42214>= 6.2, < 6.2.4-25556-2

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

CVSS:3.1/AV:N/AC:L/PR:L/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 DSM version
    In DSM, go to Control Panel > System > Overview to view the installed version, or run 'cat /etc/VERSION' via SSH to retrieve the exact build number
    Affected if Version is 7.0.x before 7.0.1-42214, or 6.2.x before 6.2.4-25556-2
  2. Confirm File service is enabled
    In DSM, go to Control Panel > File Services > SMB/AFP/FTP to verify if any file sharing service is turned on. Check if SMB (Windows file service), AFP, or NFS is active
    Affected if Any file service (SMB, AFP, or NFS) is enabled and exposed to network users
  3. Verify user access to file services
    In DSM, go to Control Panel > User & Group to review which users have permissions to access file services. Check file sharing settings for shared folders
    Affected if One or more authenticated users exist with access to file services
  4. Review network exposure
    In DSM, go to Control Panel > Security > Firewall to check if file service ports (SMB: 445/139, AFP: 548) are exposed to untrusted networks
    Affected if File services are accessible from external or untrusted networks without VPN or firewall restrictions

You are affected if your DSM version falls within the affected ranges AND you have file services enabled with authenticated users able to access them over the network.

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 6.2.4-25556-2 / 7.0.1-42214 or later
Fixed in 6.2.4-25556-27.0.1-42214
Interim mitigation

Upgrade Synology DSM to version 6.2.4-25556-2 or later. Additionally, limit the number of authenticated users with file service access and apply network segmentation to reduce the attack surface.

Recommended fix High confidence

DSM 6.2.4-25556-2 or DSM 7.0.1-42214 (or later respective releases)

  1. 1. Back up all critical data on the Synology NAS before performing any system update.
  2. 2. Log into Synology DiskStation Manager as an administrator.
  3. 3. Navigate to Control Panel > Update & Restore > DSM Update.
  4. 4. Check for available updates and install the appropriate version:
  5. - For DSM 6.2 systems: Upgrade to DSM 6.2.4-25556-2 or later
  6. - For DSM 7.0 systems: Upgrade to DSM 7.0.1-42214 or later
  7. 5. After the update completes, verify the DSM version by going to Control Panel > System > DSM Update to confirm the installed version is patched.
Caveat Major DSM version upgrades may have compatibility implications with existing packages and configurations; review package compatibility before upgrading and ensure backups are current

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

Fix this in Diskstation Manager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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