dbcve.org
Quts HeroOperating system · Qnap

CVE-2019-7198

CRITICAL · 9.8 CVSS v3.1 Published 2020-12-10
Fix available
A fix is available. Upgrade to 4.4.3.1354 / 4.5.1.1456 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
This command injection vulnerability allows attackers to execute arbitrary commands in a compromised application. QNAP have already fixed this vulnerability in the following versions of QTS and QuTS hero. QuTS hero h4.5.1.1472 build 20201031 and later QTS 4.5.1.1456 build 20201015 and later QTS 4.4.3.1354 build 20200702 and later

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

This is a command injection vulnerability in QNAP QTS and QuTS hero network-attached storage (NAS) firmware that allows remote attackers to execute arbitrary operating system commands by injecting malicious input into vulnerable parameters in the web interface.

MitigationUpgrade QNAP NAS devices to the patched versions: QuTS hero h4.5.1.1472 build 20201031, QTS 4.5.1.1456 build 20201015, or QTS 4.4.3.1354 build 20200702 or later. Prioritize external-facing NAS systems given the CVSS 9.8 severity.

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
Quts HeroOperating system
Affected:< h4.5.1.1472
QtsOperating system
Affected:< 4.4.3.1354< 4.5.1.1456

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. Identify QNAP firmware product type
    Access the QNAP admin web interface and locate the firmware/version information, typically shown on the login page or in Control Panel > System > System Information. Alternatively, SSH to the NAS and run: cat /etc/version
    Affected if The device is running QNAP QTS or QuTS hero firmware
  2. Check QuTS hero version
    If running QuTS hero, compare the displayed firmware version against the affected range: any build earlier than h4.5.1.1472 is vulnerable
    Affected if QuTS hero version is earlier than h4.5.1.1472
  3. Check QTS version
    If running QTS, compare the displayed firmware version against affected ranges: any build earlier than 4.5.1.1456 OR between 4.4.3.0000 and 4.4.3.1353 is vulnerable
    Affected if QTS version is earlier than 4.5.1.1456 or earlier than 4.4.3.1354
  4. Verify web interface exposure
    Determine if the QNAP web management interface (ports 8080 or 443) is accessible from external networks or untrusted VLANs
    Affected if The web interface is exposed to untrusted networks (the vulnerability is exploited through web interface parameters)

A user is affected if their QNAP NAS runs QTS version earlier than 4.4.3.1354 or earlier than 4.5.1.1456, or QuTS hero earlier than h4.5.1.1472, and the web 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 4.4.3.1354 / 4.5.1.1456 or later
Fixed in 4.4.3.13544.5.1.1456
Interim mitigation

Upgrade QNAP NAS devices to the patched versions: QuTS hero h4.5.1.1472 build 20201031, QTS 4.5.1.1456 build 20201015, or QTS 4.4.3.1354 build 20200702 or later. Prioritize external-facing NAS systems given the CVSS 9.8 severity.

Recommended fix High confidence

QTS 4.4.3.1354 (build 20200702) / QTS 4.5.1.1456 (build 20201015) / QuTS hero h4.5.1.1472 (build 20201031) depending on branch

  1. 1. Log into the QNAP admin interface (QTS or QuTS hero).
  2. 2. Navigate to Control Panel > System > Firmware Update.
  3. 3. Check the current firmware version under the System Information section.
  4. 4. Identify which firmware branch you are currently running (QTS 4.4.3, QTS 4.5.1, or QuTS hero h4.5.1).
  5. 5. If running QTS 4.4.3.x, upgrade to QTS 4.4.3.1354 (build 20200702) or later.
  6. 6. If running QTS 4.5.1.x, upgrade to QTS 4.5.1.1456 (build 20201015) or later.
  7. 7. If running QuTS hero h4.5.1.x, upgrade to h4.5.1.1472 (build 20201031) or later.
  8. 8. Use the 'Check for Update' feature to download and install the appropriate stable firmware release.
Caveat Review QNAP release notes before upgrading; firmware updates may require downtime and typically cannot be rolled back

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

Fix this in Quts Hero 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-2019-7198 — 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-2019-7198 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