# RW-Fuzzer: A Fuzzing Method for Vulnerability Mining on Router Web Interface

Authors: Longjuan Wang; Chunjie Cao; Jun Ye; Wenjie Zhong
Journal: Wireless Communications and Mobile Computing
 (2022)

---

## Abstract

As the main routing device of the network, most routers can be set up and managed through their web enabled admin portal. This paper proposes a new method for router admin portal vulnerability mining fuzzing test (RW-fuzzer: Router Web fuzzer). The mutation samples that generated by Boofuzz are used to construct the test sample set for fuzzy testing. The constructed mutation test cases are more suitable for the attack load or critical value of the router’s Web interface. They can cause unexpected errors for the devices more easily, which achieves the goal of discover potential vulnerabilities, and the practicality is excellent. Based on the proposed RW-fuzzer method, this work conducted fuzzing tests on 4 widely sold router models from manufacturers. Four nday vulnerabilities and one 0day vulnerability have been found. Experiment results show that the proposed RW-fuzzer method is effective.


---

## Body

## 1. Introduction

A router is a network communication device that connects various local area networks and wide area networks in the Internet. It has the functions of network interconnection, data processing, and network management and plays a vital role in the Internet. The router itself has a large number of exploitable security vulnerability. These security vulnerabilities can present a range of risks to users, including intelligence gathering, identity theft, data theft, damage or destruction of computer equipment, congestion and destruction of network traffic, firmware removal, and botnet infection. The Mirai IoT (Internet of Things) malware DDoS attack that broke out in 2016 caused the DNS server and the websites of many mainstream Internet companies to be paralyzed, which included Twitter, payment website PayPal, and music website Spotify. In this case, the botnet of the DDoS attack reached more than 300,000 units, of which routers accounted for the majority. What is more, the malware used Telnet scanners to identify router devices exposed online and used a combination of vulnerabilities and default credentials to infect insecure routers. Hence, the routers can be added to a massive botnet. In September 2019, FortiGuard Labs of Fortinet, an integrated automation network security solution provider, discovered and reported an unauthorized command injection vulnerability in router D-Link products (FG-VD-19-117/CVE-2019-16920). An attacker can use this vulnerability to achieve remote code execution (RCE) on the device without authentication, and this vulnerability is marked as a high-severity vulnerability. Additionally, in 2019, the 360 Security Research Institute team conducted an in-depth analysis of the vulnerability [1]. After extracting the vulnerability identification pattern, the self-developed FirmwareTotal (IoT firmware automatic security analysis solution) was used to analyze the firmware of more than 200,000 routers in the entire network. This scan found that the vulnerability exists in 58 versions of firmware in 13 different D-Link models of routers.The existence of router vulnerabilities poses a threat to user security, so the mining of router device vulnerabilities has become a research hotspot in the field of security research.Most routers develop Web applications based on common Web technologies such as PHP and Javascript for the convenience of users. Then, the applications are used to configure and manage routers’ Web interface. This paper proposes a fuzzing test method for router Web-side vulnerability mining in view of the vulnerability risks existing on the router Web interface. The main work and contributions are as follows:(1)
Export test targets in batch processing, which has higher operational efficiency than the original single import method(2)
The first to apply is the fuzzing method commonly used in software vulnerability testing to the vulnerability detection of the router Web interface. The reconstructed mutation samples and its testing process are close to the request of the real browser. It is more suitable for the attack load on the web interface of the router. It is easier to trigger the exception of the device, showing good operability(3)
The paper verifies the proposed method. The fuzzing test is carried out on 4 real devices including DP-Link, B-Link, ASUS, and other router equipment manufacturers, and 4 nday vulnerabilities and a 0day vulnerability are found. The results indicate the validity and applicability of the methodSection2 of this paper will describe the related work; Section 3 will introduce the router Web-side vulnerability mining fuzz test method (RW-fuzzer); Section 4 uses the method proposed in this paper to test several routers and analyze the test results and summary; Section 5 summarizes the work of this paper and looks forward to the next work.


## 2. Relative Work

### 2.1. Routers

