Tc500 FirmwareOperating system · Synology

CVE-2024-11131

CRITICAL · 9.8 CVSS v3.1 Published 2025-03-19
Fix available
A fix is available. Upgrade to 1.2.0-0525 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
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.

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 out-of-bounds read vulnerability exists in the video interface of Synology BC500, CC400W, and TC500 camera firmware versions prior to 1.2.0-0525. This memory corruption issue allows remote attackers to execute arbitrary code without authentication, earning a critical CVSS score of 9.8.

MitigationUpgrade all affected Synology camera models (BC500, CC400W, TC500) to firmware version 1.2.0-0525 or later to remediate the out-of-bounds read vulnerability.

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
Tc500 FirmwareOperating system
Affected:< 1.2.0-0525
Cc400w FirmwareOperating system
Affected:< 1.2.0-0525
Bc500 FirmwareOperating system
Affected:< 1.2.0-0525

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

CVSS:3.1/AV:N/AC:L/PR:N/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 camera model
    Locate the Synology camera model number on the physical device label or in the device's web interface under System Information or Device Status.
    Affected if The model is BC500, CC400W, or TC500.
  2. Check firmware version
    Access the camera web interface and navigate to System > Firmware or System > About. Alternatively, use the Synology app or SSH to the device and run: cat /etc/os-release or look for version info in the system settings.
    Affected if The displayed firmware version is lower than 1.2.0-0525.
  3. Confirm video interface is enabled
    In the camera web interface, verify that the video streaming or RTSP service is enabled under Network Settings or Streaming Settings.
    Affected if Video interface streaming is active, as this is the vulnerable component.
  4. Assess network exposure
    Check if the camera's web interface or video ports (typically 80, 443, 554 for RTSP) are exposed to untrusted networks. Review router/firewall rules and camera network configuration.
    Affected if The camera is directly accessible from the internet or untrusted networks without proper firewall segmentation.

You are affected if you have a BC500, CC400W, or TC500 camera running firmware version lower than 1.2.0-0525 with the video interface enabled and 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.0-0525 or later
Fixed in 1.2.0-0525
Interim mitigation

Upgrade all affected Synology camera models (BC500, CC400W, TC500) to firmware version 1.2.0-0525 or later to remediate the out-of-bounds read vulnerability.

Recommended fix High confidence

1.2.0-0525

  1. Download firmware version 1.2.0-0525 or later for your specific camera model (TC500, CC400W, or BC500) from the official Synology download center
  2. Log in to the Synology Surveillance Station or the camera's web interface
  3. Navigate to the camera settings or firmware update section
  4. Upload and install the downloaded firmware file
  5. After the update completes, verify the firmware version displays as 1.2.0-0525 or later to confirm the patch was applied

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

Fix this in Tc500 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-11131 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-11131 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