CVE-2017-15893
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 · uneditedDirectory traversal vulnerability in the SYNO.FileStation.Extract in Synology File Station before 1.1.1-0099 allows remote authenticated users to write arbitrary files via the dest_folder_path parameter.
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 confidenceDirectory traversal vulnerability in Synology File Station's SYNO.FileStation.Extract function allows remote authenticated users to write arbitrary files to the filesystem by manipulating the dest_folder_path parameter with path traversal sequences (e.g., ../../../'). This could enable privilege escalation or arbitrary code execution.
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< 1.1.1-0099CVSS 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
- None
CVSS:3.0/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Verify File Station package is installedLog into Synology DSM and open Package Center, or run 'pkginfo | grep -i file-station' via SSHAffected if File Station package is not installed (not affected)
-
Check installed File Station versionIn Package Center, click File Station and view the version number. Alternatively, check via CLI: 'cat /var/lib/dss/ticketd/pkginfo.json | grep -A5 filestation' or check the DSM web interface under Package Center > File Station > VersionAffected if Version is earlier than 1.1.1-0099 (vulnerable)
-
Confirm Extract function is accessibleVerify File Station is actually in use and the Extract/Extract archive feature is accessible to authenticated users via the web interface or API endpoint SYNO.FileStation.ExtractAffected if Authenticated users can access the Extract function (potentially exploitable)
-
Audit filesystem for unexpected filesReview the file system for newly created files in unexpected locations (e.g., /var/packages/FileStation/target, /etc, /usr/syno/synoman). Use 'find / -newer /path/to/known-good-timestamp -type f 2>/dev/null' to identify recently created files outside expected extraction directoriesAffected if Arbitrary files exist outside designated extraction directories
User is affected if Synology File Station version is below 1.1.1-0099 AND the Extract feature is accessible to authenticated users on the network.
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.
From vendor data1.1.1-0099
Update Synology File Station to version 1.1.1-0099 or later. If immediate patching is not possible, restrict access to File Station to trusted users only and implement file system monitoring for suspicious write operations outside expected directories.
- Consultation2.0 h
- Implementation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-15893 — 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-2017-15893 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