According to the “China Internet Development Report (2021),” by the end of 2020, the number of netizens in my country was 989 million. In the second half of 2020, as many as 15.698 million home routers were sold in the domestic market. The core position of the router makes it play an important role in both personal and corporate networks. Most of the routers on the market use the Web terminal for the convenience of users. Reference [2] studied 11,482 kinds of routers and found that the proportion of devices with Web interface was 83.6%. This data shows that most routers are controlled and managed through the Web. The router’s Web architecture is shown in Figure 1.Figure 1
Router Web architecture.


### 2.2. Vulnerabilities on the Web Interface of Routers

While the application of the router Web side brings convenience to users, it also brings many security risks due to the security loopholes in the Web interface. Table1 lists the common router Web-interface vulnerabilities in recent years. Hackers use these vulnerabilities to attack routers, which will bring great security threats to users.Table 1
Common router Web vulnerabilities.
Device nameCWE (list of common defects)DescribeD-Link/DIR-300CWE-352Cross-site request forgeryNetgearCWE-601URL redirects to untrusted siteD-Link DIR-600/300CWE-200Information leakageD-Link 850LCWE-319Sensitive information transmitted in clear textD-Link/DIR8xxCWE-295Improper certificate validationBillion 7700NR4CWE-798Use hardcoded certificatesLink 850LCWE-798Use hardcoded certificatesTOTOLINKCWE-20Improper certificate validationTP-LinkCWE-284Improper access control


### 2.3. Research on Router Security

The role of routers in the network makes the study of router security one of the key research directions of security researchers in recent years. Some researchers start from improving router security. Reference [3] maximizes the authentication capability of a router by embedding a device-based MAC address application to monitor user entries. The method periodically changes the password of the router, sends the encrypted password to the user, and at the same time informs the administrator about the change. The router transmits data through the Internet to improve its security. Reference [4] proposes the IDRBT-IoT Secure Router (IISR), which can resist a large number of network attacks. IISR protects the IoT ecosystem by providing a one-step solution, which therefore protects the network from malicious activity. Reference [5] presents an evaluation study of Manufacturer Usage Descriptions (MUDs), proposing a mechanism to identify and eliminate configuration vulnerabilities before creating a device’s MUD profile, which minimizes the attack surface.More researchers invest in how to detect router vulnerabilities. Literature [6] is mainly used to discover the vulnerabilities of SOHO router devices and realize automatic pattern recognition of multiple types of vulnerabilities in SOHO routers. For the D-CONF operation in popular SOHO routers, the CONF-READ communication model is extended, and it is carried out. In order to improve, an improved SRFuzzer method based on DCONF mode, fuzzification mechanism is proposed, focusing on detecting read operation problems. Reference [7] developed the WNV detector, a general and extensible framework for detecting vulnerabilities in wireless networks, which enables automated and fine-grained device identification and effectively detects security vulnerabilities in wireless routers. Reference [8] proposed the first gray-box fuzzy framework EWVHunter based on embedded device Web front-end for security analysis of embedded devices. EWVHunter can automatically detect authentication bypass vulnerabilities and command injection vulnerabilities in embedded devices by using information from official firmware and logic programs that control the terminal’s Web front-end. Reference [9] designed a black-box fuzzing tool named SIoTFuzzer, which can detect the vulnerabilities of IoT devices, design, and implement for automatic discovery of IoT devices’ loopholes through device monitoring deployed in the system or built in simulators. The test targets are mainly routers and IP cameras. Reference [10] designed an IoT firmware vulnerability detection platform that integrates offline static detection and online dynamic detection. The platform is able to effectively identify various security weaknesses and risks in firmware such as dangerous processes, exploitable vulnerabilities, and other attack surfaces.


### 2.4. Fuzzing Test Technology

