dbcve.org
QtsOperating system · Qnap

CVE-2024-50405

MEDIUM · 5.5 CVSS v3.1 Published 2025-03-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
61/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
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 who have gained administrator access to modify application data. We have already fixed the vulnerability in the following versions: QTS 5.2.3.3006 build 20250108 and later QuTS hero h5.2.3.3006 build 20250108 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 with existing administrator access to inject carriage return and line feed characters into HTTP headers, potentially enabling HTTP response splitting attacks to modify application data.

MitigationUpgrade QNAP devices to QTS 5.2.3.3006 build 20250108 or later / QuTS hero h5.2.3.3006 build 20250108 or later. Since the vulnerability requires administrator access, prioritize least-privilege admin controls and monitor for credential compromise.

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= 5.2.1.2930= 5.2.2.2950
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= h5.2.1.2929= h5.2.1.2940= h5.2.2.2952

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
Changed
Confidentiality
None
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:N/I:L/A:L

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 OS version
    Log into QTS/QuTS hero admin console and navigate to Control Panel > System > Firmware Update, or run 'getsysinfo' via SSH to retrieve the firmware version and build number
    Affected if The displayed version matches any of: QTS 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, 5.2.1.2930, 5.2.2.2950 OR QuTS hero 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, h5.2.1.2929, h5.2.1.2940, h5.2.2.2952
  2. Determine OS type (QTS vs QuTS hero)
    Check the System Information page in the admin console or the output of 'getsysinfo' - QuTS hero versions contain an 'h' prefix (e.g., h5.2.0.x)
    Affected if Running QuTS hero with version starting with h5.2.0 or h5.2.1 or h5.2.2 and the full version matches any in the affected list
  3. Confirm administrator accounts exist
    Navigate to Control Panel > Administration > User Accounts in the admin UI, or query user accounts via command line 'getusrlist'
    Affected if Any administrator-level accounts are configured on the device (the vulnerability requires existing administrator access)
  4. Verify web server is enabled
    Confirm the QTS/QuTS web server is running by accessing the admin login page over HTTPS (port 8080 or 443)
    Affected if The web administration interface is accessible (HTTP header injection occurs in the web server component)

You are affected if your QNAP device runs QTS or QuTS hero versions matching exactly those listed and has administrator accounts configured.

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 QNAP devices to QTS 5.2.3.3006 build 20250108 or later / QuTS hero h5.2.3.3006 build 20250108 or later. Since the vulnerability requires administrator access, prioritize least-privilege admin controls and monitor for credential compromise.

Recommended fix High confidence

QTS 5.2.3.3006 build 20250108 or later; QuTS hero h5.2.3.3006 build 20250108 or later

  1. 1. Back up all critical data on the QNAP device before proceeding with firmware update.
  2. 2. Log in to the QNAP admin interface (QTS or QuTS hero).
  3. 3. Navigate to Control Panel > System Administration > Firmware Update.
  4. 4. Click 'Check for Update' to identify available updates.
  5. 5. If available, update to QTS 5.2.3.3006 (build 20250108) or later, or QuTS hero h5.2.3.3006 (build 20250108) or later.
  6. 6. Verify the update completed successfully by checking the firmware version in Control Panel > System Administration > System Info.
Caveat Standard firmware update precautions apply - ensure power stability and backup data; no specific breaking changes mentioned in advisory

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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