CVE-2022-22685
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 WebDAV Server before 2.4.0-0062 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 confidenceA path traversal vulnerability exists in the webapi component of Synology WebDAV Server versions prior to 2.4.0-0062. The vulnerability allows authenticated remote users to manipulate file paths using directory traversal sequences (such as ../) to access and delete files outside the intended WebDAV directory scope, leading to unauthorized arbitrary file deletion.
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< 2.4.0-0062CVSS 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.
-
Identify WebDAV Server versionAccess Synology Package Center and locate WebDAV Server in the installed package list, or check the version via command line if availableAffected if Installed version is lower than 2.4.0-0062
-
Confirm WebDAV service is runningLog into Synology DSM and verify that WebDAV Server is listed as running in Package Center or in the Services control panelAffected if WebDAV Server is installed and running (the vulnerability only applies to running instances)
-
Review WebDAV authentication configurationIn DSM, open WebDAV Server settings and examine which users or groups have WebDAV access permissionsAffected if Any authenticated user account (beyond only administrators) is granted WebDAV access - the flaw allows any authenticated user to perform unauthorized file deletion
You are affected if WebDAV Server is running with a version prior to 2.4.0-0062 and non-administrator authenticated users have WebDAV access permissions.
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 · scoped2.4.0-0062
Update Synology WebDAV Server to version 2.4.0-0062 or later. If immediate patching is not possible, restrict WebDAV access to trusted authenticated users only and monitor for suspicious file deletion activity.
2.4.0-0062
- Open Synology DiskStation Manager (DSM) and navigate to Package Center
- Locate WebDAV Server in the list of installed packages
- Click on WebDAV Server and select 'Update' if an update is available
- Confirm the update to version 2.4.0-0062 or later
- Verify the update was successful by checking the installed version in Package Center
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.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 $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-22685 — 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-22685 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