# CVE-2019-18827: Security feature bypass in n/a

> Attackers can bypass JTAG security restrictions on Barco ClickShare Button devices by accessing the interface during the ROM execution phase before firmware loads.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Dec 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-56mr-9636-w954

## What is CVE-2019-18827?

CVE-2019-18827 is a medium-severity vulnerability in n/a, published on 16 Dec 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization), CWE-285 (Improper Authorization)

## Which versions are affected by CVE-2019-18827?

It affects 4 products.


Products: Barco Clickshare Cs-100 Firmware, Barco Clickshare Cse-200\+ Firmware, Barco Clickshare Cse-200 Firmware, Barco Clickshare Cse-800 Firmware.

## How do I fix CVE-2019-18827?

No fix has been published for CVE-2019-18827 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-18827 being exploited?

There is no known exploitation of CVE-2019-18827 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2019-18826](https://insights.sbomify.com/CVE-2019-18826/): Security feature bypass in n/a (critical 9.8)
- [CVE-2019-18830](https://insights.sbomify.com/CVE-2019-18830/): Command injection in n/a (critical 9.8)
- [CVE-2018-10943](https://insights.sbomify.com/CVE-2018-10943/): Denial of service in n/a (high 7.5)
- [CVE-2019-18828](https://insights.sbomify.com/CVE-2019-18828/): Hardcoded credentials in n/a (medium 6.8)
- [CVE-2019-18831](https://insights.sbomify.com/CVE-2019-18831/): Hardcoded credentials in n/a (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-18827 and fix it if it is affected.

What it is: CVE-2019-18827 is a medium-severity vulnerability in n/a, published on 16 Dec 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-18827 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-18827/ (Markdown: https://insights.sbomify.com/CVE-2019-18827/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-18827
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-18827
- OSV: https://osv.dev/vulnerability/CVE-2019-18827

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-18827/
Summaries are generated and may contain mistakes; the official description above is the record.