File StationApplication · Qnap

CVE-2025-29877

HIGH · 7.5 CVSS v3.1 Published 2025-06-06
Fix available
A fix is available. Upgrade to 5.5.6.4847 or later.
See remediation →
84/100
Remediation priority · High
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 NULL pointer dereference vulnerability has been reported to affect File Station 5. If a remote attacker gains a user account, they can then exploit the vulnerability to launch a denial-of-service (DoS) attack. 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 confidence

A NULL pointer dereference vulnerability in File Station 5 allows an authenticated remote attacker to cause a denial-of-service condition. The attacker must first obtain valid user credentials to exploit this vulnerability.

MitigationUpgrade File Station to version 5.5.6.4847 or later to remediate this vulnerability.

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
File StationApplication
Affected:>= 5.5.6.4691, < 5.5.6.4847

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
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

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 File Station 5 is installed
    Access the QNAP NAS admin interface and navigate to the App Center or use the QNAP CLI tool (if available) to list installed applications. Look for File Station in the installed applications list.
    Affected if File Station 5 is not installed, the system is not affected by this vulnerability.
  2. Determine installed File Station version
    In the QNAP admin interface, go to App Center, find File Station, and view its version information. Alternatively, access the NAS via SSH and check the package manifest or version file for File Station.
    Affected if Unable to determine the version, assume potentially affected.
  3. Compare version against affected range
    Compare the installed version number to the affected range: versions >= 5.5.6.4691 and < 5.5.6.4847 are vulnerable.
    Affected if Installed version falls within >= 5.5.6.4691 and < 5.5.6.4847, the system is affected.
  4. Confirm user authentication is enabled
    Verify that user authentication is configured on the QNAP NAS. Check if local users or domain users can log in to the File Station web interface.
    Affected if The vulnerability requires valid user credentials to exploit; systems with disabled user authentication have reduced attack surface but the vulnerable code may still be present.

The system is affected if File Station 5 is installed with a version greater than or equal to 5.5.6.4691 and less than 5.5.6.4847.

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

Upgrade File Station to version 5.5.6.4847 or later to remediate this vulnerability.

Recommended fix High confidence

File Station 5.5.6.4847 or later

  1. 1. Log in to the QNAP NAS admin interface
  2. 2. Navigate to App Center or File Station settings
  3. 3. Check the current File Station version (should be >= 5.5.6.4691 and < 5.5.6.4847)
  4. 4. Update File Station to version 5.5.6.4847 or later
  5. 5. Verify the update was successful by checking the File Station version number
  6. 6. Restart File Station service if prompted
Caveat Standard QNAP update process - review release notes for any configuration changes

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

Fix this in File Station Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-29877 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-29877 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