dbcve.org
QtsOperating system · Qnap

CVE-2024-48867

HIGH · 7.5 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 →
84/100
Remediation priority · High
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 neutralization of CRLF sequences ('CRLF Injection') vulnerability has been reported to affect several QNAP operating system versions. If exploited, the vulnerability could allow remote attackers to modify application data. 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 · high confidence

CRLF Injection vulnerability in QNAP QTS and QuTS hero operating systems allows remote attackers to inject carriage return and line feed characters into HTTP responses, potentially modifying application data or splitting HTTP responses. The vulnerability stems from improper neutralization of user-supplied input before inclusion in web responses.

MitigationUpdate QNAP systems to QTS 5.1.9.2954 build 20241120 / 5.2.2.2950 build 20241114 or later, or QuTS hero h5.1.9.2954 build 20241120 / h5.2.2.2952 build 20241116 or later 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
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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. Check QTS version in admin console
    Log into the QNAP admin web interface, navigate to Control Panel > System > Firmware, and note the QTS version and build number displayed.
    Affected if The displayed 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
  2. Check QuTS hero version in admin console
    Log into the QNAP admin web interface, navigate to Control Panel > System > Firmware, and note the QuTS hero version and build number displayed.
    Affected if The displayed 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, h5.1.7.2770
  3. Check QTS version via command line
    Access the QNAP device via SSH and run the command: cat /etc/config/qpkg.conf | grep -i build or check the output of getsysinfo to retrieve the firmware version.
    Affected if The version output matches any of the affected QTS versions listed above.
  4. Check QuTS hero version via command line
    Access the QNAP device via SSH and run the command: getsysinfo or check the version displayed in /etc/config/qpkg.conf for QuTS hero packages.
    Affected if The version output matches any of the affected QuTS hero versions listed above.

The system is affected if it is running any of the specifically listed QTS or QuTS hero versions, as this is a server-side HTTP response injection flaw that requires no specific configuration to be exploitable.

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

Update QNAP systems to QTS 5.1.9.2954 build 20241120 / 5.2.2.2950 build 20241114 or later, or QuTS hero h5.1.9.2954 build 20241120 / h5.2.2.2952 build 20241116 or later to remediate this vulnerability.

Recommended fix High confidence

QTS 5.1.9.2954 (build 20241120) / QTS 5.2.2.2950 (build 20241114) / QuTS hero h5.1.9.2954 (build 20241120) / QuTS hero h5.2.2.2952 (build 20241116)

  1. 1. Identify the current QTS or QuTS hero version by logging into the QNAP admin interface and checking System > Firmware
  2. 2. Determine the appropriate upgrade path: For QTS 5.1.x versions, upgrade to QTS 5.1.9.2954 build 20241120 or later; For QTS 5.2.x versions, upgrade to QTS 5.2.2.2950 build 20241114 or later; For QuTS hero h5.1.x versions, upgrade to h5.1.9.2954 build 20241120 or later; For QuTS hero h5.2.x versions, upgrade to h5.2.2.2952 build 20241116 or later
  3. 3. Back up all critical data stored on the NAS before performing the firmware upgrade
  4. 4. Download the appropriate firmware update from the QNAP download center at www.qnap.com or use the QNAP Utility/Console to check for updates
  5. 5. Apply the firmware update through the QNAP admin interface under Control Panel > System > Firmware Update, or use the Qfinder Pro utility
  6. 6. After the upgrade completes, verify the new version by checking System > Firmware to confirm the build number matches or exceeds the fixed versions listed above
Caveat Standard QNAP firmware upgrade risks apply - ensure data backup before proceeding; some applications or settings may require reconfiguration after major version upgrades

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
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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