en/security/bulletin/2018-02-01.html - platform/docs/source.android.com - Git at Google

 <html devsite>
   <head>
     <title>Android Security Bulletin—February 2018</title>
     <meta name="project_path" value="/_project.yaml" />
     <meta name="book_path" value="/_book.yaml" />
   </head>
   <body>
   <!--
       Copyright 2018 The Android Open Source Project

       Licensed under the Apache License, Version 2.0 (the "License");
       you may not use this file except in compliance with the License.
       You may obtain a copy of the License at

           //www.apache.org/licenses/LICENSE-2.0

       Unless required by applicable law or agreed to in writing, software
       distributed under the License is distributed on an "AS IS" BASIS,
       WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
       See the License for the specific language governing permissions and
       limitations under the License.
   -->
   <p><em>Published February 5, 2018 | Updated April 2, 2018</em></p>


 <p>
 The Android Security Bulletin contains details of security vulnerabilities
 affecting Android devices. Security patch levels of 2018-02-05 or later address
 all of these issues. To learn how to check a device's security patch level, see
 <a href="https://support.google.com/pixelphone/answer/4457705">Check and update
 your Android version</a>.
 </p>
 <p>
 Android partners are notified of all issues at least a month before publication.
 Source code patches for these issues have been released to the Android Open
 Source Project (AOSP) repository and linked from this bulletin. This bulletin
 also includes links to patches outside of AOSP.</p>
 <p>
 The most severe of these issues is a critical security vulnerability in Media
 framework that could enable a remote attacker using a specially crafted file to
 execute arbitrary code within the context of a privileged process. The <a
 href="/security/overview/updates-resources.html#severity">severity
 assessment</a> is based on the effect that exploiting the vulnerability would
 possibly have on an affected device, assuming the platform and service
 mitigations are turned off for development purposes or if successfully bypassed.
 </p>
 <p>
 We have had no reports of active customer exploitation or abuse of these newly
 reported issues. Refer to the <a href="#mitigations">Android
 and Google Play Protect mitigations</a> section for details on the <a
 href="/security/enhancements/index.html">Android
 security platform protections</a> and Google Play Protect, which improve the
 security of the Android platform.
 </p>
 <p class="note">
 <strong>Note:</strong> Information on the latest over-the-air update (OTA) and
 firmware images for Google devices is available in the
 <a href="/security/bulletin/pixel/2018-02-01">February 2018 Pixel&hairsp;/&hairsp;Nexus
 Security Bulletin</a>.
 </p>
 <h2 id="mitigations">Android and Google service mitigations</h2>
 <p>
 This is a summary of the mitigations provided by the <a
 href="/security/enhancements/index.html">Android
 security platform</a> and service protections such as <a
 href="https://www.android.com/play-protect">Google Play Protect</a>. These
 capabilities reduce the likelihood that security vulnerabilities could be
 successfully exploited on Android.
 </p>
 <ul>
 <li>Exploitation for many issues on Android is made more difficult by
 enhancements in newer versions of the Android platform. We encourage all users
 	to update to the latest version of Android where possible.</li>
 <li>The Android security team actively monitors for abuse through <a
 href="https://www.android.com/play-protect">Google Play Protect</a> and warns
 users about <a
 href="/security/reports/Google_Android_Security_PHA_classifications.pdf">Potentially
 Harmful Applications</a>. Google Play Protect is enabled by default on devices
 with <a href="http://www.android.com/gms">Google Mobile Services</a>, and is
 especially important for users who install apps from outside of Google
 Play.</li>
 </ul>
 <h2 id="2018-02-01-details">2018-02-01 security patch level—Vulnerability details</h2>
 <p>
 In the sections below, we provide details for each of the security
 vulnerabilities that apply to the 2018-02-01 patch level. Vulnerabilities are
 grouped under the component that they affect. There is a description of the
 issue and a table with the CVE, associated references, <a href="#type">type
 of vulnerability</a>,
 <a href="/security/overview/updates-resources.html#severity">severity</a>,
 and updated AOSP versions (where applicable). When available, we link the public
 change that addressed the issue to the bug ID, like the AOSP change list. When
 multiple changes relate to a single bug, additional references are linked to
 numbers following the bug ID.
 </p>

 <h3 id="media-framework">Media framework</h3>
 <p>The most severe vulnerability in this section could enable a remote attacker
 using a specially crafted file to execute arbitrary code within the context of
 a privileged process.</p>

 <table>
   <col width="17%">
   <col width="19%">
   <col width="9%">
   <col width="14%">
   <col width="39%">
   <tr>
     <th>CVE</th>
     <th>References</th>
     <th>Type</th>
     <th>Severity</th>
     <th>Updated AOSP versions</th>
   </tr>
   <tr>
     <td>CVE-2017-13228</td>
     <td><a href="https://android.googlesource.com/platform/external/libavc/+/04b68a0a51729b655bcd0f5ae5ec20645eeda946">
     A-69478425</a></td>
     <td>RCE</td>
     <td>Critical</td>
     <td>6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td>
   </tr>
   <tr>
     <td>CVE-2017-13231</td>
    <td><a href="https://android.googlesource.com/platform/hardware/interfaces/+/16a3cd0b0729bd53265897cf8c790013156e92ce">
    A-67962232</a>
    </td>
     <td>EoP</td>
     <td>High</td>
     <td>8.0, 8.1</td>
   </tr>
   <tr>
     <td>CVE-2017-13232</td>
    <td><a href="https://android.googlesource.com/platform/frameworks/av/+/6a5d1fc7cbccd85054e56542a633149622effa67">
    A-68953950</a>
    </td>
     <td>ID</td>
     <td>High</td>
     <td>5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td>
   </tr>
   <tr>
     <td rowspan="2">CVE-2017-13230</td>
     <td rowspan="2"><a href="https://android.googlesource.com/platform/external/libhevc/+/68e532d83a1b98f6b5e297d71b547ed93a68dfe3">
     A-65483665</a></td>
     <td>DoS</td>
     <td>High</td>
     <td>7.0, 7.1.1, 7.1.2, 8.0, 8.1</td>
   </tr>
   <tr>
     <td>RCE</td>
     <td>Critical</td>
     <td>5.1.1, 6.0, 6.0.1</td>
   </tr>
   <tr>
     <td>CVE-2017-13233</td>
    <td><a href="https://android.googlesource.com/platform/external/libhevc/+/a22314db4e0cfe11ef3e50dac6a13d52f7a595b3">
    A-62851602</a>
    </td>
     <td>DoS</td>
     <td>High</td>
     <td>5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td>
   </tr>
   <tr>
     <td>CVE-2017-13234</td>
    <td><a href="https://android.googlesource.com/platform/external/sonivox/+/33f45caed3b60bf81790e9b76cf82c8e8d6ed902">
    A-68159767</a>
    </td>
     <td>DoS</td>
     <td>High</td>
     <td>5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td>
   </tr>
 </table>


 <h3 id="system">System</h3>
 <p>The most severe vulnerability in this section could enable a local malicious
 application to execute commands normally limited to privileged processes.</p>

 <table>
   <col width="17%">
   <col width="19%">
   <col width="9%">
   <col width="14%">
   <col width="39%">
   <tr>
     <th>CVE</th>
     <th>References</th>
     <th>Type</th>
     <th>Severity</th>
     <th>Updated AOSP versions</th>
   </tr>
   <tr>
     <td>CVE-2017-13236</td>
    <td><a href="https://android.googlesource.com/platform/system/security/+/80592e62a6ae095041e95b811ad7066dd44d37f6">
    A-68217699</a>
   [<a href="https://android.googlesource.com/platform/system/security/+/b49160023ee8f73ce0ac97f9f4604a34ebdecf76">2</a>]
    </td>
     <td>EoP</td>
     <td>Moderate</td>
     <td>8.0, 8.1</td>
   </tr>
 </table>

 <h2 id="2018-02-05-details">2018-02-05 security patch level—Vulnerability details</h2>
 <p>
 In the sections below, we provide details for each of the security
 vulnerabilities that apply to the 2018-02-05 patch level. Vulnerabilities are
 grouped under the component that they affect and include details such as the
 CVE, associated references, <a href="#type">type of vulnerability</a>,
 <a href="/security/overview/updates-resources.html#severity">severity</a>,
 component (where applicable), and updated AOSP versions (where applicable). When
 available, we link the public change that addressed the issue to the bug ID,
 like the AOSP change list. When multiple changes relate to a single bug,
 additional references are linked to numbers following the bug ID.
 </p>

 <h3 id="htc-components">HTC components</h3>
 <p>The most severe vulnerability in this section could enable a local malicious
 application to obtain unauthorized access to data.</p>

 <table>
   <col width="17%">
   <col width="19%">
   <col width="9%">
   <col width="14%">
   <col width="39%">
   <tr>
     <th>CVE</th>
     <th>References</th>
     <th>Type</th>
     <th>Severity</th>
     <th>Component</th>
   </tr>
   <tr>
     <td>CVE-2017-13238</td>
     <td>A-64610940<a href="#asterisk">*</a></td>
     <td>ID</td>
     <td>High</td>
     <td>Bootloader</td>
   </tr>
   <tr>
     <td>CVE-2017-13247</td>
     <td>A-71486645<a href="#asterisk">*</a></td>
     <td>EoP</td>
     <td>Moderate</td>
     <td>Bootloader</td>
   </tr>
 </table>


 <h3 id="kernel-components">Kernel components</h3>
 <p>The most severe vulnerability in this section could enable a local malicious
 application to execute arbitrary code within the context of a privileged
 process.</p>

 <table>
   <col width="17%">
   <col width="19%">
   <col width="9%">
   <col width="14%">
   <col width="39%">
   <tr>
     <th>CVE</th>
     <th>References</th>
     <th>Type</th>
     <th>Severity</th>
     <th>Component</th>
   </tr>
   <tr>
     <td>CVE-2017-15265</td>
     <td>A-67900971<br />
         <a
 href="https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/sound/?h=v4.4.103&id=23709ae9b61429502fcd4686e7a97333f3b3544a">
 Upstream kernel</a></td>
     <td>EoP</td>
     <td>High</td>
     <td>ALSA</td>
   </tr>
   <tr>
     <td>CVE-2015-9016</td>
     <td>A-63083046<br />
         <a
 href="https://github.com/torvalds/linux/commit/0048b4837affd153897ed1222283492070027aa9">
 Upstream kernel</a></td>
     <td>EoP</td>
     <td>High</td>
     <td>Multi-queue block IO</td>
   </tr>
   <tr>
     <td>CVE-2017-13273</td>
     <td>A-65853158<a href="#asterisk">*</a></td>
     <td>EoP</td>
     <td>High</td>
     <td>Kernel</td>
   </tr>
 </table>


 <h3 id="nvidia-components">NVIDIA components</h3>
 <p>The most severe vulnerability in this section could enable a local malicious
 application to execute arbitrary code within the context of a privileged
 process.</p>

 <table>
   <col width="17%">
   <col width="19%">
   <col width="9%">
   <col width="14%">
   <col width="39%">
   <tr>
     <th>CVE</th>
     <th>References</th>
     <th>Type</th>
     <th>Severity</th>
     <th>Component</th>
   </tr>
   <tr>
     <td>CVE-2017-6279</td>
     <td>A-65023166<a href="#asterisk">*</a><br />
         N-CVE-2017-6279</td>
     <td>EoP</td>
     <td>High</td>
     <td>Media framework</td>
   </tr>
   <tr>
     <td>CVE-2017-6258</td>
     <td>A-38027496<a href="#asterisk">*</a><br />
         N-CVE-2017-6258</td>
     <td>EoP</td>
     <td>High</td>
     <td>Media framework</td>
   </tr>
 </table>


 <h3 id="qualcomm-components">Qualcomm components</h3>
 <p>The most severe vulnerability in this section could enable a remote attacker
 using a specially crafted file to execute arbitrary code within the context of
 a privileged process.</p>

 <table>
   <col width="17%">
   <col width="19%">
   <col width="9%">
   <col width="14%">
   <col width="39%">
   <tr>
     <th>CVE</th>
     <th>References</th>
     <th>Type</th>
     <th>Severity</th>
     <th>Component</th>
   </tr>
   <tr>
     <td>CVE-2017-15860</td>
     <td>A-68992416<br />
         <a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-2.0/commit/?id=71331327ac389bff7d5af2707c4325e5b7949013">
 QC-CR#2082544</a>
    [<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-2.0/commit/?id=a6afff2717791ceb281354833d4489123ae62605">2</a>]</td>
     <td>RCE</td>
     <td>Critical</td>
     <td>WLan</td>
   </tr>
   <tr>
     <td>CVE-2017-11041</td>
     <td>A-35269676<a href="#asterisk">*</a><br />
         QC-CR#2053101</td>
     <td>EoP</td>
     <td>High</td>
     <td>Media framework</td>
   </tr>
   <tr>
     <td>CVE-2017-17767</td>
     <td>A-64750179<a href="#asterisk">*</a><br />
         QC-CR#2115779</td>
     <td>EoP</td>
     <td>High</td>
     <td>Media framework</td>
   </tr>
   <tr>
     <td>CVE-2017-17765</td>
     <td>A-68992445<br />
         <a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=66e561b0c7fff54e8cacd87d2b7d9bb3eef4f13b">
 QC-CR#2115112</a></td>
     <td>EoP</td>
     <td>High</td>
     <td>WLan</td>
   </tr>
   <tr>
     <td>CVE-2017-15862</td>
     <td>A-68992439<br />
         <a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=41ee23cd0972ef2ed47dd76eb7cd44a0268e4f9f">
 QC-CR#2114426</a></td>
     <td>EoP</td>
     <td>High</td>
     <td>WLan</td>
   </tr>
   <tr>
     <td>CVE-2017-14884</td>
     <td>A-68992429<br />
         <a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-2.0/commit/?id=0ce15ef4075719a82858b7324690be7011cab832">
 QC-CR#2113052</a></td>
     <td>EoP</td>
     <td>High</td>
     <td>WLan</td>
   </tr>
   <tr>
     <td>CVE-2017-15829</td>
     <td>A-68992397<br />
         <a href="https://source.codeaurora.org/quic/la/kernel/msm-4.4/commit/?id=c1b60e554e158bfcf6932ed2c543c309236e0f79">
 QC-CR#2097917</a></td>
     <td>EoP</td>
     <td>High</td>
     <td>Graphics_Linux</td>
   </tr>
   <tr>
     <td>CVE-2017-15820</td>
     <td>A-68992396<br />
         <a href="https://source.codeaurora.org/quic/la/kernel/msm-4.4/commit/?id=7599c5b7d87248b4772d6c4b70ccb922704c8095">
 QC-CR#2093377</a></td>
     <td>EoP</td>
     <td>High</td>
     <td>Graphics_Linux</td>
   </tr>
   <tr>
     <td>CVE-2017-17764</td>
     <td>A-68992443<br />
         <a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=f451565c052a0322565225515f46be677c0d1b18">
 QC-CR#2114789</a></td>
     <td>EoP</td>
     <td>High</td>
     <td>WLan</td>
   </tr>
   <tr>
     <td>CVE-2017-15861</td>
     <td>A-68992434<br />
         <a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=13e3a516935a0dd90a7bc39e51c30c1592c548b7">
 QC-CR#2114187</a></td>
     <td>EoP</td>
     <td>High</td>
     <td>WLan</td>
   </tr>
 </table>


 <h3 id="qualcomm-closed-source-components">Qualcomm closed-source
 components</h3>
 <p>These vulnerabilities affect Qualcomm components and are described in
 further detail in the appropriate Qualcomm AMSS security bulletin or security
 alert. The severity assessment of these issues is provided directly by
 Qualcomm.</p>

 <table>
   <col width="17%">
   <col width="19%">
   <col width="9%">
   <col width="14%">
   <col width="39%">
   <tr>
     <th>CVE</th>
     <th>References</th>
     <th>Type</th>
     <th>Severity</th>
     <th>Component</th>
   </tr>
   <tr>
     <td>CVE-2017-14910</td>
     <td>A-62212114<a href="#asterisk">*</a></td>
     <td>N/A</td>
     <td>High</td>
     <td>Closed-source component</td>
   </tr>
 </table>

 <h2 id="common-questions-and-answers">Common questions and answers</h2>
 <p>
 This section answers common questions that may occur after reading this
 bulletin.</p>
 <p><strong>1. How do I determine if my device is updated to address these issues?
 </strong></p>
 <p>To learn how to check a device's security patch level, see
 <a href="https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices">Check
 and update your Android version</a>.</p>
 <ul>
 <li>Security patch levels of 2018-02-01 or later address all issues associated
 	with the 2018-02-01 security patch level.</li>
 <li>Security patch levels of 2018-02-05 or later address all issues associated
 	with the 2018-02-05 security patch level and all previous patch levels.</li>
 </ul>
 <p>
 Device manufacturers that include these updates should set the patch string
 level to:
 </p>
 <ul>
 	<li>[ro.build.version.security_patch]:[2018-02-01]</li>
 	<li>[ro.build.version.security_patch]:[2018-02-05]</li>
 </ul>
 <p>
 <strong>2. Why does this bulletin have two security patch levels?</strong>
 </p>
 <p>
 This bulletin has two security patch levels so that Android partners have the
 flexibility to fix a subset of vulnerabilities that are similar across all
 Android devices more quickly. Android partners are encouraged to fix all issues
 in this bulletin and use the latest security patch level.
 </p>
 <ul>
 <li>Devices that use the 2018-02-01 security patch level must include all issues
 associated with that security patch level, as well as fixes for all issues
 	reported in previous security bulletins.</li>
 <li>Devices that use the security patch level of 2018-02-05 or newer must
 include all applicable patches in this (and previous) security
 	bulletins.</li>
 </ul>
 <p>
 Partners are encouraged to bundle the fixes for all issues they are addressing
 in a single update.
 </p>
 <p id="type">
 <strong>3. What do the entries in the <em>Type</em> column mean?</strong>
 </p>
 <p>
 Entries in the <em>Type</em> column of the vulnerability details table reference
 the classification of the security vulnerability.
 </p>
 <table>
   <col width="25%">
   <col width="75%">
   <tr>
    <th>Abbreviation</th>
    <th>Definition</th>
   </tr>
   <tr>
    <td>RCE</td>
    <td>Remote code execution</td>
   </tr>
   <tr>
    <td>EoP</td>
    <td>Elevation of privilege</td>
   </tr>
   <tr>
    <td>ID</td>
    <td>Information disclosure</td>
   </tr>
   <tr>
    <td>DoS</td>
    <td>Denial of service</td>
   </tr>
   <tr>
    <td>N/A</td>
    <td>Classification not available</td>
   </tr>
 </table>
 <p>
 <strong>4. What do the entries in the <em>References</em> column mean?</strong>
 </p>
 <p>
 Entries under the <em>References</em> column of the vulnerability details table
 may contain a prefix identifying the organization to which the reference value
 belongs.
 </p>
 <table>
   <col width="25%">
   <col width="75%">
   <tr>
    <th>Prefix</th>
    <th>Reference</th>
   </tr>
   <tr>
    <td>A-</td>
    <td>Android bug ID</td>
   </tr>
   <tr>
    <td>QC-</td>
    <td>Qualcomm reference number</td>
   </tr>
   <tr>
    <td>M-</td>
    <td>MediaTek reference number</td>
   </tr>
   <tr>
    <td>N-</td>
    <td>NVIDIA reference number</td>
   </tr>
   <tr>
    <td>B-</td>
    <td>Broadcom reference number</td>
   </tr>
 </table>
 <p id="asterisk">
 <strong>5. What does a * next to the Android bug ID in the <em>References</em>
 column mean?</strong>
 </p>
 <p>
 Issues that are not publicly available have a * next to the Android bug ID in
 the <em>References</em> column. The update for that issue is generally contained
 in the latest binary drivers for Nexus devices available from the <a
 href="https://developers.google.com/android/nexus/drivers">Google Developer
 site</a>.
 </p>
 <p>
 <strong>6. Why are security vulnerabilities split between this bulletin and
 device/partner security bulletins, such as the Pixel / Nexus bulletin?</strong>
 </p>
 <p>
 Security vulnerabilities that are documented in this security bulletin are
 required in order to declare the latest security patch level on Android devices.
 Additional security vulnerabilities that are documented in the device/partner
 security bulletins are not required for declaring a security patch level.
 Android device and chipset manufacturers are encouraged to document the presence
 of other fixes on their devices through their own security websites, such as the
 <a href="https://security.samsungmobile.com/securityUpdate.smsb">Samsung</a>, <a
 href="https://lgsecurity.lge.com/security_updates.html">LGE</a>, or <a
 href="/security/bulletin/pixel/">Pixel&hairsp;/&hairsp;Nexus</a>
 security bulletins.
 </p>
 <h2 id="versions">Versions</h2>
 <table>
   <col width="25%">
   <col width="25%">
   <col width="50%">
   <tr>
    <th>Version</th>
 	  <th>Date</th>
    <th>Notes</th>
   </tr>
   <tr>
    <td>1.0</td>
    <td>February 5, 2018</td>
    <td>Bulletin published.</td>
   </tr>
   <tr>
    <td>1.1</td>
    <td>February 7, 2018</td>
    <td>Bulletin revise to include AOSP links.</td>
   </tr>
   <tr>
    <td>1.2</td>
    <td>February 14, 2018</td>
    <td>Corrected CVE numbers for CVE-2017-13273, CVE-2017-15860, CVE-2017-15861 and
      CVE-2017-15862.</td>
   </tr>
     <tr>
    <td>1.3</td>
    <td>April 2, 2018</td>
    <td>Moved CVE-2017-15817 from the February Android Bulletin to the February Pixel Bulletin.</td>
   </tr>
 </table>
 	</body></html>
	<html devsite>
	<head>
	<title>Android Security Bulletin—February 2018</title>
	<meta name="project_path" value="/_project.yaml" />
	<meta name="book_path" value="/_book.yaml" />
	</head>
	<body>
	<!--
	Copyright 2018 The Android Open Source Project

	Licensed under the Apache License, Version 2.0 (the "License");
	you may not use this file except in compliance with the License.
	You may obtain a copy of the License at

	//www.apache.org/licenses/LICENSE-2.0

	Unless required by applicable law or agreed to in writing, software
	distributed under the License is distributed on an "AS IS" BASIS,
	WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
	See the License for the specific language governing permissions and
	limitations under the License.
	-->
	<p><em>Published February 5, 2018 \| Updated April 2, 2018</em></p>


	<p>
	The Android Security Bulletin contains details of security vulnerabilities
	affecting Android devices. Security patch levels of 2018-02-05 or later address
	all of these issues. To learn how to check a device's security patch level, see
	<a href="https://support.google.com/pixelphone/answer/4457705">Check and update
	your Android version</a>.
	</p>
	<p>
	Android partners are notified of all issues at least a month before publication.
	Source code patches for these issues have been released to the Android Open
	Source Project (AOSP) repository and linked from this bulletin. This bulletin
	also includes links to patches outside of AOSP.</p>
	<p>
	The most severe of these issues is a critical security vulnerability in Media
	framework that could enable a remote attacker using a specially crafted file to
	execute arbitrary code within the context of a privileged process. The <a
	href="/security/overview/updates-resources.html#severity">severity
	assessment</a> is based on the effect that exploiting the vulnerability would
	possibly have on an affected device, assuming the platform and service
	mitigations are turned off for development purposes or if successfully bypassed.
	</p>
	<p>
	We have had no reports of active customer exploitation or abuse of these newly
	reported issues. Refer to the <a href="#mitigations">Android
	and Google Play Protect mitigations</a> section for details on the <a
	href="/security/enhancements/index.html">Android
	security platform protections</a> and Google Play Protect, which improve the
	security of the Android platform.
	</p>
	<p class="note">
	<strong>Note:</strong> Information on the latest over-the-air update (OTA) and
	firmware images for Google devices is available in the
	<a href="/security/bulletin/pixel/2018-02-01">February 2018 Pixel&hairsp;/&hairsp;Nexus
	Security Bulletin</a>.
	</p>
	<h2 id="mitigations">Android and Google service mitigations</h2>
	<p>
	This is a summary of the mitigations provided by the <a
	href="/security/enhancements/index.html">Android
	security platform</a> and service protections such as <a
	href="https://www.android.com/play-protect">Google Play Protect</a>. These
	capabilities reduce the likelihood that security vulnerabilities could be
	successfully exploited on Android.
	</p>
	<ul>
	<li>Exploitation for many issues on Android is made more difficult by
	enhancements in newer versions of the Android platform. We encourage all users
	to update to the latest version of Android where possible.</li>
	<li>The Android security team actively monitors for abuse through <a
	href="https://www.android.com/play-protect">Google Play Protect</a> and warns
	users about <a
	href="/security/reports/Google_Android_Security_PHA_classifications.pdf">Potentially
	Harmful Applications</a>. Google Play Protect is enabled by default on devices
	with <a href="http://www.android.com/gms">Google Mobile Services</a>, and is
	especially important for users who install apps from outside of Google
	Play.</li>
	</ul>
	<h2 id="2018-02-01-details">2018-02-01 security patch level—Vulnerability details</h2>
	<p>
	In the sections below, we provide details for each of the security
	vulnerabilities that apply to the 2018-02-01 patch level. Vulnerabilities are
	grouped under the component that they affect. There is a description of the
	issue and a table with the CVE, associated references, <a href="#type">type
	of vulnerability</a>,
	<a href="/security/overview/updates-resources.html#severity">severity</a>,
	and updated AOSP versions (where applicable). When available, we link the public
	change that addressed the issue to the bug ID, like the AOSP change list. When
	multiple changes relate to a single bug, additional references are linked to
	numbers following the bug ID.
	</p>

	<h3 id="media-framework">Media framework</h3>
	<p>The most severe vulnerability in this section could enable a remote attacker
	using a specially crafted file to execute arbitrary code within the context of
	a privileged process.</p>

	<table>
	<col width="17%">
	<col width="19%">
	<col width="9%">
	<col width="14%">
	<col width="39%">
	<tr>
	<th>CVE</th>
	<th>References</th>
	<th>Type</th>
	<th>Severity</th>
	<th>Updated AOSP versions</th>
	</tr>
	<tr>
	<td>CVE-2017-13228</td>
	<td><a href="https://android.googlesource.com/platform/external/libavc/+/04b68a0a51729b655bcd0f5ae5ec20645eeda946">
	A-69478425</a></td>
	<td>RCE</td>
	<td>Critical</td>
	<td>6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td>
	</tr>
	<tr>
	<td>CVE-2017-13231</td>
	<td><a href="https://android.googlesource.com/platform/hardware/interfaces/+/16a3cd0b0729bd53265897cf8c790013156e92ce">
	A-67962232</a>
	</td>
	<td>EoP</td>
	<td>High</td>
	<td>8.0, 8.1</td>
	</tr>
	<tr>
	<td>CVE-2017-13232</td>
	<td><a href="https://android.googlesource.com/platform/frameworks/av/+/6a5d1fc7cbccd85054e56542a633149622effa67">
	A-68953950</a>
	</td>
	<td>ID</td>
	<td>High</td>
	<td>5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td>
	</tr>
	<tr>
	<td rowspan="2">CVE-2017-13230</td>
	<td rowspan="2"><a href="https://android.googlesource.com/platform/external/libhevc/+/68e532d83a1b98f6b5e297d71b547ed93a68dfe3">
	A-65483665</a></td>
	<td>DoS</td>
	<td>High</td>
	<td>7.0, 7.1.1, 7.1.2, 8.0, 8.1</td>
	</tr>
	<tr>
	<td>RCE</td>
	<td>Critical</td>
	<td>5.1.1, 6.0, 6.0.1</td>
	</tr>
	<tr>
	<td>CVE-2017-13233</td>
	<td><a href="https://android.googlesource.com/platform/external/libhevc/+/a22314db4e0cfe11ef3e50dac6a13d52f7a595b3">
	A-62851602</a>
	</td>
	<td>DoS</td>
	<td>High</td>
	<td>5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td>
	</tr>
	<tr>
	<td>CVE-2017-13234</td>
	<td><a href="https://android.googlesource.com/platform/external/sonivox/+/33f45caed3b60bf81790e9b76cf82c8e8d6ed902">
	A-68159767</a>
	</td>
	<td>DoS</td>
	<td>High</td>
	<td>5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td>
	</tr>
	</table>


	<h3 id="system">System</h3>
	<p>The most severe vulnerability in this section could enable a local malicious
	application to execute commands normally limited to privileged processes.</p>

	<table>
	<col width="17%">
	<col width="19%">
	<col width="9%">
	<col width="14%">
	<col width="39%">
	<tr>
	<th>CVE</th>
	<th>References</th>
	<th>Type</th>
	<th>Severity</th>
	<th>Updated AOSP versions</th>
	</tr>
	<tr>
	<td>CVE-2017-13236</td>
	<td><a href="https://android.googlesource.com/platform/system/security/+/80592e62a6ae095041e95b811ad7066dd44d37f6">
	A-68217699</a>
	[<a href="https://android.googlesource.com/platform/system/security/+/b49160023ee8f73ce0ac97f9f4604a34ebdecf76">2</a>]
	</td>
	<td>EoP</td>
	<td>Moderate</td>
	<td>8.0, 8.1</td>
	</tr>
	</table>

	<h2 id="2018-02-05-details">2018-02-05 security patch level—Vulnerability details</h2>
	<p>
	In the sections below, we provide details for each of the security
	vulnerabilities that apply to the 2018-02-05 patch level. Vulnerabilities are
	grouped under the component that they affect and include details such as the
	CVE, associated references, <a href="#type">type of vulnerability</a>,
	<a href="/security/overview/updates-resources.html#severity">severity</a>,
	component (where applicable), and updated AOSP versions (where applicable). When
	available, we link the public change that addressed the issue to the bug ID,
	like the AOSP change list. When multiple changes relate to a single bug,
	additional references are linked to numbers following the bug ID.
	</p>

	<h3 id="htc-components">HTC components</h3>
	<p>The most severe vulnerability in this section could enable a local malicious
	application to obtain unauthorized access to data.</p>

	<table>
	<col width="17%">
	<col width="19%">
	<col width="9%">
	<col width="14%">
	<col width="39%">
	<tr>
	<th>CVE</th>
	<th>References</th>
	<th>Type</th>
	<th>Severity</th>
	<th>Component</th>
	</tr>
	<tr>
	<td>CVE-2017-13238</td>
	<td>A-64610940<a href="#asterisk">*</a></td>
	<td>ID</td>
	<td>High</td>
	<td>Bootloader</td>
	</tr>
	<tr>
	<td>CVE-2017-13247</td>
	<td>A-71486645<a href="#asterisk">*</a></td>
	<td>EoP</td>
	<td>Moderate</td>
	<td>Bootloader</td>
	</tr>
	</table>


	<h3 id="kernel-components">Kernel components</h3>
	<p>The most severe vulnerability in this section could enable a local malicious
	application to execute arbitrary code within the context of a privileged
	process.</p>

	<table>
	<col width="17%">
	<col width="19%">
	<col width="9%">
	<col width="14%">
	<col width="39%">
	<tr>
	<th>CVE</th>
	<th>References</th>
	<th>Type</th>
	<th>Severity</th>
	<th>Component</th>
	</tr>
	<tr>
	<td>CVE-2017-15265</td>
	<td>A-67900971<br />
	<a
	href="https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/sound/?h=v4.4.103&id=23709ae9b61429502fcd4686e7a97333f3b3544a">
	Upstream kernel</a></td>
	<td>EoP</td>
	<td>High</td>
	<td>ALSA</td>
	</tr>
	<tr>
	<td>CVE-2015-9016</td>
	<td>A-63083046<br />
	<a
	href="https://github.com/torvalds/linux/commit/0048b4837affd153897ed1222283492070027aa9">
	Upstream kernel</a></td>
	<td>EoP</td>
	<td>High</td>
	<td>Multi-queue block IO</td>
	</tr>
	<tr>
	<td>CVE-2017-13273</td>
	<td>A-65853158<a href="#asterisk">*</a></td>
	<td>EoP</td>
	<td>High</td>
	<td>Kernel</td>
	</tr>
	</table>


	<h3 id="nvidia-components">NVIDIA components</h3>
	<p>The most severe vulnerability in this section could enable a local malicious
	application to execute arbitrary code within the context of a privileged
	process.</p>

	<table>
	<col width="17%">
	<col width="19%">
	<col width="9%">
	<col width="14%">
	<col width="39%">
	<tr>
	<th>CVE</th>
	<th>References</th>
	<th>Type</th>
	<th>Severity</th>
	<th>Component</th>
	</tr>
	<tr>
	<td>CVE-2017-6279</td>
	<td>A-65023166<a href="#asterisk">*</a><br />
	N-CVE-2017-6279</td>
	<td>EoP</td>
	<td>High</td>
	<td>Media framework</td>
	</tr>
	<tr>
	<td>CVE-2017-6258</td>
	<td>A-38027496<a href="#asterisk">*</a><br />
	N-CVE-2017-6258</td>
	<td>EoP</td>
	<td>High</td>
	<td>Media framework</td>
	</tr>
	</table>


	<h3 id="qualcomm-components">Qualcomm components</h3>
	<p>The most severe vulnerability in this section could enable a remote attacker
	using a specially crafted file to execute arbitrary code within the context of
	a privileged process.</p>

	<table>
	<col width="17%">
	<col width="19%">
	<col width="9%">
	<col width="14%">
	<col width="39%">
	<tr>
	<th>CVE</th>
	<th>References</th>
	<th>Type</th>
	<th>Severity</th>
	<th>Component</th>
	</tr>
	<tr>
	<td>CVE-2017-15860</td>
	<td>A-68992416<br />
	<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-2.0/commit/?id=71331327ac389bff7d5af2707c4325e5b7949013">
	QC-CR#2082544</a>
	[<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-2.0/commit/?id=a6afff2717791ceb281354833d4489123ae62605">2</a>]</td>
	<td>RCE</td>
	<td>Critical</td>
	<td>WLan</td>
	</tr>
	<tr>
	<td>CVE-2017-11041</td>
	<td>A-35269676<a href="#asterisk">*</a><br />
	QC-CR#2053101</td>
	<td>EoP</td>
	<td>High</td>
	<td>Media framework</td>
	</tr>
	<tr>
	<td>CVE-2017-17767</td>
	<td>A-64750179<a href="#asterisk">*</a><br />
	QC-CR#2115779</td>
	<td>EoP</td>
	<td>High</td>
	<td>Media framework</td>
	</tr>
	<tr>
	<td>CVE-2017-17765</td>
	<td>A-68992445<br />
	<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=66e561b0c7fff54e8cacd87d2b7d9bb3eef4f13b">
	QC-CR#2115112</a></td>
	<td>EoP</td>
	<td>High</td>
	<td>WLan</td>
	</tr>
	<tr>
	<td>CVE-2017-15862</td>
	<td>A-68992439<br />
	<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=41ee23cd0972ef2ed47dd76eb7cd44a0268e4f9f">
	QC-CR#2114426</a></td>
	<td>EoP</td>
	<td>High</td>
	<td>WLan</td>
	</tr>
	<tr>
	<td>CVE-2017-14884</td>
	<td>A-68992429<br />
	<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-2.0/commit/?id=0ce15ef4075719a82858b7324690be7011cab832">
	QC-CR#2113052</a></td>
	<td>EoP</td>
	<td>High</td>
	<td>WLan</td>
	</tr>
	<tr>
	<td>CVE-2017-15829</td>
	<td>A-68992397<br />
	<a href="https://source.codeaurora.org/quic/la/kernel/msm-4.4/commit/?id=c1b60e554e158bfcf6932ed2c543c309236e0f79">
	QC-CR#2097917</a></td>
	<td>EoP</td>
	<td>High</td>
	<td>Graphics_Linux</td>
	</tr>
	<tr>
	<td>CVE-2017-15820</td>
	<td>A-68992396<br />
	<a href="https://source.codeaurora.org/quic/la/kernel/msm-4.4/commit/?id=7599c5b7d87248b4772d6c4b70ccb922704c8095">
	QC-CR#2093377</a></td>
	<td>EoP</td>
	<td>High</td>
	<td>Graphics_Linux</td>
	</tr>
	<tr>
	<td>CVE-2017-17764</td>
	<td>A-68992443<br />
	<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=f451565c052a0322565225515f46be677c0d1b18">
	QC-CR#2114789</a></td>
	<td>EoP</td>
	<td>High</td>
	<td>WLan</td>
	</tr>
	<tr>
	<td>CVE-2017-15861</td>
	<td>A-68992434<br />
	<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=13e3a516935a0dd90a7bc39e51c30c1592c548b7">
	QC-CR#2114187</a></td>
	<td>EoP</td>
	<td>High</td>
	<td>WLan</td>
	</tr>
	</table>


	<h3 id="qualcomm-closed-source-components">Qualcomm closed-source
	components</h3>
	<p>These vulnerabilities affect Qualcomm components and are described in
	further detail in the appropriate Qualcomm AMSS security bulletin or security
	alert. The severity assessment of these issues is provided directly by
	Qualcomm.</p>

	<table>
	<col width="17%">
	<col width="19%">
	<col width="9%">
	<col width="14%">
	<col width="39%">
	<tr>
	<th>CVE</th>
	<th>References</th>
	<th>Type</th>
	<th>Severity</th>
	<th>Component</th>
	</tr>
	<tr>
	<td>CVE-2017-14910</td>
	<td>A-62212114<a href="#asterisk">*</a></td>
	<td>N/A</td>
	<td>High</td>
	<td>Closed-source component</td>
	</tr>
	</table>

	<h2 id="common-questions-and-answers">Common questions and answers</h2>
	<p>
	This section answers common questions that may occur after reading this
	bulletin.</p>
	<p><strong>1. How do I determine if my device is updated to address these issues?
	</strong></p>
	<p>To learn how to check a device's security patch level, see
	<a href="https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices">Check
	and update your Android version</a>.</p>
	<ul>
	<li>Security patch levels of 2018-02-01 or later address all issues associated
	with the 2018-02-01 security patch level.</li>
	<li>Security patch levels of 2018-02-05 or later address all issues associated
	with the 2018-02-05 security patch level and all previous patch levels.</li>
	</ul>
	<p>
	Device manufacturers that include these updates should set the patch string
	level to:
	</p>
	<ul>
	<li>[ro.build.version.security_patch]:[2018-02-01]</li>
	<li>[ro.build.version.security_patch]:[2018-02-05]</li>
	</ul>
	<p>
	<strong>2. Why does this bulletin have two security patch levels?</strong>
	</p>
	<p>
	This bulletin has two security patch levels so that Android partners have the
	flexibility to fix a subset of vulnerabilities that are similar across all
	Android devices more quickly. Android partners are encouraged to fix all issues
	in this bulletin and use the latest security patch level.
	</p>
	<ul>
	<li>Devices that use the 2018-02-01 security patch level must include all issues
	associated with that security patch level, as well as fixes for all issues
	reported in previous security bulletins.</li>
	<li>Devices that use the security patch level of 2018-02-05 or newer must
	include all applicable patches in this (and previous) security
	bulletins.</li>
	</ul>
	<p>
	Partners are encouraged to bundle the fixes for all issues they are addressing
	in a single update.
	</p>
	<p id="type">
	<strong>3. What do the entries in the <em>Type</em> column mean?</strong>
	</p>
	<p>
	Entries in the <em>Type</em> column of the vulnerability details table reference
	the classification of the security vulnerability.
	</p>
	<table>
	<col width="25%">
	<col width="75%">
	<tr>
	<th>Abbreviation</th>
	<th>Definition</th>
	</tr>
	<tr>
	<td>RCE</td>
	<td>Remote code execution</td>
	</tr>
	<tr>
	<td>EoP</td>
	<td>Elevation of privilege</td>
	</tr>
	<tr>
	<td>ID</td>
	<td>Information disclosure</td>
	</tr>
	<tr>
	<td>DoS</td>
	<td>Denial of service</td>
	</tr>
	<tr>
	<td>N/A</td>
	<td>Classification not available</td>
	</tr>
	</table>
	<p>
	<strong>4. What do the entries in the <em>References</em> column mean?</strong>
	</p>
	<p>
	Entries under the <em>References</em> column of the vulnerability details table
	may contain a prefix identifying the organization to which the reference value
	belongs.
	</p>
	<table>
	<col width="25%">
	<col width="75%">
	<tr>
	<th>Prefix</th>
	<th>Reference</th>
	</tr>
	<tr>
	<td>A-</td>
	<td>Android bug ID</td>
	</tr>
	<tr>
	<td>QC-</td>
	<td>Qualcomm reference number</td>
	</tr>
	<tr>
	<td>M-</td>
	<td>MediaTek reference number</td>
	</tr>
	<tr>
	<td>N-</td>
	<td>NVIDIA reference number</td>
	</tr>
	<tr>
	<td>B-</td>
	<td>Broadcom reference number</td>
	</tr>
	</table>
	<p id="asterisk">
	<strong>5. What does a * next to the Android bug ID in the <em>References</em>
	column mean?</strong>
	</p>
	<p>
	Issues that are not publicly available have a * next to the Android bug ID in
	the <em>References</em> column. The update for that issue is generally contained
	in the latest binary drivers for Nexus devices available from the <a
	href="https://developers.google.com/android/nexus/drivers">Google Developer
	site</a>.
	</p>
	<p>
	<strong>6. Why are security vulnerabilities split between this bulletin and
	device/partner security bulletins, such as the Pixel / Nexus bulletin?</strong>
	</p>
	<p>
	Security vulnerabilities that are documented in this security bulletin are
	required in order to declare the latest security patch level on Android devices.
	Additional security vulnerabilities that are documented in the device/partner
	security bulletins are not required for declaring a security patch level.
	Android device and chipset manufacturers are encouraged to document the presence
	of other fixes on their devices through their own security websites, such as the
	<a href="https://security.samsungmobile.com/securityUpdate.smsb">Samsung</a>, <a
	href="https://lgsecurity.lge.com/security_updates.html">LGE</a>, or <a
	href="/security/bulletin/pixel/">Pixel&hairsp;/&hairsp;Nexus</a>
	security bulletins.
	</p>
	<h2 id="versions">Versions</h2>
	<table>
	<col width="25%">
	<col width="25%">
	<col width="50%">
	<tr>
	<th>Version</th>
	<th>Date</th>
	<th>Notes</th>
	</tr>
	<tr>
	<td>1.0</td>
	<td>February 5, 2018</td>
	<td>Bulletin published.</td>
	</tr>
	<tr>
	<td>1.1</td>
	<td>February 7, 2018</td>
	<td>Bulletin revise to include AOSP links.</td>
	</tr>
	<tr>
	<td>1.2</td>
	<td>February 14, 2018</td>
	<td>Corrected CVE numbers for CVE-2017-13273, CVE-2017-15860, CVE-2017-15861 and
	CVE-2017-15862.</td>
	</tr>
	<tr>
	<td>1.3</td>
	<td>April 2, 2018</td>
	<td>Moved CVE-2017-15817 from the February Android Bulletin to the February Pixel Bulletin.</td>
	</tr>
	</table>
	</body></html>