Fuzzing test [11] is a software automation testing method originally developed by Miller in 1989. This method has been widely used in software vulnerability mining and is also used to mine router equipment vulnerabilities, which is still in the exploratory stage [12]. Fuzzing is a simple and effective method for vulnerability testing, and commonly used fuzzing tools include SPIKE, Peach, Sulley, Autodafe, and GPF. Boofuzz [13] is a python-based network protocol fuzzing framework, which is a fork and subsequent version based on the Sulley fuzzing framework. The idea of the Boofuzz framework is to perform fuzz testing based on mutation and can customize the length of the data block. It also includes excellent session management and monitoring modules, which can efficiently mine potential vulnerabilities of common communication protocols in IoT devices, including http, ftp, and udp. Boofuzz is suitable for constructing fuzz format data packets of network protocols, so this paper improves the framework to be suitable for vulnerability mining of router devices.Fuzzing testing method is widely used in software vulnerability testing and has shown good performances in software vulnerability testing. In this paper, combining fuzzing testing technology, we propose RW-fuzz method for vulnerability mining on the Web interface of routers.


## 2.1. Routers

According to the “China Internet Development Report (2021),” by the end of 2020, the number of netizens in my country was 989 million. In the second half of 2020, as many as 15.698 million home routers were sold in the domestic market. The core position of the router makes it play an important role in both personal and corporate networks. Most of the routers on the market use the Web terminal for the convenience of users. Reference [2] studied 11,482 kinds of routers and found that the proportion of devices with Web interface was 83.6%. This data shows that most routers are controlled and managed through the Web. The router’s Web architecture is shown in Figure 1.Figure 1
Router Web architecture.


## 2.2. Vulnerabilities on the Web Interface of Routers

While the application of the router Web side brings convenience to users, it also brings many security risks due to the security loopholes in the Web interface. Table1 lists the common router Web-interface vulnerabilities in recent years. Hackers use these vulnerabilities to attack routers, which will bring great security threats to users.Table 1
Common router Web vulnerabilities.
Device nameCWE (list of common defects)DescribeD-Link/DIR-300CWE-352Cross-site request forgeryNetgearCWE-601URL redirects to untrusted siteD-Link DIR-600/300CWE-200Information leakageD-Link 850LCWE-319Sensitive information transmitted in clear textD-Link/DIR8xxCWE-295Improper certificate validationBillion 7700NR4CWE-798Use hardcoded certificatesLink 850LCWE-798Use hardcoded certificatesTOTOLINKCWE-20Improper certificate validationTP-LinkCWE-284Improper access control


## 2.3. Research on Router Security

The role of routers in the network makes the study of router security one of the key research directions of security researchers in recent years. Some researchers start from improving router security. Reference [3] maximizes the authentication capability of a router by embedding a device-based MAC address application to monitor user entries. The method periodically changes the password of the router, sends the encrypted password to the user, and at the same time informs the administrator about the change. The router transmits data through the Internet to improve its security. Reference [4] proposes the IDRBT-IoT Secure Router (IISR), which can resist a large number of network attacks. IISR protects the IoT ecosystem by providing a one-step solution, which therefore protects the network from malicious activity. Reference [5] presents an evaluation study of Manufacturer Usage Descriptions (MUDs), proposing a mechanism to identify and eliminate configuration vulnerabilities before creating a device’s MUD profile, which minimizes the attack surface.More researchers invest in how to detect router vulnerabilities. Literature [6] is mainly used to discover the vulnerabilities of SOHO router devices and realize automatic pattern recognition of multiple types of vulnerabilities in SOHO routers. For the D-CONF operation in popular SOHO routers, the CONF-READ communication model is extended, and it is carried out. In order to improve, an improved SRFuzzer method based on DCONF mode, fuzzification mechanism is proposed, focusing on detecting read operation problems. Reference [7] developed the WNV detector, a general and extensible framework for detecting vulnerabilities in wireless networks, which enables automated and fine-grained device identification and effectively detects security vulnerabilities in wireless routers. Reference [8] proposed the first gray-box fuzzy framework EWVHunter based on embedded device Web front-end for security analysis of embedded devices. EWVHunter can automatically detect authentication bypass vulnerabilities and command injection vulnerabilities in embedded devices by using information from official firmware and logic programs that control the terminal’s Web front-end. Reference [9] designed a black-box fuzzing tool named SIoTFuzzer, which can detect the vulnerabilities of IoT devices, design, and implement for automatic discovery of IoT devices’ loopholes through device monitoring deployed in the system or built in simulators. The test targets are mainly routers and IP cameras. Reference [10] designed an IoT firmware vulnerability detection platform that integrates offline static detection and online dynamic detection. The platform is able to effectively identify various security weaknesses and risks in firmware such as dangerous processes, exploitable vulnerabilities, and other attack surfaces.


