CVE-2017-20210
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 · uneditedPhoto Station 5.4.1 & 5.2.7 include the security fix for the vulnerability related to the XMR mining programs identified by internal research.
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 vulnerability in QNAP Photo Station (versions prior to 5.4.1 and 5.2.7) allowed remote execution of XMR (Monero) cryptocurrency mining programs, indicating a critical remote code execution (RCE) flaw in the web application. The CVSS 9.8 score reflects an easily exploitable vulnerability enabling attackers to compromise affected systems for cryptojacking purposes.
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= 5.2.7= 5.4.1CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Identify Photo Station installationAccess QNAP Admin Panel, navigate to Photo Station (or App Center > Photo Station) and view the version information displayed in the application details or about sectionAffected if Photo Station is installed on the QNAP device
-
Confirm installed versionLocate the version number displayed in the Photo Station interface. If accessing via command line, check /etc/config/qpkg/PhotoStation or use qpkgmanager command to query installed packagesAffected if Version is below 5.2.7 or below 5.4.1 (both versions 5.2.x < 5.2.7 and 5.4.x < 5.4.1 are vulnerable)
-
Inspect running processes for mining activityVia QNAP SSH or admin shell, run 'ps aux' or check the Task Manager in the web interface for unknown processes. Look for processes named xmrig, xmr-stak, or any process consuming high CPU while idleAffected if Processes matching cryptocurrency mining software are running
-
Check for outbound mining pool connectionsUse 'netstat -an' or the QNAP Network Traffic analysis to identify connections to known mining pool ports (such as 3333, 5555, or uncommon high ports to suspicious IP ranges)Affected if The system has active connections to known Monero mining pool IP addresses or ports
A system is affected if Photo Station version is below 5.2.7 or below 5.4.1, or if cryptocurrency mining processes are detected running on the QNAP device.
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 dataUpgrade Photo Station to version 5.4.1 or 5.2.7 (or later) to apply the security patch. Verify that no unauthorized mining processes are running on affected systems.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-20210 — 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-20210 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