A bash script for searching extracted firmware file systems to identify security issues, sensitive data, and interesting artifacts.
Firmwalker is a bash script that automates security analysis of extracted firmware file systems from IoT devices and embedded systems. It searches through file systems for sensitive information, configuration files, potential vulnerabilities, and interesting artifacts that could indicate security issues. The tool helps security researchers and penetration testers quickly identify attack surfaces in firmware without manual file-by-file examination.
Security researchers, penetration testers, IoT developers, and firmware analysts who need to examine firmware for security vulnerabilities, sensitive data exposure, or configuration issues.
Firmwalker saves time by automating tedious manual searches through firmware file systems, provides comprehensive checks for common security issues, and offers extensibility through customizable data files and ESLint integration for static analysis.
Script for searching the extracted firmware file system for goodies!
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Automates detection of sensitive files like etc/shadow, SSL certificates, and configuration files, covering a wide range of IoT-specific artifacts as detailed in the README.
Supports customization through data files and ESLint rules, allowing users to add new search patterns and static analysis checks, enhancing adaptability.
Runs with a single bash command using path arguments, requiring minimal setup beyond optional ESLint installation for static analysis.
Combines searches for keywords, services, and data extraction like URLs and IPs, providing a holistic view of potential firmware vulnerabilities.
Requires global npm installation of ESLint for static code analysis, adding complexity and potential version conflicts for users.
Only generates plain text files, lacking support for structured formats like JSON or CSV, which complicates integration with other security tools.
Shodan integration is marked as experimental in the README, meaning it may be unstable or lack comprehensive documentation for reliable use.