Bc500 FirmwareOperating system · Synology

CVE-2023-47802

HIGH · 7.2 CVSS v3.1 Published 2024-06-28
Fix available
A fix is available. Upgrade to 1.0.7-0298 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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 improper neutralization of special elements used in an OS command ('OS Command Injection') is found in the IP block functionality. This allows remote authenticated users with administrator privileges to execute arbitrary commands via unspecified vectors. The following models with Synology Camera Firmware versions before 1.0.7-0298 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

The IP block functionality in Synology BC500 and TC500 camera firmware lacks proper input sanitization, allowing an authenticated administrator to inject arbitrary OS commands through unspecified vectors. This command injection occurs due to improper neutralization of special elements in user-supplied input processed by the IP block feature.

MitigationUpdate Synology BC500 and TC500 camera firmware to version 1.0.7-0298 or later to patch the vulnerability. As a compensating control, limit administrative access to trusted personnel only and monitor for suspicious command execution.

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.7-0298
Tc500 FirmwareOperating system
Affected:< 1.0.7-0298

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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 camera model
    Access the device web interface or check the physical device label to confirm the model is Synology BC500 or TC500
    Affected if The device is a Synology BC500 or TC500 camera
  2. Check the installed firmware version
    Log into the camera admin panel and navigate to System > Firmware/About, or use SSH to run 'cat /etc/version' or check the web interface version display
    Affected if The firmware version is lower than 1.0.7-0298 (for example, 1.0.6-xxxx or earlier)
  3. Verify the IP Block feature is accessible
    Log in as administrator and navigate to Network Security or Access Control settings in the web interface to confirm the IP Block functionality exists and is configurable
    Affected if The IP Block feature is present and the administrator account has access to configure it

A user is affected if they have a Synology BC500 or TC500 camera running firmware version lower than 1.0.7-0298 with the IP Block feature accessible to an authenticated administrator.

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.7-0298 or later
Fixed in 1.0.7-0298
Interim mitigation

Update Synology BC500 and TC500 camera firmware to version 1.0.7-0298 or later to patch the vulnerability. As a compensating control, limit administrative access to trusted personnel only and monitor for suspicious command execution.

Recommended fix High confidence

Firmware 1.0.7-0298 or later for BC500 and TC500

  1. Download the Synology BC500 or TC500 firmware version 1.0.7-0298 or later from the official Synology website
  2. Log into the camera's web management interface as administrator
  3. Navigate to the System or Maintenance section of the camera settings
  4. Locate the Firmware Update or Software Update option
  5. Upload and apply the new firmware version
  6. Verify the firmware update was successful and the camera is functioning normally

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

Fix this in Bc500 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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