QtsOperating system · Qnap

CVE-2018-19944

HIGH · 7.5 CVSS v3.1 Published 2020-12-31
Fix available
A fix is available. Upgrade to 4.4.3.1354 or later.
See remediation →
84/100
Remediation priority · High
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 cleartext transmission of sensitive information vulnerability has been reported to affect certain QTS devices. If exploited, this vulnerability allows a remote attacker to gain access to sensitive information. QNAP have already fixed this vulnerability in the following versions: 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 · moderate confidence

A cleartext transmission vulnerability in QNAP QTS allows remote attackers to intercept sensitive information due to unencrypted communications between the device and clients or other systems.

MitigationUpdate QNAP QTS firmware to version 4.4.3.1354 build 20200702 or later to remediate the cleartext transmission vulnerability.

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

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 QNAP QTS is in use
    Access the QNAP admin web interface (typically https://<device-ip>:8080) or log in via SSH. If the QNAP management interface is present, QTS is installed.
    Affected if The device runs QNAP QTS firmware.
  2. Identify installed QTS version
    In the QTS admin interface, go to Control Panel > System > Firmware Update, or check the System Information page. The firmware version and build number will be displayed (e.g., 4.4.3.1354 or 4.4.1.1905).
    Affected if The displayed version is below 4.4.3.1354.
  3. Check build number if version appears ambiguous
    If the version number shows 4.4.3.x but the exact build is unclear, locate the full build number in System > About > Firmware Version. The vulnerable builds are those earlier than build 20200702.
    Affected if The build number is earlier than 20200702.
  4. Inspect network services for unencrypted access
    In QTS Control Panel, review Network Services (FTP, Telnet, Web Server, etc.). Check if services are configured to allow cleartext/unencrypted connections (e.g., FTP enabled, Telnet enabled, HTTP admin access without HTTPS enforcement).
    Affected if Any critical service (admin interface, file transfers, remote access) is accessible over unencrypted HTTP/FTP/Telnet rather than only encrypted HTTPS/SFTP/SSH.
  5. Verify admin interface encryption settings
    Go to Control Panel > System > Security > SSL Certificate and verify that Force SSL/TLS is enabled, and that the admin web interface redirects HTTP to HTTPS.
    Affected if Force SSL/TLS is disabled or the admin interface accepts unencrypted HTTP connections.

A user is affected if their QNAP QTS firmware version is below 4.4.3.1354 (build 20200702) AND unencrypted network services or cleartext admin access are enabled on the device.

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.

From vendor data
Upgrade available Upgrade to 4.4.3.1354 or later
Fixed in 4.4.3.1354
Interim mitigation

Update QNAP QTS firmware to version 4.4.3.1354 build 20200702 or later to remediate the cleartext transmission vulnerability.

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-2018-19944 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-19944 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