TP-LINK WVR/WAR/ER pptp_client.lua lcpechointerval command injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.7 | $0-$5k | 0.00 |
Summary
A vulnerability described as critical has been identified in TP-LINK WVR, WAR and ER. This affects an unknown function of the file pptp_client.lua. Such manipulation of the argument lcpechointerval as part of Variable leads to command injection. This vulnerability is documented as CVE-2017-15615. The attack can be executed remotely. There is not any exploit available.
Details
A vulnerability, which was classified as critical, has been found in TP-LINK WVR, WAR and ER (Wireless LAN Software) (unknown version). Affected by this issue is an unknown code block of the file pptp_client.lua. The manipulation of the argument lcpechointerval as part of a Variable leads to a command injection vulnerability. Using CWE to declare the problem leads to 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. Impacted is confidentiality, integrity, and availability. CVE summarizes:
TP-Link WVR, WAR and ER devices allow remote authenticated administrators to execute arbitrary commands via command injection in the lcpechointerval variable in the pptp_client.lua file.
The bug was discovered 01/10/2018. The weakness was released 01/11/2018 (Website). The advisory is available at securityfocus.com. This vulnerability is handled as CVE-2017-15615 since 10/19/2017. The attack may be launched remotely. The requirement for exploitation is a simple authentication. Technical details are known, but there is no available exploit. This vulnerability is assigned to T1202 by the MITRE ATT&CK project.
The vulnerability was handled as a non-public zero-day exploit for at least 1 days. During that time the estimated underground price was around $0-$5k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Entries connected to this vulnerability are available at VDB-111744, VDB-111745, VDB-111747 and VDB-111748. If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Vendor
Name
License
Website
- Vendor: https://www.tp-link.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.7VulDB Meta Temp Score: 6.7
VulDB Base Score: 6.3
VulDB Temp Score: 6.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.2
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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Command injectionCWE: CWE-77 / CWE-74 / CWE-707
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
10/19/2017 🔍01/10/2018 🔍
01/11/2018 🔍
01/11/2018 🔍
01/12/2018 🔍
12/22/2019 🔍
Sources
Vendor: tp-link.comAdvisory: securityfocus.com⛔
Status: Not defined
CVE: CVE-2017-15615 (🔍)
GCVE (CVE): GCVE-0-2017-15615
GCVE (VulDB): GCVE-100-111746
See also: 🔍
Entry
Created: 01/12/2018 07:58Updated: 12/22/2019 11:43
Changes: 01/12/2018 07:58 (59), 12/22/2019 11:43 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.