dbcve.org
QtsOperating system · Qnap

CVE-2024-27127

HIGH · 8.8 CVSS v3.1 Published 2024-05-21
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 double free vulnerability has been reported to affect several QNAP operating system versions. If exploited, the vulnerability could allow authenticated users to execute arbitrary code via a network. We have already fixed the vulnerability in the following version: 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 · moderate confidence

This is a double free memory corruption vulnerability in QNAP QTS and QuTS hero operating systems. The flaw allows an authenticated attacker to achieve arbitrary code execution through network-based exploitation, likely by manipulating memory management operations to overwrite function pointers or execute code in an unintended manner.

MitigationOrganizations should immediately identify affected QNAP devices, verify current firmware versions, and upgrade to QTS 5.1.7.2770 build 20240520 or later, or QuTS hero h5.1.7.2770 build 20240520 or later. Prior to updating, organizations should ensure backups are current and test the upgrade in a non-production environment.

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
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 QNAP device type
    Access the web admin interface or log in via SSH and run `uname -a` or check `/etc/platform` to confirm whether the device runs QTS or QuTS hero
    Affected if Device is a QNAP NAS running either QTS or QuTS hero operating system
  2. Check QTS firmware version
    In web admin interface, go to Control Panel > System > Firmware Update, or via SSH run `getcfg system version` or check the output of `cat /etc/config/.global.ini`
    Affected if Version matches any of: 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
  3. Check QuTS hero firmware version
    In web admin interface, go to Control Panel > System > Firmware Update, or via SSH run `getcfg system version` or check the output of `cat /etc/config/.global.ini`
    Affected if Version matches any of: 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
  4. Verify authentication exposure
    Confirm whether remote administrative access is enabled (via web, SSH, or QVPN/Qsync services) and review user accounts with administrative privileges
    Affected if Remote authentication is enabled and untrusted users have admin-level access to the device

Device is affected if it runs QTS versions 5.1.0.2348 through 5.1.6.2722 or QuTS hero versions h5.1.0.2409 through h5.1.6.2734, and has authenticated network access available to potential attackers.

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

Organizations should immediately identify affected QNAP devices, verify current firmware versions, and upgrade to QTS 5.1.7.2770 build 20240520 or later, or QuTS hero h5.1.7.2770 build 20240520 or later. Prior to updating, organizations should ensure backups are current and test the upgrade in a non-production environment.

Recommended fix High confidence

QTS 5.1.7.2770 build 20240520 (or later) / QuTS hero h5.1.7.2770 build 20240520 (or later)

  1. Log into QNAP admin interface and navigate to Control Panel > System > Firmware Update
  2. Check current QTS or QuTS hero version under System > Storage & Snapshots or Control Panel > System > About (note: this vulnerability affects QTS 5.1.0.2348, 5.1.0.2399, 5.1.0.2418, 5.1.0.2444 and QuTS hero h5.1.0.2409, h5.1.0.2424, h5.1.0.2453, h5.1.0.2466)
  3. Backup critical data before performing firmware update as standard precaution
  4. Use QNAP's built-in update mechanism (Control Panel > System > Firmware Update > Check for Update) to update to QTS 5.1.7.2770 build 20240520 or later (or QuTS hero h5.1.7.2770 build 20240520 or later)
  5. Verify the update was successful and system is running the fixed version

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

Fix this in Qts Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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