dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 11 Jan 2024.
Qvr FirmwareOperating system · Qnap

CVE-2023-47565

HIGH · 8.8 CVSS v3.1 Published 2023-12-08
Fix available
A fix is available. Upgrade to 5.0.0 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS 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
An OS command injection vulnerability has been found to affect legacy QNAP VioStor NVR models running QVR Firmware 4.x. If exploited, the vulnerability could allow authenticated users to execute commands via a network. We have already fixed the vulnerability in the following versions: QVR Firmware 5.0.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

OS command injection vulnerability in QNAP VioStor NVR devices running QVR Firmware 4.x allows authenticated users to inject and execute arbitrary operating system commands through the web interface or network service, potentially leading to full system compromise.

MitigationUpgrade QVR Firmware to version 5.0.0 or later. If immediate upgrade is not feasible, restrict network access to the NVR management interface to trusted IP addresses and ensure strong authentication controls are in place.

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 FirmwareOperating system
Affected:>= 4.0.0, < 5.0.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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 QVR Firmware version via web interface
    Log into the QNAP VioStor NVR admin web interface and navigate to System Settings > Firmware Update or System Status to view the installed QVR Firmware version
    Affected if The displayed version is 4.x (greater than or equal to 4.0.0 but less than 5.0.0)
  2. Identify QVR Firmware version via CLI
    Access the device via SSH or serial console and run the command: cat /etc/config/qvr_version or cat /mnt/HDA_ROOT/.config/version to read the firmware version
    Affected if The version output shows 4.x (greater than or equal to 4.0.0 but less than 5.0.0)
  3. Confirm QVR service is running
    Via SSH, run: ps aux | grep -i qvr or systemctl status qvr to verify the QVR application service is active
    Affected if The QVR service process is running and the version from step 1 or 2 is in the affected range
  4. Verify web management interface accessibility
    Attempt to access the NVR web portal via HTTP/HTTPS on the device IP address (typically ports 80, 443, or 8080) to confirm the web interface is reachable
    Affected if The web interface responds and the firmware version is in the affected range (this confirms the attack surface exists)

You are affected if your QNAP VioStor NVR is running QVR Firmware version 4.0.0 through 4.x (any version below 5.0.0) with the QVR web interface accessible on the network.

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 5.0.0 or later
Fixed in 5.0.0
Interim mitigation

Upgrade QVR Firmware to version 5.0.0 or later. If immediate upgrade is not feasible, restrict network access to the NVR management interface to trusted IP addresses and ensure strong authentication controls are in place.

Recommended fix High confidence

QVR Firmware 5.0.0 or later

  1. 1. Identify the specific QNAP VioStor NVR device running QVR Firmware 4.x
  2. 2. Backup all configuration data and recordings if possible
  3. 3. Access the QNAP device management interface
  4. 4. Navigate to QVR Firmware settings and check current version (should be >= 4.0.0 and < 5.0.0)
  5. 5. Initiate firmware upgrade to QVR Firmware 5.0.0 or later
  6. 6. Verify the upgrade completed successfully
  7. 7. Confirm the new firmware version is 5.0.0 or higher
Caveat Major version upgrade from 4.x to 5.x may have configuration or compatibility changes - review QNAP release notes before upgrading

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

Fix this in Qvr Firmware Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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