CVE-2019-11822
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 · uneditedRelative path traversal vulnerability in SYNO.PhotoStation.File in Synology Photo Station before 6.8.11-3489 and before 6.3-2977 allows remote attackers to upload arbitrary files via the uploadphoto 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 · moderate confidenceThis is a relative path traversal vulnerability in Synology Photo Station's SYNO.PhotoStation.File component. The vulnerability allows remote attackers to upload arbitrary files to the server by manipulating the uploadphoto parameter, potentially enabling remote code execution if the attacker can write executable content to web-accessible directories.
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, < 6.3-2977>= 6.8, < 6.8.11-3489CVSS 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.
-
Identify Photo Station versionOpen Synology DSM Package Center, locate Photo Station, and record the installed version number shown in the package detailsAffected if The installed version falls within < 6.3-2977 (for 6.3 branch) or >= 6.8 and < 6.8.11-3489 (for 6.8 branch)
-
Confirm DSM firmware versionIn DSM, go to Control Panel > System > System Update to see the DSM version, which bundles Photo StationAffected if DSM version bundles an affected Photo Station version per the ranges above
-
Verify Photo Station web access is enabledIn DSM Control Panel > Application Portal > Photo Station, check if the Photo Station web interface is accessibleAffected if Photo Station web interface is exposed and the installed version is vulnerable
-
Check SYNO.PhotoStation.File API exposureAttempt to access the Photo Station API endpoint /photo/webapi/ SYNO.PhotoStation.File or verify in the Photo Station configuration that the file upload API is publicly accessibleAffected if The upload API endpoint is reachable without authentication or with compromised credentials
A user is affected if their Synology Photo Station version is 6.3 through 6.3-2976, or 6.8 through 6.8.11-3488, and the Photo Station web interface or its SYNO.PhotoStation.File upload API is accessible to remote attackers
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-29776.8.11-3489
Upgrade Photo Station to version 6.8.11-3489 or 6.3-2977 or later. If immediate patching is not possible, consider restricting access to Photo Station via network segmentation or firewall rules, and monitor for unauthorized file uploads.
- 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-2019-11822 — 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-2019-11822 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