IoTGoat - IoTGoat is a deliberately insecure firmware creat

项目说明

<p align="center"><img src="/images/.png" alt="IoTGoat" width="250" height="350" /></p>

Description

The IoTGoat Project is a deliberately insecure firmware based on OpenWrt and maintained by OWASP as a platform to educate software de and security professionals with testing commonly found in IoT devices. The challenges are based on the OWASP IoT Top 10 noted below, as well as "easter eggs" from project contributors. For a list of challenges, see the IoTGoat challenges wiki page.

| OWASP IoT Top 10 2018 | Description |
| :--- | :--- |
| I1 Weak, Guessable, or Hardcoded Passwords | Use of easily bruteforced, publicly a, or unchangeable credentials, including backdoors in firmware or client software that grants unauthorized access to deployed systems. |
| I2 Insecure Network Services | Unneeded or insecure network services running on the device itself, especially those exposed to the internet, that compromise the confidentiality, integrity/authenticity, or a of information or allow unauthorized remote control. |
| I3 Insecure Ecosystem Interfaces | Insecure web, backend API, cloud, or mobile interfaces in the ecosystem outside of the device that allows compromise of the device or its related components. Common issues include a lack of authentication/authorization, lacking or weak encryption, and a lack of input and output filtering. |
| I4 Lack of Secure Update Mechanism | Lack of ability to securely update the device. This includes lack of firmware on device, lack of secure delivery \(un-encrypted in transit\), lack of anti-rollback mechanisms, and lack of notifications of security changes due to updates. |
| I5 Use of Insecure or Outdated Components | Use of deprecated or insecure software components/libraries that could allow the device to be compromised. This includes insecure customization of operating system platforms, and the use of third-party software or hardware components from a compromised supply chain |
| I6 Insufficient Privacy Protection | User’s personal information stored on the device or in the ecosystem that is used insecurely, improperly, or without permission. |
| I7 Insecure Data Transfer and Storage | Lack of encryption or access control of sensitive data anywhere within the ecosystem, including at rest, in transit, or during processing |
| I8 Lack of Device Management | Lack of security support on devices deployed in production, including asset management, update management, secure decommissioning, systems monitoring, and response capabilities. |
| I9 Insecure Default Settings | Devices or systems shipped with insecure default settings or lack the ability to make the system more secure by restricting operators from modifying configurations. |
| I10 Lack of Physical Hardening | Lack of physical hardening measures, allowing potential attackers to gain sensiti that can help in a future remote attack or take local control of the device. |

Getting started

Several methods exist to get started with hacking IoTGoat.

1. For those looking to extract the filesystem, analyze configurations and binaries statically, download the latest precompiled firmware release from Refer to OWASP's Firmware Security Testing Methodology to help with identifying .

2. For dynamic web testing and binary runtime analysis, the quickest way to get started is downloading the latest "IoTGoat-x86.vmdk" () and create a custom machine using the IoTGoat disk image. Select the following operating system details Type: Linux : Linux 2.6 / 3.x / 4.x (32-bit) and Enable PAE/NX in machine settings. Both the .vmdk and .vdi have been tested in the latest release (April 2020) for Windows 10, Ubuntu 18.04 LTS, and MacOS Moja to OWASP's Web Security Testing Guide and ASVS projects for additional guidance on identifying web application

3. Emulate firmware with opensource tools (e.g. Firmadyne, ARM-X Framework, and FAT) that le QEMU to IoTGoat locally.

4. Use the IoTGoat-raspberry-pi2-sysupgrade.img firmware to flash on a Raspberry Pi 2 (BRCM2708 & BRCM2709).

5. Use the Docker setup to run IoTGoat in a containerized en. Refer to the Docker setup guide for more details.

Refer to the Getting started page for additional details and screencaptures.

Building from source

OpenWrt can build many different CPU platforms and boards. Building from source gi the flexibility to flash IoTGoat on supported OpenWrt hardware. Ensure 10-15GB disk space is a with at least 4GB of RAM and a supported Linux distribution such as Ubuntu 18.04. Use the following steps to get started with building custom firmware.

> Do e as a normal user, don't use root user or sudo when building!

The first build will take some time to complete and will vary based on the provided internet connection for downloading the toolchain. Once a successful build is complete, the compiled firmware will be placed in the following directory IoTGoat/OpenWrt/openwrt-18.06.2/bin/targets/ depending on the target selected in menuconfig. For example, IoTGoat Raspberry Pi 2 firmware will be located in the following directory IoTGoat/OpenWrt/openwrt-18.06.2/bin/targets/brcm2708/bcm2709. IoTGoat build configuration files are made a for x86 (.config-x86) and Raspberry Pi 2 (.config-rpi) platforms.

#### Project leaders

* Aaron Guzman ()
* Fotios Chantzis
* Paulino Calderon

Contributors

* Parag Mhatre ()
* Abhina (cyanide284)
* Jason Andress ()
* @0x48piraj
* Abdallah Ajjawi ()
* Amar Djebbara ()

Screenshots

![]()
***
![]()
***
![]()
***
![]()

License

The MIT License (MIT)

项目信息

开发语言：C

Star 数：943

技术要点

该项目属于漏洞知识库方向的开源资源，代码结构清晰，适合安全研究人员学习参考。项目围绕 IoTGoat is a deliberately insecure firmware created to educate software developers and security professionals with testing commonly found vulnerabilities in IoT devices.展开，提供了可运行的实现，对理解相关安全机制、工具原理与攻防技术具有较高的研究价值。

从技术实现角度看，此类项目的核心在于对底层原理的深入理解与工程化落地。开发者在研究过程中可以结合官方文档与社区讨论，梳理项目的初始化流程、核心模块职责与数据流转，逐步掌握其中的技术细节与设计思路。

使用与学习建议

1. 下载源码压缩包，解压到本地环境。

2. 根据项目类型准备对应的运行环境与依赖。

3. 按照 README 中的步骤完成配置与部署。

4. 在隔离的测试环境中运行验证，避免影响生产系统。

免责声明

本资源来源于开源社区，仅供安全研究、技术学习与合法授权范围内的攻防演练使用，请勿用于任何非法或侵害他人权益的用途。使用本项目产生的一切后果由使用者自行承担。