<?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: QuadRooter Android security flaw</title>
	<atom:link href="http://www.epanorama.net/blog/2016/08/10/quadrooter-android-security-flaw/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.epanorama.net/blog/2016/08/10/quadrooter-android-security-flaw/</link>
	<description>All about electronics and circuit design</description>
	<lastBuildDate>Wed, 22 Apr 2026 08:40:06 +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/08/10/quadrooter-android-security-flaw/comment-page-1/#comment-1511601</link>
		<dc:creator><![CDATA[Tomi Engdahl]]></dc:creator>
		<pubDate>Wed, 07 Sep 2016 07:19:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.epanorama.net/newepa/?p=45166#comment-1511601</guid>
		<description><![CDATA[Zack Whittaker / ZDNet: 	
Google fixes final two “Quadrooter” Android flaws, which were rated as “critical”, a month after their disclosure

Google fixes final &#039;Quadrooter&#039; flaws with new security patch
The outstanding flaws were fixed a month after the initial disclosure.
http://www.zdnet.com/article/google-fixes-quadrooter-flaws-in-latest-round-of-android-security-patches/

What took Google a month to fix took others just a couple of weeks.

In the latest round of Android security fixes released Tuesday, the company fixed two remaining flaws that were part of the so-called &quot;Quadrooter&quot; set of vulnerabilities announced last month.

Quadrooter was particularly troublesome because the set of four flaws (hence the name &quot;quad&quot;) affected at least 900 million Android devices. These high-risk vulnerabilities would allow a dedicated and well-trained attacker to gain complete access to an affected phone and its data. 

Google, which develops Android, said that most phones had received at least two or even three of the fixes in previous security bulletins. But the rest would remain outstanding for a month, until now, when the company released its regularly-scheduled monthly patches.

According to the bulletin, Google confirmed that the two escalation of privilege bugs -- CVE-2016-2059 (rated &quot;high&quot;) and CVE-2016-5340 (rated &quot;critical&quot;) -- were fixed.

The Android software and phone maker also fixed six more critical bugs in the mobile operating system, including two remote code execution flaw in core Android components.]]></description>
		<content:encoded><![CDATA[<p>Zack Whittaker / ZDNet:<br />
Google fixes final two “Quadrooter” Android flaws, which were rated as “critical”, a month after their disclosure</p>
<p>Google fixes final &#8216;Quadrooter&#8217; flaws with new security patch<br />
The outstanding flaws were fixed a month after the initial disclosure.<br />
<a href="http://www.zdnet.com/article/google-fixes-quadrooter-flaws-in-latest-round-of-android-security-patches/" rel="nofollow">http://www.zdnet.com/article/google-fixes-quadrooter-flaws-in-latest-round-of-android-security-patches/</a></p>
<p>What took Google a month to fix took others just a couple of weeks.</p>
<p>In the latest round of Android security fixes released Tuesday, the company fixed two remaining flaws that were part of the so-called &#8220;Quadrooter&#8221; set of vulnerabilities announced last month.</p>
<p>Quadrooter was particularly troublesome because the set of four flaws (hence the name &#8220;quad&#8221;) affected at least 900 million Android devices. These high-risk vulnerabilities would allow a dedicated and well-trained attacker to gain complete access to an affected phone and its data. </p>
<p>Google, which develops Android, said that most phones had received at least two or even three of the fixes in previous security bulletins. But the rest would remain outstanding for a month, until now, when the company released its regularly-scheduled monthly patches.</p>
<p>According to the bulletin, Google confirmed that the two escalation of privilege bugs &#8212; CVE-2016-2059 (rated &#8220;high&#8221;) and CVE-2016-5340 (rated &#8220;critical&#8221;) &#8212; were fixed.</p>
<p>The Android software and phone maker also fixed six more critical bugs in the mobile operating system, including two remote code execution flaw in core Android components.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tomi Engdahl</title>
		<link>https://www.epanorama.net/blog/2016/08/10/quadrooter-android-security-flaw/comment-page-1/#comment-1504825</link>
		<dc:creator><![CDATA[Tomi Engdahl]]></dc:creator>
		<pubDate>Wed, 10 Aug 2016 16:48:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.epanorama.net/newepa/?p=45166#comment-1504825</guid>
		<description><![CDATA[The problem is there are still so many hands in the pot when it comes to updating Android. Google updates its software, but device makers have to tailor it for their phones — and sometimes they get their software not from Google, but from chipmakers like Qualcomm. And then sometimes mobile carriers want to do their own testing to make sure they aren’t inadvertently introducing other problems onto their network.

All that means the time from when a flaw is identified or disclosed to when it is fixed is longer than it should be, sometimes leaving hundreds of millions of phones vulnerable for weeks or months.

“The problem continues to be that Android security updates are really hard because of [their] fragmented ecosystem,” said Check Point mobile security evangelist Jeff Zacuto told Recode.

Source: http://www.recode.net/2016/8/8/12403088/android-security-mess-quadrooter]]></description>
		<content:encoded><![CDATA[<p>The problem is there are still so many hands in the pot when it comes to updating Android. Google updates its software, but device makers have to tailor it for their phones — and sometimes they get their software not from Google, but from chipmakers like Qualcomm. And then sometimes mobile carriers want to do their own testing to make sure they aren’t inadvertently introducing other problems onto their network.</p>
<p>All that means the time from when a flaw is identified or disclosed to when it is fixed is longer than it should be, sometimes leaving hundreds of millions of phones vulnerable for weeks or months.</p>
<p>“The problem continues to be that Android security updates are really hard because of [their] fragmented ecosystem,” said Check Point mobile security evangelist Jeff Zacuto told Recode.</p>
<p>Source: <a href="http://www.recode.net/2016/8/8/12403088/android-security-mess-quadrooter" rel="nofollow">http://www.recode.net/2016/8/8/12403088/android-security-mess-quadrooter</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
