TP-LINK TL-WVR/TL-WAR/TL-ER/TL-R uhttpd interface.lua get_device_byif t_bindif command injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.5 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in TP-LINK TL-WVR, TL-WAR, TL-ER and TL-R. Affected by this issue is the function get_device_byif in the library /usr/lib/lua/luci/controller/admin/interface.lua of the component uhttpd. The manipulation of the argument t_bindif leads to command injection.
This vulnerability is traded as CVE-2017-16960. It is possible to initiate the attack remotely. There is no exploit available.
Details
A vulnerability was found in TP-LINK TL-WVR, TL-WAR, TL-ER and TL-R (Router Operating System) (affected version not known). It has been rated as critical. This issue affects the function get_device_byif in the library /usr/lib/lua/luci/controller/admin/interface.lua of the component uhttpd. The manipulation of the argument t_bindif with an unknown input 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. The summary by CVE is:
TP-Link TL-WVR, TL-WAR, TL-ER, and TL-R devices allow remote authenticated users to execute arbitrary commands via shell metacharacters in the t_bindif field of an admin/interface command to cgi-bin/luci, related to the get_device_byif function in /usr/lib/lua/luci/controller/admin/interface.lua in uhttpd.
The bug was discovered 11/27/2017. The weakness was shared 11/27/2017 (Website). It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2017-16960 since 11/27/2017. The attack may be initiated remotely. A simple authentication is required for exploitation. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1202 according to MITRE ATT&CK.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The entries VDB-109978, VDB-109977 and VDB-109976 are related to this item. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
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: 7.6VulDB Meta Temp Score: 7.6
VulDB Base Score: 6.3
VulDB Temp Score: 6.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.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: 🔍
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
11/27/2017 🔍11/27/2017 🔍
11/27/2017 🔍
11/27/2017 🔍
11/27/2017 🔍
12/10/2019 🔍
Sources
Vendor: tp-link.comAdvisory: github.com
Status: Not defined
CVE: CVE-2017-16960 (🔍)
GCVE (CVE): GCVE-0-2017-16960
GCVE (VulDB): GCVE-100-109979
See also: 🔍
Entry
Created: 11/27/2017 16:22Updated: 12/10/2019 16:50
Changes: 11/27/2017 16:22 (59), 12/10/2019 16:50 (1)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.