dbcve.org
Diskstation ManagerOperating system · Synology

CVE-2024-10444

HIGH · 7.5 CVSS v3.1 Published 2025-03-19
Fix available
A fix is available. Upgrade to 7.1.1-42962-8 / 7.2.1-69057-7 or later.
See remediation →
82/100
Remediation priority · High
Remotely reachable 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
Improper certificate validation vulnerability in the LDAP utilities in Synology DiskStation Manager (DSM) before 7.1.1-42962-8, 7.2.1-69057-7 and 7.2.2-72806-3 allows man-in-the-middle attackers to hijack the authentication of administrators via unspecified vectors.

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

Improper certificate validation in Synology DSM's LDAP utilities allows man-in-the-middle attackers to intercept LDAP authentication traffic and hijack administrator sessions. The vulnerability stems from the LDAP client not properly validating SSL/TLS certificates from the directory server, enabling credential theft during authentication.

MitigationUpgrade Synology DSM to version 7.1.1-42962-8, 7.2.1-69057-7, or 7.2.2-72806-3 or later to obtain the certificate validation fix. Until patched, avoid LDAP authentication over untrusted networks and use VPN tunnels for directory server access.

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
Diskstation ManagerOperating system
Affected:>= 7.1, < 7.1.1-42962-8>= 7.2.1-69057, < 7.2.1-69057-7>= 7.2.2, < 7.2.2-72806-3

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/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. Check DSM version installed
    Log into DSM, go to Control Panel > System > Version, or run command: cat /etc/VERSION
    Affected if The version falls in any of these ranges: 7.1.x before 7.1.1-42962-8, 7.2.1-69057 before 7.2.1-69057-7, or 7.2.2 before 7.2.2-72806-3
  2. Verify if LDAP client is configured
    Go to Control Panel > Directory Server, or check for LDAP configuration files in /etc or /var directories
    Affected if LDAP client is enabled and connected to a directory server
  3. Check LDAP SSL/TLS certificate validation setting
    In DSM Directory Server settings, examine the SSL/TLS option for LDAP connections. The vulnerability exists when certificate validation is disabled or not enforced.
    Affected if Certificate validation is disabled or set to not verify server certificates for LDAP over SSL/TLS

You are affected if your DSM version is within the affected ranges AND LDAP client is configured with SSL/TLS without proper certificate validation.

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 7.1.1-42962-8 / 7.2.1-69057-7 / 7.2.2-72806-3 or later
Fixed in 7.1.1-42962-87.2.1-69057-77.2.2-72806-3
Interim mitigation

Upgrade Synology DSM to version 7.1.1-42962-8, 7.2.1-69057-7, or 7.2.2-72806-3 or later to obtain the certificate validation fix. Until patched, avoid LDAP authentication over untrusted networks and use VPN tunnels for directory server access.

Recommended fix High confidence

DSM 7.1.1-42962-8 (or later 7.1.x), DSM 7.2.1-69057-7 (or later 7.2.1), or DSM 7.2.2-72806-3 (or later 7.2.2)

  1. Back up all critical data and configurations on the DiskStation before proceeding with any system update.
  2. Log in to DSM as an administrator and navigate to Control Panel > Update & Restore > DSM Update.
  3. Check the current DSM version under Control Panel > About to confirm it falls within an affected version range.
  4. Click 'Download Update' or use Synology Assistant to download the appropriate update package for your model: for DSM 7.1.x, update to 7.1.1-42962-8 or later; for DSM 7.2.1, update to 7.2.1-69057-7 or later; for DSM 7.2.2, update to 7.2.2-72806-3 or later.
  5. Apply the update and restart the DiskStation when prompted.
  6. After the system restarts, verify the new DSM version under Control Panel > About confirms the update was successful.
Caveat Standard DSM update risks apply—ensure backup and review Synology release notes for any configuration or feature changes before applying

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

Fix this in Diskstation Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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