TP-LINK TL-WVR/TL-WAR/TL-ER/TL-R uhttpd bridge.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 was found in TP-LINK TL-WVR, TL-WAR, TL-ER and TL-R. It has been rated as critical. Affected is the function get_device_byif in the library /usr/lib/lua/luci/controller/admin/bridge.lua of the component uhttpd. Performing a manipulation of the argument t_bindif results in command injection.
This vulnerability is reported as CVE-2017-16958. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability was found in TP-LINK TL-WVR, TL-WAR, TL-ER and TL-R (Router Operating System) (version unknown). It has been classified as critical. This affects the function get_device_byif in the library /usr/lib/lua/luci/controller/admin/bridge.lua of the component uhttpd. The manipulation of the argument t_bindif with an unknown input leads to a command injection vulnerability. CWE is classifying the issue as 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. This is going to have an impact on 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/bridge command to cgi-bin/luci, related to the get_device_byif function in /usr/lib/lua/luci/controller/admin/bridge.lua in uhttpd.
The bug was discovered 11/27/2017. The weakness was disclosed 11/27/2017 (Website). The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2017-16958 since 11/27/2017. It is possible to initiate the attack remotely. The successful exploitation requires a authentication. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1202 for this issue.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The entries VDB-109979, VDB-109978 and VDB-109976 are pretty similar. Several companies clearly confirm that VulDB is the primary source for best 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-16958 (🔍)
GCVE (CVE): GCVE-0-2017-16958
GCVE (VulDB): GCVE-100-109977
See also: 🔍
Entry
Created: 11/27/2017 16:21Updated: 12/10/2019 16:46
Changes: 11/27/2017 16:21 (59), 12/10/2019 16:46 (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.