CVE-2022-27610
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 · uneditedImproper limitation of a pathname to a restricted directory ('Path Traversal') vulnerability in webapi component in Synology DiskStation Manager (DSM) before 6.2.3-25423 allows remote authenticated users to delete 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 confidenceThis is a path traversal vulnerability in the webapi component of Synology DiskStation Manager (DSM). It allows remote authenticated users to escape the intended restricted directory and delete arbitrary files on the system by manipulating file paths in webapi requests.
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>= 6.2, < 6.2.3-25423CVSS 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
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check DSM version via web interfaceLog into the Synology DiskStation Manager web interface. The version is typically displayed on the Welcome page or in the Control Panel > System > Version section. Alternatively, use the command line: cat /etc/VERSIONAffected if The installed version is 6.2 or higher but lower than 6.2.3-25423
-
Verify webapi component is accessibleConfirm the webapi is enabled by attempting to access the API endpoint. In DSM, the webapi is typically available at /webapi/query.cgi. If the system responds to requests at this endpoint, the component is active.Affected if The webapi endpoint responds to requests (component is enabled and reachable)
-
Confirm remote authentication is enabledCheck if the DSM allows remote user authentication. In Control Panel > User & Group, verify that user accounts exist and remote access is permitted. The vulnerability requires an authenticated user session.Affected if Remote authenticated users can log into DSM via the web interface or API
-
Determine if the system is exposed to untrusted networksReview network firewall rules and VPN/access controls. Check if the DSM management interface (port 5000/5001) or webapi endpoints are accessible from untrusted networks or the internet.Affected if The webapi is accessible from networks outside the trusted internal environment
The system is affected if DSM version is 6.2 or higher but below 6.2.3-25423, the webapi component is accessible, and remote authenticated users can access the system.
Generated from the published advisory. Verify against your own configuration.
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 · scoped6.2.3-25423
Upgrade DSM to version 6.2.3-25423 or later to obtain the patched webapi component. Additionally, review user account permissions and restrict API access to only necessary authenticated users.
DSM 6.2.3-25423 or later
- Log into Synology DiskStation Manager (DSM) as an administrator
- Navigate to Control Panel > Update & Restore > DSM Update
- Check the current DSM version under Control Panel > About to confirm it is below 6.2.3-25423
- If available, apply the latest DSM update from Control Panel > Update & Restore to reach version 6.2.3-25423 or newer
- Alternatively, download the DSM 6.2.3-25423 (or newer) update file from Synology's Download Center and manually apply it via Control Panel > Update & Restore > Manual DSM Update
- After the update completes, verify the DSM version under Control Panel > About shows 6.2.3-25423 or later
- Confirm the webapi functionality is operating normally after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2022-27610 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-27610 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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