dbcve.org
Nas Proxy ServerApplication · Qnap

CVE-2021-34360

HIGH · 8.8 CVSS v3.1 Published 2022-05-26
Fix available
A fix is available. Upgrade to 1.4.2 / 1.4.3 or later.
See remediation →
95/100
Remediation priority · Urgent
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 cross-site request forgery (CSRF) vulnerability has been reported to affect QNAP device running Proxy Server. If exploited, this vulnerability allows remote attackers to inject malicious code. We have already fixed this vulnerability in the following versions of Proxy Server: QTS 4.5.x: Proxy Server 1.4.2 ( 2021/12/30 ) and later QuTS hero h5.0.0: Proxy Server 1.4.3 ( 2022/01/18 ) and later QuTScloud c4.5.6: Proxy Server 1.4.2 ( 2021/12/30 ) 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 · high confidence

A cross-site request forgery (CSRF) vulnerability in QNAP Proxy Server allows remote attackers to inject malicious code by tricking authenticated users into executing unintended requests. The vulnerability affects QTS 4.5.x, QuTS hero h5.0.0, and QuTScloud c4.5.6 deployments running Proxy Server versions prior to the patched releases.

MitigationUpdate Proxy Server to version 1.4.2 or later (QTS/QuTScloud) or 1.4.3 or later (QuTS hero) as specified. Additionally, implement anti-CSRF tokens in the application to prevent future CSRF attacks.

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
Nas Proxy ServerApplication
Affected:>= 1.4.0, < 1.4.2>= 1.4.0, < 1.4.3

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Identify NAS firmware version
    Access the QNAP admin console and navigate to Control Panel > System > Firmware Update, or run 'getcfg system version' via SSH. Look for the QTS, QuTS hero, or QuTScloud version number.
    Affected if The firmware is QTS 4.5.x, QuTS hero h5.0.0, or QuTScloud c4.5.6.
  2. Verify Proxy Server is installed
    Log into the QNAP admin console and check Applications > myQNAPcloud > Proxy Server, or look for the Proxy Server package in the App Center.
    Affected if Proxy Server appears in the installed applications list.
  3. Determine Proxy Server version
    In the Proxy Server application settings or App Center details, locate the version number field. It is typically displayed as 'Proxy Server x.x.x'.
    Affected if The displayed version is 1.4.0, 1.4.1, or 1.4.2.
  4. Confirm Proxy Server is enabled
    In the Proxy Server application interface, check the status indicator or navigate to the enable/disable toggle to see if the service is currently running.
    Affected if Proxy Server status shows as 'Running' or 'Enabled' and the version is in the affected range.

A user is affected if their NAS runs QTS 4.5.x, QuTS hero h5.0.0, or QuTScloud c4.5.6 with Proxy Server enabled and the Proxy Server version is 1.4.0 through 1.4.1 (QTS/QuTScloud) or 1.4.0 through 1.4.2 (QuTS hero).

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 1.4.2 / 1.4.3 or later
Fixed in 1.4.21.4.3
Interim mitigation

Update Proxy Server to version 1.4.2 or later (QTS/QuTScloud) or 1.4.3 or later (QuTS hero) as specified. Additionally, implement anti-CSRF tokens in the application to prevent future CSRF attacks.

Recommended fix High confidence

QTS 4.5.x: Proxy Server 1.4.2+; QuTScloud c4.5.6: Proxy Server 1.4.2+; QuTS hero h5.0.0: Proxy Server 1.4.3+

  1. 1. Identify the QNAP NAS model and the operating system version (QTS 4.5.x, QuTS hero h5.0.0, or QuTScloud c4.5.6)
  2. 2. Log into QTS/QuTScloud/QuTS hero as administrator
  3. 3. Navigate to App Center > myQNAPcloud
  4. 4. Locate Proxy Server in the installed applications
  5. 5. Check the current version of Proxy Server (must be >= 1.4.0 to be vulnerable)
  6. 6. If running QTS 4.5.x or QuTScloud c4.5.6: Update Proxy Server to version 1.4.2 or later
  7. 7. If running QuTS hero h5.0.0: Update Proxy Server to version 1.4.3 or later
  8. 8. Verify the update was successful by checking the Proxy Server version again

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

Fix this in Nas Proxy Server 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-2021-34360 — 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-2021-34360 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