CVE-2025-22484
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 · uneditedAn allocation of resources without limits or throttling vulnerability has been reported to affect File Station 5. If a remote attacker gains a user account, they can then exploit the vulnerability to prevent other systems, applications, or processes from accessing the same type of resource. We have already fixed the vulnerability in the following version: File Station 5 5.5.6.4847 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 confidenceThis is a resource exhaustion vulnerability in QNAP File Station 5 where lack of proper resource limits allows an authenticated remote attacker to consume excessive resources (such as memory, file handles, or connections), causing denial of service for other legitimate users and processes attempting to access the same resources.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
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 checksWork through these to decide whether this CVE applies to you.
-
Verify File Station 5 is installedAccess QNAP NAS admin console, go to App Center or use command 'qpkg -l | grep -i file-station' to list installed packagesAffected if File Station 5 is not installed or has been removed entirely
-
Check File Station 5 version numberIn QNAP admin console, go to App Center > File Station > click on the app to view version, or run 'qpkg -i FileStation' to get version infoAffected if Version displayed is below 5.5.6.4847 or cannot be determined (unknown version)
-
Confirm File Station service is runningIn QNAP admin console go to Control Panel > System > Services > File Station must be enabled, or check via command 'sqlite3 /etc/config/qpkg.conf "select * from QPKG where Name like '%FileStation%'"'Affected if File Station service shows as Running and version is vulnerable
-
Check for abnormal resource usageMonitor system resources via QNAP Resource Monitor or command 'top' / 'htop' looking for high memory usage or many File Station-related processesAffected if Excessive resource consumption by File Station processes is observed, potentially indicating exploitation of this vulnerability
User is affected if File Station 5 is installed, running, and its version is earlier than 5.5.6.4847
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpdate File Station 5 to version 5.5.6.4847 or later to apply the vendor patch that implements proper resource throttling limits.
File Station 5 5.5.6.4847 or later
- 1. Identify the current version of File Station 5 installed on the QNAP device
- 2. Navigate to the QNAP App Center or File Station settings
- 3. Check for and apply any available updates to File Station 5
- 4. Upgrade to File Station 5 version 5.5.6.4847 or later
- 5. Verify the upgrade was successful by checking the installed version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-22484 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-22484 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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