dbcve.org
AdmApplication · Asustor

CVE-2023-30770

CRITICAL · 9.8 CVSS v3.1 Published 2023-04-17
Fix available
A fix is available. Upgrade to 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
A stack-based buffer overflow vulnerability was found in the ASUSTOR Data Master (ADM) due to the lack of data size validation. An attacker can exploit this vulnerability to execute arbitrary code. Affected ADM versions include: 4.0.6.REG2, 4.1.0 and below as well as 4.2.0.RE71 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

A stack-based buffer overflow vulnerability exists in ASUSTOR Data Master (ADM) due to insufficient data size validation during input processing. This memory corruption flaw allows an attacker to overwrite stack memory and achieve arbitrary code execution with elevated privileges. The critical CVSS 9.8 score reflects the ease of exploitation and complete confidentiality/integrity impact.

MitigationApply vendor-provided security patches for ADM versions 4.0.6.REG2, 4.1.0 and below, and 4.2.0.RE71 and below. Until patched, restrict network exposure of the ADM management interface and disable unused services.

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.rib4, <= 4.0.6.reg2>= 4.1.0.rhu2, < 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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/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. Identify if ASUSTOR Data Master (ADM) is installed
    Check for ADM by accessing the web management interface (default ports 8000, 8001, 8080, or 443), or by logging into the NAS via SSH and running: cat /etc/os-release or ls -la /usr/local/AppCentral/asustor 2>/dev/null
    Affected if ADM is found to be running on the system
  2. Determine the installed ADM version
    Log into the ADM web interface, navigate to Settings > System > Appearance > About, or via CLI run: cat /var/ARrekord/arch_version 2>/dev/null or grep -r 'ADM_VERSION' /usr/local/etc/ 2>/dev/null
    Affected if The version displayed cannot be confirmed as 4.2.1.rge2 or later, or 4.0.0.rib4 through 4.0.6.reg2, or 4.1.0.rhu2 through 4.2.1.rge1 (version falls within affected ranges)
  3. Verify network exposure of the ADM management interface
    Check router/firewall configuration to determine if ports used by ADM (8000, 8001, 8080, 443) are exposed to the public internet or untrusted networks. Use: nmap -p 8000,8001,8080,443 <external-ip> or check port forwarding rules in router
    Affected if The ADM web interface is reachable from untrusted networks (internet) without firewall restriction
  4. Confirm the vulnerable input processing feature is enabled
    The vulnerability is in the web server component of ADM. Verify the web service is active by attempting to access the login page over HTTP/HTTPS, or via CLI: ps aux | grep -i apache or nginx (ADM uses lighttpd)
    Affected if The ADM web service is running and accepting connections, enabling the attack vector

A system is affected if it runs ADM version 4.0.0.rib4 through 4.0.6.reg2, or 4.1.0.rhu2 through 4.2.1.rge1, with the web management interface accessible over the network.

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.1.rge2 or later
Fixed in 4.2.1.rge2
Interim mitigation

Apply vendor-provided security patches for ADM versions 4.0.6.REG2, 4.1.0 and below, and 4.2.0.RE71 and below. Until patched, restrict network exposure of the ADM management interface and disable unused services.

Recommended fix High confidence

4.2.1.rge2 or later

  1. Log into the ASUSTOR Data Master (ADM) web interface as an administrator
  2. Navigate to the 'Settings' or 'System' section
  3. Locate the 'Firmware Update' or 'ADM Update' option
  4. Check for available updates - the system should show version 4.2.1.rge2 or later as available
  5. Download and apply the firmware update to version 4.2.1.rge2 or newer
  6. After the update completes, verify the ADM version shows 4.2.1.rge2 or higher to confirm the fix
Caveat Standard firmware update risks apply - ensure data is backed up and services may be briefly interrupted during the update process

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

Fix this in Adm 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-30770 — 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-30770 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