dbcve.org
Router ManagerApplication · Synology

CVE-2023-32956

CRITICAL · 9.8 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 →
100/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 CGI component in Synology Router Manager (SRM) before 1.2.5-8227-6 and 1.3.1-9346-3 allows remote attackers to execute arbitrary code 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

OS command injection vulnerability in the CGI component of Synology Router Manager allows remote unauthenticated attackers to execute arbitrary OS commands by injecting malicious commands through unspecified vectors. This is a pre-authentication flaw with critical severity (CVSS 9.8).

MitigationUpdate Synology Router Manager to version 1.2.5-8227-6 or 1.3.1-9346-3 or later to remediate the vulnerability. If immediate patching is not possible, restrict external access to the SRM web interface via firewall rules.

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

CVSS:3.1/AV:N/AC:L/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. Identify SRM version via web interface
    Log into the Synology Router Manager web interface and navigate to Control Panel > System > Information to view the firmware version
    Affected if The version displayed is 1.2.x (any build before 8227-6) or 1.3.x (any build before 9346-3)
  2. Identify SRM version via command line
    Access the router via SSH and run 'cat /etc/VERSION' to retrieve the exact version and build number
    Affected if The version output shows a build number less than 8227-6 for the 1.2 branch or less than 9346-3 for the 1.3 branch
  3. Confirm CGI component is network-accessible
    Verify that the SRM web interface (which hosts the CGI component) is reachable from external or untrusted network segments
    Affected if The SRM web interface is exposed to the internet or untrusted networks without firewall filtering

If your SRM version is 1.2.x with build before 8227-6 or 1.3.x with build before 9346-3 AND the web interface is network-accessible, you are affected by this pre-authentication command injection vulnerability.

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

Update Synology Router Manager to version 1.2.5-8227-6 or 1.3.1-9346-3 or later to remediate the vulnerability. If immediate patching is not possible, restrict external access to the SRM web interface via firewall rules.

Recommended fix High confidence

Upgrade to SRM 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 Synology Router Manager (SRM) web interface
  2. 2. Go to Control Panel > System > DSM Update or check the current version in Control Panel > System Information
  3. 3. Identify your current version branch (1.2.x or 1.3.x)
  4. 4. For version 1.2.x: Upgrade to version 1.2.5-8227-6 or later
  5. 5. For version 1.3.x: Upgrade to version 1.3.1-9346-3 or later
  6. 6. Download the appropriate update from Synology's support website if not available via auto-update
  7. 7. Apply the update via Control Panel > System > DSM Update > Manual DSM Update
  8. 8. Verify the installation was successful by checking the version in Control Panel > System Information
Caveat SRM upgrades may reset some network configurations; ensure you have a backup of critical settings

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

Fix this in Router Manager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,800
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,880.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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