dbcve.org
Qsync CentralApplication · Qnap

CVE-2023-47564

HIGH · 8.1 CVSS v3.1 Published 2024-02-02
Fix available
A fix is available. Upgrade to 4.3.0.11 / 4.4.0.15 or later.
See remediation →
87/100
Remediation priority · High
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 incorrect permission assignment for critical resource vulnerability has been reported to affect Qsync Central. If exploited, the vulnerability could allow authenticated users to read or modify the resource via a network. We have already fixed the vulnerability in the following versions: Qsync Central 4.4.0.15 ( 2024/01/04 ) and later Qsync Central 4.3.0.11 ( 2024/01/11 ) 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

This is an incorrect permission assignment vulnerability in Qsync Central (QNAP's file synchronization software) that allows authenticated users to improperly read or modify critical resources via network access. The vulnerability stems from overly permissive access controls on sensitive functionality.

MitigationUpgrade Qsync Central to version 4.4.0.15 (or later) or 4.3.0.11 (or later) depending on your current major version branch, as these patches contain the corrected permission assignments.

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
Qsync CentralApplication
Affected:>= 4.3.0.0, < 4.3.0.11>= 4.4.0.0, < 4.4.0.15

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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. Verify Qsync Central is installed
    Log into the QNAP NAS admin interface and navigate to the App Center or check the running processes to confirm Qsync Central is installed and active
    Affected if Qsync Central is not installed on the system, the vulnerability does not apply
  2. Identify the installed Qsync Central version
    In the QNAP admin panel, go to Qsync Central > Settings > About, or use the command line to query the package version (e.g., run 'qpkg -g Qsync_Central' or check /share/CACHEDEV1_DATA/.qpkg/Qsync_Central/.config.xml)
    Affected if The exact version number cannot be determined from the system
  3. Compare installed version to affected ranges
    Check if the installed version falls within: 4.3.0.0 through 4.3.0.10 (inclusive), OR 4.4.0.0 through 4.4.0.14 (inclusive)
    Affected if The installed version is within either of these ranges (>=4.3.0.0 and <4.3.0.11, OR >=4.4.0.0 and <4.4.0.15)
  4. Confirm network access to Qsync Central is enabled
    Verify that Qsync Central is accessible over the network by checking its binding to network interfaces or verifying remote access settings in Qsync Central > Settings
    Affected if Qsync Central is not accessible over the network, the exploit vector is not present

The system is affected if Qsync Central is installed with a version between 4.3.0.0 and 4.3.0.10, or between 4.4.0.0 and 4.4.0.14, and the service is network-accessible with authentication enabled.

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 4.3.0.11 / 4.4.0.15 or later
Fixed in 4.3.0.114.4.0.15
Interim mitigation

Upgrade Qsync Central to version 4.4.0.15 (or later) or 4.3.0.11 (or later) depending on your current major version branch, as these patches contain the corrected permission assignments.

Recommended fix High confidence

Qsync Central 4.4.0.15 (or 4.3.0.11 for the 4.3.x branch)

  1. 1. Identify the current installed version of Qsync Central by accessing the QNAP admin interface and navigating to Qsync Central settings.
  2. 2. If currently running Qsync Central version 4.4.0.x, upgrade to version 4.4.0.15 or later.
  3. 3. If currently running Qsync Central version 4.3.0.x, upgrade to version 4.3.0.11 or later.
  4. 4. Perform the upgrade through the QNAP App Center or by downloading the update from the official QNAP download center.
  5. 5. After upgrading, verify the new version is installed and confirm the vulnerability is remediated.

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

Fix this in Qsync Central Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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