dbcve.org
Bc500 FirmwareOperating system · Synology

CVE-2023-47803

MEDIUM · 5.3 CVSS v3.1 Published 2024-06-28
Fix available
A fix is available. Upgrade to 1.0.7-0298 or later.
See remediation →
62/100
Remediation priority · Elevated
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 improper limitation of a pathname to a restricted directory ('Path Traversal') is found in the Language Settings functionality. This allows remote attackers to read specific files containing non-sensitive information 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 · moderate confidence

A path traversal vulnerability in the Language Settings functionality of Synology BC500 and TC500 camera firmware versions prior to 1.0.7-0298 allows remote attackers to read specific files containing non-sensitive information through improper path validation.

MitigationUpdate affected camera firmware to version 1.0.7-0298 or later to patch the path traversal vulnerability in the Language Settings functionality.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

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
    Access the camera's web interface or check the device label to confirm the model is Synology BC500 or TC500
    Affected if device is not a BC500 or TC500 model
  2. Check firmware version
    Navigate to the camera's web interface, typically under Settings > System > Firmware, or access the device via SSH and run 'grep -i version /etc/*release' or 'cat /var/log/firmware_version' to retrieve the installed firmware version
    Affected if firmware version is earlier than 1.0.7-0298
  3. Verify Language Settings accessibility
    Attempt to access the Language Settings endpoint on the camera's web interface (typically /language.cgi or similar), or examine the camera's HTTP response headers and available CGI endpoints for language-related functionality
    Affected if Language Settings endpoint is exposed and responds to requests
  4. Confirm web interface exposure
    Check if the camera's web management interface is accessible from the network by attempting to reach its IP address on common ports (80/443)
    Affected if web interface is network-accessible

A user is affected if they own a Synology BC500 or TC500 camera running firmware version earlier than 1.0.7-0298 with the Language Settings functionality accessible on the network.

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 affected camera firmware to version 1.0.7-0298 or later to patch the path traversal vulnerability in the Language Settings functionality.

Recommended fix High confidence

Firmware 1.0.7-0298 or later for BC500 and TC500

  1. 1. Identify the affected device model (BC500 or TC500)
  2. 2. Access the Synology device admin interface
  3. 3. Navigate to the firmware update section (typically under System > Update & Restore)
  4. 4. Download firmware version 1.0.7-0298 or later from the official Synology download center
  5. 5. Apply the firmware update to the device
  6. 6. Verify the firmware version has been updated successfully after reboot

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 / QA1.0 h
10.0 hours of engineering $1,800
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,880.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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