CVE-2020-28334 json
Barco wePresent WiPG-1600W devices use Hard-coded Credentials (issue 2 of 2).
published 5y ago modified 4mo ago also EUVD-2020-20797
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 4.8%
- EPSS 4.8% chance of exploitation in 30 days, percentile 91%
- public exploits
- 0
- none known
Summary
Barco wePresent WiPG-1600W devices use Hard-coded Credentials (issue 2 of 2). Affected Version(s): 2.5.1.8, 2.5.0.25, 2.5.0.24, 2.4.1.19. The Barco wePresent WiPG-1600W device has a hardcoded root password hash included in the firmware image. Exploiting CVE-2020-28329, CVE-2020-28330 and CVE-2020-28331 could potentially be used in a simple and automated exploit chain to go from unauthenticated remote attacker to root shell.
Is CVE-2020-28334 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
4.77% chance of exploitation in the next 30 days, higher than 91% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- packetstormsecurity.com http://packetstormsecurity.com/files/160163/Barco-wePresent-Global-Hardcoded-Root-SSH-Password.html referenced PoC, tagged "exploit" by a source, unverified
- korelogic.com https://korelogic.com/Resources/Advisories/KL-001-2020-008.txt referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 10.0 | AV:N/AC:L/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-798 Use of Hard-coded Credentials
References
-
packetstormsecurity.com
/files/160163/Barco-wePresent-Global-Hardcoded-Root-SSH-Password.html
exploit, third-party-advisory, vdb-entry
-
korelogic.com
/Resources/Advisories/KL-001-2020-008.txt
exploit, third-party-advisory
Sources
- CVE List CVE-2020-28334
- NVD CVE-2020-28334
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.