# iot security Published articles for iot security. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Mongoose: Preauth RCE and mTLS Bypass on Millions of Devices DevFeed: [Mongoose: Preauth RCE and mTLS Bypass on Millions of Devices]() Original publisher: [Read original article]() Author: Simone Margaritelli Published: 2026-04-01T22:00:00Z Content type: article Language: en Sources: [evilsocket]() Topics: [Mongoose](), [Vulnerabilities](), [Security](), [Embedded Systems](), [Internet of things](), [C](), [cross-platform](), [HTTP](), [MQTT](), [WebSocket]() Tags: [authentication-bypass](), [buffer-overflow](), [c](), [cesanta](), [cross-platform](), [cve](), [cve-2026-5244](), [cve-2026-5245](), [cve-2026-5246](), [cybersecurity](), [embedded](), [embedded-devices](), [embedded-systems](), [exploit](), [heap-overflow](), [http](), [https](), [industrial-control](), [iot](), [iot-security](), [library](), [mdns](), [mips](), [mongoose](), [mqtt](), [mtls](), [rce](), [responsible-disclosure](), [security](), [stack-overflow](), [tls](), [vulnerability-research]() ### AI overview The article reports three independently exploitable vulnerabilities in Mongoose v7.20, an embedded C networking library used in IoT devices: an mTLS authentication bypass, a preauthentication heap-overflow RCE through client public-key parsing, and a preauthentication RCE through mDNS over UDP. Mongoose v7.21 reportedly includes patches for the issues, which were assigned CVE-2026-5244, CVE-2026-5245, and CVE-2026-5246. ### Source excerpt So, Mongoose. I ## TP-Link Tapo C200: Hardcoded Keys, Buffer Overflows and Privacy in the Era of AI Assisted Reverse Engineering DevFeed: [TP-Link Tapo C200: Hardcoded Keys, Buffer Overflows and Privacy in the Era of AI Assisted Reverse Engineering]() Original publisher: [Read original article]() Author: Simone Margaritelli Published: 2025-12-17T23:00:00Z Content type: article Language: en Sources: [evilsocket]() Topics: [Reverse Engineering](), [Vulnerabilities](), [Security](), [Embedded Systems](), [Android](), [Amazon Web Services]() Tags: [ai](), [ai-assisted-reverse-engineering](), [android](), [assembly](), [aws](), [china](), [cve](), [cve-2025-14299](), [cve-2025-14300](), [cve-2025-8065](), [cybersecurity](), [embedded-devices](), [embedded-systems](), [exploit](), [firmware](), [ghidra](), [ghidramcp](), [hardcoded-credentials](), [integer-overflow](), [iot](), [iot-security](), [memory](), [mips](), [privacy](), [re](), [reverse-engineering](), [reversing](), [security](), [security-research](), [security-vulnerabilities](), [tapo-c200](), [tapo-camera](), [tp-link](), [tplink](), [vulnerability-research]() ### AI overview This article describes an AI-assisted reverse-engineering investigation of TP-Link Tapo C200 camera firmware. The author reports finding several security vulnerabilities affecting about 25,000 devices directly exposed on the internet, and discusses the tools and process used. ### Source excerpt Hi friends and welcome to the last post for this year! Whenever someone asks me how to get started with reverse engineering, I always giv ## IoT Security & Threat Modeling DevFeed: [IoT Security & Threat Modeling]() Original publisher: [Read original article]() Author: Adam Published: 2021-04-22T00:00:00Z Content type: opinion Language: en Sources: [Shostack & Friends Blog]() Topics: [Internet of things](), [Security](), [Architecture & Design]() Tags: [devices](), [government](), [iot](), [iot-security](), [security](), [systems](), [uk]() ### AI overview This commentary connects the UK Government's Code of Practice for Consumer IoT Security with threat modeling. It highlights IoT-facilitated technology abuse, fitness systems, and children's products, arguing that technologists should consider broader harms and ask what can go wrong beyond the STRIDE framework. ### Source excerpt Expanding on the UK Government's 'The Uk Code of Practice for Consumer IoT Security' and how it aligns with Threat Modeling. ## 'Best Practices for IoT Security' DevFeed: ['Best Practices for IoT Security']() Original publisher: [Read original article]() Author: Adam Published: 2020-06-08T00:00:00Z Content type: opinion Language: en Sources: [Shostack & Friends Blog]() Topics: [Internet of Things (IoT)](), [Security]() Tags: [iot](), [iot-security](), [research](), [security]() ### AI overview The article highlights a draft by Christopher Bellman and Paul C. van Oorschot that examines what "best practice" means in IoT security. The draft distinguishes security activities from desired outcomes and notes confusion in existing guidelines. ### Source excerpt There's an interesting new draft, Best Practices for IoT Security: What Does That Even Mean? by Christopher Bellman and Paul C. van Oorschot. ## This Is Not a Post About BLE, Introducing BLEAH DevFeed: [This Is Not a Post About BLE, Introducing BLEAH]() Original publisher: [Read original article]() Author: Simone Margaritelli Published: 2017-09-23T15:06:56Z Content type: tutorial Language: en Sources: [evilsocket]() Topics: [Bluetooth](), [Security](), [Fuzzing/Fuzz testing](), [Internet of things](), [Tool](), [Open Source]() Tags: [ble](), [bleah](), [bluetooth](), [bluetooth-low-energy](), [btle](), [cybersecurity](), [fuzzing](), [hack](), [iot](), [iot-security](), [offensive-tools](), [open-source](), [security](), [tools](), [wireless-security]() ### AI overview An introduction to hacking Bluetooth Low Energy devices that also presents BLEAH, an open-source tool. The article discusses BLE's discoverability, connection behavior, data access, and lack of built-in protocol security, while noting that automatic fuzzing features were kept in a private fork. ### Source excerpt This is not a post about BLE, but rather on how to hack it ... well, to be honest, BLE devices are usually very easy to hack, so it's just a quick intro to it, I'll also take the chance to open source one of the last tools I've made and that I kept private so far. I moved the features I thought to be dangerous ( aka: auto fuzzing all the BLE things and bring chaos ) in a private fork which will stay private, however it's not that complicated to chain bleah with other tools ( cough ... radamsa ... cough ) and have lots of fun. Oh and this is also because someone asked me some intro on BLE, so yeah, his fault. ## Hacking a Herb Vaporizer to Set Its Temperature Limit From 190C to 6553.5C Remotely DevFeed: [Hacking a Herb Vaporizer to Set Its Temperature Limit From 190C to 6553.5C Remotely]() Original publisher: [Read original article]() Author: Simone Margaritelli Published: 2017-08-25T01:10:53Z Content type: opinion Language: en Sources: [evilsocket]() Topics: [Hacking](), [Bluetooth](), [Security](), [Hardware]() Tags: [ble](), [bluetooth](), [bluetooth-low-energy](), [btle](), [crafty](), [crafty-vaporizer](), [cybersecurity](), [embedded-devices](), [firmware](), [hacking](), [iot-security](), [linux](), [low-energy](), [no-authentication](), [protocol-reversing](), [responsible-disclosure](), [security](), [terminal](), [vaporizer]() ### AI overview The article describes reverse engineering the Crafty vaporizer's mobile application and Bluetooth Low Energy interface. It reports that device descriptors could be read and written without authentication and that the temperature value was stored as two bytes, allowing a remote attempt to change the limit from 190°C to 6553.5°C. The author did not test the modified setting. ### Source excerpt Tonight my brain decided, instead of sleeping (why even bother trying, right?), to start a new short adventure in the Bluetooth Low Energy world. I'm a happy Crafty vaporizer owner and as I discovered by chance, I can access it using my laptop.