Asus GT-AC5300 up to 3.0.0.4.384_32738 appGet.cgi?hook=select_list("Storage_x_SharedPath sh_path0 memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.5 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Asus GT-AC5300 up to 3.0.0.4.384_32738 and classified as critical. The impacted element is an unknown function of the file appGet.cgi?hook=select_list("Storage_x_SharedPath. The manipulation of the argument sh_path0 as part of Request leads to memory corruption. This vulnerability is listed as CVE-2018-17022. The attack may be initiated remotely. There is no available exploit.
Details
A vulnerability was found in Asus GT-AC5300 up to 3.0.0.4.384_32738 and classified as critical. This issue affects an unknown part of the file appGet.cgi?hook=select_list("Storage_x_SharedPath. The manipulation of the argument sh_path0 as part of a 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. The summary by CVE is:
Stack-based buffer overflow on the ASUS GT-AC5300 router through 3.0.0.4.384_32738 allows remote attackers to cause a denial of service (device crash) or possibly have unspecified other impact by setting a long sh_path0 value and then sending an appGet.cgi?hook=select_list("Storage_x_SharedPath") request, because ej_select_list in router/httpd/web.c uses strcpy.
The bug was discovered 09/13/2018. The weakness was presented 09/13/2018 (GitHub Repository). It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2018-17022 since 09/13/2018. The exploitation is known to be easy. The attack may be initiated remotely. A simple authentication is necessary for exploitation. Technical details of the vulnerability are known, but there is no available exploit.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
See VDB-124044, VDB-124042 and VDB-124041 for similar entries. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
Version
License
Website
- Vendor: https://www.asus.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.9VulDB Meta Temp Score: 5.8
VulDB Base Score: 4.7
VulDB Temp Score: 4.4
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: 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
09/13/2018 🔍09/13/2018 🔍
09/13/2018 🔍
09/13/2018 🔍
09/15/2018 🔍
05/26/2020 🔍
Sources
Vendor: asus.comAdvisory: github.com
Status: Not defined
CVE: CVE-2018-17022 (🔍)
GCVE (CVE): GCVE-0-2018-17022
GCVE (VulDB): GCVE-100-124043
See also: 🔍
Entry
Created: 09/15/2018 07:36Updated: 05/26/2020 22:24
Changes: 09/15/2018 07:36 (58), 05/26/2020 22:24 (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.