dbcve.org
Router ManagerOperating system · Synology

CVE-2024-39347

MEDIUM · 5.9 CVSS v3.1 Published 2024-06-28
Fix available
A fix is available. Upgrade to 1.2.5-8227 / 1.3.1-9346 or later.
See remediation →
68/100
Remediation priority · Elevated
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
Incorrect default permissions vulnerability in firewall functionality in Synology Router Manager (SRM) before 1.2.5-8227-11 and 1.3.1-9346-8 allows man-in-the-middle attackers to access highly sensitive intranet resources 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

Vulnerability in Synology Router Manager (SRM) firewall functionality involves incorrect default permissions that could allow man-in-the-middle attackers to bypass firewall controls and access highly sensitive intranet resources. The exact nature of the permission misconfiguration is unspecified in the advisory.

MitigationUpdate SRM to version 1.2.5-8227-11 or 1.3.1-9346-8 or later to remediate. Additionally, review firewall rules and monitor for signs of lateral movement given the high-sensitivity nature of the compromised resources.

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 ManagerOperating system
Affected:>= 1.2, < 1.2.5-8227>= 1.3, < 1.3.1-9346= 1.2.5-8227= 1.3.1-9346

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

CVSS:3.1/AV:N/AC:H/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 SRM version
    Log into the Synology Router Manager web interface and navigate to Control Panel > System > Security > Hardware & Power, or run `get_key_value /etc/synoinfo.conf version` via SSH to retrieve the installed SRM version
    Affected if The installed version falls within 1.2.x through 1.2.5-8227, or 1.3.x through 1.3.1-9346 (i.e., versions earlier than 1.2.5-8227-11 or 1.3.1-9346-8)
  2. Verify the firewall is active
    In the SRM web interface, navigate to Control Panel > Security > Firewall to confirm the firewall is enabled, or run `iptables -L -n` via SSH to list active firewall rules
    Affected if The firewall is enabled and the device is on an affected SRM version
  3. Review firewall rule configuration
    In the SRM web interface, go to Control Panel > Security > Firewall > Create > Create firewall rule and inspect the ruleset, particularly rules that govern inbound access to internal network segments
    Affected if The device runs an affected SRM version with firewall rules permitting access to sensitive internal resources (e.g., internal subnets, management interfaces)

A user is affected if their SRM version is 1.2.x through 1.2.5-8227 or 1.3.x through 1.3.1-9346 and the firewall functionality is enabled with rules that could expose sensitive intranet resources.

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

Update SRM to version 1.2.5-8227-11 or 1.3.1-9346-8 or later to remediate. Additionally, review firewall rules and monitor for signs of lateral movement given the high-sensitivity nature of the compromised resources.

Recommended fix High confidence

1.2.5-8227-11 or 1.3.1-9346-8 (depending on your current major version branch)

  1. 1. Access Synology Router Manager (SRM) web interface
  2. 2. Navigate to Control Panel > System > Update & Restore
  3. 3. Check the current SRM version under 'DSM/SRM Update'
  4. 4. If running version 1.2.x (< 1.2.5-8227-11), initiate update to version 1.2.5-8227-11 or later
  5. 5. If running version 1.3.x (< 1.3.1-9346-8), initiate update to version 1.3.1-9346-8 or later
  6. 6. Allow the update to complete and verify the new version after reboot
Caveat Standard SRM update - ensure backup of router configuration before updating

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

Fix this in Router Manager Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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