CVE-2018-13288
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 · uneditedInformation exposure vulnerability in SYNO.FolderSharing.List in Synology File Station before 1.2.3-0252 and before 1.1.5-0125 allows remote attackers to obtain sensitive information via the (1) folder_path or (2) real_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 confidenceInformation disclosure vulnerability in Synology File Station's SYNO.FolderSharing.List API endpoint. The folder_path and real_path parameters are not properly validated, allowing remote attackers to potentially access sensitive path information they should not have visibility into.
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.1.5-0125>= 1.2, < 1.2.2-0250CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Synology File Station is installedCheck if the File Station package is installed on the Synology NAS. In DSM, open Package Center and look for 'File Station', or run 'cat /etc/synoinfo.conf | grep -i filestation' via SSH.Affected if File Station is not installed, the vulnerability does not apply.
-
Determine installed File Station versionIn DSM Package Center, click on File Station and view the version information. Alternatively, access the API directly at 'http://[NAS-IP]/webapi/entry.cgi?api=SYNO.Core.Package.Version&method=get&version=1' to retrieve package version details.Affected if Version cannot be determined, assume potentially affected if the package is installed.
-
Compare version against vulnerable rangesCheck if the installed version falls within: 1.1.x where x < 5-0125, OR 1.2.x where x < 2-0250. Versions 1.1.5-0125 and above, or 1.2.2-0250 and above, are patched.Affected if Installed version is 1.1.0-0125 through 1.1.4-xxxx, or 1.2.0-0249 through 1.2.1-xxxx, indicating the patch is not applied.
-
Verify SYNO.FolderSharing.List API is accessibleCheck if the File Station API endpoint responds. Attempt a request to 'http://[NAS-IP]/webapi/entry.cgi?api=SYNO.FolderSharing.List&method=list&version=1&folder_path=/' via a web browser or curl tool.Affected if The API endpoint returns a valid response (even if error), indicating the vulnerable endpoint is exposed on the network.
A Synology NAS with File Station installed and the SYNO.FolderSharing.List API accessible, running a version below 1.1.5-0125 or between 1.2.0-0249 and 1.2.1-xxxx, is affected by this information disclosure vulnerability.
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.5-01251.2.2-0250
Update Synology File Station to version 1.2.3-0252 or later (or 1.1.5-0125 or later for older branches) to obtain the security patch that addresses this information exposure issue.
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-13288 — 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-2018-13288 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