## 2.4. Fuzzing Test Technology

Fuzzing test [11] is a software automation testing method originally developed by Miller in 1989. This method has been widely used in software vulnerability mining and is also used to mine router equipment vulnerabilities, which is still in the exploratory stage [12]. Fuzzing is a simple and effective method for vulnerability testing, and commonly used fuzzing tools include SPIKE, Peach, Sulley, Autodafe, and GPF. Boofuzz [13] is a python-based network protocol fuzzing framework, which is a fork and subsequent version based on the Sulley fuzzing framework. The idea of the Boofuzz framework is to perform fuzz testing based on mutation and can customize the length of the data block. It also includes excellent session management and monitoring modules, which can efficiently mine potential vulnerabilities of common communication protocols in IoT devices, including http, ftp, and udp. Boofuzz is suitable for constructing fuzz format data packets of network protocols, so this paper improves the framework to be suitable for vulnerability mining of router devices.Fuzzing testing method is widely used in software vulnerability testing and has shown good performances in software vulnerability testing. In this paper, combining fuzzing testing technology, we propose RW-fuzz method for vulnerability mining on the Web interface of routers.


## 3. Fuzzing Test Method for Router Web-Side Vulnerability Mining

RW-fuzzer is divided into seven modules: collection module, parsing module, test case generation module, fuzzing module, monitoring module, exception handling module, and logging module. RW-fuzzer is implemented based on the python programming language. First, the Burp Suite crawler is used to grab the http items on the Web side of the router device and manually export them to the local and then use the python parsing module to parse the data packets. All packets are then put on a queue, and their web function point interfaces are automatically fuzzed one by one. RW-fuzzer can avoid problems such as repeated data packet capture, repeated definition, and repeated field analysis for each function point. The overall structure of RW-fuzzer is shown in Figure2.Figure 2
RW-fuzzer overall structure.


### 3.1. Collection Module

When manually browsing and traversing each function point on the Web side of the router device, turn on the monitoring of the Burp Suite proxy, view some historical data packets, and export them. The collection module uses the proxy monitoring function of Burp Suite to monitor the traffic of each function point on the Web side of the router device, record the detailed information of each http data packet, and finally export all the data packets (http items) to local storage.


### 3.2. Parsing Module

The parsing module is used to process http item packets exported from Burp Suite. First, use python’s xmlparse module to parse the http item data to obtain a complete data packet object, including the http request header and http request body. Then, the request parameters and http headers of each data packet are parsed into dictionary format, so that when using python’s requests module, it can be easily made http requests. The pseudocode of the parsing module is shown in Figure3.Figure 3
Parsing module pseudocode.


### 3.3. Test Sample Generation Module

The test samples are generated by the use samples of the Boofuzz framework, and some basic test samples that can be used to detect command execution and unauthorized vulnerabilities are added. Using the boundary value generation method based on fuzzy heuristics when generating test samples can effectively increase the probability of triggering vulnerabilities in the testing process. The flowchart of test sample generation is shown in Figure4.Figure 4
Test sample generation flowchart.The mutation rules generated by the test cases refer to the IoTFuzzer [14] framework. Typical mutation-based mutation rules include the following: changing the length of the string to test for buffer overflow and randomly filling in the format character “%s%n” to test the format String vulnerability; change all fields that accept numbers to negative numbers or 0xFFFFFF to test integer overflow and array out-of-bound vulnerabilities, etc.


### 3.4. Fuzzing Module

