dbcve.org
Diskstation ManagerOperating system · Synology

CVE-2022-27626

HIGH · 8.1 CVSS v3.1 Published 2022-10-20
Fix available
A fix is available. Upgrade to 7.1.1-42962-2 or later.
See remediation →
90/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
A vulnerability regarding concurrent execution using shared resource with improper synchronization ('Race Condition') is found in the session processing functionality of Out-of-Band (OOB) Management. This allows remote attackers to execute arbitrary commands via unspecified vectors. The following models with Synology DiskStation Manager (DSM) versions before 7.1.1-42962-2 may be affected: DS3622xs+, FS3410, and HD6500.

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

A race condition vulnerability exists in the Out-of-Band (OOB) Management session processing functionality of Synology DSM. The improper synchronization in shared resource access allows remote attackers to potentially manipulate timing to execute arbitrary commands. The CVSS 8.1 indicates high-severity remote code execution capability.

MitigationUpgrade Synology DSM to version 7.1.1-42962-2 or later on affected models (DS3622xs+, FS3410, HD6500). If patching is not immediately possible, consider network segmentation to restrict access to OOB management interfaces.

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 ManagerOperating system
Affected:< 7.1.1-42962-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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/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. Check DSM version
    Log into DSM and go to Control Panel > System > System Information, or run `cat /etc/VERSION` via SSH to view the installed DSM version number
    Affected if The installed version is lower than 7.1.1-42962-2
  2. Confirm OOB Management status
    Check if Out-of-Band Management (OOB/Intel AMT/BMC) is enabled on the device. On supported Synology models, this is typically configured in Control Panel > Hardware & Power > Out-of-Band Management, or via the `Get-Command` PowerShell cmdlet for Intel AMT
    Affected if OOB Management interface is enabled and accessible on the network
  3. Verify network accessibility of OOB interface
    Determine if the OOB management port (typically 16992-16994 for Intel AMT) is exposed externally or accessible from untrusted networks by reviewing firewall rules and port configurations
    Affected if The OOB management interface is reachable from untrusted networks or the internet
  4. Check for suspicious OOB sessions
    Review OOB management logs for unexpected or unauthorized session initiation, failed authentication attempts, or commands executed outside normal administration windows
    Affected if Unexpected OOB sessions or commands appear in the management interface logs

You are affected if your DSM version is below 7.1.1-42962-2 AND the OOB Management feature is enabled on your system.

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 7.1.1-42962-2 or later
Fixed in 7.1.1-42962-2
Interim mitigation

Upgrade Synology DSM to version 7.1.1-42962-2 or later on affected models (DS3622xs+, FS3410, HD6500). If patching is not immediately possible, consider network segmentation to restrict access to OOB management interfaces.

Recommended fix High confidence

DSM 7.1.1-42962-2

  1. 1. Back up all critical data on the Synology NAS before performing any system update
  2. 2. Log in to Synology DiskStation Manager (DSM) as an administrator
  3. 3. Navigate to Control Panel > Update & Restore > DSM Update
  4. 4. Check for available updates - ensure the update version is 7.1.1-42962-2 or later
  5. 5. Download and install the DSM 7.1.1-42962-2 update or newer
  6. 6. After the update completes, verify the DSM version by going to Control Panel > About > Version (should show 7.1.1-42962-2 or higher)
  7. 7. Verify that the OOB Management service is functioning correctly post-update
Caveat DSM 7.x updates may require reconfiguration of some applications or settings; review Synology's upgrade notes before proceeding

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

Fix this in Diskstation Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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