Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixed Language on Securing-your-IoT-from-hacking.md #1433

Merged
merged 1 commit into from
Dec 6, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/Securing-your-IoT-from-hacking.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
## General Weaknesses

Whenever you add devices to your network you generate additional points of potential intrusion. This is not only valid for your mobile phones and computers, but also for you Smart TV, you Alexa, or all of your SONOFF devices (ESP8266).
Whenever you add devices to your network, you generate additional points of potential intrusion. This is not only valid for your mobile phones and computers, but also for your Smart TV, your Alexa, or all of your SONOFF devices (ESP8266).

There are following potential risks you have to mitigate:

Expand All @@ -14,10 +14,10 @@ There are following potential risks you have to mitigate:
It is possible to [set a password to the webadmin interface]( https://github.com/arendst/Tasmota/pull/12900), however ESP8266 devices *SHALL* not be exposed to internet or accessible to other network clients. (e.g. users in the same network) [[1]](https://github.com/arendst/Tasmota/discussions/14166#discussioncomment-1872750) [[2]](https://github.com/arendst/Tasmota/discussions/14166#discussioncomment-1871619).

#### Scenario 2
If someone is able to get your WLAN key, he can login into your network, if he is nearby and scan for any traffic and for any devices. Many communication is not encrypted in your WLAN by default. Therefore be part of your WLAN gives the attacker a great opportunity to screw-up the rest of your infrastructure. Also be part of your WLAN does mean, that the attacker can use your IP-Address and your traffic to do nasty things.
If someone is able to get your WLAN key, they can login into your network. If they are nearby, they can scan for any traffic and for any devices. Many communications are not encrypted on your WLAN by default. Therefore being part of your WLAN gives the attacker a greater opportunity to screw-up the rest of your infrastructure. Also being part of your WLAN does mean, that the attacker can use your IP-Address and your traffic to do nasty things.

#### Scenario 3
If you can hack an ESP82xx device, you might get access to the keys stored in the device. For example, the MQTT password allows you to read ALL of your devices and change any device at any time. With the information of the MQTT-Server user/password, it might be not required anymore to physically be in your WLAN. Maybe your MQTT Server is publicly accessible. Then the attacker can control your home from any place.
If you can hack an ESP82xx device, you might get access to the keys stored in the device. For example, the MQTT password allows you to monitor and control ALL of your devices at any time. If you are using a publicly accessible MQTT Server and an attacker has captured your MQTT Server infomation (e.g. hostname, user, and password), an attacker can monitor and control your home from anywhere on the Internet.

Update: Beginning with version 6.0.0, passwords are not directly exposed through the serial connection or web interface in configuration mode. Therefore it is now less simple, **however still possible** to obtain the MQTT or WLAN password from a device. Such can be accomplished by downloading a configuration backup via the web UI of the device and decoding it using the `decode-config.py` script found in the Tasmota `tools` folder.

Expand Down
Loading