dbcve.org
QtsOperating system · Qnap

CVE-2018-0730

CRITICAL · 9.8 CVSS v3.1 Published 2019-12-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
This command injection vulnerability in File Station allows attackers to execute commands on the affected device. To fix the vulnerability, QNAP recommend updating QTS to their latest versions.

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 confidence

This is a command injection vulnerability in QNAP's File Station application that allows remote attackers to execute arbitrary OS commands on affected QNAP Network Attached Storage (NAS) devices. The vulnerability stems from insufficient input sanitization in the File Station web interface, enabling attackers to inject malicious commands through crafted requests.

MitigationUpdate QTS to the latest version as recommended by QNAP to patch the command injection vulnerability. This is a critical-severity issue requiring immediate remediation.

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.6= 4.3.3.0868= 4.3.3.0998= 4.3.4.0899= 4.3.4.1029= 4.3.6.0895= 4.3.6.0907= 4.3.6.0923= 4.3.6.0944= 4.3.6.0959= 4.3.6.0979= 4.3.6.0993

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.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 checks

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

  1. Verify this is a QNAP NAS device
    Check the device model, hostname, or access the web administration interface at port 8080 or 443. QNAP NAS devices typically show a QTS login page.
    Affected if The device is not a QNAP NAS running QTS - if so, this CVE does not apply.
  2. Identify the installed QTS version
    Log into QTS admin interface and navigate to Control Panel > System > System Status, or run the command 'getsysinfo' via SSH. The version will appear as something like 4.3.6.0998.
    Affected if The QTS version matches exactly one of the following build numbers: 4.2.6, 4.3.3.0868, 4.3.3.0998, 4.3.4.0899, 4.3.4.1029, 4.3.6.0895, 4.3.6.0907, 4.3.6.0923, 4.3.6.0944, 4.3.6.0959, 4.3.6.0979, or 4.3.6.0993.
  3. Confirm File Station is accessible
    Check if File Station web interface is enabled by navigating to QTS Control Panel > Applications > File Station, or attempt to access it directly at '/fileStation/' on the NAS IP.
    Affected if File Station is enabled and accessible - the command injection flaw requires File Station to be available.
  4. Verify File Station is reachable over the network
    Check that the QNAP admin interface (and thus File Station) is exposed to network requests. This may be confirmed by reviewing firewall rules or network access settings in Control Panel > System > Security.
    Affected if File Station port is open to network users beyond the local administrative network.

You are affected if this is a QNAP NAS running QTS with a version matching one of the 12 specific build numbers listed AND File Station is enabled and 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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update QTS to the latest version as recommended by QNAP to patch the command injection vulnerability. This is a critical-severity issue requiring immediate remediation.

Recommended fix Moderate confidence

QTS latest version (QTS 4.2.6 build 20181026 or later for the 4.2.x branch; QTS 4.3.3 build 20181108 or later for the 4.3.3 branch; QTS 4.3.4 build 20181108 or later for the 4.3.4 branch)

  1. 1. Log into the QNAP QTS admin interface as an administrator
  2. 2. Navigate to Control Panel > System > Firmware Update
  3. 3. Click 'Check for Update' to identify the latest available QTS version
  4. 4. If a newer version is available, click 'Update Now' to download and install it
  5. 5. Wait for the update process to complete - do not power off the NAS during this process
  6. 6. After the system reboots, verify the QTS version has been updated successfully
  7. 7. Confirm that File Station is now running the patched version
Caveat Standard QTS firmware update risks apply - ensure backups are current and power supply is stable during upgrade

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

Fix this in Qts Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,120
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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