TP-LINK TL-R600VPN HTTP Server header-parsing HTTP Request memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.9 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as critical has been found in TP-LINK TL-R600VPN. Affected is the function header-parsing of the component HTTP Server. The manipulation as part of HTTP Request results in memory corruption.
This vulnerability was named CVE-2018-3951. The attack may be performed from remote. There is no available exploit.
Details
A vulnerability classified as critical has been found in TP-LINK TL-R600VPN (Router Operating System) (the affected version unknown). Affected is the function header-parsing of the component HTTP Server. The manipulation as part of a HTTP Request leads to a memory corruption vulnerability. CWE is classifying the issue as CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:
An exploitable remote code execution vulnerability exists in the HTTP header-parsing function of the TP-Link TL-R600VPN HTTP Server. A specially crafted HTTP request can cause a buffer overflow, resulting in remote code execution on the device. An attacker can send an authenticated HTTP request to trigger this vulnerability.
The bug was discovered 11/19/2018. The weakness was presented 12/01/2018 (Website). The advisory is shared for download at talosintelligence.com. This vulnerability is traded as CVE-2018-3951 since 01/02/2018. It is possible to launch the attack remotely. A authentication is necessary for exploitation. There are known technical details, but no exploit is available.
The vulnerability was handled as a non-public zero-day exploit for at least 12 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.
See VDB-127367, VDB-127366 and VDB-127365 for similar entries. VulDB is the best source for vulnerability data and more expert information about this specific topic.
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.9VulDB Meta Temp Score: 6.9
VulDB Base Score: 6.3
VulDB Temp Score: 6.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.2
NVD Vector: 🔍
CNA Base Score: 7.2
CNA Vector (Talos): 🔍
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: Memory corruptionCWE: CWE-119
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
01/02/2018 🔍11/19/2018 🔍
12/01/2018 🔍
12/01/2018 🔍
12/01/2018 🔍
06/12/2023 🔍
Sources
Vendor: tp-link.comAdvisory: talosintelligence.com
Status: Not defined
CVE: CVE-2018-3951 (🔍)
GCVE (CVE): GCVE-0-2018-3951
GCVE (VulDB): GCVE-100-127368
See also: 🔍
Entry
Created: 12/01/2018 20:12Updated: 06/12/2023 13:41
Changes: 12/01/2018 20:12 (63), 04/16/2020 16:32 (1), 06/12/2023 13:41 (14)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.