CVE-2017-11149
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 · uneditedServer-side request forgery (SSRF) vulnerability in Downloader in Synology Download Station 3.8.x before 3.8.5-3475 and 3.x before 3.5-2984 allows remote authenticated users to download arbitrary local files via crafted URI.
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 confidenceServer-side request forgery (SSRF) in Synology Download Station's Downloader allows authenticated remote users to supply crafted URIs (e.g., file:// protocol) to access arbitrary local files on the server, bypassing the intended restriction to only download from remote HTTP/HTTPS sources.
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= 3.2-2295= 3.3-2382= 3.3-2383= 3.3-2386= 3.4-2477= 3.4-2478= 3.4-2480= 3.4-2485= 3.4-2486= 3.4-2489= 3.4-2490= 3.4-2514CVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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.
-
Confirm Download Station is installedAccess Synology DSM and navigate to Package Center to verify Download Station is installed, or run 'synopkg list' via SSH to enumerate installed packagesAffected if Download Station does not appear in the installed packages list
-
Identify installed Download Station versionIn DSM Package Center, click on Download Station and view the version details, or run 'synopkg getinfo DownloadStation' via SSH to retrieve the exact version numberAffected if version matches any of these: 3.2-2295, 3.3-2382, 3.3-2383, 3.3-2386, 3.4-2477, 3.4-2478, 3.4-2480, 3.4-2485, 3.4-2486, 3.4-2489, 3.4-2490, 3.4-2514
-
Verify Downloader component is accessibleLog into DSM and access the Download Station application. Check that the Downloader functionality (the URI input field for adding downloads) is available and operationalAffected if Download Station interface loads and the Downloader URI input field is accessible to authenticated users
Environment is affected if Download Station is installed with a version matching any of the listed affected versions and the Downloader feature is accessible to authenticated users
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 dataUpdate Synology Download Station to version 3.8.5-3475 or 3.5-2984 or later. Additionally, restrict Download Station's network access and consider implementing additional input validation at the network perimeter.
- Consultation3.0 h
- Implementation2.0 h
- Testing3.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,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-11149 — 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-11149 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