# CVE-2019-18833: Information disclosure in n/a

> An attacker performing a Man-in-the-Middle attack can obtain the encryption key for shared media content, exposing sensitive data.

- **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:** 17 Dec 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-q859-mjw3-4xvp

## What is CVE-2019-18833?

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

### Official description

Barco ClickShare Button R9861500D01 devices before 1.9.0 allow Information exposure (issue 2 of 2).. The encryption key of the media content which is shared between a ClickShare Button and a ClickShare Base Unit is randomly generated for each new session and communicated over a TLS connection. An attacker who is able to perform a Man-in-the-Middle attack between the TLS connection, is able to obtain the encryption key.

Weakness: CWE-311 (Missing Encryption of Sensitive Data)

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

It affects 1 product.


Products: Barco Clickshare Button R9861500d01 Firmware.

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

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

## Is CVE-2019-18833 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-18832](https://insights.sbomify.com/CVE-2019-18832/): Weak cryptography in n/a (high 8.1)
- [CVE-2019-18829](https://insights.sbomify.com/CVE-2019-18829/): Other in n/a (high 7.8)
- [CVE-2019-18824](https://insights.sbomify.com/CVE-2019-18824/): Other in n/a (medium 6.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-18833 is a medium-severity vulnerability in n/a, published on 17 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-18833 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-18833/ (Markdown: https://insights.sbomify.com/CVE-2019-18833/index.md)
```

## Sources

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

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