CVE-2022-26233 in the critical feed json
Barco Control Room Management through Suite 2.9 Build 0275 was discovered to be vulnerable to directory traversal, allowing attackers to ac…
published 4y ago modified 4mo ago also EUVD-2022-30797
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 15.0%
- EPSS 15.0% chance of exploitation in 30 days, percentile 96%
- public exploits
- 0
- none known, plus a Nuclei check
Summary
Barco Control Room Management through Suite 2.9 Build 0275 was discovered to be vulnerable to directory traversal, allowing attackers to access sensitive information and components. Requests must begin with the "GET /..\.." substring.
Is CVE-2022-26233 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
15.03% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- Nuclei template Barco Control Room Management Suite <=2.9 Build 0275 - Local File Inclusion nuclei detection template
- seclists.org http://seclists.org/fulldisclosure/2022/Apr/0 referenced PoC, tagged "exploit" by a source, unverified
- packetstormsecurity.com http://packetstormsecurity.com/files/166577/Barco-Control-Room-Management-Suite-Directory-Traversal.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
References
-
seclists.org
/fulldisclosure/2022/Apr/0
exploit, mailing-list, third-party-advisory
-
packetstormsecurity.com
/files/166577/Barco-Control-Room-Management-Suite-Directory-Traversal.html
exploit, third-party-advisory, vdb-entry
Sources
- CVE List CVE-2022-26233
- NVD CVE-2022-26233
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.