IoTFuzzer: Discovering Memory Corruptions in IoT Through App-based Fuzzing
Network and Distributed System Security Symposium, 2018
331 citations recorded by the source corpus.
—With more IoT devices entering the consumer market, it becomes imperative to detect their security vulnerabilities before an attacker does. Existing binary analysis based approaches only work on firmware, which is less accessible except for those equipped with special tools for extracting the code from the device. To address this challenge in IoT security analysis, we present in this paper a novel automatic fuzzing framework, called I O TF UZZER , which aims at finding memory corruption vulnerabilities in IoT devices without access to their firmware images. The key idea is based upon the observation that most IoT devices are controlled through their official mobile apps, and such an app often contains rich information about the protocol it uses to communicate with its device. Therefore, by identifying and reusing program-specific logic (e.g., encryption) to mutate the test case (particularly message fields), we are able to effectively probe IoT targets without relying on any knowledge about its protocol specifications. In our research, we implemented I O TF UZZER and evaluated 17 real-world IoT devices running on different protocols, and our approach successfully identified 15 memory corruption vulnerabilities (including 8 previously unknown ones).
Subfields: Artificial Intelligence, Software, Signal Processing
View Paper: https://www.semanticscholar.org/paper/778338a5d75dd82f45a7c4877222525ec670308b
Citations in the corpus
- SoK: Security Evaluation of Home-Based IoT Deployments (2019, unknown): “[43] presented IoTFuzzer that instruments the mobile application within an IoT deployment to find bugs on the IoT device.”
- Edge Computing Security: State of the Art and Challenges (2019, unknown): “[47] who demonstrated fuzzing mechanisms from the IoT-app side to identify possible memory corruptions without the need of firmware.”
- Fuzzing: A Survey for Roadmap (2022, unknown): “Blackbox fuzzing does not have any knowledge about the internal states of each execution [3, 29, 36, 78, 99].”