CVE-2021-29091
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 limitation of a pathname to a restricted directory ('Path Traversal') vulnerability in file management component in Synology Photo Station before 6.8.14-3500 allows remote authenticated users to write 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 confidencePath traversal vulnerability in Synology Photo Station's file management component allows authenticated remote users to write arbitrary files to restricted directories by manipulating file path inputs (e.g., using '..' sequences or absolute paths). The vulnerability exists in versions prior to 6.8.14-3500.
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.14-3500CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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.
-
Verify Photo Station is installedLog into Synology DSM and open Package Center, or run 'sudo synopkg list' via SSH to list installed packages. Look for 'Photo Station' in the package list.Affected if Photo Station is not installed on the Synology NAS, the vulnerability does not apply.
-
Determine installed Photo Station versionIn DSM Package Center, click on Photo Station and view the version number. Alternatively, access Photo Station directly via web browser and check the version in Settings > About, or run 'sudo synopkg info PhotoStation' via SSH.Affected if The installed version is 6.8 or higher but lower than 6.8.14-3500.
-
Confirm remote access is enabledIn DSM, go to Control Panel > Application Portal > Photo Station settings, or check if the Photo Station web interface is accessible from outside the local network (via DDNS or QuickConnect).Affected if Photo Station is accessible remotely (either via DDNS, QuickConnect, or open firewall rules) and the version is in the affected range.
-
Check if file management feature is activeLog into Photo Station as a user and verify the 'File Browser' or file management feature is accessible. This feature is required for the path traversal to be exploitable.Affected if Authenticated users have access to the file management component and the version is in the affected range.
A Synology NAS is affected if Photo Station is installed with version 6.8 through 6.8.13-3499 and is accessible to authenticated remote 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.8.14-3500
Upgrade Synology Photo Station to version 6.8.14-3500 or later, or apply the latest available security patch from Synology's update repository.
- Consultation3.0 h
- Implementation2.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 $3,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-29091 — 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-2021-29091 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