<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Bluetooth pairing vulnerability</title><link>/nordic/nordic-blog/b/blog/posts/bluetooth-pairing-vulnerability</link><description>The Bluetooth SIG released an errata for the 4.2 and 5.0 versions of Bluetooth specification on July 23rd relating to a potential vulnerability with the pairing procedures.
For Bluetooth low energy; this only impacts the low energy secure connections</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><item><title>RE: Bluetooth pairing vulnerability</title><link>https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/bluetooth-pairing-vulnerability</link><pubDate>Wed, 17 Aug 2022 17:36:12 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b0600ef8-1458-4865-b49d-efd7eda1bb81</guid><dc:creator>danielmeyers</dc:creator><slash:comments>0</slash:comments><description>&lt;p&gt;I don&amp;#39;t know how to explain it but recently our system administrator said that in the office security management data should be sent over the L2CAP security management channel. The security management protocol provides the user interface via the GAP layer. The user sets input and output capabilities and device pairing parameters. How am I supposed to set this up, I don&amp;#39;t understand anything, because I&amp;#39;m a writer and I&amp;#39;m just providing coursework writing help to &lt;a href="https://writemypapers4me.net/coursework-help/"&gt;https://writemypapers4me.net/coursework-help/&lt;/a&gt;. Now I have to learn it, and here I am reading this forum.&lt;/p&gt;&lt;img src="https://devzone.nordicsemi.com/aggbug?PostID=1209&amp;AppID=4&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description></item><item><title>RE: Bluetooth pairing vulnerability</title><link>https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/bluetooth-pairing-vulnerability</link><pubDate>Tue, 04 Dec 2018 13:16:56 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b0600ef8-1458-4865-b49d-efd7eda1bb81</guid><dc:creator>Bragma</dc:creator><slash:comments>1</slash:comments><description>&lt;p&gt;I am using S332 in a new project and I am tied to SDK 14.2. What&amp;#39;s the suggested mitigation in this case? Thanks!&lt;/p&gt;&lt;img src="https://devzone.nordicsemi.com/aggbug?PostID=1209&amp;AppID=4&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description></item><item><title>RE: Bluetooth pairing vulnerability</title><link>https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/bluetooth-pairing-vulnerability</link><pubDate>Sun, 05 Aug 2018 23:22:48 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b0600ef8-1458-4865-b49d-efd7eda1bb81</guid><dc:creator>kordi</dc:creator><slash:comments>2</slash:comments><description>&lt;p&gt;I&amp;#39;m sorry but whether it is possible to do this operation without the involvement of man? it turns out a person should see the numbers on the screen of a device such as Android and on the screen of an embedded device&amp;nbsp;like nrf dk, and if I need to secure a fast connection of a screenless device with android so to speak m2m) How can I do it? Thanks&lt;/p&gt;&lt;img src="https://devzone.nordicsemi.com/aggbug?PostID=1209&amp;AppID=4&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description></item></channel></rss>