Asus RT-AX57 3.0.0.4_386_52041 Request sub_4CCE4 ifname privilege escalation

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
7.9$0-$5k0.00

Summaryinfo

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.

Detailsinfo

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.

Productinfo

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 8.0
VulDB 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: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Privilege escalation
CWE: Unknown
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

10/30/2023 🔍
11/09/2023 +10 days 🔍
11/09/2023 +0 days 🔍
12/05/2023 +26 days 🔍

Sourcesinfo

Vendor: asus.com

Advisory: github.com
Status: Not defined

CVE: CVE-2023-47008 (🔍)
GCVE (CVE): GCVE-0-2023-47008
GCVE (VulDB): GCVE-100-244841

Entryinfo

Created: 11/09/2023 04:02
Updated: 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.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Do you want to use VulDB in your project?

Use the official API to access entries easily!