CVE-2017-6360
Public exploit available. Not confirmed exploited in the wild yet. A vendor fix is available.
What to do
The vendor has published a fix. Version details are below where the sources state them.
- Qnap QtsAffected: ≤ 4.2.4Upgrade to: after 4.2.4Stated by: NVD
Versions as the sources state them. Full version matrix after sign-in
Steps
Written by AI from the record- Check your QNAP NAS for the installed QTS version and Build number; confirm whether it is earlier than 4.2.4 Build 20170313.
- If you are affected, upgrade QTS to 4.2.4 Build 20170313 or later using QNAP’s release notes.
- Apply any QNAP “recommendations” or workaround guidance linked by QNAP support (as an interim measure if you can’t upgrade immediately).
- After upgrading, verify the NAS is reachable only as intended (avoid unnecessary exposure) and review access/admin activity for suspicious logins.
What it is
From the CVE record
QNAP QTS before 4.2.4 Build 20170313 allows attackers to gain administrator privileges and obtain sensitive information via unspecified vectors.
In plain language
Written by AI from the recordQNAP QTS versions before 4.2.4 (Build 20170313) have a serious flaw that can let an attacker take administrator control and view sensitive data; if you run this NAS software, you should act now.
QNAP QTS before 4.2.4 Build 20170313 has an unspecified input-handling weakness (CWE-78) that enables remote attackers to gain administrator privileges and obtain sensitive information; public exploit code is available.
If you're affected
- Full administrator takeover
- Sensitive data exposure
- Account and configuration compromise
- Service disruption risk
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
1 source with a proof of concept or module.
Exploit links, PoCs and Metasploit modules after sign-in- EPSS
66% chance of exploitation activity in the next 30 days, which ranks it in the 99th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
A public exploit existed 67 days before the patch.
- EPSS band changemoderate → highepss band change
- EPSS band changehigh → moderateepss band change
- EPSS band changemoderate → highepss band change
- EPSS band changehigh → moderateepss band change
- EPSS band changemoderate → highepss band change
- EPSS band changehigh → moderate
Affected products
And 1 more affected product. See all after sign-in
Technical detail
CVSS 3.0 vector
Open in the CVSS calculatorCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Scored 9.8 by NVD.
How it is reached
- Attack Vector NetworkExploitable remotely over the network without any special conditions
- Attack Complexity LowNo special conditions — the attack can be reliably reproduced
- Privileges Required NoneNo authentication required — anyone can exploit this
- User Interaction NoneNo user interaction needed — fully automated exploitation
Scope
- Scope UnchangedImpact is limited to the vulnerable component itself
Impact if exploited
- Confidentiality HighTotal information disclosure — all data in the component is compromised
- Integrity HighTotal loss of integrity — attacker can modify any data in the component
- Availability HighTotal denial of service — the component is completely unavailable
Weaknesses
ATT&CK techniques
Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.
Sources
References in the record
And 7 more references. See all after sign-in
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Qts, not every advisory. This one: public exploit.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI