CVE-2017-11162
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 synphotoio in Synology Photo Station before 6.7.4-3433 and 6.3-2968 allows remote authenticated users to read 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 · moderate confidenceDirectory traversal vulnerability in the synphotoio component of Synology Photo Station allows authenticated remote users to read arbitrary files on the filesystem via path traversal sequences in unspecified vectors.
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.3-2967<= 6.7.3-3432CVSS 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.
-
Identify Synology Photo Station versionAccess the Photo Station interface, then go to Control Panel > Package Center > Photo Station, or run 'cat /etc/synoinfo.conf | grep photostation' via SSH to retrieve the installed version numberAffected if The installed version is 6.3-2967 or earlier, or 6.7.3-3432 or earlier
-
Verify synphotoio component is accessibleConfirm the synphotoio module is installed and exposed via the web interface. Check if the Photo Station API endpoint /photo/synphotoio/ is accessible (e.g., visit https://[server]/photo/synphotoio/)Affected if The synphotoio component is present and reachable without being explicitly disabled
-
Confirm authentication to Photo StationAttempt to log into Photo Station with valid credentials, or verify that guest access or weak authentication is configured that allows remote user authenticationAffected if Remote users can authenticate to Photo Station (whether as standard user, admin, or via guest account)
-
Test for path traversal capabilityWith authenticated access, send a request to the synphotoio endpoint containing path traversal sequences such as '../' or '..%2f' to attempt accessing files outside the Photo Station directoryAffected if The application accepts and processes path traversal sequences in requests to synphotoio, allowing filesystem access beyond the intended directory
A user is affected if their Synology Photo Station version is 6.3-2967 or earlier, or 6.7.3-3432 or earlier, the synphotoio component is accessible, and they can authenticate to the Photo Station service
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 Photo Station to version 6.7.4-3433, 6.3-2968, or later to patch the directory traversal vulnerability in synphotoio.
- Consultation2.0 h
- Implementation1.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-11162 — 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-11162 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