dbcve.org
Smb ServiceApplication · Qnap

CVE-2024-50387

CRITICAL · 9.8 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
A SQL injection vulnerability has been reported to affect several QNAP operating system versions. If exploited, the vulnerability could allow remote attackers to inject malicious code. We have already fixed the vulnerability in the following version: SMB Service 4.15.002 and later SMB Service h4.15.002 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

SQL injection vulnerability in QNAP SMB Service allows remote attackers to inject malicious code. The flaw affects multiple QNAP OS versions and has been patched in SMB Service version 4.15.002 and later (and h4.15.002 for hardware variants).

MitigationApply QNAP SMB Service updates 4.15.002/h4.15.002 or later to all affected systems to remediate this critical SQL 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
Smb ServiceApplication
Affected:= 4.15.001= h4.15.001

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
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Verify QNAP SMB Service is installed
    Access QNAP admin panel or use command line (e.g., `ps aux | grep smb` or check via App Center) to confirm SMB Service is present on the system
    Affected if SMB Service is not installed or not running, the vulnerability does not apply
  2. Identify SMB Service version number
    In QNAP admin panel, go to Control Panel > Network Services > Win/Mac/NFS > SMB Service, or use command `sqms/smb_util.sh -v` or check version via QNAP App Center for SMB Service package
    Affected if Unable to retrieve version - assume potentially affected if service is running
  3. Compare installed version to affected ranges
    Check if version equals exactly 4.15.001 or h4.15.001 (exact version match as specified in affected products)
    Affected if Installed version is exactly 4.15.001 or h4.15.001 - these are the only confirmed affected versions
  4. Confirm version is below fixed release
    If version is 4.15.001 or h4.15.001, verify it is not yet updated to 4.15.002/h4.15.002 or later
    Affected if Version is 4.15.001 or h4.15.001 and has not been patched to 4.15.002/h4.15.002 or newer

System is affected only if QNAP SMB Service is running and the installed version is exactly 4.15.001 or h4.15.001; versions 4.15.002/h4.15.002 and later are patched.

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

Apply QNAP SMB Service updates 4.15.002/h4.15.002 or later to all affected systems to remediate this critical SQL injection vulnerability.

Recommended fix High confidence

SMB Service 4.15.002 or later (or SMB Service h4.15.002 or later for h4 branch)

  1. 1. Identify the current SMB Service version installed on the QNAP device (check if using 4.x branch or h4.x branch)
  2. 2. Access the QNAP admin interface or use QNAP's update mechanism to check for SMB Service updates
  3. 3. Download and install SMB Service version 4.15.002 or later (for 4.x branch)
  4. 4. Alternatively, download and install SMB Service version h4.15.002 or later (for h4.x branch)
  5. 5. Verify the installed SMB Service version after upgrade to confirm it matches 4.15.002+/h4.15.002+
  6. 6. Test that SMB shares and functionality remain operational after the update

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

Fix this in Smb Service Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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