dbcve.org
Bc500 FirmwareOperating system · Synology

CVE-2024-39349

CRITICAL · 9.8 CVSS v3.1 Published 2024-06-28
Fix available
A fix is available. Upgrade to 1.0.7-0298 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 buffer copy without checking size of input ('Classic Buffer Overflow') is found in the libjansson component and it does not affect the upstream library. This allows remote attackers to execute arbitrary code 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

A classic buffer overflow vulnerability exists in the libjansson component within Synology BC500 and TC500 camera firmware versions prior to 1.0.7-0298. The vulnerability stems from copying buffer data without proper size validation, allowing remote attackers to execute arbitrary code via unspecified vectors. This flaw is specific to Synology's implementation and does not affect the upstream libjansson library.

MitigationUpgrade Synology BC500 and TC500 camera firmware to version 1.0.7-0298 or later to remediate the buffer overflow. If immediate patching is not possible, restrict network exposure of affected camera management interfaces.

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
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 device model
    Access the camera's web admin interface, Synology app, or management console and locate the device model information. This is typically found under Settings > Device Info or System > Status.
    Affected if Device is not a Synology BC500 or TC500 camera - this vulnerability only affects these specific models.
  2. Locate firmware version information
    In the same device management interface, navigate to System > Firmware, System > About, or Settings > Device Info to find the currently installed firmware version number.
    Affected if Unable to retrieve firmware version - you cannot determine vulnerability status without this information.
  3. Compare firmware version to vulnerable range
    Note the installed firmware version (e.g., 1.0.6-XXXX, 1.0.5-XXXX) and compare it against the vulnerable threshold: any version prior to 1.0.7-0298 is affected.
    Affected if Firmware version is less than 1.0.7-0298 - the buffer overflow in libjansson is present in these versions.
  4. Confirm libjansson component is in use
    This check is implicit - the vulnerability exists in Synology's custom implementation of libjansson within the camera firmware itself. No specific feature enablement is required; the vulnerable code is present in the base firmware.
    Affected if This is a firmware-level vulnerability in the libjansson library implementation - all vulnerable firmware versions contain the affected component by default.

You are affected if you have a Synology BC500 or TC500 camera running firmware version lower than 1.0.7-0298.

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

Upgrade Synology BC500 and TC500 camera firmware to version 1.0.7-0298 or later to remediate the buffer overflow. If immediate patching is not possible, restrict network exposure of affected camera management interfaces.

Recommended fix High confidence

Firmware version 1.0.7-0298 or later

  1. 1. Identify the Synology device model (BC500 or TC500) that needs to be patched
  2. 2. Access the Synology device management interface or DSM
  3. 3. Navigate to the firmware update section for the camera device
  4. 4. Check the current firmware version to confirm it is below 1.0.7-0298
  5. 5. Download the fixed firmware version 1.0.7-0298 or later from the official Synology download center (www.synology.com)
  6. 6. Apply the firmware update through the device management interface or using Synology's update mechanism
  7. 7. Verify the firmware has been successfully updated to 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
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
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,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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