CVE-2017-16772
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 · uneditedImproper input validation vulnerability in SYNOPHOTO_Flickr_MultiUpload in Synology Photo Station before 6.8.3-3463 and before 6.3-2971 allows remote authenticated users to execute arbitrary codes via the prog_id 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 confidenceImproper input validation in the SYNOPHOTO_Flickr_MultiUpload component of Synology Photo Station allows remote authenticated users to execute arbitrary code by providing malicious input through the prog_id parameter.
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.8, < 6.8.3-3463>= 6.3, < 6.3-2971CVSS 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
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 Photo Station is installedAccess Synology DSM and check installed packages, or run 'grep -i photo /var/log/packages' to list installed packagesAffected if Photo Station package is not found in package manager
-
Identify Photo Station versionIn DSM, open Package Center, find Photo Station, and note the version number displayed; alternatively, check the version via Photo Station application info pageAffected if Version cannot be determined or is not visible in package manager
-
Compare version against affected rangesIf version starts with 6.8.x, verify it is below 6.8.3-3463. If version starts with 6.3.x, verify it is below 6.3-2971. Any version in between these ranges or below is affectedAffected if Installed version falls within 6.8.0 to 6.8.3-3462 (exclusive) OR 6.3.0 to 6.3-2970 (exclusive)
-
Check Flickr upload functionalityAccess Photo Station and navigate to Settings > Account > Flickr integration, or attempt to access the SYNOPHOTO_Flickr_MultiUpload API endpoint if knownAffected if Flickr integration feature is present and accessible in Photo Station interface
A user is affected if Photo Station is installed with a version between 6.3 and 6.3-2970 or between 6.8 and 6.8.3-3462, and the Flickr upload component 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 data6.3-29716.8.3-3463
Update Synology Photo Station to version 6.8.3-3463 (or later 6.8.x) or version 6.3-2971 (or later 6.3.x) to remediate the input validation vulnerability.
- 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-16772 — 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-16772 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