dbcve.org
Data MasterOperating system · Asustor

CVE-2026-24932

MEDIUM · 5.9 CVSS v3.1 Published 2026-02-03
Fix available
A fix is available. Upgrade to 5.1.2.re51 or later.
See remediation →
68/100
Remediation priority · Elevated
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
The DDNS update function in ADM fails to properly validate the hostname of the DDNS server's TLS/SSL certificate. Although the connection uses HTTPS, an improper validated TLS/SSL certificates allows a remote attacker can intercept the communication to perform a Man-in-the-Middle (MitM) attack, which may obtain the sensitive information of DDNS updating process, including the user's account email, MD5 hashed password, and device serial number.This issue affects ADM: from 4.1.0 through 4.3.3.ROF1, from 5.0.0 through 5.1.1.RCI1.

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

The DDNS update function in ADM (Asustor Device Manager) fails to properly validate the hostname field of TLS/SSL certificates when establishing HTTPS connections to DDNS update servers. This certificate validation flaw allows remote attackers positioned on the network path to perform Man-in-the-Middle (MitM) attacks, intercepting sensitive credentials including user account email addresses, MD5-hashed passwords, and device serial numbers during the DDNS update process.

MitigationUpdate ADM to a patched version beyond 4.3.3.ROF1 or 5.1.1.RCI1 that implements proper TLS certificate hostname validation, or temporarily disable DDNS updates until the patch can be applied.

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.1.0.rhu2, <= 4.3.3.rof1>= 5.0.0.ra82, < 5.1.2.re51

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

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/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. Check ADM version
    Log into Asustor Device Manager and navigate to Settings > System > Backup/Restore, or run the command 'ADMVER' via the terminal to retrieve the installed ADM version number
    Affected if The installed version falls within 4.1.0.rhu2 through 4.3.3.rof1, or within 5.0.0.ra82 through 5.1.1.rci1 (versions below 5.1.2.re51)
  2. Verify DDNS service status
    In ADM, go to Access Control > DDNS or run 'ls' command in /usr/local/etc/ddns/ to see if any DDNS providers are configured
    Affected if Any DDNS provider is actively configured or enabled on the device
  3. Confirm DDNS update protocol
    Inspect the DDNS configuration in ADM under Access Control > DDNS, or examine the configuration file in /usr/local/etc/ddns/ to determine if HTTPS/SSL is selected as the update method
    Affected if HTTPS/SSL update method is selected for any DDNS provider (the vulnerability applies specifically to HTTPS connections)

The environment is affected if the ADM version is within the vulnerable ranges AND DDNS is configured with HTTPS updates enabled, as only HTTPS connections trigger the certificate hostname validation flaw.

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 5.1.2.re51 or later
Fixed in 5.1.2.re51
Interim mitigation

Update ADM to a patched version beyond 4.3.3.ROF1 or 5.1.1.RCI1 that implements proper TLS certificate hostname validation, or temporarily disable DDNS updates until the patch can be applied.

Recommended fix Moderate confidence

ADM 5.1.2.re51 or later (for 5.x branch); ADM 4.3.4 or later (for 4.x branch)

  1. 1. Identify the current ADM version installed on the ASUSTOR device via the ADM dashboard (Settings > System > Maintenance > Backup/Restore).
  2. 2. If running version 4.1.0.rhu2 through 4.3.3.rof1, plan upgrade to the latest 4.3.x release or later.
  3. 3. If running version 5.0.0.ra82 through 5.1.1.RCI1, plan upgrade to version 5.1.2.re51 or later.
  4. 4. Before upgrading, backup the ADM configuration via Settings > System > Maintenance > Backup/Restore.
  5. 5. Download the firmware update from the official ASUSTOR support page (www.asustor.com/service/downloads).
  6. 6. Install the firmware update via Settings > System > Firmware Update in ADM, or manually upload the .adm file.
  7. 7. After reboot, verify the DDNS update function works correctly and confirm the new version is installed.
Caveat Firmware upgrades may temporarily disrupt services; ensure proper backup before proceeding

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

Fix this in Data Master Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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