dbcve.org
Diskstation Manager Unified ControllerApplication · Synology

CVE-2023-2729

HIGH · 7.5 CVSS v3.1 Published 2023-06-13
Fix available
A fix is available. Upgrade to 1.3.1-9346 / 7.2-64561 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
Use of insufficiently random values vulnerability in User Management Functionality in Synology DiskStation Manager (DSM) before 7.2-64561 allows remote attackers to obtain user credential 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

Synology DSM contains a vulnerability in its User Management functionality where insufficiently random values (likely session tokens, authentication tokens, or password reset codes) are generated. Remote attackers can exploit this predictability to obtain user credentials without authentication, enabling account takeover.

MitigationUpgrade Synology DSM to version 7.2-64561 or later to remediate the insufficient randomness vulnerability in the user management component.

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 Manager Unified ControllerApplication
Affected:= 3.1
Router ManagerApplication
Affected:>= 1.2, < 1.3.1-9346= 1.3.1-9346
Diskstation ManagerOperating system
Affected:>= 6.2, < 7.2-64561

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

CVSS:3.1/AV:N/AC:L/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. Identify the Synology product type
    Access the web interface and check the product name in the control panel, or run `cat /etc/VERSION` from the command line to see if the device is running DiskStation Manager (DSM), Synology Router Manager (SRM), or DiskStation Manager Unified Controller (DUC)
    Affected if The device is running DSM, SRM, or DUC (any of these products are potentially affected)
  2. Check DiskStation Manager version
    In the DSM web interface, go to Control Panel > Help & Support > About to view the exact version number. From command line, run `cat /etc/VERSION` and look for the `productversion` field
    Affected if DSM version is 6.2 or higher but lower than 7.2-64561 (versions 6.2 through 7.2-64560 are affected)
  3. Check Synology Router Manager version
    In the SRM web interface, go to Control Panel > Help & Support > About to view the exact version. From command line, run `cat /etc/VERSION` and look for the `productversion` field
    Affected if SRM version is 1.2 or higher but lower than 1.3.1-9346, or exactly 1.3.1-9346 (these specific versions are affected)
  4. Check DiskStation Manager Unified Controller version
    In the DUC web interface, go to Control Panel > Help & Support > About to view the version. From command line, run `cat /etc/VERSION` and look for the `productversion` field
    Affected if DUC version is exactly 3.1 (this specific version is affected)

The environment is affected if running DSM versions 6.2 through 7.2-64560, SRM versions 1.2 through 1.3.1-9345 (or exactly 1.3.1-9346), or DUC version 3.1.

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 1.3.1-9346 / 7.2-64561 or later
Fixed in 1.3.1-93467.2-64561
Interim mitigation

Upgrade Synology DSM to version 7.2-64561 or later to remediate the insufficient randomness vulnerability in the user management component.

Recommended fix Moderate confidence

DSM 7.2-64561 or later; Router Manager 1.3.1-9347 or later; DSM Unified Controller - contact vendor

  1. 1. Identify the exact Synology product and current version running (DSM, Router Manager, or DSM Unified Controller)
  2. 2. For DiskStation Manager (DSM): Backup all data and configurations
  3. 3. For DiskStation Manager (DSM): Access the Control Panel > Update & Restore > DSM Update
  4. 4. For DiskStation Manager (DSM): Update to DSM version 7.2-64561 or later
  5. 5. For Router Manager: Update to SRM version 1.3.1-9347 or later (the next version after 1.3.1-9346)
  6. 6. For DSM Unified Controller: Contact Synology support for specific guidance on version 3.1 remediation
  7. 7. After update, verify the system is running the patched version via Control Panel > About
Caveat Major DSM updates may require data migration review; backup before upgrading

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

Fix this in Diskstation Manager Unified Controller Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
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,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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