Skip to main content

ZigBee Security Assessment

ZigBee (802.15.4) is a relatively new protocol compared to Wi-Fi (802.11), but with low power consumption and long battery life it is ideal for Home Network Systems such as thermostats etc. The reason behind ZigBee devices being low power consuming because it work on very low frequency and have a fewer commands to send compared to Wi-Fi.

Since it's relatively new protocol and not much popular, there are fewer tools/ frameworks to test it. However some good software/ hardware are available. They can be purchased/ downloaded from respective sites.

Atmel RZ Raven USB Stick (hardware)
Atmel JTAGICE mkII On-Chip Programmer (hardware)
Atmel 100-mm to 50-mm JTAG standoff adapter (hardware)
50-mm male-to-male header (hardware)
AVR Studio for Windows (software, free)
KillerBee Firmware for the RZUSBSTICK (software, free)
A Windows host for programming the RZ Raven USB Stick (one-time operation)

Issues to be looked into ZigBee:
Similar to 802.11 ZigBee may also suffer from same issues, like encryption, key provisioning mechanism, authentication etc. ZigBee uses AES for encryption but how the keys are being provisioned can lead to defeat entire encryption purpose. Then how ZigBee devices being authenticated when they try to join a network.

KillerBee provides an excellent framework to do security assessment. Some of the tools are:
zbstumbler: for network discovery
zbdump: packet sniffer
zbreplay: packet replay
zbdsniff: sniffing packets

Though I have never personally worked on ZigBee, hoping to get my hands on shortly at it and documenting the findings.


Me said…
Have you found anything interesting yet? :)

Popular posts from this blog

File Upload through Null Byte Injection

Sometimes, during file upload we come across situation wherein there would be check on the file extension at the client side as well as server side too. If the application does allow only .jpeg extension to be uploaded, the client side java script checks for the extension of the file before passing the request. We all know that how easily this can be defeated.
Some applications, checks for the extension at the server side also. That's not easy to bypass. However there are some ways with which it still can be bypassed. Most of server side scripts are written in high level languages such as Php, Java etc who still use some C/C++ libraries to read the file name and contents. That leads to the problem. In C/C++ a line ends with /00 or which is called Null Byte. So whenever the interpreter sees a null byte at the end of the a string, it stops reading thinking it has reached at the end of the string.
This can be used for the bypass. It works for many servers, specially php servers. Th…

SQL Injection in search field

Earlier I had written about performing SQL injection in search field and how to do a DoS attack and privilege escalation using 'Like' operators. Now another SQLi exploitation I came across recently. That too in the search field. This becomes important as lots of people don't pay much attention on the search forms/ fields in the application. My aim is to show that a search form can also be exploited with SQL Injection. The following queries are based on a real world exploitation. The steps and data are for just illustration purpose only. Suppose, the search form provides the details of users who have accessed the application some time and their login time details etc, we just need to provide their name in the search box provided. All the data were being going as Post request. So, to just fingerprint the database, I provide, 'nil'+'esh' in the search field and it successfully gives me the results. That means the database behind the application is concatenat…

Insecure protocols

Some basic insecure protocols and risk associated with them: