dbcve.org
Qvr EliteApplication · Qnap

CVE-2021-38682

CRITICAL · 9.8 CVSS v3.1 Published 2022-01-14
Fix available
A fix is available. Upgrade to 2.1.3.0 / 2.1.4.0 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
A stack buffer overflow vulnerability has been reported to affect QNAP device running QVR Elite, QVR Pro, QVR Guard. If exploited, this vulnerability allows attackers to execute arbitrary code. We have already fixed this vulnerability in the following versions of QVR Elite, QVR Pro, QVR Guard: QuTS hero h5.0.0: QVR Elite 2.1.4.0 (2021/12/06) and later QuTS hero h4.5.4: QVR Elite 2.1.4.0 (2021/12/06) and later QTS 5.0.0: QVR Elite 2.1.4.0 (2021/12/06) and later QTS 4.5.4: QVR Elite 2.1.4.0 (2021/12/06) and later QTS 4.5.4: QVR Pro 2.1.3.0 (2021/12/06) and later QTS 5.0.0: QVR Pro 2.1.3.0 (2021/12/06) and later QTS 4.5.4: QVR Guard 2.1.3.0 and later QTS 5.0.0: QVR Guard 2.1.3.0 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 stack buffer overflow vulnerability in QNAP QVR Elite, QVR Pro, and QVR Guard allows remote attackers to execute arbitrary code without authentication due to improper bounds checking in stack memory operations. This critical flaw affects QNAP surveillance/NVR systems and can be exploited over the network.

MitigationUpgrade affected QNAP devices to the patched versions: QVR Elite 2.1.4.0 or later, QVR Pro 2.1.3.0 or later, QVR Guard 2.1.3.0 or later, applied to the corresponding QTS or QuTS hero firmware versions.

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
Qvr EliteApplication
Affected:< 2.1.4.0
Qvr GuardApplication
Affected:< 2.1.3.0
Qvr ProApplication
Affected:< 2.1.3.0

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.1/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. Identify installed QVR application
    Log into QTS/QuTS hero admin interface and navigate to App Center to find installed QVR surveillance applications (QVR Elite, QVR Pro, or QVR Guard)
    Affected if Any of these three QVR applications are installed on the device
  2. Check QVR Elite version
    In QTS App Center, click on QVR Elite and view the version information. Compare against 2.1.4.0
    Affected if Version is lower than 2.1.4.0 (for example 2.1.3.0 or earlier)
  3. Check QVR Pro version
    In QTS App Center, click on QVR Pro and view the version information. Compare against 2.1.3.0
    Affected if Version is lower than 2.1.3.0 (for example 2.1.2.0 or earlier)
  4. Check QVR Guard version
    In QTS App Center, click on QVR Guard and view the version information. Compare against 2.1.3.0
    Affected if Version is lower than 2.1.3.0 (for example 2.1.2.0 or earlier)
  5. Verify QVR network exposure
    Check if the QVR service ports (default 8080, 8081, or custom surveillance ports) are exposed to untrusted networks or the internet via router firewall rules
    Affected if QVR management or streaming ports are accessible from untrusted networks without VPN or authentication barriers

The system is affected if any QVR Elite version is below 2.1.4.0, or QVR Pro/QVR Guard versions are below 2.1.3.0, and the surveillance service is network-accessible.

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 2.1.3.0 / 2.1.4.0 or later
Fixed in 2.1.3.02.1.4.0
Interim mitigation

Upgrade affected QNAP devices to the patched versions: QVR Elite 2.1.4.0 or later, QVR Pro 2.1.3.0 or later, QVR Guard 2.1.3.0 or later, applied to the corresponding QTS or QuTS hero firmware versions.

Recommended fix High confidence

QVR Elite 2.1.4.0 or later / QVR Pro 2.1.3.0 or later / QVR Guard 2.1.3.0 or later

  1. Log into the QNAP device as an administrator
  2. Navigate to App Center or the specific QVR application (QVR Elite, QVR Pro, or QVR Guard)
  3. Check the current version of the installed QVR application
  4. Update the QVR application to version 2.1.4.0 or later for QVR Elite, or version 2.1.3.0 or later for QVR Pro/QVR Guard
  5. Verify the update was successful by checking the application version in the QNAP interface
  6. Restart the QVR service if prompted to ensure the patched version is fully operational
Caveat Review QNAP release notes for any specific migration requirements or compatibility considerations before upgrading

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

Fix this in Qvr Elite Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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