dbcve.org
Data MasterOperating system · Asustor

CVE-2026-3179

HIGH · 8.1 CVSS v3.1 Published 2026-02-25
Fix available
A fix is available. Upgrade to 5.1.2.reo1 or later.
See remediation →
90/100
Remediation priority · Urgent
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
The FTP Backup on the ADM does not properly sanitize filenames received from the FTP server when parsing directory listings. A malicious server or MITM attacker can craft filenames containing path traversal sequences, causing the client to write files outside the intended backup directory. A path traversal vulnerability may allow an attacker to overwrite arbitrary files on the system and potentially achieve privilege escalation or remote code execution. Affected products and versions include: from ADM 4.1.0 through ADM 4.3.3.ROF1 as well as from ADM 5.0.0 through ADM 5.1.2.RE51.

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 path traversal vulnerability exists in the FTP Backup feature of ADM where filenames received from an FTP server during directory listing parsing are not properly sanitized. An attacker controlling the FTP server or positioned as MITM can embed path traversal sequences (e.g., ../../etc/passwd) in filenames, causing the client to write files outside the intended backup directory.

MitigationUpgrade ADM to a version beyond 4.3.3.ROF1 or 5.1.2.RE51 that includes the patch for proper filename sanitization. If immediate patching is not possible, avoid using untrusted FTP servers for backups and ensure network integrity to prevent MITM attacks.

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
Data MasterOperating system
Affected:>= 4.1.0.rhu2, <= 4.3.3.rof1>= 5.0.0.ra82, < 5.1.2.reo1

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

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/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. Check installed ADM version
    Access the ADM web interface and navigate to Settings > System > Update to view the current version. Alternatively, run 'adc' command via SSH to retrieve the firmware version.
    Affected if Version is >= 4.1.0.rhu2 and <= 4.3.3.rof1, OR >= 5.0.0.ra82 and < 5.1.2.reo1
  2. Verify FTP Backup feature status
    Log into ADM web interface and go to Backup & Restore > FTP Backup. Check if any FTP backup jobs are created or enabled.
    Affected if FTP Backup feature is enabled and configured with at least one FTP server
  3. Inspect FTP server configurations
    Navigate to Backup & Restore > FTP Backup and examine the configured FTP server addresses. Note whether servers are internal/trusted or external/untrusted.
    Affected if FTP backup jobs point to external or untrusted FTP servers, or servers on insecure networks
  4. Review backup destination paths
    In FTP Backup settings, check the 'Local Backup Path' destination for each backup job. Identify the base directory where backups are stored.
    Affected if Backup destination is set to a directory that, if traversed, could affect critical system areas

The environment is affected if the ADM version falls within the vulnerable ranges AND FTP Backup is configured with any FTP server, regardless of whether it is trusted, because the path traversal occurs during filename parsing from the server response.

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.1.2.reo1 or later
Fixed in 5.1.2.reo1
Interim mitigation

Upgrade ADM to a version beyond 4.3.3.ROF1 or 5.1.2.RE51 that includes the patch for proper filename sanitization. If immediate patching is not possible, avoid using untrusted FTP servers for backups and ensure network integrity to prevent MITM attacks.

Recommended fix Moderate confidence

ADM 5.1.2.reo1 or later (for 5.x users); migrate to ADM 5.x (for 4.x users)

  1. Identify the current ADM version in use via the ADM dashboard (Settings > System > Maintenance > Version)
  2. If running ADM 4.x (4.1.0.rhu2 through 4.3.3.rof1), plan migration to ADM 5.x as 4.x is end-of-life
  3. If running ADM 5.x (5.0.0.ra82 through 5.1.2.re51), update to ADM 5.1.2.reo1 or later via Settings > System > Maintenance > Firmware Update
  4. After upgrade, verify the FTP Backup functionality works correctly with a test backup job
  5. Ensure FTP connections use explicit TLS (FTPES) to mitigate MITM risks during backup operations
Caveat Upgrading from ADM 4.x to 5.x may require configuration review as some settings and features differ between major versions

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

Fix this in Data Master Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
38.0 hours of engineering $6,560
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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