Optilink OP-XT71000N 2.2 /diag_ping_admin.asp command injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.9 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Optilink OP-XT71000N 2.2. Affected by this vulnerability is an unknown functionality of the file /diag_ping_admin.asp. This manipulation causes an unknown weakness. This vulnerability is registered as CVE-2020-23583. Remote exploitation of the attack is possible. No exploit is available. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Details
A vulnerability was found in Optilink OP-XT71000N 2.2. It has been declared as critical. Affected by this vulnerability is an unknown code of the file /diag_ping_admin.asp. The CWE definition for the vulnerability is CWE-77. The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
OPTILINK OP-XT71000N V2.2 is vulnerable to Remote Code Execution. The issue occurs when the attacker sends an arbitrary code on "/diag_ping_admin.asp" to "PingTest" interface that leads to COMMAND EXECUTION. An attacker can successfully trigger the COMMAND and can compromise full system.
The weakness was published 11/23/2022. The advisory is shared at github.com. This vulnerability is known as CVE-2020-23583 since 08/13/2020. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1202 for this issue.
By approaching the search of inurl:diag_ping_admin.asp it is possible to find vulnerable targets with Google Hacking.
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
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.0VulDB Meta Temp Score: 7.9
VulDB Base Score: 6.3
VulDB Temp Score: 6.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
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: Command injectionCWE: CWE-77 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
Google Hack: 🔍
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/13/2020 🔍11/23/2022 🔍
11/23/2022 🔍
04/25/2025 🔍
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2020-23583 (🔍)
GCVE (CVE): GCVE-0-2020-23583
GCVE (VulDB): GCVE-100-214225
Entry
Created: 11/23/2022 11:07 AMUpdated: 04/25/2025 11:36 PM
Changes: 11/23/2022 11:07 AM (36), 12/22/2022 11:16 AM (12), 04/25/2025 11:36 PM (16)
Complete: 🔍
Cache ID: 244:25B:40
No comments yet. Languages: en.
Please log in to comment.