dbcve.org
Bc500 FirmwareOperating system · Synology

CVE-2024-5463

MEDIUM · 6.5 CVSS v3.1 Published 2024-06-04
Fix available
A fix is available. Upgrade to 1.1.1-0383 or later.
See remediation →
74/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 buffer copy without checking the size of input ('Classic Buffer Overflow') has been found in the login component. This allows remote attackers to write specific files containing non-sensitive information and conduct limited denial-of-service attacks via unspecified vectors. This attack only affects the login service which will automatically restart. The following models with Synology Camera Firmware versions before 1.1.1-0383 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

Buffer overflow vulnerability in the login component of Synology BC500 and TC500 cameras allows remote attackers to write specific non-sensitive files and conduct limited denial-of-service attacks via unspecified vectors. The affected login service automatically restarts after exploitation.

MitigationUpdate Synology BC500 and TC500 camera firmware to version 1.1.1-0383 or later to remediate this vulnerability.

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.1.1-0383
Tc500 FirmwareOperating system
Affected:< 1.1.1-0383

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
None
Integrity
Low
Availability
Low

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

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 Synology camera web interface or check the device label. Confirm the model is either BC500 or TC500.
    Affected if Model is BC500 or TC500 and firmware version is below 1.1.1-0383
  2. Check firmware version via web interface
    Log into the camera web management panel, navigate to Settings or System Information section, and locate the firmware version field.
    Affected if Firmware version displayed is less than 1.1.1-0383
  3. Check firmware version via command line
    If SSH access is enabled, connect to the camera and run the command: cat /etc/version or grep version /var/log/messages to retrieve the installed firmware version.
    Affected if Retrieved firmware version is lower than 1.1.1-0383
  4. Verify login service accessibility
    Confirm the camera login service is reachable over the network on the default HTTP/HTTPS ports (typically 80 or 443). The vulnerability requires the login component to be network-accessible.
    Affected if Login service is exposed on the network and firmware version is below 1.1.1-0383

You are affected if you own a Synology BC500 or TC500 camera running firmware version lower than 1.1.1-0383, and the camera login service is network-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.1.1-0383 or later
Fixed in 1.1.1-0383
Interim mitigation

Update Synology BC500 and TC500 camera firmware to version 1.1.1-0383 or later to remediate this vulnerability.

Recommended fix High confidence

Firmware version 1.1.1-0383

  1. 1. Identify the Synology camera model (BC500 or TC500) requiring remediation.
  2. 2. Access the camera's web interface or Synology surveillance station management console.
  3. 3. Navigate to the firmware update section for the affected camera.
  4. 4. Check the current firmware version to confirm it is below 1.1.1-0383.
  5. 5. Download the latest firmware version 1.1.1-0383 or later from the official Synology download center at www.synology.com.
  6. 6. Apply the firmware update following the standard Synology camera firmware upgrade procedure.
  7. 7. After the update completes, verify the new firmware version is 1.1.1-0383 or higher.
  8. 8. Confirm the login service is functioning normally after the automatic restart.

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
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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