dbcve.org
QtsOperating system · Qnap

CVE-2018-19957

MEDIUM · 6.1 CVSS v3.1 Published 2021-09-10
Fix available
A fix is available. Upgrade to 4.5.4.1715 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 vulnerability involving insufficient HTTP security headers has been reported to affect QNAP NAS running QTS, QuTS hero, and QuTScloud. This vulnerability allows remote attackers to launch privacy and security attacks. We have already fixed this vulnerability in the following versions: QTS 4.5.4.1715 build 20210630 and later QuTS hero h4.5.4.1771 build 20210825 and later QuTScloud c4.5.6.1755 build 20210809 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

Insufficient HTTP security headers in QNAP NAS firmware (QTS, QuTS hero, QuTScloud) allows remote attackers to exploit missing security headers like X-Frame-Options, X-Content-Type-Options, or Content-Security-Policy, leading to privacy and security attacks such as clickjacking, MIME sniffing, or XSS.

MitigationUpgrade affected QNAP NAS devices to QTS 4.5.4.1715 (build 20210630+), QuTS hero h4.5.4.1771 (build 20210825+), or QuTScloud c4.5.6.1755 (build 20210809+) to implement proper HTTP security headers.

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.5.4.1715
Quts HeroOperating system
Affected:< h4.5.4.1771
QutscloudOperating system
Affected:< c4.5.6.1755

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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. Identify QNAP firmware version
    Log into the QNAP admin interface (QTS/QuTS hero/QuTScloud) and navigate to Control Panel > System > Firmware Update, or run 'getconf' via SSH to retrieve the build number and version
    Affected if The installed version is below QTS 4.5.4.1715, QuTS hero h4.5.4.1771, or QuTScloud c4.5.6.1755
  2. Check for X-Frame-Options header
    Send an HTTP request to the NAS web interface (e.g., using curl -I https://[nas-ip]) and inspect the response headers for the presence of X-Frame-Options
    Affected if The X-Frame-Options header is missing from HTTP responses, exposing the device to clickjacking attacks
  3. Check for X-Content-Type-Options header
    Send an HTTP request to the NAS and examine response headers for X-Content-Type-Options with value 'nosniff'
    Affected if The X-Content-Type-Options header is missing, allowing MIME sniffing vulnerabilities
  4. Check for Content-Security-Policy header
    Inspect HTTP response headers from the NAS web interface for the Content-Security-Policy header
    Affected if The Content-Security-Policy header is missing, allowing potential XSS attacks via inline scripts or untrusted content sources

A user is affected if their QNAP device runs firmware versions below 4.5.4.1715 (QTS), h4.5.4.1771 (QuTS hero), or c4.5.6.1755 (QuTScloud) AND any of the three security headers (X-Frame-Options, X-Content-Type-Options, Content-Security-Policy) are absent from HTTP responses.

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.5.4.1715 or later
Fixed in 4.5.4.1715
Interim mitigation

Upgrade affected QNAP NAS devices to QTS 4.5.4.1715 (build 20210630+), QuTS hero h4.5.4.1771 (build 20210825+), or QuTScloud c4.5.6.1755 (build 20210809+) to implement proper HTTP security headers.

Recommended fix High confidence

QTS 4.5.4.1715 (build 20210630), QuTS hero h4.5.4.1771 (build 20210825), or QuTScloud c4.5.6.1755 (build 20210809) depending on product

  1. 1. Log into the QNAP NAS admin interface (QTS, QuTS hero, or QuTScloud).
  2. 2. Navigate to Control Panel > System > Firmware Update (or similar location depending on version).
  3. 3. Check the current firmware version and build number to confirm it is below the fixed version.
  4. 4. Use the built-in firmware update feature to check for and install the appropriate update: For QTS, install version 4.5.4.1715 (build 20210630) or later; For QuTS hero, install version h4.5.4.1771 (build 20210825) or later; For QuTScloud, install version c4.5.6.1755 (build 20210809) or later.
  5. 5. After the update completes, verify the firmware version has been successfully upgraded.
  6. 6. Confirm the HTTP security headers vulnerability is remediated by checking that proper X-Frame-Options or Content-Security-Policy headers are now present in HTTP responses.
Caveat Standard firmware update best practices apply - backup critical data before updating

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

Fix this in Qts Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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