dbcve.org
QtsOperating system · Qnap

CVE-2020-2490

HIGH · 7.2 CVSS v3.1 Published 2020-11-16
Fix available
A fix is available. Upgrade to 4.4.3.1421 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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
If exploited, the command injection vulnerability could allow remote attackers to execute arbitrary commands. This issue affects: QNAP Systems Inc. QTS versions prior to 4.4.3.1421 on build 20200907.

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 (network-attached storage operating system) affecting versions prior to 4.4.3.1421 on build 20200907. The vulnerability allows remote attackers to execute arbitrary commands on the affected system by injecting malicious commands through unsanitized input that gets passed to the system shell.

MitigationUpdate QNAP QTS to version 4.4.3.1421 or later on build 20200907. Minimize network exposure to the NAS device until the patch is applied.

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

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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. Confirm the device is running QNAP QTS
    Access the QTS admin interface (usually via web browser to the device's IP) and check the login page or System Settings > System Information. QTS is the Linux-based operating system for QNAP NAS devices.
    Affected if The device is not a QNAP NAS running QTS - different products are not affected by this CVE.
  2. Check the QTS version number
    In the QTS admin panel, navigate to Control Panel > System > System Information > System Status. The version is displayed as something like '4.4.x.x'. Note the exact version number shown.
    Affected if The version is lower than 4.4.3.1421, indicating the system is running a vulnerable version.
  3. Check the QTS build number
    In System Information, look for the build number or date. The build is typically displayed as 'Build 20200907' or a similar date code.
    Affected if The build is earlier than 20200907, or the build date is before September 7, 2020.
  4. Verify version is below the patched release
    Compare your installed version (from step 2) and build (from step 3) against the patched version 4.4.3.1421 on build 20200907. If both the version number and build date are lower, the system is vulnerable.
    Affected if Version is less than 4.4.3.1421 OR the build is earlier than 20200907 - either condition indicates vulnerability.
  5. Determine if the QTS web interface is network-accessible
    Check if port 8080 or 443 (the QTS admin ports) are exposed to the internet or untrusted networks. This can be done via router port forwarding rules, firewall configuration, or external port scanning of the public IP.
    Affected if The QTS admin interface is directly accessible from the internet - this command injection can be exploited remotely over the network.

If the device runs QNAP QTS with version lower than 4.4.3.1421 or build earlier than 20200907, and the QTS admin interface is network-accessible, the system is vulnerable to remote command injection via CVE-2020-2490.

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.1421 or later
Fixed in 4.4.3.1421
Interim mitigation

Update QNAP QTS to version 4.4.3.1421 or later on build 20200907. Minimize network exposure to the NAS device until the patch is applied.

Fix this in Qts Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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