dbcve.org
QtsOperating system · Qnap

CVE-2017-17028

CRITICAL · 9.8 CVSS v3.0 Published 2017-12-21
Fix available
A fix is available. Upgrade to after 4.3.3.0378 or later.
See remediation →
100/100
Remediation priority · Urgent
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
A buffer overflow vulnerability in external device function in QNAP QTS version 4.2.6 build 20171026, 4.3.3.0378 build 20171117, 4.3.4.0387 (Beta 2) build 20171116 and earlier could allow remote attackers to execute arbitrary code on NAS devices.

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

A buffer overflow vulnerability exists in the external device function of QNAP QTS firmware versions 4.2.6 build 20171026, 4.3.3.0378 build 20171117, 4.3.4.0387 Beta 2 build 20171116 and earlier. The overflow allows remote attackers to execute arbitrary code on affected NAS devices due to insufficient bounds checking in the external device handling code.

MitigationApply the vendor-supplied QNAP QTS firmware update to remediate this vulnerability. If updates are unavailable, consider network segmentation to limit exposure of the NAS management interfaces to untrusted networks.

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
QtsOperating system
Affected:<= 4.3.3.0378= 4.3.4.0358= 4.3.4.0370= 4.3.4.0372= 4.3.4.0374= 4.3.4.0387

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
High
Availability
High

CVSS:3.0/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 checks

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

  1. Check QTS firmware version
    Access the QNAP admin interface (http://[NAS-IP]) and navigate to Control Panel > System > Firmware Update, or run 'ver' command via SSH to retrieve the installed QTS version and build number
    Affected if The installed version is 4.2.6 build 20171026 or earlier, 4.3.3.0378 or earlier, or exactly 4.3.4.0358, 4.3.4.0370, 4.3.4.0372, 4.3.4.0374, or 4.3.4.0387
  2. Verify external device function is enabled
    Log into QTS admin panel and navigate to Control Panel > External Device to check if any external device functions (USB, eSATA, or external storage devices) are configured or connected
    Affected if External device handling is actively configured or external devices are attached to the NAS
  3. Confirm management interface exposure
    Check network accessibility of the QTS web admin interface (port 8080 or 443) and verify if it is exposed to untrusted networks
    Affected if The NAS management interface is reachable from networks outside the local trusted network

You are affected if your QNAP device runs QTS version 4.2.6 build 20171026 or earlier, 4.3.3.0378 or earlier, or any of the specific versions 4.3.4.0358/0370/0372/0374/0387, AND the external device function is enabled on the device.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 4.3.3.0378
Interim mitigation

Apply the vendor-supplied QNAP QTS firmware update to remediate this vulnerability. If updates are unavailable, consider network segmentation to limit exposure of the NAS management interfaces to untrusted networks.

Recommended fix Moderate confidence

QTS 4.3.4.0387 or later (the fixed release that addresses this buffer overflow vulnerability)

  1. 1. Log into the QNAP QTS administrative interface
  2. 2. Navigate to Control Panel > System > Firmware Update
  3. 3. Check for available firmware updates
  4. 4. If an update is available, backup all critical data on the NAS before proceeding
  5. 5. Run the firmware update to install the latest QTS version
Caveat firmware updates on QNAP NAS devices may require downtime and should be performed during maintenance windows; ensure backups are verified before updating

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Qts Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-17028 — 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-17028 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