CVE-2017-12071
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 file_upload.php in Synology Photo Station before 6.7.4-3433 and 6.3-2968 allows remote authenticated users to download arbitrary local files via the url 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 confidenceServer-side request forgery (SSRF) vulnerability in file_upload.php in Synology Photo Station allows remote authenticated users to download arbitrary local files via the url parameter, effectively enabling local file disclosure.
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 installed Photo Station versionAccess Synology DSM > Package Center > Photo Station and note the version number displayed, or run 'synopkg list' and filter for Photo Station to retrieve the exact version.Affected if The installed version is 6.3-2967 or earlier, or 6.7.3-3432 or earlier.
-
Locate vulnerable file_upload.phpVerify the presence of file_upload.php in the Photo Station web directory, typically found under /var/packages/PhotoStation/target/photo/file_upload.php or the web root of the Photo Station application.Affected if The file exists and is accessible within the Photo Station installation.
-
Confirm Photo Station is network-accessibleCheck if the Synology NAS hosting Photo Station is exposed to the network by verifying the web interface ports (typically 5000/5001 or 80/443) are open and reachable from untrusted networks.Affected if Photo Station can be reached over the network from outside the local administrative segment.
-
Verify authentication is required for Photo StationReview Synology DSM security settings to confirm that Photo Station requires valid user authentication, and check whether guest access or weak authentication is enabled.Affected if Authenticated users (including low-privilege users) can access Photo Station and the file_upload.php endpoint.
Your environment is affected if Photo Station is network-accessible with version 6.3-2967 or earlier, or 6.7.3-3432 or earlier, and the file_upload.php endpoint accepts requests from 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 Photo Station to version 6.7.4-3433 or 6.3-2968 or later. If immediate patching is not possible, restrict administrative access and consider network segmentation to limit exposure.
- Consultation1.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-12071 — 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-12071 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