CVE-2025-54146
NULL Pointer Dereference in Qsync Central Enables Remote DoS
Publication date: 2026-02-11
Last updated on: 2026-02-12
Assigner: QNAP Systems, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| qnap | qsync_central | From 5.0.0.0 (inc) to 5.0.0.4 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-476 | The product dereferences a pointer that it expects to be valid but is NULL. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a NULL pointer dereference issue affecting Qsync Central. It occurs when a remote attacker who has gained access to a user account exploits the flaw to cause the software to crash or become unavailable.
Essentially, the attacker triggers a condition where the program tries to access a memory location that is not properly initialized (NULL), leading to a denial-of-service (DoS) situation.
How can this vulnerability impact me? :
If exploited, this vulnerability can cause a denial-of-service (DoS) attack on Qsync Central, making the service unavailable or unstable.
An attacker with a user account could disrupt normal operations by crashing the application, potentially affecting availability of data synchronization services.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, you should upgrade Qsync Central to version 5.0.0.4 or later, as the vulnerability has been fixed in this version.
Additionally, since the vulnerability can be exploited by a remote attacker who has a user account, it is advisable to review and restrict user account access to trusted users only.