dbcve.org
AdmApplication · Asustor

CVE-2023-2909

CRITICAL · 10.0 CVSS v3.1 Published 2023-05-31
Fix available
A fix is available. Upgrade to after 4.2.1.rge2 or later.
See remediation →
100/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
EZ Sync service fails to adequately handle user input, allowing an attacker to navigate beyond the intended directory structure and delete files. Affected products and versions include: ADM 4.0.6.REG2, 4.1.0 and below as well as ADM 4.2.1.RGE2 and below.

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

The EZ Sync service contains a path traversal vulnerability (CWE-22) that fails to properly sanitize user input, allowing attackers to use directory traversal sequences (e.g., ../../../) to navigate outside the intended directory and delete arbitrary files on the affected system.

MitigationApply vendor-supplied patches for ADM versions 4.0.6.REG2, 4.1.0 and below, and 4.2.1.RGE2 and below. If no patch is available, implement input validation to reject path traversal sequences and restrict the service to intended directories.

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
AdmApplication
Affected:>= 4.0.0, <= 4.0.6.reg2>= 4.1.0, <= 4.1.0rlq1>= 4.2.0, <= 4.2.1.rge2

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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. Verify EZ Sync service status
    Check if the EZ Sync service is enabled or running on the Asustor ADM system. This can typically be done through the ADM web interface under Services or via CLI if available.
    Affected if EZ Sync service is enabled or running on the system
  2. Check installed ADM version
    Locate the installed ADM version in the system settings or via CLI command (such as 'adm-version' or through the web control panel under System Information).
    Affected if The installed version falls within: 4.0.0 through 4.0.6.reg2, OR 4.1.0 through 4.1.0rlq1, OR 4.2.0 through 4.2.1.rge2
  3. Inspect EZ Sync configuration for traversal exposure
    Review EZ Sync service configuration files or logs for evidence of path traversal requests or improper input handling. Look for any user-accessible endpoints that accept file paths.
    Affected if The service exposes file operations without validating for directory traversal sequences like ../ or ..\
  4. Check for unauthorized file deletion indicators
    Review system logs (such as /var/log/ezsync.log or similar) for suspicious delete operations, especially those targeting files outside the intended sync directory.
    Affected if Logs show file deletion attempts using path traversal patterns or deletions of files outside the expected sync directory

A user is affected if EZ Sync is enabled and the ADM version falls within the affected version ranges (4.0.0-4.0.6.reg2, 4.1.0-4.1.0rlq1, or 4.2.0-4.2.1.rge2).

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 a release after 4.2.1.rge2
Interim mitigation

Apply vendor-supplied patches for ADM versions 4.0.6.REG2, 4.1.0 and below, and 4.2.1.RGE2 and below. If no patch is available, implement input validation to reject path traversal sequences and restrict the service to intended directories.

Recommended fix Moderate confidence

ADM version higher than 4.0.6.REG2, 4.1.0, or 4.2.1.RGE2 (e.g., 4.0.7+, 4.1.1+, 4.2.2+)

  1. 1. Identify the current ADM version installed on the Asustor NAS device
  2. 2. Access the ADM web interface and navigate to Settings > System > Update & Restore > Online Update
  3. 3. Check for available updates and upgrade to a version higher than the vulnerable releases
  4. 4. Alternatively, download the latest ADM firmware from the official Asustor support website (www.asustor.com) and manually update via Settings > System > Update & Restore > Manual Update
  5. 5. After updating, verify the EZ Sync service functionality
Caveat Review Asustor release notes for any configuration or feature changes between versions before upgrading

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

Fix this in Adm Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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