<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Wireless on it-learn.io | IT, Networking &amp; Cybersecurity Blog</title><link>https://blog.it-learn.io/tags/wireless/</link><description>Recent content in Wireless on it-learn.io | IT, Networking &amp; Cybersecurity Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 06 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.it-learn.io/tags/wireless/index.xml" rel="self" type="application/rss+xml"/><item><title>Bluetooth Exploitation (BlueBorne): No Pairing Needed, No Interaction Required</title><link>https://blog.it-learn.io/posts/2026-05-06-bluetooth-blueborne-exploitation-no-pairing-needed/</link><pubDate>Wed, 06 May 2026 00:00:00 +0000</pubDate><guid>https://blog.it-learn.io/posts/2026-05-06-bluetooth-blueborne-exploitation-no-pairing-needed/</guid><description>&lt;p&gt;Bluetooth was designed as a cable replacement — a short-range, low-power protocol for connecting peripherals. Security was something of an afterthought. The protocol&amp;rsquo;s authentication model assumed that physical proximity implied trust. Pairing, in early versions, was little more than a shared PIN exchanged between devices.&lt;/p&gt;
&lt;p&gt;The BlueBorne vulnerability cluster, disclosed by Armis Security in September 2017, shattered that proximity-as-trust assumption. BlueBorne proved that an attacker could achieve remote code execution on a Bluetooth-enabled device — Android phone, Linux server, Windows laptop, IoT device — without the device being discoverable, without any user interaction, and without any prior pairing. The attacker needed only a Bluetooth adapter and proximity.&lt;/p&gt;</description></item></channel></rss>