dbcve.org
Bc500 FirmwareOperating system · Synology

CVE-2023-5746

CRITICAL · 9.8 CVSS v3.1 Published 2023-10-25
Fix available
A fix is available. Upgrade to 1.0.5-0185 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 use of externally-controlled format string is found in the cgi component. This allows remote attackers to execute arbitrary code via unspecified vectors. The following models with Synology Camera Firmware versions before 1.0.5-0185 may be affected: BC500 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

A format string vulnerability exists in the CGI component of Synology BC500 and TC500 camera firmware versions prior to 1.0.5-0185. The vulnerability allows remote attackers to control format strings passed to vulnerable functions, potentially enabling memory manipulation and arbitrary code execution.

MitigationUpdate affected camera firmware to version 1.0.5-0185 or later. If immediate patching is not possible, restrict network access to camera management interfaces and monitor for exploitation attempts.

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
Bc500 FirmwareOperating system
Affected:< 1.0.5-0185
Tc500 FirmwareOperating system
Affected:< 1.0.5-0185

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 the device model
    Access the camera's web interface or administrative panel and locate the device information page to confirm the model is Synology BC500 or TC500
    Affected if Device model is BC500 or TC500
  2. Check the installed firmware version
    In the camera's web interface, navigate to Configuration or System settings to view the firmware version. Alternatively, access the camera via SSH or the Synology utility and run: cat /etc/os-release or look for version information in the system settings
    Affected if Firmware version is lower than 1.0.5-0185 (e.g., 1.0.5-0180, 1.0.4-xxxx, etc.)
  3. Confirm CGI component is exposed
    Verify that the camera's CGI interface is accessible on the network. Attempt to access a common CGI endpoint such as http://[camera-ip]/cgi-bin/ or check network exposure of the management interface
    Affected if CGI component is network-accessible (required for remote exploitation)
  4. Review authentication and access controls
    Check if the camera management interface is protected by strong authentication and if network access is restricted to trusted IPs or VPN
    Affected if Camera management interface has weak or no access controls

If the device is a Synology BC500 or TC500 with firmware version prior to 1.0.5-0185 and the CGI component is network-accessible, the environment is affected by this vulnerability.

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.0.5-0185 or later
Fixed in 1.0.5-0185
Interim mitigation

Update affected camera firmware to version 1.0.5-0185 or later. If immediate patching is not possible, restrict network access to camera management interfaces and monitor for exploitation attempts.

Recommended fix High confidence

BC500 and TC500 Firmware 1.0.5-0185 or later

  1. Identify all BC500 and TC500 camera devices on the network requiring updates
  2. Access the Synology camera web management interface or Synology Surveillance Station
  3. Navigate to the firmware update section (typically under System > Firmware or Maintenance > Update)
  4. Check the current firmware version of each camera device
  5. Download firmware version 1.0.5-0185 or later from the official Synology download center (www.synology.com)
  6. Apply the firmware update to each affected BC500 and TC500 camera
  7. Verify that each device has been successfully updated to firmware version 1.0.5-0185 or later
  8. Test that the cgi component functions normally after the security update

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

Fix this in Bc500 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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