dbcve.org
Unified ControllerApplication · Synology

CVE-2024-10442

CRITICAL · 10.0 CVSS v3.1 Published 2025-03-19
Fix available
A fix is available. Upgrade to 1.2.2-0353 / 1.3.0-0423 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
Off-by-one error vulnerability in the transmission component in Synology Replication Service before 1.0.12-0066, 1.2.2-0353 and 1.3.0-0423 and Synology Unified Controller (DSMUC) before 3.1.4-23079 allows remote attackers to execute arbitrary code, potentially leading to a broader impact across the system 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

An off-by-one error in the transmission component of Synology Replication Service (versions before 1.0.12-0066, 1.2.2-0353, 1.3.0-0423) and Synology Unified Controller (before 3.1.4-23079) allows remote attackers to execute arbitrary code. The vulnerability stems from incorrect bounds checking in the transmission handling logic, which can be exploited to overwrite memory boundaries and achieve code execution.

MitigationUpdate Synology Replication Service to version 1.0.12-0066, 1.2.2-0353, or 1.3.0-0423 (depending on your release line) and DSMUC to version 3.1.4-23079 or later. If immediate patching is not possible, restrict network access to the replication service ports and disable the service if not required.

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
Unified ControllerApplication
Affected:< 3.1.4-23079
Replication ServiceApplication
Affected:<= 1.0.12-0066< 1.2.2-0353
Replication ServiceApplication
Affected:< 1.3.0-0423

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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 Synology Unified Controller version
    Access DSM and navigate to Control Panel > Update & Restore > DSM Update, or check the version via the help menu (Help > About). Record the full version number including the build number (e.g., 3.1.4-23079).
    Affected if The installed version is less than 3.1.4-23079.
  2. Identify installed Synology Replication Service version
    Open Package Center in DSM, locate Synology Replication Service in the installed packages list, and note the version number shown.
    Affected if The installed version is 1.0.12-0066 or lower, or is between 1.0.12-0067 and 1.2.2-0352, or is between 1.2.2-0353 and 1.3.0-0422.
  3. Verify if Replication Service is currently enabled
    Open Storage Manager or the replication service settings panel in DSM and confirm whether the replication service is actively running or enabled for any replication tasks.
    Affected if The replication service is running or enabled, and the version falls within any of the affected ranges.
  4. Check network exposure of replication service ports
    Access DSM Control Panel > Security > Firewall and review the firewall rules. Identify any rules allowing inbound access to the ports used by the replication service (commonly port 5550 or configured replication ports).
    Affected if The replication service ports are open to untrusted networks or the internet, and the service version is vulnerable.

You are affected if Synology Unified Controller is below version 3.1.4-23079 or Synology Replication Service is at or below 1.0.12-0066, below 1.2.2-0353, or below 1.3.0-0423, AND the replication service is enabled and network-accessible.

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.2-0353 / 1.3.0-0423 / 3.1.4-23079 or later
Fixed in 1.2.2-03531.3.0-04233.1.4-23079
Interim mitigation

Update Synology Replication Service to version 1.0.12-0066, 1.2.2-0353, or 1.3.0-0423 (depending on your release line) and DSMUC to version 3.1.4-23079 or later. If immediate patching is not possible, restrict network access to the replication service ports and disable the service if not required.

Recommended fix High confidence

Unified Controller: 3.1.4-23079 or later; Replication Service: 1.0.12-0066, 1.2.2-0353, or 1.3.0-0423 (depending on branch)

  1. 1. Identify the exact version of Synology Unified Controller (DSMUC) currently installed
  2. 2. Identify the exact version of Synology Replication Service currently installed
  3. 3. For Unified Controller: Upgrade to version 3.1.4-23079 or later
  4. 4. For Replication Service versions <= 1.0.12-0066: Upgrade to version 1.0.12-0066 or later (or migrate to a supported branch)
  5. 5. For Replication Service versions > 1.0.12-0066 but < 1.2.2-0353: Upgrade to version 1.2.2-0353 or later
  6. 6. For Replication Service versions >= 1.2.2-0353 but < 1.3.0-0423: Upgrade to version 1.3.0-0423 or later
  7. 7. After upgrade, verify the new version numbers are correctly reported in the Synology admin interface
  8. 8. Test that replication functionality continues to work as expected
Caveat Review Synology release notes for the target version to check for any configuration or feature changes that may affect existing replication jobs

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

Fix this in Unified Controller Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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