CVE-2023-5028 json
China Unicom TEWA-800G debug log file
published 2023-09-17 3 y ago modified 2026-06-17 4 mo ago also EUVD-2023-57374
- cvss
- 2.0
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 28%
- public exploits
- 0
- none known
Summary
A vulnerability, which was classified as problematic, has been found in China Unicom TEWA-800G 4.16L.04_CT2015_Yueme. Affected by this issue is some unknown functionality. The manipulation leads to information exposure through debug log file. It is possible to launch the attack on the physical device. The complexity of an attack is rather high. The exploitation is known to be difficult. The exploit has been disclosed to the public and may be used. VDB-239870 is the identifier assigned to this vulnerability.
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 16 mo ago
Exploit prediction
0.35% chance of exploitation in the next 30 days, higher than 28% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/pinglan123/-/wiki/%E4%B8%AD%E5%9B%BD%E8%81%94%E9%80%9A%E5%AE%B6%E7%94%A8%E7%BD%91%E5%85%B3 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 2.0 | CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N |
| CNA | 3.0 | 2.0 | CVSS:3.0/AV:P/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N |
| CNA | 2.0 | 1.2 | AV:L/AC:H/Au:N/C:P/I:N/A:N |
| NVD | 3.1 | 4.6 | CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected products
- China Unicom TEWA-800G
Classification
References
-
github.com
/pinglan123/-/wiki/%E4%B8%AD%E5%9B%BD%E8%81%94%E9%80%9A%E5%AE%B6%E7%94%A8%E7%BD%91%E5%85%B3
exploit, third-party-advisory
-
vuldb.com
/?id.239870
vdb-entry, technical-description, third-party-advisory
-
vuldb.com
/?ctiid.239870
signature, permissions-required, third-party-advisory
Sources
- CVE List CVE-2023-5028
- NVD CVE-2023-5028
Fencer Vulns 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.