dbcve.org
Diskstation ManagerOperating system · Synology

CVE-2025-1021

HIGH · 7.5 CVSS v3.1 Published 2025-04-23
Fix available
A fix is available. Upgrade to 7.1.1-42962-8 / 7.2.1-69057-7 or later.
See remediation →
84/100
Remediation priority · High
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
Missing authorization vulnerability in synocopy in Synology DiskStation Manager (DSM) before 7.1.1-42962-8, 7.2.1-69057-7 and 7.2.2-72806-3 allows remote attackers to read arbitrary files 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

A missing authorization vulnerability in the synocopy component of Synology DiskStation Manager (DSM) allows unauthenticated remote attackers to read arbitrary files on the affected system. The vulnerability affects DSM versions prior to 7.1.1-42962-8, 7.2.1-69057-7, and 7.2.2-72806-3, and can be exploited remotely without authentication.

MitigationUpgrade DSM to one of the patched versions (7.1.1-42962-8, 7.2.1-69057-7, or 7.2.2-72806-3) and review access controls around the synocopy functionality.

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, < 7.1.1-42962-8>= 7.2.1-69057, < 7.2.1-69057-7>= 7.2.2, < 7.2.2-72806-3

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify DSM version
    Log into DSM via web interface and navigate to Control Panel > System > System Information, or run 'cat /etc/VERSION' via SSH to retrieve the exact DSM build number and version string
    Affected if The installed version falls within any of these ranges: 7.1.x before build 42962-8, 7.2.1-x before build 69057-7, or 7.2.2-x before build 72806-3
  2. Confirm synocopy component is present
    Check if the synocopy binary or web endpoint exists on the system. On DSM, this is typically accessible via the web interface or as a CGI binary under /usr/syno/synoman/webapi/
    Affected if The synocopy component is installed and exposed on the system (this is default in vulnerable DSM versions)
  3. Verify network exposure of synocopy
    Review firewall rules and port mappings on the Synology device. Check if the DSM web interface (ports 5000/5001 or 80/443) is exposed to untrusted networks. The vulnerability is remotely exploitable without authentication, so external exposure increases risk
    Affected if The DSM web interface or synocopy endpoint is accessible from untrusted networks (internet or DMZ)

If the DSM version is below 7.1.1-42962-8, 7.2.1-69057-7, or 7.2.2-72806-3 AND the synocopy component is exposed, the system is vulnerable to unauthenticated arbitrary file read attacks

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-8 / 7.2.1-69057-7 / 7.2.2-72806-3 or later
Fixed in 7.1.1-42962-87.2.1-69057-77.2.2-72806-3
Interim mitigation

Upgrade DSM to one of the patched versions (7.1.1-42962-8, 7.2.1-69057-7, or 7.2.2-72806-3) and review access controls around the synocopy functionality.

Recommended fix High confidence

DSM 7.1.1-42962-8, DSM 7.2.1-69057-7, or DSM 7.2.2-72806-3 (or later) depending on your current major version branch

  1. 1. Identify your current DSM version in Control Panel > Update & Restore > DSM Update
  2. 2. Based on your current version, determine the target upgrade path: if on 7.1.x, upgrade to 7.1.1-42962-8 or later; if on 7.2.1.x, upgrade to 7.2.1-69057-7 or later; if on 7.2.2.x, upgrade to 7.2.2-72806-3 or later
  3. 3. In Control Panel > Update & Restore, click 'Download Update' to obtain the latest DSM update containing the security fix
  4. 4. Apply the DSM update and restart the device when prompted
Caveat Standard DSM update risks apply - ensure backups exist before upgrading; updates may require downtime

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

Fix this in Diskstation Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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