Skip to content

Commit 80f3f49

Browse files
authored
Merge pull request #1884 from HackTricks-wiki/update_Shelly_IoT_door_controller_config_fail__leaving_yo_20260211_190152
Shelly IoT door controller config fail leaving your garage, ...
2 parents 6d85af2 + 00b4484 commit 80f3f49

1 file changed

Lines changed: 22 additions & 0 deletions

File tree

  • src/generic-methodologies-and-resources/pentesting-wifi

src/generic-methodologies-and-resources/pentesting-wifi/README.md

Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -911,8 +911,30 @@ These methods, particularly PIN entry, are susceptible to the same vulnerabiliti
911911
912912
**EvilDirect Hijacking** is an attack specific to Wi-Fi Direct. It mirrors the concept of an Evil Twin attack but targets Wi-Fi Direct connections. In this scenario, an attacker impersonates a legitimate group owner with the aim of deceiving devices into connecting to a malicious entity. This method can be executed using tools like `airbase-ng` by specifying the channel, ESSID, and MAC address of the impersonated device:
913913
914+
## Commissioning AP persistence & dual-homed IoT pivoting (Shelly Gen4 case)
915+
916+
Some consumer IoT relays/controllers keep the commissioning **open AP** active after joining the IoT WLAN (e.g., Shelly Gen4 SSIDs starting with `Shelly`). The device stays **dual-homed**: an AP interface with default IP `192.168.33.1` plus a client interface on the internal WLAN.
917+
918+
**Abuse flow (Wi‑Fi proximity required):**
919+
920+
1. Join the provisioning AP, obtain a DHCP lease, and browse the **AP-side HTTP API**.
921+
2. Trigger relays via unauthenticated endpoints, e.g. `http://192.168.33.1/relay/0?turn=on` (door/gate/garage impact). Firmware upload endpoints can add persistence.
922+
3. Use it as a **pivot**: Shelly scripting can send HTTP from the internal interface to other LAN hosts. Example pivot to another Shelly at `10.0.98.221`:
923+
```javascript
924+
Shelly.addEventHandler(function (event) {
925+
if (event.component === "switch:0" && event.info.state) {
926+
Shelly.call("HTTP.GET", { url: "http://10.0.98.221/light/0?turn=on" });
927+
}
928+
});
929+
```
930+
Swap the URL for any reachable internal HTTP target; dual-homing avoids extra routing/NAT work.
931+
4. At-scale: query vendor SSIDs on **wigle.net** (e.g., `Shelly`) to locate commissioning APs for on-site exploitation.
932+
933+
For persistence, leave the commissioning AP enabled.
934+
914935
## References
915936
937+
- [https://www.pentestpartners.com/security-blog/shelly-iot-door-controller-config-fail-leaving-your-garage-home-and-security-exposed/](https://www.pentestpartners.com/security-blog/shelly-iot-door-controller-config-fail-leaving-your-garage-home-and-security-exposed/)
916938
- [https://posts.specterops.io/modern-wireless-attacks-pt-i-basic-rogue-ap-theory-evil-twin-and-karma-attacks-35a8571550ee](https://posts.specterops.io/modern-wireless-attacks-pt-i-basic-rogue-ap-theory-evil-twin-and-karma-attacks-35a8571550ee)
917939
- [https://posts.specterops.io/modern-wireless-attacks-pt-ii-mana-and-known-beacon-attacks-97a359d385f9](https://posts.specterops.io/modern-wireless-attacks-pt-ii-mana-and-known-beacon-attacks-97a359d385f9)
918940
- [https://posts.specterops.io/modern-wireless-tradecraft-pt-iii-management-frame-access-control-lists-mfacls-22ca7f314a38](https://posts.specterops.io/modern-wireless-tradecraft-pt-iii-management-frame-access-control-lists-mfacls-22ca7f314a38)

0 commit comments

Comments
 (0)