dbcve.org
Router ManagerApplication · Synology

CVE-2023-32955

HIGH · 8.1 CVSS v3.1 Published 2023-05-16
Fix available
A fix is available. Upgrade to 1.2.5-8227-6 / 1.3.1-9346-3 or later.
See remediation →
90/100
Remediation priority · Urgent
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
Improper neutralization of special elements used in an OS command ('OS Command Injection') vulnerability in DHCP Client Functionality in Synology Router Manager (SRM) before 1.2.5-8227-6 and 1.3.1-9346-3 allows man-in-the-middle attackers to execute arbitrary commands 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

OS command injection vulnerability in the DHCP client functionality of Synology Router Manager. An attacker positioned as man-in-the-middle can inject arbitrary OS commands through unspecified vectors in the DHCP client processing, likely due to improper sanitization of DHCP response data before passing it to system shell commands.

MitigationApply the vendor-supplied firmware update to SRM version 1.2.5-8227-6 (for 1.2.x branches) or 1.3.1-9346-3 (for 1.3.x branches) or later. Until patched, restrict physical and network access to the broadcast domain to limit MITM attack opportunities.

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
Router ManagerApplication
Affected:>= 1.2, < 1.2.5-8227-6>= 1.3, < 1.3.1-9346-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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/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. Check Synology Router Manager version via web interface
    Log into the SRM web interface, navigate to Control Panel > System > Information, and locate the firmware version displayed under 'Software Information'.
    Affected if The version is >= 1.2 and < 1.2.5-8227-6, or >= 1.3 and < 1.3.1-9346-3
  2. Check SRM version via command line
    Access the router via SSH and run the command: cat /etc.defaults/VERSION | grep -E 'productversion|buildnumber'
    Affected if The version is >= 1.2 and < 1.2.5-8227-6, or >= 1.3 and < 1.3.1-9346-3
  3. Verify DHCP client is in use
    Check if the router is configured to obtain IP settings via DHCP from an upstream ISP or network. In SRM web interface, go to Network Center > Internet > WAN > Type and confirm it is set to 'Automatic (DHCP)'.
    Affected if The router uses DHCP on any WAN or LAN interface, making the DHCP client processing active and potentially exploitable

The system is affected if SRM version falls within the vulnerable ranges (1.2.x before 1.2.5-8227-6 or 1.3.x before 1.3.1-9346-3) AND the DHCP client feature is enabled on the router.

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.2.5-8227-6 / 1.3.1-9346-3 or later
Fixed in 1.2.5-8227-61.3.1-9346-3
Interim mitigation

Apply the vendor-supplied firmware update to SRM version 1.2.5-8227-6 (for 1.2.x branches) or 1.3.1-9346-3 (for 1.3.x branches) or later. Until patched, restrict physical and network access to the broadcast domain to limit MITM attack opportunities.

Recommended fix High confidence

1.2.5-8227-6 (for 1.2.x branch) or 1.3.1-9346-3 (for 1.3.x branch)

  1. 1. Log into the Synology Router Manager (SRM) web interface.
  2. 2. Navigate to Control Panel > System > DSM Update (or check the current version in Help > About).
  3. 3. Identify your current SRM version - if it starts with 1.2.x, you are on the 1.2 branch; if it starts with 1.3.x, you are on the 1.3 branch.
  4. 4. For SRM 1.2.x versions: Update to version 1.2.5-8227-6 or later.
  5. 5. For SRM 1.3.x versions: Update to version 1.3.1-9346-3 or later.
  6. 6. Use the built-in DSM Update function to download and install the appropriate update from Synology.
  7. 7. After update completes, verify the new version is installed by checking Help > About.

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

Fix this in Router Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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