dbcve.org
Bc500 FirmwareOperating system · Synology

CVE-2024-39351

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 NTP configuration. 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

An OS command injection vulnerability exists in the NTP configuration of Synology BC500 and TC500 IP cameras. Remote authenticated attackers with administrator privileges can inject and execute arbitrary OS commands through improperly sanitized input in NTP settings. The vulnerability affects firmware versions prior to 1.0.7-0298.

MitigationUpdate Synology BC500 and TC500 firmware to version 1.0.7-0298 or later. Until patched, restrict administrative access to trusted personnel only and monitor for unauthorized NTP configuration changes.

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 device model and firmware version
    Access the camera's web interface or use SNMP/SSH to retrieve the system information. Look for the firmware version in the device settings or system status page.
    Affected if The firmware version is below 1.0.7-0298 on a BC500 or TC500 model.
  2. Locate the NTP configuration settings
    Navigate to the camera's web interface and find the NTP settings page, typically under Network or Time settings. The vulnerable parameter is the NTP server input field.
    Affected if The NTP configuration page is accessible with administrator privileges.
  3. Verify NTP server input handling
    If you have access, examine how the NTP server hostname or IP address is processed. The vulnerability allows command injection through unsanitized input in this field.
    Affected if The NTP server field accepts and processes special characters without validation or sanitization.
  4. Review system logs for suspicious activity
    Check the camera's system logs or audit logs for entries indicating NTP configuration changes, especially those containing unusual characters or patterns that may indicate command injection attempts.
    Affected if Logs show NTP configuration changes with unexpected characters or commands, or indicate unauthorized administrative actions.

A user is affected if they are running Synology BC500 or TC500 firmware prior to version 1.0.7-0298 and the NTP configuration interface is 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.0.7-0298 or later
Fixed in 1.0.7-0298
Interim mitigation

Update Synology BC500 and TC500 firmware to version 1.0.7-0298 or later. Until patched, restrict administrative access to trusted personnel only and monitor for unauthorized NTP configuration changes.

Recommended fix High confidence

Firmware version 1.0.7-0298 or later

  1. 1. Obtain the fixed firmware version 1.0.7-0298 or later from the official Synology download center at www.synology.com
  2. 2. Access the Synology camera web interface for the affected BC500 or TC500 device
  3. 3. Navigate to the System or Maintenance section of the management interface
  4. 4. Locate the Firmware Update or Upgrade option
  5. 5. Upload the downloaded firmware file (version 1.0.7-0298 or later)
  6. 6. Follow the on-screen prompts to apply the firmware update
  7. 7. After the update completes, verify the device is running version 1.0.7-0298 or later

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-2024-39351 — 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-2024-39351 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