dbcve.org
QtsOperating system · Qnap

CVE-2024-21904

MEDIUM · 6.5 CVSS v3.1 Published 2024-09-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
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
A path traversal vulnerability has been reported to affect several QNAP operating system versions. If exploited, the vulnerability could allow users to read the contents of unexpected files and expose sensitive data via a network. We have already fixed the vulnerability in the following versions: QTS 5.1.7.2770 build 20240520 and later QuTS hero h5.1.7.2770 build 20240520 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 path traversal vulnerability in QNAP QTS and QuTS hero operating systems allows authenticated users to access files outside the intended web root directory via directory traversal sequences (e.g., ../../../') in HTTP requests, potentially reading sensitive system files.

MitigationUpgrade to QTS 5.1.7.2770 build 20240520 or later / QuTS hero h5.1.7.2770 build 20240520 or later. If immediate patching is not possible, restrict administrative interface access to trusted IP addresses only and disable unnecessary network services.

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:= 5.1.0.2348= 5.1.0.2399= 5.1.0.2418= 5.1.0.2444= 5.1.0.2466= 5.1.1.2491= 5.1.2.2533= 5.1.3.2578= 5.1.4.2596= 5.1.5.2645= 5.1.5.2679= 5.1.6.2722
Quts HeroOperating system
Affected:= h5.1.0.2409= h5.1.0.2424= h5.1.0.2453= h5.1.0.2466= h5.1.1.2488= h5.1.2.2534= h5.1.3.2578= h5.1.4.2596= h5.1.5.2647= h5.1.5.2680= h5.1.6.2734

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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. Check QTS or QuTS hero version
    Log into the QNAP admin interface and go to Control Panel > System > Firmware, or run 'fw_var.sh get_system_version' via SSH
    Affected if The displayed version matches any of the affected versions: QTS 5.1.0.2348, 5.1.0.2399, 5.1.0.2418, 5.1.0.2444, 5.1.0.2466, 5.1.1.2491, 5.1.2.2533, 5.1.3.2578, 5.1.4.2596, 5.1.5.2645, 5.1.5.2679, 5.1.6.2722 or QuTS hero h5.1.0.2409, h5.1.0.2424, h5.1.0.2453, h5.1.0.2466, h5.1.1.2488, h5.1.2.2534, h5
  2. Verify administrative access is enabled
    Check if the QNAP web administration interface (ports 808 or 443) is accessible from network segments where untrusted users exist
    Affected if The admin interface is exposed to network segments containing untrusted or anonymous users
  3. Confirm user authentication is possible
    Determine if any user accounts exist with access to the web-based QTS/QuTS hero interface
    Affected if User accounts with web interface access are present in the system

The system is affected if the installed QTS or QuTS hero version matches any of the specific versions listed and the administrative web interface is accessible to authenticated users.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to QTS 5.1.7.2770 build 20240520 or later / QuTS hero h5.1.7.2770 build 20240520 or later. If immediate patching is not possible, restrict administrative interface access to trusted IP addresses only and disable unnecessary network services.

Recommended fix High confidence

QTS 5.1.7.2770 build 20240520 or later, or QuTS hero h5.1.7.2770 build 20240520 or later

  1. Log into the QNAP device as an administrator
  2. Navigate to Control Panel > System > System Information to identify the current QTS or QuTS hero version and build number
  3. If the current version matches one of the affected versions (QTS 5.1.0.2348, 5.1.0.2399, 5.1.0.2418, 5.1.0.2444 or QuTS hero h5.1.0.2409, h5.1.0.2424, h5.1.0.2453, h5.1.0.2466), proceed with firmware update
  4. Go to Control Panel > System > Firmware Update
  5. Select Check for Update or manually download the firmware from QNAP's support website
  6. Install QTS 5.1.7.2770 build 20240520 or later (for QTS devices) or QuTS hero h5.1.7.2770 build 20240520 or later (for QuTS hero devices)
  7. Allow the system to reboot after the update completes
  8. Verify the new version by checking System Information again

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

Fix this in Qts Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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