First, convert the mutated test cases into keys and values in http packet parameters, such as {“addr”: “127.0.0.1”,“size”,0xFFFFFFF}. Secondly, use python’s requests module to convert the data in dictionary format to the http packet body. Then, parameter fuzzing is performed on the data packets of the get method or postmethod with http parameters (using the control variable method to perform mutation-based fuzzing test on the value of each variable). The pseudocode is shown in Figure5.Figure 5
Fuzzing module pseudocode.After the parameter fuzzing test is completed, the fuzzing module automatically fuzzes each field of the http packet header and uses different parsing methods for different header fields during testing. For example, for the user-agent header, only the characters before and after the slash are fuzzed, including Mozilla/5.0 and ApplewebKit/537.36. At this time, the fuzzing test also adopts the control variable strategy and successively replaces the parameters of each variable, thereby increasing the stability of the fuzzing test. The flow of the fuzzing module is shown in Figure6.Figure 6
Fuzzing module flowchart.


### 3.5. Monitoring Module

In the vulnerability mining of router devices, monitoring of network protocols is relatively easy to implement, and it is only necessary to detect whether remote services are available by sending normal data packets of the corresponding protocol. If the input length is too long, it will cause a buffer overflow, which will cause the service to crash and become temporarily inaccessible (if the device has a watchdog service, it will restart after detecting an abnormality in the service). When testing, first send a request that can cause an exception, then make a normal access request, and set a threshold for the number of requests. If the service is still unavailable after the number of normal access requests exceeds the threshold, it means that the device has a buffer overflow, memory corruption vulnerabilities such as pointer out-of-bounds.For command injection vulnerabilities, the only need is to inject a malicious command execution string into the data packet during testing and inject the command enclosed in backticks into the payload, for example: “telnetd -p 2309 -l/bin/sh.” When the server receives the test command, it will splice the received payload into the system() function parameter string. Due to the characteristics of Linux system commands, the server will execute the injected content first. Therefore, the black-box fuzz method can efficiently detect command injection vulnerabilities. In the above example, the injected command is to start the telnetd service operation. If the server has a command injection vulnerability, the attacker will be able to connect to the corresponding port directly through the socket. The pseudocode of the monitoring module is shown in Figure7.Figure 7
Monitor module pseudocode.


### 3.6. Exception Filtering Module

The exception filtering module is used to exclude false positives in fuzzing. In some cases, after getting the result of a service crash, the results of fuzzing may have false positives. For example, some http function interfaces in the background of the router device were triggered during the test, causing the router device to restart normally, and the test result was falsely reported as a service crash caused by a memory corruption vulnerability. Therefore, RW-fuzzer needs to perform secondary detection on the crash report in the final test result and eliminate false positive results by using automated or semimanual analysis methods. The flowchart of the exception filtering module is shown in Figure8.Figure 8
Anomaly filtering module flowchart.


### 3.7. Logging Module

The logging module is responsible for recording the http packet information (http item) that caused the device to crash, as well as the timestamp, url, get or post method parameter packet information that triggers the crash, etc., and export the above information to local storage. The flowchart of the logging module is shown in Figure9.Figure 9
Logging module.


## 3.1. Collection Module

When manually browsing and traversing each function point on the Web side of the router device, turn on the monitoring of the Burp Suite proxy, view some historical data packets, and export them. The collection module uses the proxy monitoring function of Burp Suite to monitor the traffic of each function point on the Web side of the router device, record the detailed information of each http data packet, and finally export all the data packets (http items) to local storage.


## 3.2. Parsing Module

The parsing module is used to process http item packets exported from Burp Suite. First, use python’s xmlparse module to parse the http item data to obtain a complete data packet object, including the http request header and http request body. Then, the request parameters and http headers of each data packet are parsed into dictionary format, so that when using python’s requests module, it can be easily made http requests. The pseudocode of the parsing module is shown in Figure3.Figure 3
Parsing module pseudocode.


## 3.3. Test Sample Generation Module

The test samples are generated by the use samples of the Boofuzz framework, and some basic test samples that can be used to detect command execution and unauthorized vulnerabilities are added. Using the boundary value generation method based on fuzzy heuristics when generating test samples can effectively increase the probability of triggering vulnerabilities in the testing process. The flowchart of test sample generation is shown in Figure4.Figure 4
Test sample generation flowchart.The mutation rules generated by the test cases refer to the IoTFuzzer [14] framework. Typical mutation-based mutation rules include the following: changing the length of the string to test for buffer overflow and randomly filling in the format character “%s%n” to test the format String vulnerability; change all fields that accept numbers to negative numbers or 0xFFFFFF to test integer overflow and array out-of-bound vulnerabilities, etc.


