Telos Z-IP One up to 4.0.0r Web UI pathname traversal
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.3 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in Telos Z-IP One up to 4.0.0r. Affected by this vulnerability is an unknown functionality of the component Web UI. This manipulation causes pathname traversal. This vulnerability is handled as CVE-2020-17383. The attack can be initiated remotely. There is not any exploit available.
Details
A vulnerability classified as critical was found in Telos Z-IP One up to 4.0.0r. Affected by this vulnerability is an unknown functionality of the component Web UI. The manipulation with an unknown input leads to a pathname traversal vulnerability. The CWE definition for the vulnerability is CWE-21. As an impact it is known to affect confidentiality, integrity, and availability.
The weakness was released 01/25/2022. The advisory is shared at sra.io. This vulnerability is known as CVE-2020-17383 since 08/07/2020. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1006 for this issue.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
- 4.0.0a
- 4.0.0b
- 4.0.0c
- 4.0.0d
- 4.0.0e
- 4.0.0f
- 4.0.0g
- 4.0.0h
- 4.0.0i
- 4.0.0j
- 4.0.0k
- 4.0.0l
- 4.0.0m
- 4.0.0n
- 4.0.0o
- 4.0.0p
- 4.0.0q
- 4.0.0r
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.3
VulDB Base Score: 7.3
VulDB Temp Score: 7.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Pathname traversalCWE: CWE-21 / CWE-22
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
08/07/2020 🔍01/25/2022 🔍
01/25/2022 🔍
01/28/2022 🔍
Sources
Advisory: sra.ioStatus: Not defined
CVE: CVE-2020-17383 (🔍)
GCVE (CVE): GCVE-0-2020-17383
GCVE (VulDB): GCVE-100-191521
Entry
Created: 01/25/2022 07:35Updated: 01/28/2022 08:58
Changes: 01/25/2022 07:35 (37), 01/28/2022 08:57 (1), 01/28/2022 08:58 (1)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.