Asus GT-AC5300 up to 3.0.0.4.384_32738 GET Request input validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.2 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in Asus GT-AC5300 up to 3.0.0.4.384_32738. Impacted is an unknown function of the component GET Request Handler. Performing a manipulation results in input validation. This vulnerability is identified as CVE-2018-17020. The attack can be initiated remotely. There is not any exploit available. It is suggested to use restrictive firewalling.
Details
A vulnerability, which was classified as problematic, was found in Asus GT-AC5300 up to 3.0.0.4.384_32738. This affects an unknown functionality of the component GET Request Handler. The manipulation with an unknown input leads to a input validation vulnerability. CWE is classifying the issue as CWE-20. The product receives input or data, but it does
not validate or incorrectly validates that the input has the
properties that are required to process the data safely and
correctly. This is going to have an impact on availability. The summary by CVE is:
ASUS GT-AC5300 devices with firmware through 3.0.0.4.384_32738 allow remote attackers to cause a denial of service via a single "GET / HTTP/1.1\r\n" line.
The bug was discovered 09/13/2018. The weakness was released 09/13/2018 (Website). The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2018-17020 since 09/13/2018. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available.
It is possible to mitigate the weakness by firewalling .
Entries connected to this vulnerability are available at VDB-124044, VDB-124043 and VDB-124042. Several companies clearly confirm that VulDB is the primary source for best 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: 6.4VulDB Meta Temp Score: 6.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.2
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
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: Input validationCWE: CWE-20
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: FirewallStatus: 🔍
0-Day Time: 🔍
Timeline
09/13/2018 🔍09/13/2018 🔍
09/13/2018 🔍
09/13/2018 🔍
09/15/2018 🔍
03/23/2020 🔍
Sources
Vendor: asus.comAdvisory: github.com
Status: Not defined
CVE: CVE-2018-17020 (🔍)
GCVE (CVE): GCVE-0-2018-17020
GCVE (VulDB): GCVE-100-124041
See also: 🔍
Entry
Created: 09/15/2018 07:36Updated: 03/23/2020 19:32
Changes: 09/15/2018 07:36 (57), 03/23/2020 19:32 (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.