dbcve.org
AdmApplication · Asustor

CVE-2022-37398

HIGH · 8.8 CVSS v3.1 Published 2022-08-05
Fix available
A fix is available. Upgrade to after 4.1.0.rjd1 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 inside ADM when using WebDAV due to the lack of data size validation. An attacker can exploit this vulnerability to run arbitrary code. Affected ADM versions include: 3.5.9.RUE3 and below, 4.0.5.RVI1 and below as well as 4.1.0.RJD1 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 QNAP ADM (Administrative Module) WebDAV functionality due to insufficient data size validation. Attackers can exploit this to overflow a stack buffer and execute arbitrary code with the privileges of the affected service.

MitigationUpdate QNAP ADM to a version beyond 3.5.9.RUE3, 4.0.5.RVI1, or 4.1.0.RJD1 (depending on the release branch). If immediate patching is not feasible, disable the WebDAV service and restrict administrative interface access to trusted networks.

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:>= 3.5.0, <= 3.5.9.rue3>= 4.0.0, <= 4.0.5.rvi1>= 4.1.0, <= 4.1.0.rjd1

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

CVSS:3.1/AV:N/AC:L/PR:L/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 installed Asustor ADM version
    Access the ADM web interface and navigate to Settings > System > Firmware Update, or run the command 'ADM version' via SSH/terminal to retrieve the current firmware version string
    Affected if The version falls within 3.5.0 to 3.5.9.rue3, 4.0.0 to 4.0.5.rvi1, or 4.1.0 to 4.1.0.rjd1
  2. Verify WebDAV service status
    In the ADM web interface, go to Services > WebDAV and confirm whether the WebDAV service is turned ON, or check via command line if available
    Affected if WebDAV service is enabled and the installed version is within the affected ranges listed above
  3. Confirm WebDAV configuration
    Inspect the WebDAV configuration settings to verify that the service is actively accepting connections. On Asustor devices, this can typically be found in /volume1/.system/asustor/webdav/ or through the ADM web UI under Services > WebDAV
    Affected if WebDAV is configured and running on an affected version

You are affected if the installed Asustor ADM version falls within the affected ranges (3.5.0-3.5.9.rue3, 4.0.0-4.0.5.rvi1, or 4.1.0-4.1.0.rjd1) AND the WebDAV service is enabled

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.1.0.rjd1
Interim mitigation

Update QNAP ADM to a version beyond 3.5.9.RUE3, 4.0.5.RVI1, or 4.1.0.RJD1 (depending on the release branch). If immediate patching is not feasible, disable the WebDAV service and restrict administrative interface access to trusted networks.

Recommended fix Moderate confidence

Upgrade to ADM version 3.5.10 or later (for 3.5.x line), 4.0.6 or later (for 4.0.x line), or 4.1.1 or later (for 4.1.x line) - or the latest available stable ADM release

  1. 1. Log into the ADM web interface of your Asustor NAS.
  2. 2. Navigate to 'Settings' > 'System' > 'Administration'.
  3. 3. Check your current ADM version under 'System Information'.
  4. 4. Go to 'App Central' > 'Settings' and check for updates, or visit Asustor's support website (www.asustor.com) to download the latest ADM firmware.
  5. 5. If an update is available, click 'Update Now' to install it, or manually upload the firmware file if downloading from Asustor's website.
  6. 6. After the update completes, verify the new ADM version is greater than 3.5.9.RUE3, 4.0.5.RVI1, or 4.1.0.RJD1 respectively.
Caveat Review Asustor release notes before upgrading to check for any compatibility issues with installed apps or configurations

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

Fix this in Adm Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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