Diskstation ManagerOperating system · Synology

CVE-2021-29087

HIGH · 7.5 CVSS v3.1 Published 2021-06-23
Fix available
A fix is available. Upgrade to 3.1-23033 / 6.2.3-25426-3 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
Improper limitation of a pathname to a restricted directory ('Path Traversal') vulnerability in webapi component in Synology DiskStation Manager (DSM) before 6.2.3-25426-3 allows remote attackers to write 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 path traversal vulnerability in the webapi component of Synology DiskStation Manager (DSM) versions prior to 6.2.3-25426-3 allows remote attackers to write arbitrary files to the filesystem via unspecified vectors. This can lead to remote code execution if attackers write malicious scripts to web-accessible directories.

MitigationUpgrade Synology DSM to version 6.2.3-25426-3 or later to patch the path traversal vulnerability. If immediate patching is not possible, restrict network access to the webapi interface and monitor for unauthorized file creation.

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:>= 6.2, < 6.2.3-25426-3
Diskstation Manager Unified ControllerOperating system
Affected:< 3.1-23033

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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. Check installed DSM version
    Log into the Synology web interface and go to Control Panel > DSM Desktop > DSM version, or run `cat /etc/VERSION` via SSH on the device
    Affected if The version is 6.2.x but lower than 6.2.3-25426-3, or the version shows as any build before 3.1-23033 for Unified Controller systems
  2. Verify webapi endpoint is accessible
    Attempt to reach the webapi endpoint at `https://[your-dsm-ip]/webapi/` from a network client
    Affected if The endpoint responds with JSON data, indicating the webapi is exposed and reachable
  3. Inspect web-accessible directories for unauthorized files
    Check directories such as /webman/ and /webapi/ for any unexpected or recently created script files (e.g., .php, .cgi, .sh) using `ls -la /var/packages/WebStation/target/apache22/data/` or the equivalent web root path
    Affected if Any unfamiliar script files exist that were not intentionally deployed by an administrator
  4. Review file creation timestamps in web directories
    Use `find /var/packages/WebStation/ -type f -mtime -30` (or similar) to list files modified within the last 30 days in web-accessible directories
    Affected if Files appear with creation/modification timestamps that correlate with the period when the vulnerability was publicly disclosed or actively exploited

A system is affected if it runs DSM version 6.2 through 6.2.3-25426-2 (or Unified Controller below 3.1-23033) AND has the webapi component network-accessible, with potential indicators being unauthorized script files in web directories.

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.

From vendor data
Upgrade available Upgrade to 3.1-23033 / 6.2.3-25426-3 or later
Fixed in 3.1-230336.2.3-25426-3
Interim mitigation

Upgrade Synology DSM to version 6.2.3-25426-3 or later to patch the path traversal vulnerability. If immediate patching is not possible, restrict network access to the webapi interface and monitor for unauthorized file creation.

Fix this in Diskstation Manager Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-29087 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-2021-29087 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