dbcve.org
Photo StationApplication · Synology

CVE-2017-12079

HIGH · 7.5 CVSS v3.0 Published 2017-12-04
Fix available
A fix is available. Upgrade to 6.3-2970 / 6.8.1-3458 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Files or directories accessible to external parties vulnerability in picasa.php in Synology Photo Station before 6.8.1-3458 and before 6.3-2970 allows remote attackers to obtain arbitrary files via prog_id field.

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 confidence

This is a path traversal/local file inclusion vulnerability in Synology Photo Station's picasa.php. The prog_id parameter is not properly sanitized, allowing remote unauthenticated attackers to read arbitrary files from the server filesystem by manipulating the parameter to contain directory traversal sequences (e.g., ../../). This can expose sensitive configuration files, credentials, and source code.

MitigationUpdate Synology Photo Station to version 6.8.1-3458 or 6.3-2970 or later to patch the vulnerability. As an interim control, restrict network access to Photo Station from untrusted sources until the update can be applied.

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
Photo StationApplication
Affected:>= 6.8, < 6.8.1-3458>= 6.3, < 6.3-2970

CVSS 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
High
Integrity
None
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Photo Station is installed
    Log into the Synology NAS administrative interface and navigate to the package center to verify if Photo Station package is installed, or check for the presence of the Photo Station web files in /web/photo or similar directory on the file system.
    Affected if Photo Station is not installed then this CVE does not apply to the environment.
  2. Identify the installed Photo Station version
    Within the Synology package center, view the installed Photo Station package details to see the current version number, or access Photo Station directly and look for the version information typically found in the application settings or about section.
    Affected if The installed version falls within the affected ranges: version 6.8 through 6.8.1-3457 (exclusive), or version 6.3 through 6.3-2969 (exclusive). Versions 6.8.1-3458 and 6.3-2970 or later are not affected.
  3. Locate the vulnerable picasa.php script
    Check if the file picasa.php exists in the Photo Station web directory, typically found at /web/photo/picasa.php or similar path within the Synology web station directory structure.
    Affected if If picasa.php does not exist, the specific vulnerable endpoint is not present and the issue may not be exploitable.
  4. Verify the vulnerability exists (safe test)
    Using a local authenticated session, attempt a safe test by sending a request to the picasa.php endpoint with a prog_id parameter containing a known local file path such as ../../../../etc/passwd or a Synology-specific configuration file, observing if the file contents are returned in the response.
    Affected if If the response contains the contents of the targeted file, the vulnerability is present and the environment is affected by this CVE.

The environment is affected if Synology Photo Station is installed with a version between 6.3 and 6.3-2969, or between 6.8 and 6.8.1-3457, and the picasa.php endpoint responds with file contents when given directory traversal sequences in the prog_id parameter.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 6.3-2970 / 6.8.1-3458 or later
Fixed in 6.3-29706.8.1-3458
Interim mitigation

Update Synology Photo Station to version 6.8.1-3458 or 6.3-2970 or later to patch the vulnerability. As an interim control, restrict network access to Photo Station from untrusted sources until the update can be applied.

Fix this in Photo Station Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,832.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-12079 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-12079 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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