Asus RT-AX57 3.0.0.4_386_52041 Request sub_4CCE4 ifname privilege escalation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.9 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Asus RT-AX57 3.0.0.4_386_52041. This vulnerability affects the function sub_4CCE4 of the component Request Handler. The manipulation of the argument ifname leads to an unknown weakness.
This vulnerability is documented as CVE-2023-47008. The attack can be initiated remotely. There is not any exploit available.
Details
A vulnerability was found in Asus RT-AX57 3.0.0.4_386_52041 and classified as critical. This issue affects the function sub_4CCE4 of the component Request Handler. The manipulation of the argument ifname with an unknown input leads to a unknown weakness. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
An issue in ASUS RT-AX57 v.3.0.0.4_386_52041 allows a remote attacker to execute arbitrary code via a crafted request to the ifname field in the sub_4CCE4 function.
The weakness was released 11/09/2023. The advisory is shared at github.com. The identification of this vulnerability is CVE-2023-47008 since 10/30/2023. Technical details are known, but no exploit is available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
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: 8.0VulDB Meta Temp Score: 7.9
VulDB Base Score: 6.3
VulDB Temp Score: 6.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.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: 🔍
Exploiting
Class: Privilege escalationCWE: Unknown
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
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
10/30/2023 🔍11/09/2023 🔍
11/09/2023 🔍
12/05/2023 🔍
Sources
Vendor: asus.comAdvisory: github.com
Status: Not defined
CVE: CVE-2023-47008 (🔍)
GCVE (CVE): GCVE-0-2023-47008
GCVE (VulDB): GCVE-100-244841
Entry
Created: 11/09/2023 04:02Updated: 12/05/2023 14:08
Changes: 11/09/2023 04:02 (38), 12/05/2023 14:08 (11)
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.