## 3.4. Fuzzing Module

First, convert the mutated test cases into keys and values in http packet parameters, such as {“addr”: “127.0.0.1”,“size”,0xFFFFFFF}. Secondly, use python’s requests module to convert the data in dictionary format to the http packet body. Then, parameter fuzzing is performed on the data packets of the get method or postmethod with http parameters (using the control variable method to perform mutation-based fuzzing test on the value of each variable). The pseudocode is shown in Figure5.Figure 5
Fuzzing module pseudocode.After the parameter fuzzing test is completed, the fuzzing module automatically fuzzes each field of the http packet header and uses different parsing methods for different header fields during testing. For example, for the user-agent header, only the characters before and after the slash are fuzzed, including Mozilla/5.0 and ApplewebKit/537.36. At this time, the fuzzing test also adopts the control variable strategy and successively replaces the parameters of each variable, thereby increasing the stability of the fuzzing test. The flow of the fuzzing module is shown in Figure6.Figure 6
Fuzzing module flowchart.


## 3.5. Monitoring Module

In the vulnerability mining of router devices, monitoring of network protocols is relatively easy to implement, and it is only necessary to detect whether remote services are available by sending normal data packets of the corresponding protocol. If the input length is too long, it will cause a buffer overflow, which will cause the service to crash and become temporarily inaccessible (if the device has a watchdog service, it will restart after detecting an abnormality in the service). When testing, first send a request that can cause an exception, then make a normal access request, and set a threshold for the number of requests. If the service is still unavailable after the number of normal access requests exceeds the threshold, it means that the device has a buffer overflow, memory corruption vulnerabilities such as pointer out-of-bounds.For command injection vulnerabilities, the only need is to inject a malicious command execution string into the data packet during testing and inject the command enclosed in backticks into the payload, for example: “telnetd -p 2309 -l/bin/sh.” When the server receives the test command, it will splice the received payload into the system() function parameter string. Due to the characteristics of Linux system commands, the server will execute the injected content first. Therefore, the black-box fuzz method can efficiently detect command injection vulnerabilities. In the above example, the injected command is to start the telnetd service operation. If the server has a command injection vulnerability, the attacker will be able to connect to the corresponding port directly through the socket. The pseudocode of the monitoring module is shown in Figure7.Figure 7
Monitor module pseudocode.


## 3.6. Exception Filtering Module

The exception filtering module is used to exclude false positives in fuzzing. In some cases, after getting the result of a service crash, the results of fuzzing may have false positives. For example, some http function interfaces in the background of the router device were triggered during the test, causing the router device to restart normally, and the test result was falsely reported as a service crash caused by a memory corruption vulnerability. Therefore, RW-fuzzer needs to perform secondary detection on the crash report in the final test result and eliminate false positive results by using automated or semimanual analysis methods. The flowchart of the exception filtering module is shown in Figure8.Figure 8
Anomaly filtering module flowchart.


## 3.7. Logging Module

The logging module is responsible for recording the http packet information (http item) that caused the device to crash, as well as the timestamp, url, get or post method parameter packet information that triggers the crash, etc., and export the above information to local storage. The flowchart of the logging module is shown in Figure9.Figure 9
Logging module.


## 4. Experiments and Result Analysis

In this chapter, the proposed RW-fuzzer method is used to conduct actual fuzzing experiments on several home routers to verify the vulnerability mining effect of the RW-fuzzer method. The following is a detailed description of a certain experimental process. The specific experimental environment is as follows: OS: Ubuntu 16.04, software environment: Burp Suite and Boofuzz, and router equipment: a certain model of TP-Link home router.


### 4.1. Procedure

