Cyber Resilience

CVE-2024-11131

Memory Safety in Synology Bc500 Firmware ≤ 1.2.0-0525

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

Summary

CVE-2024-11131 is a critical-severity Out-of-bounds Read (CWE-125) vulnerability in Synology Bc500 Firmware. Its CVSS base score is 9.8 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 50% 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-8 (Security and Privacy Engineering Principles) — 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.

A vulnerability involving an out-of-bounds read in the video interface allows remote attackers to execute arbitrary code on affected Synology camera devices. The issue impacts BC500, CC400W, and TC500 models running Camera Firmware versions prior to 1.2.0-0525 and carries a CVSS 3.1 score of 9.8.

Unauthenticated attackers with network access can exploit the flaw via unspecified vectors to achieve code execution, potentially compromising the confidentiality, integrity, and availability of the device without requiring user interaction.

The official Synology advisory Synology_SA_24_24 recommends upgrading to firmware version 1.2.0-0525 or later to address the issue.

EPSS scores for the CVE rose from lower values to a peak of 0.1011 on 2026-05-18 before receding to the current level of 0.0552, indicating a period of increased exploitation interest after disclosure.

EU & UK References

Vulnerability Data

A vulnerability regarding out-of-bounds read is found in the video interface. This allows remote attackers to execute arbitrary code via unspecified vectors. The following models with Synology Camera Firmware versions before 1.2.0-0525 may be affected: BC500, CC400W and TC500.

CWE(s)

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.
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.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
T1211 Exploitation for Stealth Stealth
Adversaries may exploit vulnerabilities to evade detection by hiding activity, suppressing logging, or operating within trusted or unmonitored components.
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-5746Same product: Synology Bc500
CVE-2023-38430Same product class: NAS / storage appliance
CVE-2024-56807Same product class: NAS / storage appliance
CVE-2025-54165Same product class: NAS / storage appliance
CVE-2025-52871Same product class: NAS / storage appliance
CVE-2023-38432Same product class: NAS / storage appliance
CVE-2025-29871Same product class: NAS / storage appliance
CVE-2025-54170Same product class: NAS / storage appliance
CVE-2023-26607Same product class: NAS / storage appliance
CVE-2023-1380Same product class: NAS / storage appliance

Affected Assets

synology
bc500 firmware
≤ 1.2.0-0525
synology
cc400w firmware
≤ 1.2.0-0525
synology
tc500 firmware
≤ 1.2.0-0525

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation directly finds out-of-bounds read flaws through static analysis, fuzzing, and dynamic bounds checks.

Secure engineering principles require bounds checking and memory-safe constructs that stop out-of-bounds reads from being introduced.

Process isolation confines the effects of an out-of-bounds read to the compromised process.

Input validation rejects malformed indices or lengths that would otherwise cause reads outside buffer bounds.

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-development practices such as bounds checking and memory-safe languages directly prevent out-of-bounds reads.

ID.RA-01 partial match
prevents

Vulnerability scanning and recording can discover instances of out-of-bounds reads after code is deployed.

PR.PS-02 partial match
prevents

Routine patching replaces vulnerable code containing out-of-bounds read flaws.

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.

finds

Security testing in development and acceptance includes fuzzing and static analysis that detect out-of-bounds read defects before release.

A.8.15 Logging partial match
finds

Logging can record evidence of an out-of-bounds read but does not prevent the weakness itself.

prevents

Secure development life cycle mandates input validation and bounds checking that directly prevent out-of-bounds reads.

prevents

Application security requirements include explicit bounds and memory-safety specifications that mitigate buffer over-reads.

prevents

Secure system architecture and engineering principles require memory-safe design patterns and runtime protections against out-of-bounds access.

prevents

Secure coding standards explicitly forbid unsafe pointer arithmetic and mandate bounds-checked reads, eliminating CWE-125.

References