dbcve.org
Myqnapcloud LinkApplication · Qnap

CVE-2024-32764

CRITICAL · 9.9 CVSS v3.1 Published 2024-04-26
Fix available
A fix is available. Upgrade to 2.4.51 or later.
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 missing authentication for critical function vulnerability has been reported to affect myQNAPcloud Link. If exploited, the vulnerability could allow users with the privilege level of some functionality via a network. We have already fixed the vulnerability in the following version: myQNAPcloud Link 2.4.51 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

This is a missing authentication vulnerability in myQNAPcloud Link that allows unauthorized users to access critical functions without proper authentication. The vulnerability is network-exploitable and could allow attackers to gain elevated privileges or access restricted functionality.

MitigationUpgrade myQNAPcloud Link to version 2.4.51 or later. If immediate upgrading is not possible, restrict network access to the myQNAPcloud Link service to minimize attack surface.

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
Myqnapcloud LinkApplication
Affected:>= 2.4.0, < 2.4.51

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:H/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. Confirm myQNAPcloud Link is accessible
    Check if the myQNAPcloud Link service is running and network-accessible. Attempt to access the myQNAPcloud Link web interface via its hostname or IP (typically on port 8080 or 443). If the service responds, it is installed and active.
    Affected if The myQNAPcloud Link service is running and reachable on the network.
  2. Locate version information in web interface
    Log into the myQNAPcloud Link web portal and navigate to the Settings or About section. Look for the version number displayed in the interface.
    Affected if Version information is displayed and shows a version between 2.4.0 and 2.4.50 inclusive.
  3. Check version via QTS admin console
    Access the QNAP NAS admin interface (QTS). Navigate to myQNAPcloud section or App Center. Find myQNAPcloud Link in the installed applications list and note the version number displayed.
    Affected if The displayed version is 2.4.0 through 2.4.50.
  4. Verify version via command line
    If you have SSH access to the QNAP device, check for myQNAPcloud Link version using the qpkg command or by inspecting the application package information. Run: `qpkg -i | grep -i myqnapcloud` or check `/etc/config/qpkg.conf` for the package version.
    Affected if The package version is 2.4.0 to 2.4.50.

A system is affected if myQNAPcloud Link is installed and the installed version falls within the range 2.4.0 to 2.4.50 inclusive.

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 2.4.51 or later
Fixed in 2.4.51
Interim mitigation

Upgrade myQNAPcloud Link to version 2.4.51 or later. If immediate upgrading is not possible, restrict network access to the myQNAPcloud Link service to minimize attack surface.

Recommended fix High confidence

myQNAPcloud Link 2.4.51 or later

  1. 1. Identify the current version of myQNAPcloud Link installed on the QNAP device
  2. 2. Access the QNAP admin interface and navigate to myQNAPcloud settings
  3. 3. Check if the current version is below 2.4.51
  4. 4. If version is below 2.4.51, apply the update to myQNAPcloud Link 2.4.51 or later through the QNAP firmware update mechanism
  5. 5. Verify the installation of version 2.4.51 or higher after the update completes

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

Fix this in Myqnapcloud Link Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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