dbcve.org
Diskstation ManagerOperating system · Synology

CVE-2024-45539

HIGH · 7.5 CVSS v3.1 Published 2025-12-04
Fix available
A fix is available. Upgrade to 3.1.4-23079 / 7.2.1-69057-2 or later.
See remediation →
84/100
Remediation priority · High
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
Out-of-bounds write vulnerability in cgi components in Synology DiskStation Manager (DSM) before 7.2.1-69057-2 and 7.2.2-72806 and Synology Unified Controller (DSMUC) before 3.1.4-23079 allows remote attackers to conduct denial-of-service attacks 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 · moderate confidence

An out-of-bounds write vulnerability exists in the CGI components of Synology DiskStation Manager (DSM) and Synology Unified Controller (DSMUC). The flaw allows remote, unauthenticated attackers to write data beyond allocated memory boundaries via unspecified vectors, causing denial of service.

MitigationApply vendor-supplied updates: upgrade DSM to version 7.2.1-69057-2 or 7.2.2-72806 (or later), or DSMUC to version 3.1.4-23079 or later.

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.2.1-69057, < 7.2.1-69057-2>= 7.2.2-72803, < 7.2.2-72806
Diskstation Manager Unified ControllerOperating system
Affected:>= 3.1-23028, < 3.1.4-23079

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 product type
    Log into the Synology device and check the main dashboard, or run 'cat /proc/version' or 'uname -a' via SSH to determine if the device runs DSM (DiskStation Manager) or DSMUC (DiskStation Manager Unified Controller)
    Affected if Device runs DSM or DSMUC and is accessible over the network
  2. Check DSM version number
    In DSM web interface: open Control Panel > System > Overview to view the version. Via SSH: run 'cat /etc/VERSION' or 'synoget --version'
    Affected if DSM version is 7.2.1-69057 through 7.2.1-69057-1, OR 7.2.2-72803 through 7.2.2-72805
  3. Check DSMUC version number
    In DSMUC web interface: navigate to the system information page. Via SSH: run 'cat /etc/VERSION' or check the unified controller version file
    Affected if DSMUC version is 3.1-23028 through 3.1.4-23078
  4. Verify CGI component exposure
    Confirm that the CGI web interface is accessible externally or on the local network by checking the web server configuration or testing access to /cgi-bin/ endpoints
    Affected if CGI components are exposed and the version falls within affected ranges

The environment is affected if the installed DSM version is 7.2.1-69057 through 7.2.1-69057-1 or 7.2.2-72803 through 7.2.2-72805, or if DSMUC version is 3.1-23028 through 3.1.4-23078.

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 3.1.4-23079 / 7.2.1-69057-2 / 7.2.2-72806 or later
Fixed in 3.1.4-230797.2.1-69057-27.2.2-72806
Interim mitigation

Apply vendor-supplied updates: upgrade DSM to version 7.2.1-69057-2 or 7.2.2-72806 (or later), or DSMUC to version 3.1.4-23079 or later.

Recommended fix High confidence

DSM 7.2.1-69057-2 or DSM 7.2.2-72806 (for DiskStation Manager); DSMUC 3.1.4-23079 (for Unified Controller)

  1. Identify the current DSM version by checking System Information in the control panel
  2. For DSM 7.2.1 branch (versions 7.2.1-69057 through 7.2.1-69057-1): Upgrade to version 7.2.1-69057-2
  3. For DSM 7.2.2 branch (versions 7.2.2-72803 through 7.2.2-72805): Upgrade to version 7.2.2-72806
  4. For DSM Unified Controller (versions 3.1-23028 through 3.1.4-23078): Upgrade to version 3.1.4-23079
  5. Download the update from Synology's Download Center or use the built-in Update & Restore > DSM Update function
  6. Perform the upgrade following Synology's standard update procedures
  7. After upgrade, verify the system is running the patched version
Caveat Point release upgrades typically have minimal breaking changes; review Synology release notes for any known issues before updating

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