dbcve.org
Router ManagerApplication · Synology

CVE-2023-41738

HIGH · 8.8 CVSS v3.1 Published 2023-08-31
Fix available
A fix is available. Upgrade to 1.3.1-9346-6 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 Directory Domain Functionality in Synology Router Manager (SRM) before 1.3.1-9346-6 allows remote authenticated users 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 · high confidence

OS Command Injection vulnerability in the Directory Domain Functionality of Synology Router Manager (SRM) versions prior to 1.3.1-9346-6 allows remote authenticated users to execute arbitrary operating system commands through unspecified vectors. The vulnerability requires authentication but can be exploited remotely, giving attackers the ability to run commands with the privileges of the affected SRM service.

MitigationUpdate Synology Router Manager to version 1.3.1-9346-6 or later to remediate this vulnerability. If immediate patching is not possible, restrict access to the SRM management interface to trusted users only and monitor for unauthorized 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
Router ManagerApplication
Affected:< 1.3.1-9346-6

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

CVSS:3.1/AV:N/AC:L/PR:L/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 installed SRM version
    Access the SRM web interface and navigate to Control Panel > System > Update & Restore, or use the command line and check /etc/version or the DSM version information via the web UI
    Affected if The installed version is any release prior to 1.3.1-9346-6
  2. Verify Directory Domain functionality status
    Check if the Directory Domain (Domain Controller) feature is enabled in SRM under Control Panel > Domain/LDAP > Directory Service or similar domain-related settings
    Affected if The Directory Domain feature is actively configured or enabled on the SRM device
  3. Review SRM user accounts
    Inspect the list of users with access to SRM management interface in Control Panel > User & Group to identify any unauthorized or suspicious accounts
    Affected if Unknown or unauthorized user accounts exist in the SRM user database
  4. Examine running processes
    Use SSH to access SRM and review running processes using ps aux or similar process listing tools for unexpected shell scripts or network-related executables
    Affected if Unfamiliar processes are running, especially shell scripts or network listeners that were not intentionally deployed
  5. Check authentication logs
    Review SRM system logs or /var/log/syno_authd.log for authentication events, looking for successful logins from unfamiliar IP addresses or at unusual times
    Affected if Authentication logs show login attempts or successful accesses from IP addresses you do not recognize

You are affected if your SRM version is below 1.3.1-9346-6 AND the Directory Domain functionality is enabled or was recently used.

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-6 or later
Fixed in 1.3.1-9346-6
Interim mitigation

Update Synology Router Manager to version 1.3.1-9346-6 or later to remediate this vulnerability. If immediate patching is not possible, restrict access to the SRM management interface to trusted users only and monitor for unauthorized access.

Recommended fix High confidence

1.3.1-9346-6

  1. Log in to Synology Router Manager (SRM) as administrator
  2. Navigate to Control Panel > Update & Restore > DSM Update
  3. Check for available updates - the fix is included in version 1.3.1-9346-6
  4. Download and install the update to patch the OS Command Injection vulnerability
  5. After update, verify the SRM version shows 1.3.1-9346-6 or later
Caveat Review release notes for any configuration changes; backup SRM settings before updating

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
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,950
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,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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