dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 22 Jun 2022. Known ransomware use
QtsOperating system · Qnap

CVE-2019-7193

CRITICAL · 9.8 CVSS v3.1 Published 2019-12-05
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
In the wild Ransomware Public exploit 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 improper input validation vulnerability allows remote attackers to inject arbitrary code to the system. 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 · high confidence

CVE-2019-7193 is an improper input validation vulnerability in QNAP QTS (Network Attached Storage operating system) that allows remote attackers to inject arbitrary code via unsanitized input fields. The vulnerability stems from the application failing to properly validate or sanitize user-supplied data before processing it, enabling remote code execution on affected QNAP devices.

MitigationApply the vendor-recommended fix by updating QNAP QTS to the latest version. This is a critical severity vulnerability (CVSS 9.8) requiring immediate remediation due to the potential for complete system compromise through remote code injection.

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.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= 4.3.6.1013= 4.3.6.1033= 4.4.1.0948= 4.4.1.0949= 4.4.1.0978

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. Check QTS firmware version
    Log into the QNAP NAS admin interface and navigate to Control Panel > System > Firmware Update, or run 'getsysinfo' via QNAP CLI to retrieve the installed QTS version.
    Affected if The installed version matches one of the following: 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, 4.3.6.1013, 4.3.6.1033, 4.4.1.0948, 4.4.1.0949, or 4.4.1.0978
  2. Verify QTS web server is accessible
    Confirm that the QNAP administrative web interface (port 8080 or 443) is exposed to the network. This vulnerability is exploitable without authentication, meaning any reachable web request can trigger it.
    Affected if The QTS web interface is reachable from a network where an attacker could send malicious requests.

If your QNAP device runs any of the listed QTS versions and has its web interface accessible on the network, you are affected by this vulnerability.

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

Apply the vendor-recommended fix by updating QNAP QTS to the latest version. This is a critical severity vulnerability (CVSS 9.8) requiring immediate remediation due to the potential for complete system compromise through remote code injection.

Recommended fix Moderate confidence

Update QTS to the latest available stable release (QNAP recommends updating to their latest versions beyond the affected 4.3.6.x builds)

  1. Log in to the QNAP NAS administrative interface
  2. Navigate to Control Panel > System > Firmware Update
  3. Ensure the NAS is connected to the internet
  4. Click 'Check for Update' to identify available QTS updates
  5. Backup all critical data on the NAS before proceeding with the update
  6. Apply the latest QTS firmware update available
  7. After the update completes, verify the QTS version has changed from the affected versions (4.3.6.0895, 4.3.6.0907, 4.3.6.0923, 4.3.6.0944)
  8. Restart the NAS if prompted to ensure all security patches take effect
Caveat Standard firmware update risks apply - review QNAP release notes for any configuration or feature changes before proceeding

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

Fix this in Qts Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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-2019-7193 — 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-7193 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