dbcve.org
QtsOperating system · Qnap

CVE-2017-13067

CRITICAL · 9.8 CVSS v3.0 Published 2017-09-14
Fix available
A fix is available. Upgrade to after 4.3.3.0299 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
QNAP has patched a remote code execution vulnerability affecting the QTS Media Library in all versions prior to QTS 4.2.6 build 20170905 and QTS 4.3.3.0299 build 20170901. This particular vulnerability allows a remote attacker to execute commands on a QNAP NAS using a transcoding service on port 9251. A remote user does not require any privileges to successfully execute an attack.

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

Unauthenticated remote code execution vulnerability in QNAP QTS Media Library transcoding service (port 9251). Attackers can execute arbitrary commands on affected NAS devices without any credentials due to improper input validation in the transcoding functionality.

MitigationUpdate QTS firmware to version 4.2.6 build 20170905 or later, or version 4.3.3.0299 build 20170901 or later. If patching is not immediately possible, disable the transcoding service or block external access to port 9251 at the network perimeter.

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.2.0, <= 4.2.6>= 4.3.0, <= 4.3.3.0299

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
    Log into the QNAP admin interface and navigate to Control Panel > System > Firm Update, or run 'qnpm version' via SSH. The version is typically displayed on the dashboard or in System Information.
    Affected if The installed version is 4.2.0 through 4.2.6, or 4.3.0 through 4.3.3.0299 (specifically builds before 20170905 for 4.2.x or before 20170901 for 4.3.x).
  2. Verify transcoding service is enabled
    In QTS admin, go to Control Panel > Applications > Media Library, or check if the 'Multimedia Console' or transcoding-related services are active. On the command line, run 'ps | grep -i trans' or check the Multimedia Console status.
    Affected if The transcoding or Media Library service is currently enabled on the system.
  3. Confirm port 9251 is listening
    Run 'netstat -tuln | grep 9251' or 'ss -tuln | grep 9251' via SSH to check if the transcoding service port is bound and listening.
    Affected if Port 9251 is open and listening, indicating the vulnerable transcoding service is exposed.
  4. Check network exposure of port 9251
    Review firewall rules or port forwarding settings to determine if port 9251 is accessible from external networks. Run an external port scan or check the QNAP firewall configuration in Control Panel > Security > Firewall.
    Affected if Port 9251 is exposed to untrusted networks or the internet without proper access controls.

A system is affected if it runs QTS versions 4.2.0-4.2.6 or 4.3.0-4.3.3.0299 with the transcoding service enabled and port 9251 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.0299
Interim mitigation

Update QTS firmware to version 4.2.6 build 20170905 or later, or version 4.3.3.0299 build 20170901 or later. If patching is not immediately possible, disable the transcoding service or block external access to port 9251 at the network perimeter.

Recommended fix High confidence

QTS 4.2.6 build 20170905 or QTS 4.3.3.0299 build 20170901 (depending on major version branch)

  1. Log into the QNAP NAS administrative interface (QTS)
  2. Navigate to Control Panel > System > Firmware Update
  3. Check the current QTS version under System Information
  4. If running QTS 4.2.x (versions 4.2.0-4.2.6), update to QTS 4.2.6 build 20170905 or later
  5. If running QTS 4.3.x (versions 4.3.0-4.3.3.0299), update to QTS 4.3.3.0299 build 20170901 or later
  6. Use the 'Check for Update' feature to download and install the appropriate firmware
  7. Restart the NAS after the update completes
  8. Verify the new build number matches or exceeds the fixed versions (20170905 for 4.2.6 or 20170901 for 4.3.3.0299)
Caveat firmware updates may temporarily disrupt services; verify backup before updating; some legacy applications may not be compatible with newer QTS versions

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

Fix this in Qts Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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