dbcve.org
QtsOperating system · Qnap

CVE-2024-27124

HIGH · 7.5 CVSS v3.1 Published 2024-04-26
Fix available
A fix is available. Upgrade to 4.5.4.2627 / 5.1.3.2578 or later.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges

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 reported to affect several QNAP operating system versions. If exploited, the vulnerability could allow users to execute commands via a network. We have already fixed the vulnerability in the following versions: QTS 5.1.3.2578 build 20231110 and later QTS 4.5.4.2627 build 20231225 and later QuTS hero h5.1.3.2578 build 20231110 and later QuTS hero h4.5.4.2626 build 20231225 and later QuTScloud c5.1.5.2651 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 QTS, QuTS hero, and QuTScloud operating systems that allows authenticated or unauthenticated remote attackers to execute arbitrary operating system commands on the underlying device through insufficient input validation in web interface components.

MitigationUpgrade QNAP devices to the fixed versions: QTS 5.1.3.2578+, QTS 4.5.4.2627+, QuTS hero h5.1.3.2578+, QuTS hero h4.5.4.2626+, or QuTScloud c5.1.5.2651+ to remediate the command injection vulnerability.

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:>= 4.5.1, < 4.5.4.2627>= 5.0.0, < 5.1.3.2578= 4.5.4.2627= 5.1.3.2578
Quts HeroOperating system
Affected:>= h4.5.0, < h4.5.4.2626>= h5.0.0, < h5.1.3.2578= h4.5.4.2626= h5.1.3.2578
QutscloudOperating system
Affected:>= c5.0.0.1919, < c5.1.5.2651

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

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/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 the QNAP product variant
    Log into the QNAP admin web interface and check the dashboard or system information page to determine if the device runs QTS, QuTS hero, or QuTScloud. The product name is typically displayed in the top-left corner of the main console.
    Affected if The device runs QTS, QuTS hero, or QuTScloud and the web interface is accessible
  2. Check the installed QTS version
    In the QTS web console, navigate to Control Panel > System > Firmware Update, or go to Control Panel > System > System Settings > About. The firmware version is displayed on this page. Alternatively, access the device via SSH and run: cat /etc/config/version
    Affected if The QTS version is >= 4.5.1 and < 4.5.4.2627, OR >= 5.0.0 and < 5.1.3.2578, OR equals exactly 4.5.4.2627 or 5.1.3.2578
  3. Check the installed QuTS hero version
    In the QuTS hero web console, go to Control Panel > System > Firmware Update, or Control Panel > System > System Settings > About to view the firmware version. Via SSH, run: cat /etc/config/version
    Affected if The QuTS hero version is >= h4.5.0 and < h4.5.4.2626, OR >= h5.0.0 and < h5.1.3.2578, OR equals exactly h4.5.4.2626 or h5.1.3.2578
  4. Check the installed QuTScloud version
    In the QuTScloud admin console, navigate to Settings > System > About to view the firmware version. Via SSH, run: cat /etc/config/version
    Affected if The QuTScloud version is >= c5.0.0.1919 and < c5.1.5.2651

The device is affected if it runs QTS, QuTS hero, or QuTScloud at any version within the specified ranges (including the boundary versions) and the web interface is accessible to 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
Upgrade available Upgrade to 4.5.4.2627 / 5.1.3.2578 or later
Fixed in 4.5.4.26275.1.3.2578
Interim mitigation

Upgrade QNAP devices to the fixed versions: QTS 5.1.3.2578+, QTS 4.5.4.2627+, QuTS hero h5.1.3.2578+, QuTS hero h4.5.4.2626+, or QuTScloud c5.1.5.2651+ to remediate the command injection vulnerability.

Recommended fix High confidence

QTS 5.1.3.2578 (build 20231110+) or QTS 4.5.4.2627 (build 20231225+); QuTS hero h5.1.3.2578 (build 20231110+) or h4.5.4.2626 (build 20231225+); QuTScloud c5.1.5.2651+

  1. 1. Identify the current QNAP system type (QTS, QuTS Hero, or QuTScloud) and the currently installed version via the QNAP admin interface.
  2. 2. For QTS systems: Upgrade to QTS 5.1.3.2578 build 20231110 or later if running version 5.x; OR upgrade to QTS 4.5.4.2627 build 20231225 or later if running version 4.x.
  3. 3. For QuTS hero systems: Upgrade to QuTS hero h5.1.3.2578 build 20231110 or later if running h5.x; OR upgrade to QuTS hero h4.5.4.2626 build 20231225 or later if running h4.x.
  4. 4. For QuTScloud systems: Upgrade to QuTScloud c5.1.5.2651 or later.
  5. 5. Perform the upgrade through the QNAP Control Panel > System > Firmware Update, or download the specific update from the QNAP download center.
  6. 6. After upgrade, verify the new build version matches or exceeds the fixed versions specified.
Caveat Review QNAP release notes for your specific version path; some major version upgrades may introduce feature changes or require app reinstallation

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

Fix this in Qts Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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