dbcve.org
QtsOperating system · Qnap

CVE-2017-17031

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 password 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 in the password handling function of QNAP QTS allows remote attackers to overflow a buffer and execute arbitrary code on affected NAS devices. The vulnerability is exploitable without authentication due to insufficient bounds checking when processing password input.

MitigationApply vendor patches from QNAP for affected QTS versions (4.2.6, 4.3.3.0378, 4.3.4.0387 and earlier). If patches are unavailable, consider network segmentation or disabling remote access to the NAS administration interface.

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. Confirm the device is a QNAP NAS running QTS
    Access the web administration interface of the NAS (typically on port 8080 or 443). If the login page displays QNAP branding, the device is a QNAP NAS running QTS. Alternatively, access via SSH and check the system information.
    Affected if The device is a QNAP NAS with QTS web interface accessible over the network.
  2. Retrieve the installed QTS firmware version
    In the web admin interface, go to Control Panel > System > Firmware Update > Check Update History to view the current QTS version. Or via SSH, run the command 'qmgr -c "print_system_version"' or check the About page in the QTS interface.
    Affected if Unable to retrieve a QTS version number from the system.
  3. Compare the installed version against the affected list
    Compare the retrieved version number to the following affected versions: 4.3.3.0378 and earlier, 4.3.4.0358, 4.3.4.0370, 4.3.4.0372, 4.3.4.0374, 4.3.4.0387. Exact matches or lower versions are considered affected.
    Affected if The installed version is exactly 4.3.3.0378 or lower, OR exactly 4.3.4.0358, 4.3.4.0370, 4.3.4.0372, 4.3.4.0374, or 4.3.4.0387.
  4. Verify remote access to the QTS administration interface is enabled
    Check if the QTS web interface (HTTP/HTTPS on ports 80, 443, 8080, 8081) is accessible from external networks. In the web admin, go to Control Panel > System > General Settings > System Administration to review access settings.
    Affected if The QTS admin interface is accessible from untrusted networks (e.g., the internet).

The system is affected if it is a QNAP NAS running QTS version 4.3.4.0387 or lower (including specific point releases 4.3.4.0358, 0370, 0372, 0374), and the QTS web administration interface is network-accessible.

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 vendor patches from QNAP for affected QTS versions (4.2.6, 4.3.3.0378, 4.3.4.0387 and earlier). If patches are unavailable, consider network segmentation or disabling remote access to the NAS administration interface.

Recommended fix Moderate confidence

QTS 4.3.4.0387 (Beta 2) or earlier to the latest stable QTS 4.3.x or 4.4.x release available from QNAP

  1. 1. Log in to the QNAP QTS admin console.
  2. 2. Navigate to Control Panel > System > Firmware Update.
  3. 3. Check the current QTS version under the System Information section.
  4. 4. If the current version is 4.3.4.0387 (Beta 2) or earlier, proceed with the update.
  5. 5. Click 'Check for Update' to see if a newer stable firmware is available.
  6. 6. Download and install any available firmware updates that are newer than the affected versions.
  7. 7. After updating, verify the new QTS version is installed and the device is functioning normally.
Caveat firmware updates on QNAP NAS devices may require downtime and should be planned during maintenance windows

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

Fix this in Qts Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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