<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="https://shkspr.mobi/blog/wp-content/themes/edent-wordpress-theme/rss-style.xsl" type="text/xsl"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	    xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	     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/"
	  xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>
<channel>
	<title>Samsung Lock Screen Security Flaw &#8211; Terence Eden’s Blog</title>
	<atom:link href="https://shkspr.mobi/blog/2013/03/samsung-lock-screen-security-flaw/feed/" rel="self" type="application/rss+xml" />
	<link>https://shkspr.mobi/blog</link>
	<description>Regular nonsense about tech and its effects 🙃</description>
	<lastBuildDate>Tue, 04 Mar 2025 09:34:46 +0000</lastBuildDate>
	<language>en-GB</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.0</generator>

<image>
	<url>https://shkspr.mobi/blog/wp-content/uploads/2023/07/cropped-avatar-32x32.jpeg</url>
	<title>Samsung Lock Screen Security Flaw &#8211; Terence Eden’s Blog</title>
	<link>https://shkspr.mobi/blog</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title><![CDATA[Samsung Lock Screen Security Flaw]]></title>
		<link>https://shkspr.mobi/blog/2013/03/samsung-lock-screen-security-flaw/</link>
					<comments>https://shkspr.mobi/blog/2013/03/samsung-lock-screen-security-flaw/#comments</comments>
				<dc:creator><![CDATA[@edent]]></dc:creator>
		<pubDate>Mon, 04 Mar 2013 12:00:25 +0000</pubDate>
				<category><![CDATA[mobile]]></category>
		<category><![CDATA[android]]></category>
		<category><![CDATA[bug]]></category>
		<category><![CDATA[samsung]]></category>
		<category><![CDATA[security]]></category>
		<guid isPermaLink="false">http://shkspr.mobi/blog/?p=7690</guid>

					<description><![CDATA[Here&#039;s a rather nifty security flaw I discovered on Samsung&#039;s Android 4.1.2.  It allows you - in limited circumstances - to run apps and dial numbers even when the device is locked.  Video:    This attack works against Pattern Lock, PIN, Password, and Face Unlock.  There is no way to secure your phone against your home screen being accessed.  Notes  HOWTO       Lock the device with a &#34;secure&#34;…]]></description>
										<content:encoded><![CDATA[<p>Here's a rather nifty security flaw I discovered on Samsung's Android 4.1.2.  It allows you - in limited circumstances - to run apps and dial numbers <strong>even when the device is locked</strong>.</p>

<p><a href="https://www.youtube.com/watch?v=6i-0t63wOII">Video</a>:</p>

<iframe title="Samsung Security Flaw - Galaxy Note II" width="620" height="349" src="https://www.youtube.com/embed/6i-0t63wOII?feature=oembed" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen=""></iframe>

<p>This attack works against Pattern Lock, PIN, Password, and Face Unlock.  There is <strong>no way to secure your phone</strong> against your home screen being accessed.</p>

<h2 id="notes"><a href="https://shkspr.mobi/blog/2013/03/samsung-lock-screen-security-flaw/#notes">Notes</a></h2>

<h3 id="howto"><a href="https://shkspr.mobi/blog/2013/03/samsung-lock-screen-security-flaw/#howto">HOWTO</a></h3>

<ol>
    <li>Lock the device with a "secure" pattern, PIN, or password.</li>
    <li>Activate the screen.</li>
    <li>Press "Emergency Call".</li>
    <li>Press the "ICE" button on the bottom left.</li>
    <li>Hold down the physical home key for a few seconds and then release.</li>
    <li>The phone's home screen will be displayed - briefly.</li>
    <li>While the home screen is displayed, click on an app or a widget.</li>
    <li>The app or widget will launch.</li>
    <li>If the widget is "direct dial" the phone will start ringing.</li>
</ol>

<h3 id="limited-scope"><a href="https://shkspr.mobi/blog/2013/03/samsung-lock-screen-security-flaw/#limited-scope">Limited Scope</a></h3>

<p>It's true, this attack is of limited value.  That's one of the reasons why I've disclosed it.</p>

<p>Making a call relies on the phone having a direct dial widget on the home screen.</p>

<p>Running the apps is also of limited use - they go into the background immediately.  If the app performs an action on launch (like recording from the microphone, switching on the flash, playing music, interacting with a server) that action will occur.</p>

<p>There is also the privacy concern that an attacker could see what apps you have installed on your homescreen - or see your calendar / emails if you use a widget which displays them.</p>

<p>Rapidly tapping the home button will - depending on your launcher - allow you to see what is on every home screen.  Using an external video camera you should be able to clearly see all the user's calender &amp; email widgets if they have enabled them.</p>

<h3 id="target"><a href="https://shkspr.mobi/blog/2013/03/samsung-lock-screen-security-flaw/#target">Target</a></h3>

<p>I've only tried this on one class of handset.  Galaxy Note II N7100.  Running 4.1.2 - the latest UK variant.
The two devices both ran the stock launcher and lock screen.
One device was rooted - the other was factory fresh.</p>

<p>I have <strong>not tested on any other devices</strong>.</p>

<h3 id="defending-yourself"><a href="https://shkspr.mobi/blog/2013/03/samsung-lock-screen-security-flaw/#defending-yourself">Defending Yourself</a></h3>

<p>This attack works against Pattern Lock, PIN, Password, and Face Unlock.  There is <strong>no way to secure your phone</strong> against your home screen being accessed.</p>

<p>Your options are:</p>

<ul>
    <li>Do not use direct dial widgets on your homescreen.</li>
    <li>Remove any calendar or email widgets which may show sensitive information from your homescreens.</li>
    <li>Ensure that any apps which you do have on your homescreens do not automatically cost you money or act maliciously when launched.</li>
    <li>Use an app locker to prompt for a password when apps are launched.</li>
    <li>Changing to a different launcher <em>will not</em> protect you.</li>
    <li>Using a 3rd party lock screen <em>will not</em> protect you if it accesses the emergency dialer.</li>
</ul>

<h3 id="responsible-disclosure"><a href="https://shkspr.mobi/blog/2013/03/samsung-lock-screen-security-flaw/#responsible-disclosure">Responsible Disclosure</a></h3>

<p>Samsung don't have a dedicated responsible disclosure team.  Nor do they offer a bug bounty.
The nearest I've found is this unlisted email address.</p>

<blockquote class="social-embed" id="social-embed-245983805259784193" lang="en" itemscope="" itemtype="https://schema.org/SocialMediaPosting"><header class="social-embed-header" itemprop="author" itemscope="" itemtype="https://schema.org/Person"><a href="https://twitter.com/iamnion" class="social-embed-user" itemprop="url"><img class="social-embed-avatar social-embed-avatar-circle" src="data:image/webp;base64,UklGRmwCAABXRUJQVlA4IGACAAAQDACdASowADAAPrVOoEsnJCMhqrVdUOAWiWMArz/DvWhonqUIaMhbi4zKSCyXd88RCfeIGIcrviHMA939ga2O5XwVT49LRAOXwB7PsJrrqATq5IsKdfLM04H9/IxdlZz5fM3bq9bzegAA/vPUXharnbV7mEv3E/tx6+0NAumtQ1gAji81d9cntbxJ+yTUcFJnm0nU7GU8XpoYNzfxMWTJEqF4oxvpSrtb2YWqNezzqf2LaHdW14GX9OG9g56j1vFFFJk1IPi/HngzXNuHZvzQwgNlKwDlCD7samRKjT8zz2vrNlieM+1gg3AQvNR90hu3i8SnaMRFkZs7bkBrzn90wovFwuJ68S+GokABlxYeJxBTZhVPJRlZN66RDwGh3p7y6MQhSya1HG9fiNzxhb3kATEV77iuUosw1KD8Th48bXfqxCzdG/Z/6K8qPYPceAzKesbtv/h+0P2HtlCT7FhqlCRCH9qE0YQTrbAGFIgC0PdUYbnkJfUJJbpHfWt7tT5HL9gOF+Wd8YnuR2xlQoLuZL+slgc5lVeYUUTgSuCFeINXqLUh9d3Mnu0MYc9RPet6+GeAuHdjZ+uRaf+oYSR6YD/G7J8at1VMrRpCpdYynil7Fd+7YPRuFwdiiZ216Jed7B6Vau/sss2iihcAuZe/oz48mN8DBIL0dSmkQp9pD5J4jOtKddiY4CzvnZtMbylijpBDSkJQSnE5xiT5Hr+3TDYU+oXTkUrscf0haMy3qe4rwZxTtwPfJeDKpuMFcB33qBMVeXyc2zbLtM3iUNMO7FgDXAg/RssXiqiOvuaoAA==" alt="" itemprop="image"><div class="social-embed-user-names"><p class="social-embed-user-names-name" itemprop="name">Nico Golde</p>@iamnion</div></a><img class="social-embed-logo" alt="Twitter" src="data:image/svg+xml,%3Csvg%20xmlns%3D%22http%3A%2F%2Fwww.w3.org%2F2000%2Fsvg%22%0Aaria-label%3D%22Twitter%22%20role%3D%22img%22%0AviewBox%3D%220%200%20512%20512%22%3E%3Cpath%0Ad%3D%22m0%200H512V512H0%22%0Afill%3D%22%23fff%22%2F%3E%3Cpath%20fill%3D%22%231d9bf0%22%20d%3D%22m458%20140q-23%2010-45%2012%2025-15%2034-43-24%2014-50%2019a79%2079%200%2000-135%2072q-101-7-163-83a80%2080%200%200024%20106q-17%200-36-10s-3%2062%2064%2079q-19%205-36%201s15%2053%2074%2055q-50%2040-117%2033a224%20224%200%2000346-200q23-16%2040-41%22%2F%3E%3C%2Fsvg%3E"></header><section class="social-embed-text" itemprop="articleBody">i don't find this anywhere publicly, but actually <a href="https://twitter.com/hashtag/samsung">#samsung</a>'s mobile devision has a <a href="https://twitter.com/hashtag/security">#security</a> point of contact by now: m.security@samsung.com</section><hr class="social-embed-hr"><footer class="social-embed-footer"><a href="https://twitter.com/iamnion/status/245983805259784193"><span aria-label="3 likes" class="social-embed-meta">❤️ 3</span><span aria-label="0 replies" class="social-embed-meta">💬 0</span><span aria-label="0 reposts" class="social-embed-meta">🔁 0</span><time datetime="2012-09-12T20:34:43.000Z" itemprop="datePublished">20:34 - Wed 12 September 2012</time></a></footer></blockquote>

<p>I spoke to several external security people, and Samsung relationship managers within the industry, who have raised the issue directly with Samsung.  I also tried emailing Samsung directly. I know that people within Samsung have been made aware of this bug.</p>

<p>Despite that, five days later, and Samsung's security team have <strong>not</strong> made any contact with me to discuss this bug or its disclosure.<br>
I wonder if this is typical of Samsung's attitude towards their customers and the industry in general? Do they believe that if they ignore problems, they will disappear?</p>

<h3 id="conclusion"><a href="https://shkspr.mobi/blog/2013/03/samsung-lock-screen-security-flaw/#conclusion">Conclusion</a></h3>

<p>Samsung have a <a href="http://www.androidcentral.com/samsung-exynos-kernel-exploit-what-you-need-know">really</a> <a href="http://www.smh.com.au/it-pro/security-it/security-risk-for-millions-of-android-phone-users-20120926-26khk.html">poor</a> <a href="http://www.talkandroid.com/125226-casual-user-exposes-major-security-flaw-on-galaxy-s-iii-courtesy-of-samsung-kies-desktop-software/">record</a> on <a href="https://web.archive.org/web/20130526193725/http://www.androidcentral.com/major-security-flaw-found-atts-upcoming-samsung-galaxy-s-ii-device">Android security</a>.  Avoid purchasing their phones at all costs.</p>
<img src="https://shkspr.mobi/blog/wp-content/themes/edent-wordpress-theme/info/okgo.php?ID=7690&HTTP_REFERER=RSS" alt="" width="1" height="1" loading="eager">]]></content:encoded>
					
					<wfw:commentRss>https://shkspr.mobi/blog/2013/03/samsung-lock-screen-security-flaw/feed/</wfw:commentRss>
			<slash:comments>31</slash:comments>
		
		
			</item>
	</channel>
</rss>
