dbcve.org
QtsOperating system · Qnap

CVE-2024-53691

HIGH · 8.8 CVSS v3.1 Published 2024-12-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
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 link following vulnerability has been reported to affect several QNAP operating system versions. If exploited, the vulnerability could allow remote attackers who have gained user access to traverse the file system to unintended locations. We have already fixed the vulnerability in the following versions: QTS 5.1.8.2823 build 20240712 and later QTS 5.2.0.2802 build 20240620 and later QuTS hero h5.1.8.2823 build 20240712 and later QuTS hero h5.2.0.2802 build 20240620 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

This is a path traversal (link following) vulnerability in QNAP QTS and QuTS hero operating systems. Exploitation allows authenticated remote attackers who already have user-level access to escape intended directory boundaries and access files outside the permitted filesystem scope. The CVSS 8.8 score indicates high exploitability with significant confidentiality and integrity impact.

MitigationApply the available firmware updates: QTS 5.1.8.2823 build 20240712 or later, QTS 5.2.0.2802 build 20240620 or later, QuTS hero h5.1.8.2823 build 20240712 or later, or QuTS hero h5.2.0.2802 build 20240620 or later.

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= h5.1.7.2770

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 QTS or QuTS hero version
    Log into the QNAP admin console and go to Control Panel > System > Firmware Update > Firmware Information, or run 'getsysinfo' via QCLI/QMQNA command line
    Affected if The firmware version matches any of the listed affected versions: QTS 5.1.0.2348 through 5.1.6.2722, or QuTS Hero h5.1.0.2409 through h5.1.7.2770
  2. Verify Management Interface Accessibility
    Check if the QTS/QuTS web admin console (port 8080 or 443) is accessible from network segments that contain untrusted users
    Affected if The management interface is exposed to users beyond the trusted admin group
  3. Confirm User Account Configuration
    Review all user accounts in Control Panel > Privilege > Users to identify accounts with standard user-level permissions
    Affected if Non-admin user accounts exist and are allowed to access file management features
  4. Check for Path Traversal Indicators
    Review system logs in Log Center for unusual file access patterns involving '../' sequences or access to system directories from user sessions
    Affected if Logs show file access attempts with directory traversal patterns from user-level accounts

The system is affected if it runs any QTS version between 5.1.0.2348 and 5.1.6.2722 or any QuTS Hero version between h5.1.0.2409 and h5.1.7.2770, especially if the admin interface is accessible to authenticated users with standard privileges.

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

Apply the available firmware updates: QTS 5.1.8.2823 build 20240712 or later, QTS 5.2.0.2802 build 20240620 or later, QuTS hero h5.1.8.2823 build 20240712 or later, or QuTS hero h5.2.0.2802 build 20240620 or later.

Recommended fix High confidence

QTS 5.1.8.2823 (build 20240712) or QTS 5.2.0.2802 (build 20240620) or later; QuTS hero h5.1.8.2823 (build 20240712) or h5.2.0.2802 (build 20240620) or later

  1. 1. Back up all critical data on the NAS before proceeding with the firmware upgrade
  2. 2. Log in to the QNAP QTS or QuTS hero admin interface
  3. 3. Navigate to Control Panel > System > Firmware Update
  4. 4. Click 'Check for Update' to see available firmware versions
  5. 5. If the recommended version (QTS 5.1.8.2823 build 20240712 or later, or QTS 5.2.0.2802 build 20240620 or later) is available, select it and click 'Update Now'
  6. 6. Wait for the update process to complete - do not power off the device
  7. 7. After the NAS reboots, verify the new firmware version in Control Panel > System > Firmware Update > About
Caveat Review QNAP release notes before upgrading as firmware updates may temporarily affect NAS services or require reconfiguration of some applications

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
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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