dbcve.org
Diskstation ManagerOperating system · Synology

CVE-2022-27625

CRITICAL · 9.8 CVSS v3.1 Published 2022-10-20
Fix available
A fix is available. Upgrade to 7.1.1-42962-2 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
A vulnerability regarding improper restriction of operations within the bounds of a memory buffer is found in the message 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 · high confidence

Buffer overflow vulnerability in the Out-of-Band (OOB) Management message processing functionality of Synology DSM. The improper restriction of memory buffer operations allows remote attackers to execute arbitrary commands without authentication.

MitigationUpgrade Synology DSM to version 7.1.1-42962-2 or later for affected models (DS3622xs+, FS3410, HD6500). If immediate patching is not possible, consider network isolation of 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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/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. Determine the installed DSM version
    Access the Synology web interface and navigate to Control Panel > System > Update & Restore, or run the command 'grep -i version /etc/VERSION' via SSH to retrieve the exact DSM version number
    Affected if The installed version is lower than 7.1.1-42962-2
  2. Verify the DSM build number
    Run 'cat /etc/VERSION' or check the build number in the web interface under DSM version details
    Affected if The build number is lower than 42962-2 (for the 7.1.1 release line)
  3. Confirm OOB Management interface status
    Access the web interface and navigate to Hardware & Power > OOB Management, or check via SSH using 'ls -la /etc/syno/oob' or similar configuration paths
    Affected if The OOB Management interface is enabled and accessible on the network
  4. Identify the specific Synology model
    Check the model name via the web interface Overview page or by running 'cat /proc/model' or 'cat /sys/firmware/devicetree/base/model' via SSH
    Affected if The device is a DS3622xs+, FS3410, or HD6500 model running a vulnerable DSM version

The environment is affected if the installed DSM version is below 7.1.1-42962-2 AND the OOB Management interface is enabled on a supported model.

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 for affected models (DS3622xs+, FS3410, HD6500). If immediate patching is not possible, consider network isolation of OOB management interfaces.

Recommended fix High confidence

DSM 7.1.1-42962-2

  1. Log into Synology DiskStation Manager (DSM) as an administrator
  2. Navigate to Control Panel > Update & Restore
  3. Click on 'DSM Update' to check for available updates
  4. Select DSM 7.1.1-42962-2 or a newer version from the available updates
  5. Confirm and proceed with the update installation
  6. Allow the system to reboot and complete the update process
  7. After reboot, verify the DSM version is 7.1.1-42962-2 or later via Control Panel > About

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
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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