CVE-2019-18827
published 2019-12-16CVE-2019-18827: On Barco ClickShare Button R9861500D01 devices (before firmware version 1.9.0) JTAG access is disabled after ROM code execution. This means that JTAG access is…
PriorityP434medium5.9CVSS 3.1
AVNACHPRNUINSUCHINAN
EPSS
1.35%
68.1th percentile
On Barco ClickShare Button R9861500D01 devices (before firmware version 1.9.0) JTAG access is disabled after ROM code execution. This means that JTAG access is possible when the system is running code from ROM before handing control over to embedded firmware.
Affected
4 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| barco | clickshare_cs-100_firmware | < 1.9.0 | 1.9.0 |
| barco | clickshare_cse-200_+_firmware | < 1.9.0 | 1.9.0 |
| barco | clickshare_cse-200_firmware | < 1.9.0 | 1.9.0 |
| barco | clickshare_cse-800_firmware | < 1.9.0 | 1.9.0 |
CVSS provenance
nvdv3.15.9MEDIUMCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
nvdv2.04.3MEDIUMAV:N/AC:M/Au:N/C:P/I:N/A:N
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
No detection rules found.
No public exploits indexed.
CWE
Internal Asset Exposed to Unsafe Debug Access Level or State
mitre_cwe
CWE-1244 Internal Asset Exposed to Unsafe Debug Access Level or State
CWE-1244: Internal Asset Exposed to Unsafe Debug Access Level or State
The product uses physical debug or test
interfaces with support for multiple access levels, but it
assigns the wrong debug access level to an internal asset,
providing unintended access to the asset from untrusted debug
agents.
Debug authorization can have multiple levels of
access, defined such that different system internal assets
are accessible based on the current authorized debug
level. Other than debugger authentication (e.g., using
passwords or challenges), the authorization can also be
based on the system state or boot stage. For example, full
system debug access might only be allowed early in boot
after a system reset to ensure that previous session data is
not accessible to the authenticated debugger.
Modes
CWE
Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
mitre_cwe
CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.
A race condition occurs within concurrent environments, and it is effectively a property of a code sequence. Depending on the context, a code sequence may be in the form of a function call, a small number of instructions, a series of program invocations, etc. A race condition violates these properties, which are closely related: Exclusivity - the code sequence is given exclusive access to the shared resource, i.e., no other code sequence can modify properties
CWE
On-Chip Debug and Test Interface With Improper Access Control
mitre_cwe
CWE-1191 On-Chip Debug and Test Interface With Improper Access Control
CWE-1191: On-Chip Debug and Test Interface With Improper Access Control
The chip does not implement or does not correctly perform access control to check whether users are authorized to access internal registers and test modes through the physical debug/test interface.
A device's internal information may be accessed through a scan chain of interconnected internal registers, usually through a JTAG interface. The JTAG interface provides access to these registers in a serial fashion in the form of a scan chain for the purposes of debugging programs running on a device. Since almost all information contained within a device may be accessed over this interface, device manufacturers typically insert some form of authentication and authorization to prevent unintended use of this sensitive infor
https://labs.f-secure.com/advisories/multiple-vulnerabilities-in-barco-clickshare/https://www.barco.com/en/clickshare/firmware-updatehttps://www.barco.com/en/support/software/R33050069?majorVersion=01&minorVersion=09&patchVersion=01&buildVersion=007https://www.barco.com/en/support/software/R33050070?majorVersion=01&minorVersion=09&patchVersion=01&buildVersion=007https://www.barco.com/en/support/software/R33050095?majorVersion=01&minorVersion=09&patchVersion=01&buildVersion=007https://www.barco.com/en/support/software/R33050125?majorVersion=01&minorVersion=09&patchVersion=01&buildVersion=007https://labs.f-secure.com/advisories/multiple-vulnerabilities-in-barco-clickshare/https://www.barco.com/en/clickshare/firmware-updatehttps://www.barco.com/en/support/software/R33050069?majorVersion=01&minorVersion=09&patchVersion=01&buildVersion=007https://www.barco.com/en/support/software/R33050070?majorVersion=01&minorVersion=09&patchVersion=01&buildVersion=007https://www.barco.com/en/support/software/R33050095?majorVersion=01&minorVersion=09&patchVersion=01&buildVersion=007https://www.barco.com/en/support/software/R33050125?majorVersion=01&minorVersion=09&patchVersion=01&buildVersion=007
2019-12-16
Published