dbcve.org
Clickshare Cs 100 FirmwareOperating system · Barco

CVE-2019-18830

CRITICAL · 9.8 CVSS v3.1 Published 2019-12-16
Fix available
A fix is available. Upgrade to 1.9.0 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
Barco ClickShare Button R9861500D01 devices before 1.9.0 allow OS Command Injection. The embedded 'dongle_bridge' program used to expose the functionalities of the ClickShare Button to a USB host, is vulnerable to OS command injection vulnerabilities. These vulnerabilities could lead to code execution on the ClickShare Button with the privileges of the user 'nobody'.

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 Barco ClickShare Button R9861500D01 dongle runs a 'dongle_bridge' program that exposes button functionalities to a USB host. Versions before 1.9.0 fail to properly sanitize input, allowing attackers to inject OS commands that execute with 'nobody' user privileges. This is a classic command injection flaw in the firmware's input handling layer.

MitigationUpgrade the ClickShare Button firmware to version 1.9.0 or later to obtain the vendor patch. If immediate patching is not possible, restrict physical access to the dongle and limit network exposure of ClickShare infrastructure.

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
Clickshare Cs 100 FirmwareOperating system
Affected:< 1.9.0
Clickshare Cse 200 FirmwareOperating system
Affected:< 1.9.0
Clickshare Cse 200\+ FirmwareOperating system
Affected:< 1.9.0
Clickshare Cse 800 FirmwareOperating system
Affected:< 1.9.0

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 the ClickShare device model
    Locate the physical ClickShare dongle (R9861500D01) and check the product label or documentation for the model variant (CS 100, CSE 200, CSE 200+, or CSE 800). Alternatively, access the ClickShare base unit admin interface and view the connected device information.
    Affected if The model is one of CS 100, CSE 200, CSE 200+, or CSE 800 and the dongle is connected.
  2. Check the firmware version
    Access the ClickShare base unit web interface or admin panel and navigate to the device status or firmware information section to view the dongle firmware version. Compare the displayed version number against the affected range.
    Affected if The dongle firmware version is below 1.9.0.
  3. Verify dongle_bridge program exposure
    On the ClickShare base unit, check if the dongle_bridge service or process is running and accessible. This may require SSH access to the base unit or review of system logs indicating USB device communication.
    Affected if The dongle_bridge program is active and accepting input from the connected USB dongle.
  4. Confirm USB input handling is enabled
    Verify that the ClickShare system has USB device support enabled and the dongle is actively communicating with the base unit. Check system logs or device status for active USB enumeration events.
    Affected if The dongle is connected and USB input handling to the dongle_bridge component is enabled.

You are affected if your ClickShare model is a CS 100, CSE 200, CSE 200+, or CSE 800 with dongle firmware version below 1.9.0 and the dongle is actively connected with the dongle_bridge component handling input.

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.9.0 or later
Fixed in 1.9.0
Interim mitigation

Upgrade the ClickShare Button firmware to version 1.9.0 or later to obtain the vendor patch. If immediate patching is not possible, restrict physical access to the dongle and limit network exposure of ClickShare infrastructure.

Recommended fix High confidence

Firmware 1.9.0

  1. Download the firmware version 1.9.0 or later from the official Barco website (www.barco.com) for your specific ClickShare model (CS 100, CSE 200, CSE 200+, or CSE 800)
  2. Access the ClickShare Base Unit's admin interface via web browser
  3. Navigate to the firmware update or administration section
  4. Upload the downloaded firmware file and initiate the update process
  5. Wait for the firmware update to complete (do not power off the device during the update)
  6. Verify the firmware version has been updated to 1.9.0 or later by checking the system information in the admin interface
  7. Reboot the device if prompted to ensure all changes take effect

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

Fix this in Clickshare Cs 100 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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