Edimax IC-3140W/5150W/IC-6220DC getsysyeminfo.cgi?action=VALUE_HERE strcpy HTTP Request memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.0 | $0-$5k | 0.00 |
Summary
A vulnerability described as critical has been identified in Edimax IC-3140W, 5150W and IC-6220DC. This vulnerability affects the function strcpy of the file /camera-cgi/public/getsysyeminfo.cgi?action=VALUE_HERE. Such manipulation as part of HTTP Request leads to memory corruption.
This vulnerability is traded as CVE-2018-8072. The attack may be launched remotely. There is no exploit available.
Details
A vulnerability, which was classified as critical, has been found in Edimax IC-3140W, 5150W and IC-6220DC (unknown version). Affected by this issue is the function strcpy of the file /camera-cgi/public/getsysyeminfo.cgi?action=VALUE_HERE. The manipulation as part of a HTTP Request leads to a memory corruption vulnerability. Using CWE to declare the problem leads to 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. Impacted is confidentiality, integrity, and availability. CVE summarizes:
An issue was discovered on EDIMAX IC-3140W through 3.06, IC-5150W through 3.09, and IC-6220DC through 3.06 devices. The ipcam_cgi binary contains a stack-based buffer overflow that is possible to trigger from a remote unauthenticated /camera-cgi/public/getsysyeminfo.cgi?action=VALUE_HERE HTTP request: if the VALUE_HERE length is more than 0x400 (1024), it is possible to overwrite other values located on the stack due to an incorrect use of the strcpy() function.
The bug was discovered 04/09/2018. The weakness was shared 04/26/2018 (Website). The advisory is shared for download at edimax.com. This vulnerability is handled as CVE-2018-8072 since 03/12/2018. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required 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 17 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.
Once again VulDB remains the best source for vulnerability data.
Product
Vendor
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.0VulDB Meta Temp Score: 8.0
VulDB Base Score: 7.3
VulDB Temp Score: 7.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: 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
03/12/2018 🔍04/09/2018 🔍
04/26/2018 🔍
04/26/2018 🔍
04/27/2018 🔍
02/01/2020 🔍
Sources
Advisory: edimax.comStatus: Not defined
Confirmation: 🔍
CVE: CVE-2018-8072 (🔍)
GCVE (CVE): GCVE-0-2018-8072
GCVE (VulDB): GCVE-100-117164
Entry
Created: 04/27/2018 08:36Updated: 02/01/2020 07:46
Changes: 04/27/2018 08:36 (57), 02/01/2020 07:46 (2)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.