dbcve.org
Data MasterOperating system · Asustor

CVE-2023-3699

MEDIUM · 5.5 CVSS v3.1 Published 2023-08-22
Fix available
A fix is available. Upgrade to 4.2.3.rk91 or later.
See remediation →
57/100
Remediation priority · Elevated
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
An Improper Privilege Management vulnerability was found in ASUSTOR Data Master (ADM) allows an unprivileged local users to modify the storage devices configuration. 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 · moderate confidence

Improper Privilege Management vulnerability in ASUSTOR Data Master (ADM) allows unprivileged local users to modify storage device configuration. The application fails to properly enforce authorization checks, permitting users without appropriate permissions to alter storage settings that should be restricted to administrators.

MitigationApply vendor-supplied firmware updates for affected ADM versions (4.0.6.RIS1, 4.1.0 and below, 4.2.2.RI61 and below). If no patch available, restrict local user access to the system and monitor for unauthorized storage configuration changes.

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.3.rk91

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

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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 ASUSTOR Data Master installation
    Check if ASUSTOR ADM is running on the system by looking for ADM-related processes or accessing the ADM web interface (typically on port 8000 or 8001)
    Affected if ADM is installed and accessible on the system
  2. Check ADM version
    Access ADM web interface, go to Settings > System > Backup/Restore, or use the command 'adsm --version' if available via SSH to determine the exact ADM version installed
    Affected if Installed version is >= 4.0.6.ris1 and < 4.2.3.rk91 (or version cannot be determined but falls within this range)
  3. Verify non-administrator user accounts exist
    Check for local user accounts by accessing ADM User Management section or using 'dm user list' command via SSH to enumerate non-admin accounts
    Affected if There are non-administrator user accounts configured on the system
  4. Inspect storage configuration permissions
    Navigate to Storage Manager in ADM web interface and verify which user roles have permission to modify storage device configuration settings
    Affected if Non-administrator users have Modify or Write permissions on storage configuration when they should not (authorization not properly enforced)
  5. Review audit logs for storage changes
    Check ADM logs in Storage Manager > Information > Log or system audit logs for any storage configuration changes made by non-admin users
    Affected if Storage configuration changes were made by users without administrator privileges

The environment is affected if ASUSTOR ADM version is between 4.0.6.ris1 and 4.2.3.rk91 and non-administrator users can modify storage device configuration settings.

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.3.rk91 or later
Fixed in 4.2.3.rk91
Interim mitigation

Apply vendor-supplied firmware updates for affected ADM versions (4.0.6.RIS1, 4.1.0 and below, 4.2.2.RI61 and below). If no patch available, restrict local user access to the system and monitor for unauthorized storage configuration changes.

Recommended fix Moderate confidence

ADM 4.2.3.rk91 or later

  1. Access the ASUSTOR NAS admin interface (ADM)
  2. Navigate to Settings > System > Firmware Update
  3. Check for the latest available ADM version
  4. If not automatically offered, manually download ADM 4.2.3.rk91 or later from the ASUSTOR support website
  5. Backup critical data before applying the firmware update
  6. Apply the firmware update and restart the NAS
Caveat Firmware updates on NAS devices may reset some configurations; review settings after upgrade

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-3699 — 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-3699 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