The IP address of the background Web management service of the experimental router is 192.168.1.1, and the proposed RW-fuzzer is used to mine the Web service for vulnerabilities during the experiment. First, use the collection module to monitor traffic and export the monitored HTTP packets. The exported packets are then parsed using the parsing module, and fuzzing is performed using the test case generation module and the fuzzing module. After the fuzzing test, there are the following vulnerability records in the log file recorded by the logging module (as shown in Figure10), indicating that the experimental router has a buffer overflow vulnerability. The URL of the vulnerability point is http://192.168.1.1/userRpm/PingIframeRpm.htm.Figure 10
Vulnerability URL logging.For further vulnerability analysis, we search in the log file for the parameter list of the get method in the data package that causes the vulnerability, which is shown in Figure11.Figure 11
Vulnerable packet logging.The triggering of this vulnerability can cause the router Web service to crash, making the router background service inaccessible for a short period of time. At this time, the browser is used to access the background Web service of the experimental router, and the browser prompts that the Web service on port 80 cannot be connected. Therefore, it is judged that the experiment has triggered a memory corruption vulnerability.


### 4.2. Analysis of Results

By analyzing the fields in the post data packet of the http protocol, it can be concluded that the mutation fields of the vulnerability are ping_addr and sendNum. The test value of the sendNum field is a boundary value, and it can be determined that this field triggers a memory corruption vulnerability. Next, the firmware of the experimental router was obtained from the official service support of TPLINK [15] and disassembled using binwalk software. After the disassembly is successful, use the IDA software to load the httpd service and analyze the disassembly code (0x00451A4C) of the sendNum string, as shown in Figure 12. It can be seen from the disassembly code that the httpd service uses the atoi function to convert the sendNum parameter in the http protocol received from the Web side.Figure 12
httpd disassembly code.Further analysis of the execution flow of the return value of the atoi function shows that at the address of 0x004738A0, the value of the v0 register is the result of the addition of the previous addu instruction, as shown in Figure13. In the addu instruction, the value of the s1 register is a legal address, and the value of the t0 register is the result converted by the atoi function. Since the value of the t0 register during fuzzing is -1, the result of the addu instruction (v0 register) is an invalid address. The experimental router caused an illegal memory access when using this illegal address, causing the service to crash.Figure 13
Illegal memory access disassembled code match.In addition to testing the device, fuzzing tests were also performed on 4 real-world devices including D-Link, B-Link, and ASUS router equipment manufacturers, and 4 nday vulnerabilities were found (as shown in Table2). The effectiveness and applicability of the method are verified by experiments.Table 2
Router Web vulnerability discovered.
Equipment manufacturer and modelVulnerabilities foundD-Link (DIR-816)CNVD-2020-42655B-Link (WR-9000)CVE-2016-6563, CVE-2016-6563ASUS (RT-68U)CVE-2018-6636TP-LinkBuffer overflow


### 4.3. Comparison

IoTFuzzer [14] is an application-based fuzzing framework designed to discover memory corruption in physical IoT devices without firmware images. It leverages fuzzing and taint analysis, focusing only on moving to the Web interface and detecting only through activity check memory corruption, and the framework is not strong enough to find Web server vulnerabilities. This article refers to the mutation rules generated by test cases in its framework to find Web-side vulnerabilities. Reference [16] uses qemu to simulate the web interface of some Linux-based devices. This method does not work with Web interfaces that contain special hardware-related operations such as Wi-Fi configuration. The most popular solution for finding vulnerabilities is to obfuscate the SOHO router’s Web server module. However, its effectiveness is limited by the lack of input specifications, the router’s internal operational state, and a test environment recovery mechanism. The RW-fuzzer method proposed in this paper is effective and applicable to the router vulnerability mining on the Web side.


## 4.1. Procedure

The IP address of the background Web management service of the experimental router is 192.168.1.1, and the proposed RW-fuzzer is used to mine the Web service for vulnerabilities during the experiment. First, use the collection module to monitor traffic and export the monitored HTTP packets. The exported packets are then parsed using the parsing module, and fuzzing is performed using the test case generation module and the fuzzing module. After the fuzzing test, there are the following vulnerability records in the log file recorded by the logging module (as shown in Figure10), indicating that the experimental router has a buffer overflow vulnerability. The URL of the vulnerability point is http://192.168.1.1/userRpm/PingIframeRpm.htm.Figure 10
Vulnerability URL logging.For further vulnerability analysis, we search in the log file for the parameter list of the get method in the data package that causes the vulnerability, which is shown in Figure11.Figure 11
Vulnerable packet logging.The triggering of this vulnerability can cause the router Web service to crash, making the router background service inaccessible for a short period of time. At this time, the browser is used to access the background Web service of the experimental router, and the browser prompts that the Web service on port 80 cannot be connected. Therefore, it is judged that the experiment has triggered a memory corruption vulnerability.


