<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>Comments on: How to Hack Smart Bluetooth Locks and IoT Devices — Check this Out</title>
	<atom:link href="http://www.epanorama.net/blog/2016/09/16/how-to-hack-smart-bluetooth-locks-and-iot-devices-check-this-out/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.epanorama.net/blog/2016/09/16/how-to-hack-smart-bluetooth-locks-and-iot-devices-check-this-out/</link>
	<description>All about electronics and circuit design</description>
	<lastBuildDate>Fri, 03 Apr 2026 21:03:02 +0000</lastBuildDate>
		<sy:updatePeriod>hourly</sy:updatePeriod>
		<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.9.14</generator>
	<item>
		<title>By: Tomi Engdahl</title>
		<link>https://www.epanorama.net/blog/2016/09/16/how-to-hack-smart-bluetooth-locks-and-iot-devices-check-this-out/comment-page-1/#comment-1663984</link>
		<dc:creator><![CDATA[Tomi Engdahl]]></dc:creator>
		<pubDate>Thu, 12 Dec 2019 07:52:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.epanorama.net/newepa/?p=46983#comment-1663984</guid>
		<description><![CDATA[KeyWe Smart Lock unauthorized access and traffic interception
https://labs.f-secure.com/advisories/keywe-smart-lock-unauthorized-access-traffic-interception
The KeyWe smart lock suffers from multiple design flaws resulting in
an unauthenticated - potentially malicious - actor being able to
intercept and decrypt traffic coming from a legitimate user. This
traffic - as described below - can then be used to execute actions
(such as opening/closing the lock, denial of service, silencing the
lock etc.) on behalf of the owner. An attacker could exploit this
vulnerability by intercepting any legitimate communications to steal
the key and unlock the door at any point remotely. Communication
messages between a legitimate application and the lock are transported
using Bluetooth Low Energy. Before sending they are encrypted using
AES-128-ECB with a random 2B (two-byte) prefix (functioning as a
replacement for an Initialization Vector) thus disallowing a third
party to easily eavesdrop and tamper with commands originating from
the legitimate parties. The key generation process is, however,
affected by a serious flaw. Read also:
https://www.theregister.co.uk/2019/12/11/f_secure_keywe/ and
https://www.tivi.fi/uutiset/tv/d06ba2bd-3e64-4666-a382-ce5def3c7985]]></description>
		<content:encoded><![CDATA[<p>KeyWe Smart Lock unauthorized access and traffic interception<br />
<a href="https://labs.f-secure.com/advisories/keywe-smart-lock-unauthorized-access-traffic-interception" rel="nofollow">https://labs.f-secure.com/advisories/keywe-smart-lock-unauthorized-access-traffic-interception</a><br />
The KeyWe smart lock suffers from multiple design flaws resulting in<br />
an unauthenticated &#8211; potentially malicious &#8211; actor being able to<br />
intercept and decrypt traffic coming from a legitimate user. This<br />
traffic &#8211; as described below &#8211; can then be used to execute actions<br />
(such as opening/closing the lock, denial of service, silencing the<br />
lock etc.) on behalf of the owner. An attacker could exploit this<br />
vulnerability by intercepting any legitimate communications to steal<br />
the key and unlock the door at any point remotely. Communication<br />
messages between a legitimate application and the lock are transported<br />
using Bluetooth Low Energy. Before sending they are encrypted using<br />
AES-128-ECB with a random 2B (two-byte) prefix (functioning as a<br />
replacement for an Initialization Vector) thus disallowing a third<br />
party to easily eavesdrop and tamper with commands originating from<br />
the legitimate parties. The key generation process is, however,<br />
affected by a serious flaw. Read also:<br />
<a href="https://www.theregister.co.uk/2019/12/11/f_secure_keywe/" rel="nofollow">https://www.theregister.co.uk/2019/12/11/f_secure_keywe/</a> and<br />
<a href="https://www.tivi.fi/uutiset/tv/d06ba2bd-3e64-4666-a382-ce5def3c7985" rel="nofollow">https://www.tivi.fi/uutiset/tv/d06ba2bd-3e64-4666-a382-ce5def3c7985</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tomi Engdahl</title>
		<link>https://www.epanorama.net/blog/2016/09/16/how-to-hack-smart-bluetooth-locks-and-iot-devices-check-this-out/comment-page-1/#comment-1573981</link>
		<dc:creator><![CDATA[Tomi Engdahl]]></dc:creator>
		<pubDate>Mon, 11 Dec 2017 19:48:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.epanorama.net/newepa/?p=46983#comment-1573981</guid>
		<description><![CDATA[BlueSteal: Popping GATT Safes
https://www.twosixlabs.com/bluesteal-popping-gatt-safes/

In this blog post, we will detail BlueSteal, or the ability to exploit multiple security failures in the Vaultek VT20i. These vulnerabilities highlight the need to include security audits early in the product manufacturing process. These vulnerabilities include CVE-2017-17435 and CVE-2017-17436.]]></description>
		<content:encoded><![CDATA[<p>BlueSteal: Popping GATT Safes<br />
<a href="https://www.twosixlabs.com/bluesteal-popping-gatt-safes/" rel="nofollow">https://www.twosixlabs.com/bluesteal-popping-gatt-safes/</a></p>
<p>In this blog post, we will detail BlueSteal, or the ability to exploit multiple security failures in the Vaultek VT20i. These vulnerabilities highlight the need to include security audits early in the product manufacturing process. These vulnerabilities include CVE-2017-17435 and CVE-2017-17436.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
