1 <html devsite> 2 <head> 3 <title>Android Security Advisory — 2016-03-18</title> 4 <meta name="project_path" value="/_project.yaml" /> 5 <meta name="book_path" value="/_book.yaml" /> 6 </head> 7 <body> 8 <!-- 9 Copyright 2017 The Android Open Source Project 10 11 Licensed under the Apache License, Version 2.0 (the "License"); 12 you may not use this file except in compliance with the License. 13 You may obtain a copy of the License at 14 15 http://www.apache.org/licenses/LICENSE-2.0 16 17 Unless required by applicable law or agreed to in writing, software 18 distributed under the License is distributed on an "AS IS" BASIS, 19 WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 20 See the License for the specific language governing permissions and 21 limitations under the License. 22 --> 23 24 25 26 <p><em>Published March 18, 2016</em></p> 27 28 <p>Android Security Advisories are supplemental to the Nexus Security Bulletins. 29 Refer to our <a href="index.html">summary page</a> for more information about Security Advisories.</p> 30 31 <h2 id=summary>Summary</h2> 32 33 <p>Google has become aware of a rooting application using an unpatched local 34 elevation of privilege vulnerability in the kernel on some Android devices 35 (<a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1805">CVE-2015-1805</a>). 36 For this application to affect a device, the user must first install it. Google 37 already blocks installation of rooting applications that use this 38 vulnerability — both within Google Play and outside of Google 39 Play — using <a href="https://support.google.com/accounts/answer/2812853"> 40 Verify Apps</a>, and have updated our systems to detect applications that use 41 this specific vulnerability.</p> 42 43 <p>To provide a final layer of defense for this issue, partners were provided 44 with a patch for this issue on March 16, 2016. Nexus updates are being created 45 and will be released within a few days. Source code patches for this issue have 46 been released to the Android Open Source Project (AOSP) repository.</p> 47 48 <h3 id=background>Background</h3> 49 50 <p>This is a known issue in the upstream Linux kernel that was fixed in April 2014 51 but wasnt called out as a security fix and assigned 52 <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1805">CVE-2015-1805</a> 53 until February 2, 2015. On February 19, 2016, C0RE Team notified Google that 54 the issue could be exploited on Android and a patch was developed to be included 55 in an upcoming regularly scheduled monthly update.</p> 56 57 <p>On March 15, 2016 Google received a 58 report from Zimperium that this vulnerability had been abused on a Nexus 5 59 device. Google has confirmed the existence of a publicly available rooting 60 application that abuses this vulnerability on Nexus 5 and Nexus 6 to provide 61 the device user with root privileges.</p> 62 63 <p>This issue is rated as a 64 <a href="/security/overview/updates-resources.html#severity"> 65 Critical severity issue</a> due to the possibility of a local privilege escalation 66 and arbitrary code execution leading to local permanent device compromise.</p> 67 68 <h3 id=scope>Scope</h3> 69 70 71 <p>This advisory applies to all unpatched Android devices on kernel versions 3.4, 72 3.10 and 3.14, including all Nexus devices. Android devices using Linux kernel 73 version 3.18 or higher are not vulnerable.</p> 74 75 <h3 id=mitigations>Mitigations</h3> 76 77 78 <p>The following are mitigations that reduce the likelihood users are impacted 79 by this issue: </p> 80 81 <ul> 82 <li> Verify Apps has been updated to block the installation of applications that 83 we have learned are attempting to exploit this vulnerability both within and outside 84 of Google Play. 85 <li> Google Play does not allow rooting applications, like the one seeking to 86 exploit this issue. 87 <li> Android devices using <a href="https://support.google.com/nexus/answer/4457705"> 88 Linux kernel version 3.18</a> or higher are not vulnerable. 89 </ul> 90 91 <h3 id=acknowledgements>Acknowledgements</h3> 92 93 94 <p>Android would like to thank the <a href="http://c0reteam.org/">C0RE Team</a> and 95 <a href="https://www.zimperium.com/">Zimperium</a> for their contributions to 96 this advisory.</p> 97 98 <h3 id=suggested_actions>Suggested actions</h3> 99 100 101 <p>Android encourages all users to accept updates to their devices when they 102 are available.</p> 103 104 <h3 id=fixes>Fixes</h3> 105 106 107 <p>Google has released a fix in the AOSP repository for multiple kernel versions. 108 Android partners have been notified of these fixes and are encouraged to apply 109 them. If further updates are required, Android will publish them directly to ASOP.</p> 110 111 <table> 112 <tr> 113 <th>Kernel Version</th> 114 <th>Patch</th> 115 </tr> 116 <tr> 117 <td>3.4</td> 118 <td><a href="https://android.googlesource.com/kernel/common/+/f7ebfe91b806501808413c8473a300dff58ddbb5">AOSP patch</a></td> 119 </tr> 120 <tr> 121 <td>3.10</td> 122 <td><a href="https://android.googlesource.com/kernel/common/+/4a5a45669796c5b4617109182e25b321f9f00beb">AOSP patch</a></td> 123 </tr> 124 <tr> 125 <td>3.14</td> 126 <td><a href="https://android.googlesource.com/kernel/common/+/bf010e99c9bc48002f6bfa1ad801a59bf996270f">AOSP patch</a></td> 127 </tr> 128 <tr> 129 <td>3.18+</td> 130 <td>Patched in public Linux kernel</td> 131 </tr> 132 </table> 133 134 135 <h2 id=common_questions_and_answers>Common Questions and Answers</h2> 136 137 138 <p><strong>1. What's the problem?</strong></p> 139 140 <p>An elevation of privilege vulnerability in the kernel could enable a local 141 malicious application to execute arbitrary code in the kernel. This issue is 142 rated as a Critical severity due to the possibility of a local permanent device 143 compromise and the device would possibly need to be repaired by re-flashing the 144 operating system.</p> 145 146 <p><strong>2. How would an attacker seek to exploit this issue?</strong></p> 147 148 <p>Users who install an application that seeks to exploit this issue are at 149 risk. Rooting applications (like the one that is exploiting this issue) are 150 prohibited in Google Play, and Google is blocking the installation of 151 this application outside of Google Play through Verify Apps. An 152 attacker would need to convince a user to manually install an affected 153 application.</p> 154 155 <p><strong>3. Which devices could be affected?</strong></p> 156 157 <p>Google has confirmed that this exploit works on Nexus 5 and 6; however all 158 unpatched versions of Android contain the vulnerability.</p> 159 160 <p><strong>4. Has Google seen evidence of this vulnerability being abused?</strong></p> 161 162 <p>Yes, Google has seen evidence of this vulnerability being abused on a Nexus 5 using a 163 publicly available rooting tool. Google has not observed any exploitation that 164 would be classified as malicious.</p> 165 166 <p><strong>5. How will you be addressing this issue?</strong></p> 167 168 <p><a href="https://static.googleusercontent.com/media/source.android.com/en//security/reports/Android_WhitePaper_Final_02092016.pdf"> 169 Google Play</a> prohibits apps attempting to 170 exploit this issue. Similarly, Verify Apps blocks the installation of apps 171 from outside of Google Play that attempt to exploit this issue. Google Nexus 172 devices will also be patched as soon as an update is ready and weve notified 173 Android partners so they can release similar updates.</p> 174 175 <p><strong>6. How do I know if I have a device that contains a fix for this issue?</strong></p> 176 177 <p>Android has provided two options to our partners to communicate that their 178 devices are not vulnerable to this issue. Android devices with a security patch 179 level of March 18, 2016 are not vulnerable. Android devices with a security 180 patch level of April 2, 2016 and later are not vulnerable to this issue. Refer 181 to <a href="https://support.google.com/nexus/answer/4457705">this article</a> 182 for instructions on how to check the security patch level.</p> 183 184 <h2 id=revisions>Revisions</h2> 185 186 187 <ul> 188 <li> March 18, 2016: Advisory published. 189 </ul> 190 191 192 </body> 193 </html> 194