dbcve.org
QtsOperating system · Qnap

CVE-2024-48859

CRITICAL · 9.1 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 →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
An improper authentication vulnerability has been reported to affect several QNAP operating system versions. If exploited, the vulnerability could allow remote attackers to compromise the security of the system. We have already fixed the vulnerability in the following versions: QTS 5.1.9.2954 build 20241120 and later QTS 5.2.2.2950 build 20241114 and later QuTS hero h5.1.9.2954 build 20241120 and later QuTS hero h5.2.2.2952 build 20241116 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

An improper authentication vulnerability in QNAP QTS and QuTS hero operating systems could allow remote attackers to bypass authentication mechanisms and compromise system security. The vulnerability carries a CVSS score of 9.1, indicating critical severity with potential for complete system compromise.

MitigationUpgrade affected QNAP devices to QTS 5.1.9.2954 (build 20241120), QTS 5.2.2.2950 (build 20241114), QuTS hero h5.1.9.2954 (build 20241120), or QuTS hero h5.2.2.2952 (build 20241116) or later versions to remediate this 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:= 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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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. Identify QNAP OS variant
    Access the web admin console or run `uname -a` via SSH to determine if the device runs QTS or QuTS hero
    Affected if The OS is QTS or QuTS hero (both variants are affected)
  2. Retrieve firmware version
    In web UI, go to Control Panel > System > Firmware, or run command `qpkg -i | grep -i core` or check `/etc/config/qts_version` via SSH
    Affected if A version number is displayed that matches the affected builds
  3. Check QTS build number
    If running QTS, compare your build to these affected versions: 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
    Affected if Your QTS build number matches any of these exact versions
  4. Check QuTS hero build number
    If running QuTS hero, compare your build to these affected versions: 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
    Affected if Your QuTS hero build number matches any of these exact versions

You are affected if your QTS or QuTS hero build number exactly matches one of the listed vulnerable versions, as the vulnerability allows remote authentication bypass.

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.1.9.2954 (build 20241120), QTS 5.2.2.2950 (build 20241114), QuTS hero h5.1.9.2954 (build 20241120), or QuTS hero h5.2.2.2952 (build 20241116) or later versions to remediate this vulnerability.

Recommended fix High confidence

QTS: 5.1.9.2954 (build 20241120) or 5.2.2.2950 (build 20241114) | QuTS hero: h5.1.9.2954 (build 20241120) or h5.2.2.2952 (build 20241116)

  1. 1. Log in to the QNAP admin interface (QTS or QuTS hero)
  2. 2. Go to Control Panel > System > Firmware Update
  3. 3. Click 'Check for Update' to see available firmware versions
  4. 4. Select and install QTS 5.1.9.2954 (build 20241120) or later, OR QTS 5.2.2.2950 (build 20241114) or later
  5. 5. For QuTS hero systems, install h5.1.9.2954 (build 20241120) or later, OR h5.2.2.2952 (build 20241116) or later
  6. 6. Wait for the firmware update to complete and the system to reboot
  7. 7. Verify the new firmware version is installed correctly
Caveat Firmware updates carry inherent risks; ensure backups are in place and plan for potential downtime

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

Fix this in Qts Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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