Cyber Resilience

CVE-2024-10442

Synology Replication Service ≤ 1.0.12-0066

Published
19 March 2025
Modified
16 January 2026
Patch / advisory
View advisory
CVSS Score v3.1 10.0
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
EPSS Score 0.013 69th percentile
Risk Priority 84 floored blend · peak EPSS

Summary

CVE-2024-10442 is a critical-severity Off-by-one Error (CWE-193) vulnerability in Synology Diskstation Manager. Its CVSS base score is 10.0 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 31% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2024-10442 is an off-by-one error vulnerability (CWE-193) in the transmission component of Synology Replication Service versions prior to 1.0.12-0066, 1.2.2-0353, and 1.3.0-0423, as well as Synology Unified Controller (DSMUC) versions prior to 3.1.4-23079. The flaw carries a CVSS 3.1 score of 10.0 and permits remote code execution with full system impact across confidentiality, integrity, and availability.

Unauthenticated attackers with network access can exploit the issue without user interaction to run arbitrary code on affected systems, potentially compromising the broader environment through unspecified vectors.

The official Synology advisory Synology_SA_24_22 recommends updating Replication Service and DSMUC to the fixed releases listed above to address the vulnerability.

The associated EPSS score remains flat at 0.1459 with no material increase observed since disclosure.

EU & UK References

Vulnerability Data

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…

more

unspecified vectors.

CWE(s)
CWE-193

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
attack.mitre.org →
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2021-3156Same product: Synology Diskstation Manager
CVE-2024-45539Same product: Synology Diskstation Manager
CVE-2023-28709Same product class: NAS / storage appliance
CVE-2024-29231Same product: Synology Diskstation Manager
CVE-2024-45538Same product: Synology Diskstation Manager
CVE-2024-39349Same product class: NAS / storage appliance
CVE-2024-5463Same product class: NAS / storage appliance
CVE-2023-5748Same product class: NAS / storage appliance
CVE-2025-12686Same product class: NAS / storage appliance
CVE-2023-52946Same product class: NAS / storage appliance

Affected Assets

synology
unified controller
≤ 3.1.4-23079
synology
replication service
≤ 1.0.12-0066 · ≤ 1.2.2-0353
syncology
replication service
≤ 1.3.0-0423

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V6.2.1

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation can discover off-by-one errors in loops, bounds, and calculations before deployment.

SA-15 Development Process, Standards, and Tools partial match

Requiring documented development standards and tools can embed bounds-checking and arithmetic-correctness rules that stop off-by-one mistakes at introduction.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly prevent off-by-one errors via reviews, static analysis, and testing.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development and acceptance can detect off-by-one errors before release.

A.8.25 Secure development life cycle partial match
prevents

Secure development life cycle includes requirements and reviews that can catch off-by-one errors.

A.8.26 Application security requirements partial match
prevents

Application security requirements can specify bounds-checking and input validation to prevent off-by-one errors.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure system architecture and engineering principles promote defensive coding practices that reduce off-by-one mistakes.

A.8.28 Secure coding partial match
prevents

Secure coding directly addresses off-by-one errors through coding standards and peer review.

References