CVE-2019-18824 json
Barco ClickShare Button R9861500D01 devices before 1.10.0.13 have Missing Support for Integrity Check.
published 6y ago modified 4mo ago also EUVD-2019-8526
- cvss
- 6.6
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 27%
- public exploits
- 0
- none known
Summary
Barco ClickShare Button R9861500D01 devices before 1.10.0.13 have Missing Support for Integrity Check. The ClickShare Button does not verify the integrity of the mutable content on the UBIFS partition before being used.
Patch / fix
- barco clickshare_button_r9861500d01_firmware 1.10.0.13
Is CVE-2019-18824 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
0.34% chance of exploitation in the next 30 days, higher than 27% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- labs.f-secure.com https://labs.f-secure.com/advisories/multiple-vulnerabilities-in-barco-clickshare/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 6.6 | CVSS:3.1/AV:P/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.9 | AV:L/AC:M/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-345 Insufficient Verification of Data Authenticity
References
-
labs.f-secure.com
/advisories/multiple-vulnerabilities-in-barco-clickshare/
exploit, third-party-advisory
-
barco.com
/en/clickshare/firmware-update
vendor-advisory
-
barco.com
/en/clickshare/support/software/R33050070?majorVersion=01&minorVersion=10&patchVersion=00&buildVersion=013
vendor-advisory
-
barco.com
/en/clickshare/support/software/R33050069?majorVersion=01&minorVersion=10&patchVersion=00&buildVersion=013
vendor-advisory
Sources
- CVE List CVE-2019-18824
- NVD CVE-2019-18824
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.