dbcve.org
HelpdeskApplication · Qnap

CVE-2018-0714

CRITICAL · 9.8 CVSS v3.0 Published 2018-08-13
Fix available
A fix is available. Upgrade to after 1.1.21 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
Command injection vulnerability in Helpdesk versions 1.1.21 and earlier in QNAP QTS 4.2.6 build 20180531, QTS 4.3.3 build 20180528, QTS 4.3.4 build 20180528 and their earlier versions could allow remote attackers to run arbitrary commands in the compromised application.

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

Command injection vulnerability in QNAP QTS Helpdesk component versions 1.1.21 and earlier allows remote unauthenticated attackers to execute arbitrary commands on the underlying operating system via specially crafted input vectors.

MitigationUpgrade Helpdesk to version 1.1.22 or later, or update QNAP QTS to patched builds that include the fixed Helpdesk component. If immediate patching is not possible, restrict network access to the Helpdesk interface.

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
HelpdeskApplication
Affected:<= 1.1.21

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.0/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 QNAP Helpdesk is installed
    Access QNAP QTS admin panel, go to App Center, and look for 'Helpdesk' application in the installed apps list. Alternatively, check for the Helpdesk web interface by accessing http(s)://[qnap-ip]:[port]/helpdesk.
    Affected if Helpdesk application appears in the QTS App Center or the Helpdesk web interface is accessible.
  2. Identify the Helpdesk version
    In QTS App Center, click on the Helpdesk app and view the version information displayed in the app details panel. Note the exact version number shown.
    Affected if The displayed version is 1.1.21 or any earlier version (e.g., 1.1.20, 1.1.19, etc.).
  3. Check QNAP QTS firmware version as secondary indicator
    In QTS, go to Control Panel > System > Firm Update, or check the System Information dashboard to view the QTS firmware version.
    Affected if QTS firmware is older than builds that incorporate the fixed Helpdesk 1.1.22 component (if known QTS build numbers apply to your model).
  4. Determine if Helpdesk is network-accessible
    Verify whether the Helpdesk web interface port is open to external networks or exposed via port forwarding. Check QTS Firewall rules in Control Panel > Security > Firewall for rules allowing external access to the Helpdesk port.
    Affected if The Helpdesk service (typically port 8080 or 443 for the web interface) is accessible from untrusted networks or the internet.

A system is affected if the QNAP Helpdesk component is installed and its version is 1.1.21 or earlier, or if the QTS firmware does not include the patched Helpdesk version 1.1.22.

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 a release after 1.1.21
Interim mitigation

Upgrade Helpdesk to version 1.1.22 or later, or update QNAP QTS to patched builds that include the fixed Helpdesk component. If immediate patching is not possible, restrict network access to the Helpdesk interface.

Recommended fix Moderate confidence

Helpdesk version 1.1.22 or later (latest available version from QNAP)

  1. 1. Log in to the QNAP QTS admin console as an administrator
  2. 2. Navigate to Helpdesk application settings
  3. 3. Check the current Helpdesk version under Application Manager or App Center
  4. 4. If the installed version is 1.1.21 or earlier, update to the latest available version from QNAP App Center
  5. 5. Alternatively, manually download the latest Helpdesk version from QNAP's download center and reinstall

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

Fix this in Helpdesk Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
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,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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