dbcve.org
QtsOperating system · Qnap

CVE-2024-37047

MEDIUM · 6.5 CVSS v3.1 Published 2024-11-22
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 buffer copy without checking size of input vulnerability has been reported to affect several QNAP operating system versions. If exploited, the vulnerability could allow remote attackers who have gained administrator access to execute code. We have already fixed the vulnerability in the following versions: QTS 5.2.1.2930 build 20241025 and later QuTS hero h5.2.1.2929 build 20241025 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 · moderate confidence

A buffer copy without checking size vulnerability in QNAP QTS and QuTS hero operating systems allows remote authenticated administrators to execute arbitrary code. This is a classic buffer overflow where the application copies data into a buffer without validating the input size, potentially leading to memory corruption and code execution.

MitigationUpgrade affected QNAP devices to QTS 5.2.1.2930 build 20241025 or later, or QuTS hero h5.2.1.2929 build 20241025 or later. Until upgraded, restrict administrative access to trusted personnel only and monitor for suspicious admin activity.

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.2.0.2737= 5.2.0.2744= 5.2.0.2782= 5.2.0.2802= 5.2.0.2823= 5.2.0.2851= 5.2.0.2860
Quts HeroOperating system
Affected:= h5.2.0.2737= h5.2.0.2782= h5.2.0.2789= h5.2.0.2802= h5.2.0.2823= h5.2.0.2851= h5.2.0.2860

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
High
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/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. Check QTS firmware version via web interface
    Log into QTS admin console, go to Control Panel > System Administration > Firmware Update, and note the displayed version number and build
    Affected if The version matches 5.2.0.2737, 5.2.0.2744, 5.2.0.2782, 5.2.0.2802, 5.2.0.2823, 5.2.0.2851, or 5.2.0.2860
  2. Check QTS version via command line
    Access the NAS via SSH and run: `version` or `cat /etc/config/version`
    Affected if The version output matches any of the affected QTS versions listed above
  3. Check QuTS hero firmware version via web interface
    Log into QuTS hero admin console, navigate to Control Panel > System Administration > Firmware Update, and record the version and build number
    Affected if The version matches h5.2.0.2737, h5.2.0.2782, h5.2.0.2789, h5.2.0.2802, h5.2.0.2823, h5.2.0.2851, or h5.2.0.2860
  4. Check QuTS hero version via command line
    Access the NAS via SSH and run: `version` or `cat /etc/config/version`
    Affected if The version output matches any of the affected QuTS hero versions listed above
  5. Verify remote administrative access is exposed
    In the admin console, go to Control Panel > Security > Security Level, or check if the admin web interface (port 808 or 443) is accessible from untrusted networks
    Affected if The administrative interface is reachable from external networks without VPN restrictions

If the installed QTS or QuTS hero version matches any of the specific build numbers in the affected list AND administrative access is exposed, the environment is vulnerable to remote authenticated code execution.

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 affected QNAP devices to QTS 5.2.1.2930 build 20241025 or later, or QuTS hero h5.2.1.2929 build 20241025 or later. Until upgraded, restrict administrative access to trusted personnel only and monitor for suspicious admin activity.

Recommended fix High confidence

QTS 5.2.1.2930 build 20241025 or later; QuTS hero h5.2.1.2929 build 20241025 or later

  1. Identify current QTS or QuTS hero version in use (System Settings > About > Firmware Version)
  2. If running QTS version 5.2.0.2737, 5.2.0.2744, 5.2.0.2782, or 5.2.0.2802, upgrade to QTS 5.2.1.2930 build 20241025 or later
  3. If running QuTS hero version h5.2.0.2737, h5.2.0.2782, h5.2.0.2789, or h5.2.0.2802, upgrade to QuTS hero h5.2.1.2929 build 20241025 or later
  4. Access Control Panel > System > Firmware Update and use 'Check for Update' or manually download the update from QNAP website
  5. Verify the upgrade was successful and the new firmware version matches the fixed releases
  6. Review administrator accounts and ensure no unauthorized access occurred (the vulnerability requires prior administrator access)
Caveat Review QNAP release notes for QTS 5.2.1 and QuTS hero h5.2.1 for any configuration or feature changes before upgrading

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

Fix this in Qts 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 help mitigating

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-2024-37047 — 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-37047 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