## 4.2. Analysis of Results

By analyzing the fields in the post data packet of the http protocol, it can be concluded that the mutation fields of the vulnerability are ping_addr and sendNum. The test value of the sendNum field is a boundary value, and it can be determined that this field triggers a memory corruption vulnerability. Next, the firmware of the experimental router was obtained from the official service support of TPLINK [15] and disassembled using binwalk software. After the disassembly is successful, use the IDA software to load the httpd service and analyze the disassembly code (0x00451A4C) of the sendNum string, as shown in Figure 12. It can be seen from the disassembly code that the httpd service uses the atoi function to convert the sendNum parameter in the http protocol received from the Web side.Figure 12
httpd disassembly code.Further analysis of the execution flow of the return value of the atoi function shows that at the address of 0x004738A0, the value of the v0 register is the result of the addition of the previous addu instruction, as shown in Figure13. In the addu instruction, the value of the s1 register is a legal address, and the value of the t0 register is the result converted by the atoi function. Since the value of the t0 register during fuzzing is -1, the result of the addu instruction (v0 register) is an invalid address. The experimental router caused an illegal memory access when using this illegal address, causing the service to crash.Figure 13
Illegal memory access disassembled code match.In addition to testing the device, fuzzing tests were also performed on 4 real-world devices including D-Link, B-Link, and ASUS router equipment manufacturers, and 4 nday vulnerabilities were found (as shown in Table2). The effectiveness and applicability of the method are verified by experiments.Table 2
Router Web vulnerability discovered.
Equipment manufacturer and modelVulnerabilities foundD-Link (DIR-816)CNVD-2020-42655B-Link (WR-9000)CVE-2016-6563, CVE-2016-6563ASUS (RT-68U)CVE-2018-6636TP-LinkBuffer overflow


## 4.3. Comparison

IoTFuzzer [14] is an application-based fuzzing framework designed to discover memory corruption in physical IoT devices without firmware images. It leverages fuzzing and taint analysis, focusing only on moving to the Web interface and detecting only through activity check memory corruption, and the framework is not strong enough to find Web server vulnerabilities. This article refers to the mutation rules generated by test cases in its framework to find Web-side vulnerabilities. Reference [16] uses qemu to simulate the web interface of some Linux-based devices. This method does not work with Web interfaces that contain special hardware-related operations such as Wi-Fi configuration. The most popular solution for finding vulnerabilities is to obfuscate the SOHO router’s Web server module. However, its effectiveness is limited by the lack of input specifications, the router’s internal operational state, and a test environment recovery mechanism. The RW-fuzzer method proposed in this paper is effective and applicable to the router vulnerability mining on the Web side.


## 5. Conclusion and Outlook

This paper proposes a RW-fuzzer method, which uses the http packets collected by the Burp Suite tool as the input of the fuzzing test. And the algorithm rules of the Boofuzz framework are improved using a mutated use sample generation algorithm, which automatically generates mutated samples. Thus, we can mine the vulnerabilities on the Web side of the router. Based on RW-fuzzer, the paper conducted fuzzing tests on 4 actual devices including D-Link, B-Link, ASUS, and other router equipment manufacturers and found 4 nday vulnerabilities and one 0day vulnerability. Experiments show that the RW-fuzzer method is effective and applicable. However, this method still has the defects of high tool false positive rate, low single-threaded request rate, and long time spent traversing each function point on the Web page of the device. In the future work, we will study to optimize the request speed of Web fuzzing and improve it into a multithreaded way in the main fuzzing module request and monitoring module. And we will improve the data parsing module and optimize the parsing rate, so that it supports more http protocol packet formats such as xml and json.



---

*Source: 5311295-2022-04-25.xml*