dbcve.org
Data MasterOperating system · Asustor

CVE-2023-4475

MEDIUM · 5.5 CVSS v3.1 Published 2023-08-22
Fix available
A fix is available. Upgrade to 4.2.2.ri61 or later.
See remediation →
58/100
Remediation priority · Elevated
No privileges

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
An Arbitrary File Movement vulnerability was found in ASUSTOR Data Master (ADM) allows an attacker to exploit the file renaming feature to move files to unintended directories. Affected products and versions include: ADM 4.0.6.RIS1, 4.1.0 and below as well as ADM 4.2.2.RI61 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

An Arbitrary File Movement vulnerability in ASUSTOR Data Master (ADM) allows attackers to exploit the file renaming functionality to move files to unintended directories, likely through path traversal. This could enable privilege escalation, configuration tampering, or unauthorized access to sensitive data by relocating files outside their intended scope.

MitigationUpgrade ADM to a patched version beyond 4.0.6.RIS1, 4.1.0, and 4.2.2.RI61. Additionally, implement strict input validation and path traversal checks on the file rename function to prevent moving files outside authorized 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
Data MasterOperating system
Affected:>= 4.0.6.ris1, < 4.2.2.ri61

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

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

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. Identify the installed ADM version
    Access the ADM admin interface and navigate to Settings > System > Version Information, or use the CLI command 'adm version' if available
    Affected if The displayed version falls within the range >= 4.0.6.ris1 and < 4.2.2.ri61
  2. Confirm the version string format
    Verify the exact version string displayed includes the suffix (e.g., .ris1, .ri61) as shown in the affected versions
    Affected if The version shows 4.0.6.ris1 through 4.2.2.ri60 inclusive, or any 4.1.x release
  3. Check if file rename functionality is accessible
    Locate the file manager in ADM and verify the rename option is available for files in shared folders
    Affected if The file rename feature is present and operational in the current installation
  4. Verify the file rename feature accepts path input
    Attempt to rename a file using the file manager, noting whether the interface accepts directory path arguments in the new filename field
    Affected if The rename interface allows entering path-like characters (such as ../ or absolute paths) in the filename field without explicit validation errors

A user is affected if their ADM installation shows a version >= 4.0.6.ris1 and < 4.2.2.ri61, indicating the vulnerable file rename functionality is present.

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 4.2.2.ri61 or later
Fixed in 4.2.2.ri61
Interim mitigation

Upgrade ADM to a patched version beyond 4.0.6.RIS1, 4.1.0, and 4.2.2.RI61. Additionally, implement strict input validation and path traversal checks on the file rename function to prevent moving files outside authorized directories.

Recommended fix Moderate confidence

ADM 4.2.2.RI61 or later (latest stable release)

  1. 1. Log into ASUSTOR Data Master (ADM) web interface
  2. 2. Navigate to Settings > System > ADM Update
  3. 3. Check for available updates and apply the latest stable ADM version
  4. 4. Alternatively, download the firmware from the official ASUSTOR support page and manually update via Control Panel > ADM Update > Manual ADM Update
  5. 5. After update, verify the file renaming functionality works correctly in the intended directories only
Caveat Review ASUSTOR release notes for any configuration or feature changes between your current version and the upgrade version

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
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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