"The Codenomicon tools are amazing. Using them is like being attacked by the most relentless adversary who uses every possible method to find flaws in your code
We fixed subtle crash bugs in Samba that had been in the code for over ten years. We would never have found those bugs without the Codenomicon tools.
If you're serious about implementing protocols correctly, you need the Codenomicon tools."
-- Jeremy Allison,
Co Creator of Samba
Codenomicon Whitepaper
Fuzzing Bluetooth
Crash-testing bluetooth-enabled devices
Tommi Mäkilä, Jukka Taimisto and Miia Vuontisjärvi
info@codenomicon.com
Codenomicon Ltd.
Abstract
Bluetooth technology is used in many different devices: computers, mobile phones, handsfree equipment, and the car audio systems for example. When the applications become more critical, the importance of security and robustness testing is highlighted.
Lately, more attention has been paid to security of Bluetooth systems, but the focus has been on pairing and authentication. Handling of malformed data has been largely ignored. Yet it is the malformed data, broken inputs that Bluetooth systems have little tolerance for. Test results from plugfest events are worrying: failure rate of over 80% is devastating.
Malformed input may cause Bluetooth device operation to slow down, or device may show unusual behavior or crash completely. This causes degraded quality of service and even denial of service (DoS). In a worst case scenario, malformed input can be used by an outside attacker to gain unauthorized access to Bluetooth device.
