diff options
179 files changed, 12831 insertions, 4046 deletions
diff --git a/OWNERS.android b/OWNERS.android index 0b6d9eff..b5392488 100644 --- a/OWNERS.android +++ b/OWNERS.android @@ -1,8 +1,9 @@ # Used by the Gerrit find-owners plugin to find reviewers -blamb@google.com claym@google.com cqn@google.com daroberts@google.com gdimino@google.com hvm@google.com +kennethlau@google.com mheco@google.com +stayres@google.com @@ -2,7 +2,51 @@ Googlers, please see: go/sac-guide -External users, the source.android.com site contains tutorials, references, and -other information related to the Android Open Source Project (AOSP). To report -an issue with the documentation on source.android.com, please file a bug at: +The source.android.com site contains tutorials, references, and other +information related to the Android Open Source Project (AOSP). To report an +issue with the documentation on source.android.com, please file a bug at: https://issuetracker.google.com/issues/new?component=191476 + +To make updates to the source files themselves, follow the instructions below. + +### File Location ### + +The source.android.com source files are stored in the platform/docs/source.android.com/ +Android project: +https://android.googlesource.com/platform/docs/source.android.com/ + +The files to be edited are located in: <projroot>/docs/source.android.com/<language-code>/ + +Subdirectories exist for the tabs of source.android.com with their structure +roughly (but not identically) mirroring navigation of the site. For exceptions, +the contents of the Porting tab can be found in the devices/ subdirectory, +while the contents of the Tuning tab reside in the devices/tech subdirectory. +(This is temporary while navigational changes are underway.) + +## Edit Instructions ## + +1. Initialize and sync the repository and download the Android source per: +https://source.android.com/source/downloading.html + +2. Navigate to the docs/source.android.com project. + +3. Start a temporary branch for your changes with a command resembling: +$ repo start <topic-branch-name> . + +See the Repo command reference for more details: +http://source.android.com/source/using-repo.html#start + +4. Add or edit the file(s) and save your changes: +$ git add <file> +$ git commit +$ repo upload . + +5. Iteratively improve the change and amend the commit: +$ git commit -a --amend +$ repo upload . + +6. Once satisfied, include the changelist in a bug filed at: +https://issuetracker.google.com/issues/new?component=191476 + +Your change will be routed to the source.android.com team for evaluation and +inclusion. diff --git a/en/_index.yaml b/en/_index.yaml index db5f4429..796a08ac 100644 --- a/en/_index.yaml +++ b/en/_index.yaml @@ -59,12 +59,8 @@ landing_page: porting. And now this site is available in China at <a href="https://source.android.google.cn/">source.android.google.cn</a>.<br><br> - As the AOSP documentation site, we seek your contributions. With an - ever-changing ecosystem, we need your help to stay fresh. You may make - your own fixes directly to the source files by following the - instructions in our <a - href="https://android.googlesource.com/platform/docs/source.android.com/+/master/README.txt">README</a>. - You may also use the <a + As the AOSP documentation site, we seek your input. With an + ever-changing ecosystem, we need your help to stay fresh. Please use the <a href="https://issuetracker.google.com/issues/new?component=191476">Site Feedback</a> link at the bottom of any page to report bugs and offer suggestions for enhancement. See the site’s <a @@ -73,6 +69,13 @@ landing_page: image_path: /images/android_stack.png - heading: News items: + - heading: April Security Bulletins + description: > + The April 2018 Android and Pixel/Nexus Security Bulletins have been + published to support the April security release. + buttons: + - label: April 4th, 2018 + path: /security/bulletin/2018-04-01 - heading: Android 2017 Year in Review description: > The Android Security 2017 Year in Review covers everything that happened @@ -80,13 +83,6 @@ landing_page: buttons: - label: March 15th, 2018 path: /security/overview/reports - - heading: March Security Bulletins - description: > - The March 2018 Android and Pixel/Nexus Security Bulletins have been - published to support the March security release. - buttons: - - label: March 7th, 2018 - path: /security/bulletin/2018-03-01 - heading: ART DEX bytecode improvements description: > Android runtime (ART) now includes bytecode documentation for diff --git a/en/compatibility/5.1/android-5.1-cdd.html b/en/compatibility/5.1/android-5.1-cdd.html index 377d9f9d..d579ead3 100644 --- a/en/compatibility/5.1/android-5.1-cdd.html +++ b/en/compatibility/5.1/android-5.1-cdd.html @@ -4508,6 +4508,14 @@ Definition in this release. </p> <td>7.6.2. Application Shared Storage</td> <td>Apps can use ACTION_OPEN_DOCUMENT_TREE to write to secondary ext. storage</td> </tr> + <tr> + <td>7.6.2. Application Shared Storage</td> + <td>Clarify that /sdcard can share storage with /data</td> + </tr> + <tr> + <td>7.7 USB</td> + <td>Remove redundant requirement on UMS/MTP from 7.7</td> + </tr> <tr> <td>7.8.1. Microphone</td> <td>Added Android Automotive requirements.</td> diff --git a/en/compatibility/_toc-compatibility.yaml b/en/compatibility/_toc-compatibility.yaml index e10be874..d45a8653 100644 --- a/en/compatibility/_toc-compatibility.yaml +++ b/en/compatibility/_toc-compatibility.yaml @@ -53,6 +53,14 @@ toc: path: /compatibility/vts/ - title: Systems Testing with VTS path: /compatibility/vts/systems + - title: Test Framework + section: + - title: Device Shell Commands + path: /compatibility/vts/shell-commands + - title: Test Templates + path: /compatibility/vts/test-templates + - title: Multi-Device Testing + path: /compatibility/vts/multi-device-testing - title: VTS Dashboard Setup path: /compatibility/vts/setup - title: VTS Dashboard Database diff --git a/en/compatibility/vts/images/vts_batch_output_xml.png b/en/compatibility/vts/images/vts_batch_output_xml.png Binary files differnew file mode 100644 index 00000000..de95eb1d --- /dev/null +++ b/en/compatibility/vts/images/vts_batch_output_xml.png diff --git a/en/compatibility/vts/images/vts_batch_terminal_output.png b/en/compatibility/vts/images/vts_batch_terminal_output.png Binary files differnew file mode 100644 index 00000000..58a81da7 --- /dev/null +++ b/en/compatibility/vts/images/vts_batch_terminal_output.png diff --git a/en/compatibility/vts/images/vts_device_serials.png b/en/compatibility/vts/images/vts_device_serials.png Binary files differnew file mode 100644 index 00000000..22ae9525 --- /dev/null +++ b/en/compatibility/vts/images/vts_device_serials.png diff --git a/en/compatibility/vts/images/vts_hostside_agent.png b/en/compatibility/vts/images/vts_hostside_agent.png Binary files differnew file mode 100644 index 00000000..09761066 --- /dev/null +++ b/en/compatibility/vts/images/vts_hostside_agent.png diff --git a/en/compatibility/vts/images/vts_hostside_hal.png b/en/compatibility/vts/images/vts_hostside_hal.png Binary files differnew file mode 100644 index 00000000..829df99b --- /dev/null +++ b/en/compatibility/vts/images/vts_hostside_hal.png diff --git a/en/compatibility/vts/images/vts_non_batch.png b/en/compatibility/vts/images/vts_non_batch.png Binary files differnew file mode 100644 index 00000000..86df0981 --- /dev/null +++ b/en/compatibility/vts/images/vts_non_batch.png diff --git a/en/compatibility/vts/images/vts_shell_driver.png b/en/compatibility/vts/images/vts_shell_driver.png Binary files differnew file mode 100644 index 00000000..f7538db7 --- /dev/null +++ b/en/compatibility/vts/images/vts_shell_driver.png diff --git a/en/compatibility/vts/images/vts_target_hidl.png b/en/compatibility/vts/images/vts_target_hidl.png Binary files differnew file mode 100644 index 00000000..79684098 --- /dev/null +++ b/en/compatibility/vts/images/vts_target_hidl.png diff --git a/en/compatibility/vts/images/vts_template_arch.png b/en/compatibility/vts/images/vts_template_arch.png Binary files differnew file mode 100644 index 00000000..d7a19636 --- /dev/null +++ b/en/compatibility/vts/images/vts_template_arch.png diff --git a/en/compatibility/vts/images/vts_template_extension.png b/en/compatibility/vts/images/vts_template_extension.png Binary files differnew file mode 100644 index 00000000..1a36b723 --- /dev/null +++ b/en/compatibility/vts/images/vts_template_extension.png diff --git a/en/compatibility/vts/multi-device-testing.html b/en/compatibility/vts/multi-device-testing.html new file mode 100644 index 00000000..039baf77 --- /dev/null +++ b/en/compatibility/vts/multi-device-testing.html @@ -0,0 +1,212 @@ +<html devsite> + <head> + <title>Multi-Device Testing</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 + + http://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>VTS supports tests that require interaction between multiple Android +devices.</p> + +<h2 id="architecture">Architecture</h2> +<p>VTS uses the TradeFed framework to get and pass device serials to test +modules.</p> + +<p><img src="images/vts_device_serials.png"></p> +<figcaption><strong>Figure 1.</strong> VTS passing device serials.</figcaption> + +<p>Device requirements, such as number of devices and device types, are +specified in test plan configuration. For example, you can specify a test plan +that requires two Android devices with Sailfish build targets.</p> + +<h3 id="device-allocation">Device allocation</h3> +<p>The test infrastructure (usually the test scheduler) allocates available +devices that satisfy the requirements specified in test plan configuration to +the VTS framework. Allocated devices are reserved for the test plan even if the +test module is not using them. VTS agent binaries are then pushed to and run on +all allocated devices (unless specifically instructed not to run). This ensures +that TCP connections for shell commands and HAL RPCs are available for all +devices in a test script.</p> + +<h3 id="test-preparers">Test preparers</h3> +<p>The framework runs test preparers for all devices for which it received +serial numbers. Target preparers can be single or multi-device:</p> +<ul> +<li>Single-device target preparers (example at +<a href="https://android.googlesource.com/platform/test/vts/+/master/harnesses/tradefed/src/com/android/tradefed/targetprep/VtsDeviceInfoCollector.java" class="external">VtsDeviceInfoCollector</a>): +<ul> +<li>Can be specified only in test plan configuration with the required +device list (future versions will allow module level configuration).</li> +<li>Receive only one device serial.</li> +<li>Run preparing and cleanup tasks against a specific device.</li> +</ul> +</li> +<li>Multi-device target preparers (example at +<a href="https://android.googlesource.com/platform/test/vts/+/master/harnesses/tradefed/src/com/android/tradefed/targetprep/VtsPythonVirtualenvPreparer.java" class="external">VtsPythonVirtualenvPreparer</a>): +<ul> +<li>Can be specified in test plan configuration or test module +configuration</li> +<li>Receive all device serials</li> +<li>Run preparing and cleanup tasks for each device or all devices.</li> +</ul> +</li> +</ul> + +<h3 id="test-modules">Test modules</h3> +<p>Test modules get a list of devices after the test preparers finish setting up +the host/devices. One host-side Python test module runs for each multi-device +test module. Allocated Android devices are accessible from Python test modules +as a list of +<a href="https://android.googlesource.com/platform/test/vts/+/master/utils/python/controllers/android_device.py#322" class="external">AndroidDevice</a> +objects:</p> +<pre class="devsite-click-to-copy"> +devices = self.android_devices +device1 = devices[0] +device1_serial = device1.serial +</pre> + +<p>All allocated devices are reserved for the test plan, even though a test +module in the plan is only using one device.</p> + +<h2 id="device-communication">Device communication during testing</h1> +<p>Effective multi-Android tests involve communication between allocated +devices. When developing such tests, you must determine how to establish +communication between the allocated devices. The following sections provide +three communication examples (however, test developers are free to design other +models).</p> + +<h3 id="type1">Type 1: Host-side HAL tests</h3> +<p>Host-side HAL tests can use VTS HAL drivers that are pushed to devices by +default:</p> + +<p><img src="images/vts_hostside_hal.png"></p> +<figcaption><strong>Figure 2.</strong> Host-side HAL test.</figcaption> + +<p>In this scenario:</p> +<ul> +<li>Test logic executes on the host.</li> +<li>Host-side test script issues RPC calls to the drivers on each device.</li> +<li>Host side coordinates device interactions.</li> +</ul> + +<h3 id="type2">Type 2: Host-side agent-based tests</h3> +<p>Instead of using VTS agents on device, a host-side test can also push its own +agent (app or binary) to each device:</p> + +<p><img src="images/vts_hostside_agent.png"></p> +<figcaption><strong>Figure 3.</strong> Host-side, agent-based test.</figcaption> + +<p>In this scenario:</p> +<ul> +<li>Test logic executes on the host.</li> +<li>Agent app (or binary) installs on each device.</li> +<li>Host-side test script issues commands to apps on each device.</li> +<li>Host side coordinates device interactions.</li> +</ul> + +<p>For example, the +<a href="https://android.googlesource.com/platform/test/vts-testcase/nbu/+/master" class="external">Next +Billion User tests</a> in current VTS repo are host-side, app-based, +multi-device tests.</p> + +<h3 id="type3">Type 3: Target-side HIDL tests</h2> +<p>Target-side, multi-device HIDL tests put all test logic on device-side test +binaries, which requires the tests to synchronize devices during test +execution:</p> + +<p><img src="images/vts_target_hidl.png"></p> +<figcaption><strong>Figure 4. </strong>Target-based HIDL test.</figcaption> + +<p>In this scenario:</p> +<ul> +<li>Test logic executes on devices.</li> +<li>Host-side framework provides initial device identification.</li> +<li>Target-side test binary requires synchronization:<ul> +<li>Same test binary for all devices.</li> +<li>Different test binaries for each role.</li> +</ul> +</li> +</ul> + +<h2 id="example-multi-device">Example: Multi-device test plan</h2> +<p>This example specifies the config for two devices:</p> +<ul> +<li>Device 1 includes a build provider and +<code>VtsDeviceInfoCollector</code> target preparer.</li> +<li>Device 2 includes an additional <code>FilePusher</code> preparer that pushes +a group of host-driven related files to the device.</li> +</ul> + +<pre class="devsite-click-to-copy"> +<configuration description="VTS Codelab Plan"> + ... +<device name="device1"> +<build_provider class="com.android.compatibility.common.tradefed.build.CompatibilityBuildProvider" /> +<target_preparer class="com.android.tradefed.targetprep.VtsDeviceInfoCollector" /> +</device> +<device name="device2" > +<build_provider class="com.android.compatibility.common.tradefed.build.CompatibilityBuildProvider" /> +<target_preparer class="com.android.tradefed.targetprep.VtsDeviceInfoCollector" /> +<target_preparer class="com.android.compatibility.common.tradefed.targetprep.VtsFilePusher"> +<option name="push-group" value="HostDrivenTest.push" /> +</target_preparer> +</device> +<option name="compatibility:include-filter" value="VtsCodelabHelloWorldMultiDeviceTest" /> +</configuration> +</pre> + +<h2 id="example-hostside">Example: Host-side Python test script</h2> +<p>For details and examples on test preparers, see +<a href="#Test-preparers">Test Preparers</a>. For a complete host-side +multi-device example, refer to the +<a href="https://android.googlesource.com/platform/test/vts/+/master/testcases/codelab/hello_world_multi" class="external">hello_world_multi +codelab</a>. +</p> + +<pre class="devsite-click-to-copy"> +def setUpClass(self): +logging.info('number of device: %s', self.android_devices) +asserts.assertEqual(len(self.android_devices), 2, 'number of device is wrong.') +self.dut1 = self.android_devices[0] +self.dut2 = self.android_devices[1] +self.shell1 = self.dut1.shell +self.shell2 = self.dut2.shell + +def testSerialNotEqual(self): +'''Checks serial number from two device not being equal.''' +command = 'getprop | grep ro.serial' +res1 = self.shell1.Execute(command) +res2 = self.shell2.Execute(command) + +def getSerialFromShellOutput(output): +'''Get serial from getprop query''' +return output[const.STDOUT][0].strip().split(' ')[-1][1:-1] +serial1 = getSerialFromShellOutput(res1) +serial2 = getSerialFromShellOutput(res2) + +logging.info('Serial number of device 1 shell output: %s', serial1) +logging.info('Serial number of device 2 shell output: %s', serial2) +asserts.assertNotEqual(serial1, serial2, 'serials from two devices should not be the same') +asserts.assertEqual(serial1, self.dut1.serial, 'serial got from device system property is different from allocated serial') +asserts.assertEqual(serial2, self.dut2.serial, 'serial got from device system property is different from allocated serial') +</pre> + +</body> +</html>
\ No newline at end of file diff --git a/en/compatibility/vts/shell-commands.html b/en/compatibility/vts/shell-commands.html new file mode 100644 index 00000000..149226d2 --- /dev/null +++ b/en/compatibility/vts/shell-commands.html @@ -0,0 +1,166 @@ +<html devsite> + <head> + <title>Device Shell Commands</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 + + http://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>During VTS testing, shell commands are used to execute a target-side test +binary, to get/set properties, environment variables, and system information, +and to start/stop the Android framework. You can execute VTS device shell +commands using the <code>adb shell</code> command or the VTS shell driver +running on the device (recommended).</p> + +<h2 id="adb-shell">Using ADB shell</h2> +<p>Tests that require shutting down the USB port or rebooting the device during +testing must use ADB shell as the VTS shell driver is unavailable without a +persistent USB connection. You can invoke ADB shell from the +<code>AndroidDevice</code> object in the Python test script. Examples:</p> +<ul> +<li>Get an Android device object: +<pre class="devsite-click-to-copy"> +self.device = self.android_devices[0] +</pre> +</li> +<li>Issue a single shell command: +<pre class="devsite-click-to-copy"> +result = self.device.adb.shell(‘ls') +</pre> +</li> +</ul> + +<h2 id="vts-shell-driver">Using the VTS shell driver</h2> +<p>The VTS shell driver is an agent binary that runs on the device and executes +shell commands. By default, VTS uses the shell driver if the driver is running +on device because this method has less latency than using the <code>adb +shell</code> command.</p> + +<p><img src="images/vts_shell_driver.png"></p> +<figcaption><strong>Figure 1.</strong> VTS shell driver.</figcaption> + +<p>The VTS framework supports multi-device testing where each Android device +is represented as an AndroidDevice object in base runner. By default, VTS +framework pushes VTS agent and VTS shell driver binaries to each Android device +and establishes TCP connections to the VTS agents on those devices.</p> + +<p>To execute a shell command, the host-side Python script makes a function +call to the ShellMirror object inside AndroidDevice object. The ShellMirror +object packs the shell command texts into a +<a href="https://developers.google.com/protocol-buffers/" class="external">protobuf</a> +message and sends it (via the TCP channel) to the VTS agent on the Android +device. The agent running on device then forwards the shell command to VTS shell +driver via the Unix socket.</p> + +<p>When the VTS shell driver receives a shell command, it executes the command +via <a href="https://en.wikipedia.org/wiki/Nohup" class="external">nohup</a> on +the device shell to prevent hanging. Stdout, stderr, and return code are then +retrieved from <code>nohup</code> and sent back to VTS agent. Finally, the agent +replies to the host by wrapping the command result(s) into a +<code>protobuf</code> message.</p> + +<h3 id="advantages">Advantages</h3> +<p>The advantages of using the VTS shell driver instead of <code>adb +shell</code> include:</p> +<ul> +<li><strong>Reliability.</strong> The VTS shell driver uses +<code>nohup</code> to execute commands on default setting. As VTS tests are +mostly lower level HAL and kernel tests, <code>nohup</code> ensures shell +commands do not hang during execution.</li> +<li><strong>Performance</strong>. While the <code>adb shell</code> command +caches some results (such as listing files in a directory) it has a connection +overhead when performing tasks such as executing a test binary. VTS shell driver +maintains an active connection throughout the test so the only overhead is USB +communication. In our testing, using VTS shell driver to execute a command with +100 calls to an empty gtest binary is about 20 percent faster than using +<code>adb shell</code>; the actual difference is larger since VTS shell +communication has extensive logging.</li> +<li><strong>State-keeping</strong>. The VTS shell driver maintains a terminal +session for each terminal name (default terminal name is +<em>default</em>). Environment variables set in one terminal session are +available only to subsequent commands in the same session.</li> +<li><strong>Extendable</strong>. Shell command communications between VTS +framework and device driver are wrapped in protobuf to enable potential +compression, remoting, encryption, etc. in the future. Other possibilities for +improving performance are also available, including device-side result parsing +when the communication overhead becomes larger than result string parsing.</li> +</ul> + +<h3 id="disadvantages">Disadvantages</h3> +<p>The disadvantages of using the VTS shell driver instead of <code>adb +shell</code> include:</p> +<ul> +<li><strong>Additional binaries</strong>. VTS agent files must be pushed to +device and cleaned up after test execution.</li> +<li><strong>Requires active connection</strong>. If the TCP connection between +host and agent is lost during testing (due to USB disconnection, port shutdown, +device crash, etc.) either intentionally or unintentionally, a shell command +cannot be transmitted to the VTS agent. Even with automatic switching to +<code>adb shell</code>, the result and state of the command before disconnection +would be unknown.</li> +</ul> + +<h3 id="examples">Examples</h3> +<p>Examples of using shell commands in a VTS host-side Python test script:</p> +<ul> +<li>Get an Android device object: +<pre class="devsite-click-to-copy"> +self.device = self.android_devices[0] +</pre> +</li> +<li>Get an shell object for the selected device: +<pre class="devsite-click-to-copy"> +self.shell = self.device.shell +</pre> +</li> +<li>Issue a single shell command: +<pre class="devsite-click-to-copy"> +results = self.shell.Execute(‘ls') +</pre> +</li> +<li>Issue a list of shell commands: +<pre class="devsite-click-to-copy"> +results = self.shell.Execute([‘cd /data/local/tmp', ‘ls']) +</pre> +</li> +</ul> + +<h3 id="command-result-object">Command result object</h3> +<p>The return object from shell command execution is a dictionary containing the +keys <code>stdouts</code>, <code>stderrs</code>, and <code>return_codes</code>. +Regardless of whether the shell command is provided as a single string or a list +of command strings, each value of the result dictionary is always a list.</p> + +<p>To verify the return code of a list of commands, the test script must check +the indices. Example:</p> + +<pre class="devsite-click-to-copy"> +asserts.assertFalse(any(results[‘return_codes']), ‘some command failed.') +</pre> + +<p>Alternatively, the script can check each command index individually. +Example:</p> + +<pre class="devsite-click-to-copy"> +asserts.assertEqual(results[‘return_codes'][0], 0, ‘first command failed')<br> +asserts.assertEqual(results[‘return_codes'][1], 0, ‘second command failed') +</pre> + +</body> +</html>
\ No newline at end of file diff --git a/en/compatibility/vts/test-templates.html b/en/compatibility/vts/test-templates.html new file mode 100644 index 00000000..27246906 --- /dev/null +++ b/en/compatibility/vts/test-templates.html @@ -0,0 +1,382 @@ +<html devsite> + <head> + <title>Test Templates</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 + + http://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>AOSP includes test templates for test modules that are not host-side Python +subclass of VTS runner's BaseTest. </p> + +<p><img src="images/vts_template_arch.png"></p> +<figcaption><strong>Figure 1.</strong> Test template architecture.</figcaption> + +<p>Developers can use these templates to minimize the effort involved in +integrating such tests. This section covers configuring and using the test +templates (located in the VTS +<a href="https://android.googlesource.com/platform/test/vts/+/master/testcases/template/">testcases/template</a> +directory) and provides examples for commonly used templates.</p> + +<h2 id="binarytest">BinaryTest template</h2> +<p>Use the +<a href="https://android.googlesource.com/platform/test/vts/+/sdk-release/testcases/template/binary_test/binary_test.py" class="external">BinaryTest +template</a> to integrate tests that execute on target device in VTS. +Target-side tests include:</p> + +<ul> +<li><strong>C++</strong> based tests compiled and pushed to device</li> +<li>Target-side <strong>Python</strong> tests compiled as binaries</li> +<li><strong>Shell scripts</strong> executable on devices</li> +</ul> + +<p>These tests can be integrated into VTS with or without the BinaryTest +template.</p> + +<h3 id="target-side">Integrating target-side tests with +BinaryTest template</h3> +<p>The BinaryTest template is designed to help developers easily integrate +target-side tests. In most cases, you can add a few simple lines of +configuration in <code>AndroidTest.xml</code>. Example configuration from +<a href="https://android.googlesource.com/platform/test/vts-testcase/kernel/+/master/api/early_mount/AndroidTest.xml" class="external">VtsDeviceTreeEarlyMountTest</a>: +</p> + +<pre class="devsite-click-to-copy"> +<configuration description="Config for VTS VtsDeviceTreeEarlyMountTest."> + ... +<test class="com.android.tradefed.testtype.VtsMultiDeviceTest"> +<option name="test-module-name" value="VtsDeviceTreeEarlyMountTest"/> +<option name="binary-test-source" value="_32bit::DATA/nativetest/dt_early_mount_test/dt_early_mount_test" /> +<option name="binary-test-source" value="_64bit::DATA/nativetest64/dt_early_mount_test/dt_early_mount_test" /> +<option name="test-timeout" value="5m"/> +</test> +</configuration> +</pre> + +<p>In this configuration:</p> +<ul> +<li><code>binary-test-source</code> and <code>binary-test-type</code> are +template-specific.</li> +<li>Specifying the test binary source's relative host path enables the template +to handle preparation, file pushing, test execution, result parsing, and +cleanup.</li> +<li>The template contains test case creation-related methods for subclasses to +override.</li> +<li>The template assumes one test case per test binary module, and the binary +source file name is used as test case name by default.</li> +</ul> + +<h4>Configuration options</h4> +<p>The BinaryTest template supports the following configuration options:</p> + +<table> +<thead> +<tr> +<th width="25%">Option name</th> +<th width="12%">Value type</th> +<th>Description</th> +</tr> +</thead> +<tbody> +<tr> +<td>binary-test-source</td> +<td>strings</td> +<td>Binary test source paths relative to vts test-case directory on +host.<br> +Example: <code>DATA/nativetest/test</code></td> +</tr> +<tr> +<td>binary-test-working-directory</td> +<td>strings</td> +<td>Working directories (device-side path).<br> +Example: <code>/data/local/tmp/testing/</code></td> +</tr> +<tr> +<td>binary-test-envp</td> +<td>strings</td> +<td>Environment variables for binary.<br> +Example: <code>PATH=/new:$PATH</code></td> +</tr> +<tr> +<td>binary-test-args</td> +<td>strings</td> +<td>Test arguments or flags.<br> +Example: <code>--gtest_filter=test1</code></td> +</tr> +<tr> +<td>binary-test-ld-library-path</td> +<td>strings</td> +<td><code>LD_LIBRARY_PATH</code> environment variable.<br> +Example: <code>/data/local/tmp/lib</code></td> +</tr> +<tr> +<td>binary-test-disable-framework</td> +<td>boolean</td> +<td>Run <code>adb stop</code> to turn off the Android Framework before test. +Example: <code>true</code></td> +</tr> +<tr> +<td>binary-test-stop-native-servers</td> +<td>boolean</td> +<td>Stop all properly configured native servers during the testing. Example: +<code>true</code></td> +</tr> +<tr> +<td>binary-test-type</td> +<td>string</td> +<td>Template type. Other template types extend from this template, but you +don't have to specify this option for this template because you already +specified <code>binary-test-source</code>.</td> +</tr> +</tbody> +</table> + +<p>For options with value type <code>strings</code>, you can add multiple values +by repeating the options in the configuration. For example, set +<code>binary-test-source</code> twice (as shown in the +<code>VtsDeviceTreeEarlyMountTest</code> example).</p> + +<h4>Test tags</h4> +<p>You can add test tags by prefixing them to options with <code>strings</code> +values and using <code>::</code> as the delimiter. Test tags are especially +useful when including binary sources with the same name but with different +bitness or parent directories. For example, to avoid file push or result name +collision for sources with the same name but from different source directories, +you can specify different tags for these sources.</p> + +<p>As shown in the <code>VtsDeviceTreeEarlyMountTest</code> example with the +two <code>dt_early_mount_test</code> sources, the test tags are the +<code>_32bit::</code> and <code>_64bit::</code> prefixes on +<code>binary-test-source</code>. Tags ending with <code>32bit</code> or +<code>64bit</code> automatically mark the tests as available to one ABI bitness; +i.e. tests with the tag <code>_32bit</code> are not executed on 64-bit ABI. Not +specifying a tag is equal to using a tag with an empty string.</p> + +<p>Options with the same tags are grouped and isolated from other tags. For +example, <code>binary-test-args</code> with the <code>_32bit</code> tag is +applied only to <code>binary-test-source</code> with the same tag and executed +in <code>binary-test-working-directory</code> with the same tag. The +<code>binary-test-working-directory</code> option is optional for binary tests, +allowing you to specify a single working directory for a tag. When the +<code>binary-test-working-directory</code> option is left unspecified, default +directories are used for each tag.</p> + +<p>The tag name is directly appended to test case name in the result report. +For example, test case <code>testcase1</code> with tag <code>_32bit</code> +appears as <code>testcase1_32bit</code> in the result report.</p> + +<h3 id="no-target-side">Integrating target-side tests without +BinaryTest template</h2> +<p>In VTS, the default test format is host-side Python tests extended from +BaseTest in VTS runner. To integrate target-side tests, you must first push the +test files to device, execute the tests using shell commands, then parse the +results using host-side Python scripts.</p> + +<h4>Pushing test binaries</h4> +<p>We recommend pushing files using <code>VtsFilePusher</code> target preparer. +Example:</p> + +<pre class="devsite-click-to-copy"> +<target_preparer class="com.android.compatibility.common.tradefed.targetprep.VtsFilePusher"> + <option name="push" value="DATA/test->/data/local/tmp/test"/> + </target_preparer> +</pre> + +<p>The <code>VtsFilePusher</code> does the following:</p> +<ol> +<li>Checks device connectivity.</li> +<li>Determines the absolute source file path.</li> +<li>Pushes the files using <code>adb push</code> command.</li> +<li>Deletes the files after tests complete.</li> +</ol> +<p>Alternatively, you can push files manually using a host-side Python test +script that follows a similar procedure.</p> + +<h4>Running tests</h4> +<p>After pushing files to the device, run the test using shell commands in a +host-side Python test script. Example:</p> + +<pre class="devsite-click-to-copy"> +device = self.android_devices[0] +res = device.shell.Execute(["chmod a+x /data/local/tmp/test", "/data/local/tmp/test"]) +asserts.AssertFalse(any(res[return_codes])) +</pre> + +<h2 id="gtestbinarytest">GtestBinaryTest template</h2> +<p>The +<a href="https://android.googlesource.com/platform/test/vts/+/sdk-release/testcases/template/gtest_binary_test/gtest_binary_test.py" class="external">GtestBinaryTest +template</a> hosts GTest test binaries, each of which usually contains +multiple test cases. This template extends the BinaryTest template by overriding +setup, test case creation, and result parsing methods, so all BinaryTest +configurations are inherited.</p> + +<p>GtestBinaryTest adds the option <code>gtest-batch-mode</code>:</p> + +<table> +<thead> +<tr> +<th>Option name</th> +<th>Value type</th> +<th>Description</th> +</tr> +</thead> +<tbody> +<tr> +<td>binary-test-type</td> +<td>string</td> +<td>Template type. Uses the value <code>gtest</code>.</td> +</tr> +<tr> +<td>gtest-batch-mode</td> +<td>boolean</td> +<td>Run Gtest binaries in batch mode. Example: <code>true</code></td> +</tr> +</tbody> +</table> + +<p>In general, setting <code>gtest-batch-mode</code> to <code>true</code> +increases performance while decreasing reliability slightly. In VTS compliance +tests, many modules use batch mode to improve performance. For reliability +however, if the mode is unspecified it defaults to non-batch. </p> + +<h3 id=non-batch-mode>Non-batch mode</h3> +<p>Non-batch mode makes individual calls to GTest binary for each test case. For +example, if the GTest binary contains 10 test cases (after filtering by host +side configuration), the binary is called 10 times on device shell each time +with a different test filter. For each test case, a unique GTest result output +XML is generated and parsed by the template.</p> + +<p><img src="images/vts_non_batch.png"></p> +<figcaption><strong>Figure 2.</strong> Non-batch mode.</figcaption> + +<p>The advantages of using non-batch mode include:</p> +<ul> +<li><strong>Test case isolation</strong>. A crash or hang in one test case +does not affect other test cases.</li> +<li><strong>Granularity</strong>. Easier to get per-test-case profiling/coverage +measurement, systrace, bugreport, logcat, etc. Test results and logs are +retrieved immediately after each test case finishes.</li> +</ul> + +<p>The disadvantages of using non-batch mode include:</p> +<ul> +<li><strong>Redundant loading</strong>. Each time GTest binary is called, +it loads related libraries and performs initial class setups.</li> +<li><strong>Communication overhead</strong>. After a test completes, the host +and target device communicate for result parsing and next commands (future +optimizations possible).</li> +</ul> + +<h3 id="batch-mode">Batch mode</h3> +<p>In GTest batch mode, the test binary is called only once with a long test +filter value containing all test cases filtered by host-side configuration (this +avoids the redundant loading issue in non-batch mode). You can parse test +results for GTest using output.xml or using terminal output.</p> + +<p>When using output.xml (default):</p> + +<p><img src="images/vts_batch_output_xml.png"></p> +<figcaption><strong>Figure 3.</strong> Batch mode, output.xml.</figcaption> + +<p>As in non-batch mode, the test result is parsed through GTest output xml +file. However, because the output xml is generated after all tests are +completed, if a test case crashed the binary or device no result xml file is +generated. + +<p>When using terminal output:</p> + +<p><img src="images/vts_batch_terminal_output.png"></p> +<figcaption><strong>Figure 4.</strong> Batch mode, terminal output.</figcaption> + +<p>While GTest is running, it prints the test log and progress to the terminal +in a format that can be parsed by the framework for test status, results, and +logs.</p> + +<p>The advantages of using batch mode include:</p> +<ul> +<li><strong>Test case isolation</strong>. Provides the same level of test +case isolation as non-batch mode if the framework restarts the binary/device +after a crash with a reduced test filter (excluding finished and crashed test +cases).</li> +<li><strong>Granularity</strong>. Provides the same test-case granularity as +non-batch mode.</li> +</ul> + +<p>The disadvantages of using batch mode include:</p> +<ul> +<li><strong>Maintenance cost</strong>. If the GTest logging format changes, +all tests will break.</li> +<li><strong>Confusion</strong>. A test case can print something similar to GTest +progress format, which can confuse the format.</li> +</ul> +<p>Because of these disadvantages, we have temporarily removed the option to use +command line output. We will revisit this option in the future to improve the +reliability of this function.</p> + +<h2 id="hostbinarytest">HostBinaryTest template</h2> +<p>The HostBinaryTest template includes host-side executables that do not exist +in other directories or in Python scripts. These tests include:</p> +<ul> +<li>Compiled test binaries executable on host</li> +<li>Executable scripts in shell, Python, or other languages</li> +</ul> +<p>One example is the +<a href="https://android.googlesource.com/platform/test/vts-testcase/security/+/master/selinux/policy/AndroidTest.xml" class="external">VTS +Security SELinux policy host-side test</a>:</p> + +<pre class="devsite-click-to-copy"> +<configuration description="Config for VTS Security SELinux policy host-side test cases"> + ... + <test class="com.android.tradefed.testtype.VtsMultiDeviceTest"> + <option name="test-module-name" value="VtsSecuritySelinuxPolicyHost"/> + <option name="binary-test-source" value="out/host/linux-x86/bin/VtsSecuritySelinuxPolicyHostTest" /> + <option name="binary-test-type" value="host_binary_test"/> + </test> +</configuration> +</pre> + +<p>HostBinaryTest does not extend the BinaryTest template but does use similar +test configurations. In the above example, the <code>binary-test-source</code> +option specifies a host-side relative path to the test executable, and +<code>binary-test-type</code> is <code>host_binary_test</code>. Similar to +BinaryTest template, the binary filename is used as the test case name by +default.</p> + +<h2 id="extending-existing-templates">Extending existing templates</h2> +<p>You can use templates directly in the test config to include non-Python tests +or extend them in a subclass to handle specific test requirements. Templates in +the VTS repo have the following extensions:</p> + +<p><img src="images/vts_template_extension.png"></p> +<figcaption><strong>Figure 5.</strong> Extending existing templates in the VTS +repo.</figcaption> + +<p>Developers are encouraged to extend any existing template for any specific +test requirements. Common reasons to extend templates include:</p> +<ul> +<li>Special test setup procedures, such as preparing a device with special +commands.</li> +<li>Generating different test cases and test names.</li> +<li>Parsing results by reading command output or using other conditions.</li> +</ul> +<p>To make it easier to extend existing templates, the templates contain methods +specialized for each functionality. If you have improved designs for existing +templates, we encourage you to contribute to the VTS code base.</p> + +</body> +</html>
\ No newline at end of file diff --git a/en/devices/architecture/dto/multiple.html b/en/devices/architecture/dto/multiple.html index 52f47a46..f431a9d7 100644 --- a/en/devices/architecture/dto/multiple.html +++ b/en/devices/architecture/dto/multiple.html @@ -43,12 +43,18 @@ DTs.</figcaption> <p>The bootloader should be able to:</p> <ul> -<li>read the SoC ID and select the main DT correspondingly, and</li> -<li>read the board ID and select the overlay DT accordingly.</li> +<li>Read the SoC ID and select the corresponding main device tree, and</li> +<li>Read the board ID and select the set of overlay device trees accordingly. +</li> </ul> -<p>Only one main DT and one overlay DT are selected for use at runtime, and the -selected pair must be compatible.</p> +<p>Only one main DT should be selected for use at runtime. Multiple overlay DTs +may be selected but they must be compatible with the chosen main DT. Using +multiple overlays can help avoid storing one overlay per board within the DTBO +partition and enable the bootloader to determine the subset of required overlays +based on the board ID (or possibly by probing the peripherals). For +example, Board A may need the devices added by the overlays 1, 3, and 5 while +Board B may need the devices added by the overlays 1, 4, and 5.</p> <h2 id=partition>Partitioning</h2> <p>To partition, determine a bootloader runtime-accessible and trusted location diff --git a/en/devices/architecture/hidl-cpp/index.html b/en/devices/architecture/hidl-cpp/index.html index 7d8466cb..28c4aa0a 100644 --- a/en/devices/architecture/hidl-cpp/index.html +++ b/en/devices/architecture/hidl-cpp/index.html @@ -117,7 +117,7 @@ a binderized service. Example daemon code (for pure binderized service):</p> <pre class="prettyprint"> int main(int /* argc */, char* /* argv */ []) { - Nfc nfc = new Nfc(); + sp<INfc> nfc = new Nfc(); const status_t status = nfc->registerAsService(); if (status != ::android::OK) { return 1; // or handle error diff --git a/en/devices/architecture/hidl-java/index.html b/en/devices/architecture/hidl-java/index.html index 3b94247e..c4218160 100644 --- a/en/devices/architecture/hidl-java/index.html +++ b/en/devices/architecture/hidl-java/index.html @@ -136,7 +136,7 @@ to run the service is:</p> import android.hardware.foo.V1_0.IFoo; import android.hardware.foo.V1_0.IFooCallback.Stub; .... -class FooCallback extends IFoo.Stub { +class FooCallback extends IFooCallback.Stub { // implement methods } .... diff --git a/en/devices/architecture/hidl/versioning.html b/en/devices/architecture/hidl/versioning.html index 13bce259..52552f0c 100644 --- a/en/devices/architecture/hidl/versioning.html +++ b/en/devices/architecture/hidl/versioning.html @@ -112,6 +112,54 @@ types from the older version of the package, and inheritance of a subset of old-package interfaces.</li> </ul> +<h2 id=structuring>Structuring interfaces</h2> + +<p>For a well structured interface, adding new types of functionality that +are not part of the original design should require a modification to the HIDL +interface. Conversely, if you can or expect to make a change on both sides of +the interface that introduces new functionality without changing the interface +itself, then the interface is not structured.</p> + +<p>Treble supports separately-compiled vendor and system components in which the +<code>vendor.img</code> on a device and the <code>system.img</code> can be +compiled separately. All interactions between <code>vendor.img</code> and +<code>system.img</code> must be explicitly and thoroughly defined so they can +continue to work for many years. This includes many API surfaces, but a major +surface is the IPC mechanism HIDL uses for interprocess communication on the +<code>system.img</code>/<code>vendor.img</code> boundary.</p> + +<h3 id="structuring-requirements">Requirements</h3> +<p>All data passed through HIDL must be explicitly defined. To ensure an +implementation and client can continue to work together even when compiled +separately or developed on independently, data must adhere to the following +requirements:</p> + +<ul> +<li>Can be described in HIDL directly (using structs enums, etc.) with +semantic names and meaning.</li> +<li>Can be described by a public standard such as ISO/IEC 7816.</li> +<li>Can be described by a hardware standard or physical layout of hardware.</li> +<li>Can be opaque data (such as public keys, ids, etc.) if necessary.</li> +</ul> + +<p>If opague data is used, it must be read only by one side of the HIDL +interface. For example, if <code>vendor.img</code> code gives a component on the +<code>system.img</code> a string message or <code>vec<uint8_t></code> +data, that data cannot be parsed by the <code>system.img</code> itself; it can +only be passed back to <code>vendor.img</code> to interpret. <strong>When +passing a value from <code>vendor.img</code> to vendor code on +<code>system.img</code> or to another device, the format of the data and how it +is to be interpreted must be exactly described and is still part of the +interface</strong>.</p> + +<h3 id="structuring-guidelines">Guidelines</h3> + +<p>You should be able to write an implementation or client of a HAL using only +the .hal files (i.e. you should not need to look at the Android source or public +standards). We recommend specifying the exact required behavior. Statements such +as "an implementation may do A or B" encourage implementations to become +intertwined with the clients they are developed with.</p> + <h2 id=code-layout>HIDL code layout</h2> <p>HIDL includes core and vendor packages.</p> diff --git a/en/devices/tech/config/filesystem.html b/en/devices/tech/config/filesystem.html index 10b7f0b4..73633943 100644 --- a/en/devices/tech/config/filesystem.html +++ b/en/devices/tech/config/filesystem.html @@ -244,7 +244,8 @@ the autogenerated header file by adding to your module's <code>Android.mk</code> and including the empty faux library. For example, in <code>Android.mk</code>, add the following:</p> -<pre class="prettyprint"> LOCAL_STATIC_LIBRARIES := liboemaids</pre> +<pre class="prettyprint">LOCAL_HEADER_LIBRARIES := oemaids_headers</pre> + <p>In your C code, <code>#include "generated_oem_aid.h"</code> and start using the declared identifiers. For example, in <code>my_file.c</code>, add the following: </p> diff --git a/en/devices/tech/config/namespaces_libraries.html b/en/devices/tech/config/namespaces_libraries.html index b91cbe23..1e94bf1b 100644 --- a/en/devices/tech/config/namespaces_libraries.html +++ b/en/devices/tech/config/namespaces_libraries.html @@ -61,6 +61,26 @@ additional native libraries accessible to apps by putting them under the <code>/vendor/etc/public.libraries.txt</code> </p> +<p> +Starting from Android 8.0, vendor public libraries have the following additional +restrictions and required setups: +</p> + +<ol> + <li>The native library in vendor must be properly labeled so it can be + accessible to apps. If access is required by any apps (including third + party apps), the library must be labeled as <code>same_process_hal_file</code> + in a vendor-specific <code>file_contexts</code> file as follows: + <pre class="devsite-click-to-copy">/vendor/lib(64)?/libnative.so u:object_r:same_process_hal_file:s0</pre> + where <code>libnative.so</code> is the name of the native library. + </li> + <li>The library, either directly or transitively via its dependencies, must not + depend on system libraries other than VNDK-SP and LLNDK libraries. The list of + VNDK-SP and LLNDK libraries can be found at + <code>development/vndk/tools/definition/tool/datasets/eligible-list-<version>-release.csv</code>. + </li> +</ol> + <h2 id="updating-app-non-public">Updating apps to not use non-public native libraries</h2> <p> diff --git a/en/devices/tech/config/perms-whitelist.html b/en/devices/tech/config/perms-whitelist.html index c3de0de0..918f89eb 100644 --- a/en/devices/tech/config/perms-whitelist.html +++ b/en/devices/tech/config/perms-whitelist.html @@ -135,7 +135,7 @@ transitional log-mode: </p> -<pre class="devsite-click-to-copy">ro.control_privapp_permission=log</pre> +<pre class="devsite-click-to-copy">ro.control_privapp_permissions=log</pre> <p> Violations are reported in the log file, but permissions are still granted. @@ -158,11 +158,11 @@ PackageManager: Privileged permission {PERMISSION_NAME} for package {PACKAGE_NAM <p> After whitelists are in place, enable runtime enforcement by setting the build - property <code>ro.control_privapp_permission=enforce</code>. + property <code>ro.control_privapp_permissions=enforce</code>. </p> <aside class="note"><strong>Note:</strong> The - <code>ro.control_privapp_permission</code> property state must adhere to + <code>ro.control_privapp_permissions</code> property state must adhere to <a href="/compatibility/android-cdd#9_1_permissions">CDD section 9.1 requirements</a>.</aside> diff --git a/en/devices/tech/config/uicc.html b/en/devices/tech/config/uicc.html index 1fa6952c..96c1d360 100644 --- a/en/devices/tech/config/uicc.html +++ b/en/devices/tech/config/uicc.html @@ -29,7 +29,7 @@ Android platform loads certificates stored on a UICC and grants permission to apps signed by these certificates to make calls to a handful of special APIs. </p> <p>Android 7.0 extends this feature to support other storage sources, such as -Access File Rule (ARF), for UICC carrier privilege rules, dramatically +Access Rule File (ARF), for UICC carrier privilege rules, dramatically increasing the number of carriers that can use the APIs. For an API reference, see <a href="#carrierconfigmanager">CarrierConfigManager</a>; for instructions, see <a href="/devices/tech/config/carrier.html">Carrier diff --git a/en/devices/tech/ota/ab/index.html b/en/devices/tech/ota/ab/index.html index 48a9fea5..c2a9c447 100644 --- a/en/devices/tech/ota/ab/index.html +++ b/en/devices/tech/ota/ab/index.html @@ -31,6 +31,9 @@ updates successfully. </p> + <p>For more information about A/B system updates and how they work, see + <a href="#slots">Partition selection (slots)</a>. + <p>A/B system updates provide the following benefits:</p> <ul> diff --git a/en/devices/tech/ota/index.html b/en/devices/tech/ota/index.html index 1565e3b2..7b2f0dd0 100644 --- a/en/devices/tech/ota/index.html +++ b/en/devices/tech/ota/index.html @@ -35,7 +35,7 @@ applications installed by the user from Google Play. </p> - <h2 id="ab_updates">A/B updates</h2> + <h2 id="ab_updates">A/B (seamless) system updates</h2> <p> Modern A/B devices have two copies of each partition, A and B. Devices @@ -50,7 +50,7 @@ </a>. </p> - <h2 id="nonab_updates">Non-A/B updates</h2> + <h2 id="nonab_updates">Non-A/B system updates</h2> <p> Older devices have a special recovery partition containing the software diff --git a/en/devices/tech/perf/boot-times.html b/en/devices/tech/perf/boot-times.html index a7588301..fb6ad441 100644 --- a/en/devices/tech/perf/boot-times.html +++ b/en/devices/tech/perf/boot-times.html @@ -255,17 +255,27 @@ us uncover many meaningful bugs in some Android device drivers). Many processes launch during boot, but only components in critical path (bootloader > kernel > init > file system mount > zygote > system server) directly affect boot time. Profile <strong>initcall</strong> during kernel -booting to identify peripheral/components that are not critical to the -start init process, then delay those peripherals/components until later -in the boot process. +booting to identify peripheral/components that are slow and not critical +to start init process, then delay those peripherals/components until later +in the boot process by moving into loadable kernel modules. Moving to +asynchronous device/driver probe can also help to parallel slow components +in kernel > init critical path. </p> <pre class="prettyprint"> BoardConfig-common.mk: BOARD_KERNEL_CMDLINE += initcall_debug ignore_loglevel + +driver: + .probe_type = PROBE_PREFER_ASYNCHRONOUS, </pre> +<p class="note"> +<strong>Note:</strong> Driver dependencies must be resolved carefully by adding +<code>EPROBEDEFER</code> support. +</p> + <h2 id="optimizing-i-o-efficiency">Optimizing I/O efficiency</h2> <p> @@ -422,6 +432,12 @@ early stage init should be deferred to boot completed.</li></ul> </li> </ul> +<p class="note"> +<strong>Note:</strong> Property service is part of init process, so calling +<code>setproperty</code> during boot can lead a long delay if init is busy in +builtin commands. +</p> + <h3 id="using-scheduler-tuning">Using scheduler tuning</h3> <p> diff --git a/en/security/_toc.yaml b/en/security/_toc.yaml index b24dd01b..ae1f236f 100644 --- a/en/security/_toc.yaml +++ b/en/security/_toc.yaml @@ -47,6 +47,8 @@ toc: section: - title: 2018 Bulletins section: + - title: April + path: /security/bulletin/2018-04-01 - title: March path: /security/bulletin/2018-03-01 - title: February @@ -131,6 +133,8 @@ toc: path: /security/bulletin/pixel/index - title: 2018 Bulletins section: + - title: April + path: /security/bulletin/pixel/2018-04-01 - title: March path: /security/bulletin/pixel/2018-03-01 - title: February diff --git a/en/security/bulletin/2018-02-01.html b/en/security/bulletin/2018-02-01.html index 972ff4d2..8fff7409 100644 --- a/en/security/bulletin/2018-02-01.html +++ b/en/security/bulletin/2018-02-01.html @@ -20,7 +20,7 @@ See the License for the specific language governing permissions and limitations under the License. --> - <p><em>Published February 5, 2018 | Updated February 14, 2018</em></p> + <p><em>Published February 5, 2018 | Updated April 2, 2018</em></p> <p> @@ -352,16 +352,6 @@ a privileged process.</p> <th>Component</th> </tr> <tr> - <td>CVE-2017-15817</td> - <td>A-68992394<br /> - <a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/prima/commit/?id=8ba78e506e5002cdae525dd544dbf1df0ccce1ef"> -QC-CR#2076603</a> - [<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/prima/commit/?id=fe43c2b64ac81199de17efc258e95546cb0546f1">2</a>]</td> - <td>RCE</td> - <td>Critical</td> - <td>WLan</td> - </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"> @@ -650,5 +640,10 @@ security bulletins. <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> diff --git a/en/security/bulletin/2018-04-01.html b/en/security/bulletin/2018-04-01.html new file mode 100644 index 00000000..21bb5aa5 --- /dev/null +++ b/en/security/bulletin/2018-04-01.html @@ -0,0 +1,2700 @@ +<html devsite> + <head> + <title>Android Security Bulletin—April 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 April 2, 2018 | Updated April 4, 2018</em></p> + +<p> +The Android Security Bulletin contains details of security vulnerabilities +affecting Android devices. Security patch levels of 2018-04-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-04-01.html">April 2018 +Pixel / Nexus Security Bulletin</a>. +</p> + +<h2 id="announcements">Announcements</h2> +<p>We would like to thank Qualcomm for their dedicated efforts to improve the +security of mobile devices. The 2018-04-05 SPL includes a cumulative list of +addressed security issues taken from Qualcomm’s 2014–2016 partner focused +bulletins, and is a reflection of their continued effort and commitment.</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-04-01-details">2018-04-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-04-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="android-runtime">Android runtime</h3> +<p>The most severe vulnerability in this section could enable a remote attacker +to bypass user interaction requirements in order to gain access to additional +permissions.</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-13274</td> + <td><a href="https://android.googlesource.com/platform/frameworks/base/+/0b57631939f5824afef06517df723d2e766e0159">A-71360761</a></td> + <td>EoP</td> + <td>High</td> + <td>6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + </tr> +</table> + + +<h3 id="framework">Framework</h3> +<p>The most severe vulnerability in this section could enable a local malicious +application to bypass operating system protections that isolate application +data from other applications.</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-13275</td> + <td><a href="https://android.googlesource.com/platform/frameworks/minikin/+/3056f04d293bd16e56cc72e10edd060b8c1ca0f5">A-70808908</a></td> + <td>ID</td> + <td>High</td> + <td>8.0, 8.1</td> + </tr> +</table> + + +<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-13276</td> + <td><a href="https://android.googlesource.com/platform/external/aac/+/1b9cbed05b4fd376677d67b6442aa30256834ed4">A-70637599</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-13277</td> + <td><a href="https://android.googlesource.com/platform/external/libhevc/+/b7d4d588e8fcbe254f7a3d9a247af4b91ccc7285">A-72165027</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-13278</td> + <td><a href="https://android.googlesource.com/platform/frameworks/av/+/8a54af87b632c03ff2ae15a4a088801bb39fdae7">A-70546581</a></td> + <td>EoP</td> + <td>High</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-13279</td> + <td><a href="https://android.googlesource.com/platform/frameworks/av/+/d32af5db10f018219e0379f333c7f0452a4f7a31">A-68399439</a></td> + <td>DoS</td> + <td>High</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-13280</td> + <td><a href="https://android.googlesource.com/platform/frameworks/ex/+/ebd849ed8aa77c0e1dad7a08df4a55845a067b76">A-71361451</a></td> + <td>DoS</td> + <td>High</td> + <td>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 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-13281</td> + <td><a href="https://android.googlesource.com/platform/system/bt/+/6f3ddf3f5cf2b3eb52fb0adabd814a45cff07221">A-71603262</a></td> + <td>RCE</td> + <td>Critical</td> + <td>8.0, 8.1</td> + </tr> + <tr> + <td>CVE-2017-13282</td> + <td><a href="https://android.googlesource.com/platform/system/bt/+/6ecbbc093f4383e90cbbf681cd55da1303a8ef94">A-71603315</a></td> + <td>RCE</td> + <td>Critical</td> + <td>7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + </tr> + <tr> + <td>CVE-2017-13283</td> + <td><a href="https://android.googlesource.com/platform/system/bt/+/e4ec79be45304f819c88c8dbf826d58b68f6c8f8">A-71603410</a></td> + <td>RCE</td> + <td>Critical</td> + <td>7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + </tr> + <tr> + <td>CVE-2017-13267</td> + <td><a href="https://android.googlesource.com/platform/system/bt/+/57dc5964428697a104988f0aa0d1fd1d88fec939">A-69479009</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-13284</td> + <td><a href="https://android.googlesource.com/platform/system/bt/+/7f8bfcc35285ca6e93a4436699bc95c13b920caf">A-70808273</a></td> + <td>EoP</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-13285</td> + <td><a href="https://android.googlesource.com/platform/external/svox/+/cee78199bbfae81f54a40671db47096f5f32cdad">A-69177126</a></td> + <td>RCE</td> + <td>High</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-13286</td> + <td><a href="https://android.googlesource.com/platform/frameworks/base/+/47ebfaa2196aaf4fbeeec34f1a1c5be415cf041b">A-69683251</a></td> + <td>EoP</td> + <td>High</td> + <td>8.0, 8.1</td> + </tr> + <tr> + <td>CVE-2017-13287</td> + <td><a href="https://android.googlesource.com/platform/frameworks/base/+/09ba8fdffd9c8d74fdc6bfb51bcebc27fc43884a">A-71714464</a></td> + <td>EoP</td> + <td>High</td> + <td>6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + </tr> + <tr> + <td>CVE-2017-13288</td> + <td><a href="https://android.googlesource.com/platform/frameworks/base/+/b796cd32a45bcc0763c50cc1a0cc8236153dcea3">A-69634768</a></td> + <td>EoP</td> + <td>High</td> + <td>8.0, 8.1</td> + </tr> + <tr> + <td>CVE-2017-13289</td> + <td><a href="https://android.googlesource.com/platform/frameworks/base/+/5a3d2708cd2289a4882927c0e2cb0d3c21a99c02">A-70398564</a></td> + <td>EoP</td> + <td>High</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-13290</td> + <td><a href="https://android.googlesource.com/platform/system/bt/+/72b1cebaa9cc7ace841d887f0d4a4bf6daccde6e">A-69384124</a></td> + <td>ID</td> + <td>High</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-13291</td> + <td><a href="https://android.googlesource.com/platform/system/bt/+/1696f97011f5f30f1a630f3b24442ca64232b1f5">A-71603553</a></td> + <td>DoS</td> + <td>High</td> + <td>7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + </tr> +</table> + +<h2 id="2018-04-05-details">2018-04-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-04-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.</p> + +<p>When multiple changes relate to a single bug, additional references are +linked to numbers following the bug ID.</p> + +<h3 id="broadcom-components">Broadcom components</h3> +<p>The most severe vulnerability in this section could enable a proximate +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-13292</td> + <td>A-70722061<a href="#asterisk">*</a><br /> + B-V2018010201</td> + <td>RCE</td> + <td>Critical</td> + <td>bcmdhd driver</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-13293</td> + <td>A-62679701<a href="#asterisk">*</a></td> + <td>EoP</td> + <td>High</td> + <td>NFC driver</td> + </tr> + <tr> + <td>CVE-2017-5754</td> + <td>A-69856074<a href="#asterisk">*</a></td> + <td>ID</td> + <td>High</td> + <td>Memory mapping</td> + </tr> + <tr> + <td>CVE-2017-16534</td> + <td>A-69052594<br /> + <a href="https://github.com/torvalds/linux/commit/2e1c42391ff2556387b3cb6308b24f6f65619feb"> +Upstream kernel</a></td> + <td>ID</td> + <td>High</td> + <td>USB</td> + </tr> +</table> + + +<h3 id="qualcomm-components">Qualcomm components</h3> +<p>The most severe vulnerability in this section could enable a proximate +attacker using a specially crafted file to execute arbitrary code within the +context of a privileged process.</p> + +<table> + <col width="17%"> + <col width="21%"> + <col width="9%"> + <col width="14%"> + <col width="37%"> + <tr> + <th>CVE</th> + <th>References</th> + <th>Type</th> + <th>Severity</th> + <th>Component</th> + </tr> + <tr> + <td>CVE-2017-15822</td> + <td>A-71501534<br /> + <a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=dba4c106922d637ff5965b023b451f6273348eb6"> +QC-CR#2123807</a></td> + <td>RCE</td> + <td>Critical</td> + <td>WiFi</td> + </tr> + <tr> + <td>CVE-2017-17770</td> + <td>A-70237684<br /> + <a href="https://source.codeaurora.org/quic/la/kernel/msm-3.18/commit/?id=284f963af0accf7f921ec10e23acafd71c3a724b">QC-CR#2103199</a> + [<a href="https://source.codeaurora.org/quic/la/kernel/msm-4.4/commit/?id=3b0c1463e4a6b37d4413a4ba02f1727eeb8693be">2</a>]</td> + <td>EoP</td> + <td>High</td> + <td>Binder</td> + </tr> + <tr> + <td>CVE-2018-3566</td> + <td>A-72957177<br /> + <a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-2.0/commit/?id=11868230d4fe79f76eae30c742b4c68c2899caea"> +QC-CR#2143847</a></td> + <td>EoP</td> + <td>High</td> + <td>WLAN</td> + </tr> + <tr> + <td>CVE-2018-3563</td> + <td>A-72956842<br /> + <a href="https://source.codeaurora.org/quic/la/kernel/msm-4.4/commit/?id=c643a15d73b3fb6329b002662e72dfa96acfdb8a">QC-CR#2143207</a> + [<a href="https://source.codeaurora.org/quic/la/kernel/msm-3.18/commit/?id=0b8320cd49255177f0c0c8589708e983116ac420">2</a>] + [<a href="https://source.codeaurora.org/quic/la/platform/vendor/opensource/audio-kernel/commit/?id=d5231fa166521a32621c32fb749b80fc37c13c6a">3</a>]</td> + <td>EoP</td> + <td>High</td> + <td>Audio Driver</td> + </tr> + <tr> + <td>CVE-2017-13077</td> + <td>A-72957017<br /> + <a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=776f17c87599fae3202e69bb5718ac9062f14695"> +QC-CR#2129237</a></td> + <td>ID</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-18071</td> + <td>A-68326813<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>Critical</td> + <td>Closed-source component +</td> + </tr> + <tr> + <td>CVE-2017-8274</td> + <td>A-68141335<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>Critical</td> + <td>Closed-source component +</td> + </tr> + <tr> + <td>CVE-2017-18146</td> + <td>A-70221449<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>Critical</td> + <td>Closed-source component +</td> + </tr> + <tr> + <td>CVE-2017-18128</td> + <td>A-70221448<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>Critical</td> + <td>Closed-source component +</td> + </tr> + <tr> + <td>CVE-2018-3592</td> + <td>A-71501105<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>Critical</td> + <td>Closed-source component +</td> + </tr> + <tr> + <td>CVE-2018-3591</td> + <td>A-71501103<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>Critical</td> + <td>Closed-source component +</td> + </tr> + <tr> + <td>CVE-2017-18074</td> + <td>A-68326816<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component +</td> + </tr> + <tr> + <td>CVE-2017-18073</td> + <td>A-68326820<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component +</td> + </tr> + <tr> + <td>CVE-2017-18125</td> + <td>A-68326821<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component +</td> + </tr> + <tr> + <td>CVE-2017-8275</td> + <td>A-68141336<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component +</td> + </tr> + <tr> + <td>CVE-2017-11011</td> + <td>A-68326823<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component +</td> + </tr> + <tr> + <td>CVE-2017-18137</td> + <td>A-67712318<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component +</td> + </tr> + <tr> + <td>CVE-2017-18134</td> + <td>A-67712320<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component +</td> + </tr> + <tr> + <td>CVE-2017-18136</td> + <td>A-68989810<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component +</td> + </tr> + <tr> + <td>CVE-2017-18140</td> + <td>A-68989811<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component +</td> + </tr> + <tr> + <td>CVE-2017-18135</td> + <td>A-68989813<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component +</td> + </tr> + <tr> + <td>CVE-2017-18142</td> + <td>A-68989814<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component +</td> + </tr> + <tr> + <td>CVE-2017-18138</td> + <td>A-68989815<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component +</td> + </tr> + <tr> + <td>CVE-2017-18139</td> + <td>A-68989819<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component +</td> + </tr> + <tr> + <td>CVE-2017-18129</td> + <td>A-68989822<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component +</td> + </tr> + <tr> + <td>CVE-2017-18132</td> + <td>A-68989825<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component +</td> + </tr> + <tr> + <td>CVE-2017-18133</td> + <td>A-68989826<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component +</td> + </tr> + <tr> + <td>CVE-2017-18072</td> + <td>A-68989828<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component +</td> + </tr> + <tr> + <td>CVE-2017-18126</td> + <td>A-68989829<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component +</td> + </tr> + <tr> + <td>CVE-2017-18144</td> + <td>A-70221450<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component +</td> + </tr> + <tr> + <td>CVE-2017-18145</td> + <td>A-70221453<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component +</td> + </tr> + <tr> + <td>CVE-2017-18147</td> + <td>A-70221456<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component +</td> + </tr> + <tr> + <td>CVE-2017-18130</td> + <td>A-70221460<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component +</td> + </tr> + <tr> + <td>CVE-2017-18143</td> + <td>A-70221461<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component +</td> + </tr> + <tr> + <td>CVE-2017-18127</td> + <td>A-70221462<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component +</td> + </tr> + <tr> + <td>CVE-2018-3590</td> + <td>A-71501106<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2018-3593</td> + <td>A-71501107<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2018-3589</td> + <td>A-71501108<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2018-3594</td> + <td>A-71501112<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> +</table> + +<h3 id="qualcomm-closed-source-components-2014-2016-cumulative-update">Qualcomm +closed-source components 2014-2016 cumulative update</h3> +<p>These vulnerabilities affect Qualcomm components and were shared by Qualcomm +with their partners through Qualcomm AMSS security bulletins or security alerts +between 2014 and 2016. They are included in this Android security bulletin in +order to associate them with a security patch level (many Android devices may +have already addressed these issues in prior updates). 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-2014-9996</td> + <td>A-37535090<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>Critical</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2014-9971</td> + <td>A-37546253<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2014-9972</td> + <td>A-37546853<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2014-10063</td> + <td>A-37534948<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2014-10057</td> + <td>A-62261099<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2014-10059</td> + <td>A-62260706<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2014-10053</td> + <td>A-37544066<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2014-10054</td> + <td>A-62261100<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2014-10052</td> + <td>A-62258372<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2014-10050</td> + <td>A-37546901<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2014-10055</td> + <td>A-37545605<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2014-10051</td> + <td>A-37546302<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2014-10048</td> + <td>A-62258088<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2014-10062</td> + <td>A-62258373<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2014-10058</td> + <td>A-62260741<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2014-10047</td> + <td>A-37538492<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2014-10045</td> + <td>A-62258536<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2014-10056</td> + <td>A-62261338<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2014-9976</td> + <td>A-37534895<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2014-10043</td> + <td>A-62259947<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2014-10044</td> + <td>A-62260777<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2014-10046</td> + <td>A-62261408<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2014-9981</td> + <td>A-37534949<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2014-9993</td> + <td>A-37540928<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2014-9986</td> + <td>A-37534645<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2014-9994</td> + <td>A-37538493<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2014-9995</td> + <td>A-37546303<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2014-9997</td> + <td>A-37546854<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2014-9988</td> + <td>A-62258089<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2014-9990</td> + <td>A-62261216<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2014-9987</td> + <td>A-62261293<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2014-9989</td> + <td>A-62261380<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2014-9991</td> + <td>A-62261409<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2014-10039</td> + <td>A-62261608<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2014-9985</td> + <td>A-62261609<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9204</td> + <td>A-37540929<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-0574</td> + <td>A-37546304<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9205</td> + <td>A-37534696<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9221</td> + <td>A-37534796<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9212</td> + <td>A-37535795<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9210</td> + <td>A-62258538<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9211</td> + <td>A-62261217<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9207</td> + <td>A-62261410<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9202</td> + <td>A-37540473<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9213</td> + <td>A-37547700<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9209</td> + <td>A-38193247<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9203</td> + <td>A-62261218<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9206</td> + <td>A-62261294<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9215</td> + <td>A-62251854<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9216</td> + <td>A-62260780<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9169</td> + <td>A-37535098<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9173</td> + <td>A-37536244<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9179</td> + <td>A-37542567<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9177</td> + <td>A-37544075<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9187</td> + <td>A-37544109<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9162</td> + <td>A-37544110<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9172</td> + <td>A-37545607<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9181</td> + <td>A-37546754<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9219</td> + <td>A-37546859<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9183</td> + <td>A-37546860<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9182</td> + <td>A-37546904<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9185</td> + <td>A-37546952<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9184</td> + <td>A-37546953<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9170</td> + <td>A-37546954<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9175</td> + <td>A-37547404<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9171</td> + <td>A-37547405<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9192</td> + <td>A-37547750<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9208</td> + <td>A-62258540<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9224</td> + <td>A-62259949<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9201</td> + <td>A-62260711<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9200</td> + <td>A-62260779<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9198</td> + <td>A-62261219<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9196</td> + <td>A-62261339<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9199</td> + <td>A-62261411<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9174</td> + <td>A-62258090<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9178</td> + <td>A-62258541<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9180</td> + <td>A-62260712<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9176</td> + <td>A-62260713<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9189</td> + <td>A-62260820<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9188</td> + <td>A-62260821<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-0576</td> + <td>A-37543715<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9156</td> + <td>A-62260743<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9195</td> + <td>A-62251855<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9197</td> + <td>A-62260742<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9218</td> + <td>A-62260781<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9217</td> + <td>A-62261295<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9166</td> + <td>A-62251856<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9164</td> + <td>A-62258542<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9190</td> + <td>A-62259744<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9159</td> + <td>A-62259745<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9167</td> + <td>A-62259950<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9191</td> + <td>A-62260394<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9161</td> + <td>A-62260462<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9163</td> + <td>A-62260822<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9158</td> + <td>A-62261381<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9152</td> + <td>A-37546305<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9144</td> + <td>A-37540474<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9165</td> + <td>A-37539224<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9223</td> + <td>A-37543718<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9222</td> + <td>A-62258374<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9193</td> + <td>A-62259951<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9194</td> + <td>A-62261296<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9153</td> + <td>A-62260395<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9151</td> + <td>A-62260396<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9148</td> + <td>A-62260463<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9149</td> + <td>A-62260744<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9146</td> + <td>A-62260745<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9186</td> + <td>A-62261340<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9150</td> + <td>A-62261341<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9147</td> + <td>A-62261488<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-8593</td> + <td>A-37535091<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9160</td> + <td>A-37546254<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-8594</td> + <td>A-37546855<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9145</td> + <td>A-37535099<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9143</td> + <td>A-62260900<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9157</td> + <td>A-62260934<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9141</td> + <td>A-62261297<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9140</td> + <td>A-62259746<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9135</td> + <td>A-37546950<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9138</td> + <td>A-62259952<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9136</td> + <td>A-62260823<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9137</td> + <td>A-62260975<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9131</td> + <td>A-37542272<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9139</td> + <td>A-62251857<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9130</td> + <td>A-62252820<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9129</td> + <td>A-62260397<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9133</td> + <td>A-62260464<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9127</td> + <td>A-62260824<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9132</td> + <td>A-62260976<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9134</td> + <td>A-62261382<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9128</td> + <td>A-62261610<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9065</td> + <td>A-37538494<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9064</td> + <td>A-37546801<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9063</td> + <td>A-37546802<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9126</td> + <td>A-62258375<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9124</td> + <td>A-62252821<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9142</td> + <td>A-62260901<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9066</td> + <td>A-37540467<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2014-9998</td> + <td>A-62260398<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9220</td> + <td>A-62261299<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9122</td> + <td>A-62261611<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9123</td> + <td>A-62259953<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9118</td> + <td>A-62261220<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9120</td> + <td>A-62261298<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9119</td> + <td>A-62261489<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9116</td> + <td>A-37540934<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9115</td> + <td>A-37544076<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9113</td> + <td>A-37544077<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9112</td> + <td>A-62258091<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9114</td> + <td>A-62259954<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9111</td> + <td>A-62260465<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9108</td> + <td>A-62260714<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9109</td> + <td>A-62260977<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2015-9110</td> + <td>A-62261383<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10492</td> + <td>A-62261300<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10482</td> + <td>A-62260978<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10483</td> + <td>A-62258092<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10489</td> + <td>A-62258093<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10487</td> + <td>A-62259955<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10477</td> + <td>A-62260399<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10485</td> + <td>A-62260902<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10478</td> + <td>A-62260979<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10476</td> + <td>A-62260980<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10475</td> + <td>A-62260981<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10474</td> + <td>A-62260982<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10494</td> + <td>A-62261102<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10484</td> + <td>A-62261342<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10491</td> + <td>A-62261490<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10486</td> + <td>A-62267788<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10472</td> + <td>A-62259956<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10490</td> + <td>A-62260468<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10480</td> + <td>A-62261301<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10467</td> + <td>A-37526814<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10495</td> + <td>A-62261103<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10481</td> + <td>A-62260401<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10479</td> + <td>A-62261412<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10384</td> + <td>A-37536238<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10385</td> + <td>A-37544067<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10452</td> + <td>A-37523164<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10423</td> + <td>A-37534896<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10424</td> + <td>A-37540034<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10449</td> + <td>A-37546861<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10454</td> + <td>A-37544078<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10450</td> + <td>A-62260825<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10451</td> + <td>A-62267789<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10386</td> + <td>A-37534646<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10469</td> + <td>A-37542273<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10440</td> + <td>A-37535092<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10499</td> + <td>A-62259957<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10446</td> + <td>A-37547406<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10473</td> + <td>A-62260746<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10466</td> + <td>A-62260783<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10457</td> + <td>A-62260826<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10442</td> + <td>A-62267790<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10433</td> + <td>A-37540468<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10430</td> + <td>A-37540930<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10445</td> + <td>A-37545608<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10426</td> + <td>A-62252822<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10435</td> + <td>A-62260402<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10425</td> + <td>A-62260983<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10438</td> + <td>A-62261302<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10436</td> + <td>A-62261494<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10439</td> + <td>A-62263656<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10431</td> + <td>A-37540931<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10434</td> + <td>A-37540932<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10432</td> + <td>A-37546902<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10462</td> + <td>A-37539225<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10443</td> + <td>A-37540475<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10427</td> + <td>A-62261495<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10387</td> + <td>A-32583751<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10390</td> + <td>A-37536239<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10498</td> + <td>A-32582870<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10419</td> + <td>A-32577129<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10420</td> + <td>A-32579916<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10429</td> + <td>A-32579411<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10493</td> + <td>A-32574787<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10447</td> + <td>A-37542968<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10444</td> + <td>A-37544163<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-5348</td> + <td>A-37546905<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10421</td> + <td>A-32579095<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10455</td> + <td>A-32580964<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10441</td> + <td>A-32582927<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10418</td> + <td>A-37547407<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10417</td> + <td>A-32576287<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10464</td> + <td>A-32580243<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10458</td> + <td>A-32583424<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10471</td> + <td>A-37539226<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10416</td> + <td>A-62259747<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10411</td> + <td>A-62260404<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10496</td> + <td>A-62260469<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10410</td> + <td>A-62260936<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10414</td> + <td>A-62260937<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10461</td> + <td>A-62263657<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10460</td> + <td>A-62271227<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10392</td> + <td>A-37544068<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10409</td> + <td>A-37544164<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10459</td> + <td>A-62260716<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10407</td> + <td>A-62261222<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10406</td> + <td>A-62267791<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10497</td> + <td>A-62271228<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10501</td> + <td>A-62261303<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10381</td> + <td>A-37539788<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>Moderate</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10380</td> + <td>A-37541976<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>Moderate</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10412</td> + <td>A-37536245<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>Moderate</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10415</td> + <td>A-62260403<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>Moderate</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10422</td> + <td>A-37542966<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>Moderate</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10456</td> + <td>A-62261413<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>Moderate</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10428</td> + <td>A-37534697<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>Moderate</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10448</td> + <td>A-62261414<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>Moderate</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-10437</td> + <td>A-62260715<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>Moderate</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-04-01 or later address all issues associated +with the 2018-04-01 security patch level.</li> +<li>Security patch levels of 2018-04-05 or later address all issues associated +with the 2018-04-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-04-01]</li> +<li>[ro.build.version.security_patch]:[2018-04-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-04-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-04-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 / 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>April 2, 2018</td> + <td>Bulletin published.</td> + </tr> + <tr> + <td>1.1</td> + <td>April 4, 2018</td> + <td>Bulletin revised to include AOSP links.</td> + </tr> +</table> +</body></html> diff --git a/en/security/bulletin/2018.html b/en/security/bulletin/2018.html index 0df103d8..58c206cc 100644 --- a/en/security/bulletin/2018.html +++ b/en/security/bulletin/2018.html @@ -37,6 +37,21 @@ of all bulletins, see the <a href="/security/bulletin/index.html">Android Securi <th>Security patch level</th> </tr> <tr> + <td><a href="/security/bulletin/2018-04-01.html">April 2018</a></td> + <td>Coming soon + <!-- + <a href="/security/bulletin/2018-04-01.html">English</a> / + <a href="/security/bulletin/2018-04-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2018-04-01.html?hl=ko">í•œêµì–´</a> / + <a href="/security/bulletin/2018-04-01.html?hl=ru">руÌÑÑкий</a> / + <a href="/security/bulletin/2018-04-01.html?hl=zh-cn">ä¸æ–‡ (ä¸å›½)</a> / + <a href="/security/bulletin/2018-04-01.html?hl=zh-tw">ä¸æ–‡ (å°ç£)</a> + --> + </td> + <td>April 2, 2018</td> + <td>2018-04-05</td> + </tr> + <tr> <td><a href="/security/bulletin/2018-03-01.html">March 2018</a></td> <td>Coming soon <!-- diff --git a/en/security/bulletin/index.html b/en/security/bulletin/index.html index 4cbf4c3b..b4bac017 100644 --- a/en/security/bulletin/index.html +++ b/en/security/bulletin/index.html @@ -68,6 +68,21 @@ Android Open Source Project (AOSP), the upstream Linux kernel, and system-on-chi <th>Security patch level</th> </tr> <tr> + <td><a href="/security/bulletin/2018-04-01.html">April 2018</a></td> + <td>Coming soon + <!-- + <a href="/security/bulletin/2018-04-01.html">English</a> / + <a href="/security/bulletin/2018-04-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2018-04-01.html?hl=ko">í•œêµì–´</a> / + <a href="/security/bulletin/2018-04-01.html?hl=ru">руÌÑÑкий</a> / + <a href="/security/bulletin/2018-04-01.html?hl=zh-cn">ä¸æ–‡ (ä¸å›½)</a> / + <a href="/security/bulletin/2018-04-01.html?hl=zh-tw">ä¸æ–‡ (å°ç£)</a> + --> + </td> + <td>April 2, 2018</td> + <td>2018-04-05</td> + </tr> + <tr> <td><a href="/security/bulletin/2018-03-01.html">March 2018</a></td> <td>Coming soon <!-- diff --git a/en/security/bulletin/pixel/2018-02-01.html b/en/security/bulletin/pixel/2018-02-01.html index 6ebbbb9e..c8bcb259 100644 --- a/en/security/bulletin/pixel/2018-02-01.html +++ b/en/security/bulletin/pixel/2018-02-01.html @@ -22,7 +22,7 @@ --> -<p><em>Published February 5, 2018 | Updated February 7, 2018</em></p> +<p><em>Published February 5, 2018 | Updated April 2, 2018</em></p> <p> The Pixel / Nexus Security Bulletin contains details of security @@ -249,6 +249,16 @@ Upstream kernel</a></td> <th>Component</th> </tr> <tr> + <td>CVE-2017-15817</td> + <td>A-68992394<br /> + <a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/prima/commit/?id=8ba78e506e5002cdae525dd544dbf1df0ccce1ef"> +QC-CR#2076603</a> + [<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/prima/commit/?id=fe43c2b64ac81199de17efc258e95546cb0546f1">2</a>]</td> + <td>RCE</td> + <td>Critical</td> + <td>WLan</td> + </tr> + <tr> <td>CVE-2017-15859</td> <td>A-65468985<br /> <a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-2.0/commit/?id=88dcc44ea8fbe158d1dee3ea197e47794bf4449d"> @@ -620,6 +630,11 @@ bulletin, are not required for declaring a security patch level. <td>February 7, 2018</td> <td>Bulletin revised to include AOSP links.</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> diff --git a/en/security/bulletin/pixel/2018-03-01.html b/en/security/bulletin/pixel/2018-03-01.html index 799216b5..80184531 100644 --- a/en/security/bulletin/pixel/2018-03-01.html +++ b/en/security/bulletin/pixel/2018-03-01.html @@ -162,15 +162,6 @@ additional references are linked to numbers following the bug ID. <td>7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> </tr> <tr> - <td>CVE-2017-13266</td> - <td><a href="https://android.googlesource.com/platform/system/bt/+/2f2043f18463a5c963c138d24346870b1066e7a6"> - A-69478941</a> - </td> - <td>EoP</td> - <td>Moderate</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-13268</td> <td><a href="https://android.googlesource.com/platform/system/bt/+/49a57cd2346a716eca07153ac83026787fb9d03a"> A-67058064</a> diff --git a/en/security/bulletin/pixel/2018-04-01.html b/en/security/bulletin/pixel/2018-04-01.html new file mode 100644 index 00000000..0322f70a --- /dev/null +++ b/en/security/bulletin/pixel/2018-04-01.html @@ -0,0 +1,1037 @@ +<html devsite> + <head> + <title>Pixel / Nexus Security Bulletin—April 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 April 2, 2018 | Updated April 4, 2018</em></p> + +<p> +The Pixel / Nexus Security Bulletin contains details of security +vulnerabilities and functional improvements affecting +<a href="https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices">supported +Google Pixel and Nexus devices</a> (Google devices). For Google devices, +security patch levels of 2018-04-05 or later address all issues in this +bulletin and all issues in the <a href="/security/bulletin/2018-04-01">April +2018 Android Security Bulletin</a>. 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> +All supported Google devices will receive an update to the 2018-04-05 patch +level. We encourage all customers to accept these updates to their devices. +</p> +<p class="note"> +<strong>Note:</strong> The Google device firmware images are available on the +<a href="https://developers.google.com/android/nexus/images">Google Developer +site</a>. +</p> + +<h2 id="announcements">Announcements</h2> +<p>In addition to the security vulnerabilities described in the +<a href="/security/bulletin/2018-04-01">April 2018 Android Security Bulletin</a>, +Google devices also contain patches for the security vulnerabilities +described below. Partners were notified of these issues at least a month ago +and may choose to incorporate them as part of their device updates.</p> + +<h2 id="security-patches">Security patches</h2> +<p> +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="https://source.android.com/security/overview/updates-resources.html#severity">severity</a>, +and updated Android Open Source Project (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="framework">Framework</h3> + +<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-13294</td> + <td><a href="https://android.googlesource.com/platform/packages/apps/Email/+/c3e0aba2a604ce7c3807d65df1e6a2b848287019">A-71814449</a> + [<a href="https://android.googlesource.com/platform/packages/apps/UnifiedEmail/+/e00598532bbfc8618b7c051cbf6bd15491f61f27">2</a>]</td> + <td>ID</td> + <td>Moderate</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-13295</td> + <td><a href="https://android.googlesource.com/platform/frameworks/base/+/a2a36541f0b3603335e74da0a8d2b6a9d5bcec3f">A-62537081</a></td> + <td>DoS</td> + <td>Moderate</td> + <td>6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + </tr> +</table> + + +<h3 id="media-framework">Media framework</h3> + +<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-13300</td> + <td>A-71567394<a href="#asterisk">*</a></td> + <td>DoS</td> + <td>High</td> + <td>6.0, 6.0.1</td> + </tr> + <tr> + <td rowspan="2">CVE-2017-13296</td> + <td rowspan="2"><a href="https://android.googlesource.com/platform/external/libavc/+/3e3e81ede5229c5a9c6b7bf6a63844ecf07ae3ae">A-70897454</a></td> + <td>ID</td> + <td>Moderate</td> + <td>7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + </tr> + <tr> + <td>DoS</td> + <td>High</td> + <td>6.0, 6.0.1</td> + </tr> + <tr> + <td rowspan="2">CVE-2017-13297</td> + <td rowspan="2"><a href="https://android.googlesource.com/platform/external/libhevc/+/daaece3e79db33f6c473bb54a39933d387a9bf95">A-71766721</a></td> + <td>ID</td> + <td>Moderate</td> + <td>7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + </tr> + <tr> + <td>DoS</td> + <td>High</td> + <td>6.0, 6.0.1</td> + </tr> + <tr> + <td rowspan="2">CVE-2017-13298</td> + <td rowspan="2"><a href="https://android.googlesource.com/platform/frameworks/av/+/12e25a753f4b6f0aa935e54bae66023bd8321598">A-72117051</a></td> + <td>ID</td> + <td>Moderate</td> + <td>7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + </tr> + <tr> + <td>DoS</td> + <td>High</td> + <td>6.0, 6.0.1</td> + </tr> + <tr> + <td rowspan="2">CVE-2017-13299</td> + <td rowspan="2"><a href="https://android.googlesource.com/platform/external/libavc/+/d849abf312a365553ce68aec32dea93230036abe">A-70897394</a></td> + <td>NSI</td> + <td>NSI</td> + <td>7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + </tr> + <tr> + <td>DoS</td> + <td>High</td> + <td>6.0, 6.0.1</td> + </tr> +</table> + + +<h3 id="system">System</h3> + +<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-13301</td> + <td><a href="https://android.googlesource.com/platform/frameworks/base/+/384689934d293acf532e3fea3e72ef78df4f2d1e">A-66498711</a> + [<a href="https://android.googlesource.com/platform/frameworks/base/+/d52b215f82e464705373d794748325298f0a1f9a">2</a>]</td> + <td>DoS</td> + <td>Moderate</td> + <td>8.0</td> + </tr> + <tr> + <td>CVE-2017-13302</td> + <td><a href="https://android.googlesource.com/platform/frameworks/base/+/e54ad58aea33860fbb36bf828684e3df6393f602">A-69969749</a></td> + <td>DoS</td> + <td>Moderate</td> + <td>8.0</td> + </tr> +</table> + + +<h3 id="broadcom-components">Broadcom components</h3> + +<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-13303</td> + <td>A-71359108<a href="#asterisk">*</a><br /> + B-V2018010501</td> + <td>ID</td> + <td>Moderate</td> + <td>bcmdhd driver</td> + </tr> +</table> + + +<h3 id="kernel-components">Kernel components</h3> + +<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-13304</td> + <td>A-70576999<a href="#asterisk">*</a></td> + <td>ID</td> + <td>Moderate</td> + <td>mnh_sm driver</td> + </tr> + <tr> + <td>CVE-2017-13305</td> + <td>A-70526974<a href="#asterisk">*</a></td> + <td>ID</td> + <td>Moderate</td> + <td>encrypted-keys</td> + </tr> + <tr> + <td>CVE-2017-17449</td> + <td>A-70980949<br /> + <a href="https://lkml.org/lkml/2017/12/5/950">Upstream kernel</a></td> + <td>ID</td> + <td>Moderate</td> + <td>netlink tap</td> + </tr> + <tr> + <td>CVE-2017-13306</td> + <td>A-70295063<a href="#asterisk">*</a></td> + <td>EoP</td> + <td>Moderate</td> + <td>mnh driver</td> + </tr> + <tr> + <td>CVE-2017-13307</td> + <td>A-69128924<a href="#asterisk">*</a></td> + <td>EoP</td> + <td>Moderate</td> + <td>pci sysfs</td> + </tr> + <tr> + <td>CVE-2017-17712</td> + <td>A-71500434<br /> + <a href="http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=8f659a03a0ba9289b9aeb9b4470e6fb263d6f483"> +Upstream kernel</a></td> + <td>EoP</td> + <td>Moderate</td> + <td>net ipv4</td> + </tr> + <tr> + <td>CVE-2017-15115</td> + <td>A-70217214<br /> + <a href="http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=df80cd9b28b9ebaa284a41df611dbf3a2d05ca74"> +Upstream kernel</a></td> + <td>EoP</td> + <td>Moderate</td> + <td>sctp</td> + </tr> +</table> + + +<h3 id="qualcomm-components">Qualcomm components</h3> + +<table> + <col width="17%"> + <col width="25%"> + <col width="9%"> + <col width="14%"> + <col width="33%"> + <tr> + <th>CVE</th> + <th>References</th> + <th>Type</th> + <th>Severity</th> + <th>Component</th> + </tr> + <tr> + <td>CVE-2018-3598</td> + <td>A-71501698<br /> + <a href="https://source.codeaurora.org/quic/la/kernel/msm-3.18/commit/?id=bfd8ffc65e6e82de2adceba58bd67137fb3b2024"> +QC-CR#1097390</a></td> + <td>ID</td> + <td>Moderate</td> + <td>camera_v2 driver</td> + </tr> + <tr> + <td>CVE-2018-5826</td> + <td>A-69128800<a href="#asterisk">*</a><br /> + QC-CR#2157283</td> + <td>ID</td> + <td>Moderate</td> + <td>qcacld-3.0 hdd driver</td> + </tr> + <tr> + <td>CVE-2017-15853</td> + <td>A-65853393<a href="#asterisk">*</a><br /> + QC-CR#2116517<br /> + QC-CR#2125577</td> + <td>ID</td> + <td>Moderate</td> + <td>WLAN</td> + </tr> + <tr> + <td>CVE-2018-3584</td> + <td>A-64610600<a href="#asterisk">*</a><br /> + QC-CR#2142046</td> + <td>ID</td> + <td>Moderate</td> + <td>rmnet_usb</td> + </tr> + <tr> + <td>CVE-2017-8269</td> + <td>A-33967002<a href="#asterisk">*</a><br /> + QC-CR#2013145<br /> + QC-CR#2114278</td> + <td>ID</td> + <td>Moderate</td> + <td>IPA driver</td> + </tr> + <tr> + <td>CVE-2017-15837</td> + <td>A-64403015<a href="#asterisk">*</a><br /> + QC-CR#2116387</td> + <td>ID</td> + <td>Moderate</td> + <td>NL80211 driver</td> + </tr> + <tr> + <td>CVE-2018-5823</td> + <td>A-72957335<br /> + <a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=fc5bbedd4ab9fd5239be8618afe714d39dd8de49"> +QC-CR#2139436</a></td> + <td>EoP</td> + <td>Moderate</td> + <td>WLAN</td> + </tr> + <tr> + <td>CVE-2018-5825</td> + <td>A-72957269<br /> + <a href="https://source.codeaurora.org/quic/la/kernel/msm-3.10/commit/?id=5ae227670444cf8ea7b8a8d98eab41404a03332f">QC-CR#2151146</a> + [<a href="https://source.codeaurora.org/quic/la/kernel/msm-3.18/commit/?id=cf0f031ffbb6a8e08e517f653045c3f81d7f2663">2</a>] + [<a href="https://source.codeaurora.org/quic/la/kernel/msm-3.18/commit/?id=09a34b7878a732187f9138900667d8abb2b1c39c">3</a>]</td> + <td>EoP</td> + <td>Moderate</td> + <td>IPA driver</td> + </tr> + <tr> + <td>CVE-2018-5824</td> + <td>A-72957235<br /> + <a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-2.0/commit/?id=b34f6f3afe229e32a32418f75889279f6e00d157">QC-CR#2149399</a> + [<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=d3a92a1656a3ee2fc44d4ff98614a4f5b70f1893">2</a>]</td> + <td>EoP</td> + <td>Moderate</td> + <td>WLAN</td> + </tr> + <tr> + <td>CVE-2018-5827</td> + <td>A-72956920<br /> + <a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=53e6d889ac29336ba212a0d4a987455a85736fa8"> +QC-CR#2161977</a></td> + <td>EoP</td> + <td>Moderate</td> + <td>WLAN</td> + </tr> + <tr> + <td>CVE-2018-5822</td> + <td>A-71501692<br /> + <a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-2.0/commit/?id=edc42ce371b6831dc55a15bc2624175bd538aa37"> +QC-CR#2115221</a></td> + <td>EoP</td> + <td>Moderate</td> + <td>QC WLAN</td> + </tr> + <tr> + <td>CVE-2018-5821</td> + <td>A-71501687<br /> + <a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-2.0/commit/?id=08ab943766abe845a8fae21689bae18dd74e9b20"> +QC-CR#2114363</a></td> + <td>EoP</td> + <td>Moderate</td> + <td>modem driver</td> + </tr> + <tr> + <td>CVE-2018-5820</td> + <td>A-71501686<br /> + <a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-2.0/commit/?id=a4a8475ea650c16705a3eaa011524820dc5ffd44"> +QC-CR#2114336</a></td> + <td>EoP</td> + <td>Moderate</td> + <td>Modem driver</td> + </tr> + <tr> + <td>CVE-2018-3599</td> + <td>A-71501666<br /> + <a href="https://source.codeaurora.org/quic/la/kernel/msm-3.18/commit/?id=cf2702c1a77d2a164a3be03597eff7e6fe5f967e"> +QC-CR#2047235</a></td> + <td>EoP</td> + <td>Moderate</td> + <td>Qualcomm Core Services</td> + </tr> + <tr> + <td>CVE-2018-3596</td> + <td>A-35263529<a href="#asterisk">*</a><br /> + QC-CR#640898</td> + <td>EoP</td> + <td>Moderate</td> + <td>WLAN</td> + </tr> + <tr> + <td>CVE-2018-3568</td> + <td>A-72957136<br /> + <a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=70cd30a5c1fdd02af19cf0e34c41842cce89a82d"> +QC-CR#2152824</a></td> + <td>EoP</td> + <td>Moderate</td> + <td>WLAN</td> + </tr> + <tr> + <td>CVE-2018-3567</td> + <td>A-72956997<br /> + <a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-2.0/commit/?id=f2627fca43bc4403a445c2b84481383ac0249364">QC-CR#2147119</a> + [<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=25c131e8a807894e04f95bdeb1cbd0376eda3bea">2</a>]</td> + <td>EoP</td> + <td>Moderate</td> + <td>WLAN</td> + </tr> + <tr> + <td>CVE-2017-15855</td> + <td>A-72957336<br /> + <a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=75c0ea8622bb07716d2a82247e6dd1597980f223"> +QC-CR#2149501</a></td> + <td>EoP</td> + <td>Moderate</td> + <td>WLAN</td> + </tr> + <tr> + <td>CVE-2018-5828</td> + <td>A-71501691<br /> + <a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-2.0/commit/?id=6299a6bf166a60a47e9108ae2119027e787432d0"> +QC-CR#2115207</a></td> + <td>EoP</td> + <td>Moderate</td> + <td>QC WLAN</td> + </tr> + <tr> + <td>CVE-2017-15836</td> + <td>A-71501693<br /> + <a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=058e1eef2b1422bc0dd70f73832f1ac8a3dbe806"> +QC-CR#2119887</a></td> + <td>EoP</td> + <td>Moderate</td> + <td>QC WLAN</td> + </tr> + <tr> + <td>CVE-2017-14890</td> + <td>A-71501695<br /> + <a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=234e14add09a1ba4a1b1d81d474ac3978dc94fd6"> +QC-CR#2120751</a></td> + <td>EoP</td> + <td>Moderate</td> + <td>QC WLAN</td> + </tr> + <tr> + <td>CVE-2017-14894</td> + <td>A-71501694<br /> + <a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=dfca3d8173c1548a97e558cb8abd1ffd2483f8b7"> +QC-CR#2120424</a></td> + <td>EoP</td> + <td>Moderate</td> + <td>QC WLAN</td> + </tr> + <tr> + <td>CVE-2017-14880</td> + <td>A-68992477<br /> + <a href="https://source.codeaurora.org/quic/la/kernel/msm-3.18/commit/?id=cbf3702ae1c5e2cacd6f15a5eb7a799e2f1ed96f"> +QC-CR#2078734</a> + [<a href="https://source.codeaurora.org/quic/la/kernel/msm-3.10/commit/?id=d72e444dce0b9d20fdcdc4daeb6227e3536eebf7">2</a>]</td> + <td>EoP</td> + <td>Moderate</td> + <td>IPA WAN driver</td> + </tr> + <tr> + <td>CVE-2017-11075</td> + <td>A-70237705<br /> + <a href="https://source.codeaurora.org/quic/la/kernel/msm-4.4/commit/?id=7a07165c62926e899b710e1fed31532f31797dd5"> +QC-CR#2098332</a></td> + <td>EoP</td> + <td>Moderate</td> + <td>Audio DSP driver</td> + </tr> +</table> + +<h2 id="functional-updates">Functional updates</h2> +<p> +These updates are included for affected Pixel devices to address functionality +issues not related to the security of Pixel devices. The table includes +associated references; the affected category, such as Bluetooth or mobile data; +and a summary of the issue. +</p> + +<table> + <tr> + <th>References</th> + <th>Category</th> + <th>Improvements</th> + <th>Devices</th> + </tr> + <tr> + <td>A-35963245</td> + <td>Performance</td> + <td>Enable Assisted Dialing support</td> + <td>Pixel 2, Pixel 2 XL</td> + </tr> + <tr> + <td>A-37681923<br> + A-68215016</td> + <td>Logging</td> + <td>Improve anomaly detection metrics</td> + <td>All</td> + </tr> + <tr> + <td>A-63908720</td> + <td>Logging</td> + <td>Improve diskstats logging</td> + <td>All</td> + </tr> + <tr> + <td>A-64101451</td> + <td>Performance</td> + <td>Improve handover from VoLTE to VoWi-Fi during Emergency calls on certain carriers</td> + <td>Pixel, Pixel XL, Pixel 2, Pixel 2 XL</td> + </tr> + <tr> + <td>A-64586126</td> + <td>Camera</td> + <td>Improve microvideo performance in Google Camera</td> + <td>Pixel, Pixel XL, Pixel 2, Pixel 2 XL</td> + </tr> + <tr> + <td>A-64610438</td> + <td>Performance</td> + <td>Reduce delays upon opening specific apps</td> + <td>Pixel 2, Pixel 2 XL</td> + </tr> + <tr> + <td>A-65175134</td> + <td>Video</td> + <td>Improve decoding of certain video streams</td> + <td>Pixel, Pixel XL</td> + </tr> + <tr> + <td>A-65347520</td> + <td>Performance</td> + <td>Improve fingerprint and keyboard latency in certain situations</td> + <td>Pixel 2, Pixel 2 XL</td> + </tr> + <tr> + <td>A-65490850</td> + <td>UI</td> + <td>Adjust notifications when entering or exiting Wi-Fi coverage during a video call</td> + <td>Pixel 2, Pixel 2 XL</td> + </tr> + <tr> + <td>A-65509134</td> + <td>Connectivity</td> + <td>Enable IMS911 on certain networks</td> + <td>Pixel 2, Pixel 2 XL, Pixel, Pixel XL</td> + </tr> + <tr> + <td>A-66951771</td> + <td>Logging</td> + <td>Detect Wi-Fi Passport statistics for developers</td> + <td>All</td> + </tr> + <tr> + <td>A-66957450</td> + <td>Performance</td> + <td>Improve lock screen performance</td> + <td>All</td> + </tr> + <tr> + <td>A-67094673</td> + <td>Logging</td> + <td>Improve start time logging</td> + <td>All</td> + </tr> + <tr> + <td>A-67589241</td> + <td>Performance</td> + <td>Improve magnetic sensor performance on Pixel 2/Pixel 2 XL</td> + <td>Pixel 2, Pixel 2 XL</td> + </tr> + <tr> + <td>A-67593274</td> + <td>Battery</td> + <td>Reduce battery drain after modem issues</td> + <td>Pixel 2, Pixel 2 XL</td> + </tr> + <tr> + <td>A-67634615</td> + <td>Stability</td> + <td>Improve modem stability on Pixel and Pixel 2 phones</td> + <td>Pixel, Pixel XL, Pixel 2, Pixel 2 XL</td> + </tr> + <tr> + <td>A-67750231</td> + <td>UI</td> + <td>Adjust Call Forwarding UI</td> + <td>Nexus 5X, Pixel, Pixel XL, Pixel 2, Pixel 2 XL</td> + </tr> + <tr> + <td>A-67774904</td> + <td>Connectivity</td> + <td>Improve multi-calling performance over Wi-Fi</td> + <td>Pixel, Pixel XL</td> + </tr> + <tr> + <td>A-67777512</td> + <td>Connectivity</td> + <td>Improve data connectivity for T-Mobile users in parts of Australia</td> + <td>Pixel, Pixel XL</td> + </tr> + <tr> + <td>A-67882977</td> + <td>Certification</td> + <td>Update certification</td> + <td>Pixel, Pixel XL</td> + </tr> + <tr> + <td>A-68150449<br> + A-68059359<br> + A-69797741<br> + A-69378640<br> + A-68824279</td> + <td>Stability</td> + <td>Improve Wi-Fi stability on Pixel 2 phones</td> + <td>Pixel 2, Pixel 2 XL</td> + </tr> + <tr> + <td>A-68217064</td> + <td>Performance</td> + <td>Improve handover to Wi-Fi Calling in low-coverage areas</td> + <td>Pixel 2, Pixel 2 XL</td> + </tr> + <tr> + <td>A-68398312</td> + <td>Performance</td> + <td>Improve conference call performance over Wifi</td> + <td>Pixel 2, Pixel 2 XL</td> + </tr> + <tr> + <td>A-68671462</td> + <td>Connectivity</td> + <td>Improve VoLTE performance for some carriers</td> + <td>Nexus 5X, Pixel, Pixel XL, Pixel 2, Pixel 2 XL</td> + </tr> + <tr> + <td>A-68841424</td> + <td>Connectivity</td> + <td>Adjust APN updating behavior</td> + <td>All</td> + </tr> + <tr> + <td>A-68863351</td> + <td>UI</td> + <td>Improve settings app icons</td> + <td>All</td> + </tr> + <tr> + <td>A-68923696<br> + A-68922470<br> + A-68940490</td> + <td>Certification</td> + <td>Upgrade certificates to ensure continued service.</td> + <td>Nexus 5X, Pixel, Pixel XL, Pixel 2, Pixel 2 XL</td> + </tr> + <tr> + <td>A-68931709</td> + <td>Developer</td> + <td>Add methods to PeerHandle API for developers</td> + <td>All</td> + </tr> + <tr> + <td>A-68959671</td> + <td>Connectivity</td> + <td>Update Verizon Service APK for Pixel phones</td> + <td>Pixel, Pixel XL, Pixel 2, Pixel 2 XL</td> + </tr> + <tr> + <td>A-69003183</td> + <td>Logging</td> + <td>Improve Wi-Fi and RPM logging</td> + <td>Pixel 2, Pixel 2 XL</td> + </tr> + <tr> + <td>A-69017578<br> + A-68138080<br> + A-68205105<br> + A-70731000<br> + A-69574837<br> + A-68474108<br> + A-70406781</td> + <td>Connectivity, Performance</td> + <td>Improve connectivity and performance on certain carrier networks</td> + <td>Pixel, Pixel XL, Pixel 2, Pixel 2 XL</td> + </tr> + <tr> + <td>A-69064494</td> + <td>Performance</td> + <td>Improve notification listening apps</td> + <td>All</td> + </tr> + <tr> + <td>A-69152057</td> + <td>Connectivity</td> + <td>Address call forwarding issue.</td> + <td>All</td> + </tr> + <tr> + <td>A-69209000</td> + <td>Connectivity</td> + <td>Improve internet connectivity on Pixel 2 on certain WiFi networks</td> + <td>Pixel 2</td> + </tr> + <tr> + <td>A-69238007<br> + A-68202289<br> + A-69334308</td> + <td>Connectivity</td> + <td>Adjust APN settings</td> + <td>Nexus 5X, Pixel, Pixel XL, Pixel 2, Pixel 2 XL</td> + </tr> + <tr> + <td>A-69261367<br> + A-70512352</td> + <td>Messaging</td> + <td>Improve MMS messaging performance on certain carriers</td> + <td>Nexus 5X, Pixel, Pixel XL, Pixel 2, Pixel 2 XL</td> + </tr> + <tr> + <td>A-69275204</td> + <td>Battery</td> + <td>Adjust battery learned capacity increment and decrement limits</td> + <td>Pixel 2, Pixel 2 XL</td> + </tr> + <tr> + <td>A-69334266</td> + <td>Connectivity</td> + <td>Change voice domain to CS for certain carriers</td> + <td>Pixel XL</td> + </tr> + <tr> + <td>A-69475609</td> + <td>Performance</td> + <td>Adjust timeouts for Phone App</td> + <td>All</td> + </tr> + <tr> + <td>A-69672417</td> + <td>Stability</td> + <td>Improve stability for Pixel 2 devices in certain parts of Canada</td> + <td>Pixel 2, Pixel 2 XL</td> + </tr> + <tr> + <td>A-69848394<br> + A-68275646</td> + <td>Performance</td> + <td>Improve instant Apps performance</td> + <td>All</td> + </tr> + <tr> + <td>A-69870527</td> + <td>UI</td> + <td>Improve indicators for emergency call connectivity</td> + <td>Pixel 2, Pixel 2 XL</td> + </tr> + <tr> + <td>A-70045970</td> + <td>Battery</td> + <td>Optimize search logic to improve battery performance.</td> + <td>Pixel 2, Pixel 2 XL</td> + </tr> + <tr> + <td>A-70094083<br> + A-70094701</td> + <td>Battery</td> + <td>Improve battery logging for Pixel 2 and Pixel 2 XL</td> + <td>Pixel 2, Pixel 2 XL</td> + </tr> + <tr> + <td>A-70214869</td> + <td>GPS</td> + <td>Improve GPS Time performance on Pixel 2 XL</td> + <td>Pixel 2 XL</td> + </tr> + <tr> + <td>A-70338906</td> + <td>Audio</td> + <td>Improve audio speaker performance during phone calls</td> + <td>All</td> + </tr> + <tr> + <td>A-70398372</td> + <td>UI</td> + <td>Adjust advanced calling settings for Verizon</td> + <td>Nexus 5X, Pixel, Pixel XL, Pixel 2, Pixel 2 XL</td> + </tr> + <tr> + <td>A-70576351</td> + <td>Connectivity</td> + <td>Change to prioritize certain bands</td> + <td>Nexus 5X, Pixel, Pixel XL, Pixel 2, Pixel 2 XL</td> + </tr> + <tr> + <td>A-70580873<br> + A-70912923<br> + A-71497259</td> + <td>Connectivity</td> + <td>Improve in-call performance for some carriers</td> + <td>Pixel, Pixel XL, Pixel 2, Pixel 2 XL</td> + </tr> + <tr> + <td>A-70815434</td> + <td>Connectivity</td> + <td>Improve network performance on Simyo carrier</td> + <td>Nexus 5X</td> + </tr> + <tr> + <td>A-71708302</td> + <td>Logging</td> + <td>Improve connectivity metrics</td> + <td>All</td> + </tr> + <tr> + <td>A-71983424</td> + <td>Performance</td> + <td>Improve experience switching between LTE and Wifi</td> + <td>Pixel 2 XL</td> + </tr> + <tr> + <td>A-72119809</td> + <td>Connectivity</td> + <td>Improve data performance for devices with certain SIM cards</td> + <td>All</td> + </tr> + <tr> + <td>A-72175011</td> + <td>Logging</td> + <td>Improve autofill logging</td> + <td>All</td> + </tr> + <tr> + <td>A-72797728<br> + A-71599119</td> + <td>Logging</td> + <td>Improve internal troubleshooting tools</td> + <td>All</td> + </tr> + <tr> + <td>A-72871435</td> + <td>Logging</td> + <td>Improve network logging</td> + <td>All</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> +Security patch levels of 2018-04-05 or later address all issues associated with +the 2018-04-05 security patch level and all previous patch levels. To learn how +to check a device's security patch level, read the instructions on the +<a href="https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices">Pixel +and Nexus update schedule</a>. +</p> +<p id="type"> +<strong>2. 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>3. 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>4. 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>5. Why are security vulnerabilities split between this bulletin and the +Android Security Bulletins?</strong> +</p> +<p> +Security vulnerabilities that are documented in the Android Security Bulletins +are required in order to declare the latest security patch level on Android +devices. Additional security vulnerabilities, such as those documented in this +bulletin, are not required for declaring a security patch level. +</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>April 2, 2018</td> + <td>Bulletin published.</td> + </tr> + <tr> + <td>1.1</td> + <td>April 4, 2018</td> + <td>Bulletin revised to include AOSP links.</td> + </tr> +</table> +</body></html> diff --git a/en/security/bulletin/pixel/2018.html b/en/security/bulletin/pixel/2018.html index a7dfa4b4..f4a08522 100644 --- a/en/security/bulletin/pixel/2018.html +++ b/en/security/bulletin/pixel/2018.html @@ -39,6 +39,21 @@ Bulletins</a> homepage.</p> <th>Security patch level</th> </tr> <tr> + <td><a href="/security/bulletin/pixel/2018-04-01.html">April 2018</a></td> + <td>Coming soon + <!-- + <a href="/security/bulletin/pixel/2018-04-01.html">English</a> / + <a href="/security/bulletin/pixel/2018-04-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/pixel/2018-04-01.html?hl=ko">í•œêµì–´</a> / + <a href="/security/bulletin/pixel/2018-04-01.html?hl=ru">руÌÑÑкий</a> / + <a href="/security/bulletin/pixel/2018-04-01.html?hl=zh-cn">ä¸æ–‡ (ä¸å›½)</a> / + <a href="/security/bulletin/pixel/2018-04-01.html?hl=zh-tw">ä¸æ–‡ (å°ç£)</a> + --> + </td> + <td>April 2018</td> + <td>2018-04-05</td> + </tr> + <tr> <td><a href="/security/bulletin/pixel/2018-03-01.html">March 2018</a></td> <td>Coming soon <!-- diff --git a/en/security/bulletin/pixel/index.html b/en/security/bulletin/pixel/index.html index 4a018ab9..95f1eafd 100644 --- a/en/security/bulletin/pixel/index.html +++ b/en/security/bulletin/pixel/index.html @@ -59,6 +59,21 @@ AOSP 24–48 hours after the Pixel / Nexus bulletin is release <th>Security patch level</th> </tr> <tr> + <td><a href="/security/bulletin/pixel/2018-04-01.html">April 2018</a></td> + <td>Coming soon + <!-- + <a href="/security/bulletin/pixel/2018-04-01.html">English</a> / + <a href="/security/bulletin/pixel/2018-04-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/pixel/2018-04-01.html?hl=ko">í•œêµì–´</a> / + <a href="/security/bulletin/pixel/2018-04-01.html?hl=ru">руÌÑÑкий</a> / + <a href="/security/bulletin/pixel/2018-04-01.html?hl=zh-cn">ä¸æ–‡ (ä¸å›½)</a> / + <a href="/security/bulletin/pixel/2018-04-01.html?hl=zh-tw">ä¸æ–‡ (å°ç£)</a> + --> + </td> + <td>April 2018</td> + <td>2018-04-05</td> + </tr> + <tr> <td><a href="/security/bulletin/pixel/2018-03-01.html">March 2018</a></td> <td>Coming soon <!-- diff --git a/en/security/overview/acknowledgements.html b/en/security/overview/acknowledgements.html index 9d1250fd..74c88b2e 100644 --- a/en/security/overview/acknowledgements.html +++ b/en/security/overview/acknowledgements.html @@ -38,6 +38,149 @@ Rewards</a> program.</p> acknowledgements were listed together.</p> +<h4 id="apr-2018">April</h4> + +<table> + <col width="70%"> + <col width="30%"> + <tr> + <th>Researchers</th> + <th>CVEs</th> + </tr> + <tr> + <td>Billy Lau of Google + </td> + <td>CVE-2017-13305 + </td> + </tr> + <tr> + <td><a href="http://weibo.com/csddl">Chong Wang</a> and <a href="http://weibo.com/ele7enxxh">Zinuo Han</a> from Chengdu Security Response Center of Qihoo 360 Technology Co. Ltd + </td> + <td>CVE-2017-13289, CVE-2017-13286 + </td> + </tr> + <tr> + <td>Cusas @ Huawei L.O. Team + </td> + <td>CVE-2017-13279 + </td> + </tr> + <tr> + <td>Daxing Guo of Tencent's Xuanwu Lab + </td> + <td>CVE-2017-13292, CVE-2017-13303 + </td> + </tr> + <tr> + <td>Dinesh Venkatesan (<a href="https://twitter.com/malwareresearch">@malwareresearch</a>) from Symantec + </td> + <td>CVE-2017-13295 + </td> + </tr> + <tr> + <td>Elphet and Gong Guang of Alpha Team, Qihoo 360 Technology Co. Ltd + </td> + <td>CVE-2017-13276 + </td> + </tr> + <tr> + <td>En He(<a href="https://twitter.com/heeeeen4x">@heeeeen4x</a>) and Bo Liu of <a href="http://www.ms509.com">MS509Team</a> + </td> + <td>CVE-2017-13294 + </td> + </tr> + <tr> + <td>Eric Leong (<a href="https://twitter.com/ericwleong">@ericwleong</a>) + </td> + <td>CVE-2017-13301 + </td> + </tr> + <tr> + <td>Hao Chen and Guang Gong of Alpha Team, Qihoo 360 Technology Co. Ltd. + </td> + <td>CVE-2018-3596 + </td> + </tr> + <tr> + <td>Haosheng Wang (<a href="https://twitter.com/gnehsoah">@gnehsoah</a>) + </td> + <td>CVE-2017-13280 + </td> + </tr> + <tr> + <td>Jean-Baptiste Cayrou (<a href="https://twitter.com/jbcayrou">@jbcayrou</a>) + </td> + <td>CVE-2017-13284 + </td> + </tr> + <tr> + <td>Jianjun Dai(<a href="https://twitter.com/Jioun_dai">@Jioun_dai</a>) and Guang Gong of Alpha Team, Qihoo 360 Technology Co. Ltd + </td> + <td>CVE-2017-13291, CVE-2017-13283, CVE-2017-13282, CVE-2017-13281, CVE-2017-13267 + </td> + </tr> + <tr> + <td><a href="https://github.com/michalbednarski">MichaÅ‚ Bednarski</a> + </td> + <td>CVE-2017-13287 + </td> + </tr> + <tr> + <td>Patrick Delvenne (<a href="https://twitter.com/wintzx">@wintzx</a>) Orange Labs + </td> + <td>CVE-2018-3584 + </td> + </tr> + <tr> + <td>Pengfei Ding(ä¸é¹é£ž), Chenfu Bao（包沉浮）, Lenx Wei（韦韬） of Baidu X-Lab(百度安全实验室) + </td> + <td>CVE-2017-13306, CVE-2017-13290, CVE-2017-15837 + </td> + </tr> + <tr> + <td>Tencent Blade Team + </td> + <td>CVE-2017-15853 + </td> + </tr> + <tr> + <td>Vasily Vasiliev + </td> + <td>CVE-2017-13297 + </td> + </tr> + <tr> + <td>Weichao Sun of Alibaba Inc (<a href="https://twitter.com/sunblate">@sunblate</a>) + </td> + <td>CVE-2017-13277 + </td> + </tr> + <tr> + <td><a href="mailto:huahuaisadog@gmail.com">Yang Dai</a> and <a href="http://weibo.com/panyu6325">Yu Pan</a> of Vulpecker Team, Qihoo 360 Technology Co. Ltd + </td> + <td>CVE-2017-13304 + </td> + </tr> + <tr> + <td>Yonggang Guo (<a href="https://twitter.com/guoygang">@guoygang</a>) of IceSword Lab, Qihoo 360 Technology Co. Ltd + </td> + <td>CVE-2017-8269, CVE-2017-13307, CVE-2018-5826 + </td> + </tr> + <tr> + <td>Zhongwen & Chao Dai @ Huawei L.O. Team + </td> + <td>CVE-2017-13274 + </td> + </tr> + <tr> + <td><a href="http://weibo.com/ele7enxxh">Zinuo Han</a> from Chengdu Security Response Center of Qihoo 360 Technology Co. Ltd + </td> + <td>CVE-2017-13288, CVE-2017-13298, CVE-2017-13296, CVE-2017-13299, CVE-2017-13275, CVE-2017-13285 + </td> + </tr> +</table> + <h4 id="mar-2018">March</h4> diff --git a/en/security/overview/updates-resources.html b/en/security/overview/updates-resources.html index cebad2f2..508747fe 100644 --- a/en/security/overview/updates-resources.html +++ b/en/security/overview/updates-resources.html @@ -324,6 +324,8 @@ sites. Good places to start:<br> <h3 id="reports">Reports</h3> <p>Sometimes the Android Security team publishes reports or whitepapers. Here are some of the most recent.</p> <ul> + <li><a href="/security/reports/Google_Android_Security_2017_Report_Final.pdf"> + Android Security 2017 Year In Review</a></li> <li><a href="/security/reports/Google_Android_Security_2016_Report_Final.pdf"> Android Security 2016 Year In Review</a></li> <li><a href="/security/reports/Google_Android_Security_2015_Report_Final.pdf"> diff --git a/en/setup/_toc.yaml b/en/setup/_toc.yaml index b4648b20..b82fb73e 100644 --- a/en/setup/_toc.yaml +++ b/en/setup/_toc.yaml @@ -1,69 +1,69 @@ toc: +- title: Overview + path: /setup/ - title: Getting Started section: - - title: Overview - path: /setup/ - title: Codelines, Branches, and Releases - path: /setup/code-lines + path: /setup/start/codelines - title: Codenames, Tags, and Build Numbers - path: /setup/build-numbers + path: /setup/start/build-numbers - title: Project Roles - path: /setup/roles + path: /setup/start/roles - title: Brand Guidelines - path: /setup/brands + path: /setup/start/brands - title: Licenses - path: /setup/licenses + path: /setup/start/licenses - title: FAQ - path: /setup/faqs + path: /setup/start/faqs - title: Site Updates - path: /setup/site-updates + path: /setup/start/site-updates - title: Downloading and Building section: - title: Requirements - path: /setup/requirements + path: /setup/build/requirements - title: Establishing a Build Environment - path: /setup/initializing + path: /setup/build/initializing - title: Downloading the Source - path: /setup/downloading + path: /setup/build/downloading - title: Preparing to Build - path: /setup/building + path: /setup/build/building - title: Compiling with Jack - path: /setup/jack + path: /setup/build/jack - title: Using Reference Boards - path: /setup/devices + path: /setup/build/devices - title: Running Builds - path: /setup/running + path: /setup/build/running - title: Building Kernels - path: /setup/building-kernels + path: /setup/build/building-kernels - title: Known Issues - path: /setup/known-issues + path: /setup/build/known-issues - title: Developing section: - title: Overview - path: /setup/developing + path: /setup/develop/ - title: Using Repo - path: /setup/using-repo + path: /setup/develop/repo - title: Adding a New Device - path: /setup/add-device + path: /setup/develop/new-device - title: Understanding 64-bit Builds - path: /setup/64-bit-builds + path: /setup/develop/64-bit-builds - title: Contributing section: - title: Overview - path: /setup/contributing + path: /setup/contribute/ - title: Life of a Patch - path: /setup/life-of-a-patch + path: /setup/contribute/life-of-a-patch - title: Submitting Patches - path: /setup/submit-patches + path: /setup/contribute/submit-patches - title: View Patches - path: /setup/view-patches + path: /setup/contribute/view-patches - title: Life of a Bug - path: /setup/life-of-a-bug + path: /setup/contribute/life-of-a-bug - title: Reporting Bugs - path: /setup/report-bugs + path: /setup/contribute/report-bugs - title: Reading Bug Reports - path: /setup/read-bug-reports + path: /setup/contribute/read-bug-reports - title: Java Code Style Rules - path: /setup/code-style + path: /setup/contribute/code-style - title: Community path: /setup/community diff --git a/en/setup/building-kernels.html b/en/setup/build/building-kernels.html index cd03c612..28e0708a 100644 --- a/en/setup/building-kernels.html +++ b/en/setup/build/building-kernels.html @@ -23,13 +23,16 @@ -<p>This page details how to build only the <a href="/devices/architecture/kernel/">kernel</a>. The following instructions -assume you have not downloaded all of AOSP; if you have already done so, you can -skip the <code>git clone</code> steps except the step that downloads the kernel -sources.</p> +<p> + This page details how to build only the + <a href="/devices/architecture/kernel/">kernel</a>. The following instructions + assume you have not downloaded all of AOSP; if you have already done so, you + can skip the <code>git clone</code> steps except the step that downloads the + kernel sources. +</p> <p>All examples in this section use the -<a href="/setup/devices.html#hikey-boards">hikey</a> kernel.</p> +<a href="devices.html#hikey-boards">hikey</a> kernel.</p> <h2 id="figuring-out-which-kernel-to-build">Selecting a kernel</h2> <p>This table lists the name and locations of the kernel sources and binaries: @@ -224,35 +227,48 @@ dd if=zImage-dtb bs=1 skip=$(LC_ALL=C od -Ad -x -w2 zImage-dtb | grep 8b1f | cut <h2 id="downloading-sources">Downloading sources</h2> <p>Download the source for the kernel you want to build using the appropriate -<code>git clone</code> command. For example, the following command clones the <code>common</code> kernel, a generic, customizable kernel:</p> +<code>git clone</code> command. For example, the following command clones the +<code>common</code> kernel, a generic, customizable kernel:</p> <pre class="devsite-terminal devsite-click-to-copy"> git clone https://android.googlesource.com/kernel/common </pre> -<p>A full list of the kernel projects can be found in the <a href="https://android.googlesource.com/kernel">Kernel</a> directory. Below are some of the commonly used kernels and their respective <code>git clone</code> commands.</p> +<p>A full list of the kernel projects can be found in the +<a href="https://android.googlesource.com/kernel">Kernel</a> directory. Below +are some of the commonly used kernels and their respective <code>git clone</code> +commands.</p> -<p>The <code>exynos</code> project has the kernel sources for Nexus 10, and can be used as a starting point for work on Samsung Exynos chipsets.</p> +<p>The <code>exynos</code> project has the kernel sources for Nexus 10, and can +be used as a starting point for work on Samsung Exynos chipsets.</p> <pre class="devsite-terminal devsite-click-to-copy">git clone https://android.googlesource.com/kernel/exynos</pre> -<p>The <code>goldfish</code> project contains the kernel sources for the emulated platforms.</p> +<p>The <code>goldfish</code> project contains the kernel sources for the +emulated platforms.</p> <pre class="devsite-terminal devsite-click-to-copy">git clone https://android.googlesource.com/kernel/goldfish</pre> -<p>The <code>hikey-linaro</code> project is used for HiKey reference boards, and can be used as a starting point for work on HiSilicon 620 chipsets.</p> +<p>The <code>hikey-linaro</code> project is used for HiKey reference boards, +and can be used as a starting point for work on HiSilicon 620 chipsets.</p> <pre class="devsite-terminal devsite-click-to-copy">git clone https://android.googlesource.com/kernel/hikey-linaro</pre> -<p>The <code>msm</code> project has the sources for ADP1, ADP2, Nexus One, Nexus 4, Nexus 5, Nexus 6, Nexus 5X, Nexus 6P, Nexus 7 (2013), Pixel, and Pixel XL, and can be used as a starting point for work on Qualcomm MSM chipsets.</p> +<p>The <code>msm</code> project has the sources for ADP1, ADP2, Nexus One, +Nexus 4, Nexus 5, Nexus 6, Nexus 5X, Nexus 6P, Nexus 7 (2013), Pixel, and +Pixel XL, and can be used as a starting point for work on Qualcomm MSM chipsets.</p> <pre class="devsite-terminal devsite-click-to-copy">git clone https://android.googlesource.com/kernel/msm</pre> -<p>The <code>omap</code> project is used for PandaBoard and Galaxy Nexus, and can be used as a starting point for work on TI OMAP chipsets.</p> +<p>The <code>omap</code> project is used for PandaBoard and Galaxy Nexus, and +can be used as a starting point for work on TI OMAP chipsets.</p> <pre class="devsite-terminal devsite-click-to-copy">git clone https://android.googlesource.com/kernel/omap</pre> -<p>The <code>samsung</code> project is used for Nexus S, and can be used as a starting point for work on Samsung Hummingbird chipsets.</p> +<p>The <code>samsung</code> project is used for Nexus S, and can be used as a +starting point for work on Samsung Hummingbird chipsets.</p> <pre class="devsite-terminal devsite-click-to-copy">git clone https://android.googlesource.com/kernel/samsung</pre> -<p>The <code>tegra</code> project is for Xoom, Nexus 7 (2012), Nexus 9, and can be used as a starting point for work on NVIDIA Tegra chipsets.</p> +<p>The <code>tegra</code> project is for Xoom, Nexus 7 (2012), Nexus 9, and can +be used as a starting point for work on NVIDIA Tegra chipsets.</p> <pre class="devsite-terminal devsite-click-to-copy">git clone https://android.googlesource.com/kernel/tegra</pre> -<p>The <code>x86_64</code> project has the kernel sources for Nexus Player, and can be used as a starting point for work on Intel x86_64 chipsets.</p> +<p>The <code>x86_64</code> project has the kernel sources for Nexus Player, and +can be used as a starting point for work on Intel x86_64 chipsets.</p> <pre class="devsite-terminal devsite-click-to-copy">git clone https://android.googlesource.com/kernel/x86_64</pre> <h2 id="building">Building the kernel</h2> diff --git a/en/setup/building.html b/en/setup/build/building.html index 246d1460..ab57d087 100644 --- a/en/setup/building.html +++ b/en/setup/build/building.html @@ -25,7 +25,7 @@ <p>The following instructions to build the Android source tree apply to all branches, including <code>master</code>. The basic sequence of build commands -is as follows:</p> +is as follows.</p> <h2 id="obtaining-proprietary-binaries">Obtain proprietary binaries</h2> @@ -35,28 +35,28 @@ graphics acceleration. See the sections below for download links and <a href="requirements.html#binaries">Device binaries</a> for additional resources.</p> -<p class ="note">Some devices package these proprietary binaries on their -<code>/vendor</code> partition.</p> +<aside class ="note">Some devices package these proprietary binaries on their +<code>/vendor</code> partition.</aside> <h3 id="downloading-proprietary-binaries">Download proprietary binaries</h3> <p>You can download official binaries for the supported devices running tagged AOSP release branches from <a -href="https://developers.google.com/android/drivers">Google's +href="https://developers.google.com/android/drivers" class="external">Google's drivers</a>. These binaries add access to additional hardware capabilities with non-open source code. To instead build the AOSP master branch, use the -<a href="https://developers.google.com/android/blobs-preview">Binaries +<a href="https://developers.google.com/android/blobs-preview" class="external">Binaries Preview</a>. When building the master branch for a device, use -the binaries for the <a href="/setup/build-numbers.html">most recent +the binaries for the <a href="/setup/start/build-numbers.html">most recent numbered release</a> or with the most recent date.</p> <h3 id="extracting-proprietary-binaries">Extract proprietary binaries</h3> <p>Each set of binaries comes as a self-extracting script in a compressed archive. Uncompress each archive, run the included self-extracting script from -the root of the source tree, then confirm that you agree to the terms -of the enclosed license agreement. The binaries and their matching makefiles -will be installed in the <code>vendor/</code> hierarchy of the source tree.</p> +the root of the source tree, then confirm you agree to the terms of the enclosed +license agreement. The binaries and their matching makefiles will be installed +in the <code>vendor/</code> hierarchy of the source tree.</p> <h3 id="cleaning-up">Clean up</h3> @@ -68,8 +68,8 @@ make clobber <h2 id="initialize">Set up environment</h2> <p>Initialize the environment with the <code>envsetup.sh</code> script. Note -that replacing <code>source</code> with <code>.</code> (a single dot) saves a few characters, -and the short form is more commonly used in documentation.</p> +that replacing <code>source</code> with <code>.</code> (a single dot) saves a +few characters, and the short form is more commonly used in documentation.</p> <pre class="devsite-terminal devsite-click-to-copy"> source build/envsetup.sh </pre> @@ -79,18 +79,17 @@ source build/envsetup.sh </pre> <h2 id="choose-a-target">Choose a target</h2> -<p>Choose which target to build with <code>lunch</code>. The exact configuration can be passed as -an argument. For example, the following command:</p> +<p>Choose which target to build with <code>lunch</code>. The exact configuration +can be passed as an argument. For example, the following command refers to a +complete build for the emulator, with all debugging enabled:</p> <pre class="devsite-terminal devsite-click-to-copy"> lunch aosp_arm-eng </pre> -<p>refers to a complete build for the emulator, with all debugging enabled.</p> <p>If run with no arguments <code>lunch</code> will prompt you to choose a target from the menu.</p> <p>All build targets take the form <code>BUILD-BUILDTYPE</code>, where the -<code>BUILD</code> is a codename referring to the particular feature combination.</p> - -<p>The BUILDTYPE is one of the following:</p> +<code>BUILD</code> is a codename referring to the particular feature +combination. The BUILDTYPE is one of the following:</p> <table> <thead> <tr> @@ -105,7 +104,8 @@ target from the menu.</p> </tr> <tr> <td>userdebug</td> -<td>like "user" but with root access and debuggability; preferred for debugging</td> +<td>like user but with root access and debuggability; preferred for +debugging</td> </tr> <tr> <td>eng</td> @@ -118,7 +118,7 @@ target from the menu.</p> <h2 id="build-the-code">Build the code</h2> -<p>Please note, this section is merely a summary to ensure setup is complete. See +<p>This section is merely a summary to ensure setup is complete. See <a href="running.html">Running Builds</a> for detailed instructions on building Android.</p> @@ -141,11 +141,11 @@ note that you have already selected your build target with <code>lunch</code>, and it is unlikely at best to run on a different target than it was built for.</p> -<p class="note"><strong>Note:</strong> Remember to <a +<aside class="note"><strong>Note:</strong> Remember to <a href="#obtaining-proprietary-binaries">obtain proprietary binaries</a> or your build will not boot successfully on your target hardware. If you obtain binary blobs at this point you will need to unpack them, <code>make clobber</code> and -rebuild.</p> +rebuild.</aside> <h3 id="flash-a-device">Flash with fastboot</h3> @@ -154,7 +154,7 @@ be included in your path after a successful build. See <a href="running.html#flashing-a-device">Flashing a device</a> for instructions.</p> -<h3 id="emulate-an-android-device">Emulate an Android Device</h3> +<h3 id="emulate-an-android-device">Emulate an Android device</h3> <p>The emulator is added to your path automatically by the build process. To run the emulator, type:</p> @@ -163,9 +163,10 @@ run the emulator, type:</p> emulator </pre> -<h2 id="troubleshooting-common-build-errors">Troubleshooting Common Build Errors</h2> +<h2 id="troubleshooting-common-build-errors">Troubleshooting common build +errors</h2> -<h3 id="wrong-java-version">Wrong Java Version</h3> +<h3 id="wrong-java-version">Wrong Java version</h3> <p>If you are attempting to build a version of Android inconsistent with your version of Java, <code>make</code> will abort with a message such as</p> @@ -191,7 +192,7 @@ href="requirements.html#jdk">JDK Requirements</a>.</li> correct JDK to the beginning of your PATH or remove the problematic JDK.</li> </ul> -<h3 id="python-version-3">Python Version 3</h3> +<h3 id="python-version-3">Python version 3</h3> <p>Repo is built on particular functionality from Python 2.x and is unfortunately incompatible with Python 3. In order to use repo, please install @@ -201,19 +202,20 @@ Python 2.x:</p> apt-get install python </pre> -<h3 id="case-insensitive-filesystem">Case Insensitive Filesystem</h3> +<h3 id="case-insensitive-filesystem">Case insensitive filesystem</h3> -<p>If you are building on an HFS filesystem on Mac OS, you may encounter an error such as</p> +<p>If you are building on an HFS filesystem on Mac OS, you may encounter an +error such as</p> <pre> ************************************************************ You are building on a case-insensitive filesystem. Please move your source tree to a case-sensitive filesystem. ************************************************************ </pre> -<p>Please follow the instructions in <a href="initializing.html">Initializing -the Build Environment</a> for creating a case-sensitive disk image.</p> +<p>Please follow the instructions in <a href="initializing.html">Establishing a +Build Environment</a> for creating a case-sensitive disk image.</p> -<h3 id="no-usb-permission">No USB Permission</h3> +<h3 id="no-usb-permission">No USB permission</h3> <p>On most Linux systems, unprivileged users cannot access USB ports by default. If you see a permission denied error, follow the instructions diff --git a/en/setup/devices.html b/en/setup/build/devices.html index ed4d1e7e..01dee33b 100644 --- a/en/setup/devices.html +++ b/en/setup/build/devices.html @@ -25,8 +25,8 @@ <p>You can create builds for Nexus devices using Android Open Source Project (AOSP) builds and the relevant hardware-specific binaries. For available Android builds and targeted devices, see -<a href="/setup/build-numbers.html#source-code-tags-and-builds">Source Code, -Tags, and Builds</a>.</p> +<a href="../start/build-numbers.html#source-code-tags-and-builds">Source Code +Tags and Builds</a>.</p> <p>You can also create builds for <a href="https://android.googlesource.com/device/linaro/hikey/" class="external">HiKey</a> @@ -53,18 +53,20 @@ or HiKey960 development board.</p> and from <a href="http://www.lenovator.com/product/80.html" class="external">Lenovator<a/>. </p> -<img src="images/hikey960.png" alt="HiKey960 board image" /> +<img src="../images/hikey960.png" alt="HiKey960 board image" /> <figcaption><strong>Figure 1.</strong> HiKey960 board by Lenovator</figcaption> -<p>Additional resources:</p> +<h3 id="additional-resources">Additional resources</h3> <ul> <li> -<a href="https://github.com/96boards/documentation/blob/master/ConsumerEdition/HiKey960/HardwareDocs/HiKey960_Schematics.pdf" class="external">HiKey960 +<a href="https://github.com/96boards/documentation/blob/master/consumer/hikey960/hardware-docs/HiKey960_Schematics.pdf" class="external">HiKey960 schematics</a></li> <li> -<a href="http://www.96boards.org/documentation/ConsumerEdition/HiKey960/HardwareDocs/HardwareUserManual.md/" class="external">HiKey960 +<a href="https://github.com/96boards/documentation/blob/master/consumer/hikey960/hardware-docs/hardware-user-manual.md" class="external">HiKey960 user guide</a></li> <li> +<a href="https://github.com/96boards/documentation/tree/master/consumer/hikey960/hardware-docs" class="external">HiKey960 Hardware Docs directory</a></li> +<li> <a href="https://github.com/96boards/documentation/wiki/" class="external">96boards wiki</a></li> </ul> @@ -79,13 +81,6 @@ HiKey960 board.</p> <code class="devsite-terminal">repo sync -j24</code> </pre> </li> - <li>Download and extract binaries into the Android source tree: -<pre class="devsite-click-to-copy"> -<code class="devsite-terminal">wget https://dl.google.com/dl/android/aosp/arm-hikey960-OPR-cf4e0c80.tgz</code> -<code class="devsite-terminal">tar xzf arm-hikey960-OPR-cf4e0c80.tgz</code> -<code class="devsite-terimnal">./extract-arm-hikey960.sh</code> -</pre> - </li> <li>Build: <pre class="devsite-click-to-copy"> <code class="devsite-terminal">. ./build/envsetup.sh</code> @@ -117,6 +112,7 @@ HiKey960 user guide).</li> <code class="devsite-terminal">fastboot flash boot out/target/product/hikey960/boot.img</code> <code class="devsite-terminal">fastboot flash dts out/target/product/hikey960/dt.img</code> <code class="devsite-terminal">fastboot flash system out/target/product/hikey960/system.img</code> +<code class="devsite-terminal">fastboot flash vendor out/target/product/hikey960/vendor.img</code> <code class="devsite-terminal">fastboot flash cache out/target/product/hikey960/cache.img</code> <code class="devsite-terminal">fastboot flash userdata out/target/product/hikey960/userdata.img</code> </pre> @@ -174,7 +170,7 @@ and <a href="http://www.lenovator.com/product/90.html" class="external">2GB RAM</a> configurations from <a href="http://www.lenovator.com" class="external">Lenovator</a>: </p> -<img src="images/hikey620.png" alt="HiKey620 board image"/> +<img src="../images/hikey620.png" alt="HiKey620 board image"/> <figcaption><strong>Figure 2.</strong> HiKey board by Lenovator</figcaption> <p>Additional resources:</p> @@ -200,13 +196,6 @@ board.</p> <code class="devsite-terminal">repo sync -j24</code> </pre> </li> - <li>Download and extract HDMI binaries into the Android source tree: -<pre class="devsite-click-to-copy"> -<code class="devsite-terminal">wget <a href="https://dl.google.com/dl/android/aosp/linaro-hikey-20170523-4b9ebaff.tgz">https://dl.google.com/dl/android/aosp/linaro-hikey-20170523-4b9ebaff.tgz</a></code> -<code class="devsite-terminal">tar xzf linaro-hikey-20170523-4b9ebaff.tgz</code> -<code class="devsite-terminal">./extract-linaro-hikey.sh</code> -</pre> - </li> <li>Install mcopy utility: <pre class="devsite-terminal devsite-click-to-copy"> apt-get install mtools @@ -267,8 +256,8 @@ user guide</a>).</li> <ul> <li>Copy hi6220-hikey.dtb (<code>arch/arm64/boot/dts/hisilicon/hi6220-hikey.dtb</code>) to the hikey-kernel directory as file hi6220-hikey.dtb-4.9.</li> - <li>Copy the Image file <code>(arch/arm64/boot/Image-dtb</code>) to the -hikey-kernel directory as file Image-dtb-4.9.</li> + <li>Copy the Image file <code>(arch/arm64/boot/Image.gz-dtb</code>) to the +hikey-kernel directory as file Image.gz-dtb-4.9.</li> </ul> <li>Make the boot image: <pre class="devsite-terminal devsite-click-to-copy"> @@ -293,7 +282,7 @@ user guide</a>.</p> <a href="http://www.96boards.org/product/neonkey/" class="external">Neonkey SensorHub</a> connected to a Hikey or Hikey960 development board.</p> -<img src="images/neonkey-sensorhub.png" alt="Neonkey Sensorhub image" /> +<img src="../images/neonkey-sensorhub.png" alt="Neonkey Sensorhub image" /> <figcaption><strong>Figure 3.</strong> Neonkey SensorHub</figcaption> <p>Neonkey is a certified <a href="http://www.96boards.org/" class="external">96Boards</a> diff --git a/en/setup/downloading.html b/en/setup/build/downloading.html index 7599338b..0d53f39b 100644 --- a/en/setup/downloading.html +++ b/en/setup/build/downloading.html @@ -38,7 +38,7 @@ </h2> <p> Repo is a tool that makes it easier to work with Git in the context of Android. For more - information about Repo, see the <a href="developing.html">Developing</a> section. + information about Repo, see the <a href="../develop/repo.html">Repo Command Reference</a>. </p> <p> To install Repo: @@ -114,7 +114,8 @@ repo init -u https://android.googlesource.com/platform/manifest </pre> <p> - To check out a branch other than "master", specify it with <code>-b</code>. For a list of branches, see <a href="build-numbers.html#source-code-tags-and-builds">Source Code Tags and Builds</a>. + To check out a branch other than "master", specify it with <code>-b</code>. For a list of branches, see + <a href="../start/build-numbers.html#source-code-tags-and-builds">Source Code Tags and Builds</a>. </p> <pre class="devsite-terminal devsite-click-to-copy"> repo init -u https://android.googlesource.com/platform/manifest -b android-4.0.1_r1 @@ -127,7 +128,7 @@ repo init -u https://android.googlesource.com/platform/manifest -b android-4.0.1 where files such as the manifest will be kept. </p> <h2 id="getting-the-files"> - Downloading the Android Source Tree + Downloading the Android source tree </h2> <p> To pull down the Android source tree to your working directory from the repositories as @@ -137,7 +138,7 @@ repo init -u https://android.googlesource.com/platform/manifest -b android-4.0.1 <p> The Android source files will be located in your working directory under their project names. The initial sync operation will take an hour or more to complete. For more about <code>repo - sync</code> and other Repo commands, see the <a href="developing.html">Developing</a> section. + sync</code> and other Repo commands, see <a href="../develop/index.html">Developing</a>. </p> <h2 id="using-authentication"> Using Authentication @@ -236,7 +237,7 @@ repo init -u https://android.googlesource.com/a/platform/manifest between machines. </p> <h2 id="verifying-git-tags"> - Verifying Git Tags + Verifying Git tags </h2> <p> Load the following public key into your GnuPG key database. The key is used to sign annotated @@ -288,8 +289,8 @@ EXzeoxcdoafxqf6gZlJZlACgkWF7wi2YLW3Oa+jv2QSTlrx4KLM= git tag -v TAG_NAME </pre> <p> - If you haven't <a href="initializing.html#ccache">set up ccache</a> yet, now would be a good - time to do it. + If you haven't <a href="initializing.html#optimizing-a-build-environment">set + up ccache</a> yet, now would be a good time to do it. </p> </body> diff --git a/en/setup/build/initializing.html b/en/setup/build/initializing.html new file mode 100644 index 00000000..503a14ed --- /dev/null +++ b/en/setup/build/initializing.html @@ -0,0 +1,405 @@ +<html devsite> + <head> + <title>Establishing a Build Environment</title> + <meta name="project_path" value="/_project.yaml" /> + <meta name="book_path" value="/_book.yaml" /> + </head> + <body> + <!-- + Copyright 2017 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 + + http://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> + This section describes how to set up your local work environment to build + the Android source files. You must use Linux or Mac OS; building under + Windows is not currently supported. +</p> +<p> + For an overview of the entire code-review and code-update process, see <a + href="../contribute/life-of-a-patch.html">Life of a Patch</a>. +</p> +<aside class="note"><strong>Note:</strong> All commands in this site are + preceded by a dollar sign ($) to differentiate them from output or entries + within files. You may use the <em>Click to copy</em> feature at the top right + of each command box to copy all lines without the dollar signs or triple-click + each line to copy it individually without the dollar sign. +</aside> + +<h2 id="choosing-a-branch">Choosing a branch</h2> +<p> + Some requirements for the build environment are determined by the version of + the source code you plan to compile. For a full list of available branches, + see <a href="../start/build-numbers.html">Build Numbers</a>. You can also + choose to download and build the latest source code (called + <code>master</code>), in which case you will simply omit + the branch specification when you initialize the repository. +</p> +<p> + After you have selected a branch, follow the appropriate instructions below to + set up your build environment. +</p> + +<h2 id="setting-up-a-linux-build-environment">Setting up a Linux build +environment</h2> +<p> + These instructions apply to all branches, including <code>master</code>. +</p> +<p>The Android build is routinely tested in house on recent versions of + Ubuntu LTS (14.04), but most distributions should have the required + build tools available. Reports of successes or failures on other + distributions are welcome. +</p> +<p> + For Gingerbread (2.3.x) and newer versions, including the <code>master</code> + branch, a 64-bit environment is required. Older versions can be + compiled on 32-bit systems. +</p> +<aside class="note"><strong>Note:</strong> See + <a href="requirements.html">Requirements</a> for the complete list of hardware + and software requirements, then follow the detailed instructions for Ubuntu + and Mac OS below. +</aside> + +<h3 id="installing-the-jdk">Installing the JDK</h3> +<p> + The <code>master</code> branch of Android in the + <a href="https://android.googlesource.com/" class="external">Android Open + Source Project (AOSP)</a> comes with prebuilt versions of OpenJDK below + <code>prebuilts/jdk/</code> so no additional installation is required. +</p> +<p> + Older versions of Android require a separate installation of the JDK. On + Ubuntu, use + <a href="http://openjdk.java.net/install/" class="external">OpenJDK</a>. See + <a href="requirements.html#jdk">JDK Requirements</a> for precise versions and + the sections below for instructions. +</p> +<h4 id="for-ubuntu-15-04">For Ubuntu >= 15.04</h4> +<p> + Run the following: +</p> +<pre class="devsite-click-to-copy"> +<code class="devsite-terminal">sudo apt-get update</code> +<code class="devsite-terminal">sudo apt-get install openjdk-8-jdk</code> +</pre> + +<h4 id="for-ubuntu-14-04">For Ubuntu LTS 14.04</h4> +<p> + There are no available supported OpenJDK 8 packages for Ubuntu 14.04. The + <strong>Ubuntu 15.04 OpenJDK 8</strong> packages have been used successfully + with Ubuntu 14.04. <em>Newer package versions (e.g. those for 15.10, 16.04) were + found not to work on 14.04 using the instructions below.</em> +</p> +<ol> + <li>Download the <code>.deb</code> packages for 64-bit architecture from + <a href="http://old-releases.ubuntu.com/ubuntu/pool/universe/o/openjdk-8/">old-releases.ubuntu.com</a>: + <ul> + <li><a + href="http://old-releases.ubuntu.com/ubuntu/pool/universe/o/openjdk-8/openjdk-8-jre-headless_8u45-b14-1_amd64.deb">openjdk-8-jre-headless_8u45-b14-1_amd64.deb</a> + with SHA256 <code>0f5aba8db39088283b51e00054813063173a4d8809f70033976f83e214ab56c0</code> + </li> + <li><a + href="http://old-releases.ubuntu.com/ubuntu/pool/universe/o/openjdk-8/openjdk-8-jre_8u45-b14-1_amd64.deb">openjdk-8-jre_8u45-b14-1_amd64.deb</a> + with SHA256 <code>9ef76c4562d39432b69baf6c18f199707c5c56a5b4566847df908b7d74e15849</code> + </li> + <li><a + href="http://old-releases.ubuntu.com/ubuntu/pool/universe/o/openjdk-8/openjdk-8-jdk_8u45-b14-1_amd64.deb">openjdk-8-jdk_8u45-b14-1_amd64.deb</a> + with SHA256 <code>6e47215cf6205aa829e6a0a64985075bd29d1f428a4006a80c9db371c2fc3c4c</code> + </li> + </ul> + </li> + <li>Optionally, confirm the checksums of the downloaded files against the + SHA256 string listed with each package above. For example, with the + <code>sha256sum</code> tool: + <pre class="devsite-terminal devsite-click-to-copy"> + sha256sum {downloaded.deb file}</pre> + </li> + <li>Install the packages: + <pre class="devsite-terminal devsite-click-to-copy"> + sudo apt-get update</pre> + Run <code>dpkg</code> for each of the .deb files you downloaded. It may + produce errors due to missing dependencies: + <pre class="devsite-terminal devsite-click-to-copy"> + sudo dpkg -i {downloaded.deb file}</pre> + To fix missing dependencies: + <pre class="devsite-terminal devsite-click-to-copy"> + sudo apt-get -f install</pre> + </li> +</ol> + +<h4 id="default-java-version">Update the default Java version - optional</h4> +<p> + Optionally, for the Ubuntu versions above update the default Java version by + running: +</p> +<pre class="devsite-click-to-copy"> +<code class="devsite-terminal">sudo update-alternatives --config java</code> +<code class="devsite-terminal">sudo update-alternatives --config javac</code> +</pre> +<p> + If, during a build, you encounter version errors for Java, set its + path as described in the <a href="building.html#wrong-java-version">Wrong + Java Version</a> section. +</p> + +<h3 id="installing-required-packages-ubuntu-1404">Installing required packages +(Ubuntu 14.04)</h3> +<p> + You will need a 64-bit version of Ubuntu. Ubuntu 14.04 is recommended. +</p> +<pre class="devsite-terminal devsite-click-to-copy"> +sudo apt-get install git-core gnupg flex bison gperf build-essential zip curl zlib1g-dev gcc-multilib g++-multilib libc6-dev-i386 lib32ncurses5-dev x11proto-core-dev libx11-dev lib32z-dev ccache libgl1-mesa-dev libxml2-utils xsltproc unzip +</pre> +<aside class="note"><strong>Note:</strong> To use SELinux tools for policy + analysis, also install the <code>python-networkx</code> package. +</aside> +<aside class="note"><strong>Note:</strong> If you are using LDAP and want + to run ART host tests, also install the <code>libnss-sss:i386</code> + package. +</aside> + +<h3 id="installing-required-packages-ubuntu-1204">Installing required packages + (Ubuntu 12.04) +</h3> +<p> + You may use Ubuntu 12.04 to build older versions of Android. Version 12.04 + is not supported on master or recent releases. +</p> +<pre class="devsite-click-to-copy"> +<code class="devsite-terminal">sudo apt-get install git gnupg flex bison gperf build-essential zip curl libc6-dev libncurses5-dev:i386 x11proto-core-dev libx11-dev:i386 libreadline6-dev:i386 libgl1-mesa-glx:i386 libgl1-mesa-dev g++-multilib mingw32 tofrodos python-markdown libxml2-utils xsltproc zlib1g-dev:i386</code> +<code class="devsite-terminal">sudo ln -s /usr/lib/i386-linux-gnu/mesa/libGL.so.1 /usr/lib/i386-linux-gnu/libGL.so</code> +</pre> + +<h3 id="installing-required-packages-ubuntu-1004-1110">Installing required + packages (Ubuntu 10.04 -- 11.10) +</h3> +<p> + Building on Ubuntu 10.04-11.10 is no longer supported, but may be useful for + building older releases of AOSP. +</p> +<pre class="devsite-terminal devsite-click-to-copy"> +sudo apt-get install git gnupg flex bison gperf build-essential zip curl zlib1g-dev libc6-dev lib32ncurses5-dev ia32-libs x11proto-core-dev libx11-dev lib32readline5-dev lib32z-dev libgl1-mesa-dev g++-multilib mingw32 tofrodos python-markdown libxml2-utils xsltproc +</pre> +<p> + On Ubuntu 10.10: +</p> +<pre class="devsite-terminal devsite-click-to-copy"> +sudo ln -s /usr/lib32/mesa/libGL.so.1 /usr/lib32/mesa/libGL.so +</pre> +<p> + On Ubuntu 11.10: +</p> +<pre class="devsite-terminal devsite-click-to-copy"> +sudo apt-get install libx11-dev:i386 +</pre> + +<h3 id="configuring-usb-access">Configuring USB access</h3> +<p> + Install a community-maintained default set of <code>udev</code> rules for + all Android devices by following the instructions to <a + href="https://developer.android.com/studio/run/device.html#setting-up" + class="external">Set up a device for development</a>. +</p> + +<h3 id="using-a-separate-output-directory">Using a separate output +directory</h3> +<p> + By default, the output of each build is stored in the <code>out/</code> + subdirectory of the matching source tree. +</p> +<p> + On some machines with multiple storage devices, builds are + faster when storing the source files and the output on + separate volumes. For additional performance, the output + can be stored on a filesystem optimized for speed instead + of crash robustness, since all files can be re-generated + in case of filesystem corruption. +</p> +<p> + To set this up, export the <code>OUT_DIR_COMMON_BASE</code> variable + to point to the location where your output directories + will be stored. +</p> +<pre class="devsite-terminal devsite-click-to-copy"> +export OUT_DIR_COMMON_BASE=<path-to-your-out-directory> +</pre> +<p> + The output directory for each separate source tree will be named after the + directory holding the source tree. For instance, if you have source trees as + <code>/source/master1</code> and <code>/source/master2</code> and + <code>OUT_DIR_COMMON_BASE</code> is set to <code>/output</code>, the output + directories will be <code>/output/master1</code> and + <code>/output/master2</code>. +</p> +<p> + It's important in that case to not have multiple source + trees stored in directories that have the same name, + as those would end up sharing an output directory, with + unpredictable results. This is only supported on Jelly Bean (4.1) and newer, + including the <code>master</code> branch. +</p> +<h2 id="setting-up-a-mac-os-x-build-environment">Setting up a Mac OS build + environment +</h2> +<p> + In a default installation, Mac OS runs on a case-preserving but + case-insensitive filesystem. This type of filesystem is not supported by git + and will cause some git commands (such as <code>git status</code>) to behave + abnormally. Because of this, we recommend that you always work with the AOSP + source files on a case-sensitive filesystem. This can be done fairly easily + using a disk image, discussed below. +</p> +<p> + Once the proper filesystem is available, building the <code>master</code> + branch in a modern Mac OS environment is very straightforward. Earlier + branches require some additional tools and SDKs. +</p> + +<h3 id="creating-a-case-sensitive-disk-image">Creating a case-sensitive disk +image</h3> +<p> + You can create a case-sensitive filesystem within your existing Mac OS + environment using a disk image. To create the image, launch Disk + Utility and select "New Image". A size of 25GB is the minimum to + complete the build; larger numbers are more future-proof. Using sparse images + saves space while allowing to grow later as the need arises. Be sure to select + "case sensitive, journaled" as the volume format. +</p> +<p> + You can also create it from a shell with the following command: +</p> +<pre class="devsite-click-to-copy devsite-terminal" data-terminal-prefix="# "> +hdiutil create -type SPARSE -fs 'Case-sensitive Journaled HFS+' -size 40g ~/android.dmg +</pre> +<p> + This will create a <code>.dmg</code> (or possibly a + <code>.dmg.sparseimage</code>) file which, once mounted, acts as a drive with + the required formatting for Android development. +</p> +<p> + If you need a larger volume later, you can also resize the sparse image with + the following command: +</p> +<pre class="devsite-click-to-copy devsite-terminal" data-terminal-prefix="# ">hdiutil resize -size <new-size-you-want>g ~/android.dmg.sparseimage +</pre> +<p> + For a disk image named <code>android.dmg</code> stored in your home + directory, you can add helper functions to your <code>~/.bash_profile</code>: +</p> +<ul> + <li>To mount the image when you execute <code>mountAndroid</code>: + <pre class="devsite-click-to-copy"> + # mount the android file image + mountAndroid() { hdiutil attach ~/android.dmg -mountpoint /Volumes/android; }</pre> + <aside class="note"><strong>Note:</strong> If your system created a + <code>.dmg.sparseimage</code> file, replace <code>~/android.dmg</code> with + <code>~/android.dmg.sparseimage</code>. + </aside> + </li> + <li>To unmount it when you execute <code>umountAndroid</code>: + <pre class="devsite-click-to-copy"> + # unmount the android file image + umountAndroid() { hdiutil detach /Volumes/android; }</pre> + </li> +</ul> +<p> + After you've mounted the <code>android</code> volume, you'll do all your work + there. You can eject it (unmount it) just as you would an external drive. +</p> + +<h3 id="installing-the-mac-jdk">Installing the JDK</h3> +<p> + See <a href="requirements.html">Requirements</a> for the version of Java to + use when developing various versions of Android. +</p> + +<h4 id="installing-required-packages">Installing required packages</h4> +<ol> + <li>Install Xcode command line tools with: + <pre class="devsite-terminal devsite-click-to-copy"> + xcode-select --install</pre> + For older versions of Mac OS (10.8 or earlier), you must install Xcode from + the <a href="http://developer.apple.com/" class="external">Apple developer + site</a>. If you are not already registered as an Apple developer, you must + must create an Apple ID to download. + </li> + <li>Install MacPorts from + <a href="http://www.macports.org/install.php">macports.org</a>. Ensure + <code>/opt/local/bin</code> appears in your path <strong>before</strong> + <code>/usr/bin</code>. If not, add the following to your + <code>~/.bash_profile</code> file: + <pre class="devsite-click-to-copy"> + export PATH=/opt/local/bin:$PATH</pre> + <aside class="note"><strong>Note:</strong> If you do not have a + <code>.bash_profile</code> file in your home directory, create one. + </aside> + </li> + <li>Get make, git, and GPG packages from MacPorts: + <pre class="devsite-terminal devsite-click-to-copy"> + POSIXLY_CORRECT=1 sudo port install gmake libsdl git gnupg</pre> + If using Mac OS X v10.4, also install bison: + <pre class="devsite-terminal devsite-click-to-copy"> + POSIXLY_CORRECT=1 sudo port install bison</pre> + </li> +</ol> + +<h4 id="reverting-from-make-382">Reverting from make 3.82</h4> +<p> + In Android 4.0.x (Ice Cream Sandwich) and earlier, a bug exists in gmake 3.82 + that prevents Android from building. You can install version 3.81 using + MacPorts with these steps: +</p> +<ol> + <li>Edit <code>/opt/local/etc/macports/sources.conf</code> and add a line that + says: + <pre class="devsite-click-to-copy"> + file:///Users/Shared/dports</pre> + above the rsync line. Then create this directory: + <pre class="devsite-terminal devsite-click-to-copy"> + mkdir /Users/Shared/dports</pre> + </li> + <li>In the new <code>dports</code> directory, run: + <pre class="devsite-terminal devsite-click-to-copy"> + svn co --revision 50980 http://svn.macports.org/repository/macports/trunk/dports/devel/gmake/ devel/gmake/</pre> + </li> + <li>Create a port index for your new local repository: + <pre class="devsite-terminal devsite-click-to-copy"> + portindex /Users/Shared/dports</pre> + </li> + <li>Install the old version of gmake with: + <pre class="devsite-terminal devsite-click-to-copy"> + sudo port install gmake @3.81</pre> + </li> +</ol> + +<h4 id="setting-a-file-descriptor-limit">Setting a file descriptor limit</h4> +<p> + On Mac OS, the default limit on the number of simultaneous file descriptors + open is too low and a highly parallel build process may exceed this limit. To + increase the cap, add the following lines to your + <code>~/.bash_profile</code>: +</p> +<pre class="devsite-click-to-copy"> +# set the number of open files to be 1024 +ulimit -S -n 1024</pre> + +<h2 id="next-download-the-source">Next: Download the source</h2> +<p> + Your build environment is good to go! Proceed to + <a href="downloading.html">downloading the source</a>. +</p> + + </body> +</html> diff --git a/en/setup/jack.html b/en/setup/build/jack.html index 558eef73..5d32cb3e 100644 --- a/en/setup/jack.html +++ b/en/setup/build/jack.html @@ -37,10 +37,10 @@ build toolchain for Android 6.x, you don’t have to do anything differently to use Jack—just use your standard makefile commands to compile the tree or your project.</p> -<h2 class="overview">About Jack</h2> +<h2 id="overview">About Jack</h2> <p>The Jack toolchain provides the following advantages:</p> -<img src="./images/jack_overview.png" alt="Jack overview"/> +<img src="../images/jack_overview.png" alt="Jack overview"/> <figcaption><strong>Figure 1.</strong> Jack overview.</figcaption> <ul> @@ -65,7 +65,7 @@ Coverage with JaCoCo</a> and <p>Jack has its own .jack file format that contains the pre-compiled dex code for the library, allowing for faster compilation (pre-dex).</p> -<img src="./images/jack_library.png" alt="Jack library file contents"/> +<img src="../images/jack_library.png" alt="Jack library file contents"/> <figcaption><strong>Figure 2.</strong> Jack library file contents.</figcaption> <h3 id=jill>Jill</h3> @@ -73,7 +73,7 @@ for the library, allowing for faster compilation (pre-dex).</p> <p>The Jill tool translates the existing .jar libraries into the new library format, as shown below.</p> -<img src="./images/jack_jill.png" alt="Importing .jar libraries with Jill"/> +<img src="../images/jack_jill.png" alt="Importing .jar libraries with Jill"/> <figcaption><strong>Figure 3.</strong> Workflow to import an existing .jar library.</figcaption> @@ -234,11 +234,12 @@ features described below.</p> <h3 id=predexing>Predexing</h3> -<p>When generating a Jack library file, the .dex of the library is generated and -stored inside the .jack library file as a pre-dex. When compiling, Jack reuses -the pre-dex from each library. All libraries are pre-dexed:</p> +<p>When generating a Jack library file, the <code>.dex</code> of the library is +generated and stored inside the <code>.jack</code> library file as a pre-dex. +When compiling, Jack reuses the pre-dex from each library. All libraries are +pre-dexed:</p> -<img src="./images/jack_predex.png" alt="Jack libraries with pre-dex" /> +<img src="../images/jack_predex.png" alt="Jack libraries with pre-dex" /> <figcaption><strong>Figure 4.</strong> Jack libraries with pre-dex.</figcaption> <p>Jack does not reuse the library pre-dex if shrinking, obfuscation, or diff --git a/en/setup/known-issues.html b/en/setup/build/known-issues.html index e72de555..e72de555 100644 --- a/en/setup/known-issues.html +++ b/en/setup/build/known-issues.html diff --git a/en/setup/build/requirements.html b/en/setup/build/requirements.html new file mode 100644 index 00000000..0a1f4259 --- /dev/null +++ b/en/setup/build/requirements.html @@ -0,0 +1,198 @@ +<html devsite> + <head> + <title>Requirements</title> + <meta name="project_path" value="/_project.yaml" /> + <meta name="book_path" value="/_book.yaml" /> + </head> + <body> + <!-- + Copyright 2017 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 + + http://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> + Before you download and build the Android source, ensure your system meets + the following requirements then see <a href="initializing.html">Establishing + a Build Environment</a> for installation instructions by operating system. +</p> + +<h2 id=hardware-requirements>Hardware requirements</h2> +<p> + Your development workstation should meet or exceed these hardware + requirements: +</p> +<ul> + <li>A 64-bit environment is required for Android 2.3.x (Gingerbread) and + higher versions, including the master branch. You can compile older versions + on 32-bit systems. + </li> + <li>At least 100GB of free disk space to checkout the code and an extra 150GB + to build it. If you conduct multiple builds or employ ccache, you will need + even more space. + </li> + <li>If you are running Linux in a virtual machine, you need at + least 16GB of RAM/swap. + </li> +</ul> + +<h2 id=software-requirements>Software requirements</h2> +<p> + The <a href="https://android.googlesource.com/" class="external">Android Open + Source Project (AOSP)</a> <code>master</code> branch is traditionally + developed and tested on Ubuntu Long Term Support (LTS) releases, but other + distributions may be used. See the list below for recommended versions. +</p> +<p> + Your workstation must have the software listed below. See + <a href="initializing.html">Establishing a Build Environment</a> for + additional required packages and the commands to install them. +</p> + +<h3 id=latest-version>OS and JDK</h3> +<p> + If you are developing against the AOSP <code>master</code> branch, use one + of these operating systems: Ubuntu 14.04 (Trusty) or Mac OS v10.10 (Yosemite) + or later with Xcode 4.5.2 and Command Line Tools. +</p> +<p> + For the Java Development Kit (JDK), note the <code>master</code> branch of + Android in AOSP comes with a prebuilt version of OpenJDK; so no additional + installation is required. Older versions require a separate install. +</p> +<p>See <a href="#older-versions">Packages for older versions</a>. + +<h3 id=packages>Key packages</h3> +<ul> + <li>Python 2.6 to 2.7 from <a href="http://www.python.org/download/" class="external">python.org</a></li> + <li>GNU Make 3.81 to 3.82 from <a href="http://ftp.gnu.org/gnu/make/" class="external">gnu.org</a></li> + <li>Git 1.7 or newer from <a href="http://git-scm.com/download" class="external">git-scm.com</a></li> +</ul> + +<h3 id=binaries>Device binaries</h3> +<p> + Download previews, factory images, drivers, over-the-air (OTA) updates, and + other blobs below. For details, see + <a href="building.html#obtaining-proprietary-binaries">Obtaining proprietary + binaries</a>. +</p> +<ul> + <li><a href="https://developers.google.com/android/blobs-preview" class="external">Preview + binaries (blobs)</a>. For AOSP <code>master</code> branch development. + </li> + <li><a href="https://developers.google.com/android/images" class="external">Factory + images</a>. For supported devices running tagged AOSP release branches. + </li> + <li><a href="https://developers.google.com/android/drivers" class="external">Binary + hardware support files</a>. For devices running tagged AOSP release + branches. + </li> +</ul> + +<h3 id=toolchain>Build toolchain</h3> +<p> + Android 8.0 and higher support only + <a href="https://developer.android.com/ndk/guides/standalone_toolchain.html#working_with_clang" class="external">Clang/LLVM</a> + for building the Android platform. Join the + <a href="https://groups.google.com/forum/#!forum/android-llvm" class="external">android-llvm</a> + group to pose questions and get help. Report NDK/compiler issues at the + <a href="https://github.com/android-ndk/ndk" class="external">NDK GitHub</a>. +</p> +<p> + For the + <a href="https://developer.android.com/ndk/guides/index.html" class="external">Native + Development Kit (NDK)</a> and legacy kernels, GCC 4.9 included in the AOSP + master branch (under <code>prebuilts/</code>) may also be used. +</p> + +<h3 id=older-versions>Packages for older versions</h3> +<p> + This section details operating systems and JDK packages for older versions of + Android. +</p> + +<h4 id=operating-systems>Operating systems</h4> +<p> + Android is typically built with a GNU/Linux or Mac OS operating system. It is + also possible to build Android in a virtual machine on unsupported systems + such as Windows. +</p> + +<p>We recommend building on GNU/Linux instead of another operating system. The + Android build system normally uses ART, running on the build machine, to + pre-compile system dex files. Since ART is able to run only on Linux, the + build system skips this pre-compilation step on non-Linux operating systems, + resulting in an Android build with reduced performance. +</p> + +<h5 id=linux>GNU/Linux</h5> +<ul> + <li>Android 6.0 (Marshmallow) - AOSP master: Ubuntu 14.04 (Trusty)</li> + <li>Android 2.3.x (Gingerbread) - Android 5.x (Lollipop): Ubuntu 12.04 + (Precise)</li> + <li>Android 1.5 (Cupcake) - Android 2.2.x (Froyo): Ubuntu 10.04 (Lucid)</li> +</ul> +<h5 id=mac>Mac OS (Intel/x86)</h5> +<ul> + <li>Android 6.0 (Marshmallow) - AOSP master: Mac OS v10.10 (Yosemite) or + higher with Xcode 4.5.2 and Command Line Tools + </li> + <li>Android 5.x (Lollipop): Mac OS v10.8 (Mountain Lion) with Xcode 4.5.2 + and Command Line Tools + </li> + <li>Android 4.1.x-4.3.x (Jelly Bean) - Android 4.4.x (KitKat): Mac OS v10.6 + (Snow Leopard) or Mac OS X v10.7 (Lion) and Xcode 4.2 (Apple's Developer + Tools) + </li> + <li>Android 1.5 (Cupcake) - Android 4.0.x (Ice Cream Sandwich): Mac OS + v10.5 (Leopard) or Mac OS X v10.6 (Snow Leopard) and the Mac OS X v10.5 + SDK + </li> +</ul> + +<h4 id=jdk>JDK</h4> +<p> + See <a href="initializing.html#installing-the-jdk">Installing the JDK</a> + for the prebuilt path and installation instructions for older versions. +</p> +<ul> + <li>Android 7.0 (Nougat) - Android 8.0 (Oreo): Ubuntu - + <a href="http://openjdk.java.net/install/" class="external">OpenJDK 8</a>, + Mac OS - + <a href="http://www.oracle.com/technetwork/java/javase/downloads/java-archive-javase8-2177648.html#jdk-8u45-oth-JPR" class="external">jdk + 8u45 or newer</a> + </li> + <li>Android 5.x (Lollipop) - Android 6.0 (Marshmallow): Ubuntu - + <a href="http://openjdk.java.net/install/" class="external">OpenJDK 7</a>, + Mac OS - + <a href="https://www.oracle.com/technetwork/java/javase/downloads/java-archive-downloads-javase7-521261.html#jdk-7u71-oth-JPR" class="external">jdk-7u71-macosx-x64.dmg</a> + </li> + <li>Android 2.3.x (Gingerbread) - Android 4.4.x (KitKat): Ubuntu - + <a href="http://www.oracle.com/technetwork/java/javase/archive-139210.html" class="external">Java + JDK 6</a>, Mac OS - <a href="http://support.apple.com/kb/dl1572" class="external">Java JDK + 6</a> + </li> + <li>Android 1.5 (Cupcake) - Android 2.2.x (Froyo): Ubuntu - + <a href="http://www.oracle.com/technetwork/java/javase/archive-139210.html" class="external">Java + JDK 5</a> + </li> +</ul> + +<h4 id=make>Make</h4> +<p> + To avoid build errors, Android 4.0.x (Ice Cream Sandwich) and earlier must + <a href="initializing.html#reverting-from-make-382">revert from make 3.82</a>. +</p> + + </body> +</html> diff --git a/en/setup/running.html b/en/setup/build/running.html index e3d9f62d..6d6041f9 100644 --- a/en/setup/running.html +++ b/en/setup/build/running.html @@ -24,13 +24,13 @@ <p>This page provides details for running builds on specific devices and -complements the information in <a href="/setup/building.html">Building the -System</a>.</p> +complements the information in <a href="building.html">Preparing to Build</a>. +</p> <h2 id="building-fastboot-and-adb">Building fastboot and adb</h2> <p>If you don't already have <code>fastboot</code> and <code>adb</code>, you can build them with the regular build system. Use the instructions in -<a href="/setup/building.html">Building a System</a> and replace the +<a href="building.html">Preparing to Build</a> and replace the main <code>make</code> command with:</p> <pre class="devsite-click-to-copy devsite-terminal">make fastboot adb</pre> @@ -283,7 +283,7 @@ following directories:</p> <p>The recommended builds for devices are available from the <code>lunch</code> menu, accessed when running the <code>lunch</code> command with no arguments. You can download factory images and binaries for Nexus devices from -developers.google.com. See <a href="/setup/requirements#binaries">Device +developers.google.com. See <a href="requirements#binaries">Device binaries</a> for downloads. For details and additional resources, see <a href="building.html#obtaining-proprietary-binaries">Obtaining proprietary binaries</a>. diff --git a/en/setup/code-lines.html b/en/setup/code-lines.html deleted file mode 100644 index b4040abd..00000000 --- a/en/setup/code-lines.html +++ /dev/null @@ -1,187 +0,0 @@ -<html devsite> - <head> - <title>Codelines, Branches, and Releases</title> - <meta name="project_path" value="/_project.yaml" /> - <meta name="book_path" value="/_book.yaml" /> - </head> - <body> - <!-- - Copyright 2017 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 - - http://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> - The Android Open Source Project (AOSP) maintains a complete software stack to be ported by - OEMs and other device implementors and run on their own hardware. To maintain the quality of - Android, Google has contributed full-time engineers, product managers, user interface designers, - quality assurance testers, and all the other roles required to bring modern devices to market. -</p> - -<p> - Accordingly, we maintain a number of "code lines" to clearly separate the current stable - version of Android from unstable experimental work. We roll the open source administration - and maintenance of the Android code lines into the larger product development cycle. -</p> - -<p> - The chart below depicts at a conceptual level how AOSP manages code and releases. We're - referring to these as "code lines" instead of "branches" simply because at any given moment - there may be more than one branch for a given "code line". For instance, when a - release is cut, it may or may not become a new branch based on the needs of the moment. -</p> -<ol> - <li> - <p> - At any given moment, there is a current latest release of the Android platform. This - typically takes the form of a branch in the tree. - </p> - </li> - <li> - <p> - Device builders and contributors work with the current latest release, fixing bugs, - launching new devices, experimenting with new features, and so on. - </p> - </li> - <li> - <p> - In parallel, Google works internally on the next version of the Android platform and - framework according to the product's needs and goals. We develop the next - version of Android by working with a device partner on a flagship device whose - specifications are chosen to push Android in the direction we believe it should go. - </p> - </li> - <li> - <p> - When the "n+1"th version is ready, it will be published to the public source tree and - become the new latest release. - </p> - </li> -</ol> - <img src="/images/code-lines.png" alt="code-line diagram" id="figure1" > -<p class="img-caption"> - <strong>Figure 1.</strong> AOSP code and releases -</p> -<h2 id="terms-and-caveats"> - Terms and Caveats -</h2> -<ul> - <li> - <p> - A <em>release</em> corresponds to a formal version of the Android platform, such as 1.5, - 2.1, and so on. Generally speaking, a release of the platform corresponds to the version in - the <code>SdkVersion</code> field of AndroidManifest.xml files and defined within - <code>frameworks/base/api</code> in the source tree. - </p> - </li> - <li> - <p> - An <em>upstream</em> project is an open source project from which the Android stack is - pulling code. These include obvious projects such as the Linux kernel and WebKit. - Over time we are migrating some of the semi-autonomous Android projects (such as ART, - the Android SDK tools, Bionic, and so on) to work as "upstream" projects. Generally, - these projects are developed entirely in the public tree. For some upstream projects, - development is done by contributing directly to the upstream project itself. See <a href= - "submit-patches.html#upstream-projects">Upstream Projects</a> for details. In both cases, - snapshots will be periodically pulled into releases. - </p> - </li> - <li> - <p> - At all times, a release code-line (which may actually consist of more than one actual - branch in git) is considered the sole canonical source code for a given Android platform - version. OEMs and other groups building devices should pull only from a release branch. - </p> - </li> - <li> - <p> - "Experimental" code-lines are established to capture changes from the community so they can - be iterated on with an eye toward stability. - </p> - </li> - <li> - <p> - Changes that prove stable will eventually be pulled into a release branch. Note this - applies only to bug fixes, application improvements, and other changes that do not affect the - APIs of the platform. - </p> - </li> - <li> - <p> - Changes will be pulled into release branches from upstream projects (including the - Android "upstream" projects) as necessary. - </p> - </li> - <li> - <p> - The "n+1"th version (that is, next major version of the framework and platform APIs) will - be developed by Google internally. See <a href= - "#about-private-code-lines">About Private Codelines</a> for details. - </p> - </li> - <li> - <p> - Changes will be pulled from upstream, release, and experimental branches into Google's - private branch as necessary. - </p> - </li> - <li> - <p> - When the platform APIs for the next version have stabilized and been fully tested, Google - will cut a release of the next platform version. (This specifically refers to a new - <code>SdkVersion</code>.) This will also correspond to the internal code-line being made - a public release branch, and the new current platform code-line. - </p> - </li> - <li> - <p> - When a new platform version is cut, a corresponding experimental code-line will be - created at the same time. - </p> - </li> -</ul> - -<h2 id="about-private-code-lines"> - About Private Codelines -</h2> -<p> - The source management strategy above includes a code-line that Google will keep private. The - reason for this is to focus attention on the current public version of Android. -</p> -<p> - OEMs and other device builders naturally want to ship devices with the latest version of - Android. Similarly, application developers don't want to deal with more platform - versions than strictly necessary. Meanwhile, Google retains responsibility for the strategic - direction of Android as a platform and a product. Our approach focuses on a small number of - flagship devices to drive features while securing protections of Android-related intellectual - property. -</p> -<p> - As a result, Google frequently has possession of confidential information from third parties. - And we must refrain from revealing sensitive features until we've secured the appropriate - protections. In addition, there are real risks to the platform arising from having too many - platform versions extant at once. For these reasons, we have structured the open source - project -- including third-party contributions -- to focus on the currently-public stable - version of Android. "Deep development" on the next version of the platform will happen in - private until it's ready to become an official release. -</p> -<p> - We recognize many contributors will disagree with this approach. We respect others - may have a different point of view; however, this is the approach we feel is best, and - the one we've chosen to implement. -</p> - - </body> -</html> diff --git a/en/setup/community.html b/en/setup/community.html index af0d17ec..13e3e32c 100644 --- a/en/setup/community.html +++ b/en/setup/community.html @@ -42,7 +42,7 @@ Android, see the list of <a href="#resources">resources</a> below.</p> accessories, and meeting compatibility requirements. The Android OS is a Git repository of files and not a single file (.zip/tar/exe/etc.) to download. You can get started with the Android source code by following the instructions on -the <a href="downloading.html">Downloading the Source</a> +the <a href="build/downloading.html">Downloading the Source</a> page. For other information about Android, refer to the following resources.</p> <table class="columns"> @@ -67,7 +67,7 @@ page. For other information about Android, refer to the following resources.</p> <p></p> <h5>Send feedback</h5> -<a href="/setup/report-bugs.html">Report AOSP bug</a><br> +<a href="contribute/report-bugs.html">Report AOSP bug</a><br> <p></p> </td> diff --git a/en/setup/code-style.html b/en/setup/contribute/code-style.html index dbb9887f..ddf945cd 100644 --- a/en/setup/code-style.html +++ b/en/setup/contribute/code-style.html @@ -35,11 +35,11 @@ follow the standard of their choosing, such as the <a href="https://google.github.io/styleguide/javaguide.html">Google Java Style Guide</a>.</p> -<h2 id="java-language-rules">Java Language Rules</h2> +<h2 id="java-language-rules">Java language rules</h2> <p>Android follows standard Java coding conventions with the additional rules described below.</p> -<h3 id="dont-ignore-exceptions">Don't Ignore Exceptions</h3> +<h3 id="dont-ignore-exceptions">Don't ignore exceptions</h3> <p>It can be tempting to write code that completely ignores an exception, such as:</p> <pre><code>void setServerPort(String value) { @@ -121,7 +121,7 @@ void setServerPort(String value) { </li> </ul> -<h3 id="dont-catch-generic-exception">Don't Catch Generic Exception</h3> +<h3 id="dont-catch-generic-exception">Don't catch generic exception</h3> <p>It can also be tempting to be lazy when catching exceptions and do something like this:</p> <pre><code>try { @@ -167,7 +167,7 @@ this level anyway, just let the method throw it.</p> <p>Remember: exceptions are your friend! When the compiler complains you're not catching an exception, don't scowl. Smile: the compiler just made it easier for you to catch runtime problems in your code.</p> -<h3 id="dont-use-finalizers">Don't Use Finalizers</h3> +<h3 id="dont-use-finalizers">Don't use finalizers</h3> <p>Finalizers are a way to have a chunk of code executed when an object is garbage collected. While they can be handy for doing cleanup (particularly of external resources), there are no guarantees as to when a finalizer will be @@ -179,7 +179,7 @@ method needs to be called (see InputStream for an example). In this case it is appropriate but not required to print a short log message from the finalizer, as long as it is not expected to flood the logs.</p> -<h3 id="fully-qualify-imports">Fully Qualify Imports</h3> +<h3 id="fully-qualify-imports">Fully qualify imports</h3> <p>When you want to use class Bar from package foo,there are two possible ways to import it:</p> <ul> @@ -193,16 +193,16 @@ exception is made for java standard libraries (<code>java.util.*</code>, <code>java.io.*</code>, etc.) and unit test code (<code>junit.framework.*</code>).</p> -<h2 id="java-library-rules">Java Library Rules</h2> +<h2 id="java-library-rules">Java library rules</h2> <p>There are conventions for using Android's Java libraries and tools. In some cases, the convention has changed in important ways and older code might use a deprecated pattern or library. When working with such code, it's okay to continue the existing style. When creating new components however, never use deprecated libraries.</p> -<h2 id="java-style-rules">Java Style Rules</h2> +<h2 id="java-style-rules">Java style rules</h2> -<h3 id="use-javadoc-standard-comments">Use Javadoc Standard Comments</h3> +<h3 id="use-javadoc-standard-comments">Use Javadoc standard comments</h3> <p>Every file should have a copyright statement at the top, followed by package and import statements (each block separated by a blank line) and finally the class or interface declaration. In the Javadoc comments, describe what the class @@ -269,17 +269,17 @@ should follow the instructions <a href="http://www.oracle.com/technetwork/java/javase/documentation/index-137868.html">How to Write Doc Comments for the Javadoc Tool</a>.</p> -<h3 id="write-short-methods">Write Short Methods</h3> +<h3 id="write-short-methods">Write short methods</h3> <p>When feasible, keep methods small and focused. We recognize that long methods are sometimes appropriate, so no hard limit is placed on method length. If a method exceeds 40 lines or so, think about whether it can be broken up without harming the structure of the program.</p> -<h3 id="define-fields-in-standard-places">Define Fields in Standard Places</h3> +<h3 id="define-fields-in-standard-places">Define fields in standard places</h3> <p>Define fields either at the top of the file or immediately before the methods that use them.</p> -<h3 id="limit-variable-scope">Limit Variable Scope</h3> +<h3 id="limit-variable-scope">Limit variable scope</h3> <p>Keep the scope of local variables to a minimum. By doing so, you increase the readability and maintainability of your code and reduce the likelihood of error. Each variable should be declared in the innermost block @@ -337,7 +337,7 @@ is a compelling reason to do otherwise:</p> } </code></pre> -<h3 id="order-import-statements">Order Import Statements</h3> +<h3 id="order-import-statements">Order import statements</h3> <p>The ordering of import statements is:</p> <ol> <li> @@ -391,7 +391,7 @@ pattern without extra engineering effort.</p> <p>Put static imports above all the other imports ordered the same way as regular imports.</p> -<h3 id="use-spaces-for-indentation">Use Spaces for Indentation</h3> +<h3 id="use-spaces-for-indentation">Use spaces for indentation</h3> <p>We use four (4) space indents for blocks and never tabs. When in doubt, be consistent with the surrounding code.</p> <p>We use eight (8) space indents for line wraps, including function calls and @@ -404,7 +404,7 @@ assignments. For example, this is correct:</p> someLongExpression(that, wouldNotFit, on, one, line); </code></pre> -<h3 id="follow-field-naming-conventions">Follow Field Naming Conventions</h3> +<h3 id="follow-field-naming-conventions">Follow field naming conventions</h3> <ul> <li> <p>Non-public, non-static field names start with m.</p> @@ -429,7 +429,7 @@ assignments. For example, this is correct:</p> protected int mProtected; } </code></pre> -<h3 id="use-standard-brace-style">Use Standard Brace Style</h3> +<h3 id="use-standard-brace-style">Use standard brace style</h3> <p>Braces do not go on their own line; they go on the same line as the code before them:</p> <pre><code>class MyClass { @@ -459,7 +459,7 @@ are not obligated to) put it all on one line. For example, this is acceptable:</ body(); // bad! </code></pre> -<h3 id="limit-line-length">Limit Line Length</h3> +<h3 id="limit-line-length">Limit line length</h3> <p>Each line of text in your code should be at most 100 characters long. While much discussion has surrounded this rule, the decision remains that 100 characters is the maximum <em>with the following exceptions</em>:</p> @@ -471,7 +471,7 @@ ease of cut and paste.</li> simplifies tool writing).</li> </ul> -<h3 id="use-standard-java-annotations">Use Standard Java Annotations</h3> +<h3 id="use-standard-java-annotations">Use standard Java annotations</h3> <p>Annotations should precede other modifiers for the same language element. Simple marker annotations (e.g. @Override) can be listed on the same line with the language element. If there are multiple annotations, or parameterized @@ -509,7 +509,7 @@ refactored to isolate the software elements where the annotation applies.</p> </li> </ul> -<h3 id="treat-acronyms-as-words">Treat Acronyms as Words</h3> +<h3 id="treat-acronyms-as-words">Treat acronyms as words</h3> <p>Treat acronyms and abbreviations as words in naming variables, methods, and classes to make names more readable:</p> <table> @@ -546,7 +546,7 @@ classes to make names more readable:</p> acronyms, it is virtually impossible to be consistent with the surrounding code. Therefore, always treat acronyms as words.</p> -<h3 id="use-todo-comments">Use TODO Comments</h3> +<h3 id="use-todo-comments">Use TODO comments</h3> <p>Use TODO comments for code that is temporary, a short-term solution, or good-enough but not perfect. TODOs should include the string TODO in all caps, followed by a colon:</p> @@ -560,7 +560,7 @@ you either include a very specific date ("Fix by November 2005") or a very specific event ("Remove this code after all production mixers understand protocol V7.").</p> -<h3 id="log-sparingly">Log Sparingly</h3> +<h3 id="log-sparingly">Log sparingly</h3> <p>While logging is necessary, it has a significantly negative impact on performance and quickly loses its usefulness if not kept reasonably terse. The logging facilities provides five different levels of logging:</p> @@ -684,7 +684,7 @@ unnecessarily push other logs out of the buffer, just as others may not push out yours.</em></li> </ul> -<h3 id="be-consistent">Be Consistent</h3> +<h3 id="be-consistent">Be consistent</h3> <p>Our parting thought: BE CONSISTENT. If you're editing code, take a few minutes to look at the surrounding code and determine its style. If that code uses spaces around the if clauses, you should too. If the code comments have @@ -697,7 +697,7 @@ vocabulary, but local style is also important. If the code you add to a file looks drastically different from the existing code around it, it throws readers out of their rhythm when they go to read it. Try to avoid this.</p> -<h2 id="javatests-style-rules">Javatests Style Rules</h2> +<h2 id="javatests-style-rules">Javatests style rules</h2> <p>Follow test method naming conventions and use an underscore to separate what is being tested from the specific case being tested. This style makes it easier to see exactly what cases are being tested. For example:</p> diff --git a/en/setup/contributing.html b/en/setup/contribute/index.html index ec212f99..829361af 100644 --- a/en/setup/contributing.html +++ b/en/setup/contribute/index.html @@ -24,11 +24,13 @@ <p>Thanks for your interest in Android! Here are some ways you can get involved and help us improve Android. For background on the Android project and our -goals, check out the <a href="/setup/index.html">Overview</a> page.</p> +goals, check out the <a href="../index.html">Overview</a> page.</p> + <h2 id="report-bugs">Report Bugs</h2> <p>One of the easiest and most effective ways you can help improve Android is -to file bugs. For more information, visit the <a href="report-bugs.html">Reporting Bugs</a> page.</p> +to file bugs. For more information, visit the +<a href="report-bugs.html">Reporting Bugs</a> page.</p> <p>Please note that we can't guarantee that any particular bug will be fixed in any particular release. To see what happens to your bug once you report it, read <a href="life-of-a-bug.html">Life of a Bug</a>.</p> @@ -48,11 +50,11 @@ out the source, pick a bug or feature, and get coding. Note that the smaller and more targetted your patch submissions, the easier it will be for us to review them.</p> -<p>You can get started with Android by learning about the <a href="life-of-a-patch.html">Life of a Patch</a>, -and by learning about <code>git</code>, <code>repo</code>, and other tools using the links to the left. +<p>You can get started with Android by learning about the <a href="life-of-a-patch.html">Life of a Patch</a>, +and by learning about <code>git</code>, <code>repo</code>, and other tools using the links to the left. You can also view the activity on all contributions on our <a href="https://android-review.googlesource.com/">Gerrit server</a>. -If you need help along the way, you can join our <a href="/setup/community.html">discussion groups</a>.</p> +If you need help along the way, you can join our <a href="../community.html">discussion groups</a>.</p> </body> </html> diff --git a/en/setup/life-of-a-bug.html b/en/setup/contribute/life-of-a-bug.html index 571b7cd6..7490b456 100644 --- a/en/setup/life-of-a-bug.html +++ b/en/setup/contribute/life-of-a-bug.html @@ -34,7 +34,7 @@ intended only for bugs and feature requests related to the core Android software stack, and is a technical tool for the Open Source community.</p> <p>This is not a customer support forum. For support information, see the -<a href="https://support.google.com/nexus">Nexus</a> and +<a href="https://support.google.com/nexus">Nexus</a> and <a href="https://support.google.com/pixelphone">Pixel</a> help centers. Support for other devices is provided by the device manufacturers or by the carriers selling those devices.</p> diff --git a/en/setup/life-of-a-patch.html b/en/setup/contribute/life-of-a-patch.html index 6f8d144a..6f8d144a 100644 --- a/en/setup/life-of-a-patch.html +++ b/en/setup/contribute/life-of-a-patch.html diff --git a/en/setup/read-bug-reports.html b/en/setup/contribute/read-bug-reports.html index 63ff5cc0..63ff5cc0 100644 --- a/en/setup/read-bug-reports.html +++ b/en/setup/contribute/read-bug-reports.html diff --git a/en/setup/report-bugs.html b/en/setup/contribute/report-bugs.html index 85ea2fd4..85ea2fd4 100644 --- a/en/setup/report-bugs.html +++ b/en/setup/contribute/report-bugs.html diff --git a/en/setup/submit-patches.html b/en/setup/contribute/submit-patches.html index c9b7b404..578e4750 100644 --- a/en/setup/submit-patches.html +++ b/en/setup/contribute/submit-patches.html @@ -30,24 +30,24 @@ href="https://android-review.googlesource.com/">Gerrit</a>.</p> <ul> <li> <p>Before you follow the instructions on this page, you need to <a -href="/setup/initializing.html"> +href="../build/initializing.html"> initialize your build environment</a>, <a -href="/setup/downloading.html">download the source</a>, <a +href="../build/downloading.html">download the source</a>, <a href="https://android.googlesource.com/new-password">create a password</a>, and follow the instructions on the password generator page.</p> </li> <li> -<p>For details about Repo and Git, see the <a -href="/setup/developing.html">Developing</a> section.</p> +<p>For details about Repo and Git, see <a +href="../develop/index.html">Developing</a>.</p> </li> <li> <p>For information about the different roles you can play within the Android -Open Source community, see <a href="/setup/roles.html">Project +Open Source community, see <a href="../start/roles.html">Project roles</a>.</p> </li> <li> <p>If you plan to contribute code to the Android platform, be sure to read -the <a href="/setup/licenses.html">AOSP's licensing +the <a href="../start/licenses.html">AOSP's licensing information</a>.</p> </li> <li> @@ -64,7 +64,7 @@ href="#upstream-projects">Upstream Projects</a>.</p> href="https://android.googlesource.com/new-password">establish a password</a> that will identify you with the server. Follow the instructions on the password generator page. You need to do this only once. See <a -href="/setup/downloading.html#using-authentication">Using +href="../build/downloading.html#using-authentication">Using Authentication</a> for additional details.</p> <h3 id="start-a-repo-branch">Start a repo branch</h3> <p>For each change you intend to make, start a new branch within the relevant diff --git a/en/setup/view-patches.html b/en/setup/contribute/view-patches.html index c14c3149..b3921fd1 100644 --- a/en/setup/view-patches.html +++ b/en/setup/contribute/view-patches.html @@ -89,7 +89,7 @@ repo download <var>TARGET CHANGE</var></pre> which the change should be downloaded and <code><var>CHANGE</var></code> is the change number as listed in Gerrit. For more information, see the <a - href="/setup/using-repo.html">Repo reference</a>. + href="../develop/repo.html">Repo reference</a>. </p> <h2 id="how-do-i-become-a-verifier-or-reviewer">How do I become a Verifier @@ -99,7 +99,7 @@ repo download <var>TARGET CHANGE</var></pre> In short, contribute high-quality code to one or more of the Android projects. For details about the different roles in the Android Open Source community and who plays them, see <a - href="/setup/roles.html">Project Roles</a>. + href="../start/roles.html">Project Roles</a>. </p> <h2 id="diffs-and-comments">Diffs and comments</h2> diff --git a/en/setup/64-bit-builds.html b/en/setup/develop/64-bit-builds.html index 30b51d6f..30b51d6f 100644 --- a/en/setup/64-bit-builds.html +++ b/en/setup/develop/64-bit-builds.html diff --git a/en/setup/developing.html b/en/setup/develop/index.html index 1b85969d..5ecf6dbd 100644 --- a/en/setup/developing.html +++ b/en/setup/develop/index.html @@ -42,7 +42,8 @@ <p> For more details on Git, refer to - <a href="https://git-scm.com/documentation">Git Documentation</a>. + <a href="https://git-scm.com/documentation" class="external">Git + Documentation</a>. </p> <h2 id="repo">Repo</h2> @@ -62,7 +63,7 @@ In most situations, you can use Git instead of Repo, or mix Repo and Git commands to form complex commands. However, using Repo for basic across-network operations will make your work much simpler. For more details - on Repo, see the <a href="/setup/using-repo.html">Repo Command Reference</a>. + on Repo, see the <a href="repo.html">Repo Command Reference</a>. </p> <h2 id="other-tools">Other tools</h2> @@ -90,9 +91,8 @@ Android development involves the following basic workflow: </p> -<img src="images/git_workflow.png" alt="basic workflow diagram" /> +<img src="../images/git_workflow.png" alt="basic workflow diagram" /> <figcaption><strong>Figure 1.</strong> Basic Android workflow</figcaption> -<p> </p> <ol> <li>Start a new topic branch using <code>repo start</code>. </li> @@ -182,8 +182,8 @@ <p> For information about using Repo to download source, see - <a href="/setup/downloading.html">Downloading the Source</a> and the - <a href="/setup/using-repo.html">Repo Command Reference</a>. + <a href="../build/downloading.html">Downloading the Source</a> and the + <a href="repo.html">Repo Command Reference</a>. </p> <h3 id="synchronizing-clients">Synchronizing clients</h3> @@ -209,7 +209,8 @@ repo sync <var>PROJECT0 PROJECT1 ... PROJECTN</var> particular commit, which makes creating local branches and switching among them a lightweight operation. By using branches, you can isolate one aspect of your work from the others. For an interesting article about using topic - branches, refer to <a href="http://www.kernel.org/pub/software/scm/git/docs/howto/separating-topic-branches.txt" class="external">Separating + branches, refer to + <a href="http://www.kernel.org/pub/software/scm/git/docs/howto/separating-topic-branches.txt" class="external">Separating topic branches</a>. </p> @@ -323,7 +324,7 @@ repo diff <code class="devsite-terminal">git diff --cached</code> </pre> -<img src="images/git_diff.png" alt="diff vs diff-cached" /> +<img src="../images/git_diff.png" alt="diff vs diff-cached" /> <figcaption><strong>Figure 2.</strong> Uncommitted vs. committed edits. </figcaption> diff --git a/en/setup/add-device.html b/en/setup/develop/new-device.html index bd869f97..bd869f97 100644 --- a/en/setup/add-device.html +++ b/en/setup/develop/new-device.html diff --git a/en/setup/using-repo.html b/en/setup/develop/repo.html index b84d9d2f..b84d9d2f 100644 --- a/en/setup/using-repo.html +++ b/en/setup/develop/repo.html diff --git a/en/setup/initializing.html b/en/setup/initializing.html deleted file mode 100644 index 518a1d98..00000000 --- a/en/setup/initializing.html +++ /dev/null @@ -1,459 +0,0 @@ -<html devsite> - <head> - <title>Establishing a Build Environment</title> - <meta name="project_path" value="/_project.yaml" /> - <meta name="book_path" value="/_book.yaml" /> - </head> - <body> - <!-- - Copyright 2017 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 - - http://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>This section describes how to set up your local work environment to build -the Android source files. You will need to use Linux or Mac OS. Building under -Windows is not currently supported.</p> -<p>For an overview of the entire code-review and code-update process, see <a -href="life-of-a-patch.html">Life of a Patch</a>.</p> -<p class="note"><strong>Note:</strong> All commands in this site are preceded -by a dollar sign ($) to differentiate them from output or entries within files. -You may use the <em>Click to copy</em> feature at the top right of each command -box to copy all lines without the dollar signs or triple-click each line to -copy it individually without the dollar sign.</p> -<h2 id="choosing-a-branch">Choosing a Branch</h2> -<p>Some of the requirements for your build environment are determined by which -version of the source code you plan to compile. See -<a href="build-numbers.html">Build Numbers</a> for a full listing of branches you may -choose from. You may also choose to download and build the latest source code -(called <code>master</code>), in which case you will simply omit the branch specification -when you initialize the repository.</p> -<p>Once you have selected a branch, follow the appropriate instructions below to -set up your build environment.</p> -<h2 id="setting-up-a-linux-build-environment">Setting up a Linux build environment</h2> -<p>These instructions apply to all branches, including <code>master</code>.</p> -<p>The Android build is routinely tested in house on recent versions of -Ubuntu LTS (14.04), but most distributions should have the required -build tools available. Reports of successes or failures on other -distributions are welcome.</p> -<p>For Gingerbread (2.3.x) and newer versions, including the <code>master</code> -branch, a 64-bit environment is required. Older versions can be -compiled on 32-bit systems.</p> -<p class="note"><strong>Note:</strong> See the <a -href="requirements.html">Requirements</a> for the complete list of hardware and -software requirements. Then follow the detailed instructions for Ubuntu and Mac -OS below.</p> - -<h3 id="installing-the-jdk">Installing the JDK</h3> -<p>The <code>master</code> branch of Android in the <a -href="https://android.googlesource.com/">Android Open Source Project (AOSP)</a> -comes with prebuilt versions of OpenJDK below -<code>prebuilts/jdk/</code>. So no additional installation is -required.</p> - -<p>Older versions of Android require a separate installation of the JDK. On -Ubuntu, use <a href="http://openjdk.java.net/install/">OpenJDK</a>. See <a -href="requirements.html#jdk">JDK Requirements</a> for precise versions and the -sections below for instructions.</p> - -<h4 id="for-ubuntu-15-04">For Ubuntu >= 15.04</h4> -<p>Run the following:</p> -<pre class="devsite-click-to-copy"> -<code class="devsite-terminal">sudo apt-get update</code> -<code class="devsite-terminal">sudo apt-get install openjdk-8-jdk</code> -</pre> - -<h4 id="for-ubuntu-14-04">For Ubuntu LTS 14.04</h4> -<p>There are no available supported OpenJDK 8 packages for Ubuntu 14.04. The -<strong>Ubuntu 15.04 OpenJDK 8</strong> packages have been used successfully -with Ubuntu 14.04. <em>Newer package versions (e.g. those for 15.10, 16.04) were -found not to work on 14.04 using the instructions below.</em></p> -<ol> -<li> -<p>Download the <code>.deb</code> packages for 64-bit architecture from -<a href="http://old-releases.ubuntu.com/ubuntu/pool/universe/o/openjdk-8/">old-releases.ubuntu.com</a>:</p> -<ul> -<li><a -href="http://old-releases.ubuntu.com/ubuntu/pool/universe/o/openjdk-8/openjdk-8-jre-headless_8u45-b14-1_amd64.deb">openjdk-8-jre-headless_8u45-b14-1_amd64.deb</a> -with SHA256 <code>0f5aba8db39088283b51e00054813063173a4d8809f70033976f83e214ab56c0</code></li> -<li><a -href="http://old-releases.ubuntu.com/ubuntu/pool/universe/o/openjdk-8/openjdk-8-jre_8u45-b14-1_amd64.deb">openjdk-8-jre_8u45-b14-1_amd64.deb</a> -with SHA256 <code>9ef76c4562d39432b69baf6c18f199707c5c56a5b4566847df908b7d74e15849</code></li> -<li><a -href="http://old-releases.ubuntu.com/ubuntu/pool/universe/o/openjdk-8/openjdk-8-jdk_8u45-b14-1_amd64.deb">openjdk-8-jdk_8u45-b14-1_amd64.deb</a> -with SHA256 <code>6e47215cf6205aa829e6a0a64985075bd29d1f428a4006a80c9db371c2fc3c4c</code></li> -</ul> -</li> -<li> -<p>Optionally, confirm the checksums of the downloaded files against the SHA256 -string listed with each package above.</p> -<p>For example, with the <code>sha256sum</code> tool:</p> -<pre class="devsite-terminal devsite-click-to-copy"> -sha256sum {downloaded.deb file} -</pre> -</li> -<li> -<p>Install the packages:</p> -<pre class="devsite-terminal devsite-click-to-copy"> -sudo apt-get update -</pre> -<p>Run <code>dpkg</code> for each of the .deb files you downloaded. It may produce errors due to -missing dependencies:</p> -<pre class="devsite-terminal devsite-click-to-copy"> -sudo dpkg -i {downloaded.deb file} -</pre> -<p>To fix missing dependencies:</p> -<pre class="devsite-terminal devsite-click-to-copy"> -sudo apt-get -f install -</pre> -</li> -</ol> - -<h4 id="default-java-version">Update the default Java version - optional</h4> - -<p>Optionally, for the Ubuntu versions above update the default Java version by -running:</p> -<pre class="devsite-click-to-copy"> -<code class="devsite-terminal">sudo update-alternatives --config java</code> -<code class="devsite-terminal">sudo update-alternatives --config javac</code> -</pre> - -<p>If, during a build, you encounter version errors for Java, set its -path as described in the <a href="building.html#wrong-java-version">Wrong -Java Version</a> section.</p> - -<h3 id="installing-required-packages-ubuntu-1404">Installing required packages (Ubuntu 14.04)</h3> - -<p>You will need a 64-bit version of Ubuntu. Ubuntu 14.04 is recommended.</p> - -<pre class="devsite-terminal devsite-click-to-copy"> -sudo apt-get install git-core gnupg flex bison gperf build-essential zip curl zlib1g-dev gcc-multilib g++-multilib libc6-dev-i386 lib32ncurses5-dev x11proto-core-dev libx11-dev lib32z-dev ccache libgl1-mesa-dev libxml2-utils xsltproc unzip -</pre> - -<p class="note"><strong>Note:</strong> To use SELinux tools for policy -analysis, also install the <code>python-networkx</code> package.</p> - -<p class="note"><strong>Note:</strong> If you are using LDAP and want -to run ART host tests, also install the <code>libnss-sss:i386</code> -package.</p> - -<h3 id="installing-required-packages-ubuntu-1204">Installing required packages -(Ubuntu 12.04)</h3> - -<p>You may use Ubuntu 12.04 to build older versions of Android. Version 12.04 -is not supported on master or recent releases.</p> - -<pre class="devsite-click-to-copy"> -<code class="devsite-terminal">sudo apt-get install git gnupg flex bison gperf build-essential zip curl libc6-dev libncurses5-dev:i386 x11proto-core-dev libx11-dev:i386 libreadline6-dev:i386 libgl1-mesa-glx:i386 libgl1-mesa-dev g++-multilib mingw32 tofrodos python-markdown libxml2-utils xsltproc zlib1g-dev:i386</code> -<code class="devsite-terminal">sudo ln -s /usr/lib/i386-linux-gnu/mesa/libGL.so.1 /usr/lib/i386-linux-gnu/libGL.so</code> -</pre> - -<h3 id="installing-required-packages-ubuntu-1004-1110">Installing required -packages (Ubuntu 10.04 -- 11.10)</h3> -<p>Building on Ubuntu 10.04-11.10 is no longer supported, but may be useful for -building older releases of AOSP.</p> - -<pre class="devsite-terminal devsite-click-to-copy"> -sudo apt-get install git gnupg flex bison gperf build-essential zip curl zlib1g-dev libc6-dev lib32ncurses5-dev ia32-libs x11proto-core-dev libx11-dev lib32readline5-dev lib32z-dev libgl1-mesa-dev g++-multilib mingw32 tofrodos python-markdown libxml2-utils xsltproc -</pre> - -<p>On Ubuntu 10.10:</p> - -<pre class="devsite-terminal devsite-click-to-copy"> -sudo ln -s /usr/lib32/mesa/libGL.so.1 /usr/lib32/mesa/libGL.so -</pre> - -<p>On Ubuntu 11.10:</p> - -<pre class="devsite-terminal devsite-click-to-copy"> -sudo apt-get install libx11-dev:i386 -</pre> - -<h3 id="configuring-usb-access">Configuring USB Access</h3> - -<p>Install a community-maintained default set of <code>udev</code> rules for -all Android devices by following the instructions to <a -href="https://developer.android.com/studio/run/device.html#setting-up" -class="external">Set up a device for development</a>. - -<h3 id="using-a-separate-output-directory">Using a separate output directory</h3> - -<p>By default, the output of each build is stored in the <code>out/</code> -subdirectory of the matching source tree.</p> - -<p>On some machines with multiple storage devices, builds are -faster when storing the source files and the output on -separate volumes. For additional performance, the output -can be stored on a filesystem optimized for speed instead -of crash robustness, since all files can be re-generated -in case of filesystem corruption.</p> - -<p>To set this up, export the <code>OUT_DIR_COMMON_BASE</code> variable -to point to the location where your output directories -will be stored.</p> - -<pre class="devsite-terminal devsite-click-to-copy"> -export OUT_DIR_COMMON_BASE=<path-to-your-out-directory> -</pre> - -<p>The output directory for each separate source tree will be -named after the directory holding the source tree.</p> - -<p>For instance, if you have source trees as <code>/source/master1</code> -and <code>/source/master2</code> and <code>OUT_DIR_COMMON_BASE</code> is set to -<code>/output</code>, the output directories will be <code>/output/master1</code> -and <code>/output/master2</code>.</p> - -<p>It's important in that case to not have multiple source -trees stored in directories that have the same name, -as those would end up sharing an output directory, with -unpredictable results.</p> - -<p>This is only supported on Jelly Bean (4.1) and newer, -including the <code>master</code> branch.</p> - -<h2 id="setting-up-a-mac-os-x-build-environment">Setting up a Mac OS build -environment</h2> - -<p>In a default installation, Mac OS runs on a case-preserving but -case-insensitive filesystem. This type of filesystem is not supported by git -and will cause some git commands (such as <code>git status</code>) to behave -abnormally. Because of this, we recommend that you always work with the AOSP -source files on a case-sensitive filesystem. This can be done fairly easily -using a disk image, discussed below.</p> - -<p>Once the proper filesystem is available, building the <code>master</code> -branch in a modern Mac OS environment is very straightforward. Earlier -branches require some additional tools and SDKs.</p> - -<h3 id="creating-a-case-sensitive-disk-image">Creating a case-sensitive disk image</h3> - -<p>You can create a case-sensitive filesystem within your existing Mac OS environment -using a disk image. To create the image, launch Disk -Utility and select "New Image". A size of 25GB is the minimum to -complete the build; larger numbers are more future-proof. Using sparse images -saves space while allowing to grow later as the need arises. Be sure to select -"case sensitive, journaled" as the volume format.</p> - -<p>You can also create it from a shell with the following command:</p> -<pre class="devsite-click-to-copy devsite-terminal" data-terminal-prefix="# "> -hdiutil create -type SPARSE -fs 'Case-sensitive Journaled HFS+' -size 40g ~/android.dmg -</pre> - -<p>This will create a <code>.dmg</code> (or possibly a -<code>.dmg.sparseimage</code>) file which, once mounted, acts as a drive with -the required formatting for Android development.</p> - -<p>If you need a larger volume later, you can also resize the sparse image with -the following command:</p> - -<pre class="devsite-click-to-copy devsite-terminal" data-terminal-prefix="# ">hdiutil resize -size <new-size-you-want>g ~/android.dmg.sparseimage -</pre> - -<p>For a disk image named <code>android.dmg</code> stored in your home -directory, you can add helper functions to your <code>~/.bash_profile</code>:</p> - -<ul> -<li> -To mount the image when you execute <code>mountAndroid</code>: - -<pre class="devsite-click-to-copy"> -# mount the android file image -mountAndroid() { hdiutil attach ~/android.dmg -mountpoint /Volumes/android; } -</pre> - -<p class="note"><strong>Note:</strong> If your system created a -<code>.dmg.sparseimage</code> file, replace <code>~/android.dmg</code> with -<code>~/android.dmg.sparseimage</code>.</p> -</li> - -<li> -<p>To unmount it when you execute <code>umountAndroid</code>:</p> -<pre class="devsite-click-to-copy"> -# unmount the android file image -umountAndroid() { hdiutil detach /Volumes/android; } -</pre> -</li> -</ul> - -<p>Once you've mounted the <code>android</code> volume, you'll do all your work -there. You can eject it (unmount it) just like you would with an external -drive.</p> - -<h3 id="installing-the-mac-jdk">Installing the JDK</h3> - -<p>See <a href="requirements.html">Requirements</a> for the version of Java to -use when developing various versions of Android.</p> - -<h4 id="installing-required-packages">Installing required packages</h4> - -<ol> -<li> -<p>Install Xcode command line tools with: -<pre class="devsite-terminal devsite-click-to-copy"> -xcode-select --install -</pre> - -<p>For older versions of Mac OS (10.8 or earlier), you need to install Xcode from -<a href="http://developer.apple.com/">the Apple developer site</a>. -If you are not already registered as an Apple developer, you will have to -create an Apple ID in order to download.</p> -</li> - -<li> -<p>Install MacPorts from <a -href="http://www.macports.org/install.php">macports.org</a>.</p> - -<p class="note"><strong>Note:</strong> Make sure that -<code>/opt/local/bin</code> appears in your path <strong>before</strong> -<code>/usr/bin</code>. If not, please add the following to your -<code>~/.bash_profile</code> file:</p> - -<pre class="devsite-click-to-copy"> -export PATH=/opt/local/bin:$PATH -</pre> - -<p class="note"><strong>Note:</strong> If you do not have a -<code>.bash_profile</code> file in your home directory, create one.</p> -</li> - -<li> -<p>Get make, git, and GPG packages from MacPorts:</p> - -<pre class="devsite-terminal devsite-click-to-copy"> -POSIXLY_CORRECT=1 sudo port install gmake libsdl git gnupg -</pre> - -<p>If using Mac OS X v10.4, also install bison:</p> -<pre class="devsite-terminal devsite-click-to-copy"> -POSIXLY_CORRECT=1 sudo port install bison -</pre> -</li> -</ol> - -<h4 id="reverting-from-make-382">Reverting from make 3.82</h4> - -<p>In Android 4.0.x (Ice Cream Sandwich) and earlier, a bug exists in gmake 3.82 -that prevents android from building. You can install version 3.81 using -MacPorts with these steps:</p> - -<ol> -<li> -<p>Edit <code>/opt/local/etc/macports/sources.conf</code> and add a line that says:</p> -<pre class="devsite-click-to-copy"> -file:///Users/Shared/dports -</pre> - -<p>above the rsync line. Then create this directory:</p> -<pre class="devsite-terminal devsite-click-to-copy"> -mkdir /Users/Shared/dports -</pre> -</li> - -<li> -<p>In the new <code>dports</code> directory, run:</p> -<pre class="devsite-terminal devsite-click-to-copy"> -svn co --revision 50980 http://svn.macports.org/repository/macports/trunk/dports/devel/gmake/ devel/gmake/ -</pre> -</li> - -<li> -<p>Create a port index for your new local repository:</p> - -<pre class="devsite-terminal devsite-click-to-copy"> -portindex /Users/Shared/dports -</pre> -</li> - -<li> -<p>Install the old version of gmake with:</p> -<pre class="devsite-terminal devsite-click-to-copy"> -sudo port install gmake @3.81 -</pre> -</li> -</ol> - -<h4 id="setting-a-file-descriptor-limit">Setting a file descriptor limit</h4> - -<p>On Mac OS, the default limit on the number of simultaneous file descriptors -open is too low and a highly parallel build process may exceed this limit.</p> - -<p>To increase the cap, add the following lines to your <code>~/.bash_profile</code>: </p> -<pre class="devsite-click-to-copy"> -# set the number of open files to be 1024 -ulimit -S -n 1024 -</pre> - -<h2 id="optimizing-a-build-environment">Optimizing a build environment (optional)</h2> - -<h3 id="setting-up-ccache">Setting up ccache</h3> - -<p>You can optionally tell the build to use the ccache compilation tool, which -is a compiler cache for C and C++ that can help make builds faster. It -is especially useful for build servers and other high-volume production -environments. Ccache acts as a compiler cache that can be used to speed up rebuilds. -This works very well if you use <code>make clean</code> often, or if you frequently -switch between different build products.</p> - -<p class="note"><strong>Note:</strong> If you're instead conducting incremental -builds (such as an individual developer rather than a build server), ccache may -slow your builds down by making you pay for cache misses.</p> - -<p>To use ccache, issue these commands in the root of the source tree:</p> - -<pre class="devsite-click-to-copy"> -<code class="devsite-terminal">export USE_CCACHE=1</code> -<code class="devsite-terminal">export CCACHE_DIR=/<path_of_your_choice>/.ccache</code> -<code class="devsite-terminal">prebuilts/misc/linux-x86/ccache/ccache -M 50G</code> -</pre> - -<p>The suggested cache size is 50-100G.</p> - -<p>Put the following in your <code>.bashrc</code> (or equivalent):</p> - -<pre class="devsite-click-to-copy"> -export USE_CCACHE=1 -</pre> - -<p>By default the cache will be stored in <code>~/.ccache</code>. -If your home directory is on NFS or some other non-local filesystem, -you will want to specify the directory in your <code>.bashrc</code> file too.</p> - -<p>On Mac OS, you should replace <code>linux-x86</code> with <code>darwin-x86</code>:</p> - -<pre class="devsite-click-to-copy"> -prebuilts/misc/darwin-x86/ccache/ccache -M 50G -</pre> - -<p>When building Ice Cream Sandwich (4.0.x) or older, ccache is in -a different location:</p> - -<pre class="devsite-click-to-copy"> -prebuilt/linux-x86/ccache/ccache -M 50G -</pre> - -<p>This setting is stored in the CCACHE_DIR and is persistent.</p> - -<p>On Linux, you can watch ccache being used by doing the following:</p> - -<pre class="devsite-terminal devsite-click-to-copy"> -watch -n1 -d prebuilts/misc/linux-x86/ccache/ccache -s -</pre> - -<h2 id="next-download-the-source">Next: Download the source</h2> - -<p>Your build environment is good to go! Proceed to <a -href="downloading.html">downloading the source</a>.</p> - - </body> -</html> diff --git a/en/setup/licenses.html b/en/setup/licenses.html deleted file mode 100644 index a2114a2b..00000000 --- a/en/setup/licenses.html +++ /dev/null @@ -1,110 +0,0 @@ -<html devsite> - <head> - <title>Content License</title> - <meta name="project_path" value="/_project.yaml" /> - <meta name="book_path" value="/_book.yaml" /> - </head> - <body> - <!-- - Copyright 2017 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 - - http://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>The Android Open Source Project uses a few -<a href="http://www.opensource.org/">open source initiative</a> -approved open source licenses for our software.</p> -<h2 id="android-open-source-project-license">Android Open Source Project License</h2> -<p>The preferred license for the Android Open Source Project is the -<a href="http://www.apache.org/licenses/LICENSE-2.0">Apache -Software License, Version 2.0</a> ("Apache 2.0"), -and the majority of the Android software is licensed -with Apache 2.0. While the project will strive to adhere to the preferred -license, there may be exceptions that will be handled on a case-by-case -basis. For example, the Linux kernel patches are under the GPLv2 license with -system exceptions, which can be found on <a href="http://www.kernel.org/pub/linux/kernel/COPYING">kernel.org</a>.</p> -<h2 id="contributor-license-grants">Contributor License Agreements</h2> -<p>All <em>individual</em> contributors (that is, contributors making contributions -only on their own behalf) of ideas, code, or documentation to the Android Open -Source Project will be required to complete, sign, and submit an <a -href="https://cla.developers.google.com/about/google-individual">Individual -Contributor License Agreement</a>. The agreement can be executed online through the -<a href="https://android-review.googlesource.com/#/settings/agreements">code review tool</a>. -The agreement clearly defines the terms under which intellectual -property has been contributed to the Android Open Source Project. This license -is for your protection as a contributor as well as the protection of the -project; it does not change your rights to use your own contributions for any -other purpose.</p> -<p>For a <em>corporation</em> (or other entity) that has assigned employees to -work on the Android Open Source Project, a <a -href="https://cla.developers.google.com/about/google-corporate">Corporate -Contributor License Agreement</a> is available. -This version of the agreement allows a -corporation to authorize contributions submitted by its designated employees -and to grant copyright and patent licenses. Note that a Corporate Contributor -License Agreement does not remove the need for any developer to sign their own -Individual Contributor License Agreement as an individual. The individual -agreement is needed to cover any of their contributions that are <em>not</em> -owned by the corporation signing the Corporate Contributor License Agreement.</p> -<p>Please note we based our agreements on the ones the -<a href="http://www.apache.org">Apache Software Foundation</a> uses, which can -be found on the <a href="http://www.apache.org/licenses/">Apache web site</a>.</p> -<h2 id="why-apache-software-license">Why Apache Software License?</h2> -<p>We are sometimes asked why Apache Software License 2.0 is the preferred -license for Android. For userspace (that is, non-kernel) software, we do in -fact prefer ASL2.0 (and similar licenses like BSD, MIT, etc.) over other -licenses such as LGPL.</p> -<p>Android is about freedom and choice. The purpose of Android is promote -openness in the mobile world, and we don't believe it's possible to predict or -dictate all the uses to which people will want to put our software. So, while -we encourage everyone to make devices that are open and modifiable, we don't -believe it is our place to force them to do so. Using LGPL libraries would -often force them to do just that.</p> -<p>Here are some of our specific concerns:</p> -<ul> -<li> -<p>LGPL (in simplified terms) requires either: shipping of source to the -application; a written offer for source; or linking the LGPL-ed library -dynamically and allowing users to manually upgrade or replace the library. -Since Android software is typically shipped in the form of a static system -image, complying with these requirements ends up restricting OEMs' designs. -(For instance, it's difficult for a user to replace a library on read-only -flash storage.)</p> -</li> -<li> -<p>LGPL requires allowance of customer modification and reverse -engineering for debugging those modifications. Most device makers do -not want to have to be bound by these terms. So to minimize the burden on -these companies, we minimize usage of LGPL software in userspace.</li></p> -</li> -<li> -<p>Historically, LGPL libraries have been the source of a large number -of compliance problems for downstream device makers and application -developers. Educating engineers on these issues is difficult and slow-going, -unfortunately. It's critical to Android's success that it be as easy as -possible for device makers to comply with the licenses. Given the -difficulties with complying with LGPL in the past, it is most prudent to -simply not use LGPL libraries if we can avoid it.</p> -</li> -</ul> -<p>The issues discussed above are our reasons for preferring ASL2.0 for -our own code. They aren't criticisms of LGPL or other licenses. We are -passionate about this topic, even to the point where we've gone out of our -way to make sure as much code as possible is ASL2.0 licensed. However, we love all free -and open source licenses, and respect others' opinions and preferences. We've -simply decided ASL2.0 is the right license for our goals.</p> - - </body> -</html> diff --git a/en/setup/requirements.html b/en/setup/requirements.html deleted file mode 100644 index e95cbb20..00000000 --- a/en/setup/requirements.html +++ /dev/null @@ -1,180 +0,0 @@ -<html devsite> - <head> - <title>Requirements</title> - <meta name="project_path" value="/_project.yaml" /> - <meta name="book_path" value="/_book.yaml" /> - </head> - <body> - <!-- - Copyright 2017 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 - - http://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>Before you download and build the Android source, ensure your system meets - the following requirements. Then see <a href="initializing.html">Establishing a - Build Environment</a> for installation instructions by operating system.</p> - -<h2 id=hardware-requirements>Hardware requirements</h2> - -<p>Your development workstation should meet or exceed these hardware requirements:</p> - -<ul> - - <li>A 64-bit environment is required for Gingerbread (2.3.x) and newer - versions, including the master - branch. You can compile older versions on 32-bit systems. - </li> - - <li>At least 100GB of free disk space to checkout the code and an extra 150GB - to build it. If you conduct multiple builds or employ ccache, you will need - even more space.</p> - </li> - - <li>If you are running Linux in a virtual machine, you need at - least 16GB of RAM/swap. - </li> - -</ul> - -<h2 id=software-requirements>Software requirements</h2> - -<p>The <a - href="https://android.googlesource.com/">Android Open Source Project - (AOSP)</a> <code>master</code> branch is traditionally developed and tested - on Ubuntu Long Term Support (LTS) releases, but other distributions may be - used. See the list below for recommended versions.</p> - -<p>You workstation must have the software listed below. See <a - href="initializing.html">Establishing a Build Environment</a> for - additional required packages and the commands to install them.</p> - -<h3 id=latest-version>OS and JDK</h3> - -<p>If you are developing against the AOSP <code>master</code> branch, use one -of these operating systems: Ubuntu 14.04 (Trusty) or Mac OS v10.10 (Yosemite) -or later with Xcode 4.5.2 and Command Line Tools.</p> - -<p>For the Java Development Kit (JDK), note the <code>master</code> branch of -Android in AOSP comes with a prebuilt version of OpenJDK; so no additional -installation is required. Older versions require a separate install.</p> - -<p>See <a href="#older-versions">Packages for older versions</a>. - -<h3 id=packages>Key packages</h3> - <ul> - <li>Python 2.6 -- 2.7 from <a href="http://www.python.org/download/">python.org</a></li> - <li>GNU Make 3.81 -- 3.82 from <a href="http://ftp.gnu.org/gnu/make/">gnu.org</a> - <li>Git 1.7 or newer from <a href="http://git-scm.com/download">git-scm.com</a></li> - </ul> - -<h3 id=binaries>Device binaries</h3> -<p>Download previews, factory images, drivers, over-the-air (OTA) updates, and -other blobs below. See <a - href="/setup/building.html#obtaining-proprietary-binaries">Obtaining - proprietary binaries</a> for additional details.</p> - <ul> - <li><a href="https://developers.google.com/android/blobs-preview">Preview - binaries (blobs)</a> - for AOSP <code>master</code> branch - development</li> - <li><a href="https://developers.google.com/android/images">Factory - images</a> - for the supported devices running tagged AOSP release - branches</li> - <li><a href="https://developers.google.com/android/drivers">Binary - hardware support files</a> - for devices running tagged AOSP release - branches</li> - </ul> - - <h3 id=toolchain>Build toolchain</h3> - - <p>Android 8.0 and later support only <a -href="https://developer.android.com/ndk/guides/standalone_toolchain.html#working_with_clang">Clang/LLVM</a> - for building the Android platform. Join the <a -href="https://groups.google.com/forum/#!forum/android-llvm">android-llvm</a> - group to pose questions and get help. Report NDK/compiler issues at the <a -href="https://github.com/android-ndk/ndk">NDK GitHub</a>.</p> - -<p>For the -<a href="https://developer.android.com/ndk/guides/index.html">Native -Development Kit (NDK)</a> and legacy kernels, GCC 4.9 included -in the AOSP master branch (under <code>prebuilts/</code>) may also be used.</p> - -<h3 id=older-versions>Packages for older versions</h3> - -<p>The sections below provide relevant operating systems and JDK packages for -older versions of Android.</p> - -<h4 id=operating-system>Operating system</h4> - -<p>Android is typically built with a GNU/Linux or Mac OS operating system. It is - also possible to build Android in a virtual machine on unsupported systems such - as Windows.</br> - - <h5 id=linux>GNU/Linux</h5> - - <ul> - <li>Android 6.0 (Marshmallow) - AOSP master: Ubuntu 14.04 (Trusty)</li> - <li>Android 2.3.x (Gingerbread) - Android 5.x (Lollipop): Ubuntu 12.04 (Precise)</li> - <li>Android 1.5 (Cupcake) - Android 2.2.x (Froyo): Ubuntu 10.04 (Lucid)</li> - </ul> - -<h5 id=mac>Mac OS (Intel/x86)</h5> - - <ul> - <li>Android 6.0 (Marshmallow) - AOSP master: Mac OS v10.10 (Yosemite) or - later with Xcode 4.5.2 and Command Line Tools</li> - <li>Android 5.x (Lollipop): Mac OS v10.8 (Mountain Lion) with Xcode 4.5.2 - and Command Line Tools</li> - <li>Android 4.1.x-4.3.x (Jelly Bean) - Android 4.4.x (KitKat): Mac OS v10.6 - (Snow Leopard) or Mac OS X v10.7 (Lion) and Xcode 4.2 (Apple's Developer - Tools)</li> - <li>Android 1.5 (Cupcake) - Android 4.0.x (Ice Cream Sandwich): Mac OS - v10.5 (Leopard) or Mac OS X v10.6 (Snow Leopard) and the Mac OS X v10.5 - SDK</li> - </ul> - - <p><b>Note</b>: consider building on GNU/Linux, not another - operating system. The Android build system normally uses ART, - running on the build machine, to pre-compile system dex files. Since - ART is able to run only on Linux, the build system skips this - pre-compilation step on non-Linux operating systems, resulting in an - Android build with reduced performance.</p> - -<h4 id=jdk>JDK</h4> - -<p>See <a href="initializing.html#installing-the-jdk">Installing the JDK</a> -for the prebuilt path and installation instructions for older versions.</p> - <ul> - <li>Android 7.0 (Nougat) - Android 8.0 (O release): Ubuntu - <a - href="http://openjdk.java.net/install/">OpenJDK 8</a>, Mac OS - <a - href="http://www.oracle.com/technetwork/java/javase/downloads/java-archive-javase8-2177648.html#jdk-8u45-oth-JPR">jdk - 8u45 or newer</a></li> - <li>Android 5.x (Lollipop) - Android 6.0 (Marshmallow): Ubuntu - <a - href="http://openjdk.java.net/install/">OpenJDK 7</a>, Mac OS - <a - href="https://www.oracle.com/technetwork/java/javase/downloads/java-archive-downloads-javase7-521261.html#jdk-7u71-oth-JPR">jdk-7u71-macosx-x64.dmg</a></li> - <li>Android 2.3.x (Gingerbread) - Android 4.4.x (KitKat): Ubuntu - <a - href="http://www.oracle.com/technetwork/java/javase/archive-139210.html">Java JDK 6</a>, Mac OS - <a - href="http://support.apple.com/kb/dl1572">Java JDK 6</a></li> - <li>Android 1.5 (Cupcake) - Android 2.2.x (Froyo): Ubuntu - <a - href="http://www.oracle.com/technetwork/java/javase/archive-139210.html">Java JDK 5</a></li> - </ul> - - <h4 id=make>Make</h4> - <p> Android 4.0.x (Ice Cream Sandwich) and earlier will need to <a - href="initializing.html#reverting-from-make-382">revert from make 3.82</a> - to avoid build errors.</p> - - </body> -</html> diff --git a/en/setup/roles.html b/en/setup/roles.html deleted file mode 100644 index 03e2b826..00000000 --- a/en/setup/roles.html +++ /dev/null @@ -1,102 +0,0 @@ -<html devsite> - <head> - <title>Project Roles</title> - <meta name="project_path" value="/_project.yaml" /> - <meta name="book_path" value="/_book.yaml" /> - </head> - <body> - <!-- - Copyright 2017 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 - - http://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>The Android Open Source Project (AOSP) includes individuals working in a variety -of roles. Google is responsible for Android product management -and the engineering process for the core framework and platform; however, -the project considers contributions from any source, not just Google. This -page describes the kinds of roles that interested parties can take on.</p> -<p>Anyone who is interested in exploring and contributing to Android can use the -Android Open Source Project resources. Anyone can join the mailing lists, ask -questions, contribute patches, report bugs, look at submitted patches, and use -the tools. To get started with the Android code, see <a href="/setup/contributing.html">Contributing</a>.</p> -<h2 id="contributor">Contributor</h2> -<p>"Contributors" are those making contributions to the AOSP source code, -including both employees of Google or other companies, as well as individual -developers who are contributing to Android on their own behalf. There is no -distinction between contributors who are employed by Google and those who are -not; all engineers use the same tools (git, repo, and gerrit), -follow the same code review process, and are subject -to the same requirements on code style and so on.</p> -<h2 id="developer">Developer</h2> -<p>"Developers" are engineers writing applications that run on Android -devices. There is often little difference in skillset between a developer -and a contributor. But AOSP uses "developer" to distinguish between -engineers using the platform and those contributing to it. Developers -(along with users) are the "customers" of the platform the contributors -create. As such, we talk about developers a lot, though this isn't technically -a separate role in the AOSP per se.</p> -<h2 id="verifier">Verifier</h2> -<p>"Verifiers" are responsible for testing change requests. After individuals -have submitted a significant amount of high-quality code to the project, the -project leads might invite them to become verifiers.</p> -<p class="note"><strong>Note:</strong> At this time, verifiers act similarly to approvers.</p> -<h2 id="approver">Approver</h2> -<p>"Approvers" are experienced members of the project who have demonstrated their -design skills and have made significant technical contributions to the -project. In the code-review process, an approver decides whether to include or -exclude a change. Project leads (who are typically employed by Google) choose -the approvers, sometimes promoting to this position verifiers who have -demonstrated their expertise within a specific project.</p> -<h2 id="project-leads">Project Lead</h2> -<p>Android consists of a number of sub-projects; you can see these in the git -repository as individual .git files. "Project leads" are senior contributors who -oversee the engineering for individual Android projects. Typically these project -leads are Google employees. A project lead for an individual project is -responsible for the following:</p> -<ul> -<li> -<p>Lead all technical aspects of the project, including the project roadmap, - development, release cycles, versioning, and quality assurance (QA).</p> -</li> -<li> -<p>Ensure the project is tested by QA in time for scheduled Android platform - releases.</p> -</li> -<li> -<p>Designate Verifiers and Approvers for submitted patches.</p> -</li> -<li> -<p>Be fair and unbiased while reviewing changes. Accept or reject patches - based on technical merit and alignment with the Android strategy.</p> -</li> -<li> -<p>Review changes in a timely manner and make best efforts to communicate - when changes are not accepted.</p> -</li> -<li> -<p>Optionally maintain a web site for the project for information and - documents specific to the project.</p> -</li> -<li> -<p>Act as a facilitator in resolving technical conflicts.</p> -</li> -<li> -<p>Be a public face for the project and the go-to person for questions - related to the project.</p> -</li> -</ul> - - </body> -</html> diff --git a/en/setup/site-updates.html b/en/setup/site-updates.html deleted file mode 100644 index a77ebbda..00000000 --- a/en/setup/site-updates.html +++ /dev/null @@ -1,777 +0,0 @@ -<html devsite> - <head> - <title>Site Updates</title> - <meta name="project_path" value="/_project.yaml" /> - <meta name="book_path" value="/_book.yaml" /> - </head> - <body> - <!-- - Copyright 2017 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 - - http://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>This page describes significant revisions to source.android.com. Please see -the <a -href="https://android.googlesource.com/platform/docs/source.android.com/+log/master?pretty=full&no-merges">Android -Open Source Project (AOSP) docs/source.android.com log</a> for the complete -list of changes to this site. - -<h2 id="Dec-2017">December 2017</h2> - -<p>Android 8.1 has been released! See the entries below for the major platform -features introduced in this release.</p> - -<h3 id="aaudio">AAudio and MMAP</h3> - -<p>AAudio is an audio API that has enhancements to reduce latency when used in -conjunction with a HAL and driver that support MMAP. See <a -href="/devices/audio/aaudio">AAudio and MMAP</a> for documentation -describing the hardware abstraction layer (HAL) and driver changes needed to -support AAudio's MMAP feature in Android.</p> - -<h3 id="art-config">ART configuration changes</h3> - -<p>The <code>WITH_DEXPREOPT_BOOT_IMG_ONLY</code> makefile option was removed -from the Android runtime (ART) in Android 8.1 and replaced with the -<code>WITH_DEXPREOPT_BOOT_IMG_AND_SYSTEM_SERVER_ONLY</code> option that -pre-optimizes the system server jars, as well as the boot classpath. See <a -href="/devices/tech/dalvik/configure#build_options">Configuring ART</a> for the -deprecation notice.</p> - -<h3 id="biometric-unlock">Biometric unlock security measurements</h3> - -<p>Android 8.1 introduces two new metrics associated with biometric unlocks -that are intended to help device manufacturers evaluate their security more -accurately: Imposter Accept Rate (IAR) and Spoof Accept Rate (SAR). See <a -href="/security/biometric/">Measuring Biometric Unlock Security</a> for -example attacks and test methodology.</p> - -<h3 id="boot-times">Boot time optimizations</h3> - -<p>Starting in Android 8.1, power saving setting for components like UFS and -CPU governor can be disabled to improve device boot times. See <a -href="/devices/tech/perf/boot-times#disable-power-saving">Optimizing Boot -Times</a> for the new <code>init.*.rc</code> settings.</p> - -<h3 id=“color-mgmtâ€>Color management</h3> - -<p>Android 8.1 adds support for color management that can be used to provide a -consistent experience across display technologies. Applications running on -Android 8.1 can access the full capabilities of a wide gamut display to get the -most out of a display device. See <a -href="/devices/tech/display/color-mgmt">Color Management</a> for -instructions on implementing, customizing, and testing this feature.</p> - -<h3 id="opengl-config">OpenGLRenderer configuration simplification</h3> - -<p>In Android 8.1 and later, only the <code>ro.zygote.disable_gl_preload -property</code> still applies to OpenGLRenderer configuration. All other -properties have been removed. See <a -href="/devices/graphics/renderer">OpenGLRenderer Configuration</a> for the -notice and previously supported properties.</p> - -<h3 id="retail-mode">Retail demo mode made easy</h3> - -<p>Through Device Policy Manager, Android 8.1 supports demonstrating device -functionality in retail stores via a demo-type user role. See <a -href="/devices/tech/display/retail-mode.html">Retail Demo Mode</a> for -implementation instructions.</p> - -<h3 id="textclassifier">TEXTCLASSIFIER</h3> - -<p>Android 8.1 introduces the TextClassfier API that uses machine learning -techniques to help developers classify text. -See <a href="/devices/tech/display/textclassifier.html">TEXTCLASSIFIER</a> for -implementation instructions.</p> - -<h3 id="timezone-rules">Time zone rules</h3> - -<p>Android 8.1 provides a new mechanism for device manufacturers (OEMs) to push -updated time zone rules data to devices without requiring a system update. This -mechanism enables users to receive timely updates and OEMs to test time zone -updates independently of system image updates. See <a -href="/devices/tech/config/timezone-rules">Time Zone Rules</a> for -instructions on applying these updates.</p> - -<h3 id="wifi-aware">Wi-Fi Aware</h3> - -<p>The Wi-Fi Aware feature in Android 8.1 enables supporting devices to connect -to one another directly over Wi-Fi without internet or cellular network access. -This feature allows easy sharing of high-throughput data among trusted devices -and apps that are otherwise off network. See <a -href="/devices/tech/connect/wifi-aware">Wi-Fi Aware</a> for examples, source -files, and links to additional documentation.</p> - -<h2 id="Nov-2017">November 2017</h2> - -<p>The <em>Source</em> section has been renamed to - <a href="/setup"><em>Setup</em></a>. Redirects are in place to ensure the old - URLs still work.</p> - -<h2 id="Sept-2017">September 2017</h2> - -<p>This site has been released in China at <a - href="https://source.android.google.cn" - class="external-link">source.android.google.cn</a>. All - non-reference materials have also been translated into Simplified Chinese for - ease of use.</p> - -<h2 id="August-2017">August 2017</h2> - -<p>Android 8.0 has been released! This section describes the major new features -in the Android 8.0 platform.</p> - -<h3 id="architecture">Architecture</h3> - -<h4>Treble</h4> -<p> -Android 8.0 includes support for Treble, a major re-architect of the -Android OS framework designed to make it easier, faster, and less costly -for manufacturers to update devices to a new version of Android. Documentation -includes details on the <a href="/devices/architecture/hidl/index.html">HAL interface definition -language (HIDL)</a>, a new <a href="/devices/architecture/configstore/index.html">ConfigStore HAL</a>, -<a href="/devices/architecture/dto/index.html">Device Tree Overlays</a>, -the <a href="/devices/architecture/vndk/index.html">Vendor Native Development -Kit (VNDK)</a>, <a href="/devices/architecture/vintf/index.html">Vendor - Interface Objects (VINTF)</a>, <a href="/devices/architecture/kernel/modular-kernels.html"> -Modular Kernel requirements</a>, and the <a href="/devices/tech/vts/index.html"> -Vendor Test Suite (VTS) and Infrastructure</a>. -</p> - -<h4>FunctionFS support</h4> -<p> -<a class="external-link" - href="https://www.kernel.org/doc/Documentation/usb/functionfs.txt">FunctionFS</a> -(FFS) is a USB gadget function that is designed and controlled through user space. -Its support allows all of the function- and protocol-specific code to live in -user space, while all of the USB transport code lives in the kernel. Using - FFS moves Media Transfer Protocol (MTP) implementation into user space. -</p> - -<p> -On the frameworks side, most of the major changes exist in MtpServer. The -USB driver interface has been refactored into two different classes, one that -uses the old kernel driver and one that uses FFS. MtpServer is then able -to use that driver interface without needing to know the details of -implementation. The FFS driver writes the USB descriptors to a file when -the server starts up; it then writes data to endpoint files similar to the -kernel driver use. -</p> - -<h4>Kernel enhancements to LLDB/C++ debugging</h4> -<p> -The Android 8.0 release includes kernel enhancements that help developers create -better applications by improving their debugging experience. For more -information, see <a -href="/devices/architecture/kernel/lldb-debug.html">Implementing -kernel enhancements to LLDB/C++ debugging</a>. -</p> - -<h4>Kernel Hardening</h4> -<p> -Upstreamed kernel hardening features and tools to find bugs in kernel drivers. -For more information, see <a -href="/devices/architecture/kernel/hardening.html">Kernel Hardening</a>. -</p> - -<h4>Optimizing SquashFS at the Kernel Level</h4> -<p> -SquashFS is a compressed read-only filesystem for Linux, suitable for use on the -system partition. The optimizations in this document help improve the -performance of SquashFS. For more information, see <a -href="/devices/architecture/kernel/squashfs.html">Optimizing -SquashFS at the Kernel Level</a>. -</p> - -<h3 id="art-dalvik">ART and Dalvik</h3> -<h4>Fuzz Testing</h4> -<p> -The Android Open Source Project (AOSP) offers a new fuzzing testing suite for -testing the <a href="/devices/tech/dalvik/">Android -runtime (ART)</a> infrastructure. The new toolset, JFuzz and an improved -DexFuzz, are directly available in AOSP now with accompanying documentation. -See: -<a -href="https://android.googlesource.com/platform/art/+/master/tools/jfuzz/README.md">https://android.googlesource.com/platform/art/+/master/tools/jfuzz/README.md</a> -<a -href="https://android.googlesource.com/platform/art/+/master/tools/dexfuzz/README">https://android.googlesource.com/platform/art/+/master/tools/dexfuzz/README</a> -</p> -<p> -Nothing is required to implement or use the new tools. You may make changes -to the tools if required, just like you can make changes to the -runtime/compiler already. -</p> - -<h4>VDEX files: Improve System Update Performance</h4> -<p> -VDEX files improve the performance and user experience of software updates. VDEX -files store pre-validated DEX files with verifier dependencies so that during -system updates ART does not need to extract and verify the DEX files again. No -action is needed to implement this feature. It is enabled by default. To -disable the feature, set the <code>ART_ENABLE_VDEX</code> environment variable -to <code>false</code>. -</p> - -<h4>ART performance improvements</h4> -<p> -The Android runtime (ART) has been improved significantly in the Android 8.0 -release. This document summarizes enhancements device manufacturers can expect -in ART. For more information, see <a -href="/devices/tech/dalvik/improvements.html">Improving -ART Performance in Android 8.0</a>. -</p> - -<h4>Android A/B OTA Updates</h4> -<p> -This update answers common questions device manufacturers have regarding Android -A/B (seamless) system updates. For more information, see <a -href="/devices/tech/ota/ab_updates#frequently-asked-questions.html">A/B -(Seamless) System Updates Frequently asked questions</a>. -</p> - -<h3 id="automotive">Automotive</h3> - -<h4>Bluetooth connection management</h4> -<p> -Android 8.0 provides Bluetooth connection management in in-vehicle infotainment -systems for a more seamless Bluetooth user experience. For more information, see -<a href="/devices/automotive/ivi_connectivity.html#bluetooth-connection-management"> -Bluetooth connection management</a>. -</p> - -<h4>Bluetooth multi-device HFP</h4> -<p> -Bluetooth multi-device connectivity lets users connect multiple devices to telephony profiles in -an Android Automotive IVI Bluetooth. For more information, see -<a href="/devices/automotive/ivi_connectivity.html#bluetooth-multi-device-connectivity"> -IVI Connectivity</a>. -</p> - -<h4>Vehicle Camera HAL</h4> -<p> -Describes the design of an exterior view system (EVS) stack and provides the HAL -specification for supporting the acquisition and presentation of vehicle camera -data. For more information, see <a -href="/devices/automotive/camera-hal.html">Exterior -View System (EVS) Vehicle Camera HAL.</a> -</p> - -<h3 id="bluetooth">Bluetooth</h3> -<p> -See the updated <a -href="/devices/bluetooth/index.html">Bluetooth -overview</a>. -</p> - -<h4>Verifying and debugging Bluetooth</h4> -<p> -A new page about how to verify and debug the native Bluetooth stack. For more details, see -<a href="/devices/bluetooth/verifying_debugging.html">Verifying and Debugging</a>. -</p> - -<h4>Bluetooth services</h4> -<p> -Bluetooth provides a variety of features that enable core services between devices, -such as audio streaming, phone calls, and messaging. For more information about the Android -Bluetooth services, see <a href="/devices/bluetooth/services.html"> -Bluetooth Services</a>. -</p> - -<h4>BLE advertising</h4> -<p> -Bluetooth 5 supports different modes of data advertisements for Bluetooth Low Energy, -including higher bandwidth or increased range. For more information, see -<a href="/devices/bluetooth/ble_advertising.html"> -Bluetooth Low Energy Advertising</a>. -</p> - - -<h4>Bluetooth support for audio codecs</h4> -<p> -The Android 8.0 release includes support for Bluetooth high-definition audio -codecs. For more information, see <a -href="/devices/bluetooth/services.html#advanced-audio-codecs">Advanced audio codecs</a>. -</p> - - -<h3 id="camera">Camera</h3> - -<h4>Critical camera features</h4> -<p> -The Android 8.0 release contains these key enhancements to the Camera service: -shared surfaces, enable multiple surfaces sharing the same OutputConfiguration -System API for custom camera modes, and onCaptureQueueEmpty. For more -information, see <a -href="/devices/camera/versioning.html">Camera Version -Support</a>. -</p> - -<h3 id="configuration">Configuration</h3> - -<h4>Ambient Capabilities</h4> -<p> -Capabilities allow Linux processes to drop most root-like privileges, while -retaining the subset of privileges that they require to perform their function. -Ambient capabilities allows system services to configure capabilities in their -<code>.rc</code> files, bringing all their configuration into a single file. For -more information, see <a -href="/devices/tech/config/ambient.html">Implementing -Ambient Capabilities</a>. -</p> - -<h4>Privileged Permission Whitelist Requirement</h4> -<p> -Starting in Android 8.0, all privileged apps must be explicitly whitelisted in -system configuration XML files in the <code>/etc/permissions</code> directory. -If they are not, then the device will boot, but the device implementation will -not pass CTS. For more information, see <a -href="/devices/tech/config/perms-whitelist.html">Privileged -Permission Whitelist Requirement</a>. -</p> - -<h4>Implementing USB HAL</h4> -<p> -The Android 8.0 release moves handling of USB commands out of init scripts and -into a native USB daemon for better configuration and code reliability. For more -information, see <a -href="/devices/tech/config/usb-hal.html">Implementing -USB HAL</a>. -</p> - -<h3 id="connectivity">Connectivity</h3> - -<h4>Customizing Device Behavior for Out-of-balance Users</h4> -<p> -Android devices with no data balance allow network traffic through, requiring -carriers and telecoms to implement mitigation protocols. This feature implements -a generic solution that allows carriers and telcos to indicate when a device has -run out of balance. For more information, see <a -href="/devices/tech/connect/oob-users.html">Customizing -device behavior for out-of-balance users</a>. -</p> - -<h3 id="debugging">Debugging</h3> - -<h4>Enabling sanitizers in the Android build system</h4> -<p> -Sanitizers are compiler-based instrumentation components to use during -development and testing in order to identify bugs and make Android better. -Android's current set of sanitizers can discover and diagnose memory misuse bugs -and potentially dangerous undefined behavior. For more information, see <a -href="/devices/tech/debug/sanitizers.html">Enabling -Sanitizers in the Android Build System</a>. -</p> - -<h4>Recover devices in reboot loops</h4> -<p> -Android 8.0 includes a feature that sends out a "rescue party" when it notices -core system components stuck in crash loops. Rescue Party then escalates through -a series of actions to recover the device. For more information, see <a -href="/devices/tech/debug/rescue-party.html">Rescue -Party</a>. -</p> - -<h4>Storaged</h4> -<p> -Android 8.0 adds support for <code>storaged</code>, an Android native daemon that -collects and publishes storage metrics on Android devices. For more information, -see <a -href="/devices/tech/debug/storaged.html">Implementing -Storaged</a>. -</p> - -<h3 id="display">Display</h3> - -<h4>Air Traffic Control for floating windows</h4> -<p> -Android 8.0 introduces Air Traffic Control for floating windows in order to -simplify and unify how apps display on top of other apps. Everything necessary -to use the feature is included in the Android Open Source Project (AOSP). -</p> -<p> -Air Traffic Control allows developers to create a new (managed) floating -layer/window type for apps to use to display windows on-top of other apps. The -feature displays ongoing notifications for all apps using a floating layer that -lets the user manage the alert window. -</p> -<p> -The Android Compatibility Test Suite (CTS) confirms: -</p> <ul> - <li>The current alert window types are: <code>TYPE_PHONE</code>, <code>TYPE_PRIORITY_PHONE</code>, -<code>TYPE_SYSTEM_ALERT</code>, <code>TYPE_SYSTEM_OVERLAY</code>, or <code>TYPE_SYSTEM_ERROR</code> - <li>Apps targeting the O SDK won't be able to use the window types above to -display windows above other apps. They will need to use a new window type -TYPE_APPLICATION_OVERLAY. - <li>Apps targeting older SDKs can still use the current window types; however, -the windows will be z-ordered below the new TYPE_APPLICATION_OVERLAY windows. - <li>The system can move or resize windows in the new layer to reduce clutter. - <li>Device manufacturers must keep the notification that lets users control -what is displayed over other apps.</li> </ul> - -<h4>Launching activities on secondary displays</h4> -<p> -Virtual displays are available to everyone, and they don't require any special -hardware. Any application can create an instance of virtual display; and in the -Android 8.0 release, activities can be launched on that virtual display if the -associated feature is enabled. -</p> -<p> -To support multi-display features, you should either use one of the -existing supported ways of connecting secondary devices or build new hardware. -The supported ways of connecting displays on Nexus and Pixel devices are Google -Cast and <a -href="https://developer.android.com/reference/android/hardware/display/VirtualDisplay.html">virtual -displays inside apps</a>. Support of other ways depends on kernel driver support -for each particular case (like MHL or DisplayPort over USB-C) and fully -implementing interface definitions that are related to displays in -HardwareComposer HAL (IComposerCallback.hal and IComposerClient.hal). -</p> -<p> -Each of the ways may require SoC or OEM support. For example, to enable -DisplayPort over USB-C, both hardware (SOC) and software (drivers) support is -required. You might need to implement drivers for your hardware to support -connecting external displays. -</p> -<p> -The default implementation will allow launching fullscreen stacks of activities -on secondary displays. You can customize the stacks and System UI and -behavior on secondary displays. -</p> - -<h4>Support for generic tooltip</h4> -<p> -Android 8.0 allows developers to provide descriptive action names and other -helpful information on mouse hover over buttons and other icons. Device -manufacturers may style the tooltip popup. Its layout is defined in -<code>android/frameworks/base/core/res/res/layout/tooltip.xml</code>. -</a> -</p> -<p> -OEMs may replace the layout or change its dimensions and style parameters. Use -only text and keep the size reasonably small. The feature is implemented -entirely inside the View class, and there are quite exhaustive CTS tests that -check many aspects of Tooltip behavior. -</p> -<p> - -<h4>Support for extended aspect ratio</h4> -<p> -Android 8.0 includes a new manifest attribute, <a -href="https://developer.android.com/reference/android/R.attr.html#maxAspectRatio">maxAspectRatio</a>, -which lets an activity or app specify the maximum aspect ratio it supports. -maxAspectRatio replaces the previous meta-data tag with a first-class API and -allows devices to support an aspect ratio greater than 16:9. -</p><ul> -<li>If an activity or app is <a -href="https://developer.android.com/guide/topics/ui/multi-window.html#configuring">resizable</a>, -allow the activity to fill the screen. -<li>If an activity or app is non-resizeable or the platform is force resizing -the activity, allow the app window to display up to the maximum aspect ratio, -according to the <a -href="https://developer.android.com/reference/android/R.attr.html#maxAspectRatio">maxAspectRatio</a> -value. <ul> - <li>For applications on devices running Android 8.0, the default value is the -aspect ratio of the current device. - <li>For applications on devices running earlier versions of Android, the -default value is 16:9.</li> </ul> -</li> </ul> - -<h4>Implementing Adaptive Icons</h4> -<p> -Adaptive Icons maintain a consistent shape intra-device but vary from device to -device with only one icon asset provided by the developer. Additionally, icons -support two layers (foreground and background) that can be used for motion to -provide visual delight to users. For more information, see <a -href="/devices/tech/display/adaptive-icons.html">Implementing -Adaptive Icons</a>. -</p> - -<h4>Night Light</h4> -<p> -Night Light, introduced in Android 7.0.1, allows users to reduce the amount of -blue light that their screen emits. Android 8.0 gives users more control over the -intensity of this effect. For more information, see <a -href="/devices/tech/display/night-light.html">Implementing -Night Light</a>. -</p> - -<h4>Picture-in-picture</h4> -<p> -Android 8.0 includes support for picture-in-picture (PIP) on Android handheld -devices. PIP allows users to resize an app with an ongoing activity, such as a -video, into a small window. For more information, see <a -href="/devices/tech/display/pip.html">Picture-in-Picture -on Android handsets</a>. -</p> - -<h4>Better Split-Screen Interactions</h4> -<p> -Multi-window lets multiple apps simultaneously display on users' device screens. -Android 8.0 improves the default mode, split-screen, by compressing the top pane -and resizing the launcher if a user taps Home after entering split-screen. For -more information, see <a -href="/devices/tech/display/split-screen.html">Better -Split-Screen Interactions</a>. -</p> - -<h4>Add Widgets/Shortcuts</h4> -<p> -A new API in Android 8.0 allows application developers to add shortcuts and -widgets from inside the app instead of relying on the widget tray. The older -method of adding shortcuts by sending a broadcast has been deprecated for -security reasons. For more information, see <a -href="/devices/tech/display/widgets-shortcuts.html">Implementing -Add Widgets/Shortcuts</a>. -</p> - -<h3 id="downloading-building">Downloading and Building</h3> - -<h4>Android LLVM Toolchain improvements</h4> -<p> -OEMs who wish to use our latest toolchain/tools will need to ensure that any of -their private code compiles successfully with the updated toolchains. This may -require them to fix existing issues in their code with undefined behavior. (Of -course, they are free to use whatever tools they prefer to compile their own -code too.) -</p> -<p> -They must ensure their code is free of undefined behavior (by using tools like -UBSan), so they are less susceptible to problems caused by newer toolchains. All -of the toolchains are always updated directly in AOSP. Everything will be -available well before OC even ships, so OEMs should be following along -already. -</p> -<p> -See the <a href="https://llvm.org/">public Clang/LLVM</a> documentation for -general instructions and the <a -href="https://android.googlesource.com/platform/external/clang/+/dev/ReadmeAndroid.md">Android -Clang/LLVM</a> documentation set within AOSP for Android-specific guidance. -Finally, join the <a -href="https://groups.google.com/forum/#!forum/android-llvm">android-llvm</a> -public group to get help and take part in development. -</p> - -<h3 id="drm-kms">DRM / KMS</h3> - -<h4>DRM/KMS in Linux Kernel Version 4.9</h4> -<p> -The Direct Rendering Manager (DRM)/Kernel Mode Setting (KMS) framework used by -Android is developed and maintained by Linux kernel developers in the Linux -kernel. Android merges down from the Linux kernel. By merging down from our -common kernel, device manufacturers gain the DRM/KMS framework automatically. -</p> -<p> -DRM/KMS became viable in Linux kernel version 4.9, and Android <strong>strongly -encourages</strong> OEM partners to use DRM/KMS starting with this kernel -version. <a href="https://lwn.net/Articles/565422/">Atomic Display Framework -(ADF)</a>, the display framework officially supported by Android today, will not -be supported in 4.9 and higher versions of the common Android kernel; instead, -Android will support DRM/KMS from this version. OEMs can continue to use ADF (or -any other framework), but Android will not support them in the common Android -kernel. -</p> -<p> -To implement DRM/KMS, you will need to write your own drivers using -DRM/KMS in addition to merging down the DRM/KMS framework from the android -common kernel. -</p> - -<h3 id="keystore">Keystore</h3> - -<h4>Keymaster 3</h4> -<p> -Android 8.0 updates Keymaster, the keystore HAL, by extending the capabilities of -hardware-backed key storage on Android devices. This builds upon the Android 7.1.2 -updates to Keymaster 2. For more information, see <a -href="/security/keystore/index.html">Keymaster 3 documentation</a>. -</p> - -<h3 id="security-enhancements">Security Enhancements</h3> - -<h4>Insecure TLS Version Fallback removed from HttpsURLConnection</h4> -<p> -Insecure TLS/SSL protocol version fallback is a workaround for buggy -implementations of TLS protocol downgrade negotiation in some servers. This is -vulnerable to POODLE. When Chrome 45 dropped the insecure fallback in September -2015, less than 0.01% of servers relied on it. To improve security, insecure TLS -version fallback has been removed from <a -href="https://developer.android.com/reference/javax/net/ssl/HttpsURLConnection.html">HttpsURLConnection</a> -in Android 8.0. For more details, see <a -href="https://android-developers.googleblog.com/2017/04/android-o-to-drop-insecure-tls-version.html -">this blog post</a>. -</p> -<p> -To test this feature on devices with Android 8.0, run this CTS test case: -</p> - -<pre class="devsite-click-to-copy devsite-terminal" data-terminal-prefix="# "> -cts-tradefed run cts -m CtsLibcoreOkHttpTestCases</pre> - -<h3 id="performance">Performance</h3> - -<h4>Flash Wear Management</h4> -<p> -Describes eMMC behavior and new features to help OEMs lower the risk of a -failing eMMC in the automotive environment. For more information, see <a -href="/devices/tech/perf/flash-wear.html">Flash Wear -Management in Android Automotive</a>. -</p> - -<h4>Optimizing Boot Times</h4> -<p> -Guidance for improving boot times for specific Android devices. For more -information, see <a -href="/devices/tech/perf/boot-times.html">Optimizing -boot times</a>. -</p> - -<h4>Task Snapshots</h4> -<p> -Task Snapshots is infrastructure introduced in Android 8.0 that combines -screenshots for Recents Thumbnails as well as Saved Surfaces from Window Manager -to save memory. For more information, see <a -href="/devices/tech/perf/task-snapshots.html">Task -Snapshots</a>. -</p> - -<h3 id="peripherals">Peripherals</h3> - -<h4>Default Print Services</h4> -<p> -A <a -href="https://developer.android.com/reference/android/printservice/PrintService.html">print -service</a> is an app that discovers and presents printers to a device's print -framework. In earlier Android versions, users had to search for and install -third-party print services to be able to print. -</p> -<p> -Android 8.0 includes a default print service in <code><a -href="https://android.googlesource.com/platform/packages/services/BuiltInPrintService/">platform/packages/services/BuiltInPrintService/</a></code> -that lets users print on modern printers without installing any additional apps. -This implementation supports printers that use the Internet Printing Protocol -(IPP) to communicate with the printer and use PCLm, PWG-Raster, or PDF to send -printable content. For older printers, users should install the app recommended -by the <a -href="https://android.googlesource.com/platform/frameworks/base/+/android-7.0.0_r1/packages/PrintRecommendationService/">PrintRecommendationService</a> -as seen in this <a href="https://youtu.be/M_JGeGLpOKs?t=16m20s">this I/O presentation</a>. - -<h3 id="reference">Reference Updates</h3> - -<p> -The <a href="/reference/">Reference</a> section has been added to the top-level -navigation. As part of the <a href="/devices/architecture/treble">Treble</a> -release, a <a href="/reference/hidl/">HIDL reference</a> section was added. -The <a href="/reference/tradefed/">Trade Federation</a> and the -<a href="/reference/hal/">legacy HAL</a> reference documentation has been updated. -</p> - -<h3 id="settings-menu">Settings menu</h3> - -<h4>Settings: Patterns and Components</h4> -<p> -In Android 8.0, the Settings menu gains several components and widgets that -cover common uses. For more information, see <a -href="/devices/tech/settings/patterns-components.html">Patterns -and Components</a>. -</p> - -<h4>Settings: Updated information architecture</h4> -<p> -Android 8.0 introduces a new information architecture for the Settings app. The -goal of the new information architecture is to simplify the way settings are -organized and make it easier for users to quickly find the settings needed to -customize their Android devices. For more information, see Implementing <a -href="/devices/tech/settings/info-architecture.html">Updated -Information Architecture</a>. -</p> - -<h4>Personalized Settings</h4> -<p> -The Android Settings app provides a list of suggestions to the users. This -feature provides ranking for suggestions, based on any contextual signal or the -user's past interactions with suggestions. For more information, see <a -href="/devices/tech/settings/personalized.html">Personalized -Settings</a>. -</p> - -<h4>Implementing Settings: Universal Search</h4> -<p> -Android 8.0 adds expanded search capabilities for the Settings menu. This document -describes how to add a setting and ensure it is properly indexed for Settings. -For more information, see <a -href="/devices/tech/settings/universal-search.html">Universal -Search</a>. -</p> - -<h3 id="storage">Storage</h3> - -<h4>Faster storage statistics</h4> -<p> -Android 8.0 leverages the ext4 filesystem's "quota" support to return disk usage -statistics almost instantly. For more information, see <a -href="/devices/storage/faster-stats.html">Implementing -faster storage statistics</a>. -</p> - -<h2 id="april-2017">April 2017</h2> -<p>Welcome to a new source.android.com! The site has been overhauled to make it -easier for you to navigate, search, and read its ever-growing set of information. -Here is a summary of enhancements:</p> - -<h3 id="screen-estate">More screen real estate, larger type size</h3> -<p>The entire site is wider, allowing you to view more content at once. Code -samples and commands are more visible, and all text has been enlarged.</p> - -<h3 id="mobile-ready">Mobile-ready view</h3> -<p>The new site renders more cleanly on handheld devices with a dedicated -mobile view.</p> - -<div style="width:407px"> - <img src="images/mobile-view.png" alt="new mobile view" height="533px" /> - <p class="img-caption"> - <strong>Figure 1.</strong> Site's new mobile view - </p> -</div> - -<h3 id="top-tabs">New top-level tabs</h3> -<p>The former <em>Devices</em> tab has been renamed <a -href="/devices/">Porting</a>, while the old <em>Core Technologies</em> -subtab has been renamed <a href="/devices/tech/">Tuning</a> and moved to the top -of the site for better exposure.</p> - -<h3 id="security-forefront">Security at the forefront</h3> -<p>With an ever-increasing focus on security in Android, the <a -href="/security/">Security</a> tab has been moved forward (next to <a -href="/setup/">Source</a>) to reflect its importance.</p> - -<h3 id="reference-materials">Better reference materials</h3> -<p><a href="/reference/hal/">Hardware Abstraction Layer</a> and <a -href="/reference/tradefed/packages">Trade Federation</a> reference -materials are available directly from a top-level <a -href="/reference/">Reference</a> tab.</p> - -<h3 id="code-links">Persistent code links</h3> -<p>The <a href="https://android.googlesource.com/">AOSP code -repository</a> is always just a click away with the <strong>Go to Code</strong> -button at the top right of every page.</p> - -<h3 id="comprehensive-footers">Comprehensive footers</h3> -<p>In addition to the existing <em>About</em>, <em>Community</em>, and -<em>Legal</em> footers, you can now find a complete list of links at the bottom -of every page for building Android, connecting with the ecosystem, and getting -help with the operating system's use.</p> - - </body> -</html> diff --git a/en/setup/brands.html b/en/setup/start/brands.html index ca08b8dd..c530e043 100644 --- a/en/setup/brands.html +++ b/en/setup/start/brands.html @@ -79,23 +79,23 @@ assets.</p> </ul> <h4>Acceptable examples</h4> -<img src="images/JB-TM-example.png" alt="Jelly Bean trademark example" /> -<img src="images/8100-TM-example.png" alt="8100 series trademark example" /> +<img src="../images/JB-TM-example.png" alt="Jelly Bean trademark example" /> +<img src="../images/8100-TM-example.png" alt="8100 series trademark example" /> <h4>Unacceptable example</h4> -<img src="images/XBrand-TM-example.jpg" alt="XBrand trademark example" /> +<img src="../images/XBrand-TM-example.jpg" alt="XBrand trademark example" /> <h3 id="logo-android">Android logo</h3> <p>Unless expressly authorized by Google through written agreement, the Android logo and custom typeface may not be used (with or without the Android robot).</p> -<img alt="No Logo" src="images/android_logo_new_crossed_out.png"> +<img alt="No Logo" src="../images/android_logo_new_crossed_out.png"> <img alt="No Logo" src="https://developer.android.com/images/brand/android_logo_no.png"> <h3 id="robot-android">Android robot</h3> <div class="wrap"> <div class="col-4"> - <img alt="android-robot" style="float:left;margin-right:10px" src="/setup/images/Android_Robot_100.png"> + <img alt="android-robot" style="float:left;margin-right:10px" src="../images/Android_Robot_100.png"> <p style="padding-top:20px"> <a href="https://developer.android.com/images/brand/Android_Robot_100.png">100x118</a><br> <a href="https://developer.android.com/images/brand/Android_Robot_200.png">200x237</a><br> @@ -115,7 +115,7 @@ license</a>.</p> <div class="wrap" style="padding-top:20px"> <div class="col-4" style="align:center"> -<img alt="no-peace-robot" style="width:30%;height:30%" src="images/No_PeaceBot_200.jpg"> +<img alt="no-peace-robot" style="width:30%;height:30%" src="../images/No_PeaceBot_200.jpg"> </div> <div class="col-8"> <p style="padding-top:20px">The Android Peace Robot or any variation of the @@ -130,7 +130,7 @@ used in partner marketing.</p> <p>Use of the “Google Play†name and the Google Play Store icon on the packaging of the hardware, marketing materials of the hardware, or the hardware itself is allowed only on devices -<a href="/setup/faqs.html#if-my-device-is-compatible-does-it-automatically-have-access-to-google-play-and-branding">licensed +<a href="/setup/start/faqs.html#if-my-device-is-compatible-does-it-automatically-have-access-to-google-play-and-branding">licensed to access Google Play</a>. For a list of devices licensed to use Google Play, refer to <a href="https://support.google.com/googleplay/answer/1727131">Supported diff --git a/en/setup/build-numbers.html b/en/setup/start/build-numbers.html index dcfc5c0d..21519cb9 100644 --- a/en/setup/build-numbers.html +++ b/en/setup/start/build-numbers.html @@ -23,11 +23,11 @@ -<p>At a high level, Android development happens around families of -releases, which use code names ordered alphabetically after tasty -treats.</p> +<p>Android development happens around families of releases that use code names +ordered alphabetically after tasty treats.</p> -<h2 id="platform-code-names-versions-api-levels-and-ndk-releases">Platform Codenames, Versions, API Levels, and NDK Releases</h2> +<h2 id="platform-code-names-versions-api-levels-and-ndk-releases">Platform +Codenames, Versions, API Levels, and NDK Releases</h2> <p>The code names match the following version numbers, along with API levels and NDK releases provided for convenience:</p> <table> @@ -171,38 +171,58 @@ API levels and NDK releases provided for convenience:</p> </tr> </tbody> </table> -<p>Starting with Oreo, individual builds are identified with a new build ID format, in the form of PVBB.YYMMDD.bbb[.Cn].</p> -<p>The P part represents the first letter of the code name of the platform release, e.g. O is Oreo.</p> -<p>The V part represents a supported vertical. By convention, 'P' represents the primary platform branch.</p> -<p>The BB part represents a alpha numeric code which allows Google to identify the exact code branch that the build was made from.</p> -<p>The YYMMDD part identifies the date when the release is branched from or synced with the development branch. It is not guaranteed to be the exact date at which a build was made, and it is common that minor variations added to an existing build re-use the same date code as that existing build.</p> -<p>The bbb part identifies individual versions related to the same date code, sequentially starting with 001.</p> -<p>An optional, alphanumeric Cn part identifies a hotfix on top of an existing PVBB.YYMMDD.bbb build, starting from A1.</p> -<p>Older Android releases from Cupcake to Nougat uses a different build ID scheme. These Android builds are identified with a short build code, e.g. FRF85B. -</p> -<p>The first letter is the code name of the release family, e.g. F is -Froyo.</p> -<p>The second letter is a branch code that allows Google to identify -the exact code branch that the build was made from, and R is by -convention the primary release branch.</p> -<p>The next letter and two digits are a date code. The letter counts -quarters, with A being Q1 2009. Therefore, F is Q2 2010. The two -digits count days within the quarter, so F85 is June 24 2010.</p> -<p>Finally, the last letter identifies individual versions related to -the same date code, sequentially starting with A; A is actually -implicit and usually omitted for brevity.</p> -<p>The date code is not guaranteed to be the exact date at which a build -was made, and it is common that minor variations added to an existing -build re-use the same date code as that existing build.</p> + +<p>In Android 8.0 (Oreo) and higher, individual builds are identified with the + build ID format <strong>PVBB.YYMMDD.bbb[.Cn]</strong>, where:</p> +<ul> + <li>P represents the first letter of the code name of the platform release, + e.g. O is Oreo.</li> + <li>V represents a supported vertical. By convention, P represents the primary + platform branch.</li> + <li>BB represents an alphanumeric code that allows Google to identify the + exact code branch the build was made from.</li> + <li>YYMMDD identifies the date when the release is branched from or synced + with the development branch. It is not guaranteed to be the exact date at + which a build was made as it is common for minor variations added to an + existing build to re-use the same date code as the existing build.</li> + <li>bbb identifies individual versions related to the same date code, + sequentially starting with 001.</li> + <li>Cn is an optional, alphanumeric that identifies a hotfix on top of an + existing PVBB.YYMMDD.bbb build, starting from A1.</li> +</ul> + +<p>Older Android releases use a different, shorter build ID code (e.g. + <strong>FRF85B</strong>) where:</p> + +<ul> + <li>The first letter is the code name of the release family, e.g. F is Froyo. + </li> + <li>The second letter is a branch code that allows Google to identify the + exact code branch the build was made from. By convention, R is the primary + release branch.</li> + <li>The third letter and following two digits are a date code. The letter + counts quarters (A = Q1 2009, F = Q2 2010, etc.). The two digits count days + within the quarter (F85 is June 24 2010). The date code is not guaranteed to + be the exact date at which a build was made as it is common for minor + variations added to an existing build to re-use the same date code as the + existing build.</li> + <li>The last letter identifies individual versions related to the same date + code, sequentially starting with A (which is implicit and usually omitted for + brevity.</li> <h2 id="source-code-tags-and-builds">Source Code Tags and Builds</h2> <p>Starting with Donut, the exact list of tags and builds is in the -following table. Factory images, binaries, and full OTA images for -Nexus and Pixel devices can be downloaded from the Android Developer -site:</p> -<p><a href="https://developers.google.com/android/images">Images</a></p> -<p><a href="https://developers.google.com/android/drivers">Drivers</a></p> -<p><a href="https://developers.google.com/android/ota">OTA</a></p> +following table. + +<aside class="note"><strong>Note:</strong> To download + <a href="https://developers.google.com/android/images">factory images</a>, + <a href="https://developers.google.com/android/drivers">drivers</a>, and full + <a href="https://developers.google.com/android/ota">OTA</a> images for Nexus + and Pixel devices, refer to the + <a href="https://developers.google.com/android/">Android Developer site</a>. +</aside> + + <table> <thead> <tr> @@ -214,6 +234,36 @@ site:</p> </thead> <tbody> <tr> + <td>OPM4.171019.015.A1</td> + <td>android-8.1.0_r23</td> + <td>Oreo</td> + <td>Pixel 2 XL, Pixel 2</td> + </tr> + <tr> + <td>OPM5.171019.019</td> + <td>android-8.1.0_r22</td> + <td>Oreo</td> + <td>Nexus 6P</td> + </tr> + <tr> + <td>OPM3.171019.019</td> + <td>android-8.1.0_r21</td> + <td>Oreo</td> + <td>Nexus 6P</td> + </tr> + <tr> + <td>OPM2.171019.029</td> + <td>android-8.1.0_r20</td> + <td>Oreo</td> + <td>Pixel 2 XL, Pixel 2, Pixel XL, Pixel, Nexus 5X</td> + </tr> + <tr> + <td>OPM1.171019.026</td> + <td>android-8.1.0_r19</td> + <td>Oreo</td> + <td>Pixel C</td> + </tr> + <tr> <td>OPM5.171019.017</td> <td>android-8.1.0_r18</td> <td>Oreo</td> @@ -2304,32 +2354,38 @@ site:</p> </tr> </tbody> </table> -<p>The branches froyo, gingerbread, ics-mr0, ics-mr1, jb-dev, -jb-mr1-dev, jb-mr1.1-dev, jb-mr2-dev, kitkat-dev -represent development -branches that do not exactly match configurations that were tested -by Google. They might contain a variety of changes in addition to -the official tagged releases, and those haven't been as thoroughly -tested.</p> -<p>To differentiate between releases, you may obtain a list of changes +<p>The branches froyo, gingerbread, ics-mr0, ics-mr1, jb-dev, jb-mr1-dev, + jb-mr1.1-dev, jb-mr2-dev, kitkat-dev represent development branches that do + not exactly match configurations tested by Google. As such, these branches + might contain a variety of changes in addition to the official tagged releases + and might not be as thoroughly tested.</p> + +<p>To differentiate between releases, you can obtain a list of changes associated with each project by issuing the following command and passing it the two branch tags:</p> -<pre class="devsite-terminal devsite-click-to-copy">repo forall -pc 'git log --no-merges --oneline branch-1..branch-2'</pre> +<pre class="devsite-terminal devsite-click-to-copy"> +repo forall -pc 'git log --no-merges --oneline branch-1..branch-2' +</pre> <p>For example:</p> -<pre class="devsite-terminal devsite-click-to-copy">repo forall -pc 'git log --no-merges --oneline android-4.4.2_r2..android-4.4.2_r1'</pre> +<pre class="devsite-terminal devsite-click-to-copy"> +repo forall -pc 'git log --no-merges --oneline android-4.4.2_r2..android-4.4.2_r1' +</pre> -<p>And to output to a text file:</p> +<p>To send the output to a text file:</p> -<pre class="devsite-terminal devsite-click-to-copy">repo forall -pc 'git log --no-merges --oneline android-4.4.2_r2..android-4.4.2_r1' > /tmp/android-4.4.2_r2-android-4.4.2_r1-diff.txt</pre> +<pre class="devsite-terminal devsite-click-to-copy"> + repo forall -pc 'git log --no-merges --oneline android-4.4.2_r2..android-4.4.2_r1' > /tmp/android-4.4.2_r2-android-4.4.2_r1-diff.txt +</pre> <h2 id="honeycomb-gpl-modules">Honeycomb GPL Modules</h2> -<p>For Honeycomb, the entire platform source code isn't available. -However, the parts of Honeycomb licensed under the GPL and LGPL -are available under the following tags:</p> + +<p>For Honeycomb, the entire platform source code isn't available. However, the +parts of Honeycomb licensed under the GPL and LGPL are available under the +following tags:</p> <table> <thead> @@ -2402,18 +2458,20 @@ are available under the following tags:</p> </tr> </tbody> </table> -<p>There is no manifest that contains exactly those. However, there -are manifests that allow building those components. The following -commands work for 3.0_r1.1, and using other versions can be done by -switching the git checkout paramater, and if necessary the -m parameter in -repo init. The git checkout command outputs an error for the non-GPL -projects, where it can't find the tag in question.</p> + +<p>While no manifest contains exactly these modules, some manifests allow + building those components. The following commands work for 3.0_r1.1:</p> + <pre class="devsite-click-to-copy"> <code class="devsite-terminal">repo init -b master -m base-for-3.0-gpl.xml</code> <code class="devsite-terminal">repo sync</code> <code class="devsite-terminal">repo forall -c git checkout android-3.0_r1.1</code> </pre> +<p>To use another version, switch the <code>git checkout</code> parameter and + (if necessary) the <code>-m</code> parameter in <code>repo init</code>. The + <code>git checkout</code> command outputs an error for the + non-GPL projects, where it can't find the tag in question.</p> </body> </html> diff --git a/en/setup/start/codelines.html b/en/setup/start/codelines.html new file mode 100644 index 00000000..654d412c --- /dev/null +++ b/en/setup/start/codelines.html @@ -0,0 +1,168 @@ +<html devsite> + <head> + <title>Codelines, Branches, and Releases</title> + <meta name="project_path" value="/_project.yaml" /> + <meta name="book_path" value="/_book.yaml" /> + </head> + <body> + <!-- + Copyright 2017 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 + + http://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> + The Android Open Source Project (AOSP) maintains a complete software stack to + be ported by OEMs and other device implementors and run on their own hardware. + To maintain the quality of Android, Google has contributed full-time + engineers, product managers, user interface designers, quality assurance + testers, and all the other roles required to bring modern devices to market. +</p> + +<p> + Accordingly, we maintain a number of codelines to clearly separate the current + stable version of Android from unstable experimental work. We roll the open + source administration and maintenance of the Android codelines into the larger + product development cycle. +</p> + +<h2 id="aosp-management">AOSP code management</h2> +<p> + The chart below depicts the concepts behind AOSP code management and releases. +</p> + +<img src="/images/code-lines.png" alt="codeline diagram" id="figure1" > +<figcaption><strong>Figure 1.</strong> AOSP code and releases</figcaption> + +<ol> + <li> + At any given moment, there is a current latest release of the Android + platform. This typically takes the form of a branch in the tree. + </li> + <li> + Device builders and contributors work with the current latest release, + fixing bugs, launching new devices, experimenting with new features, etc. + </li> + <li> + In parallel, Google works internally on the next version of the Android + platform and framework according to the product's needs and goals. We + develop the next version of Android by working with a device partner on a + flagship device whose specifications are chosen to push Android in the + direction we believe it should go. + </li> + <li> + When the n+1th version is ready, it is published to the public source + tree and become the new latest release. + </li> +</ol> + +<aside class="note"><strong>Note:</strong> We use the term <em>codelines</em> + instead of <em>branches</em> simply because at any given moment there may be + more than one branch for a given codeline. For instance, when a release is + cut, it may or may not become a new branch based on the needs of the moment. +</aside> + + +<h2 id="terms-and-caveats">Terms and Caveats</h2> + +<ul> + <li> + A <em>release</em> corresponds to a formal version of the Android platform, + such as 1.5, 2.1, and so on. A release of the platform corresponds to the + version in the <code>SdkVersion</code> field of + <code>AndroidManifest.xml</code> files and defined within + <code>frameworks/base/api</code> in the source tree. + </li> + <li> + An <em>upstream</em> project is an open source project from which the + Android stack pulls code. In addition to projects such as the Linux kernel + and WebKit, we continue to migrate some semi-autonomous Android projects + such as ART, the Android SDK tools, Bionic, and so on to work as + upstream projects. Generally, these projects are developed entirely in the + public tree. For some upstream projects, development is done by contributing + directly to the upstream project itself. For details, see + <a href="../contribute/submit-patches.html#upstream-projects">Upstream + projects</a>. In both cases, snapshots are periodically pulled into + releases. + </li> + <li> + At all times, a release codeline (which may actually consist of more than + one actual branch in git) is considered the sole canonical source code for a + given Android platform version. OEMs and other groups building devices + should pull only from a release branch. + </li> + <li> + Experimental codelines are established to capture changes from the community + so they can be iterated on with an eye toward stability. + </li> + <li> + Changes that prove stable are eventually be pulled into a release branch. + This applies only to bug fixes, application improvements, and other changes + that do not affect the APIs of the platform. + </li> + <li> + Changes are pulled into release branches from upstream projects + (including the Android upstream projects) as necessary. + </li> + <li> + The n+1th version (the next major version of the framework and platform + APIs) is developed by Google internally. For details, see + <a href="#private-codelines">Private codelines</a>. + </li> + <li> + Changes are pulled from upstream, release, and experimental branches into + Google's private branch as necessary. + </li> + <li> + When the platform APIs for the next version have stabilized and been fully + tested, Google cuts a release of the next platform version (specifically, a + new <code>SdkVersion</code>). This corresponds to the internal codeline + being made a public release branch and the new current platform codeline. + </li> + <li> + When a new platform version is cut, a corresponding experimental codeline is + created at the same time. + </li> +</ul> + +<h2 id="private-codelines">Private codelines</h2> +<p> + The source management strategy above includes a codeline that Google keeps + private to focus attention on the current public version of Android. +</p> +<p> + OEMs and other device builders naturally want to ship devices with the latest + version of Android. Similarly, application developers don't want to deal with + more platform versions than strictly necessary. Meanwhile, Google retains + responsibility for the strategic direction of Android as a platform and a + product. Our approach focuses on a small number of flagship devices to drive + features while securing protections of Android-related intellectual property. +</p> +<p> + As a result, Google frequently has possession of confidential information from + third parties and must refrain from revealing sensitive features until + securing the appropriate protections. In addition, there are real risks to the + platform arising from having too many platform versions extant at once. For + these reasons, we have structured the open source project (including + third-party contributions) to focus on the currently-public stable version of + Android. Deep development on the next version of the platform occurs in + private until it's ready to become an official release. +</p> +<p> + We recognize many contributors disagree with this approach and we respect + their different points of view. However, this is the approach we feel is best + and the one we've chosen to implement for Android. +</p> + + </body> +</html> diff --git a/en/setup/faqs.html b/en/setup/start/faqs.html index 938f07c5..f8611db8 100644 --- a/en/setup/faqs.html +++ b/en/setup/start/faqs.html @@ -24,19 +24,26 @@ <a name="top"></a> -<p>Please see the <a -href="http://developer.android.com/guide/faq/index.html">Android FAQs</a> on -developer.android.com for answers to other common questions. +<p> + This page provides answers to Frequently Asked Questions (FAQs). For answers + other common questions, refer to + <a href="http://developer.android.com/guide/faq/index.html" class="external">Android + FAQs</a> on developer.android.com. +</p> <h2 id="open-source">Open Source</h2> -<h3 id="what-is-the-android-open-source-project">What is the Android Open Source Project?</h3> + +<h3 id="what-is-the-android-open-source-project">What is the Android Open Source +Project?</h3> <p>We use the phrase "Android Open Source Project" or "AOSP" to refer to the people, the processes, and the source code that make up Android.</p> <p>The people oversee the project and develop the actual source code. The processes refer to the tools and procedures we use to manage the development of the software. The net result is the source code you can use to build mobile phones and other devices.</p> -<h3 id="why-did-we-open-the-android-source-code">Why did we open the Android source code?</h3> + +<h3 id="why-did-we-open-the-android-source-code">Why did we open the Android +source code?</h3> <p>Google started the Android project in response to our own experiences launching mobile apps. We wanted to make sure there would always be an open platform available for carriers, OEMs, and developers to use to make @@ -46,15 +53,19 @@ the innovations of any other. The single most important goal of the Android Open Source Project (AOSP) is to make sure that the open source Android software is implemented as widely and compatibly as possible, to everyone's benefit.</p> -<h3 id="what-kind-of-open-source-project-is-android">What kind of open source project is Android?</h3> + +<h3 id="what-kind-of-open-source-project-is-android">What kind of open source +project is Android?</h3> <p>Google oversees the development of the core Android open source platform and works to create robust developer and user communities. For the most part, the Android source code is licensed under the permissive Apache Software License 2.0, rather than a "copyleft" license. The main reason for this is because our most important goal is widespread adoption of the software, and -we believe that the ASL2.0 license best achieves that goal.</p> -<p>You can find more information on this topic on our <a href="/setup/licenses.html">Licenses</a> page.</p> -<h3 id="why-is-google-in-charge-of-android">Why is Google in charge of Android?</h3> +we believe that the ASL2.0 license best achieves that goal. For details, see +<a href="licenses.html">Licenses</a>.</p> + +<h3 id="why-is-google-in-charge-of-android">Why is Google in charge of +Android?</h3> <p>Launching a software platform is complex. Openness is vital to the long-term success of a platform, since openness is required to attract investment from developers and ensure a level playing field. However, the @@ -67,10 +78,12 @@ devices running Android actually make it to market.</p> <p>By making sure Android is a success with users, we help ensure the vitality of Android as a platform and as an open source project. After all, who wants the source code to an unsuccessful product?</p> -<p>Google's goal is to ensure a successful ecosystem around Android. Of course, no -one is required to participate. We opened the Android source code -so anyone can modify and distribute the software to meet their own needs.</p> -<h3 id="what-is-googles-overall-strategy-for-android-product-development">What is Google's overall strategy for Android product development?</h3> +<p>Google's goal is to ensure a successful ecosystem around Android. Of course, +no one is required to participate. We opened the Android source code so anyone +can modify and distribute the software to meet their own needs.</p> + +<h3 id="what-is-googles-overall-strategy-for-android-product-development">What +is Google's overall strategy for Android product development?</h3> <p>We aim to release great devices into a competitive marketplace. We then incorporate the innovations and enhancements we made into the core platform as the next version.</p> @@ -81,7 +94,9 @@ devices absorb much of the product risk and blaze a trail for the broad OEM community, who follow up with many more devices that take advantage of the new features. In this way, we make sure the Android platform evolves according to the actual needs of real-world devices.</p> -<h3 id="how-is-the-android-software-developed">How is the Android software developed?</h3> + +<h3 id="how-is-the-android-software-developed">How is the Android software +developed?</h3> <p>Each platform version of Android (such as 1.5, 1.6, and so on) has a corresponding branch in the open source tree. At any given moment, the most recent such branch will be considered the "current stable" branch version. @@ -94,12 +109,14 @@ stable branch from the experimental branch as appropriate.</p> <p>Finally, Google works on the next version of the Android platform in tandem with developing a flagship device. This branch pulls in changes from the experimental and stable branches as appropriate.</p> -<p>You can find more information on this topic at our <a href="/setup/code-lines.html">Codelines, -Branches and Releases</a> page.</p> -<h3 id="why-are-parts-of-android-developed-in-private">Why are parts of Android developed in private?</h3> -<p>It typically takes more than a year to bring a device to market. And, of course, -device manufacturers want to ship the latest software they can. Developers, -meanwhile, don't want to constantly track new versions of the +<p>For details, see <a href="codelines.html">Codelines, Branches and +Releases</a>.</p> + +<h3 id="why-are-parts-of-android-developed-in-private">Why are parts of Android +developed in private?</h3> +<p>It typically takes more than a year to bring a device to market. And, of +course, device manufacturers want to ship the latest software they can. +Developers, meanwhile, don't want to constantly track new versions of the platform when writing apps. Both groups experience a tension between shipping products and not wanting to fall behind.</p> <p>To address this, some parts of the next version of Android including the @@ -112,7 +129,9 @@ future work just to keep up. Other parts of the Android system that aren't related to application compatibility are developed in the open, however. It's our intention to move more of these parts to open development over time.</p> -<h3 id="when-are-source-code-releases-made">When are source code releases made?</h3> + +<h3 id="when-are-source-code-releases-made">When are source code releases +made?</h3> <p>When they are ready. Releasing the source code is a fairly complex process. Some parts of Android are developed in the open, so that source code is always available. Other parts are developed first in @@ -120,24 +139,26 @@ a private tree, and that source code is released when the next platform version is ready.</p> <p>In some releases, core platform APIs will be ready far enough in advance that we can push the source code out for an early look prior to the -device's release; however in other releases, this isn't possible. In all cases, we -release the platform source when we feel the version has stabilized enough, +device's release; however in other releases, this isn't possible. In all cases, +we release the platform source when we feel the version has stabilized enough, and when the development process permits.</p> -<h3 id="what-is-involved-in-releasing-the-source-code-for-a-new-android-version">What is involved in releasing the source code for a new Android version?</h3> + +<h3 id="what-is-involved-in-releasing-the-source-code-for-a-new-android-version">What +is involved in releasing the source code for a new Android version?</h3> <p>Releasing the source code for a new version of the Android platform is a significant process. First, the software gets built into a system image for a device and put through various forms of certification, including government regulatory certification for the regions the phones will be deployed. It also goes through operator testing. This is an important phase -of the process, since it helps shake out a lot of software bugs.</p></p> +of the process, since it helps shake out a lot of software bugs.</p> <p>Once the release is approved by the regulators and operators, the manufacturer begins mass producing devices, and we turn to releasing the source code.</p> <p>Simultaneous to mass production, the Google team kicks off several efforts -to prepare the open source release. These efforts include making final API changes, -updating documentation (to reflect any modifications that were made during -qualification testing, for example), preparing an SDK for the new version, -and launching the platform compatibility information.</p> +to prepare the open source release. These efforts include making final API +changes, updating documentation (to reflect any modifications that were made +during qualification testing, for example), preparing an SDK for the new +version,and launching the platform compatibility information.</p> <p>Also included is a final legal sign-off to release the code into open source. Just as open source contributors are required to sign a Contributors License Agreement attesting to their intellectual property ownership of their @@ -145,7 +166,9 @@ contribution, Google too must verify it is clear to make contributions.</p> <p>From the time mass production begins, the software release process usually takes around a month. This often places source code releases around the same time the devices reach users.</p> -<h3 id="how-does-the-aosp-relate-to-the-android-compatibility-program">How does the AOSP relate to the Android Compatibility Program?</h3> + +<h3 id="how-does-the-aosp-relate-to-the-android-compatibility-program">How does +AOSP relate to the Android Compatibility Program?</h3> <p>The Android Open Source Project maintains the Android software, and develops new versions. Since it's open source, this software can be used for any purpose, including to develop devices that are not compatible with other @@ -158,8 +181,9 @@ compatibility requirements exist outside that ecosystem.</p> <p>In other words, the Android Compatibility Program is how we separate "Android-compatible devices" from devices that merely run derivatives of the source code. We welcome all uses of the Android source code, but only -Android-compatible devices -- as defined and tested by the Android -Compatibility Program -- may participate in the Android ecosystem.</p> +Android-compatible devices (as defined and tested by the Android +Compatibility Program) may participate in the Android ecosystem.</p> + <h3 id="how-can-i-contribute-to-android">How can I contribute to Android?</h3> <p>There are a number of ways you can contribute to Android. You can report bugs, write apps for Android, or contribute source code to the Android @@ -171,23 +195,28 @@ decline that contribution, since Android encourages applications to be run in the ART runtime. Similarly, we won't accept contributions such as GPL or LGPL libraries that are incompatible with our licensing goals.</p> <p>We encourage those interested in contributing source code to contact us -via the channels listed on the <a href="/setup/community.html"> -Android Community</a> page prior to beginning any work. You can find more -information on this topic from the <a href="/setup/contributing.html"> -Contributing</a> page.</p> -<h3 id="how-do-i-become-an-android-committer">How do I become an Android committer?</h3> +via the channels listed on the <a href="../community.html"> +Android Community</a> page prior to beginning any work. For details, see +<a href="../contribute/index.html">Contributing</a>.</p> + +<h3 id="how-do-i-become-an-android-committer">How do I become an Android +committer?</h3> <p>The Android Open Source Project doesn't really have a notion of a -"committer". All contributions -- including those authored by Google -employees -- go through a web-based system known as "gerrit" that's part of +"committer". All contributions (including those authored by Google +employees) go through a web-based system known as "gerrit" that's part of the Android engineering process. This system works in tandem with the git source code management system to cleanly manage source code contributions.</p> <p>Once submitted, changes need to be accepted by a designated Approver. Approvers are typically Google employees, but the same approvers are responsible for all submissions, regardless of origin.</p> -<p>You can find more information on this topic at the <a href="submit-patches.html">Submitting Patches</a> page.</p> +<p>For details, see <a href="../contribute/submit-patches.html">Submitting +Patches</a>.</p> + <a href="#top">Back to top</a> + <h2 id="compatibility">Compatibility</h2> + <h3 id="what-does-compatibility-mean">What does "compatibility" mean?</h3> <p>We define an "Android-compatible device" as one that can run any application written by third-party developers using the Android SDK and NDK. @@ -200,13 +229,17 @@ use the Android trademark.</p> Android apps ecosystem. Anyone is welcome to use the Android source code. But if the device isn't compatible, it's not considered part of the Android ecosystem.</p> -<h3 id="what-is-the-role-of-google-play-in-compatibility">What is the role of Google Play in compatibility?</h3> + +<h3 id="what-is-the-role-of-google-play-in-compatibility">What is the role of +Google Play in compatibility?</h3> <p>Devices that are Android compatible may seek to license the Google Play client software. This allows them to become part of the Android app ecosystem, enabling their users to download developers' apps from a catalog shared by all compatible devices. This option isn't available to devices that aren't compatible.</p> -<h3 id="what-kinds-of-devices-can-be-android-compatible">What kinds of devices can be Android compatible?</h3> + +<h3 id="what-kinds-of-devices-can-be-android-compatible">What kinds of devices +can be Android compatible?</h3> <p>The Android software can be ported to many different kinds of devices, including some on which third-party apps won't run properly. The <a href="/compatibility/index.html">Android Compatibility Definition @@ -214,58 +247,77 @@ Document</a> (CDD) spells out the specific device configurations that will be considered compatible.</p> <p>For example, though the Android source code could be ported to run on a phone that doesn't have a camera, the CDD requires all phones to have a camera. -This allows developers to rely on a consistent set of capabilities when writing their apps.</p> +This allows developers to rely on a consistent set of capabilities when writing +their apps.</p> <p>The CDD will evolve over time to reflect market realities. For instance, version 1.6 of the CDD supports only cell phones. But the 2.1 CDD allows devices -to omit telephony hardware, enabling non-phone devices such as tablet-style music -players to be compatible. As we make these changes, we will also +to omit telephony hardware, enabling non-phone devices such as tablet-style +music players to be compatible. As we make these changes, we will also augment Google Play to allow developers to retain control over where their apps are available. To continue the telephony example, an app that manages SMS text messages would not be useful on a media player, so Google -Play allows the developer to restrict that app exclusively to phone -devices.</p> -<h3 id="if-my-device-is-compatible-does-it-automatically-have-access-to-google-play-and-branding">If my device is compatible, does it automatically have access to Google Play and branding?</h3> +Play allows the developer to restrict that app exclusively to phone devices.</p> + +<h3 id="if-my-device-is-compatible-does-it-automatically-have-access-to-google-play-and-branding">If +my device is compatible, does it automatically have access to Google Play and +branding?</h3> <p>Google Play is a service operated by Google. Achieving compatibility is a prerequisite for obtaining access to the Google Play software and branding. Device manufacturers should complete the contact form included in <a href="/compatibility/contact-us#for-business-inquiries">licensing Google Mobile Services</a> to seek access to Google Play. We will be in contact if we can help you.</p> -<h3 id="if-i-am-not-a-manufacturer-how-can-i-get-google-play">If I am not a manufacturer, how can I get Google Play?</h3> + +<h3 id="if-i-am-not-a-manufacturer-how-can-i-get-google-play">If I am not a +manufacturer, how can I get Google Play?</h3> <p>Google Play is only licensed to handset manufacturers shipping devices. For questions about specific cases, contact <a -href="mailto:android-partnerships@google.com">android-partnerships@google.com</a>.</p> -<h3 id="how-can-i-get-access-to-the-google-apps-for-android-such-as-maps">How can I get access to the Google apps for Android, such as Maps?</h3> +href="mailto:android-partnerships@google.com">android-partnerships@google.com</a>. +</p> + +<h3 id="how-can-i-get-access-to-the-google-apps-for-android-such-as-maps">How +can I get access to the Google apps for Android, such as Maps?</h3> <p>The Google apps for Android, such as YouTube, Google Maps, Gmail, and more, are Google properties that are not part of Android and are licensed separately. Contact <a href="mailto:android-partnerships@google.com">android-partnerships@google.com</a> for inquiries related to those apps.</p> + <h3 id="is-compatibility-mandatory">Is compatibility mandatory?</h3> <p>No. The Android Compatibility Program is optional. Since the Android source -code is open, anyone can use it to build any kind of device. However, if manufacturers -wish to use the Android name with their products, or want access to Google Play, -they must first demonstrate their devices are compatible.</p> -<h3 id="how-much-does-compatibility-certification-cost">How much does compatibility certification cost?</h3> +code is open, anyone can use it to build any kind of device. However, if +manufacturers wish to use the Android name with their products, or want access +to Google Play, they must first demonstrate their devices are compatible.</p> + +<h3 id="how-much-does-compatibility-certification-cost">How much does +compatibility certification cost?</h3> <p>There is no cost to obtain Android compatibility for a device. The -Compatibility Test Suite is open source and available to anyone for device testing.</p> +Compatibility Test Suite is open source and available to anyone for device +testing.</p> + <h3 id="how-long-does-compatibility-take">How long does compatibility take?</h3> <p>The process is automated. The Compatibility Test Suite generates a report that can be provided to Google to verify compatibility. Eventually we intend to provide self-service tools to upload these reports to a public database.</p> -<h3 id="who-determines-what-will-be-part-of-the-compatibility-definition">Who determines what will be part of the compatibility definition?</h3> + +<h3 id="who-determines-what-will-be-part-of-the-compatibility-definition">Who +determines what will be part of the compatibility definition?</h3> <p>Since Google is responsible for the overall direction of Android as a platform and product, Google maintains the Compatibility Definition Document for each release. We draft the CDD for a new Android version in consultation with various OEMs who provide input on its contents.</p> -<h3 id="how-long-will-each-android-version-be-supported-for-new-devices">How long will each Android version be supported for new devices?</h3> + +<h3 id="how-long-will-each-android-version-be-supported-for-new-devices">How +long will each Android version be supported for new devices?</h3> <p>Since Android's code is open source, we can't prevent someone from using an old version to launch a device. Instead, Google chooses not to license the Google Play client software for use on versions that are considered obsolete. This allows anyone to continue to ship old versions of Android, but those devices won't use the Android name and will exist outside the Android apps ecosystem, just as if they were non-compatible.</p> -<h3 id="can-a-device-have-a-different-user-interface-and-still-be-compatible">Can a device have a different user interface and still be compatible?</h3> + +<h3 id="can-a-device-have-a-different-user-interface-and-still-be-compatible">Can +a device have a different user interface and still be compatible?</h3> <p>The Android Compatibility Program determines whether a device can run third-party applications. The user interface components shipped with a device (such as home screen, dialer, color scheme, and so on) do not @@ -273,52 +325,72 @@ generally have much effect on third-party apps. As such, device builders are free to customize the user interface as much as they like. The Compatibility Definition Document does restrict the degree to which OEMs may alter the system user interface for areas that do impact third-party apps.</p> -<h3 id="when-are-compatibility-definitions-released-for-new-android-versions">When are compatibility definitions released for new Android versions?</h3> + +<h3 id="when-are-compatibility-definitions-released-for-new-android-versions">When +are compatibility definitions released for new Android versions?</h3> <p>Our goal is to release new versions of Android Compatibility Definition Documents (CDDs) once the corresponding Android platform version has converged enough to permit it. While we can't release a final draft of a CDD for an Android software version before the first flagship device ships with that software, final CDDs will always be released after the first device. However, wherever practical we will make draft versions of CDDs available.</p> -<h3 id="how-are-device-manufacturers-compatibility-claims-validated">How are device manufacturers' compatibility claims validated?</h3> + +<h3 id="how-are-device-manufacturers-compatibility-claims-validated">How are +device manufacturers' compatibility claims validated?</h3> <p>There is no validation process for Android device compatibility. However, if the device is to include Google Play, Google will typically validate the device for compatibility before agreeing to license the Google Play client software.</p> -<h3 id="what-happens-if-a-device-that-claims-compatibility-is-later-found-to-have-compatibility-problems">What happens if a device that claims compatibility is later found to have compatibility problems?</h3> + +<h3 id="what-happens-if-a-device-that-claims-compatibility-is-later-found-to-have-compatibility-problems">What +happens if a device that claims compatibility is later found to have +compatibility problems?</h3> <p>Typically, Google's relationships with Google Play licensees allow us to ask them to release updated system images that fix the problems.</p> + <a href="#top">Back to top</a> + <h2 id="compatibility-test-suite">Compatibility Test Suite</h2> + <h3 id="what-is-the-purpose-of-the-cts">What is the purpose of the CTS?</h3> <p>The Compatibility Test Suite is a tool used by device manufacturers to help ensure their devices are compatible, and to report test results for validations. The CTS is intended to be run frequently by OEMs throughout the engineering process to catch compatibility issues early.</p> -<h3 id="what-kinds-of-things-does-the-cts-test">What kinds of things does the CTS test?</h3> + +<h3 id="what-kinds-of-things-does-the-cts-test">What kinds of things does the +CTS test?</h3> <p>The CTS currently tests that all of the supported Android strong-typed APIs are present and behave correctly. It also tests other non-API system behaviors such as application lifecycle and performance. We plan to add support in future CTS versions to test "soft" APIs such as Intents as well.</p> -<h3 id="will-the-cts-reports-be-made-public">Will the CTS reports be made public?</h3> + +<h3 id="will-the-cts-reports-be-made-public">Will the CTS reports be made +public?</h3> <p>Yes. While not currently implemented, Google intends to provide web-based self-service tools for OEMs to publish CTS reports so that they can be viewed by anyone. CTS reports can be shared as widely as manufacturers prefer.</p> + <h3 id="how-is-the-cts-licensed">How is the CTS licensed?</h3> <p>The CTS is licensed under the same Apache Software License 2.0 that the bulk of Android uses.</p> -<h3 id="does-the-cts-accept-contributions">Does the CTS accept contributions?</h3> + +<h3 id="does-the-cts-accept-contributions">Does the CTS accept +contributions?</h3> <p>Yes please! The Android Open Source Project accepts contributions to improve the CTS in the same way as for any other component. In fact, improving the coverage and quality of the CTS test cases is one of the best ways to help out Android.</p> -<h3 id="can-anyone-use-the-cts-on-existing-devices">Can anyone use the CTS on existing devices?</h3> + +<h3 id="can-anyone-use-the-cts-on-existing-devices">Can anyone use the CTS on +existing devices?</h3> <p>The Compatibility Definition Document requires that compatible devices -implement the 'adb' debugging utility. This means that any compatible device --- including ones available at retail -- must be able to run the CTS +implement the <code>adb</code> debugging utility. This means that any compatible +device (including ones available at retail) must be able to run the CTS tests.</p> + <h3 id="are-codecs-verified">Are codecs verified by CTS?</h3> <p>Yes. All mandatory codecs are verified by CTS.</p> diff --git a/en/setup/start/licenses.html b/en/setup/start/licenses.html new file mode 100644 index 00000000..4c1a3b82 --- /dev/null +++ b/en/setup/start/licenses.html @@ -0,0 +1,126 @@ +<html devsite> + <head> + <title>Content License</title> + <meta name="project_path" value="/_project.yaml" /> + <meta name="book_path" value="/_book.yaml" /> + </head> + <body> + <!-- + Copyright 2017 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 + + http://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> + The Android Open Source Project (AOSP) uses a few + <a href="http://www.opensource.org/" class="external">open source + initiative</a> approved open source licenses for our software. +</p> +<h2 id="android-open-source-project-license">AOSP license</h2> +<p> + The preferred license for AOSP is the + <a href="http://www.apache.org/licenses/LICENSE-2.0" class="external">Apache + Software License, Version 2.0</a> ("Apache 2.0"), and the majority of the + Android software is licensed with Apache 2.0. While the project strives to + adhere to the preferred license, there may be exceptions that will be handled + on a case-by-case basis. For example, the Linux kernel patches are under the + GPLv2 license with system exceptions, which can be found on + <a href="http://www.kernel.org/pub/linux/kernel/COPYING" class="external">kernel.org</a>. +</p> +<h2 id="contributor-license-grants">Contributor License Agreements</h2> +<p>All <em>individual</em> contributors (those making contributions only on + their own behalf) of ideas, code, or documentation to AOSP will be required to + complete, sign, and submit an + <a href="https://cla.developers.google.com/about/google-individual" class="external">Individual + Contributor License Agreement</a>. The agreement can be executed online + through the + <a href="https://android-review.googlesource.com/#/settings/agreements" class="external">code + review tool</a>. The agreement clearly defines the terms under which + intellectual property has been contributed to AOSP. This license is for your + protection as a contributor as well as the protection of the project; it does + not change your rights to use your own contributions for any other purpose. +</p> +<p> + For a <em>corporation</em> (or other entity) that has assigned employees to + work on AOSP, a + <a href="https://cla.developers.google.com/about/google-corporate" class="external">Corporate + Contributor License Agreement</a> is available. This version of the agreement + allows a corporation to authorize contributions submitted by its designated + employees and to grant copyright and patent licenses. A Corporate Contributor + License Agreement does not remove the need for any developer to sign their own + Individual Contributor License Agreement as an individual. The individual + agreement is needed to cover any of their contributions that are <em>not</em> + owned by the corporation signing the Corporate Contributor License Agreement. +</p> +<p> + We based our agreements on the ones used by the + <a href="http://www.apache.org">Apache Software Foundation</a>, which can + be found on the + <a href="http://www.apache.org/licenses/" class="external">Apache website</a>. +</p> +<h2 id="why-apache-software-license">Why Apache Software License?</h2> +<p> + We are sometimes asked why Apache Software License 2.0 is the preferred + license for Android. For userspace (non-kernel) software, we prefer ASL2.0 + (and similar licenses such as BSD, MIT, etc.) over other licenses such as + LGPL. +</p> +<p> + Android is about freedom and choice. The purpose of Android is promote + openness in the mobile world, and we don't believe it's possible to predict or + dictate all the uses to which people will want to put our software. So, while + we encourage everyone to make devices that are open and modifiable, we don't + believe it is our place to force them to do so. Using LGPL libraries would + often force them to do just that. +</p> +<p> + Here are some of our specific concerns: +</p> +<ul> + <li> + LGPL (in simplified terms) requires either: shipping of source to the + application; a written offer for source; or linking the LGPL-ed library + dynamically and allowing users to manually upgrade or replace the library. + Since Android software is typically shipped in the form of a static system + image, complying with these requirements restricts OEMs' designs. For + instance, it's difficult for a user to replace a library on read-only + flash storage.) + </li> + <li> + LGPL requires allowance of customer modification and reverse + engineering for debugging those modifications. Most device makers do + not want to have to be bound by these terms. So to minimize the burden on + these companies, we minimize usage of LGPL software in userspace. + </li> + </li> + <li> + Historically, LGPL libraries have been the source of a large number + of compliance problems for downstream device makers and application + developers. Educating engineers on these issues is difficult and slow-going, + unfortunately. It's critical to Android's success that it be as easy as + possible for device makers to comply with the licenses. Given the + difficulties with complying with LGPL in the past, it is most prudent to + simply not use LGPL libraries if we can avoid it. + </li> +</ul> +<p> + The issues discussed above are our reasons for preferring ASL2.0 for + our own code. They aren't criticisms of LGPL or other licenses. We are + passionate about this topic, even to the point where we've gone out of our + way to make sure as much code as possible is ASL2.0 licensed. However, we love + all free and open source licenses, and respect others' opinions and + preferences. We've simply decided ASL2.0 is the right license for our goals. +</p> + + </body> +</html> diff --git a/en/setup/start/roles.html b/en/setup/start/roles.html new file mode 100644 index 00000000..b420be2f --- /dev/null +++ b/en/setup/start/roles.html @@ -0,0 +1,122 @@ +<html devsite> + <head> + <title>Project Roles</title> + <meta name="project_path" value="/_project.yaml" /> + <meta name="book_path" value="/_book.yaml" /> + </head> + <body> + <!-- + Copyright 2017 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 + + http://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> + The Android Open Source Project (AOSP) includes individuals working in a + variety of roles. Google is responsible for Android product management + and the engineering process for the core framework and platform; however, + the project considers contributions from any source, not just Google. This + page describes the kinds of roles that interested parties can take on. +</p> +<p> + Anyone who is interested in exploring and contributing to Android can use the + AOSP resources. Anyone can join the mailing lists, ask questions, contribute + patches, report bugs, look at submitted patches, and use the tools. To get + started with the Android code, see + <a href="../contribute/index.html">Contributing</a>. +</p> + +<h2 id="contributor">Contributor</h2> +<p> + "Contributors" are those making contributions to the AOSP source code, + including both employees of Google or other companies, as well as individual + developers who are contributing to Android on their own behalf. There is no + distinction between contributors who are employed by Google and those who are + not; all engineers use the same tools (git, repo, and gerrit), follow the same + code review process, and are subject to the same requirements on code style + and so on. +</p> + +<h2 id="developer">Developer</h2> +<p> + "Developers" are engineers writing applications that run on Android + devices. There is often little difference in skillset between a developer + and a contributor. But AOSP uses "developer" to distinguish between + engineers using the platform and those contributing to it. Developers + (along with users) are the "customers" of the platform the contributors + create. As such, we talk about developers a lot, though this isn't technically + a separate role in the AOSP per se. +</p> + +<h2 id="verifier">Verifier</h2> +<p> + "Verifiers" are responsible for testing change requests. After individuals + have submitted a significant amount of high-quality code to the project, the + project leads might invite them to become verifiers. +</p> +<aside class="note"><strong>Note:</strong> At this time, verifiers act similarly +to approvers.</aside> + +<h2 id="approver">Approver</h2> +<p> + "Approvers" are experienced members of the project who have demonstrated their + design skills and have made significant technical contributions to the + project. In the code-review process, an approver decides whether to include or + exclude a change. Project leads (who are typically employed by Google) choose + the approvers, sometimes promoting to this position verifiers who have + demonstrated their expertise within a specific project. +</p> + +<h2 id="project-leads">Project lead</h2> +<p> + Android consists of a number of sub-projects; you can see these in the git + repository as individual .git files. "Project leads" are senior contributors + who oversee the engineering for individual Android projects. Typically these + project leads are Google employees. A project lead for an individual project + is responsible for the following: +</p> +<ul> + <li> + Lead all technical aspects of the project, including the project roadmap, + development, release cycles, versioning, and quality assurance (QA). + <li> + Ensure the project is tested by QA in time for scheduled Android platform + releases. + </li> + <li> + Designate Verifiers and Approvers for submitted patches. + </li> + <li> + Be fair and unbiased while reviewing changes. Accept or reject patches + based on technical merit and alignment with the Android strategy. + </li> + <li> + Review changes in a timely manner and make best efforts to communicate + when changes are not accepted.</p> + </li> + <li> + Optionally maintain a web site for the project for information and + documents specific to the project. + </li> + <li> + Act as a facilitator in resolving technical conflicts. + </li> + <li> + Be a public face for the project and the go-to person for questions + related to the project. + </li> +</ul> + + </body> +</html> diff --git a/en/setup/start/site-updates.html b/en/setup/start/site-updates.html new file mode 100644 index 00000000..2f7df35e --- /dev/null +++ b/en/setup/start/site-updates.html @@ -0,0 +1,803 @@ +<html devsite> + <head> + <title>Site Updates</title> + <meta name="project_path" value="/_project.yaml" /> + <meta name="book_path" value="/_book.yaml" /> + </head> + <body> + <!-- + Copyright 2017 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 + + http://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> + This page describes significant revisions to source.android.com. For a + complete list of changes to this site refer to the Android Open Source Project + (AOSP) + <a href="https://android.googlesource.com/platform/docs/source.android.com/+log/master?pretty=full&no-merges" class="external">docs/source.android.com + log</a>. +</p> + +<h2 id="Dec-2017">December 2017</h2> +<p> + Android 8.1 has been released! See the entries below for the major platform + features introduced in this release. +</p> + +<h3 id="aaudio">AAudio and MMAP</h3> +<p> + AAudio is an audio API that has enhancements to reduce latency when used in + conjunction with a HAL and driver that support MMAP. See + <a href="/devices/audio/aaudio">AAudio and MMAP</a> for documentation + describing the hardware abstraction layer (HAL) and driver changes needed to + support AAudio's MMAP feature in Android. +</p> + +<h3 id="art-config">ART configuration changes</h3> +<p> + The <code>WITH_DEXPREOPT_BOOT_IMG_ONLY</code> makefile option was removed + from the Android runtime (ART) in Android 8.1 and replaced with the + <code>WITH_DEXPREOPT_BOOT_IMG_AND_SYSTEM_SERVER_ONLY</code> option that + pre-optimizes the system server jars, as well as the boot classpath. See + <a href="/devices/tech/dalvik/configure#build_options">Configuring ART</a> for + the deprecation notice. +</p> + +<h3 id="biometric-unlock">Biometric unlock security measurements</h3> +<p> + Android 8.1 introduces two new metrics associated with biometric unlocks + that are intended to help device manufacturers evaluate their security more + accurately: Imposter Accept Rate (IAR) and Spoof Accept Rate (SAR). See <a + href="/security/biometric/">Measuring Biometric Unlock Security</a> for + example attacks and test methodology. +</p> + +<h3 id="boot-times">Boot time optimizations</h3> +<p> + Starting in Android 8.1, power saving setting for components like UFS and + CPU governor can be disabled to improve device boot times. See <a + href="/devices/tech/perf/boot-times#disable-power-saving">Optimizing Boot + Times</a> for the new <code>init.*.rc</code> settings. +</p> + +<h3 id=“color-mgmtâ€>Color management</h3> +<p> + Android 8.1 adds support for color management that can be used to provide a + consistent experience across display technologies. Applications running on + Android 8.1 can access the full capabilities of a wide gamut display to get + the most out of a display device. See + <a href="/devices/tech/display/color-mgmt">Color Management</a> for + instructions on implementing, customizing, and testing this feature. +</p> + +<h3 id="opengl-config">OpenGLRenderer configuration simplification</h3> +<p> + In Android 8.1 and later, only the <code>ro.zygote.disable_gl_preload + property</code> still applies to OpenGLRenderer configuration. All other + properties have been removed. See <a + href="/devices/graphics/renderer">OpenGLRenderer Configuration</a> for the + notice and previously supported properties. +</p> + +<h3 id="retail-mode">Retail demo mode made easy</h3> +<p> + Through Device Policy Manager, Android 8.1 supports demonstrating device + functionality in retail stores via a demo-type user role. See <a + href="/devices/tech/display/retail-mode.html">Retail Demo Mode</a> for + implementation instructions. +</p> + +<h3 id="textclassifier">TEXTCLASSIFIER</h3> +<p> + Android 8.1 introduces the TextClassfier API that uses machine learning + techniques to help developers classify text. + See <a href="/devices/tech/display/textclassifier.html">TEXTCLASSIFIER</a> for + implementation instructions. +</p> + +<h3 id="timezone-rules">Time zone rules</h3> +<p> + Android 8.1 provides a new mechanism for device manufacturers (OEMs) to push + updated time zone rules data to devices without requiring a system update. + This mechanism enables users to receive timely updates and OEMs to test time + zone updates independently of system image updates. See + <a href="/devices/tech/config/timezone-rules">Time Zone Rules</a> for + instructions on applying these updates. +</p> + +<h3 id="wifi-aware">Wi-Fi Aware</h3> +<p> + The Wi-Fi Aware feature in Android 8.1 enables supporting devices to connect + to one another directly over Wi-Fi without internet or cellular network access. + This feature allows easy sharing of high-throughput data among trusted devices + and apps that are otherwise off network. See <a + href="/devices/tech/connect/wifi-aware">Wi-Fi Aware</a> for examples, source + files, and links to additional documentation. +</p> + +<h2 id="Nov-2017">November 2017</h2> +<p> + The <em>Source</em> section has been renamed to + <a href="/setup"><em>Setup</em></a>. Redirects are in place to ensure the old + URLs still work. +</p> + +<h2 id="Sept-2017">September 2017</h2> +<p> + This site has been released in China at + <a href="https://source.android.google.cn" class="external-link">source.android.google.cn</a>. + All non-reference materials have also been translated into Simplified Chinese + for ease of use. +</p> + +<h2 id="August-2017">August 2017</h2> +<p> + Android 8.0 has been released! This section describes the major new features + in the Android 8.0 platform. +</p> +<h3 id="architecture">Architecture</h3> +<h4>Treble</h4> +<p> + Android 8.0 includes support for Treble, a major re-architect of the + Android OS framework designed to make it easier, faster, and less costly + for manufacturers to update devices to a new version of Android. Documentation + includes details on the <a href="/devices/architecture/hidl/index.html">HAL + interface definition language (HIDL)</a>, a new + <a href="/devices/architecture/configstore/index.html">ConfigStore HAL</a>, + <a href="/devices/architecture/dto/index.html">Device Tree Overlays</a>, the + <a href="/devices/architecture/vndk/index.html">Vendor Native Development Kit + (VNDK)</a>, <a href="/devices/architecture/vintf/index.html">Vendor Interface + Objects (VINTF)</a>, + <a href="/devices/architecture/kernel/modular-kernels.html">Modular Kernel + requirements</a>, and the <a href="/devices/tech/vts/index.html">Vendor Test + Suite (VTS) and Infrastructure</a>. +</p> + +<h4>FunctionFS support</h4> +<p> + <a class="external-link" href="https://www.kernel.org/doc/Documentation/usb/functionfs.txt">FunctionFS</a> + (FFS) is a USB gadget function that is designed and controlled through user + space. Its support allows all of the function- and protocol-specific code to + live in user space, while all of the USB transport code lives in the kernel. + Using FFS moves Media Transfer Protocol (MTP) implementation into user space. +</p> +<p> + On the frameworks side, most of the major changes exist in MtpServer. The + USB driver interface has been refactored into two different classes, one that + uses the old kernel driver and one that uses FFS. MtpServer is then able + to use that driver interface without needing to know the details of + implementation. The FFS driver writes the USB descriptors to a file when + the server starts up; it then writes data to endpoint files similar to the + kernel driver use. +</p> + +<h4>Kernel enhancements to LLDB/C++ debugging</h4> +<p> + The Android 8.0 release includes kernel enhancements that help developers + create better applications by improving their debugging experience. For more + information, see + <a href="/devices/architecture/kernel/lldb-debug.html">Implementing kernel + enhancements to LLDB/C++ debugging</a>. +</p> + +<h4>Kernel hardening</h4> +<p> + Upstreamed kernel hardening features and tools to find bugs in kernel drivers. + For more information, see + <a href="/devices/architecture/kernel/hardening.html">Kernel Hardening</a>. +</p> + +<h4>Optimizing SquashFS at the kernel level</h4> +<p> + SquashFS is a compressed read-only filesystem for Linux, suitable for use on + the system partition. The optimizations in this document help improve the + performance of SquashFS. For more information, see + <a href="/devices/architecture/kernel/squashfs.html">Optimizing SquashFS at + the Kernel Level</a>. +</p> + +<h3 id="art-dalvik">ART and Dalvik</h3> + +<h4>Fuzz testing</h4> +<p> + AOSP offers a new fuzzing testing suite for testing the + <a href="/devices/tech/dalvik/">Android runtime (ART)</a> infrastructure. The + new toolset, JFuzz and an improved DexFuzz, are directly available in AOSP now + with accompanying documentation. See: + <a href="https://android.googlesource.com/platform/art/+/master/tools/jfuzz/README.md">https://android.googlesource.com/platform/art/+/master/tools/jfuzz/README.md</a> + <a href="https://android.googlesource.com/platform/art/+/master/tools/dexfuzz/README">https://android.googlesource.com/platform/art/+/master/tools/dexfuzz/README</a> +</p> +<p> + Nothing is required to implement or use the new tools. You may make changes + to the tools if required, just like you can make changes to the + runtime/compiler already. +</p> + +<h4>VDEX files: Improve system update performance</h4> +<p> + VDEX files improve the performance and user experience of software updates. + VDEX files store pre-validated DEX files with verifier dependencies so that + during system updates ART does not need to extract and verify the DEX files + again. No action is needed to implement this feature. It is enabled by + default. To disable the feature, set the <code>ART_ENABLE_VDEX</code> + environment variable to <code>false</code>. +</p> + +<h4>ART performance improvements</h4> +<p> + The Android runtime (ART) has been improved significantly in the Android 8.0 + release. This document summarizes enhancements device manufacturers can expect + in ART. For more information, see + <a href="/devices/tech/dalvik/improvements.html">Improving ART Performance in + Android 8.0</a>. +</p> + +<h4>Android A/B OTA updates</h4> +<p> + This update answers common questions device manufacturers have regarding + Android A/B (seamless) system updates. For more information, see A/B updates + <a href="/devices/tech/ota/ab/ab_faqs.html">frequently asked questions</a>. +</p> + +<h3 id="automotive">Automotive</h3> + +<h4>Bluetooth connection management</h4> +<p> + Android 8.0 provides Bluetooth connection management in in-vehicle + infotainment systems for a more seamless Bluetooth user experience. For more + information, see + <a href="/devices/automotive/ivi_connectivity.html#bluetooth-connection-management">Bluetooth + connection management</a>. +</p> + +<h4>Bluetooth multi-device HFP</h4> +<p> + Bluetooth multi-device connectivity lets users connect multiple devices to + telephony profiles in an Android Automotive IVI Bluetooth. For more + information, see + <a href="/devices/automotive/ivi_connectivity.html#bluetooth-multi-device-connectivity">IVI + Connectivity</a>. +</p> + +<h4>Vehicle Camera HAL</h4> +<p> + Describes the design of an exterior view system (EVS) stack and provides the + HAL specification for supporting the acquisition and presentation of vehicle + camera data. For more information, see + <a href="/devices/automotive/camera-hal.html">Exterior View System (EVS) + Vehicle Camera HAL.</a> +</p> + +<h3 id="bluetooth">Bluetooth</h3> +<p> + See the updated <a href="/devices/bluetooth/index.html">Bluetooth overview</a>. +</p> + +<h4>Verifying and debugging Bluetooth</h4> +<p> + For details on how to verify and debug the native Bluetooth stack, see + <a href="/devices/bluetooth/verifying_debugging.html">Verifying and + Debugging</a>. +</p> + +<h4>Bluetooth services</h4> +<p> + Bluetooth provides a variety of features that enable core services between + devices, such as audio streaming, phone calls, and messaging. For more + information about the Android Bluetooth services, see + <a href="/devices/bluetooth/services.html">Bluetooth Services</a>. +</p> + +<h4>BLE advertising</h4> +<p> + Bluetooth 5 supports different modes of data advertisements for Bluetooth Low + Energy, including higher bandwidth or increased range. For more information, + see <a href="/devices/bluetooth/ble_advertising.html">Bluetooth Low Energy + Advertising</a>. +</p> + +<h4>Bluetooth support for audio codecs</h4> +<p> + The Android 8.0 release includes support for Bluetooth high-definition audio + codecs. For more information, see <a + href="/devices/bluetooth/services.html#advanced-audio-codecs">Advanced audio codecs</a>. +</p> +<h3 id="camera">Camera</h3> +<h4>Critical camera features</h4> +<p> + The Android 8.0 release contains these key enhancements to the Camera service: + shared surfaces, enable multiple surfaces sharing the same OutputConfiguration + System API for custom camera modes, and onCaptureQueueEmpty. For more + information, see <a href="/devices/camera/versioning.html">Camera Version + Support</a>. +</p> + +<h3 id="configuration">Configuration</h3> + +<h4>Ambient capabilities</h4> +<p> + Capabilities allow Linux processes to drop most root-like privileges, while + retaining the subset of privileges they require to perform their function. + Ambient capabilities allows system services to configure capabilities in their + <code>.rc</code> files, bringing all their configuration into a single file. + For more information, see + <a href="/devices/tech/config/ambient.html">Implementing Ambient + Capabilities</a>. +</p> + +<h4>Privileged permission whitelist requirement</h4> +<p> + Starting in Android 8.0, all privileged apps must be explicitly whitelisted in + system configuration XML files in the <code>/etc/permissions</code> directory. + If they are not, then the device will boot, but the device implementation will + not pass CTS. For more information, see + <a href="/devices/tech/config/perms-whitelist.html">Privileged Permission + Whitelist Requirement</a>. +</p> + +<h4>Implementing USB HAL</h4> +<p> + The Android 8.0 release moves handling of USB commands out of init scripts and + into a native USB daemon for better configuration and code reliability. For + more information, see <a href="/devices/tech/config/usb-hal.html">Implementing + USB HAL</a>. +</p> + +<h3 id="connectivity">Connectivity</h3> + +<h4>Customizing device behavior for out-of-balance users</h4> +<p> + Android devices with no data balance allow network traffic through, requiring + carriers and telecoms to implement mitigation protocols. This feature + implements a generic solution that allows carriers and telcos to indicate when + a device has run out of balance. For more information, see + <a href="/devices/tech/connect/oob-users.html">Customizing device behavior for + out-of-balance users</a>. +</p> + +<h3 id="debugging">Debugging</h3> + +<h4>Enabling sanitizers in the Android build system</h4> +<p> + Sanitizers are compiler-based instrumentation components to use during + development and testing in order to identify bugs and make Android better. + Android's current set of sanitizers can discover and diagnose memory misuse + bugs and potentially dangerous undefined behavior. For more information, see + <a href="/devices/tech/debug/sanitizers.html">Enabling Sanitizers in the + Android Build System</a>. +</p> + +<h4>Recover devices in reboot loops</h4> +<p> + Android 8.0 includes a feature that sends out a "rescue party" when it notices + core system components stuck in crash loops. Rescue Party then escalates + through a series of actions to recover the device. For more information, see + <a href="/devices/tech/debug/rescue-party.html">Rescue Party</a>. +</p> + +<h4>Storaged</h4> +<p> + Android 8.0 adds support for <code>storaged</code>, an Android native daemon + that collects and publishes storage metrics on Android devices. For more + information, see <a href="/devices/tech/debug/storaged.html">Implementing + Storaged</a>. +</p> + +<h3 id="display">Display</h3> + +<h4>Air Traffic Control for floating windows</h4> +<p> + Android 8.0 introduces Air Traffic Control for floating windows in order to + simplify and unify how apps display on top of other apps. Everything necessary + to use the feature is included in the AOSP. +</p> +<p> + Air Traffic Control allows developers to create a new (managed) floating + layer/window type for apps to use to display windows on-top of other apps. The + feature displays ongoing notifications for all apps using a floating layer + that lets the user manage the alert window. +</p> +<p> + The Android Compatibility Test Suite (CTS) confirms: +</p> +<ul> + <li>The current alert window types are: <code>TYPE_PHONE</code>, + <code>TYPE_PRIORITY_PHONE</code>, <code>TYPE_SYSTEM_ALERT</code>, + <code>TYPE_SYSTEM_OVERLAY</code>, or <code>TYPE_SYSTEM_ERROR</code>. + </li> + <li>Apps targeting the Android 8.0 SDK won't be able to use the window types + above to display windows above other apps. They will need to use a new + window type <code>TYPE_APPLICATION_OVERLAY</code>. + </li> + <li>Apps targeting older SDKs can still use the current window types; however, + the windows will be z-ordered below the new + <code>TYPE_APPLICATION_OVERLAY</code> windows. + </li> + <li>The system can move or resize windows in the new layer to reduce clutter. + </li> + <li>Device manufacturers must keep the notification that lets users control + what is displayed over other apps. + </li> +</ul> + +<h4>Launching activities on secondary displays</h4> +<p> + Virtual displays are available to everyone, and they don't require any special + hardware. Any application can create an instance of virtual display; in the + Android 8.0 release, activities can be launched on that virtual display if the + associated feature is enabled. +</p> +<p> + To support multi-display features, you should either use one of the + existing supported ways of connecting secondary devices or build new hardware. + The supported ways of connecting displays on Nexus and Pixel devices are + Google Cast and + <a href="https://developer.android.com/reference/android/hardware/display/VirtualDisplay.html" class="external">virtual + displays inside apps</a>. Support of other ways depends on kernel driver + support for each particular case (like MHL or DisplayPort over USB-C) and + fully implementing interface definitions that are related to displays in + HardwareComposer HAL (<code>IComposerCallback.hal</code> and + <code>IComposerClient.hal</code>). +</p> +<p> + Each of the ways may require SoC or OEM support. For example, to enable + DisplayPort over USB-C, both hardware (SOC) and software (drivers) support is + required. You might need to implement drivers for your hardware to support + connecting external displays. +</p> +<p> + The default implementation will allow launching fullscreen stacks of activities + on secondary displays. You can customize the stacks and System UI and + behavior on secondary displays. +</p> +<h4>Support for generic tooltip</h4> +<p> + Android 8.0 allows developers to provide descriptive action names and other + helpful information on mouse hover over buttons and other icons. Device + manufacturers may style the tooltip popup. Its layout is defined in + <code>android/frameworks/base/core/res/res/layout/tooltip.xml</code>. + </a> +</p> +<p> + OEMs may replace the layout or change its dimensions and style parameters. Use + only text and keep the size reasonably small. The feature is implemented + entirely inside the View class, and there are quite exhaustive CTS tests that + check many aspects of Tooltip behavior. +</p> +<p> + +<h4>Support for extended aspect ratio</h4> +<p> + Android 8.0 includes a new manifest attribute, + <a href="https://developer.android.com/reference/android/R.attr.html#maxAspectRatio" class="external">maxAspectRatio</a>, + which lets an activity or app specify the maximum aspect ratio it supports. + maxAspectRatio replaces the previous meta-data tag with a first-class API and + allows devices to support an aspect ratio greater than 16:9. +</p> +<ul> + <li>If an activity or app is + <a href="https://developer.android.com/guide/topics/ui/multi-window.html#configuring" class="external">resizable</a>, + allow the activity to fill the screen. + <li> + If an activity or app is non-resizeable or the platform is force resizing + the activity, allow the app window to display up to the maximum aspect ratio, + according to the + <a href="https://developer.android.com/reference/android/R.attr.html#maxAspectRatio" class="external">maxAspectRatio</a> + value. + <ul> + <li>For applications on devices running Android 8.0, the default value is + the aspect ratio of the current device.</li> + <li>For applications on devices running earlier versions of Android, the + default value is 16:9.</li> + </ul> + </li> +</ul> + +<h4>Implementing Adaptive Icons</h4> +<p> + Adaptive Icons maintain a consistent shape intra-device but vary from device + to device with only one icon asset provided by the developer. Additionally, + icons support two layers (foreground and background) that can be used for + motion to provide visual delight to users. For more information, see + <a href="/devices/tech/display/adaptive-icons.html">Implementing Adaptive + Icons</a>. +</p> + +<h4>Night Light</h4> +<p> + Night Light, introduced in Android 7.0.1, allows users to reduce the amount of + blue light that their screen emits. Android 8.0 gives users more control over + the intensity of this effect. For more information, see + <a href="/devices/tech/display/night-light.html">Implementing Night Light</a>. +</p> + +<h4>Picture-in-picture</h4> +<p> + Android 8.0 includes support for picture-in-picture (PIP) on Android handheld + devices. PIP allows users to resize an app with an ongoing activity, such as a + video, into a small window. For more information, see + <a href="/devices/tech/display/pip.html">Picture-in-Picture on Android + handsets</a>. +</p> + +<h4>Better split-screen interactions</h4> +<p> + Multi-window lets multiple apps simultaneously display on users' device + screens. Android 8.0 improves the default mode, split-screen, by compressing + the top pan and resizing the launcher if a user taps Home after entering + split-screen. For more information, see + <a href="/devices/tech/display/split-screen.html">Better Split-Screen + Interactions</a>. +</p> + +<h4>Add Widgets/Shortcuts</h4> +<p> + A new API in Android 8.0 allows application developers to add shortcuts and + widgets from inside the app instead of relying on the widget tray. The older + method of adding shortcuts by sending a broadcast has been deprecated for + security reasons. For more information, see + <a href="/devices/tech/display/widgets-shortcuts.html">Implementing Add + Widgets/Shortcuts</a>. +</p> + +<h3 id="downloading-building">Downloading and building</h3> + +<h4>Android LLVM Toolchain improvements</h4> +<p> + OEMs who wish to use our latest toolchain/tools must ensure that their private + code compiles successfully with the updated toolchains. This may + require them to fix existing issues in their code with undefined behavior. (Of + course, they are free to use whatever tools they prefer to compile their own + code too.) +</p> +<p> + They must ensure their code is free of undefined behavior (by using tools like + UBSan), so they are less susceptible to problems caused by newer toolchains. + All of the toolchains are always updated directly in AOSP. Everything will be + available well before OC even ships, so OEMs should be following along + already. +</p> +<p> + See the <a href="https://llvm.org/" class="external">public Clang/LLVM</a> + documentation for general instructions and the + <a href="https://android.googlesource.com/platform/external/clang/+/dev/ReadmeAndroid.md" class="external">Android + Clang/LLVM</a> documentation set within AOSP for Android-specific guidance. + Finally, join the + <a href="https://groups.google.com/forum/#!forum/android-llvm">android-llvm</a> + public group to get help and take part in development. +</p> + +<h3 id="drm-kms">DRM/KMS</h3> + +<h4>DRM/KMS in Linux Kernel Version 4.9</h4> +<p> + The Direct Rendering Manager (DRM)/Kernel Mode Setting (KMS) framework used by + Android is developed and maintained by Linux kernel developers in the Linux + kernel. Android merges down from the Linux kernel. By merging down from our + common kernel, device manufacturers gain the DRM/KMS framework automatically. +</p> +<p> + DRM/KMS became viable in Linux kernel version 4.9, and Android + <strong>strongly encourages</strong> OEM partners to use DRM/KMS starting with + this kernel version. + <a href="https://lwn.net/Articles/565422/" class="external">Atomic Display + Framework (ADF)</a>, the display framework officially supported by Android + today, will not be supported in 4.9 and higher versions of the common Android + kernel; instead, Android will support DRM/KMS from this version. OEMs can + continue to use ADF (or any other framework), but Android will not support + them in the common Android kernel. +</p> +<p> + To implement DRM/KMS, you will need to write your own drivers using + DRM/KMS in addition to merging down the DRM/KMS framework from the android + common kernel. +</p> + +<h3 id="keystore">Keystore</h3> + +<h4>Keymaster 3</h4> +<p> + Android 8.0 updates Keymaster, the keystore HAL, by extending the capabilities + of hardware-backed key storage on Android devices. This builds upon the + Android 7.1.2 updates to Keymaster 2. For more information, see + <a href="/security/keystore/index.html">Keymaster 3 documentation</a>. +</p> + +<h3 id="security-enhancements">Security enhancements</h3> + +<h4>Insecure TLS version fallback removed from HttpsURLConnection</h4> +<p> + Insecure TLS/SSL protocol version fallback is a workaround for buggy + implementations of TLS protocol downgrade negotiation in some servers. This is + vulnerable to POODLE. When Chrome 45 dropped the insecure fallback in + September 2015, less than 0.01% of servers relied on it. To improve security, + insecure TLS version fallback has been removed from + <a href="https://developer.android.com/reference/javax/net/ssl/HttpsURLConnection.html" class="external">HttpsURLConnection</a> + in Android 8.0. For more details, see + <a href="https://android-developers.googleblog.com/2017/04/android-o-to-drop-insecure-tls-version.html + " class="external">this blog post</a>. +</p> +<p> + To test this feature on devices with Android 8.0, run this CTS test case: +</p> +<pre class="devsite-click-to-copy devsite-terminal" data-terminal-prefix="# "> +cts-tradefed run cts -m CtsLibcoreOkHttpTestCases</pre> + +<h3 id="performance">Performance</h3> + +<h4>Flash wear management</h4> +<p> + Describes eMMC behavior and new features to help OEMs lower the risk of a + failing eMMC in the automotive environment. For more information, see + <a href="/devices/tech/perf/flash-wear.html">Flash Wear Management in Android + Automotive</a>. +</p> + +<h4>Optimizing boot times</h4> +<p> + Guidance for improving boot times for specific Android devices. For more + information, see <a href="/devices/tech/perf/boot-times.html">Optimizing + boot times</a>. +</p> + +<h4>Task Snapshots</h4> +<p> + Task Snapshots is infrastructure introduced in Android 8.0 that combines + screenshots for Recents Thumbnails as well as Saved Surfaces from Window + Manager to save memory. For more information, see + <a href="/devices/tech/perf/task-snapshots.html">Task Snapshots</a>. +</p> + +<h3 id="peripherals">Peripherals</h3> + +<h4>Default print services</h4> +<p> + A + <a href="https://developer.android.com/reference/android/printservice/PrintService.html" class="external">print + service</a> is an app that discovers and presents printers to a device's print + framework. In earlier Android versions, users had to search for and install + third-party print services to be able to print. +</p> +<p> + Android 8.0 includes a default print service in + <code><a href="https://android.googlesource.com/platform/packages/services/BuiltInPrintService/" class="external">platform/packages/services/BuiltInPrintService/</a></code> + that lets users print on modern printers without installing additional apps. + This implementation supports printers that use the Internet Printing Protocol + (IPP) to communicate with the printer and use PCLm, PWG-Raster, or PDF to send + printable content. For older printers, users should install the app + recommended by the + <a href="https://android.googlesource.com/platform/frameworks/base/+/android-7.0.0_r1/packages/PrintRecommendationService/" class="external">PrintRecommendationService</a> + as seen in + <a href="https://youtu.be/M_JGeGLpOKs?t=16m20s" class="external">this I/O + presentation</a>. + +<h3 id="reference">Reference updates</h3> +<p> + The <a href="/reference/">Reference</a> section has been added to the + top-level navigation. As part of the + <a href="/devices/architecture/treble">Treble</a> release, a + <a href="/reference/hidl/">HIDL reference</a> section was added. The + <a href="/reference/tradefed/">Trade Federation</a> and the + <a href="/reference/hal/">legacy HAL</a> reference documentation has been + updated. +</p> + +<h3 id="settings-menu">Settings menu</h3> + +<h4>Settings: Patterns and components</h4> +<p> + In Android 8.0, the Settings menu gains several components and widgets that + cover common uses. For more information, see + <a href="/devices/tech/settings/patterns-components.html">Patterns and + Components</a>. +</p> + +<h4>Settings: Updated information architecture</h4> +<p> + Android 8.0 introduces a new information architecture for the Settings app. + The goal of the new information architecture is to simplify the way settings + are organized and make it easier for users to quickly find the settings needed + to customize their Android devices. For more information, see Implementing + <a href="/devices/tech/settings/info-architecture.html">Updated Information + Architecture</a>. +</p> + +<h4>Personalized Settings</h4> +<p> + The Android Settings app provides a list of suggestions to the users. This + feature provides ranking for suggestions, based on any contextual signal or + the user's past interactions with suggestions. For more information, see + <a href="/devices/tech/settings/personalized.html">Personalized Settings</a>. +</p> + +<h4>Implementing Settings: Universal search</h4> +<p> + Android 8.0 adds expanded search capabilities for the Settings menu. This + document describes how to add a setting and ensure it is properly indexed for + Settings. For more information, see + <a href="/devices/tech/settings/universal-search.html">Universal Search</a>. +</p> + +<h3 id="storage">Storage</h3> + +<h4>Faster storage statistics</h4> +<p> + Android 8.0 leverages the ext4 filesystem's quota support to return disk usage + statistics almost instantly. For more information, see + <a href="/devices/storage/faster-stats.html">Implementing faster storage + statistics</a>. +</p> + +<h2 id="april-2017">April 2017</h2> +<p> + Welcome to a new source.android.com! The site has been overhauled to make it + easier for you to navigate, search, and read its ever-growing set of + information. Here is a summary of enhancements: +</p> + +<h3 id="screen-estate">More screen real estate, larger type size</h3> +<p> + The entire site is wider, allowing you to view more content at once. Code + samples and commands are more visible, and all text has been enlarged. +</p> + +<h3 id="mobile-ready">Mobile-ready view</h3> +<p>The new site renders more cleanly on handheld devices with a dedicated + mobile view. +</p> + +<img src="../images/mobile-view.png" alt="new mobile view" height="533px" /> +<figcaption><strong>Figure 1.</strong> Site's new mobile view</figcaption> + +<h3 id="top-tabs">New top-level tabs</h3> +<p> + The former <em>Devices</em> tab has been renamed + <a href="/devices/">Porting</a>, while the old <em>Core Technologies</em> + subtab has been renamed <a href="/devices/tech/">Tuning</a> and moved to the + top of the site for better exposure. +</p> + +<h3 id="security-forefront">Security at the forefront</h3> +<p> + With an ever-increasing focus on security in Android, the + <a href="/security/">Security</a> tab has been moved forward (next to + <a href="/setup/">Source</a>) to reflect its importance. +</p> + +<h3 id="reference-materials">Better reference materials</h3> +<p> + <a href="/reference/hal/">Hardware Abstraction Layer</a> and + <a href="/reference/tradefed/packages">Trade Federation</a> reference + materials are available directly from a top-level + <a href="/reference/">Reference</a> tab. +</p> + +<h3 id="code-links">Persistent code links</h3> +<p> + The <a href="https://android.googlesource.com/" class="external">AOSP code + repository</a> is just a click away with the <strong>Go to Code</strong> + button at the top right of every page. +</p> + +<h3 id="comprehensive-footers">Comprehensive footers</h3> +<p> + In addition to the existing <em>About</em>, <em>Community</em>, and + <em>Legal</em> footers, you can now find a complete list of links at the + bottom of every page for building Android, connecting with the ecosystem, and + getting help with the operating system's use. +</p> + + </body> +</html> diff --git a/ja/security/bulletin/2015-09-01.html b/ja/security/bulletin/2015-09-01.html index 9668cc8c..17c33cbf 100644 --- a/ja/security/bulletin/2015-09-01.html +++ b/ja/security/bulletin/2015-09-01.html @@ -37,7 +37,7 @@ <p>ã“ã“ã§ã¯ã€<a href="/security/enhancements">Android ã‚»ã‚ュリティ プラットフォーム</a>ã®ä¿è·ã¨ SafetyNet ã®ã‚ˆã†ãªã‚µãƒ¼ãƒ“スã®ä¿è·ã«ã‚ˆã‚‹ãƒªã‚¹ã‚¯ã®è»½æ¸›ã«ã¤ã„ã¦æ¦‚説ã—ã¾ã™ã€‚ã“ã†ã—ãŸæ©Ÿèƒ½ã¯ã€Android ã§ã‚»ã‚ュリティã®è„†å¼±æ€§ãŒæ‚ªç”¨ã•ã‚Œã‚‹å¯èƒ½æ€§ã‚’減らã—ã¾ã™ã€‚</p> <ul> - <li> Android プラットフォームã®æœ€æ–°ç‰ˆã§ã®æ©Ÿèƒ½å¼·åŒ–ã«ã‚ˆã‚Šã€Android 上ã®å¤šãã®å•é¡Œã®æ‚ªç”¨ãŒå›°é›£ã«ãªã‚Šã¾ã™ã€‚Google ã§ã¯ã€ã™ã¹ã¦ã®ãƒ¦ãƒ¼ã‚¶ãƒ¼ã«å¯¾ã—ã€ã§ãã‚‹é™ã‚Šæœ€æ–°ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã® Android ã«æ›´æ–°ã™ã‚‹ã“ã¨ã‚’ãŠã™ã™ã‚ã—ã¦ã„ã¾ã™ã€‚ + <li>Android プラットフォームã®æœ€æ–°ç‰ˆã§ã®æ©Ÿèƒ½å¼·åŒ–ã«ã‚ˆã‚Šã€Android 上ã®å¤šãã®å•é¡Œã®æ‚ªç”¨ãŒå›°é›£ã«ãªã‚Šã¾ã™ã€‚Google ã§ã¯ã€ã™ã¹ã¦ã®ãƒ¦ãƒ¼ã‚¶ãƒ¼ã«å¯¾ã—ã€ã§ãã‚‹é™ã‚Šæœ€æ–°ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã® Android ã«æ›´æ–°ã™ã‚‹ã“ã¨ã‚’ãŠã™ã™ã‚ã—ã¦ã„ã¾ã™ã€‚ </li><li> Android ã‚»ã‚ュリティ ãƒãƒ¼ãƒ ã¯ã€ã€Œã‚¢ãƒ—リã®ç¢ºèªã€ã‚„ SafetyNet ã«ã‚ˆã£ã¦è„†å¼±æ€§ã®æ‚ªç”¨ã‚’ç©æ¥µçš„ã«ç›£è¦–ã—ã¦ã„ã¾ã™ã€‚ã“ã†ã—ãŸæ©Ÿèƒ½ã¯ã€æœ‰å®³ãªãŠãã‚Œã®ã‚るアプリãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã‚‹å‰ã«è¦å‘Šã—ã¾ã™ã€‚端末ã®ãƒ«ãƒ¼ãƒˆæ¨©é™ã‚’å–å¾—ã™ã‚‹ãƒ„ールã¯ã€Google Play ã§ç¦æ¢ã•ã‚Œã¦ã„ã¾ã™ã€‚Google Play 以外ã‹ã‚‰ã‚¢ãƒ—リをインストールã™ã‚‹ãƒ¦ãƒ¼ã‚¶ãƒ¼ã‚’ä¿è·ã™ã‚‹ãŸã‚ã€ã€Œã‚¢ãƒ—リã®ç¢ºèªã€ã¯ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã§æœ‰åŠ¹ã«ãªã£ã¦ãŠã‚Šã€ãƒ«ãƒ¼ãƒˆæ¨©é™ã‚’å–å¾—ã™ã‚‹æ—¢çŸ¥ã®ã‚¢ãƒ—リã«ã¤ã„ã¦ãƒ¦ãƒ¼ã‚¶ãƒ¼ã«è¦å‘Šã—ã¾ã™ã€‚「アプリã®ç¢ºèªã€ã§ã¯ã€æ‚ªæ„ã®ã‚る既知ã®ã‚¢ãƒ—リã§æ¨©é™æ˜‡æ ¼ã®è„†å¼±æ€§ãŒæ‚ªç”¨ã•ã‚Œãªã„よã†ã«ã€ãã®ã‚ˆã†ãªã‚¢ãƒ—リã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã‚’見ã¤ã‘ã¦é˜»æ¢ã—ã¾ã™ã€‚ã“ã†ã—ãŸã‚¢ãƒ—リãŒã™ã§ã«ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ã‚‹å ´åˆã¯ã€ãƒ¦ãƒ¼ã‚¶ãƒ¼ã«é€šçŸ¥ã—ã¦ã€ãã®ã‚¢ãƒ—リã®å‰Šé™¤ã‚’試ã¿ã¾ã™ã€‚ </li><li> Google ãƒãƒ³ã‚°ã‚¢ã‚¦ãƒˆã‚„メッセンジャーã®ã‚¢ãƒ—リã§ã¯çŠ¶æ³ã‚’判æ–ã—ã€ãƒ¡ãƒ‡ã‚£ã‚¢ã‚µãƒ¼ãƒãƒ¼ãªã©ã®ãƒ—ãƒã‚»ã‚¹ã«è‡ªå‹•çš„ã«ãƒ¡ãƒ‡ã‚£ã‚¢ã‚’渡ã™ã“ã¨ã¯ã‚ã‚Šã¾ã›ã‚“。 </li></ul> diff --git a/ja/security/bulletin/2016-01-01.html b/ja/security/bulletin/2016-01-01.html index ab694d0b..494eb437 100644 --- a/ja/security/bulletin/2016-01-01.html +++ b/ja/security/bulletin/2016-01-01.html @@ -334,5 +334,4 @@ <ul> <li> 2016 å¹´ 1 月 4 æ—¥: æƒ…å ±å…¬é–‹ </li><li>2016 å¹´ 1 月 6 æ—¥: å…¬é–‹æƒ…å ±ã‚’æ”¹è¨‚ã— AOSP ãƒªãƒ³ã‚¯ã‚’è¿½åŠ - </li><li>2016 å¹´ 4 月 28 æ—¥: è¬è¾žã‹ã‚‰ CVE-2015-6617 を削除ã€æ¦‚è¦è¡¨ã« CVE-2015-6647 ã‚’è¿½åŠ -</li></ul></body></html>
\ No newline at end of file + </li><li>2016 å¹´ 4 月 28 æ—¥: è¬è¾žã‹ã‚‰ CVE-2015-6617 を削除ã€æ¦‚è¦è¡¨ã« CVE-2015-6647 ã‚’è¿½åŠ </li></ul></body></html>
\ No newline at end of file diff --git a/ja/security/bulletin/2016-02-01.html b/ja/security/bulletin/2016-02-01.html index 559343e7..cb92f71c 100644 --- a/ja/security/bulletin/2016-02-01.html +++ b/ja/security/bulletin/2016-02-01.html @@ -273,7 +273,7 @@ LMY49G 以é™ã®ãƒ“ルドã€ãŠã‚ˆã³ Android Marshmallow（セã‚ュリティ ã <p>libmediaplayerservice ã«æƒ…å ±é–‹ç¤ºã®è„†å¼±æ€§ãŒã‚ã‚Šã€æ”»æ’ƒè€…ã«ã‚ˆã‚‹ プラットフォームã®æ‚ªç”¨ã‚’阻むãŸã‚ã®ã‚»ã‚ュリティ対ç–ãŒå›žé¿ã•ã‚Œã‚‹ -ãŠãã‚ŒãŒã‚ã‚Šã¾ã™ã€‚サードパーティ製アプリã«ã‚ˆã‚‹ã‚¢ã‚¯ã‚»ã‚¹ãŒä¸å¯èƒ½ã¨ãªã£ã¦ã„ã‚‹ <a href="http://developer.android.com/guide/topics/manifest/permission-element.html#plevel">signature</a> 権é™ã‚„ <a href="http://developer.android.com/guide/topics/manifest/permission-element.html#plevel">signatureOrSystem</a> 権é™ãªã©ã¸ã®æ˜‡æ ¼ã«ã“ã®ã‚ˆã†ãªè„†å¼±æ€§ãŒåˆ©ç”¨ã•ã‚Œã‚‹ãŠãã‚ŒãŒã‚ã‚‹ãŸã‚ã€ã“ã®å•é¡Œã®é‡å¤§åº¦ã¯ã€Œé«˜ã€ã¨åˆ¤æ–ã•ã‚Œã¦ã„ã¾ã™ã€‚</p> +ãŠãã‚ŒãŒã‚ã‚Šã¾ã™ã€‚サードパーティ製アプリã«ã‚ˆã‚‹ã‚¢ã‚¯ã‚»ã‚¹ãŒä¸å¯èƒ½ã¨ãªã£ã¦ã„ã‚‹ <a href="http://developer.android.com/guide/topics/manifest/permission-element.html#plevel">signature</a> 権é™ã‚„ <a href="http://developer.android.com/guide/topics/manifest/permission-element.html#plevel">signatureOrSystem</a> 権é™ãªã©ã¸ã®æ˜‡æ ¼ã«åˆ©ç”¨ã•ã‚Œã‚‹ãŠãã‚ŒãŒã‚ã‚‹ãŸã‚ã€ã“ã®å•é¡Œã®é‡å¤§åº¦ã¯ã€Œé«˜ã€ã¨åˆ¤æ–ã•ã‚Œã¦ã„ã¾ã™ã€‚</p> <table> <tbody><tr> <th>CVE</th> diff --git a/ja/security/bulletin/2016-06-01.html b/ja/security/bulletin/2016-06-01.html index 4ae53279..69835d17 100644 --- a/ja/security/bulletin/2016-06-01.html +++ b/ja/security/bulletin/2016-06-01.html @@ -28,7 +28,7 @@ <p>最もé‡å¤§åº¦ã®é«˜ã„å•é¡Œã¯ã€å¤šæ§˜ãªæ–¹æ³•ï¼ˆãƒ¡ãƒ¼ãƒ«ã€ã‚¦ã‚§ãƒ–ã®é–²è¦§ã€MMS ãªã©ï¼‰ã«ã‚ˆã‚Šã€æ”»æ’ƒå¯¾è±¡ã®ç«¯æœ«ã§ãƒ¡ãƒ‡ã‚£ã‚¢ ファイルを処ç†ã™ã‚‹éš›ã«ãƒªãƒ¢ãƒ¼ãƒˆã§ã®ã‚³ãƒ¼ãƒ‰å®Ÿè¡ŒãŒå¯èƒ½ã«ãªã‚‹ãŠãã‚Œã®ã‚ã‚‹é‡å¤§ãªã‚»ã‚ュリティã®è„†å¼±æ€§ã§ã™ã€‚<a href="/security/overview/updates-resources.html#severity">é‡å¤§åº¦ã®è©•ä¾¡</a>ã¯ã€æ”»æ’ƒå¯¾è±¡ã®ç«¯æœ«ã§ãã®è„†å¼±æ€§ãŒæ‚ªç”¨ã•ã‚ŒãŸå ´åˆã®å½±éŸ¿ã«åŸºã¥ãã‚‚ã®ã§ã€ãƒ—ラットフォームやサービスã§ã®ãƒªã‚¹ã‚¯è»½æ¸›ç–ãŒé–‹ç™ºç›®çš„ã¾ãŸã¯ä¸æ£ãªå›žé¿ã«ã‚ˆã‚Šç„¡åŠ¹ã¨ãªã£ã¦ã„ã‚‹ã“ã¨ã‚’å‰æã¨ã—ã¦ã„ã¾ã™ã€‚</p> -<p>ã“ã®æ–°ãŸã«å ±å‘Šã•ã‚ŒãŸå•é¡Œã«ã‚ˆã£ã¦å®Ÿéš›ã®ãƒ¦ãƒ¼ã‚¶ãƒ¼ç«¯æœ«ãŒä¸æ£ä½¿ç”¨ã•ã‚ŒãŸå ±å‘Šã¯ã‚ã‚Šã¾ã›ã‚“。<a href="#mitigations">Android ã‚»ã‚ュリティ プラットフォームã®ä¿è·</a>ã‚„ SafetyNet ã®ã‚ˆã†ãªã‚µãƒ¼ãƒ“スã®ä¿è·ã«ã¤ã„ã¦è©³ã—ãã¯ã€<a href="/security/enhancements/index.html">Android 㨠Google サービスã§ã®ãƒªã‚¹ã‚¯è»½æ¸›ç–</a>ã‚’ã”覧ãã ã•ã„。ã“ã†ã—ãŸä¿è·ã«ã‚ˆã‚Šã€Android プラットフォームã®ã‚»ã‚ュリティãŒæ”¹å–„ã•ã‚Œã¾ã™ã€‚</p> +<p>ã“ã®æ–°ãŸã«å ±å‘Šã•ã‚ŒãŸå•é¡Œã«ã‚ˆã£ã¦å®Ÿéš›ã®ãƒ¦ãƒ¼ã‚¶ãƒ¼ç«¯æœ«ãŒä¸æ£ä½¿ç”¨ã•ã‚ŒãŸå ±å‘Šã¯ã‚ã‚Šã¾ã›ã‚“。<a href="/security/enhancements/index.html">Android ã‚»ã‚ュリティ プラットフォームã®ä¿è·</a>ã‚„ SafetyNet ã®ã‚ˆã†ãªã‚µãƒ¼ãƒ“スã®ä¿è·ã«ã¤ã„ã¦è©³ã—ãã¯ã€<a href="#mitigations">Android 㨠Google サービスã§ã®ãƒªã‚¹ã‚¯è»½æ¸›ç–</a>ã‚’ã”覧ãã ã•ã„。ã“ã†ã—ãŸä¿è·ã«ã‚ˆã‚Šã€Android プラットフォームã®ã‚»ã‚ュリティãŒæ”¹å–„ã•ã‚Œã¾ã™ã€‚</p> <p>ã”利用ã®ç«¯æœ«ã«ä¸Šè¨˜ã®ã‚¢ãƒƒãƒ—デートをé©ç”¨ã™ã‚‹ã“ã¨ã‚’ã™ã¹ã¦ã®ãƒ¦ãƒ¼ã‚¶ãƒ¼ã«ãŠã™ã™ã‚ã—ã¾ã™ã€‚</p> @@ -47,7 +47,7 @@ <p>調査ã«ã”å”力ãã ã•ã£ãŸä¸‹è¨˜ã®çš†æ§˜æ–¹ã«æ„Ÿè¬ã„ãŸã—ã¾ã™ï¼ˆæ•¬ç§°ç•¥ï¼‰ã€‚</p> <ul> - <li>Tencent KeenLab（<a href="https://twitter.com/returnsme">@keen_lab</a>）㮠Di Shen（<a href="https://twitter.com/keen_lab">@returnsme</a>）: CVE-2016-2468</li><li> <a href="http://bits-please.blogspot.com">Gal Beniamini</a>（<a href="https://twitter.com/laginimaineb">@laginimaineb</a>）: CVE-2016-2476</li><li>Qihoo 360 Technology Co. Ltd. IceSword Lab ã® Gengjia Chen（<a href="https://twitter.com/chengjia4574">@chengjia4574</a>）ã€pjf（<a href="http://weibo.com/jfpan">weibo.com/jfpan</a>）: CVE-2016-2492</li><li>Mobile Safe Teamã€Qihoo 360 Technology Co. Ltd. ã® Hao Chenã€Guang Gongã€Wenlin Yang: CVE-2016-2470ã€CVE-2016-2471ã€CVE-2016-2472ã€CVE-2016-2473ã€CVE-2016-2498</li><li> <a href="http://www.iwobanas.com">Iwo Banas</a>: CVE-2016-2496</li><li>Qihoo 360 Technology Co. Ltd. IceSword Lab ã® Jianqiang Zhao（<a href="https://twitter.com/jianqiangzhao">@jianqiangzhao</a>）ã€pjf（<a href="http://weibo.com/jfpan">weibo.com/jfpan</a>）: CVE-2016-2490ã€CVE-2016-2491</li><li>Google ã® Lee Campbell: CVE-2016-2500</li><li>Google ã‚»ã‚ュリティ ãƒãƒ¼ãƒ ã® Maciej SzawÅ‚owski: CVE-2016-2474</li><li>Google ã® Marco Nelissen ãŠã‚ˆã³ Max Spector: CVE-2016-2487</li><li>Google Project Zero ã® Mark Brand: CVE-2016-2494</li><li><a href="https://twitter.com/Mingjian_Zhou">C0RE Team</a> ã® Mingjian Zhou（<a href="https://twitter.com/chiachih_wu">@Mingjian_Zhou</a>）ã€Chiachih Wu（<a href="http://c0reteam.org">@chiachih_wu</a>）ã€Xuxian Jiang: CVE-2016-2477ã€CVE-2016-2478ã€CVE-2016-2479ã€CVE-2016-2480ã€CVE-2016-2481ã€CVE-2016-2482ã€CVE-2016-2483ã€CVE-2016-2484ã€CVE-2016-2485ã€CVE-2016-2486</li><li> <a href="mailto:sbauer@plzdonthack.me">Scott Bauer</a>（<a href="https://twitter.com/ScottyBauer1">@ScottyBauer1</a>）: CVE-2016-2066ã€CVE-2016-2061ã€CVE-2016-2465ã€CVE-2016-2469ã€CVE-2016-2489</li><li>Vasily Vasilev: CVE-2016-2463</li><li>Alibaba Inc. ã® Weichao Sun（<a href="https://twitter.com/sunblate">@sunblate</a>）: CVE-2016-2495</li><li>Tencent Security Platform Department ã® Xiling Gong: CVE-2016-2499</li><li>Android ã‚»ã‚ュリティ ãƒãƒ¼ãƒ ã® Zach Riggle（<a href="https://twitter.com/ebeip90">@ebeip90</a>）: CVE-2016-2493</li></ul> + <li>Tencent KeenLab（<a href="https://twitter.com/keen_lab">@keen_lab</a>）㮠Di Shen（<a href="https://twitter.com/returnsme">@returnsme</a>）: CVE-2016-2468</li><li> <a href="http://bits-please.blogspot.com">Gal Beniamini</a>（<a href="https://twitter.com/laginimaineb">@laginimaineb</a>）: CVE-2016-2476</li><li>Qihoo 360 Technology Co. Ltd. IceSword Lab ã® Gengjia Chen（<a href="https://twitter.com/chengjia4574">@chengjia4574</a>）ã€pjf（<a href="http://weibo.com/jfpan">weibo.com/jfpan</a>）: CVE-2016-2492</li><li>Mobile Safe Teamã€Qihoo 360 Technology Co. Ltd. ã® Hao Chenã€Guang Gongã€Wenlin Yang: CVE-2016-2470ã€CVE-2016-2471ã€CVE-2016-2472ã€CVE-2016-2473ã€CVE-2016-2498</li><li> <a href="http://www.iwobanas.com">Iwo Banas</a>: CVE-2016-2496</li><li>Qihoo 360 Technology Co. Ltd. IceSword Lab ã® Jianqiang Zhao（<a href="https://twitter.com/jianqiangzhao">@jianqiangzhao</a>）ã€pjf（<a href="http://weibo.com/jfpan">weibo.com/jfpan</a>）: CVE-2016-2490ã€CVE-2016-2491</li><li>Google ã® Lee Campbell: CVE-2016-2500</li><li>Google ã‚»ã‚ュリティ ãƒãƒ¼ãƒ ã® Maciej SzawÅ‚owski: CVE-2016-2474</li><li>Google ã® Marco Nelissen ãŠã‚ˆã³ Max Spector: CVE-2016-2487</li><li>Google Project Zero ã® Mark Brand: CVE-2016-2494</li><li><a href="http://c0reteam.org">C0RE Team</a> ã® Mingjian Zhou（<a href="https://twitter.com/Mingjian_Zhou">@Mingjian_Zhou</a>）ã€Chiachih Wu（<a href="https://twitter.com/chiachih_wu">@chiachih_wu</a>）ã€Xuxian Jiang: CVE-2016-2477ã€CVE-2016-2478ã€CVE-2016-2479ã€CVE-2016-2480ã€CVE-2016-2481ã€CVE-2016-2482ã€CVE-2016-2483ã€CVE-2016-2484ã€CVE-2016-2485ã€CVE-2016-2486</li><li> <a href="mailto:sbauer@plzdonthack.me">Scott Bauer</a>（<a href="https://twitter.com/ScottyBauer1">@ScottyBauer1</a>）: CVE-2016-2066ã€CVE-2016-2061ã€CVE-2016-2465ã€CVE-2016-2469ã€CVE-2016-2489</li><li>Vasily Vasilev: CVE-2016-2463</li><li>Alibaba Inc. ã® Weichao Sun（<a href="https://twitter.com/sunblate">@sunblate</a>）: CVE-2016-2495</li><li>Tencent Security Platform Department ã® Xiling Gong: CVE-2016-2499</li><li>Android ã‚»ã‚ュリティ ãƒãƒ¼ãƒ ã® Zach Riggle（<a href="https://twitter.com/ebeip90">@ebeip90</a>）: CVE-2016-2493</li></ul> <h2 id="security_vulnerability_details">ã‚»ã‚ュリティã®è„†å¼±æ€§ã®è©³ç´°</h2> diff --git a/ja/security/bulletin/2016-07-01.html b/ja/security/bulletin/2016-07-01.html index 31a859f9..89588a9b 100644 --- a/ja/security/bulletin/2016-07-01.html +++ b/ja/security/bulletin/2016-07-01.html @@ -57,7 +57,7 @@ <h3 id="remote-code-execution-vulnerability-in-mediaserver"> メディアサーãƒãƒ¼ã§ã®ãƒªãƒ¢ãƒ¼ãƒˆã‚³ãƒ¼ãƒ‰å®Ÿè¡Œã®è„†å¼±æ€§</h3> -<p>メディアサーãƒãƒ¼ã«ãƒªãƒ¢ãƒ¼ãƒˆã‚³ãƒ¼ãƒ‰å®Ÿè¡Œã®è„†å¼±æ€§ãŒã‚ã‚‹ãŸã‚ã€æ”»æ’ƒè€…ãŒç‰¹åˆ¥ã«ç´°å·¥ã—ãŸãƒ•ã‚¡ã‚¤ãƒ«ã‚’使用ã—ã¦ã€ãƒ¡ãƒ‡ã‚£ã‚¢ ファイルやデータã®å‡¦ç†ä¸ã«ãƒ¡ãƒ¢ãƒªç ´å£Šã‚’引ãèµ·ã“ã™ãŠãã‚ŒãŒã‚ã‚Šã¾ã™ã€‚ã“ã®å•é¡Œã¯ã€ãƒ¡ãƒ‡ã‚£ã‚¢ã‚µãƒ¼ãƒãƒ¼ã®ãƒ—ãƒã‚»ã‚¹ã«ãŠã„ã¦ãƒªãƒ¢ãƒ¼ãƒˆã§ã‚³ãƒ¼ãƒ‰ãŒå®Ÿè¡Œã•ã‚Œã‚‹ãŠãã‚ŒãŒã‚ã‚‹ãŸã‚ã€é‡å¤§ã¨è¦‹ãªã•ã‚Œã¦ã„ã¾ã™ã€‚メディアサーãƒãƒ¼ã®ãƒ—ãƒã‚»ã‚¹ã¯ã€éŸ³å£°ã‚„å‹•ç”»ã®ã‚¹ãƒˆãƒªãƒ¼ãƒ ã«ã‚¢ã‚¯ã‚»ã‚¹ã§ãã‚‹ã»ã‹ã€ã‚µãƒ¼ãƒ‰ãƒ‘ーティ製アプリãŒé€šå¸¸ã¯ã‚¢ã‚¯ã‚»ã‚¹ã§ããªã„よã†ãªæ¨©é™ã«ã‚¢ã‚¯ã‚»ã‚¹ã§ãã¾ã™ã€‚</p> +<p>メディアサーãƒãƒ¼ã«ãƒªãƒ¢ãƒ¼ãƒˆã‚³ãƒ¼ãƒ‰å®Ÿè¡Œã®è„†å¼±æ€§ãŒã‚ã‚‹ãŸã‚ã€æ”»æ’ƒè€…ãŒç‰¹åˆ¥ã«ç´°å·¥ã—ãŸãƒ•ã‚¡ã‚¤ãƒ«ã‚’使用ã—ã¦ã€ãƒ¡ãƒ‡ã‚£ã‚¢ ファイルやデータã®å‡¦ç†ä¸ã«ãƒ¡ãƒ¢ãƒªç ´å£Šã‚’引ãèµ·ã“ã™ãŠãã‚ŒãŒã‚ã‚Šã¾ã™ã€‚メディアサーãƒãƒ¼ã®ãƒ—ãƒã‚»ã‚¹ã«ãŠã„ã¦ãƒªãƒ¢ãƒ¼ãƒˆã§ã‚³ãƒ¼ãƒ‰ãŒå®Ÿè¡Œã•ã‚Œã‚‹ãŠãã‚ŒãŒã‚ã‚‹ãŸã‚ã€ã“ã®å•é¡Œã¯ã€Œé‡å¤§ã€ã¨åˆ¤æ–ã•ã‚Œã¦ã„ã¾ã™ã€‚メディアサーãƒãƒ¼ã®ãƒ—ãƒã‚»ã‚¹ã¯ã€éŸ³å£°ã‚„å‹•ç”»ã®ã‚¹ãƒˆãƒªãƒ¼ãƒ ã«ã‚¢ã‚¯ã‚»ã‚¹ã§ãã‚‹ã»ã‹ã€ã‚µãƒ¼ãƒ‰ãƒ‘ーティ製アプリãŒé€šå¸¸ã¯ã‚¢ã‚¯ã‚»ã‚¹ã§ããªã„よã†ãªæ¨©é™ã«ã‚¢ã‚¯ã‚»ã‚¹ã§ãã¾ã™ã€‚</p> <p>影響をå—ã‘る機能ã¯ã‚ªãƒšãƒ¬ãƒ¼ãƒ†ã‚£ãƒ³ã‚° システムã®ä¸æ ¸éƒ¨åˆ†ã¨ã—ã¦æä¾›ã•ã‚Œã¦ãŠã‚Šã€è¤‡æ•°ã®ã‚¢ãƒ—リã«ãŠã„ã¦ã€ãƒªãƒ¢ãƒ¼ãƒˆ コンテンツ（特㫠MMS やブラウザã§ã®ãƒ¡ãƒ‡ã‚£ã‚¢ã®å†ç”Ÿï¼‰ã«ã‚ˆã£ã¦ã“ã®è„†å¼±æ€§ãŒæ”»æ’ƒã•ã‚Œã‚‹ãŠãã‚ŒãŒã‚ã‚Šã¾ã™ã€‚</p> <table> @@ -105,8 +105,8 @@ <tr> <td>CVE-2016-2508</td> <td><a href="https://android.googlesource.com/platform/frameworks/av/+/f81038006b4c59a5a148dcad887371206033c28f"> -A-28799341</a> - [<a href="https://android.googlesource.com/platform/frameworks/av/+/d112f7d0c1dbaf0368365885becb11ca8d3f13a4">2</a>] + A-28799341</a> + [<a href="https://android.googlesource.com/platform/frameworks/av/+/d112f7d0c1dbaf0368365885becb11ca8d3f13a4">2</a>] </td> <td>é‡å¤§</td> <td><a href="#all_nexus">ã™ã¹ã¦ã® Nexus</a></td> @@ -116,8 +116,8 @@ A-28799341</a> <tr> <td>CVE-2016-3741</td> <td><a href="https://android.googlesource.com/platform/external/libavc/+/e629194c62a9a129ce378e08cb1059a8a53f1795"> -A-28165661</a> - [<a href="https://android.googlesource.com/platform/external/libavc/+/cc676ebd95247646e67907ccab150fb77a847335">2</a>] + A-28165661</a> + [<a href="https://android.googlesource.com/platform/external/libavc/+/cc676ebd95247646e67907ccab150fb77a847335">2</a>] </td> <td>é‡å¤§</td> <td><a href="#all_nexus">ã™ã¹ã¦ã® Nexus</a></td> @@ -495,8 +495,8 @@ OpenSSL ã§ã®æƒ…å ±é–‹ç¤ºã®è„†å¼±æ€§</h3> <tr> <td>CVE-2016-3754</td> <td><a href="https://android.googlesource.com/platform/frameworks/av/+/6fdee2a83432b3b150d6a34f231c4e2f7353c01e"> -A-28615448</a> - [<a href="https://android.googlesource.com/platform/frameworks/av/+/e7142a0703bc93f75e213e96ebc19000022afed9">2</a>] + A-28615448</a> + [<a href="https://android.googlesource.com/platform/frameworks/av/+/e7142a0703bc93f75e213e96ebc19000022afed9">2</a>] </td> <td>高</td> <td><a href="#all_nexus">ã™ã¹ã¦ã® Nexus</a></td> @@ -670,8 +670,8 @@ Bluetooth ã§ã®æ¨©é™æ˜‡æ ¼ã®è„†å¼±æ€§</h3> <tr> <td>CVE-2016-3760</td> <td><a href="https://android.googlesource.com/platform/hardware/libhardware/+/8b3d5a64c3c8d010ad4517f652731f09107ae9c5">A-27410683</a> - [<a href="https://android.googlesource.com/platform/system/bt/+/37c88107679d36c419572732b4af6e18bb2f7dce">2</a>] - [<a href="https://android.googlesource.com/platform/packages/apps/Bluetooth/+/122feb9a0b04290f55183ff2f0384c6c53756bd8">3</a>] +[<a href="https://android.googlesource.com/platform/system/bt/+/37c88107679d36c419572732b4af6e18bb2f7dce">2</a>] +[<a href="https://android.googlesource.com/platform/packages/apps/Bluetooth/+/122feb9a0b04290f55183ff2f0384c6c53756bd8">3</a>] </td> <td>ä¸</td> <td><a href="#all_nexus">ã™ã¹ã¦ã® Nexus</a></td> @@ -836,8 +836,8 @@ NFC ã§ã®æ¨©é™æ˜‡æ ¼ã®è„†å¼±æ€§</h3> <tr> <td>CVE-2016-3766</td> <td><a href="https://android.googlesource.com/platform/frameworks/av/+/6fdee2a83432b3b150d6a34f231c4e2f7353c01e"> -A-28471206</a> - [<a href="https://android.googlesource.com/platform/frameworks/av/+/e7142a0703bc93f75e213e96ebc19000022afed9">2</a>] + A-28471206</a> + [<a href="https://android.googlesource.com/platform/frameworks/av/+/e7142a0703bc93f75e213e96ebc19000022afed9">2</a>] </td> <td>ä¸</td> <td><a href="#all_nexus">ã™ã¹ã¦ã® Nexus</a></td> @@ -1105,7 +1105,7 @@ USB ドライãƒã§ã®æ¨©é™æ˜‡æ ¼ã®è„†å¼±æ€§</h3> <td>CVE-2014-9795</td> <td>A-28820720<br /> <a href="https://us.codeaurora.org/cgit/quic/la//kernel/lk/commit/?id=ce2a0ea1f14298abc83729f3a095adab43342342">QC-CR681957</a> - [<a href="https://us.codeaurora.org/cgit/quic/la//kernel/lk/commit/?id=fc3b31f81a1c128c2bcc745564a075022cd72a2e">2</a>] + [<a href="https://us.codeaurora.org/cgit/quic/la//kernel/lk/commit/?id=fc3b31f81a1c128c2bcc745564a075022cd72a2e">2</a>] </td> <td>é‡å¤§</td> <td>Nexus 5</td> @@ -1198,7 +1198,7 @@ USB ドライãƒã§ã®æ¨©é™æ˜‡æ ¼ã®è„†å¼±æ€§</h3> <td>CVE-2014-9783</td> <td>A-28441831<br /> <a href="https://us.codeaurora.org/cgit/quic/la/kernel/msm/commit/?id=2b1050b49a9a5f7bb57006648d145e001a3eaa8b">QC-CR511382</a> - [<a href="https://us.codeaurora.org/cgit/quic/la/kernel/msm-3.10/commit/?id=a7502f4f801bb95bff73617309835bb7a016cde5">2</a>]</td> + [<a href="https://us.codeaurora.org/cgit/quic/la/kernel/msm-3.10/commit/?id=a7502f4f801bb95bff73617309835bb7a016cde5">2</a>]</td> <td>高</td> <td>Nexus 7（2013）</td> <td>2014 å¹´ 3 月 31 æ—¥</td> @@ -1247,7 +1247,7 @@ USB ドライãƒã§ã®æ¨©é™æ˜‡æ ¼ã®è„†å¼±æ€§</h3> <td>CVE-2014-9790</td> <td>A-28769136<br /> <a href="https://us.codeaurora.org/cgit/quic/la/kernel/msm/commit/?h=LA.BF.1.1.3_rb1.12&id=6ed921bda8cbb505e8654dfc1095185b0bccc38e">QC-CR545716</a> - [<a href="https://us.codeaurora.org/cgit/quic/la/kernel/msm/commit?h=LA.BF.1.1.3_rb1.12&id=9bc30c0d1832f7dd5b6fa10d5e48a29025176569">2</a>]</td> + [<a href="https://us.codeaurora.org/cgit/quic/la/kernel/msm/commit?h=LA.BF.1.1.3_rb1.12&id=9bc30c0d1832f7dd5b6fa10d5e48a29025176569">2</a>]</td> <td>高</td> <td>Nexus 5ã€Nexus 7（2013）</td> <td>2014 å¹´ 4 月 30 æ—¥</td> diff --git a/ja/security/bulletin/2016-08-01.html b/ja/security/bulletin/2016-08-01.html index 2014204b..81c58137 100644 --- a/ja/security/bulletin/2016-08-01.html +++ b/ja/security/bulletin/2016-08-01.html @@ -1088,7 +1088,7 @@ QC-CR#794217</a></p> <a href="https://us.codeaurora.org/cgit/quic/la//kernel/msm/commit/?id=ad376e4053b87bd58f62f45b6df2c5544bc21aee"> QC-CR#836226</a></p></td> <td>高</td> - <td>Google Nexus 5</td> + <td>Nexus 5</td> <td>2015 å¹´ 9 月 11 æ—¥</td> </tr> <tr> @@ -1098,7 +1098,7 @@ QC-CR#836226</a></p></td> <a href="https://us.codeaurora.org/cgit/quic/la/kernel/msm-3.10/commit/?id=c10f03f191307f7114af89933f2d91b830150094"> QC-CR#550061</a></p></td> <td>ä¸</td> - <td>Google Nexus 5</td> + <td>Nexus 5</td> <td>2014 å¹´ 3 月 13 æ—¥</td> </tr> <tr> @@ -1431,7 +1431,7 @@ N-CVE-2016-3844</p></td> <td>CVE-2016-3845</td> <td>A-28399876*</td> <td>高</td> - <td>Google Nexus 5</td> + <td>Nexus 5</td> <td>2016 å¹´ 4 月 20 æ—¥</td> </tr> </tbody></table> @@ -1608,8 +1608,7 @@ QC-CR#945164</a></p></td> <h3 id="elevation-of-privilege-vulnerability-in-lg-electronics-bootloader"> LG Electronics ブートãƒãƒ¼ãƒ€ãƒ¼ã§ã®æ¨©é™æ˜‡æ ¼ã®è„†å¼±æ€§</h3> <p> -LG Electronics ブートãƒãƒ¼ãƒ€ãƒ¼ã«æ¨©é™æ˜‡æ ¼ã®è„†å¼±æ€§ãŒã‚ã‚‹ãŸã‚ã€æ”»æ’ƒè€…ã«ã‚ˆã£ã¦ã‚«ãƒ¼ãƒãƒ«å†…ã§ä»»æ„ã®ã‚³ãƒ¼ãƒ‰ãŒå®Ÿè¡Œã•ã‚Œã‚‹ãŠãã‚ŒãŒã‚ã‚Šã¾ã™ã€‚ -最åˆã«ç‰¹æ¨©ãƒ—ãƒã‚»ã‚¹ã¸ã®ä¾µå…¥ãŒå¿…è¦ã§ã‚ã‚‹ãŸã‚ã€ã“ã®å•é¡Œã®é‡å¤§åº¦ã¯ã€Œé«˜ã€ã¨åˆ¤æ–ã•ã‚Œã¦ã„ã¾ã™ã€‚ +LG Electronics ブートãƒãƒ¼ãƒ€ãƒ¼ã«æ¨©é™æ˜‡æ ¼ã®è„†å¼±æ€§ãŒã‚ã‚‹ãŸã‚ã€æ”»æ’ƒè€…ã«ã‚ˆã£ã¦ã‚«ãƒ¼ãƒãƒ«å†…ã§ä»»æ„ã®ã‚³ãƒ¼ãƒ‰ãŒå®Ÿè¡Œã•ã‚Œã‚‹ãŠãã‚ŒãŒã‚ã‚Šã¾ã™ã€‚最åˆã«ç‰¹æ¨©ãƒ—ãƒã‚»ã‚¹ã¸ã®ä¾µå…¥ãŒå¿…è¦ã§ã‚ã‚‹ãŸã‚ã€ã“ã®å•é¡Œã®é‡å¤§åº¦ã¯ã€Œé«˜ã€ã¨åˆ¤æ–ã•ã‚Œã¦ã„ã¾ã™ã€‚ </p> <table> <colgroup><col width="19%" /> @@ -1684,7 +1683,7 @@ QC-CR#786116</a></p></td> <a href="https://us.codeaurora.org/cgit/quic/la/kernel/msm-3.10/commit/?id=bfc6eee5e30a0c20bc37495233506f4f0cc4991d"> QC-CR#542223</a></p></td> <td>ä¸</td> - <td>Google Nexus 5</td> + <td>Nexus 5</td> <td>2014 å¹´ 3 月 27 æ—¥</td> </tr> <tr> @@ -1724,7 +1723,7 @@ QC-CR#551795</a></p></td> <a href="https://us.codeaurora.org/cgit/quic/la/kernel/msm-3.10/commit/?id=46135d80765cb70a914f02a6e7b6abe64679ec86"> QC-CR#563752</a></p></td> <td>ä¸</td> - <td>Google Nexus 5</td> + <td>Nexus 5</td> <td>2014 å¹´ 4 月 30 æ—¥</td> </tr> <tr> @@ -1744,7 +1743,7 @@ QC-CR#554575</a></p></td> <a href="https://us.codeaurora.org/cgit/quic/la//kernel/msm-3.10/commit/?id=8756624acb1e090b45baf07b2a8d0ebde114000e"> QC-CR#547910</a></p></td> <td>ä¸</td> - <td>Google Nexus 5</td> + <td>Nexus 5</td> <td>2014 å¹´ 7 月 3 æ—¥</td> </tr> <tr> @@ -2090,16 +2089,17 @@ Qualcomm コンãƒãƒ¼ãƒãƒ³ãƒˆã§ã®è„†å¼±æ€§</h3> <p> <a href="#2016-08-01-details">2016-08-01</a> 㨠<a href="#2016-08-05-details">2016-08-05</a> ã®ã‚»ã‚ュリティ脆弱性ã®è©³ç´°ã«é–¢ã™ã‚‹ã‚»ã‚¯ã‚·ãƒ§ãƒ³ã§ã€å„表ä¸ã®ã€Œæ›´æ–°ã•ã‚ŒãŸ Nexus 端末ã€åˆ—ã«ã€ãã®å•é¡Œã®å½±éŸ¿ã‚’å—ã‘ã‚‹ã€æ›´æ–°å¯¾è±¡ã® Nexus 端末ã®ç¨®é¡žã‚’記載ã—ã¦ã„ã¾ã™ã€‚ã“ã®åˆ—ã«ã¯æ¬¡ã®ã„ãšã‚Œã‹ãŒè¡¨ç¤ºã•ã‚Œã¦ã„ã¾ã™ã€‚</p> <ul> -<li><strong>ã™ã¹ã¦ã® Nexus 端末</strong>: å•é¡ŒãŒã™ã¹ã¦ã® Nexus 端末ã«å½±éŸ¿ã‚’与ãˆã‚‹å ´åˆã€è¡¨ã®ã€Œæ›´æ–°ã•ã‚ŒãŸ Nexus 端末ã€åˆ—ã«ã¯ã€Œã™ã¹ã¦ã® Nexusã€ã¨è¨˜è¼‰ã•ã‚Œã¦ã„ã¾ã™ã€‚<em></em>「ã™ã¹ã¦ã® Nexusã€ã«ã¯<a href="https://support.google.com/nexus/answer/4457705#nexus_devices">サãƒãƒ¼ãƒˆå¯¾è±¡ã®ç«¯æœ«</a>（Nexus 5ã€Nexus 5Xã€Nexus 6ã€Nexus 6Pã€Nexus 7（2013）ã€Nexus 9ã€Android Oneã€Nexus Playerã€Pixel C）ãŒå«ã¾ã‚Œã¾ã™ã€‚</li> -<li><strong>一部㮠Nexus 端末</strong>: å•é¡ŒãŒä¸€éƒ¨ã® Nexus 端末ã®ã¿ã«å½±éŸ¿ã™ã‚‹å ´åˆã€ã€Œæ›´æ–°ã•ã‚ŒãŸ Nexus 端末ã€åˆ—ã«ã¯å½±éŸ¿ã‚’å—ã‘ã‚‹ Nexus 端末ãŒè¨˜è¼‰ã•ã‚Œã¦ã„ã¾ã™ã€‚<em></em></li> -<li><strong>影響をå—ã‘ã‚‹ Nexus 端末ãŒãªã„</strong>: å•é¡Œã®å½±éŸ¿ã‚’å—ã‘ã‚‹ Nexus 端末ãŒãªã„å ´åˆã€è¡¨ã®ã€Œæ›´æ–°ã•ã‚ŒãŸ Nexus 端末ã€åˆ—ã«ã¯ã€Œãªã—ã€ã¨è¨˜è¼‰ã•ã‚Œã¦ã„ã¾ã™ã€‚<em></em> +<li><strong>ã™ã¹ã¦ã® Nexus 端末</strong>: å•é¡ŒãŒã™ã¹ã¦ã® Nexus 端末ã«å½±éŸ¿ã‚’与ãˆã‚‹å ´åˆã€è¡¨ã®ã€Œæ›´æ–°ã•ã‚ŒãŸ Nexus 端末<em></em>ã€åˆ—ã«ã¯ã€Œã™ã¹ã¦ã® Nexusã€ã¨è¨˜è¼‰ã•ã‚Œã¦ã„ã¾ã™ã€‚「ã™ã¹ã¦ã® Nexusã€ã«ã¯<a href="https://support.google.com/nexus/answer/4457705#nexus_devices">サãƒãƒ¼ãƒˆå¯¾è±¡ã®ç«¯æœ«</a>（Nexus 5ã€Nexus 5Xã€Nexus 6ã€Nexus 6Pã€Nexus 7（2013）ã€Nexus 9ã€Android Oneã€Nexus Playerã€Pixel C）ãŒå«ã¾ã‚Œã¾ã™ã€‚</li> +<li><strong>一部㮠Nexus 端末</strong>: å•é¡ŒãŒä¸€éƒ¨ã® Nexus 端末ã®ã¿ã«å½±éŸ¿ã™ã‚‹å ´åˆã€ã€Œæ›´æ–°ã•ã‚ŒãŸ Nexus 端末<em></em>ã€åˆ—ã«ã¯å½±éŸ¿ã‚’å—ã‘ã‚‹ Nexus 端末ãŒè¨˜è¼‰ã•ã‚Œã¦ã„ã¾ã™ã€‚</li> +<li><strong>影響をå—ã‘ã‚‹ Nexus 端末ãŒãªã„</strong>: å•é¡Œã®å½±éŸ¿ã‚’å—ã‘ã‚‹ Nexus 端末ãŒãªã„å ´åˆã€è¡¨ã®ã€Œæ›´æ–°ã•ã‚ŒãŸ Nexus 端末<em></em>ã€åˆ—ã«ã¯ã€Œãªã—ã€ã¨è¨˜è¼‰ã•ã‚Œã¦ã„ã¾ã™ã€‚ </li> </ul> <p> <strong>4. 「å‚ç…§ã€åˆ—ã®é …ç›®ã¯ã©ã®ã‚ˆã†ãªæƒ…å ±ã«é–¢é€£ä»˜ã‘られã¦ã„ã¾ã™ã‹ï¼Ÿ</strong> </p> <p> -脆弱性ã®è©³ç´°ã®è¡¨ã§ã€Œå‚ç…§ã€åˆ—ã«è¨˜è¼‰ã•ã‚Œã¦ã„る内容ã«ã¯ã€å‚ç…§ã®å€¤ãŒå±žã—ã¦ã„る組織を示ã—ãŸæŽ¥é 辞ãŒå«ã¾ã‚Œã¦ã„ã‚‹å ´åˆãŒã‚ã‚Šã¾ã™ã€‚<em></em>å„接é 辞ã®æ„味ã¯ä»¥ä¸‹ã®ã¨ãŠã‚Šã§ã™ã€‚</p> +脆弱性ã®è©³ç´°ã®è¡¨ã§ã€Œå‚ç…§<em></em>ã€åˆ—ã«è¨˜è¼‰ã•ã‚Œã¦ã„る内容ã«ã¯ã€å‚ç…§ã®å€¤ãŒå±žã—ã¦ã„る組織を示ã—ãŸæŽ¥é 辞ãŒå«ã¾ã‚Œã¦ã„ã‚‹å ´åˆãŒã‚ã‚Šã¾ã™ã€‚å„接é 辞ã®æ„味ã¯ä»¥ä¸‹ã®ã¨ãŠã‚Šã§ã™ã€‚ +</p> <table> <tbody><tr> <th>接é 辞</th> diff --git a/ja/security/bulletin/2016-10-01.html b/ja/security/bulletin/2016-10-01.html index e6e06546..c02bcebd 100644 --- a/ja/security/bulletin/2016-10-01.html +++ b/ja/security/bulletin/2016-10-01.html @@ -1699,7 +1699,7 @@ Binder ã«æƒ…å ±é–‹ç¤ºã®è„†å¼±æ€§ãŒã‚ã‚‹ãŸã‚ã€æ‚ªæ„ã®ã‚ã‚‹ãƒãƒ¼ã‚«ãƒ«ã <ul> <li><strong>ã™ã¹ã¦ã® Nexus 端末</strong>: å•é¡ŒãŒã™ã¹ã¦ã® Nexus 端末ã«å½±éŸ¿ã‚’与ãˆã‚‹å ´åˆã€è¡¨ã®ã€Œæ›´æ–°ã•ã‚ŒãŸ Nexus 端末<em></em>ã€åˆ—ã«ã¯ã€Œã™ã¹ã¦ã® Nexusã€ã¨è¨˜è¼‰ã•ã‚Œã¦ã„ã¾ã™ã€‚「ã™ã¹ã¦ã® Nexusã€ã«ã¯<a href="https://support.google.com/nexus/answer/4457705#nexus_devices">サãƒãƒ¼ãƒˆå¯¾è±¡ã®ç«¯æœ«</a>（Nexus 5ã€Nexus 5Xã€Nexus 6ã€Nexus 6Pã€Nexus 9ã€Android Oneã€Nexus Playerã€Pixel C）ãŒå«ã¾ã‚Œã¾ã™ã€‚</li> <li><strong>一部㮠Nexus 端末</strong>: å•é¡ŒãŒä¸€éƒ¨ã® Nexus 端末ã®ã¿ã«å½±éŸ¿ã™ã‚‹å ´åˆã€ã€Œæ›´æ–°ã•ã‚ŒãŸ Nexus 端末<em></em>ã€åˆ—ã«ã¯å½±éŸ¿ã‚’å—ã‘ã‚‹ Nexus 端末ãŒè¨˜è¼‰ã•ã‚Œã¦ã„ã¾ã™ã€‚</li> - <li><strong>影響をå—ã‘ã‚‹ Nexus 端末ãŒãªã„</strong>: å•é¡Œã®å½±éŸ¿ã‚’å—ã‘ã‚‹ Nexus 端末ãŒãªã„å ´åˆã€è¡¨ã®ã€Œæ›´æ–°ã•ã‚ŒãŸ Nexus 端末<em></em>ã€åˆ—ã«ã¯ã€Œãªã—ã€ã¨è¨˜è¼‰ã•ã‚Œã¦ã„ã¾ã™ã€‚</li> + <li><strong>影響をå—ã‘ã‚‹ Nexus 端末ãŒãªã„</strong>: å•é¡Œã®å½±éŸ¿ã‚’å—ã‘ã‚‹ Android 7.0 æ載 Nexus 端末ãŒãªã„å ´åˆã€è¡¨ã®ã€Œæ›´æ–°ã•ã‚ŒãŸ Nexus 端末<em></em>ã€åˆ—ã«ã¯ã€Œãªã—ã€ã¨è¨˜è¼‰ã•ã‚Œã¦ã„ã¾ã™ã€‚</li> </ul> <p> <strong>4. 「å‚ç…§ã€åˆ—ã®é …ç›®ã¯ã©ã®ã‚ˆã†ãªæƒ…å ±ã«é–¢é€£ä»˜ã‘られã¦ã„ã¾ã™ã‹ï¼Ÿ</strong> diff --git a/ja/security/bulletin/2017-01-01.html b/ja/security/bulletin/2017-01-01.html index 0ee00ae0..66fc336e 100644 --- a/ja/security/bulletin/2017-01-01.html +++ b/ja/security/bulletin/2017-01-01.html @@ -22,25 +22,25 @@ <p><em>2017 å¹´ 1 月 3 日公開 | 2017 å¹´ 2 月 2 日更新</em></p> -<p>Android ã®ã‚»ã‚ュリティã«é–¢ã™ã‚‹å…¬é–‹æƒ…å ±ã«ã¯ã€Android æ載端末ã«å½±éŸ¿ã‚’与ãˆã‚‹ã‚»ã‚ュリティã®è„†å¼±æ€§ã®è©³ç´°ã‚’掲載ã—ã¦ã„ã¾ã™ã€‚æƒ…å ±ã®å…¬é–‹ã«ä¼´ã„ã€Google 端末ã«å¯¾ã™ã‚‹ã‚»ã‚ュリティ アップデートを無線（OTA）アップデートã§é…ä¿¡ã—ã¾ã—ãŸã€‚Google 端末ã®ãƒ•ã‚¡ãƒ¼ãƒ ウェア イメージも <a href="https://developers.google.com/android/nexus/images">Google デベãƒãƒƒãƒ‘ー サイト</a>ã§ãƒªãƒªãƒ¼ã‚¹ã—ã¦ã„ã¾ã™ã€‚2017 å¹´ 1 月 5 日以é™ã®ã‚»ã‚ュリティ パッムレベルã§ã¯ã€ä¸‹è¨˜ã®ã™ã¹ã¦ã®å•é¡Œã«å¯¾å‡¦ã—ã¦ã„ã¾ã™ã€‚端末ã®ã‚»ã‚ュリティ パッãƒãƒ¬ãƒ™ãƒ«ã‚’確èªã™ã‚‹æ–¹æ³•ã«ã¤ã„ã¦ã¯ã€<a href="https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices">Pixel 㨠Nexus ã®ã‚¢ãƒƒãƒ—デート スケジュール</a>ã‚’ã”覧ãã ã•ã„。</p> +<p>Android ã®ã‚»ã‚ュリティã«é–¢ã™ã‚‹å…¬é–‹æƒ…å ±ã«ã¯ã€Android æ載端末ã«å½±éŸ¿ã‚’与ãˆã‚‹ã‚»ã‚ュリティã®è„†å¼±æ€§ã®è©³ç´°ã‚’掲載ã—ã¦ã„ã¾ã™ã€‚æƒ…å ±ã®å…¬é–‹ã«ä¼´ã„ã€Google 端末ã«å¯¾ã™ã‚‹ã‚»ã‚ュリティ アップデートを無線（OTA）アップデートã§é…ä¿¡ã—ã¾ã—ãŸã€‚Google 端末ã®ãƒ•ã‚¡ãƒ¼ãƒ ウェア イメージも <a href="https://developers.google.com/android/nexus/images">Google デベãƒãƒƒãƒ‘ー サイト</a>ã§ãƒªãƒªãƒ¼ã‚¹ã—ã¦ã„ã¾ã™ã€‚2017 å¹´ 1 月 5 日以é™ã®ã‚»ã‚ュリティ パッãƒãƒ¬ãƒ™ãƒ«ã§ã¯ã€ä¸‹è¨˜ã®ã™ã¹ã¦ã®å•é¡Œã«å¯¾å‡¦ã—ã¦ã„ã¾ã™ã€‚端末ã®ã‚»ã‚ュリティ パッãƒãƒ¬ãƒ™ãƒ«ã‚’確èªã™ã‚‹æ–¹æ³•ã«ã¤ã„ã¦ã¯ã€<a href="https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices">Pixel 㨠Nexus ã®ã‚¢ãƒƒãƒ—デート スケジュール</a>ã‚’ã”覧ãã ã•ã„。</p> -<p>パートナーã«ã¯ã€ã“ã®å…¬é–‹æƒ…å ±ã«è¨˜è¼‰ã®å•é¡Œã«ã¤ã„㦠2016 å¹´ 12 月 5 æ—¥ã¾ã§ã«é€šçŸ¥æ¸ˆã¿ã§ã™ã€‚Android オープンソース プãƒã‚¸ã‚§ã‚¯ãƒˆï¼ˆAOSP）レãƒã‚¸ãƒˆãƒªã«ã€ä¸‹è¨˜ã®å•é¡Œã«å¯¾ã™ã‚‹ã‚½ãƒ¼ã‚¹ã‚³ãƒ¼ãƒ‰ã®ãƒ‘ッãƒã‚’リリースã—ã¦ã„ã¾ã™ã€‚AOSP 以外ã®ãƒ‘ッãƒã¸ã®ãƒªãƒ³ã‚¯ã‚‚掲載ã—ã¦ã„ã¾ã™ã€‚</p> +<p>パートナーã«ã¯ã€ã“ã®å…¬é–‹æƒ…å ±ã«è¨˜è¼‰ã®å•é¡Œã«ã¤ã„㦠2016 å¹´ 12 月 5 æ—¥ã¾ã§ã«é€šçŸ¥æ¸ˆã¿ã§ã™ã€‚Android オープンソース プãƒã‚¸ã‚§ã‚¯ãƒˆï¼ˆAOSP）ã®ãƒ¬ãƒã‚¸ãƒˆãƒªã«ã€ä¸‹è¨˜ã®å•é¡Œã«å¯¾ã™ã‚‹ã‚½ãƒ¼ã‚¹ã‚³ãƒ¼ãƒ‰ã®ãƒ‘ッãƒã‚’リリースã—ã¦ã„ã¾ã™ã€‚ã¾ãŸã€ã“ã®å…¬é–‹æƒ…å ±ã§ã¯ã€ã“れらã®ãƒ‘ッãƒã¸ã®ãƒªãƒ³ã‚¯ã«åŠ ãˆã€AOSP 以外ã®ãƒ‘ッãƒã¸ã®ãƒªãƒ³ã‚¯ã‚‚掲載ã—ã¦ã„ã¾ã™ã€‚</p> <p>下記ã®å•é¡Œã®ã†ã¡æœ€ã‚‚é‡å¤§åº¦ã®é«˜ã„ã‚‚ã®ã¯ã€å¤šæ§˜ãªæ–¹æ³•ï¼ˆãƒ¡ãƒ¼ãƒ«ã€ã‚¦ã‚§ãƒ–ã®é–²è¦§ã€MMS ãªã©ï¼‰ã«ã‚ˆã‚Šã€æ”»æ’ƒå¯¾è±¡ã®ç«¯æœ«ã§ãƒ¡ãƒ‡ã‚£ã‚¢ ファイルを処ç†ã™ã‚‹éš›ã«ãƒªãƒ¢ãƒ¼ãƒˆã§ã®ã‚³ãƒ¼ãƒ‰å®Ÿè¡ŒãŒå¯èƒ½ã«ãªã‚‹ãŠãã‚Œã®ã‚ã‚‹é‡å¤§ãªã‚»ã‚ュリティã®è„†å¼±æ€§ã§ã™ã€‚<a href="/security/overview/updates-resources.html#severity">é‡å¤§åº¦ã®è©•ä¾¡</a>ã¯ã€æ”»æ’ƒå¯¾è±¡ã®ç«¯æœ«ã§ãã®è„†å¼±æ€§ãŒæ‚ªç”¨ã•ã‚ŒãŸå ´åˆã®å½±éŸ¿ã«åŸºã¥ãã‚‚ã®ã§ã€ãƒ—ラットフォームやサービスã§ã®ãƒªã‚¹ã‚¯è»½æ¸›ç–ãŒé–‹ç™ºç›®çš„ã¾ãŸã¯ä¸æ£ãªå›žé¿ã«ã‚ˆã‚Šç„¡åŠ¹ã¨ãªã£ã¦ã„ã‚‹ã“ã¨ã‚’å‰æã¨ã—ã¦ã„ã¾ã™ã€‚</p> <p>ã“ã®æ–°ãŸã«å ±å‘Šã•ã‚ŒãŸå•é¡Œã«ã‚ˆã£ã¦å®Ÿéš›ã®ãƒ¦ãƒ¼ã‚¶ãƒ¼ç«¯æœ«ãŒä¸æ£ä½¿ç”¨ã•ã‚ŒãŸå ±å‘Šã¯ã‚ã‚Šã¾ã›ã‚“。<a href="/security/enhancements/index.html">Android ã‚»ã‚ュリティ プラットフォームã®ä¿è·</a>ã‚„ <a href="https://developer.android.com/training/safetynet/index.html">SafetyNet</a> ã®ã‚ˆã†ãªã‚µãƒ¼ãƒ“スã®ä¿è·ã«ã¤ã„ã¦è©³ã—ãã¯ã€<a href="#mitigations">Android 㨠Google サービスã§ã®ãƒªã‚¹ã‚¯è»½æ¸›ç–</a>ã‚’ã”覧ãã ã•ã„。ã“ã†ã—ãŸä¿è·ã«ã‚ˆã‚Šã€Android プラットフォームã®ã‚»ã‚ュリティãŒæ”¹å–„ã•ã‚Œã¾ã™ã€‚</p> -<p>ã”利用ã®ç«¯æœ«ã§ä¸Šè¨˜ã®æ›´æ–°ã‚’è¡Œã†ã“ã¨ã‚’ã™ã¹ã¦ã®ãƒ¦ãƒ¼ã‚¶ãƒ¼ã«ãŠã™ã™ã‚ã—ã¾ã™ã€‚</p> +<p>ã”利用ã®ç«¯æœ«ã«ã“ã®ã‚¢ãƒƒãƒ—デートをé©ç”¨ã™ã‚‹ã“ã¨ã‚’ã™ã¹ã¦ã®ãƒ¦ãƒ¼ã‚¶ãƒ¼ã«ãŠã™ã™ã‚ã—ã¾ã™ã€‚</p> <h2 id="announcements">ãŠçŸ¥ã‚‰ã›</h2> <ul> <li>ã“ã®å…¬é–‹æƒ…å ±ã§ã¯ã€2 ã¤ã®ã‚»ã‚ュリティ パッãƒãƒ¬ãƒ™ãƒ«æ–‡å—列を定義ã—ã¦ã„ã¾ã™ã€‚ã“ã‚Œã¯ã€ã™ã¹ã¦ã® Android æ載端末ã§åŒæ§˜ã®å•é¡ŒãŒç™ºç”Ÿã™ã‚‹ä¸€éƒ¨ã®è„†å¼±æ€§ã‚’サブセットã¨ã—ã€Android パートナーãŒè¿…速ã‹ã¤æŸ”軟ã«ä¿®æ£ã§ãるよã†ã«ã™ã‚‹ãŸã‚ã§ã™ã€‚詳ã—ãã¯ã€<a href="#common-questions-and-answers">一般的ãªè³ªå•ã¨å›žç”</a>ã‚’ã”覧ãã ã•ã„。 <ul> - <li><strong>2017-01-01</strong>: 部分的ã«å¯¾å‡¦ã—ãŸã‚»ã‚ュリティ パッãƒãƒ¬ãƒ™ãƒ«æ–‡å—列。ã“ã®ã‚»ã‚ュリティ パッムレベル文å—列ã¯ã€2017-01-01（ãŠã‚ˆã³ãれ以å‰ã®ã™ã¹ã¦ã®ã‚»ã‚ュリティ パッムレベル文å—列）ã«é–¢é€£ã™ã‚‹ã™ã¹ã¦ã®å•é¡Œã«å¯¾å‡¦ã—ã¦ã„ã‚‹ã“ã¨ã‚’示ã—ã¾ã™ã€‚</li> - <li><strong>2017-01-05</strong>: 完全ã«å¯¾å‡¦ã—ãŸã‚»ã‚ュリティ パッãƒãƒ¬ãƒ™ãƒ«æ–‡å—列。ã“ã®ã‚»ã‚ュリティ パッムレベル文å—列ã¯ã€2017-01-01 㨠2017-01-05（ãŠã‚ˆã³ãれ以å‰ã®ã™ã¹ã¦ã®ã‚»ã‚ュリティ パッムレベル文å—列）ã«é–¢é€£ã™ã‚‹ã™ã¹ã¦ã®å•é¡Œã«å¯¾å‡¦ã—ã¦ã„ã‚‹ã“ã¨ã‚’示ã—ã¾ã™ã€‚</li> + <li><strong>2017-01-01</strong>: 部分的ã«å¯¾å‡¦ã—ãŸã‚»ã‚ュリティ パッãƒãƒ¬ãƒ™ãƒ«æ–‡å—列。ã“ã®ã‚»ã‚ュリティ パッãƒãƒ¬ãƒ™ãƒ«æ–‡å—列ã¯ã€2017-01-01（ãŠã‚ˆã³ãれ以å‰ã®ã™ã¹ã¦ã®ã‚»ã‚ュリティ パッãƒãƒ¬ãƒ™ãƒ«æ–‡å—列）ã«é–¢é€£ã™ã‚‹ã™ã¹ã¦ã®å•é¡Œã«å¯¾å‡¦ã—ã¦ã„ã‚‹ã“ã¨ã‚’示ã—ã¾ã™ã€‚</li> + <li><strong>2017-01-05</strong>: 完全ã«å¯¾å‡¦ã—ãŸã‚»ã‚ュリティ パッãƒãƒ¬ãƒ™ãƒ«æ–‡å—列。ã“ã®ã‚»ã‚ュリティ パッãƒãƒ¬ãƒ™ãƒ«æ–‡å—列ã¯ã€2017-01-01 㨠2017-01-05（ãŠã‚ˆã³ãれ以å‰ã®ã™ã¹ã¦ã®ã‚»ã‚ュリティ パッãƒãƒ¬ãƒ™ãƒ«æ–‡å—列）ã«é–¢é€£ã™ã‚‹ã™ã¹ã¦ã®å•é¡Œã«å¯¾å‡¦ã—ã¦ã„ã‚‹ã“ã¨ã‚’示ã—ã¾ã™ã€‚</li> </ul> </li> - <li>サãƒãƒ¼ãƒˆå¯¾è±¡ã® Google 端末ã«ã¯ã€2017 å¹´ 1 月 5 æ—¥ã®ã‚»ã‚ュリティ パッムレベルã®ã‚¢ãƒƒãƒ—デート 1 件㌠OTA ã§é…ä¿¡ã•ã‚Œã¾ã™ã€‚</li> + <li>サãƒãƒ¼ãƒˆå¯¾è±¡ã® Google 端末ã«ã¯ã€2017 å¹´ 1 月 5 æ—¥ã®ã‚»ã‚ュリティ パッãƒãƒ¬ãƒ™ãƒ«ã®ã‚¢ãƒƒãƒ—デート 1 件㌠OTA ã§é…ä¿¡ã•ã‚Œã¾ã™ã€‚</li> </ul> <h2 id="security-vulnerability-summary">ã‚»ã‚ュリティã®è„†å¼±æ€§ã®æ¦‚è¦</h2> <p>下記ã®è¡¨ã«ã€ã‚»ã‚ュリティã®è„†å¼±æ€§ã€ãã®å…±é€šè„†å¼±æ€§è˜åˆ¥å（CVE）ã€é‡å¤§åº¦ã®åˆ¤å®šã€Google 端末ã¸ã®å½±éŸ¿ãŒã‚ã‚‹ã‹ã©ã†ã‹ã®ä¸€è¦§ã‚’示ã—ã¾ã™ã€‚<a href="/security/overview/updates-resources.html#severity">é‡å¤§åº¦ã®è©•ä¾¡</a>ã¯ã€æ”»æ’ƒå¯¾è±¡ã®ç«¯æœ«ã§ãã®è„†å¼±æ€§ãŒæ‚ªç”¨ã•ã‚ŒãŸå ´åˆã®å½±éŸ¿ã«åŸºã¥ãã‚‚ã®ã§ã€ãƒ—ラットフォームやサービスã§ã®ãƒªã‚¹ã‚¯è»½æ¸›ç–ãŒé–‹ç™ºç›®çš„ã¾ãŸã¯ä¸æ£ãªå›žé¿ã«ã‚ˆã‚Šç„¡åŠ¹ã¨ãªã£ã¦ã„ã‚‹ã“ã¨ã‚’å‰æã¨ã—ã¦ã„ã¾ã™ã€‚</p> @@ -65,7 +65,7 @@ <li>Qihoo 360 Technology Co. Ltd. IceSword Lab ã® Gengjia Chen（<a href="https://twitter.com/chengjia4574">@chengjia4574</a>）ã€<a href="http://weibo.com/jfpan">pjf</a>: CVE-2016-8464</li> <li>Google WebM Team: CVE-2017-0393</li> <li><a href="http://www.360.com">Qihoo 360 Technology Co. Ltd.</a> Alpha Team ã® Guang Gong（龚广）（<a href="http://twitter.com/oldfresher">@oldfresher</a>）: CVE-2017-0387</li> - <li>Alpha Teamã€Qihoo 360 Technology Co. Ltd. ã® Hao Chen 㨠Guang Gong: CVE-2016-8415ã€CVE-2016-8454ã€CVE-2016-8455ã€CVE-2016-8456ã€CVE-2016-8457ã€CVE-2016-8465</li> + <li>Qihoo 360 Technology Co. Ltd. Alpha Team ã® Hao Chenã€Guang Gong: CVE-2016-8415ã€CVE-2016-8454ã€CVE-2016-8455ã€CVE-2016-8456ã€CVE-2016-8457ã€CVE-2016-8465</li> <li>Qihoo 360 IceSword Lab ã® Jianqiang Zhao（<a href="https://twitter.com/jianqiangzhao">@jianqiangzhao</a>）ã€<a href="http://weibo.com/jfpan">pjf</a>: CVE-2016-8475</li> <li>Jon Sawyer（<a href="http://twitter.com/jcase">@jcase</a>）ã€Sean Beaupre（<a href="https://twitter.com/firewaterdevs">@firewaterdevs</a>）: CVE-2016-8462</li> <li>Jon Sawyer（<a href="http://twitter.com/jcase">@jcase</a>）ã€Sean Beaupre（<a href="https://twitter.com/firewaterdevs">@firewaterdevs</a>）ã€Ben Actis（<a href="https://twitter.com/ben_ra">@Ben_RA</a>）: CVE-2016-8461</li> @@ -96,7 +96,7 @@ <li>Google ã® Zubin Mithra</li> </ul> -<h2 id="2017-01-01-details">ã‚»ã‚ュリティ パッムレベル 2017-01-01 ã®è„†å¼±æ€§ã®è©³ç´°</h2> +<h2 id="2017-01-01-details">ã‚»ã‚ュリティ パッãƒãƒ¬ãƒ™ãƒ« 2017-01-01 ã®è„†å¼±æ€§ã®è©³ç´°</h2> <p> パッãƒãƒ¬ãƒ™ãƒ« 2017-01-01 ã«è©²å½“ã™ã‚‹ã‚»ã‚ュリティ脆弱性ã®å„é …ç›®ã«ã¤ã„ã¦ã€ä¸‹è¨˜ã«è©³ç´°ã‚’説明ã—ã¾ã™ã€‚å•é¡Œã®å†…容ã¨ãã®é‡å¤§åº¦ã®æ ¹æ‹ ã«ã¤ã„ã¦èª¬æ˜Žã—ã€CVEã€é–¢é€£ã™ã‚‹å‚照先ã€é‡å¤§åº¦ã€æ›´æ–°å¯¾è±¡ã® Google 端末ã€æ›´æ–°å¯¾è±¡ã® AOSP ãƒãƒ¼ã‚¸ãƒ§ãƒ³ï¼ˆè©²å½“ã™ã‚‹å ´åˆï¼‰ã€å ±å‘Šæ—¥ã‚’表ã«ã¾ã¨ã‚ã¦ã„ã¾ã™ã€‚該当ã™ã‚‹å ´åˆã¯ã€ãƒã‚° ID ã®æ¬„ã«ã€ãã®å•é¡Œã«å¯¾å‡¦ã—ãŸä¸€èˆ¬å…¬é–‹ã•ã‚Œã¦ã„る変更（AOSP ã®å¤‰æ›´ã®ä¸€è¦§ãªã©ï¼‰ã¸ã®ãƒªãƒ³ã‚¯ãŒã‚ã‚Šã¾ã™ã€‚複数ã®å¤‰æ›´ãŒåŒã˜ãƒã‚°ã«é–¢ä¿‚ã™ã‚‹å ´åˆã¯ã€ãƒã‚° ID ã®å¾Œã«ç¶šã番å·ã§ã€è¿½åŠ ã®å‚照先ã¸ã®ãƒªãƒ³ã‚¯ã‚’示ã—ã¾ã™ã€‚</p> @@ -583,7 +583,7 @@ Framesequence ライブラリã«ãƒªãƒ¢ãƒ¼ãƒˆã‚³ãƒ¼ãƒ‰å®Ÿè¡Œã®è„†å¼±æ€§ãŒã‚ã‚‹ </tr> </tbody></table> -<h2 id="2017-01-05-details">ã‚»ã‚ュリティ パッムレベル 2017-01-05 ã®è„†å¼±æ€§ã®è©³ç´°</h2> +<h2 id="2017-01-05-details">ã‚»ã‚ュリティ パッãƒãƒ¬ãƒ™ãƒ« 2017-01-05 ã®è„†å¼±æ€§ã®è©³ç´°</h2> <p> パッãƒãƒ¬ãƒ™ãƒ« 2017-01-05 ã«è©²å½“ã™ã‚‹ã‚»ã‚ュリティ脆弱性ã®å„é …ç›®ã«ã¤ã„ã¦ã€ä¸‹è¨˜ã«è©³ç´°ã‚’説明ã—ã¾ã™ã€‚ å•é¡Œã®å†…容ã¨ãã®é‡å¤§åº¦ã®æ ¹æ‹ ã«ã¤ã„ã¦èª¬æ˜Žã—ã€CVEã€é–¢é€£ã™ã‚‹å‚照先ã€é‡å¤§åº¦ã€æ›´æ–°å¯¾è±¡ã® Google 端末ã€æ›´æ–°å¯¾è±¡ã® AOSP ãƒãƒ¼ã‚¸ãƒ§ãƒ³ï¼ˆè©²å½“ã™ã‚‹å ´åˆï¼‰ã€å ±å‘Šæ—¥ã‚’表ã«ã¾ã¨ã‚ã¦ã„ã¾ã™ã€‚該当ã™ã‚‹å ´åˆã¯ã€ãƒã‚° ID ã®æ¬„ã«ã€ãã®å•é¡Œã«å¯¾å‡¦ã—ãŸä¸€èˆ¬å…¬é–‹ã•ã‚Œã¦ã„る変更（AOSP ã®å¤‰æ›´ã®ä¸€è¦§ãªã©ï¼‰ã¸ã®ãƒªãƒ³ã‚¯ãŒã‚ã‚Šã¾ã™ã€‚複数ã®å¤‰æ›´ãŒåŒã˜ãƒã‚°ã«é–¢ä¿‚ã™ã‚‹å ´åˆã¯ã€ãƒã‚° ID ã®å¾Œã«ç¶šã番å·ã§ã€è¿½åŠ ã®å‚照先ã¸ã®ãƒªãƒ³ã‚¯ã‚’示ã—ã¾ã™ã€‚</p> @@ -1932,15 +1932,15 @@ Broadcom Wi-Fi ドライãƒã«æ¨©é™æ˜‡æ ¼ã®è„†å¼±æ€§ãŒã‚ã‚‹ãŸã‚ã€æ‚ªæ„ã </tbody></table> <h2 id="common-questions-and-answers">一般的ãªè³ªå•ã¨å›žç”</h2> -<p>上記ã®å…¬é–‹æƒ…å ±ã«å¯¾ã™ã‚‹ä¸€èˆ¬çš„ãªè³ªå•ã«ã¤ã„ã¦ã€ä»¥ä¸‹ã§å›žç”ã—ã¾ã™ã€‚</p> +<p>上記ã®å…¬é–‹æƒ…å ±ã«å¯¾ã™ã‚‹ä¸€èˆ¬çš„ãªè³ªå•ã«ã¤ã„ã¦ã®å›žç”ã¯ä»¥ä¸‹ã®ã¨ãŠã‚Šã§ã™ã€‚</p> <p><strong>1. 上記ã®å•é¡Œã«å¯¾å‡¦ã™ã‚‹ã‚ˆã†ã«ç«¯æœ«ãŒæ›´æ–°ã•ã‚Œã¦ã„ã‚‹ã‹ã©ã†ã‹ã‚’確ã‹ã‚ã‚‹ã«ã¯ã€ã©ã†ã™ã‚Œã°ã‚ˆã„ã§ã™ã‹ï¼Ÿ </strong></p> <p>端末ã®ã‚»ã‚ュリティ パッãƒãƒ¬ãƒ™ãƒ«ã‚’確èªã™ã‚‹æ–¹æ³•ã«ã¤ã„ã¦ã¯ã€<a href="https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices">Pixel ãŠã‚ˆã³ Nexus ã®ã‚¢ãƒƒãƒ—デート スケジュール</a>ã«è¨˜è¼‰ã•ã‚Œã¦ã„ã‚‹æ‰‹é †ã‚’ã”覧ãã ã•ã„。</p> <ul> - <li>ã‚»ã‚ュリティ パッムレベル 2017-01-01 以é™ã§ã¯ã€ã‚»ã‚ュリティ パッムレベル 2017-01-01 ã«é–¢é€£ã™ã‚‹ã™ã¹ã¦ã®å•é¡Œã«å¯¾å‡¦ã—ã¦ã„ã¾ã™ã€‚</li> - <li>ã‚»ã‚ュリティ パッムレベル 2017-01-05 以é™ã§ã¯ã€ã‚»ã‚ュリティ パッムレベル 2017-01-05ã€ãŠã‚ˆã³ãれ以å‰ã®ã™ã¹ã¦ã®ãƒ‘ッãƒãƒ¬ãƒ™ãƒ«ã«é–¢é€£ã™ã‚‹ã™ã¹ã¦ã®å•é¡Œã«å¯¾å‡¦ã—ã¦ã„ã¾ã™ã€‚</li> + <li>ã‚»ã‚ュリティ パッãƒãƒ¬ãƒ™ãƒ« 2017-01-01 以é™ã§ã¯ã€ã‚»ã‚ュリティ パッãƒãƒ¬ãƒ™ãƒ« 2017-01-01 ã«é–¢é€£ã™ã‚‹ã™ã¹ã¦ã®å•é¡Œã«å¯¾å‡¦ã—ã¦ã„ã¾ã™ã€‚</li> + <li>ã‚»ã‚ュリティ パッãƒãƒ¬ãƒ™ãƒ« 2017-01-05 以é™ã§ã¯ã€ã‚»ã‚ュリティ パッãƒãƒ¬ãƒ™ãƒ« 2017-01-05ã€ãŠã‚ˆã³ãれ以å‰ã®ã™ã¹ã¦ã®ãƒ‘ッãƒãƒ¬ãƒ™ãƒ«ã«é–¢é€£ã™ã‚‹ã™ã¹ã¦ã®å•é¡Œã«å¯¾å‡¦ã—ã¦ã„ã¾ã™ã€‚</li> </ul> <p>ã“ã®ã‚¢ãƒƒãƒ—デートを組ã¿è¾¼ã‚“ã 端末メーカーã¯ã€ãƒ‘ッãƒãƒ¬ãƒ™ãƒ«æ–‡å—列を以下ã«è¨å®šã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚</p> <ul> @@ -1949,16 +1949,16 @@ Broadcom Wi-Fi ドライãƒã«æ¨©é™æ˜‡æ ¼ã®è„†å¼±æ€§ãŒã‚ã‚‹ãŸã‚ã€æ‚ªæ„ã </ul> <p><strong>2. ã“ã®å…¬é–‹æƒ…å ±ã« 2 ã¤ã®ã‚»ã‚ュリティ パッãƒãƒ¬ãƒ™ãƒ«ãŒã‚ã‚‹ã®ã¯ãªãœã§ã™ã‹ï¼Ÿ</strong></p> -<p>ã“ã®å…¬é–‹æƒ…å ±ã§ã¯ã€2 ã¤ã®ã‚»ã‚ュリティ パッãƒãƒ¬ãƒ™ãƒ«ã‚’定義ã—ã¦ã„ã¾ã™ã€‚ã“ã‚Œã¯ã€ã™ã¹ã¦ã® Android æ載端末ã§åŒæ§˜ã®å•é¡ŒãŒç™ºç”Ÿã™ã‚‹ä¸€éƒ¨ã®è„†å¼±æ€§ã‚’サブセットã¨ã—ã€Android パートナーãŒè¿…速ã‹ã¤æŸ”軟ã«ä¿®æ£ã§ãるよã†ã«ã™ã‚‹ãŸã‚ã§ã™ã€‚Android パートナーã«ã¯ã€ã“ã®å…¬é–‹æƒ…å ±ã«æŽ²è¼‰ã•ã‚Œã¦ã„ã‚‹å•é¡Œã‚’ã™ã¹ã¦ä¿®æ£ã—ã€æœ€æ–°ã®ã‚»ã‚ュリティ パッムレベルを使用ã™ã‚‹ã“ã¨ãŒæŽ¨å¥¨ã•ã‚Œã¦ã„ã¾ã™ã€‚</p> +<p>ã“ã®å…¬é–‹æƒ…å ±ã§ã¯ã€2 ã¤ã®ã‚»ã‚ュリティ パッãƒãƒ¬ãƒ™ãƒ«ã‚’定義ã—ã¦ã„ã¾ã™ã€‚ã“ã‚Œã¯ã€ã™ã¹ã¦ã® Android æ載端末ã§åŒæ§˜ã®å•é¡ŒãŒç™ºç”Ÿã™ã‚‹ä¸€éƒ¨ã®è„†å¼±æ€§ã‚’サブセットã¨ã—ã€Android パートナーãŒè¿…速ã‹ã¤æŸ”軟ã«ä¿®æ£ã§ãるよã†ã«ã™ã‚‹ãŸã‚ã§ã™ã€‚Android パートナーã«ã¯ã€ã“ã®å…¬é–‹æƒ…å ±ã«æŽ²è¼‰ã•ã‚Œã¦ã„ã‚‹å•é¡Œã‚’ã™ã¹ã¦ä¿®æ£ã—ã€æœ€æ–°ã®ã‚»ã‚ュリティ パッãƒãƒ¬ãƒ™ãƒ«ã‚’使用ã™ã‚‹ã“ã¨ãŒæŽ¨å¥¨ã•ã‚Œã¦ã„ã¾ã™ã€‚</p> <ul> - <li>2017 å¹´ 1 月 1 æ—¥ã®ã‚»ã‚ュリティ パッムレベルを使用ã™ã‚‹ç«¯æœ«ã«ã¯ã€ãã®ã‚»ã‚ュリティ パッムレベルã«é–¢é€£ã™ã‚‹ã™ã¹ã¦ã®å•é¡Œã¨ã€ãれ以å‰ã®ã‚»ã‚ュリティã«é–¢ã™ã‚‹å…¬é–‹æƒ…å ±ã§å ±å‘Šã•ã‚ŒãŸã™ã¹ã¦ã®å•é¡Œã®ä¿®æ£ã‚’組ã¿è¾¼ã‚€å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚</li> - <li>2017 å¹´ 1 月 5 日以é™ã®ã‚»ã‚ュリティ パッムレベルを使用ã™ã‚‹ç«¯æœ«ã«ã¯ã€ä»Šå›žï¼ˆãŠã‚ˆã³ãれ以å‰ï¼‰ã®ã‚»ã‚ュリティã«é–¢ã™ã‚‹å…¬é–‹æƒ…å ±ã«æŽ²è¼‰ã•ã‚ŒãŸã€è©²å½“ã™ã‚‹ã™ã¹ã¦ã®ãƒ‘ッãƒã‚’組ã¿è¾¼ã‚€å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚</li> + <li>2017 å¹´ 1 月 1 æ—¥ã®ã‚»ã‚ュリティ パッãƒãƒ¬ãƒ™ãƒ«ã‚’使用ã™ã‚‹ç«¯æœ«ã«ã¯ã€ãã®ã‚»ã‚ュリティ パッãƒãƒ¬ãƒ™ãƒ«ã«é–¢é€£ã™ã‚‹ã™ã¹ã¦ã®å•é¡Œã¨ã€ãれ以å‰ã®ã‚»ã‚ュリティã«é–¢ã™ã‚‹å…¬é–‹æƒ…å ±ã§å ±å‘Šã•ã‚ŒãŸã™ã¹ã¦ã®å•é¡Œã®ä¿®æ£ã‚’組ã¿è¾¼ã‚€å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚</li> + <li>2017 å¹´ 1 月 5 日以é™ã®ã‚»ã‚ュリティ パッãƒãƒ¬ãƒ™ãƒ«ã‚’使用ã™ã‚‹ç«¯æœ«ã«ã¯ã€ä»Šå›žï¼ˆãŠã‚ˆã³ãれ以å‰ï¼‰ã®ã‚»ã‚ュリティã«é–¢ã™ã‚‹å…¬é–‹æƒ…å ±ã«æŽ²è¼‰ã•ã‚ŒãŸã€è©²å½“ã™ã‚‹ã™ã¹ã¦ã®ãƒ‘ッãƒã‚’組ã¿è¾¼ã‚€å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚</li> </ul> <p>パートナーã«ã¯ã€å¯¾å‡¦ã™ã‚‹ã™ã¹ã¦ã®å•é¡Œã®ä¿®æ£ã‚’ 1 ã¤ã®ã‚¢ãƒƒãƒ—デートã«ã¾ã¨ã‚ã¦æä¾›ã™ã‚‹ã“ã¨ãŒæŽ¨å¥¨ã•ã‚Œã¦ã„ã¾ã™ã€‚</p> <p><strong>3. å„å•é¡Œã®å½±éŸ¿ã‚’å—ã‘ã‚‹ Google 端末を判æ–ã™ã‚‹ã«ã¯ã©ã†ã™ã‚Œã°ã‚ˆã„ã§ã™ã‹ï¼Ÿ</strong></p> -<p><a href="#2017-01-01-details">2017-05-01</a> 㨠<a href="#2017-01-05-details">2017-05-05</a> ã®ã‚»ã‚ュリティã®è„†å¼±æ€§ã®è©³ç´°ã«é–¢ã™ã‚‹ã‚»ã‚¯ã‚·ãƒ§ãƒ³ã§ã€å„表ä¸ã®ã€Œæ›´æ–°å¯¾è±¡ã® Google 端末<em></em>ã€åˆ—ã«ã€ãã®å•é¡Œã®å½±éŸ¿ã‚’å—ã‘ã‚‹ã€æ›´æ–°å¯¾è±¡ã® Google 端末ã®ç¨®é¡žã‚’記載ã—ã¦ã„ã¾ã™ã€‚ã“ã®åˆ—ã«ã¯æ¬¡ã®ã„ãšã‚Œã‹ãŒè¡¨ç¤ºã•ã‚Œã¦ã„ã¾ã™ã€‚</p> +<p><a href="#2017-01-01-details">2017-01-01</a> 㨠<a href="#2017-01-05-details">2017-01-05</a> ã®ã‚»ã‚ュリティã®è„†å¼±æ€§ã®è©³ç´°ã«é–¢ã™ã‚‹ã‚»ã‚¯ã‚·ãƒ§ãƒ³ã§ã€å„表ä¸ã®ã€Œæ›´æ–°å¯¾è±¡ã® Google 端末<em></em>ã€åˆ—ã«ã€ãã®å•é¡Œã®å½±éŸ¿ã‚’å—ã‘ã‚‹ã€æ›´æ–°å¯¾è±¡ã® Google 端末ã®ç¨®é¡žã‚’記載ã—ã¦ã„ã¾ã™ã€‚ã“ã®åˆ—ã«ã¯æ¬¡ã®ã„ãšã‚Œã‹ãŒè¡¨ç¤ºã•ã‚Œã¦ã„ã¾ã™ã€‚</p> <ul> <li><strong>ã™ã¹ã¦ã® Google 端末</strong>: å•é¡ŒãŒã™ã¹ã¦ã®ç«¯æœ«ã¨ Pixel 端末ã«å½±éŸ¿ã‚’与ãˆã‚‹å ´åˆã€è¡¨ã®ã€Œæ›´æ–°å¯¾è±¡ã® Google 端末<em></em>ã€åˆ—ã«ã¯ã€Œã™ã¹ã¦ã€ã¨è¨˜è¼‰ã•ã‚Œã¦ã„ã¾ã™ã€‚「ã™ã¹ã¦ã€ã«ã¯<a href="https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices">サãƒãƒ¼ãƒˆå¯¾è±¡ã®ç«¯æœ«</a>（Nexus 5Xã€Nexus 6ã€Nexus 6Pã€Nexus 9ã€Android Oneã€Nexus Playerã€Pixel Cã€Pixelã€Pixel XL）ãŒå«ã¾ã‚Œã¾ã™ã€‚</li> <li><strong>一部㮠Google 端末</strong>: å•é¡ŒãŒä¸€éƒ¨ã® Google 端末ã®ã¿ã«å½±éŸ¿ã™ã‚‹å ´åˆã€ã€Œæ›´æ–°å¯¾è±¡ã® Google 端末<em></em>ã€åˆ—ã«ã¯å½±éŸ¿ã‚’å—ã‘ã‚‹ Google 端末ãŒè¨˜è¼‰ã•ã‚Œã¦ã„ã¾ã™ã€‚</li> diff --git a/ja/security/bulletin/2017-03-01.html b/ja/security/bulletin/2017-03-01.html index 6fd440ad..c48f1260 100644 --- a/ja/security/bulletin/2017-03-01.html +++ b/ja/security/bulletin/2017-03-01.html @@ -24,8 +24,8 @@ <p>Android ã®ã‚»ã‚ュリティã«é–¢ã™ã‚‹å…¬é–‹æƒ…å ±ã«ã¯ã€Android æ載端末ã«å½±éŸ¿ã‚’与ãˆã‚‹ã‚»ã‚ュリティã®è„†å¼±æ€§ã®è©³ç´°ã‚’掲載ã—ã¦ã„ã¾ã™ã€‚æƒ…å ±ã®å…¬é–‹ã«ä¼´ã„ã€Google 端末ã«å¯¾ã™ã‚‹ã‚»ã‚ュリティ アップデートを無線（OTA）アップデートã§é…ä¿¡ã—ã¾ã—ãŸã€‚Google 端末ã®ãƒ•ã‚¡ãƒ¼ãƒ ウェア イメージも <a href="https://developers.google.com/android/nexus/images">Google デベãƒãƒƒãƒ‘ー サイト</a>ã§ãƒªãƒªãƒ¼ã‚¹ã—ã¦ã„ã¾ã™ã€‚2017 å¹´ 3 月 5 日以é™ã®ã‚»ã‚ュリティ パッムレベルã§ã¯ã€ä¸‹è¨˜ã®ã™ã¹ã¦ã®å•é¡Œã«å¯¾å‡¦ã—ã¦ã„ã¾ã™ã€‚端末ã®ã‚»ã‚ュリティ パッãƒãƒ¬ãƒ™ãƒ«ã‚’確èªã™ã‚‹æ–¹æ³•ã«ã¤ã„ã¦ã¯ã€<a href="https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices">Pixel 㨠Nexus ã®ã‚¢ãƒƒãƒ—デート スケジュール</a>ã‚’ã”覧ãã ã•ã„。</p> <p>パートナーã«ã¯ã€ã“ã®å…¬é–‹æƒ…å ±ã«è¨˜è¼‰ã®å•é¡Œã«ã¤ã„㦠2017 å¹´ 2 月 6 æ—¥ã¾ã§ã«é€šçŸ¥æ¸ˆã¿ã§ã™ã€‚Android オープンソース プãƒã‚¸ã‚§ã‚¯ãƒˆï¼ˆAOSP）レãƒã‚¸ãƒˆãƒªã«ã€ä¸‹è¨˜ã®å•é¡Œã«å¯¾ã™ã‚‹ã‚½ãƒ¼ã‚¹ã‚³ãƒ¼ãƒ‰ã®ãƒ‘ッãƒã‚’リリースã—ã¦ã„ã¾ã™ã€‚AOSP 以外ã®ãƒ‘ッãƒã¸ã®ãƒªãƒ³ã‚¯ã‚‚掲載ã—ã¦ã„ã¾ã™ã€‚</p> <p>下記ã®å•é¡Œã®ã†ã¡æœ€ã‚‚é‡å¤§åº¦ã®é«˜ã„ã‚‚ã®ã¯ã€å¤šæ§˜ãªæ–¹æ³•ï¼ˆãƒ¡ãƒ¼ãƒ«ã€ã‚¦ã‚§ãƒ–ã®é–²è¦§ã€MMS ãªã©ï¼‰ã«ã‚ˆã‚Šã€æ”»æ’ƒå¯¾è±¡ã®ç«¯æœ«ã§ãƒ¡ãƒ‡ã‚£ã‚¢ ファイルを処ç†ã™ã‚‹éš›ã«ãƒªãƒ¢ãƒ¼ãƒˆã§ã®ã‚³ãƒ¼ãƒ‰å®Ÿè¡ŒãŒå¯èƒ½ã«ãªã‚‹ãŠãã‚Œã®ã‚ã‚‹é‡å¤§ãªã‚»ã‚ュリティã®è„†å¼±æ€§ã§ã™ã€‚<a href="/security/overview/updates-resources.html#severity">é‡å¤§åº¦ã®è©•ä¾¡</a>ã¯ã€æ”»æ’ƒå¯¾è±¡ã®ç«¯æœ«ã§ãã®è„†å¼±æ€§ãŒæ‚ªç”¨ã•ã‚ŒãŸå ´åˆã®å½±éŸ¿ã«åŸºã¥ãã‚‚ã®ã§ã€ãƒ—ラットフォームやサービスã§ã®ãƒªã‚¹ã‚¯è»½æ¸›ç–ãŒé–‹ç™ºç›®çš„ã¾ãŸã¯ä¸æ£ãªå›žé¿ã«ã‚ˆã‚Šç„¡åŠ¹ã¨ãªã£ã¦ã„ã‚‹ã“ã¨ã‚’å‰æã¨ã—ã¦ã„ã¾ã™ã€‚</p> -<p>ã“ã®æ–°ãŸã«å ±å‘Šã•ã‚ŒãŸå•é¡Œã«ã‚ˆã£ã¦å®Ÿéš›ã®ãƒ¦ãƒ¼ã‚¶ãƒ¼ç«¯æœ«ãŒä¸æ£ä½¿ç”¨ã•ã‚ŒãŸå ±å‘Šã¯ã‚ã‚Šã¾ã›ã‚“。<a href="#mitigations">Android ã‚»ã‚ュリティ プラットフォームã®ä¿è·</a>ã‚„ <a href="/security/enhancements/index.html">SafetyNet</a> ã®ã‚ˆã†ãªã‚µãƒ¼ãƒ“スã®ä¿è·ã«ã¤ã„ã¦è©³ã—ãã¯ã€<a href="https://developer.android.com/training/safetynet/index.html">Android 㨠Google サービスã§ã®ãƒªã‚¹ã‚¯è»½æ¸›ç–</a>ã‚’ã”覧ãã ã•ã„。ã“ã†ã—ãŸä¿è·ã«ã‚ˆã‚Šã€Android プラットフォームã®ã‚»ã‚ュリティãŒæ”¹å–„ã•ã‚Œã¾ã™ã€‚</p> -<p>ã”利用ã®ç«¯æœ«ã§ä¸Šè¨˜ã®æ›´æ–°ã‚’è¡Œã†ã“ã¨ã‚’ã™ã¹ã¦ã®ãƒ¦ãƒ¼ã‚¶ãƒ¼ã«ãŠã™ã™ã‚ã—ã¾ã™ã€‚</p> +<p>ã“ã®æ–°ãŸã«å ±å‘Šã•ã‚ŒãŸå•é¡Œã«ã‚ˆã£ã¦å®Ÿéš›ã®ãƒ¦ãƒ¼ã‚¶ãƒ¼ç«¯æœ«ãŒä¸æ£ä½¿ç”¨ã•ã‚ŒãŸå ±å‘Šã¯ã‚ã‚Šã¾ã›ã‚“。<a href="/security/enhancements/index.html">Android ã‚»ã‚ュリティ プラットフォームã®ä¿è·</a>ã‚„ <a href="https://developer.android.com/training/safetynet/index.html">SafetyNet</a> ã®ã‚ˆã†ãªã‚µãƒ¼ãƒ“スã®ä¿è·ã«ã¤ã„ã¦è©³ã—ãã¯ã€<a href="#mitigations">Android 㨠Google サービスã§ã®ãƒªã‚¹ã‚¯è»½æ¸›ç–</a>ã‚’ã”覧ãã ã•ã„。ã“ã†ã—ãŸä¿è·ã«ã‚ˆã‚Šã€Android プラットフォームã®ã‚»ã‚ュリティãŒæ”¹å–„ã•ã‚Œã¾ã™ã€‚</p> +<p>ã”利用ã®ç«¯æœ«ã«ã“ã®ã‚¢ãƒƒãƒ—デートをé©ç”¨ã™ã‚‹ã“ã¨ã‚’ã™ã¹ã¦ã®ãƒ¦ãƒ¼ã‚¶ãƒ¼ã«ãŠã™ã™ã‚ã—ã¾ã™ã€‚</p> <h2 id="announcements">ãŠçŸ¥ã‚‰ã›</h2> <ul> <li>ã“ã®å…¬é–‹æƒ…å ±ã§ã¯ã€2 ã¤ã®ã‚»ã‚ュリティ パッムレベル文å—列を定義ã—ã¦ã„ã¾ã™ã€‚ã“ã‚Œã¯ã€ã™ã¹ã¦ã® Android æ載端末ã§åŒæ§˜ã®å•é¡ŒãŒç™ºç”Ÿã™ã‚‹ä¸€éƒ¨ã®è„†å¼±æ€§ã‚’サブセットã¨ã—ã€Android パートナーãŒè¿…速ã‹ã¤æŸ”軟ã«ä¿®æ£ã§ãるよã†ã«ã™ã‚‹ãŸã‚ã§ã™ã€‚詳ã—ãã¯ã€<a href="#common-questions-and-answers">一般的ãªè³ªå•ã¨å›žç”</a>ã‚’ã”覧ãã ã•ã„。<ul> @@ -45,7 +45,7 @@ <h2 id="acknowledgements">è¬è¾ž</h2> <p>調査ã«ã”å”力ãã ã•ã£ãŸä¸‹è¨˜ã®çš†æ§˜æ–¹ã«æ„Ÿè¬ã„ãŸã—ã¾ã™ï¼ˆæ•¬ç§°ç•¥ï¼‰ã€‚</p> <ul> -<li>Google Dynamic Tools ãƒãƒ¼ãƒ ã® Alexander Potapenko: CVE-2017-0537</li><li>Alibaba Mobile Security Group ã® Baozeng Dingã€Chengming Yangã€Peng Xiaoã€Yang Song: CVE-2017-0506</li><li>Alibaba Mobile Security Group ã® Baozeng Dingã€Ning Youã€Chengming Yangã€Peng Xiaoã€Yang Song: CVE-2017-0463</li><li>Android Security ã® Billy Lau: CVE-2017-0335ã€CVE-2017-0336ã€CVE-2017-0338ã€CVE-2017-0460</li><li><a href="mailto:derrek.haxx@gmail.com">derrek</a>（<a href="https://twitter.com/derrekr6">@derrekr6</a>）: CVE-2016-8413ã€CVE-2016-8477ã€CVE-2017-0531</li><li><a href="mailto:derrek.haxx@gmail.com">derrek</a>（<a href="https://twitter.com/derrekr6">@derrekr6</a>）ã€<a href="mailto:sbauer@plzdonthack.me">Scott Bauer</a>（<a href="https://twitter.com/ScottyBauer1">@ScottyBauer1</a>）: CVE-2017-0521</li><li>Tencent KeenLab（<a href="https://twitter.com/returnsme">@keen_lab</a>）㮠Di Shen（<a href="https://twitter.com/keen_lab">@returnsme</a>）: CVE-2017-0334ã€CVE-2017-0456ã€CVE-2017-0457ã€CVE-2017-0525</li><li><a href="https://twitter.com/heeeeen4x">MS509Team</a> ã® En He（<a href="http://www.ms509.com">@heeeeen4x</a>）ã€Bo Liu: CVE-2017-0490</li><li>Qihoo 360 Technology Co. Ltd. IceSword Lab ã® Gengjia Chen（<a href="https://twitter.com/chengjia4574">@chengjia4574</a>）ã€<a href="http://weibo.com/jfpan">pjf</a>: CVE-2017-0500ã€CVE-2017-0501ã€CVE-2017-0502ã€CVE-2017-0503ã€CVE-2017-0509ã€CVE-2017-0524ã€CVE-2017-0529ã€CVE-2017-0536</li><li>Qihoo 360 Technology Co. Ltd. ã® Alpha Team ã® Hao Chenã€Guang Gong: CVE-2017-0453ã€CVE-2017-0461ã€CVE-2017-0464</li><li>Sony Mobile Communications Inc. ã® Hiroki Yamamotoã€Fang Chen: CVE-2017-0481</li><li>IBM Security X-Force Researcher ã® Sagi Kedmiã€Roee Hay: CVE-2017-0510</li><li><a href="https://twitter.com/Jioun_dai">Qihoo 360 Skyeye Labs</a> ã® Jianjun Dai（<a href="https://skyeye.360safe.com">@Jioun_dai</a>）: CVE-2017-0478</li><li>Qihoo 360 IceSword Lab ã® Jianqiang Zhao（<a href="https://twitter.com/jianqiangzhao">@jianqiangzhao</a>）ã€<a href="http://weibo.com/jfpan">pjf</a>: CVE-2016-8416ã€CVE-2016-8478ã€CVE-2017-0458ã€CVE-2017-0459ã€CVE-2017-0518ã€CVE-2017-0519ã€CVE-2017-0533ã€CVE-2017-0534</li><li><a href="mailto:zlbzlb815@163.com">C0RE Team</a> ã® <a href="mailto:segfault5514@gmail.com">Lubo Zhang</a>ã€<a href="mailto:computernik@gmail.com">Tong Lin</a>ã€<a href="http://c0reteam.org">Yuan-Tsung Lo</a>ã€Xuxian Jiang: CVE-2016-8479</li><li>Google ã®å¤§è²«èª : CVE-2017-0491</li><li><a href="https://twitter.com/Mingjian_Zhou">C0RE Team</a> ã® Mingjian Zhou（<a href="mailto:arnow117@gmail.com">@Mingjian_Zhou</a>）ã€<a href="http://c0reteam.org">Hanxiang Wen</a>ã€Xuxian Jiang: CVE-2017-0479ã€CVE-2017-0480</li><li>Nathan Crandall（<a href="https://twitter.com/natecray">@natecray</a>）: CVE-2017-0535</li><li>Tesla Motors Product Security Team ã® Nathan Crandall（<a href="https://twitter.com/natecray">@natecray</a>）: CVE-2017-0306</li><li>Baidu X-Lab（百度安全实验室）㮠Pengfei Ding（ä¸é¹é£žï¼‰ã€Chenfu Bao（包沉浮）ã€Lenx Wei（韦韬）: CVE-2016-8417</li><li>Tencent KeenLab ã® Qidan He（何淇丹）（<a href="https://twitter.com/flanker_hqd">@flanker_hqd</a>）: CVE-2017-0337ã€CVE-2017-0476</li><li>Qihoo 360 ã® Qing Zhangã€Singapore Institute of Technology（SIT）㮠Guangdong Bai: CVE-2017-0496</li><li>Ant-financial Light-Year Security Lab（蚂èšé‡‘æœå·´æ–¯å…‰å¹´å®‰å…¨å®žéªŒå®¤ï¼‰ã® Quheã€wanchouchou: CVE-2017-0522</li><li>DarkMatter Secure Communications ã® <a href="mailto:keun-o.park@darkmatter.ae">Sahara</a>: CVE-2017-0528</li><li>UC Santa Barbara Shellphish Grill Team ã® salls（<a href="https://twitter.com/chris_salls">@chris_salls</a>）: CVE-2017-0505</li><li><a href="mailto:sbauer@plzdonthack.me">Scott Bauer</a>（<a href="https://twitter.com/ScottyBauer1">@ScottyBauer1</a>）: CVE-2017-0504ã€CVE-2017-0516</li><li>Sean Beaupre（beaups）: CVE-2017-0455</li><li>Trend Micro ã® Seven Shen（<a href="https://twitter.com/lingtongshen">@lingtongshen</a>）: CVE-2017-0452</li><li>Fujitsu ã® Shinichi Matsumoto: CVE-2017-0498</li><li><a href="mailto:smarques84@gmail.com">ByteRev</a> ã® <a href="http://www.byterev.com">Stéphane Marques</a>: CVE-2017-0489</li><li>Google ã® Svetoslav Ganov: CVE-2017-0492</li><li><a href="mailto:segfault5514@gmail.com">C0RE Team</a> ã® <a href="mailto:computernik@gmail.com">Tong Lin</a>ã€<a href="http://c0reteam.org">Yuan-Tsung Lo</a>ã€Xuxian Jiang: CVE-2017-0333</li><li><a href="https://twitter.com/vysea">Trend Micro</a> <a href="http://blog.trendmicro.com/trendlabs-security-intelligence/category/mobile">Mobile Threat Response Team</a> ã® V.E.O（<a href="http://www.trendmicro.com">@VYSEa</a>）: CVE-2017-0466ã€CVE-2017-0467ã€CVE-2017-0468ã€CVE-2017-0469ã€CVE-2017-0470ã€CVE-2017-0471ã€CVE-2017-0472ã€CVE-2017-0473ã€CVE-2017-0482ã€CVE-2017-0484ã€CVE-2017-0485ã€CVE-2017-0486ã€CVE-2017-0487ã€CVE-2017-0494ã€CVE-2017-0495</li><li>Ant-financial Light-Year Security Lab（蚂èšé‡‘æœå·´æ–¯å…‰å¹´å®‰å…¨å®žéªŒå®¤ï¼‰ã® Wish Wu（å´æ½æµ æ¤å½¼ï¼‰ï¼ˆ<a href="https://twitter.com/wish_wu">@wish_wu</a>）: CVE-2017-0477</li><li>Qihoo 360 Technology Co. Ltd ã® Vulpecker Team ã® Yu Pan: CVE-2017-0517ã€CVE-2017-0532</li><li><a href="mailto:computernik@gmail.com">C0RE Team</a> ã® <a href="http://c0reteam.org">Yuan-Tsung Lo</a>ã€Xuxian Jiang: CVE-2017-0526ã€CVE-2017-0527</li><li><a href="https://twitter.com/nikos233__">C0RE Team</a> ã® Yuqi Lu（<a href="mailto:vancouverdou@gmail.com">@nikos233</a>）ã€<a href="mailto:shaodacheng2016@gmail.com">Wenke Dou</a>ã€<a href="https://twitter.com/Mingjian_Zhou">Dacheng Shao</a>ã€Mingjian Zhou（<a href="http://c0reteam.org">@Mingjian_Zhou</a>）ã€Xuxian Jiang: CVE-2017-0483</li> +<li>Google Dynamic Tools ãƒãƒ¼ãƒ ã® Alexander Potapenko: CVE-2017-0537</li><li>Alibaba Mobile Security Group ã® Baozeng Dingã€Chengming Yangã€Peng Xiaoã€Yang Song: CVE-2017-0506</li><li>Alibaba Mobile Security Group ã® Baozeng Dingã€Ning Youã€Chengming Yangã€Peng Xiaoã€Yang Song: CVE-2017-0463</li><li>Android Security ã® Billy Lau: CVE-2017-0335ã€CVE-2017-0336ã€CVE-2017-0338ã€CVE-2017-0460</li><li><a href="mailto:derrek.haxx@gmail.com">derrek</a>（<a href="https://twitter.com/derrekr6">@derrekr6</a>）: CVE-2016-8413ã€CVE-2016-8477ã€CVE-2017-0531</li><li><a href="mailto:derrek.haxx@gmail.com">derrek</a>（<a href="https://twitter.com/derrekr6">@derrekr6</a>）ã€<a href="mailto:sbauer@plzdonthack.me">Scott Bauer</a>（<a href="https://twitter.com/ScottyBauer1">@ScottyBauer1</a>）: CVE-2017-0521</li><li>Tencent KeenLab（<a href="https://twitter.com/keen_lab">@keen_lab</a>）㮠Di Shen（<a href="https://twitter.com/returnsme">@returnsme</a>）: CVE-2017-0334ã€CVE-2017-0456ã€CVE-2017-0457ã€CVE-2017-0525</li><li><a href="http://www.ms509.com">MS509Team</a> ã® En He（<a href="https://twitter.com/heeeeen4x">@heeeeen4x</a>）ã€Bo Liu: CVE-2017-0490</li><li>Qihoo 360 Technology Co. Ltd. IceSword Lab ã® Gengjia Chen（<a href="https://twitter.com/chengjia4574">@chengjia4574</a>）ã€<a href="http://weibo.com/jfpan">pjf</a>: CVE-2017-0500ã€CVE-2017-0501ã€CVE-2017-0502ã€CVE-2017-0503ã€CVE-2017-0509ã€CVE-2017-0524ã€CVE-2017-0529ã€CVE-2017-0536</li><li>Qihoo 360 Technology Co. Ltd. ã® Alpha Team ã® Hao Chenã€Guang Gong: CVE-2017-0453ã€CVE-2017-0461ã€CVE-2017-0464</li><li>Sony Mobile Communications Inc. ã® Hiroki Yamamotoã€Fang Chen: CVE-2017-0481</li><li>IBM Security X-Force Researcher ã® Sagi Kedmiã€Roee Hay: CVE-2017-0510</li><li><a href="https://skyeye.360safe.com">Qihoo 360 Skyeye Labs</a> ã® Jianjun Dai（<a href="https://twitter.com/Jioun_dai">@Jioun_dai</a>）: CVE-2017-0478</li><li>Qihoo 360 IceSword Lab ã® Jianqiang Zhao（<a href="https://twitter.com/jianqiangzhao">@jianqiangzhao</a>）ã€<a href="http://weibo.com/jfpan">pjf</a>: CVE-2016-8416ã€CVE-2016-8478ã€CVE-2017-0458ã€CVE-2017-0459ã€CVE-2017-0518ã€CVE-2017-0519ã€CVE-2017-0533ã€CVE-2017-0534</li><li><a href="http://c0reteam.org">C0RE Team</a> ã® <a href="mailto:zlbzlb815@163.com">Lubo Zhang</a>ã€<a href="mailto:segfault5514@gmail.com">Tong Lin</a>ã€<a href="mailto:computernik@gmail.com">Yuan-Tsung Lo</a>ã€Xuxian Jiang: CVE-2016-8479</li><li>Google ã®å¤§è²«èª : CVE-2017-0491</li><li><a href="http://c0reteam.org">C0RE Team</a> ã® Mingjian Zhou（<a href="https://twitter.com/Mingjian_Zhou">@Mingjian_Zhou</a>）ã€<a href="mailto:arnow117@gmail.com">Hanxiang Wen</a>ã€Xuxian Jiang: CVE-2017-0479ã€CVE-2017-0480</li><li>Nathan Crandall（<a href="https://twitter.com/natecray">@natecray</a>）: CVE-2017-0535</li><li>Tesla Motors Product Security Team ã® Nathan Crandall（<a href="https://twitter.com/natecray">@natecray</a>）: CVE-2017-0306</li><li>Baidu X-Lab（百度安全实验室）㮠Pengfei Ding（ä¸é¹é£žï¼‰ã€Chenfu Bao（包沉浮）ã€Lenx Wei（韦韬）: CVE-2016-8417</li><li>Tencent KeenLab ã® Qidan He（何淇丹）（<a href="https://twitter.com/flanker_hqd">@flanker_hqd</a>）: CVE-2017-0337ã€CVE-2017-0476</li><li>Qihoo 360 ã® Qing Zhangã€Singapore Institute of Technology（SIT）㮠Guangdong Bai: CVE-2017-0496</li><li>Ant-financial Light-Year Security Lab（蚂èšé‡‘æœå·´æ–¯å…‰å¹´å®‰å…¨å®žéªŒå®¤ï¼‰ã® Quheã€wanchouchou: CVE-2017-0522</li><li>DarkMatter Secure Communications ã® <a href="mailto:keun-o.park@darkmatter.ae">Sahara</a>: CVE-2017-0528</li><li>UC Santa Barbara Shellphish Grill Team ã® salls（<a href="https://twitter.com/chris_salls">@chris_salls</a>）: CVE-2017-0505</li><li><a href="mailto:sbauer@plzdonthack.me">Scott Bauer</a>（<a href="https://twitter.com/ScottyBauer1">@ScottyBauer1</a>）: CVE-2017-0504ã€CVE-2017-0516</li><li>Sean Beaupre（beaups）: CVE-2017-0455</li><li>Trend Micro ã® Seven Shen（<a href="https://twitter.com/lingtongshen">@lingtongshen</a>）: CVE-2017-0452</li><li>Fujitsu ã® Shinichi Matsumoto: CVE-2017-0498</li><li><a href="http://www.byterev.com">ByteRev</a> ã® <a href="mailto:smarques84@gmail.com">Stéphane Marques</a>: CVE-2017-0489</li><li>Google ã® Svetoslav Ganov: CVE-2017-0492</li><li><a href="http://c0reteam.org">C0RE Team</a> ã® <a href="mailto:segfault5514@gmail.com">Tong Lin</a>ã€<a href="mailto:computernik@gmail.com">Yuan-Tsung Lo</a>ã€Xuxian Jiang: CVE-2017-0333</li><li><a href="http://www.trendmicro.com">Trend Micro</a> <a href="http://blog.trendmicro.com/trendlabs-security-intelligence/category/mobile">Mobile Threat Response Team</a> ã® V.E.O（<a href="https://twitter.com/vysea">@VYSEa</a>）: CVE-2017-0466ã€CVE-2017-0467ã€CVE-2017-0468ã€CVE-2017-0469ã€CVE-2017-0470ã€CVE-2017-0471ã€CVE-2017-0472ã€CVE-2017-0473ã€CVE-2017-0482ã€CVE-2017-0484ã€CVE-2017-0485ã€CVE-2017-0486ã€CVE-2017-0487ã€CVE-2017-0494ã€CVE-2017-0495</li><li>Ant-financial Light-Year Security Lab（蚂èšé‡‘æœå·´æ–¯å…‰å¹´å®‰å…¨å®žéªŒå®¤ï¼‰ã® Wish Wu（å´æ½æµ æ¤å½¼ï¼‰ï¼ˆ<a href="https://twitter.com/wish_wu">@wish_wu</a>）: CVE-2017-0477</li><li>Qihoo 360 Technology Co. Ltd ã® Vulpecker Team ã® Yu Pan: CVE-2017-0517ã€CVE-2017-0532</li><li><a href="http://c0reteam.org">C0RE Team</a> ã® <a href="mailto:computernik@gmail.com">Yuan-Tsung Lo</a>ã€Xuxian Jiang: CVE-2017-0526ã€CVE-2017-0527</li><li><a href="http://c0reteam.org">C0RE Team</a> ã® Yuqi Lu（<a href="https://twitter.com/nikos233__">@nikos233</a>）ã€<a href="mailto:vancouverdou@gmail.com">Wenke Dou</a>ã€<a href="mailto:shaodacheng2016@gmail.com">Dacheng Shao</a>ã€Mingjian Zhou（<a href="https://twitter.com/Mingjian_Zhou">@Mingjian_Zhou</a>）ã€Xuxian Jiang: CVE-2017-0483</li> <li>Qihoo 360 Technology Co. Ltd. Chengdu Security Response Center ã® Zinuo Han（<a href="https://weibo.com/ele7enxxh">weibo.com/ele7enxxh</a>）: CVE-2017-0475ã€CVE-2017-0497</li></ul> <h2 id="2017-03-01-details">ã‚»ã‚ュリティ パッムレベル 2017-03-01 ã®è„†å¼±æ€§ã®è©³ç´°</h2> @@ -2083,7 +2083,7 @@ QC-CR#1090007</a> </tbody></table> <p>* ã“ã®å•é¡Œã«å¯¾ã™ã‚‹ãƒ‘ッãƒã¯å…¬é–‹ã•ã‚Œã¦ã„ã¾ã›ã‚“。アップデート㯠<a href="https://developers.google.com/android/nexus/drivers">Google デベãƒãƒƒãƒ‘ー サイト</a>ã‹ã‚‰å…¥æ‰‹ã§ãã‚‹ Nexus 端末用最新ãƒã‚¤ãƒŠãƒª ドライãƒã«å«ã¾ã‚Œã¦ã„ã¾ã™ã€‚</p> <h2 id="common-questions-and-answers">一般的ãªè³ªå•ã¨å›žç”</h2> -<p>上記ã®å…¬é–‹æƒ…å ±ã«å¯¾ã™ã‚‹ä¸€èˆ¬çš„ãªè³ªå•ã«ã¤ã„ã¦ã€ä»¥ä¸‹ã§å›žç”ã—ã¾ã™ã€‚</p> +<p>上記ã®å…¬é–‹æƒ…å ±ã«å¯¾ã™ã‚‹ä¸€èˆ¬çš„ãªè³ªå•ã«ã¤ã„ã¦ã®å›žç”ã¯ä»¥ä¸‹ã®ã¨ãŠã‚Šã§ã™ã€‚</p> <p><strong>1. 上記ã®å•é¡Œã«å¯¾å‡¦ã™ã‚‹ã‚ˆã†ã«ç«¯æœ«ãŒæ›´æ–°ã•ã‚Œã¦ã„ã‚‹ã‹ã©ã†ã‹ã‚’確ã‹ã‚ã‚‹ã«ã¯ã€ã©ã†ã™ã‚Œã°ã‚ˆã„ã§ã™ã‹ï¼Ÿ </strong></p> <p>端末ã®ã‚»ã‚ュリティ パッãƒãƒ¬ãƒ™ãƒ«ã‚’確èªã™ã‚‹æ–¹æ³•ã«ã¤ã„ã¦ã¯ã€<a href="https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices">Pixel ãŠã‚ˆã³ Nexus ã®ã‚¢ãƒƒãƒ—デート スケジュール</a>ã«è¨˜è¼‰ã•ã‚Œã¦ã„ã‚‹æ‰‹é †ã‚’ã”覧ãã ã•ã„。</p> diff --git a/ja/security/bulletin/2017-05-01.html b/ja/security/bulletin/2017-05-01.html index 5da194ee..06368e99 100644 --- a/ja/security/bulletin/2017-05-01.html +++ b/ja/security/bulletin/2017-05-01.html @@ -74,7 +74,7 @@ <li><a href="mailto:sbauer@plzdonthack.me">Scott Bauer</a>（<a href="https://twitter.com/ScottyBauer1">@ScottyBauer1</a>）: CVE-2016-10274</li> <li><a href="http://c0reteam.org">C0RE Team</a> ã® <a href="mailto:segfault5514@gmail.com">Tong Lin</a>ã€<a href="mailto:computernik@gmail.com">Yuan-Tsung Lo</a>ã€Xuxian Jiang: CVE-2016-10291</li> <li>Vasily Vasiliev: CVE-2017-0589</li> -<li><a href="http://www.trendmicro.com">Trend Micro</a>ã€<a href="http://blog.trendmicro.com/trendlabs-security-intelligence/category/mobile">Mobile Threat Response Team</a> ã® V.E.O（<a href="https://twitter.com/vysea">@VYSEa</a>）: CVE-2017-0590ã€CVE-2017-0587ã€CVE-2017-0600</li> +<li><a href="http://www.trendmicro.com">Trend Micro</a> <a href="http://blog.trendmicro.com/trendlabs-security-intelligence/category/mobile">Mobile Threat Response Team</a> ã® V.E.O（<a href="https://twitter.com/vysea">@VYSEa</a>）: CVE-2017-0590ã€CVE-2017-0587ã€CVE-2017-0600</li> <li>Tencent Security Platform Department ã® Xiling Gong: CVE-2017-0597</li> <li>360 Marvel Team ã® Xingyuan Lin: CVE-2017-0627</li> <li>Alibaba Inc. ã® Yong Wang（王勇）（<a href="https://twitter.com/ThomasKing2014">@ThomasKing2014</a>）: CVE-2017-0588</li> @@ -2371,7 +2371,7 @@ QC-CR#832915</a></td> <p>*** Android 7.1.1 以é™ãŒæ載ã•ã‚ŒãŸã‚µãƒãƒ¼ãƒˆå¯¾è±¡ã® Google 端末ã«ãŠã„ã¦ã€é©ç”¨ã§ãã‚‹ã™ã¹ã¦ã®ã‚¢ãƒƒãƒ—デートãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ã‚‹å ´åˆã¯ã€ã“ã®è„†å¼±æ€§ãŒæ‚ªç”¨ã•ã‚Œã‚‹ã“ã¨ã¯ã‚ã‚Šã¾ã›ã‚“。</p> <h2 id="common-questions-and-answers">一般的ãªè³ªå•ã¨å›žç”</h2> -<p>上記ã®å…¬é–‹æƒ…å ±ã«å¯¾ã™ã‚‹ä¸€èˆ¬çš„ãªè³ªå•ã«ã¤ã„ã¦ã€ä»¥ä¸‹ã§å›žç”ã—ã¾ã™ã€‚</p> +<p>上記ã®å…¬é–‹æƒ…å ±ã«å¯¾ã™ã‚‹ä¸€èˆ¬çš„ãªè³ªå•ã«ã¤ã„ã¦ã®å›žç”ã¯ä»¥ä¸‹ã®ã¨ãŠã‚Šã§ã™ã€‚</p> <p><strong>1. 上記ã®å•é¡Œã«å¯¾å‡¦ã™ã‚‹ã‚ˆã†ã«ç«¯æœ«ãŒæ›´æ–°ã•ã‚Œã¦ã„ã‚‹ã‹ã‚’判æ–ã™ã‚‹ã«ã¯ã€ã©ã†ã™ã‚Œã°ã‚ˆã„ã§ã™ã‹ï¼Ÿ </strong></p> diff --git a/ja/security/bulletin/2017-11-01.html b/ja/security/bulletin/2017-11-01.html index c9269e2b..f554c2ba 100644 --- a/ja/security/bulletin/2017-11-01.html +++ b/ja/security/bulletin/2017-11-01.html @@ -41,10 +41,11 @@ Android パートナーã«ã¯ã€2017-11-01 ãŠã‚ˆã³ 2017-11-05 パッãƒãƒ¬ãƒ™ã <li>KRACK 脆弱性ã«å¯¾ã™ã‚‹ã‚»ã‚ュリティ パッãƒã¯ã€2017-11-06 ã‚»ã‚ュリティ パッãƒãƒ¬ãƒ™ãƒ«ã§æä¾›ã•ã‚Œã¾ã™ã€‚</li> </ul> <h2 id="mitigations">Android 㨠Google サービスã§ã®ãƒªã‚¹ã‚¯è»½æ¸›ç–</h2> -<p>ã“ã“ã§ã¯ã€<a href="/security/enhancements/index.html">Android ã‚»ã‚ュリティ プラットフォーム</a>ã®ä¿è·ã¨ <a href="//www.android.com/play-protect">Google Play プãƒãƒ†ã‚¯ãƒˆ</a>ã®ã‚ˆã†ãªã‚µãƒ¼ãƒ“スã®ä¿è·ã«ã‚ˆã‚‹ãƒªã‚¹ã‚¯ã®è»½æ¸›ã«ã¤ã„ã¦æ¦‚説ã—ã¾ã™ã€‚ã“ã†ã—ãŸæ©Ÿèƒ½ã¯ã€Android ã§ã‚»ã‚ュリティã®è„†å¼±æ€§ãŒæ‚ªç”¨ã•ã‚Œã‚‹å¯èƒ½æ€§ã‚’減らã—ã¾ã™ã€‚ +<p> +ã“ã“ã§ã¯ã€<a href="/security/enhancements/index.html">Android ã‚»ã‚ュリティ プラットフォーム</a>ã®ä¿è·ã¨ <a href="//www.android.com/play-protect">Google Play プãƒãƒ†ã‚¯ãƒˆ</a>ã®ã‚ˆã†ãªã‚µãƒ¼ãƒ“スã®ä¿è·ã«ã‚ˆã‚‹ãƒªã‚¹ã‚¯ã®è»½æ¸›ã«ã¤ã„ã¦æ¦‚説ã—ã¾ã™ã€‚ã“ã†ã—ãŸæ©Ÿèƒ½ã¯ã€Android ã§ã‚»ã‚ュリティã®è„†å¼±æ€§ãŒæ‚ªç”¨ã•ã‚Œã‚‹å¯èƒ½æ€§ã‚’減らã—ã¾ã™ã€‚ </p> <ul> - <li>Android プラットフォームã®æœ€æ–°ç‰ˆã§ã®æ©Ÿèƒ½å¼·åŒ–ã«ã‚ˆã‚Šã€Android ã«ã‚る多ãã®å•é¡Œã®æ‚ªç”¨ãŒå›°é›£ã«ãªã‚Šã¾ã™ã€‚Google ã§ã¯ã€ã™ã¹ã¦ã®ãƒ¦ãƒ¼ã‚¶ãƒ¼ã«å¯¾ã—ã€ã§ãã‚‹é™ã‚Šæœ€æ–°ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã® Android ã«æ›´æ–°ã™ã‚‹ã“ã¨ã‚’ãŠã™ã™ã‚ã—ã¦ã„ã¾ã™ã€‚</li> + <li>Android プラットフォームã®æœ€æ–°ç‰ˆã§ã®æ©Ÿèƒ½å¼·åŒ–ã«ã‚ˆã‚Šã€Android 上ã®å¤šãã®å•é¡Œã®æ‚ªç”¨ãŒå›°é›£ã«ãªã‚Šã¾ã™ã€‚Google ã§ã¯ã€ã™ã¹ã¦ã®ãƒ¦ãƒ¼ã‚¶ãƒ¼ã«å¯¾ã—ã€ã§ãã‚‹é™ã‚Šæœ€æ–°ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã® Android ã«æ›´æ–°ã™ã‚‹ã“ã¨ã‚’ãŠã™ã™ã‚ã—ã¦ã„ã¾ã™ã€‚</li> <li>Android ã‚»ã‚ュリティ ãƒãƒ¼ãƒ ã¯ã€<a href="//www.android.com/play-protect">Google Play プãƒãƒ†ã‚¯ãƒˆ</a>ã«ã‚ˆã£ã¦è„†å¼±æ€§ã®æ‚ªç”¨ã‚’ç©æ¥µçš„ã«ç›£è¦–ã—ã¦ãŠã‚Šã€<a href="/security/reports/Google_Android_Security_PHA_classifications.pdf">有害ãªãŠãã‚Œã®ã‚るアプリ</a>ã«ã¤ã„ã¦ãƒ¦ãƒ¼ã‚¶ãƒ¼ã«è¦å‘Šã—ã¦ã„ã¾ã™ã€‚Google Play プãƒãƒ†ã‚¯ãƒˆã¯ã€<a href="//www.android.com/gms">Google モãƒã‚¤ãƒ« サービス</a>ã‚’æ載ã—ãŸç«¯æœ«ã§ã¯ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã§æœ‰åŠ¹ã«ãªã£ã¦ãŠã‚Šã€Google Play 以外ã‹ã‚‰ã‚¢ãƒ—リをインストールã™ã‚‹ãƒ¦ãƒ¼ã‚¶ãƒ¼ã«ã¨ã£ã¦ã¯ç‰¹ã«é‡è¦ã§ã™ã€‚</li> </ul> <h2 id="2017-11-01-details">ã‚»ã‚ュリティ パッãƒãƒ¬ãƒ™ãƒ« 2017-11-01 ã®è„†å¼±æ€§ã®è©³ç´°</h2> @@ -184,11 +185,11 @@ Android パートナーã«ã¯ã€2017-11-01 ãŠã‚ˆã³ 2017-11-05 パッãƒãƒ¬ãƒ™ã <h2 id="2017-11-05-details">ã‚»ã‚ュリティ パッãƒãƒ¬ãƒ™ãƒ« 2017-11-05 ã®è„†å¼±æ€§ã®è©³ç´°</h2> <p> -パッãƒãƒ¬ãƒ™ãƒ« 2017-11-05 ã«è©²å½“ã™ã‚‹ã‚»ã‚ュリティ脆弱性ã®å„é …ç›®ã«ã¤ã„ã¦ã€ä¸‹è¨˜ã«è©³ç´°ã‚’説明ã—ã¾ã™ã€‚影響をå—ã‘るコンãƒãƒ¼ãƒãƒ³ãƒˆã”ã¨ã«è„†å¼±æ€§ã‚’分類ã—ã€CVEã€é–¢é€£ã™ã‚‹å‚照先ã€<a href="#type">脆弱性ã®ç¨®é¡ž</a>ã€<a href="/security/overview/updates-resources.html#severity">é‡å¤§åº¦</a>ã€ã‚³ãƒ³ãƒãƒ¼ãƒãƒ³ãƒˆï¼ˆè©²å½“ã™ã‚‹å ´åˆï¼‰ã€æ›´æ–°å¯¾è±¡ã® AOSP ãƒãƒ¼ã‚¸ãƒ§ãƒ³ï¼ˆè©²å½“ã™ã‚‹å ´åˆï¼‰ãªã©ã®è©³ç´°ã‚’記載ã—ã¦ã„ã¾ã™ã€‚該当ã™ã‚‹å ´åˆã¯ã€ãƒã‚° ID ã®æ¬„ã«ã€ãã®å•é¡Œã«å¯¾å‡¦ã—ãŸä¸€èˆ¬å…¬é–‹ã•ã‚Œã¦ã„る変更（AOSP ã®å¤‰æ›´ã®ä¸€è¦§ãªã©ï¼‰ã¸ã®ãƒªãƒ³ã‚¯ãŒã‚ã‚Šã¾ã™ã€‚複数ã®å¤‰æ›´ãŒåŒã˜ãƒã‚°ã«é–¢ä¿‚ã™ã‚‹å ´åˆã¯ã€ãƒã‚° ID ã®å¾Œã«ç¶šã番å·ã§ã€è¿½åŠ ã®å‚照先ã¸ã®ãƒªãƒ³ã‚¯ã‚’示ã—ã¾ã™ã€‚ +パッãƒãƒ¬ãƒ™ãƒ« 2017-11-05 ã«è©²å½“ã™ã‚‹ã‚»ã‚ュリティ脆弱性ã®å„é …ç›®ã«ã¤ã„ã¦ã€ä¸‹è¨˜ã«è©³ç´°ã‚’説明ã—ã¾ã™ã€‚影響をå—ã‘るコンãƒãƒ¼ãƒãƒ³ãƒˆã”ã¨ã«è„†å¼±æ€§ã‚’分類ã—ã€CVEã€é–¢é€£ã™ã‚‹å‚照先ã€<a href="#type">脆弱性ã®ã‚¿ã‚¤ãƒ—</a>ã€<a href="/security/overview/updates-resources.html#severity">é‡å¤§åº¦</a>ã€ã‚³ãƒ³ãƒãƒ¼ãƒãƒ³ãƒˆï¼ˆè©²å½“ã™ã‚‹å ´åˆï¼‰ã€æ›´æ–°å¯¾è±¡ã® AOSP ãƒãƒ¼ã‚¸ãƒ§ãƒ³ï¼ˆè©²å½“ã™ã‚‹å ´åˆï¼‰ãªã©ã®è©³ç´°ã‚’記載ã—ã¦ã„ã¾ã™ã€‚該当ã™ã‚‹å ´åˆã¯ã€ãƒã‚° ID ã®æ¬„ã«ã€ãã®å•é¡Œã«å¯¾å‡¦ã—ãŸä¸€èˆ¬å…¬é–‹ã•ã‚Œã¦ã„る変更（AOSP ã®å¤‰æ›´ã®ä¸€è¦§ãªã©ï¼‰ã¸ã®ãƒªãƒ³ã‚¯ãŒã‚ã‚Šã¾ã™ã€‚複数ã®å¤‰æ›´ãŒåŒã˜ãƒã‚°ã«é–¢ä¿‚ã™ã‚‹å ´åˆã¯ã€ãƒã‚° ID ã®å¾Œã«ç¶šã番å·ã§ã€è¿½åŠ ã®å‚照先ã¸ã®ãƒªãƒ³ã‚¯ã‚’示ã—ã¾ã™ã€‚ </p> <h3 id="kernel-components">カーãƒãƒ« コンãƒãƒ¼ãƒãƒ³ãƒˆ</h3> -<p>カーãƒãƒ« コンãƒãƒ¼ãƒãƒ³ãƒˆã®æœ€ã‚‚é‡å¤§ãªè„†å¼±æ€§ã¯ã€æ‚ªæ„ã®ã‚ã‚‹ãƒãƒ¼ã‚«ãƒ«ã‚¢ãƒ—リã«ã‚ˆã£ã¦ç‰¹æ¨©ãƒ—ãƒã‚»ã‚¹å†…ã§ä»»æ„ã®ã‚³ãƒ¼ãƒ‰ãŒå®Ÿè¡Œã•ã‚Œã‚‹ãŠãã‚ŒãŒã‚ã‚‹ã“ã¨ã§ã™ã€‚</p> +<p>カーãƒãƒ« コンãƒãƒ¼ãƒãƒ³ãƒˆã«é‡å¤§ãªè„†å¼±æ€§ãŒã‚ã‚‹ãŸã‚ã€æ‚ªæ„ã®ã‚ã‚‹ãƒãƒ¼ã‚«ãƒ«ã‚¢ãƒ—リã«ã‚ˆã£ã¦ç‰¹æ¨©ãƒ—ãƒã‚»ã‚¹å†…ã§ä»»æ„ã®ã‚³ãƒ¼ãƒ‰ãŒå®Ÿè¡Œã•ã‚Œã‚‹ãŠãã‚ŒãŒã‚ã‚Šã¾ã™ã€‚</p> <table> <colgroup><col width="17%" /> @@ -224,7 +225,7 @@ Android パートナーã«ã¯ã€2017-11-01 ãŠã‚ˆã³ 2017-11-05 パッãƒãƒ¬ãƒ™ã </tbody></table> <h3 id="mediatek-components">MediaTek コンãƒãƒ¼ãƒãƒ³ãƒˆ</h3> -<p>MediaTek コンãƒãƒ¼ãƒãƒ³ãƒˆã®æœ€ã‚‚é‡å¤§ãªè„†å¼±æ€§ã¯ã€æ‚ªæ„ã®ã‚ã‚‹ãƒãƒ¼ã‚«ãƒ«ã‚¢ãƒ—リã«ã‚ˆã£ã¦ç‰¹æ¨©ãƒ—ãƒã‚»ã‚¹å†…ã§ä»»æ„ã®ã‚³ãƒ¼ãƒ‰ãŒå®Ÿè¡Œã•ã‚Œã‚‹ãŠãã‚ŒãŒã‚ã‚‹ã“ã¨ã§ã™ã€‚</p> +<p>MediaTek コンãƒãƒ¼ãƒãƒ³ãƒˆã«é‡å¤§ãªè„†å¼±æ€§ãŒã‚ã‚‹ãŸã‚ã€æ‚ªæ„ã®ã‚ã‚‹ãƒãƒ¼ã‚«ãƒ«ã‚¢ãƒ—リã«ã‚ˆã£ã¦ç‰¹æ¨©ãƒ—ãƒã‚»ã‚¹å†…ã§ä»»æ„ã®ã‚³ãƒ¼ãƒ‰ãŒå®Ÿè¡Œã•ã‚Œã‚‹ãŠãã‚ŒãŒã‚ã‚Šã¾ã™ã€‚</p> <table> <colgroup><col width="17%" /> @@ -358,7 +359,7 @@ QC-CR#2008683</a> <h2 id="2017-11-06-details">ã‚»ã‚ュリティ パッãƒãƒ¬ãƒ™ãƒ« 2017-11-06 ã®è„†å¼±æ€§ã®è©³ç´°</h2> <p> -パッãƒãƒ¬ãƒ™ãƒ« 2017-11-06 ã«è©²å½“ã™ã‚‹ã‚»ã‚ュリティ脆弱性ã®å„é …ç›®ã«ã¤ã„ã¦ã€ä¸‹è¨˜ã«è©³ç´°ã‚’説明ã—ã¾ã™ã€‚影響をå—ã‘るコンãƒãƒ¼ãƒãƒ³ãƒˆã”ã¨ã«è„†å¼±æ€§ã‚’分類ã—ã€CVEã€é–¢é€£ã™ã‚‹å‚照先ã€<a href="#type">脆弱性ã®ç¨®é¡ž</a>ã€<a href="/security/overview/updates-resources.html#severity">é‡å¤§åº¦</a>ã€ã‚³ãƒ³ãƒãƒ¼ãƒãƒ³ãƒˆï¼ˆè©²å½“ã™ã‚‹å ´åˆï¼‰ã€æ›´æ–°å¯¾è±¡ã® AOSP ãƒãƒ¼ã‚¸ãƒ§ãƒ³ï¼ˆè©²å½“ã™ã‚‹å ´åˆï¼‰ãªã©ã®è©³ç´°ã‚’記載ã—ã¦ã„ã¾ã™ã€‚該当ã™ã‚‹å ´åˆã¯ã€ãƒã‚° ID ã®æ¬„ã«ã€ãã®å•é¡Œã«å¯¾å‡¦ã—ãŸä¸€èˆ¬å…¬é–‹ã•ã‚Œã¦ã„る変更（AOSP ã®å¤‰æ›´ã®ä¸€è¦§ãªã©ï¼‰ã¸ã®ãƒªãƒ³ã‚¯ãŒã‚ã‚Šã¾ã™ã€‚複数ã®å¤‰æ›´ãŒåŒã˜ãƒã‚°ã«é–¢ä¿‚ã™ã‚‹å ´åˆã¯ã€ãƒã‚° ID ã®å¾Œã«ç¶šã番å·ã§ã€è¿½åŠ ã®å‚照先ã¸ã®ãƒªãƒ³ã‚¯ã‚’示ã—ã¾ã™ã€‚</p> +パッãƒãƒ¬ãƒ™ãƒ« 2017-11-06 ã«è©²å½“ã™ã‚‹ã‚»ã‚ュリティ脆弱性ã®å„é …ç›®ã«ã¤ã„ã¦ã€ä¸‹è¨˜ã«è©³ç´°ã‚’説明ã—ã¾ã™ã€‚影響をå—ã‘るコンãƒãƒ¼ãƒãƒ³ãƒˆã”ã¨ã«è„†å¼±æ€§ã‚’分類ã—ã€CVEã€é–¢é€£ã™ã‚‹å‚照先ã€<a href="#type">脆弱性ã®ã‚¿ã‚¤ãƒ—</a>ã€<a href="/security/overview/updates-resources.html#severity">é‡å¤§åº¦</a>ã€ã‚³ãƒ³ãƒãƒ¼ãƒãƒ³ãƒˆï¼ˆè©²å½“ã™ã‚‹å ´åˆï¼‰ã€æ›´æ–°å¯¾è±¡ã® AOSP ãƒãƒ¼ã‚¸ãƒ§ãƒ³ï¼ˆè©²å½“ã™ã‚‹å ´åˆï¼‰ãªã©ã®è©³ç´°ã‚’記載ã—ã¦ã„ã¾ã™ã€‚該当ã™ã‚‹å ´åˆã¯ã€ãƒã‚° ID ã®æ¬„ã«ã€ãã®å•é¡Œã«å¯¾å‡¦ã—ãŸä¸€èˆ¬å…¬é–‹ã•ã‚Œã¦ã„る変更（AOSP ã®å¤‰æ›´ã®ä¸€è¦§ãªã©ï¼‰ã¸ã®ãƒªãƒ³ã‚¯ãŒã‚ã‚Šã¾ã™ã€‚複数ã®å¤‰æ›´ãŒåŒã˜ãƒã‚°ã«é–¢ä¿‚ã™ã‚‹å ´åˆã¯ã€ãƒã‚° ID ã®å¾Œã«ç¶šã番å·ã§ã€è¿½åŠ ã®å‚照先ã¸ã®ãƒªãƒ³ã‚¯ã‚’示ã—ã¾ã™ã€‚</p> <h3 id="11-06-system">システム</h3> <p> システムã®æœ€ã‚‚é‡å¤§ãªè„†å¼±æ€§ã¯ã€è¿‘ãã«ã„る攻撃者ã«ã‚ˆã£ã¦ã€ä¿è·ã•ã‚Œã¦ã„ãªã„ Wi-Fi ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ã«æŽ¥ç¶šã™ã‚‹å‰ã®ãƒ¦ãƒ¼ã‚¶ãƒ¼æ“作è¦ä»¶ãŒå›žé¿ã•ã‚Œã‚‹ãŠãã‚ŒãŒã‚ã‚‹ã“ã¨ã§ã™ã€‚ @@ -511,7 +512,7 @@ QC-CR#2008683</a> <td>サービス拒å¦</td> </tr> <tr> - <td>N/A</td> + <td>ãªã—</td> <td>該当ã™ã‚‹åˆ†é¡žãªã—</td> </tr> </tbody></table> diff --git a/ja/security/bulletin/2018-01-01.html b/ja/security/bulletin/2018-01-01.html index d4901572..4db7eee4 100644 --- a/ja/security/bulletin/2018-01-01.html +++ b/ja/security/bulletin/2018-01-01.html @@ -19,14 +19,13 @@ See the License for the specific language governing permissions and limitations under the License. --> -<p><em>公開日: 2018 å¹´ 1 月 2 æ—¥</em></p> +<p><em>2018 å¹´ 1 月 2 日公開 | 2018 å¹´ 1 月 29 日更新</em></p> <p> Android ã®ã‚»ã‚ュリティã«é–¢ã™ã‚‹å…¬é–‹æƒ…å ±ã«ã¯ã€Android æ載端末ã«å½±éŸ¿ã‚’与ãˆã‚‹ã‚»ã‚ュリティã®è„†å¼±æ€§ã®è©³ç´°ã‚’掲載ã—ã¦ã„ã¾ã™ã€‚ã‚»ã‚ュリティ パッãƒãƒ¬ãƒ™ãƒ« 2018-01-05 以é™ã§ã¯ã€ä¸‹è¨˜ã®ã™ã¹ã¦ã®å•é¡Œã«å¯¾å‡¦ã—ã¦ã„ã¾ã™ã€‚端末ã®ã‚»ã‚ュリティ パッãƒãƒ¬ãƒ™ãƒ«ã‚’確èªã™ã‚‹æ–¹æ³•ã«ã¤ã„ã¦ã¯ã€<a href="https://support.google.com/pixelphone/answer/4457705">Android ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã‚’確èªã—ã¦æ›´æ–°ã™ã‚‹</a>ã‚’ã”覧ãã ã•ã„。 </p> <p> -Android パートナーã«ã¯ã€æƒ…å ±å…¬é–‹ã®å°‘ãªãã¨ã‚‚ 1 ã‹æœˆå‰ã«ã™ã¹ã¦ã®å•é¡ŒãŒé€šçŸ¥ã•ã‚Œã¾ã™ã€‚下記ã®å•é¡Œã«å¯¾ã™ã‚‹ã‚½ãƒ¼ã‚¹ã‚³ãƒ¼ãƒ‰ã®ãƒ‘ッãƒã¯ã€ã“ã‚Œã‹ã‚‰ 48 時間ã®é–“ã« Android オープンソース プãƒã‚¸ã‚§ã‚¯ãƒˆï¼ˆAOSP）レãƒã‚¸ãƒˆãƒªã«ãƒªãƒªãƒ¼ã‚¹ã•ã‚Œã¾ã™ã€‚AOSP リンクãŒåˆ©ç”¨å¯èƒ½ã«ãªã‚Šæ¬¡ç¬¬ã€ã“ã®å…¬é–‹æƒ…å ±ã‚’æ”¹è¨‚ã—ã¾ã™ã€‚ -</p> +Android パートナーã«ã¯ã€æƒ…å ±å…¬é–‹ã® 1 ã‹æœˆå‰ã¾ã§ã«ã™ã¹ã¦ã®å•é¡ŒãŒé€šçŸ¥ã•ã‚Œã¾ã™ã€‚Android オープンソース プãƒã‚¸ã‚§ã‚¯ãƒˆï¼ˆAOSP）ã®ãƒ¬ãƒã‚¸ãƒˆãƒªã«ã€ä¸‹è¨˜ã®å•é¡Œã«å¯¾ã™ã‚‹ã‚½ãƒ¼ã‚¹ã‚³ãƒ¼ãƒ‰ã®ãƒ‘ッãƒã‚’リリースã—ã¦ã„ã¾ã™ã€‚ã¾ãŸã€ã“ã®å…¬é–‹æƒ…å ±ã§ã¯ã€ã“れらã®ãƒ‘ッãƒã¸ã®ãƒªãƒ³ã‚¯ã«åŠ ãˆã€AOSP 以外ã®ãƒ‘ッãƒã¸ã®ãƒªãƒ³ã‚¯ã‚‚掲載ã—ã¦ã„ã¾ã™ã€‚</p> <p> 下記ã®å•é¡Œã®ã†ã¡æœ€ã‚‚é‡å¤§åº¦ã®é«˜ã„ã‚‚ã®ã¯ã€ãƒ¡ãƒ‡ã‚£ã‚¢ フレームワークã«é‡å¤§ãªã‚»ã‚ュリティã®è„†å¼±æ€§ãŒã‚ã‚‹ãŸã‚ã€é›¢ã‚ŒãŸå ´æ‰€ã«ã„る攻撃者ãŒç‰¹åˆ¥ã«ç´°å·¥ã—ãŸãƒ•ã‚¡ã‚¤ãƒ«ã‚’使用ã—ã¦ã€ç‰¹æ¨©ãƒ—ãƒã‚»ã‚¹å†…ã§ä»»æ„ã®ã‚³ãƒ¼ãƒ‰ã‚’実行ã™ã‚‹ãŠãã‚ŒãŒã‚ã‚‹ã“ã¨ã§ã™ã€‚<a href="/security/overview/updates-resources.html#severity">é‡å¤§åº¦ã®è©•ä¾¡</a>ã¯ã€æ”»æ’ƒå¯¾è±¡ã®ç«¯æœ«ã§ãã®è„†å¼±æ€§ãŒæ‚ªç”¨ã•ã‚ŒãŸå ´åˆã®å½±éŸ¿ã«åŸºã¥ãã‚‚ã®ã§ã€ãƒ—ラットフォームやサービスã§ã®ãƒªã‚¹ã‚¯è»½æ¸›ç–ãŒé–‹ç™ºç›®çš„ã¾ãŸã¯ä¸æ£ãªå›žé¿ã«ã‚ˆã‚Šç„¡åŠ¹ã¨ãªã£ã¦ã„ã‚‹ã“ã¨ã‚’å‰æã¨ã—ã¦ã„ã¾ã™ã€‚ </p> @@ -37,6 +36,14 @@ Android パートナーã«ã¯ã€æƒ…å ±å…¬é–‹ã®å°‘ãªãã¨ã‚‚ 1 ã‹æœˆå‰ã«ã™ <strong>注:</strong> 最新ã®ç„¡ç·šï¼ˆOTA）アップデート㨠Google 端末ã®ãƒ•ã‚¡ãƒ¼ãƒ ウェア イメージã«ã¤ã„ã¦ã®æƒ…å ±ã¯ã€2018 å¹´ 1 月㮠Pixel&hairsp;/&hairsp;Nexus ã®ã‚»ã‚ュリティã«é–¢ã™ã‚‹å…¬é–‹æƒ…å ±ã§ã”覧ã„ãŸã ã‘ã¾ã™ã€‚ </p> <h2 id="announcements">ãŠçŸ¥ã‚‰ã›</h2> +<aside class="note"> +<p><strong>注:</strong> CVE-2017-5715ã€CVE-2017-5753ã€CVE-2017-5754（プãƒã‚»ãƒƒã‚µã®æŠ•æ©Ÿçš„実行ã«é–¢ã™ã‚‹ä¸€é€£ã®è„†å¼±æ€§ï¼‰ãŒå…¬é–‹ã•ã‚Œã¦ã„ã¾ã™ã€‚Android ã§ã¯ã€ARM ベース㮠Android æ載端末ã«ãŠã„ã¦ä¸æ£ãªæƒ…å ±é–‹ç¤ºã‚’å¯èƒ½ã«ã™ã‚‹ã“れらã®è„†å¼±æ€§ãŒå†ç¾ã•ã‚Œã¦ã‚‚èªè˜ã§ãã¾ã›ã‚“。 +</p> +<p> +ä¿è·ã‚’強化ã™ã‚‹ã«ã¯ã€ã“ã®å…¬é–‹æƒ…å ±ã«å«ã¾ã‚Œã¦ã„ã‚‹ CVE-2017-13218 ã«å¯¾ã™ã‚‹ã‚¢ãƒƒãƒ—デートをé©ç”¨ã—ã¦ã€é«˜ç²¾åº¦ã‚¿ã‚¤ãƒžãƒ¼ã¸ã®ã‚¢ã‚¯ã‚»ã‚¹ã‚’減らã—ã¾ã™ã€‚ã“ã‚Œã«ã‚ˆã‚Šã€æ—¢çŸ¥ã®ã™ã¹ã¦ã®ç¨®é¡žã® ARM プãƒã‚»ãƒƒã‚µã«å¯¾ã™ã‚‹ã‚µã‚¤ãƒ‰ãƒãƒ£ãƒãƒ«æ”»æ’ƒï¼ˆCVE-2017-5715ã€CVE-2017-5753ã€CVE-2017-5754 ãªã©ï¼‰ã‚’制é™ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚ +</p> +<p>Google ã§ã¯ã€Android æ載端末ã«åˆ©ç”¨å¯èƒ½ãªã‚»ã‚ュリティ アップデートをé©ç”¨ã™ã‚‹ã“ã¨ã‚’ãŠã™ã™ã‚ã—ã¦ã„ã¾ã™ã€‚詳ã—ãã¯ã€<a href="https://security.googleblog.com/2018/01/todays-cpu-vulnerability-what-you-need.html">Google ã‚»ã‚ュリティ ブãƒã‚°</a>ã‚’ã”覧ãã ã•ã„。</p> +</aside> <p> æ–°ãŸã« <a href="/security/bulletin/pixel/">Pixel  /  Nexus ã®ã‚»ã‚ュリティã«é–¢ã™ã‚‹å…¬é–‹æƒ…å ±</a>ã®æ供を開始ã—ã¾ã—ãŸã€‚ã“ã®å…¬é–‹æƒ…å ±ã«ã¯ã€Pixel 端末㨠Nexus 端末ã§å¯¾å‡¦ã•ã‚Œã¦ã„ã‚‹ãã®ä»–ã®ã‚»ã‚ュリティã®è„†å¼±æ€§ã‚„機能強化ã«ã¤ã„ã¦ã®æƒ…å ±ã‚’æŽ²è¼‰ã—ã¦ã„ã¾ã™ã€‚Android æ載端末メーカーã¯ã€è‡ªç¤¾ã®ç«¯æœ«ã§ãれらã®å•é¡Œã«å¯¾å‡¦ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚詳ã—ãã¯ã€<a href="#common-questions-and-answers">一般的ãªè³ªå•ã¨å›žç”</a>ã‚’ã”覧ãã ã•ã„。 </p> @@ -68,7 +75,8 @@ Android パートナーã«ã¯ã€æƒ…å ±å…¬é–‹ã®å°‘ãªãã¨ã‚‚ 1 ã‹æœˆå‰ã«ã™ </tr> <tr> <td>CVE-2017-13176</td> - <td>A-68341964</td> + <td><a href="https://android.googlesource.com/platform/frameworks/base/+/4afa0352d6c1046f9e9b67fbf0011bcd751fcbb5"> + A-68341964</a></td> <td>EoP</td> <td>高</td> <td>5.1.1ã€6.0ã€6.0.1ã€7.0ã€7.1.1ã€7.1.2ã€8.0ã€8.1</td> @@ -92,109 +100,124 @@ Android パートナーã«ã¯ã€æƒ…å ±å…¬é–‹ã®å°‘ãªãã¨ã‚‚ 1 ã‹æœˆå‰ã«ã™ <th>更新対象㮠AOSP ãƒãƒ¼ã‚¸ãƒ§ãƒ³</th> </tr> <tr> - <td>CVE-2017-13177</td> - <td>A-68320413</td> - <td>RCE</td> - <td>é‡å¤§</td> - <td>5.1.1ã€6.0ã€6.0.1ã€7.0ã€7.1.1ã€7.1.2ã€8.0ã€8.1</td> + <td>CVE-2017-13177</td> + <td><a href="https://android.googlesource.com/platform/external/libhevc/+/b686bb2df155fd1f55220d56f38cc0033afe278c"> + A-68320413</a></td> + <td>RCE</td> + <td>é‡å¤§</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-13178</td> - <td>A-66969281</td> - <td>RCE</td> - <td>é‡å¤§</td> - <td>6.0.1ã€7.0ã€7.1.1ã€7.1.2ã€8.0ã€8.1</td> + <td>CVE-2017-13178</td> + <td><a href="https://android.googlesource.com/platform/frameworks/av/+/646a18fef28d19ba5beb6a2e1c00ac4c2663a10b"> + A-66969281</a></td> + <td>RCE</td> + <td>é‡å¤§</td> + <td>6.0.1ã€7.0ã€7.1.1ã€7.1.2ã€8.0ã€8.1</td> </tr> <tr> - <td>CVE-2017-13179</td> - <td>A-66969193</td> - <td>RCE</td> - <td>é‡å¤§</td> - <td>6.0.1ã€7.0ã€7.1.1ã€7.1.2ã€8.0ã€8.1</td> + <td>CVE-2017-13179</td> + <td><a href="https://android.googlesource.com/platform/frameworks/av/+/47d4b33b504e14e98420943f771a9aecd6d09516"> + A-66969193</a></td> + <td>RCE</td> + <td>é‡å¤§</td> + <td>6.0.1ã€7.0ã€7.1.1ã€7.1.2ã€8.0ã€8.1</td> </tr> <tr> - <td>CVE-2017-13180</td> - <td>A-66969349</td> - <td>EoP</td> - <td>高</td> - <td>6.0ã€6.0.1ã€7.0ã€7.1.1ã€7.1.2ã€8.0ã€8.1</td> + <td>CVE-2017-13180</td> + <td><a href="https://android.googlesource.com/platform/frameworks/av/+/cf1e36f93fc8776e3a8109149424babeee7f8382"> + A-66969349</a></td> + <td>EoP</td> + <td>高</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-13181</td> - <td>A-67864232</td> - <td>EoP</td> - <td>高</td> - <td>7.0ã€7.1.1ã€7.1.2ã€8.0ã€8.1</td> + <td>CVE-2017-13181</td> + <td><a href="https://android.googlesource.com/platform/frameworks/base/+/d64e9594d3d73c613010ca9fafc7af9782e9225d"> + A-67864232</a></td> + <td>EoP</td> + <td>高</td> + <td>7.0ã€7.1.1ã€7.1.2ã€8.0ã€8.1</td> </tr> <tr> - <td>CVE-2017-13182</td> - <td>A-67737022</td> - <td>EoP</td> - <td>高</td> - <td>8.0ã€8.1</td> + <td>CVE-2017-13182</td> + <td><a href="https://android.googlesource.com/platform/frameworks/av/+/f1652e1b9f1d2840c79b6bf784d1befe40f4799e"> + A-67737022</a></td> + <td>EoP</td> + <td>高</td> + <td>8.0ã€8.1</td> </tr> <tr> - <td>CVE-2017-13184</td> - <td>A-65483324</td> - <td>EoP</td> - <td>高</td> - <td>8.0ã€8.1</td> + <td>CVE-2017-13184</td> + <td><a href="https://android.googlesource.com/platform/frameworks/native/+/16392a119661fd1da750d4d4e8e03442578bc543"> + A-65483324</a></td> + <td>EoP</td> + <td>高</td> + <td>8.0ã€8.1</td> </tr> <tr> - <td>CVE-2017-0855</td> - <td>A-64452857</td> - <td>DoS</td> - <td>高</td> - <td>5.1.1ã€6.0ã€6.0.1ã€7.0ã€7.1.1ã€7.1.2ã€8.0</td> + <td>CVE-2017-0855</td> + <td><a href="https://android.googlesource.com/platform/frameworks/av/+/d7d6df849cec9d0a9c1fd0d9957a1b8edef361b7"> + A-64452857</a></td> + <td>DoS</td> + <td>高</td> + <td>5.1.1ã€6.0ã€6.0.1ã€7.0ã€7.1.1ã€7.1.2ã€8.0</td> </tr> <tr> - <td>CVE-2017-13191</td> - <td>A-64380403</td> - <td>DoS</td> - <td>高</td> - <td>5.1.1ã€6.0ã€6.0.1ã€7.0ã€7.1.1ã€7.1.2ã€8.0ã€8.1</td> + <td>CVE-2017-13191</td> + <td><a href="https://android.googlesource.com/platform/external/libhevc/+/f5b2fa243b4c45a4cd885e85f49ae548ab88c264"> + A-64380403</a></td> + <td>DoS</td> + <td>高</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-13192</td> - <td>A-64380202</td> - <td>DoS</td> - <td>高</td> - <td>5.1.1ã€6.0ã€6.0.1ã€7.0ã€7.1.1ã€7.1.2ã€8.0ã€8.1</td> + <td>CVE-2017-13192</td> + <td><a href="https://android.googlesource.com/platform/external/libhevc/+/52ca619511acbd542d843df1f92f858ce13048a5"> + A-64380202</a></td> + <td>DoS</td> + <td>高</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-13193</td> - <td>A-65718319</td> - <td>DoS</td> - <td>高</td> - <td>5.1.1ã€6.0ã€6.0.1ã€7.0ã€7.1.1ã€7.1.2ã€8.0ã€8.1</td> + <td>CVE-2017-13193</td> + <td><a href="https://android.googlesource.com/platform/external/libhevc/+/b3f31e493ef6fa886989198da9787807635eaae2"> + A-65718319</a></td> + <td>DoS</td> + <td>高</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-13195</td> - <td>A-65398821</td> - <td>DoS</td> - <td>高</td> - <td>5.1.1ã€6.0ã€6.0.1ã€7.0ã€7.1.1ã€7.1.2ã€8.0ã€8.1</td> + <td>CVE-2017-13195</td> + <td><a href="https://android.googlesource.com/platform/external/libhevc/+/066e3b1f9c954d95045bc9d33d2cdc9df419784f"> + A-65398821</a></td> + <td>DoS</td> + <td>高</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-13196</td> - <td>A-63522067</td> - <td>DoS</td> - <td>高</td> - <td>5.1.1ã€6.0ã€6.0.1ã€7.0ã€7.1.1ã€7.1.2ã€8.0ã€8.1</td> + <td>CVE-2017-13196</td> + <td><a href="https://android.googlesource.com/platform/external/libhevc/+/f5b2fa243b4c45a4cd885e85f49ae548ab88c264"> + A-63522067</a></td> + <td>DoS</td> + <td>高</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-13197</td> - <td>A-64784973</td> - <td>DoS</td> - <td>高</td> - <td>6.0ã€6.0.1ã€7.0ã€7.1.1ã€7.1.2ã€8.0ã€8.1</td> + <td>CVE-2017-13197</td> + <td><a href="https://android.googlesource.com/platform/external/libhevc/+/0a714d3a14d256c6a5675d6fbd975ca26e9bc471"> + A-64784973</a></td> + <td>DoS</td> + <td>高</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-13199</td> - <td>A-33846679</td> - <td>DoS</td> - <td>高</td> - <td>8.0ã€8.1</td> + <td>CVE-2017-13199</td> + <td><a href="https://android.googlesource.com/platform/frameworks/base/+/42b2e419b48a26d2ba599d87e3a2a02c4aa625f4"> + A-33846679</a></td> + <td>DoS</td> + <td>高</td> + <td>8.0ã€8.1</td> </tr> </tbody></table> @@ -215,32 +238,38 @@ Android パートナーã«ã¯ã€æƒ…å ±å…¬é–‹ã®å°‘ãªãã¨ã‚‚ 1 ã‹æœˆå‰ã«ã™ <th>更新対象㮠AOSP ãƒãƒ¼ã‚¸ãƒ§ãƒ³</th> </tr> <tr> - <td>CVE-2017-13208</td> - <td>A-67474440</td> - <td>RCE</td> - <td>é‡å¤§</td> - <td>5.1.1ã€6.0ã€6.0.1ã€7.0ã€7.1.1ã€7.1.2ã€8.0ã€8.1</td> + <td>CVE-2017-13208</td> + <td><a href="https://android.googlesource.com/platform/system/core/+/b71335264a7c3629f80b7bf1f87375c75c42d868"> + A-67474440</a></td> + <td>RCE</td> + <td>é‡å¤§</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-13209</td> - <td>A-68217907</td> - <td>EoP</td> - <td>高</td> - <td>8.0ã€8.1</td> + <td>CVE-2017-13209</td> + <td><a href="https://android.googlesource.com/platform/system/libhidl/+/a4d0252ab5b6f6cc52a221538e1536c5b55c1fa7"> + A-68217907</a> +[<a href="https://android.googlesource.com/platform/system/tools/hidl/+/8539fc8ac94d5c92ef9df33675844ab294f68d61">2</a>] +[<a href="https://android.googlesource.com/platform/system/hwservicemanager/+/e1b4a889e8b84f5c13b76333d4de90dbe102a0de">3</a>]</td> + <td>EoP</td> + <td>高</td> + <td>8.0ã€8.1</td> </tr> <tr> - <td>CVE-2017-13210</td> - <td>A-67782345</td> - <td>EoP</td> - <td>高</td> - <td>5.1.1ã€6.0ã€6.0.1ã€7.0ã€7.1.1ã€7.1.2ã€8.0ã€8.1</td> + <td>CVE-2017-13210</td> + <td><a href="https://android.googlesource.com/platform/system/media/+/e770e378dc8e2320679272234285456ca2244a62"> + A-67782345</a></td> + <td>EoP</td> + <td>高</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-13211</td> - <td>A-65174158</td> - <td>DoS</td> - <td>高</td> - <td>8.0</td> + <td>CVE-2017-13211</td> + <td><a href="https://android.googlesource.com/platform/system/bt/+/181144a50114c824cfe3cdfd695c11a074673a5e"> + A-65174158</a></td> + <td>DoS</td> + <td>高</td> + <td>8.0</td> </tr> </tbody></table> @@ -274,7 +303,7 @@ Android パートナーã«ã¯ã€æƒ…å ±å…¬é–‹ã®å°‘ãªãã¨ã‚‚ 1 ã‹æœˆå‰ã«ã™ </tbody></table> <h3 id="kernel-components">カーãƒãƒ« コンãƒãƒ¼ãƒãƒ³ãƒˆ</h3> -<p>カーãƒãƒ« コンãƒãƒ¼ãƒãƒ³ãƒˆã®æœ€ã‚‚é‡å¤§ãªè„†å¼±æ€§ã¯ã€æ‚ªæ„ã®ã‚ã‚‹ãƒãƒ¼ã‚«ãƒ«ã‚¢ãƒ—リã«ã‚ˆã£ã¦ç‰¹æ¨©ãƒ—ãƒã‚»ã‚¹å†…ã§ä»»æ„ã®ã‚³ãƒ¼ãƒ‰ãŒå®Ÿè¡Œã•ã‚Œã‚‹ãŠãã‚ŒãŒã‚ã‚‹ã“ã¨ã§ã™ã€‚</p> +<p>カーãƒãƒ« コンãƒãƒ¼ãƒãƒ³ãƒˆã«é‡å¤§ãªè„†å¼±æ€§ãŒã‚ã‚‹ãŸã‚ã€æ‚ªæ„ã®ã‚ã‚‹ãƒãƒ¼ã‚«ãƒ«ã‚¢ãƒ—リã«ã‚ˆã£ã¦ç‰¹æ¨©ãƒ—ãƒã‚»ã‚¹å†…ã§ä»»æ„ã®ã‚³ãƒ¼ãƒ‰ãŒå®Ÿè¡Œã•ã‚Œã‚‹ãŠãã‚ŒãŒã‚ã‚Šã¾ã™ã€‚</p> <table> <colgroup><col width="17%" /> @@ -319,7 +348,7 @@ Android パートナーã«ã¯ã€æƒ…å ±å…¬é–‹ã®å°‘ãªãã¨ã‚‚ 1 ã‹æœˆå‰ã«ã™ <td>A-68266545<a href="#asterisk">*</a></td> <td>ID</td> <td>高</td> - <td>タイマー</td> + <td>高精度タイマー</td> </tr> </tbody></table> @@ -373,32 +402,6 @@ Android パートナーã«ã¯ã€æƒ…å ±å…¬é–‹ã®å°‘ãªãã¨ã‚‚ 1 ã‹æœˆå‰ã«ã™ </tr> </tbody></table> -<h3 id="mediatek-components">MediaTek コンãƒãƒ¼ãƒãƒ³ãƒˆ</h3> -<p>MediaTek コンãƒãƒ¼ãƒãƒ³ãƒˆã®æœ€ã‚‚é‡å¤§ãªè„†å¼±æ€§ã¯ã€æ‚ªæ„ã®ã‚ã‚‹ãƒãƒ¼ã‚«ãƒ«ã‚¢ãƒ—リã«ã‚ˆã£ã¦ç‰¹æ¨©ãƒ—ãƒã‚»ã‚¹å†…ã§ä»»æ„ã®ã‚³ãƒ¼ãƒ‰ãŒå®Ÿè¡Œã•ã‚Œã‚‹ãŠãã‚ŒãŒã‚ã‚‹ã“ã¨ã§ã™ã€‚</p> - -<table> - <colgroup><col width="17%" /> - <col width="19%" /> - <col width="9%" /> - <col width="14%" /> - <col width="39%" /> - </colgroup><tbody><tr> - <th>CVE</th> - <th>å‚ç…§</th> - <th>タイプ</th> - <th>é‡å¤§åº¦</th> - <th>コンãƒãƒ¼ãƒãƒ³ãƒˆ</th> - </tr> - <tr> - <td>CVE-2017-13225</td> - <td>A-38308024<a href="#asterisk">*</a><br /> - M-ALPS03495789</td> - <td>EoP</td> - <td>高</td> - <td>MTK Media</td> - </tr> -</tbody></table> - <h3 id="nvidia-components">NVIDIA コンãƒãƒ¼ãƒãƒ³ãƒˆ</h3> <p>NVIDIA コンãƒãƒ¼ãƒãƒ³ãƒˆã®æœ€ã‚‚é‡å¤§ãªè„†å¼±æ€§ã¯ã€æ‚ªæ„ã®ã‚ã‚‹ãƒãƒ¼ã‚«ãƒ«ã‚¢ãƒ—リã«ã‚ˆã£ã¦ç‰¹æ¨©ãƒ—ãƒã‚»ã‚¹å†…ã§ä»»æ„ã®ã‚³ãƒ¼ãƒ‰ãŒå®Ÿè¡Œã•ã‚Œã‚‹ãŠãã‚ŒãŒã‚ã‚‹ã“ã¨ã§ã™ã€‚</p> @@ -550,10 +553,10 @@ QC-CR#2060780</a></td> <li>[ro.build.version.security_patch]:[2018-01-05]</li> </ul> <p> -<strong>2. ã“ã®å…¬é–‹æƒ…å ±ã« 2 ã¤ã®ã‚»ã‚ュリティ パッムレベルãŒã‚ã‚‹ã®ã¯ãªãœã§ã™ã‹ï¼Ÿ</strong> +<strong>2. ã“ã®å…¬é–‹æƒ…å ±ã« 2 ã¤ã®ã‚»ã‚ュリティ パッãƒãƒ¬ãƒ™ãƒ«ãŒã‚ã‚‹ã®ã¯ãªãœã§ã™ã‹ï¼Ÿ</strong> </p> <p> -ã“ã®å…¬é–‹æƒ…å ±ã§ã¯ã€2 ã¤ã®ã‚»ã‚ュリティ パッムレベルを定義ã—ã¦ã„ã¾ã™ã€‚ã“ã‚Œã¯ã€ã™ã¹ã¦ã® Android æ載端末ã§åŒæ§˜ã®å•é¡ŒãŒç™ºç”Ÿã™ã‚‹ä¸€éƒ¨ã®è„†å¼±æ€§ã‚’サブセットã¨ã—ã€Android パートナーãŒè¿…速ã‹ã¤æŸ”軟ã«ä¿®æ£ã§ãるよã†ã«ã™ã‚‹ãŸã‚ã§ã™ã€‚Android パートナーã«ã¯ã€ã“ã®å…¬é–‹æƒ…å ±ã«æŽ²è¼‰ã•ã‚Œã¦ã„ã‚‹å•é¡Œã‚’ã™ã¹ã¦ä¿®æ£ã—ã€æœ€æ–°ã®ã‚»ã‚ュリティ パッãƒãƒ¬ãƒ™ãƒ«ã‚’使用ã™ã‚‹ã“ã¨ãŒæŽ¨å¥¨ã•ã‚Œã¦ã„ã¾ã™ã€‚ +ã“ã®å…¬é–‹æƒ…å ±ã§ã¯ã€2 ã¤ã®ã‚»ã‚ュリティ パッãƒãƒ¬ãƒ™ãƒ«ã‚’定義ã—ã¦ã„ã¾ã™ã€‚ã“ã‚Œã¯ã€ã™ã¹ã¦ã® Android æ載端末ã§åŒæ§˜ã®å•é¡ŒãŒç™ºç”Ÿã™ã‚‹ä¸€éƒ¨ã®è„†å¼±æ€§ã‚’サブセットã¨ã—ã€Android パートナーãŒè¿…速ã‹ã¤æŸ”軟ã«ä¿®æ£ã§ãるよã†ã«ã™ã‚‹ãŸã‚ã§ã™ã€‚Android パートナーã«ã¯ã€ã“ã®å…¬é–‹æƒ…å ±ã«æŽ²è¼‰ã•ã‚Œã¦ã„ã‚‹å•é¡Œã‚’ã™ã¹ã¦ä¿®æ£ã—ã€æœ€æ–°ã®ã‚»ã‚ュリティ パッãƒãƒ¬ãƒ™ãƒ«ã‚’使用ã™ã‚‹ã“ã¨ãŒæŽ¨å¥¨ã•ã‚Œã¦ã„ã¾ã™ã€‚ </p> <ul> <li>2018-01-01 ã®ã‚»ã‚ュリティ パッãƒãƒ¬ãƒ™ãƒ«ã‚’使用ã™ã‚‹ç«¯æœ«ã§ã¯ã€ãã®ã‚»ã‚ュリティ パッãƒãƒ¬ãƒ™ãƒ«ã«é–¢é€£ã™ã‚‹ã™ã¹ã¦ã®å•é¡Œã¨ã€ãれ以å‰ã®ã‚»ã‚ュリティã«é–¢ã™ã‚‹å…¬é–‹æƒ…å ±ã§å ±å‘Šã•ã‚ŒãŸã™ã¹ã¦ã®å•é¡Œã®ä¿®æ£ã‚’å«ã‚ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚</li> @@ -563,10 +566,10 @@ QC-CR#2060780</a></td> パートナーã«ã¯ã€å¯¾å‡¦ã™ã‚‹ã™ã¹ã¦ã®å•é¡Œã®ä¿®æ£ã‚’ 1 ã¤ã®ã‚¢ãƒƒãƒ—デートã«ã¾ã¨ã‚ã¦æä¾›ã™ã‚‹ã“ã¨ãŒæŽ¨å¥¨ã•ã‚Œã¦ã„ã¾ã™ã€‚ </p> <p id="type"> -<strong>3. 「タイプã€åˆ—ã®é …ç›®ã¯ã©ã†ã„ã†æ„味ã§ã™ã‹ï¼Ÿ<em></em></strong> +<strong>3. 「タイプã€<em></em>列ã®é …ç›®ã¯ã©ã†ã„ã†æ„味ã§ã™ã‹ï¼Ÿ</strong> </p> <p> -脆弱性ã®è©³ç´°ã®è¡¨ã§ã€Œã‚¿ã‚¤ãƒ—ã€åˆ—ã«è¨˜è¼‰ã—ãŸé …ç›®ã¯ã€ã‚»ã‚ュリティã®è„†å¼±æ€§ã®åˆ†é¡žã‚’示ã—ã¦ã„ã¾ã™ã€‚<em></em> +脆弱性ã®è©³ç´°ã®è¡¨ã§ã€Œã‚¿ã‚¤ãƒ—ã€<em></em>列ã«è¨˜è¼‰ã—ãŸé …ç›®ã¯ã€ã‚»ã‚ュリティã®è„†å¼±æ€§ã®åˆ†é¡žã‚’示ã—ã¦ã„ã¾ã™ã€‚ </p> <table> <colgroup><col width="25%" /> @@ -592,15 +595,15 @@ QC-CR#2060780</a></td> <td>サービス拒å¦</td> </tr> <tr> - <td>N/A</td> + <td>ãªã—</td> <td>該当ã™ã‚‹åˆ†é¡žãªã—</td> </tr> </tbody></table> <p> -<strong>4. 「å‚ç…§ã€åˆ—ã®é …ç›®ã¯ã©ã†ã„ã†æ„味ã§ã™ã‹ï¼Ÿ<em></em></strong> +<strong>4. 「å‚ç…§ã€<em></em>列ã®é …ç›®ã¯ã©ã†ã„ã†æ„味ã§ã™ã‹ï¼Ÿ</strong> </p> <p> -脆弱性ã®è©³ç´°ã®è¡¨ã§ã€Œå‚ç…§ã€åˆ—ã«è¨˜è¼‰ã—ãŸé …ç›®ã«ã¯ã€ãã®å‚照番å·ãŒå±žã™çµ„織を示ã™æŽ¥é 辞をå«ã‚ã¦ã„ã‚‹å ´åˆãŒã‚ã‚Šã¾ã™ã€‚<em></em> +脆弱性ã®è©³ç´°ã®è¡¨ã§ã€Œå‚ç…§ã€<em></em>列ã«è¨˜è¼‰ã—ãŸé …ç›®ã«ã¯ã€ãã®å‚照番å·ãŒå±žã™çµ„織を示ã™æŽ¥é 辞をå«ã‚ã¦ã„ã‚‹å ´åˆãŒã‚ã‚Šã¾ã™ã€‚ </p> <table> <colgroup><col width="25%" /> @@ -631,10 +634,10 @@ QC-CR#2060780</a></td> </tr> </tbody></table> <p id="asterisk"> -<strong>5. 「å‚ç…§ã€åˆ—ã® Android ãƒã‚° ID ã®æ¨ªã«ã‚る「*ã€ã¯ã©ã†ã„ã†æ„味ã§ã™ã‹ï¼Ÿ<em></em></strong> +<strong>5. 「å‚ç…§ã€<em></em>列㮠Android ãƒã‚° ID ã®æ¨ªã«ã‚る「*ã€ã¯ã©ã†ã„ã†æ„味ã§ã™ã‹ï¼Ÿ</strong> </p> <p> -公開ã•ã‚Œã¦ã„ãªã„å•é¡Œã«ã¯ã€ã€Œå‚ç…§ã€åˆ—ã® Android ãƒã‚° ID ã®æ¨ªã«ã€Œ*ã€ã‚’付ã‘ã¦ã„ã¾ã™ã€‚<em></em>ã“ã®å•é¡Œã®ã‚¢ãƒƒãƒ—デートã¯ã€é€šå¸¸ã€<a href="https://developers.google.com/android/nexus/drivers">Google デベãƒãƒƒãƒ‘ー サイト</a>ã‹ã‚‰å…¥æ‰‹ã§ãã‚‹ Nexus 端末用最新ãƒã‚¤ãƒŠãƒª ドライãƒã«å«ã¾ã‚Œã¦ã„ã¾ã™ã€‚ +公開ã•ã‚Œã¦ã„ãªã„å•é¡Œã«ã¯ã€ã€Œå‚ç…§ã€<em></em>列㮠Android ãƒã‚° ID ã®æ¨ªã«ã€Œ*ã€ã‚’付ã‘ã¦ã„ã¾ã™ã€‚ã“ã®å•é¡Œã®ã‚¢ãƒƒãƒ—デートã¯ã€é€šå¸¸ã€<a href="https://developers.google.com/android/nexus/drivers">Google デベãƒãƒƒãƒ‘ー サイト</a>ã‹ã‚‰å…¥æ‰‹ã§ãã‚‹ Nexus 端末用最新ãƒã‚¤ãƒŠãƒª ドライãƒã«å«ã¾ã‚Œã¦ã„ã¾ã™ã€‚ </p> <p> <strong>6. ã‚»ã‚ュリティã®è„†å¼±æ€§ãŒã€ã“ã®å…¬é–‹æƒ…å ±ã¨ç«¯æœ«ã‚„パートナーã®ã‚»ã‚ュリティã«é–¢ã™ã‚‹å…¬é–‹æƒ…å ±ï¼ˆPixel / Nexus ã®ã‚»ã‚ュリティã«é–¢ã™ã‚‹å…¬é–‹æƒ…å ±ãªã©ï¼‰ã«åˆ†ã‘られã¦ã„ã‚‹ã®ã¯ãªãœã§ã™ã‹ï¼Ÿ</strong> @@ -644,9 +647,9 @@ Android æ載端末ã®æœ€æ–°ã®ã‚»ã‚ュリティ パッãƒãƒ¬ãƒ™ãƒ«ã‚’宣言ã </p> <h2 id="versions">ãƒãƒ¼ã‚¸ãƒ§ãƒ³</h2> <table> - <colgroup><col width="25%" /> + <colgroup><col width="15%" /> <col width="25%" /> - <col width="50%" /> + <col width="60%" /> </colgroup><tbody><tr> <th>ãƒãƒ¼ã‚¸ãƒ§ãƒ³</th> <th>日付</th> @@ -657,6 +660,20 @@ Android æ載端末ã®æœ€æ–°ã®ã‚»ã‚ュリティ パッãƒãƒ¬ãƒ™ãƒ«ã‚’宣言ã <td>2018 å¹´ 1 月 2 æ—¥</td> <td>æƒ…å ±å…¬é–‹</td> </tr> -</tbody></table> + <tr> + <td>1.1</td> + <td>2018 å¹´ 1 月 3 æ—¥</td> + <td>å…¬é–‹æƒ…å ±ã‚’æ›´æ–°ã— CVE-2017-13218 ã«é–¢ã™ã‚‹ãŠçŸ¥ã‚‰ã›ã‚’è¿½åŠ </td> + </tr> + <tr> + <td>1.2</td> + <td>2018 å¹´ 1 月 5 æ—¥</td> + <td>å…¬é–‹æƒ…å ±ã‚’æ”¹è¨‚ã— AOSP ãƒªãƒ³ã‚¯ã‚’è¿½åŠ </td> + </tr> + <tr> + <td>1.3</td> + <td>2018 å¹´ 1 月 29 æ—¥</td> + <td>CVE-2017-13225 ã‚’ <a href="/security/bulletin/pixel/">Pixel / Nexus ã®ã‚»ã‚ュリティã«é–¢ã™ã‚‹å…¬é–‹æƒ…å ±</a>ã«ç§»å‹•</td> +</tr></tbody></table> </body></html>
\ No newline at end of file diff --git a/ja/security/bulletin/pixel/2017-10-01.html b/ja/security/bulletin/pixel/2017-10-01.html index 44f5f2dc..fcad3ba0 100644 --- a/ja/security/bulletin/pixel/2017-10-01.html +++ b/ja/security/bulletin/pixel/2017-10-01.html @@ -161,7 +161,7 @@ <th>å‚ç…§</th> <th>タイプ</th> <th>é‡å¤§åº¦</th> - <th>æ›´æ–°ã•ã‚ŒãŸ AOSP ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³</th> + <th>更新対象㮠AOSP ãƒãƒ¼ã‚¸ãƒ§ãƒ³</th> </tr> <tr> <td>CVE-2017-0822</td> @@ -554,7 +554,7 @@ QC-CR#2016076</a></td> <td>サービス拒å¦</td> </tr> <tr> - <td>N/A</td> + <td>ãªã—</td> <td>該当ã™ã‚‹åˆ†é¡žãªã—</td> </tr> </tbody></table> diff --git a/ja/security/bulletin/pixel/2018-03-01.html b/ja/security/bulletin/pixel/2018-03-01.html new file mode 100644 index 00000000..73168b45 --- /dev/null +++ b/ja/security/bulletin/pixel/2018-03-01.html @@ -0,0 +1,653 @@ +<html devsite><head> + <title>Pixel  /  Nexus ã®ã‚»ã‚ュリティã«é–¢ã™ã‚‹å…¬é–‹æƒ…å ± - 2018 å¹´ 3 月</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>2018 å¹´ 3 月 5 日公開</em></p> + +<p> +Pixel / Nexus ã®ã‚»ã‚ュリティã«é–¢ã™ã‚‹å…¬é–‹æƒ…å ±ã«ã¯ã€<a href="https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices">サãƒãƒ¼ãƒˆå¯¾è±¡ã® Google Pixel 端末㨠Nexus 端末</a>（Google 端末）ã«å½±éŸ¿ã‚’与ãˆã‚‹ã‚»ã‚ュリティã®è„†å¼±æ€§ã‚„機能強化ã®è©³ç´°ã‚’掲載ã—ã¦ã„ã¾ã™ã€‚Google 端末ã§ã¯ã€ã‚»ã‚ュリティ パッãƒãƒ¬ãƒ™ãƒ« 2018-03-05 以é™ã«ãŠã„ã¦ã€ã“ã®å…¬é–‹æƒ…å ±ã«æŽ²è¼‰ã•ã‚Œã¦ã„ã‚‹ã™ã¹ã¦ã®å•é¡Œã¨ã€<a href="/security/bulletin/2018-03-01">2018 å¹´ 3 月㮠Android ã®ã‚»ã‚ュリティã«é–¢ã™ã‚‹å…¬é–‹æƒ…å ±</a>ã«æŽ²è¼‰ã•ã‚Œã¦ã„ã‚‹ã™ã¹ã¦ã®å•é¡Œã«å¯¾å‡¦ã—ã¦ã„ã¾ã™ã€‚端末ã®ã‚»ã‚ュリティ パッãƒãƒ¬ãƒ™ãƒ«ã‚’確èªã™ã‚‹æ–¹æ³•ã«ã¤ã„ã¦ã¯ã€<a href="https://support.google.com/pixelphone/answer/4457705">Android ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã‚’確èªã—ã¦æ›´æ–°ã™ã‚‹</a>ã‚’ã”覧ãã ã•ã„。</p> +<p> +パッãƒãƒ¬ãƒ™ãƒ« 2018-03-05 ã¸ã®ã‚¢ãƒƒãƒ—デートã¯ã€ã‚µãƒãƒ¼ãƒˆå¯¾è±¡ã®ã™ã¹ã¦ã® Google 端末ã«é€ä¿¡ã•ã‚Œã¾ã™ã€‚ã”利用ã®ç«¯æœ«ã«ã“ã®ã‚¢ãƒƒãƒ—デートをé©ç”¨ã™ã‚‹ã“ã¨ã‚’ã™ã¹ã¦ã®ãƒ¦ãƒ¼ã‚¶ãƒ¼ã«ãŠã™ã™ã‚ã—ã¾ã™ã€‚ +</p> +<p class="note"> +<strong>注:</strong> Google 端末ã®ãƒ•ã‚¡ãƒ¼ãƒ ウェア イメージã¯ã€<a href="https://developers.google.com/android/nexus/images">Google デベãƒãƒƒãƒ‘ー サイト</a>ã§å…¥æ‰‹ã§ãã¾ã™ã€‚ +</p> + +<h2 id="announcements">ãŠçŸ¥ã‚‰ã›</h2> +<p><a href="/security/bulletin/2018-03-01">2018 å¹´ 3 月㮠Android ã®ã‚»ã‚ュリティã«é–¢ã™ã‚‹å…¬é–‹æƒ…å ±</a>ã«æŽ²è¼‰ã•ã‚Œã¦ã„ã‚‹ã‚»ã‚ュリティã®è„†å¼±æ€§ã«åŠ ãˆã¦ã€Google 端末ã«ã¯ã€ä¸‹è¨˜ã®ã‚»ã‚ュリティã®è„†å¼±æ€§ã«å¯¾ã™ã‚‹ãƒ‘ッãƒã‚‚å«ã¾ã‚Œã¦ã„ã¾ã™ã€‚パートナーã«ã¯å°‘ãªãã¨ã‚‚ 1 ã‹æœˆå‰ã«ä¸‹è¨˜ã®å•é¡ŒãŒé€šçŸ¥ã•ã‚Œã¦ãŠã‚Šã€ãƒ‘ートナーã¯ç«¯æœ«ã®ã‚¢ãƒƒãƒ—デートã«ã“ã†ã—ãŸãƒ‘ッãƒã‚’組ã¿è¾¼ã‚€ã“ã¨ãŒã§ãã¾ã™ã€‚</p> + +<h2 id="security-patches">ã‚»ã‚ュリティ パッãƒ</h2> +<p> +脆弱性ã¯ã€å½±éŸ¿ã‚’å—ã‘るコンãƒãƒ¼ãƒãƒ³ãƒˆã”ã¨ã«åˆ†é¡žã—ã¦ã„ã¾ã™ã€‚å•é¡Œã®å†…容ã«ã¤ã„ã¦èª¬æ˜Žã—ã€CVEã€é–¢é€£ã™ã‚‹å‚照先ã€<a href="#type">脆弱性ã®ã‚¿ã‚¤ãƒ—</a>ã€<a href="https://source.android.com/security/overview/updates-resources.html#severity">é‡å¤§åº¦</a>ã€æ›´æ–°å¯¾è±¡ã® AOSP（Android オープンソース プãƒã‚¸ã‚§ã‚¯ãƒˆï¼‰ãƒãƒ¼ã‚¸ãƒ§ãƒ³ï¼ˆè©²å½“ã™ã‚‹å ´åˆï¼‰ã‚’表ã«ã¾ã¨ã‚ã¦ã„ã¾ã™ã€‚該当ã™ã‚‹å ´åˆã¯ã€ãƒã‚° ID ã®æ¬„ã«ã€ãã®å•é¡Œã«å¯¾å‡¦ã—ãŸä¸€èˆ¬å…¬é–‹ã•ã‚Œã¦ã„る変更（AOSP ã®å¤‰æ›´ã®ä¸€è¦§ãªã©ï¼‰ã¸ã®ãƒªãƒ³ã‚¯ãŒã‚ã‚Šã¾ã™ã€‚複数ã®å¤‰æ›´ãŒåŒã˜ãƒã‚°ã«é–¢ä¿‚ã™ã‚‹å ´åˆã¯ã€ãƒã‚° ID ã®å¾Œã«ç¶šã番å·ã§ã€è¿½åŠ ã®å‚照先ã¸ã®ãƒªãƒ³ã‚¯ã‚’示ã—ã¾ã™ã€‚ +</p> + +<h3 id="framework">フレームワーク</h3> + +<table> + <colgroup><col width="17%" /> + <col width="19%" /> + <col width="9%" /> + <col width="14%" /> + <col width="39%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>å‚ç…§</th> + <th>タイプ</th> + <th>é‡å¤§åº¦</th> + <th>更新対象㮠AOSP ãƒãƒ¼ã‚¸ãƒ§ãƒ³</th> + </tr> + <tr> + <td>CVE-2017-13263</td> + <td>A-69383160</td> + <td>EoP</td> + <td>ä¸</td> + <td>8.0ã€8.1</td> + </tr> +</tbody></table> + +<h3 id="media-framework">メディア フレームワーク</h3> + +<table> + <colgroup><col width="17%" /> + <col width="19%" /> + <col width="9%" /> + <col width="14%" /> + <col width="39%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>å‚ç…§</th> + <th>タイプ</th> + <th>é‡å¤§åº¦</th> + <th>更新対象㮠AOSP ãƒãƒ¼ã‚¸ãƒ§ãƒ³</th> + </tr> + <tr> + <td rowspan="2">CVE-2017-13264</td> + <td rowspan="2">A-70294343</td> + <td>NSI</td> + <td>NSI</td> + <td>7.0ã€7.1.1ã€7.1.2ã€8.0ã€8.1</td> + </tr> + <tr> + <td>DoS</td> + <td>高</td> + <td>6.0ã€6.0.1</td> + </tr> + <tr> + <td rowspan="2">CVE-2017-13254</td> + <td rowspan="2">A-70239507</td> + <td>NSI</td> + <td>NSI</td> + <td>7.0ã€7.1.1ã€7.1.2ã€8.0ã€8.1</td> + </tr> + <tr> + <td>DoS</td> + <td>高</td> + <td>5.1.1ã€6.0ã€6.0.1</td> + </tr> +</tbody></table> + +<h3 id="system">システム</h3> + +<table> + <colgroup><col width="17%" /> + <col width="19%" /> + <col width="9%" /> + <col width="14%" /> + <col width="39%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>å‚ç…§</th> + <th>タイプ</th> + <th>é‡å¤§åº¦</th> + <th>更新対象㮠AOSP ãƒãƒ¼ã‚¸ãƒ§ãƒ³</th> + </tr> + <tr> + <td>CVE-2017-13265</td> + <td>A-36232423</td> + <td>EoP</td> + <td>ä¸</td> + <td>7.0ã€7.1.1ã€7.1.2ã€8.0ã€8.1</td> + </tr> + <tr> + <td>CVE-2017-13266</td> + <td>A-69478941</td> + <td>EoP</td> + <td>ä¸</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-13268</td> + <td>A-67058064</td> + <td>ID</td> + <td>ä¸</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-13269</td> + <td>A-68818034</td> + <td>ID</td> + <td>ä¸</td> + <td>5.1.1ã€6.0ã€6.0.1ã€7.0ã€7.1.1ã€7.1.2ã€8.0ã€8.1</td> + </tr> +</tbody></table> + +<h3 id="kernel-components">カーãƒãƒ« コンãƒãƒ¼ãƒãƒ³ãƒˆ</h3> + +<table> + <colgroup><col width="17%" /> + <col width="19%" /> + <col width="9%" /> + <col width="14%" /> + <col width="39%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>å‚ç…§</th> + <th>タイプ</th> + <th>é‡å¤§åº¦</th> + <th>コンãƒãƒ¼ãƒãƒ³ãƒˆ</th> + </tr> + <tr> + <td>CVE-2017-5754</td> + <td>A-69856074<a href="#asterisk">*</a></td> + <td>ID</td> + <td>高</td> + <td>メモリ マッピング</td> + </tr> + <tr> + <td>CVE-2017-13270</td> + <td>A-69474744<a href="#asterisk">*</a></td> + <td>EoP</td> + <td>ä¸</td> + <td>Mnh_sm ドライãƒ</td> + </tr> + <tr> + <td>CVE-2017-13271</td> + <td>A-69006799<a href="#asterisk">*</a></td> + <td>EoP</td> + <td>ä¸</td> + <td>Mnh_sm ドライãƒ</td> + </tr> + <tr> + <td>CVE-2017-16527</td> + <td>A-69051382<br /> +<a href="https://github.com/torvalds/linux/commit/124751d5e63c823092060074bd0abaae61aaa9c4"> +アップストリームカーãƒãƒ«</a></td> + <td>EoP</td> + <td>ä¸</td> + <td>USB サウンド ドライãƒ</td> + </tr> + <tr> + <td>CVE-2017-15649</td> + <td>A-69160446<br /> +<a href="http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=008ba2a13f2d04c947adc536d19debb8fe66f110"> +アップストリームカーãƒãƒ«</a> +[<a href="http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4971613c1639d8e5f102c4e797c3bf8f83a5a69e">2</a>]</td> + <td>EoP</td> + <td>ä¸</td> + <td>ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ ドライãƒ</td> + </tr> + <tr> + <td>CVE-2017-1000111</td> + <td>A-68806121<br /> +<a href="http://patchwork.ozlabs.org/patch/800274/">アップストリームカーãƒãƒ«</a></td> + <td>EoP</td> + <td>ä¸</td> + <td>ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ ドライãƒ</td> + </tr> +</tbody></table> + +<h3 id="nvidia-components">NVIDIA コンãƒãƒ¼ãƒãƒ³ãƒˆ</h3> + +<table> + <colgroup><col width="17%" /> + <col width="19%" /> + <col width="9%" /> + <col width="14%" /> + <col width="39%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>å‚ç…§</th> + <th>タイプ</th> + <th>é‡å¤§åº¦</th> + <th>コンãƒãƒ¼ãƒãƒ³ãƒˆ</th> + </tr> + <tr> + <td>CVE-2017-6287</td> + <td>A-64893264<a href="#asterisk">*</a><br /> + N-CVE-2017-6287</td> + <td>ID</td> + <td>ä¸</td> + <td>メディア フレームワーク</td> + </tr> + <tr> + <td>CVE-2017-6285</td> + <td>A-64893156<a href="#asterisk">*</a><br /> + N-CVE-2017-6285</td> + <td>ID</td> + <td>ä¸</td> + <td>メディア フレームワーク</td> + </tr> + <tr> + <td>CVE-2017-6288</td> + <td>A-65482562<a href="#asterisk">*</a><br /> + N-CVE-2017-6288</td> + <td>ID</td> + <td>ä¸</td> + <td>メディア フレームワーク</td> + </tr> +</tbody></table> + +<h3 id="qualcomm-components">Qualcomm コンãƒãƒ¼ãƒãƒ³ãƒˆ</h3> + +<table> + <colgroup><col width="17%" /> + <col width="19%" /> + <col width="9%" /> + <col width="14%" /> + <col width="39%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>å‚ç…§</th> + <th>タイプ</th> + <th>é‡å¤§åº¦</th> + <th>コンãƒãƒ¼ãƒãƒ³ãƒˆ</th> + </tr> + <tr> + <td>CVE-2017-18061</td> + <td>A-70237701<br /> +<a href="https://source.codeaurora.org/quic/la/kernel/msm-3.18/commit/?id=b65cf2a007e88fe86dbd6d3269682fc585a4130f"> +QC-CR#2117246</a></td> + <td>EoP</td> + <td>ä¸</td> + <td>Wil6210</td> + </tr> + <tr> + <td>CVE-2017-18050</td> + <td>A-70237697<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=63b57442d65dfdb4b4634ff32059b1bca8c72fb7"> +QC-CR#2119443</a></td> + <td>EoP</td> + <td>ä¸</td> + <td>Wma 管ç†</td> + </tr> + <tr> + <td>CVE-2017-18054</td> + <td>A-70237694<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=6eefc756612e39fab49ff719b3dc9b94def53396"> +QC-CR#2119432</a></td> + <td>EoP</td> + <td>ä¸</td> + <td>Wma</td> + </tr> + <tr> + <td>CVE-2017-18055</td> + <td>A-70237693<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=50a0554d12cff58b3ffbd51d3194304244b87023"> +QC-CR#2119430</a></td> + <td>EoP</td> + <td>ä¸</td> + <td>Wma</td> + </tr> + <tr> + <td>CVE-2017-18065</td> + <td>A-70237685<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=a8bc0f90ef49ea0aee90047a17772e4eebff259a"> +QC-CR#2113423</a></td> + <td>EoP</td> + <td>ä¸</td> + <td>Wma</td> + </tr> + <tr> + <td>CVE-2017-18066</td> + <td>A-70235107<br /> +<a href="https://source.codeaurora.org/quic/la/kernel/msm-3.18/commit/?id=ff11f44c0c10c94170f03a8698f73f7e08b74625"> +QC-CR#2107976</a></td> + <td>EoP</td> + <td>ä¸</td> + <td>é›»æºãƒ‰ãƒ©ã‚¤ãƒ</td> + </tr> + <tr> + <td>CVE-2017-18062</td> + <td>A-68992451<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=d7927eb7c9c2d79a3e24cddd1e9447ab98bf6700"> +QC-CR#2115375</a></td> + <td>EoP</td> + <td>ä¸</td> + <td>Wma</td> + </tr> + <tr> + <td>CVE-2018-3561</td> + <td>A-68870904<a href="#asterisk">*</a><br /> + QC-CR#2068569</td> + <td>EoP</td> + <td>ä¸</td> + <td>Diagchar</td> + </tr> + <tr> + <td>CVE-2018-3560</td> + <td>A-68664502<a href="#asterisk">*</a><br /> + QC-CR#2142216</td> + <td>EoP</td> + <td>ä¸</td> + <td>Qdsp6v2 サウンド ドライãƒ</td> + </tr> + <tr> + <td>CVE-2017-15834</td> + <td>A-70237704<br /> +<a href="https://source.codeaurora.org/quic/la/kernel/msm-3.18/commit/?id=2e1b54e38f1516e70d9f6581c4f1ee935effb903"> +QC-CR#2111858</a></td> + <td>EoP</td> + <td>ä¸</td> + <td>Diagchar</td> + </tr> + <tr> + <td>CVE-2017-15833</td> + <td>A-70237702<br /> +<a href="https://source.codeaurora.org/quic/la/kernel/msm-3.10/commit/?id=51ce6aec73d80e1f1fcc9c7fa71e9c2fcbdbc0fd"> +QC-CR#2059835</a></td> + <td>EoP</td> + <td>ä¸</td> + <td>é›»æºãƒ‰ãƒ©ã‚¤ãƒ</td> + </tr> + <tr> + <td>CVE-2017-15831</td> + <td>A-70237687<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=31e6a657320e4299c659e3d57d38a89afe8c1ce1"> +QC-CR#2114255</a></td> + <td>EoP</td> + <td>ä¸</td> + <td>Wma</td> + </tr> + <tr> + <td>CVE-2017-15830</td> + <td>A-70237719<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=8a7a2a9c5d203e3395811963061c79d3bc257ebe"> +QC-CR#2120725</a></td> + <td>EoP</td> + <td>ä¸</td> + <td>sme ドライãƒ</td> + </tr> + <tr> + <td>CVE-2017-14889</td> + <td>A-70237700<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=e11e9dc8298dc0632050cacce96e9652d017f755"> +QC-CR#2119803</a></td> + <td>EoP</td> + <td>ä¸</td> + <td>Wma</td> + </tr> + <tr> + <td>CVE-2017-14887</td> + <td>A-70237715<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=4ce28e7c85f89e2c3555ec840b6adda47bd5dab0"> +QC-CR#2119673</a></td> + <td>EoP</td> + <td>ä¸</td> + <td>WLAN</td> + </tr> + <tr> + <td>CVE-2017-14879</td> + <td>A-63851638<a href="#asterisk">*</a><br /> + QC-CR#2056307</td> + <td>EoP</td> + <td>ä¸</td> + <td>IPA</td> + </tr> + <tr> + <td>CVE-2017-11082</td> + <td>A-66937387<br /> +<a href="https://www.codeaurora.org/gitweb/quic/la/?p=kernel/msm-3.10.git;a=commit;h=2d4f8cd8d11f8fb1491a20d7e316cc0fd03eeb59"> +QC-CR#2071560</a></td> + <td>EoP</td> + <td>ä¸</td> + <td>WLAN</td> + </tr> + <tr> + <td>CVE-2017-11074</td> + <td>A-68940798<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/prima/commit/?id=f5ae7b35c90f14b7e66b3a91d4fb247563a8a22b"> +QC-CR#2049138</a></td> + <td>EoP</td> + <td>ä¸</td> + <td>WLAN</td> + </tr> + <tr> + <td>CVE-2017-18052</td> + <td>A-70237712<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=c04c4870bd86a5f878553d7acf207388f3d6c3bd"> +QC-CR#2119439</a></td> + <td>ID</td> + <td>ä¸</td> + <td>WLAN</td> + </tr> + <tr> + <td>CVE-2017-18057</td> + <td>A-70237709<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=24d41d2bd3d98325b3800345f4ba27a334b3894b"> +QC-CR#2119403</a></td> + <td>ID</td> + <td>ä¸</td> + <td>WLAN</td> + </tr> + <tr> + <td>CVE-2017-18059</td> + <td>A-70237708<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=217705da7726002ffe61dad51a6c9cc97c52f649"> +QC-CR#2119399</a></td> + <td>ID</td> + <td>ä¸</td> + <td>WLAN</td> + </tr> + <tr> + <td>CVE-2017-18060</td> + <td>A-70237707<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=f3d81bd0b3cb992c214d94196b33168b02589c6b"> +QC-CR#2119394</a></td> + <td>ID</td> + <td>ä¸</td> + <td>WLAN</td> + </tr> + <tr> + <td>CVE-2017-18051</td> + <td>A-70237696<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=38fba6a9f6ca3c7bf0c4c1bd84fa2b89fbcaeb93"> +QC-CR#2119442</a></td> + <td>ID</td> + <td>ä¸</td> + <td>WLAN</td> + </tr> + <tr> + <td>CVE-2017-18053</td> + <td>A-70237695<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=da1c6e996ac7635c202296e31118f088f9427947"> +QC-CR#2119434</a></td> + <td>ID</td> + <td>ä¸</td> + <td>WLAN</td> + </tr> + <tr> + <td>CVE-2017-18058</td> + <td>A-70237690<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=d6d42a10d4abf09299cdfacdd8aed5c26731b5ff"> +QC-CR#2119401</a></td> + <td>ID</td> + <td>ä¸</td> + <td>WLAN</td> + </tr> + <tr> + <td>CVE-2017-15855</td> + <td>A-38232131<a href="#asterisk">*</a><br /> + QC-CR#2139514</td> + <td>ID</td> + <td>ä¸</td> + <td>Camera_v2 ドライãƒ</td> + </tr> + <tr> + <td>CVE-2017-15814</td> + <td>A-64836865<a href="#asterisk">*</a><br /> + QC-CR#2092793</td> + <td>ID</td> + <td>ä¸</td> + <td>Camera_v2 ドライãƒ</td> + </tr> +</tbody></table> + +<h2 id="functional-updates">機能ã®æ›´æ–°</h2> +<p> +影響をå—ã‘ã‚‹ Pixel 端末ã«ã¯ã€Pixel 端末ã®ã‚»ã‚ュリティã«é–¢ä¿‚ã—ãªã„機能ã®å•é¡Œã«å¯¾å‡¦ã™ã‚‹ä¸‹è¨˜ã®ã‚¢ãƒƒãƒ—デートãŒçµ„ã¿è¾¼ã¾ã‚Œã¦ã„ã¾ã™ã€‚関連ã™ã‚‹å‚照先ã€å½±éŸ¿ã‚’å—ã‘るカテゴリ（Bluetooth やモãƒã‚¤ãƒ«ãƒ‡ãƒ¼ã‚¿ãªã©ï¼‰ã€å•é¡Œã®æ¦‚è¦ã‚’下記ã®è¡¨ã«ã¾ã¨ã‚ã¦ã„ã¾ã™ã€‚ +</p> + +<table> + <tbody><tr> + <th>å‚ç…§</th> + <th>カテゴリ</th> + <th>改善内容</th> + <th>端末</th> + </tr> + <tr> + <td>A-70491468</td> + <td>パフォーマンス</td> + <td>指紋ã§ã®ãƒãƒƒã‚¯è§£é™¤ã«ã‚ˆã‚Šç”»é¢å¾©å¸°ã®ãƒ‘フォーマンスをå‘上</td> + <td>Pixel 2ã€Pixel 2 XL</td> + </tr> + <tr> + <td>A-69307875</td> + <td>オーディオ</td> + <td>動画を撮影ã™ã‚‹éš›ã®ã‚ªãƒ¼ãƒ‡ã‚£ã‚ªæ€§èƒ½ã‚’å‘上</td> + <td>Pixel 2 XL</td> + </tr> + <tr> + <td>A-70641186</td> + <td>レãƒãƒ¼ãƒˆ</td> + <td>クラッシュ レãƒãƒ¼ãƒˆã‚’改善</td> + <td>Pixel 2ã€Pixel 2 XL</td> + </tr> +</tbody></table> + +<h2 id="common-questions-and-answers">一般的ãªè³ªå•ã¨å›žç”</h2> +<p> +上記ã®å…¬é–‹æƒ…å ±ã«å¯¾ã™ã‚‹ä¸€èˆ¬çš„ãªè³ªå•ã«ã¤ã„ã¦ã€ä»¥ä¸‹ã§å›žç”ã—ã¾ã™ã€‚ +</p> +<p> +<strong>1. 上記ã®å•é¡Œã«å¯¾å‡¦ã™ã‚‹ã‚ˆã†ã«ç«¯æœ«ãŒæ›´æ–°ã•ã‚Œã¦ã„ã‚‹ã‹ã©ã†ã‹ã‚’確ã‹ã‚ã‚‹ã«ã¯ã€ã©ã†ã™ã‚Œã°ã‚ˆã„ã§ã™ã‹ï¼Ÿ +</strong> +</p> +<p> +ã‚»ã‚ュリティ パッãƒãƒ¬ãƒ™ãƒ« 2018-03-05 以é™ã§ã¯ã€ã‚»ã‚ュリティ パッãƒãƒ¬ãƒ™ãƒ« 2018-03-05ã€ãŠã‚ˆã³ãれ以å‰ã®ã™ã¹ã¦ã®ãƒ‘ッãƒãƒ¬ãƒ™ãƒ«ã«é–¢é€£ã™ã‚‹ã™ã¹ã¦ã®å•é¡Œã«å¯¾å‡¦ã—ã¦ã„ã¾ã™ã€‚端末ã®ã‚»ã‚ュリティ パッãƒãƒ¬ãƒ™ãƒ«ã‚’確èªã™ã‚‹æ–¹æ³•ã«ã¤ã„ã¦ã¯ã€<a href="https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices">Pixel ãŠã‚ˆã³ Nexus ã®ã‚¢ãƒƒãƒ—デート スケジュール</a>ã«è¨˜è¼‰ã•ã‚Œã¦ã„ã‚‹æ‰‹é †ã‚’ã”覧ãã ã•ã„。 +</p> +<p id="type"> +<strong>2. 「タイプã€<em></em>列ã®é …ç›®ã¯ã©ã†ã„ã†æ„味ã§ã™ã‹ï¼Ÿ</strong> +</p> +<p> +脆弱性ã®è©³ç´°ã®è¡¨ã§ã€Œã‚¿ã‚¤ãƒ—ã€<em></em>列ã«è¨˜è¼‰ã—ãŸé …ç›®ã¯ã€ã‚»ã‚ュリティã®è„†å¼±æ€§ã®åˆ†é¡žã‚’示ã—ã¦ã„ã¾ã™ã€‚ +</p> +<table> + <colgroup><col width="25%" /> + <col width="75%" /> + </colgroup><tbody><tr> + <th>略語</th> + <th>定義</th> + </tr> + <tr> + <td>RCE</td> + <td>リモートコード実行</td> + </tr> + <tr> + <td>EoP</td> + <td>権é™æ˜‡æ ¼</td> + </tr> + <tr> + <td>ID</td> + <td>æƒ…å ±é–‹ç¤º</td> + </tr> + <tr> + <td>DoS</td> + <td>サービス拒å¦</td> + </tr> + <tr> + <td>ãªã—</td> + <td>該当ã™ã‚‹åˆ†é¡žãªã—</td> + </tr> +</tbody></table> +<p> +<strong>3. 「å‚ç…§ã€<em></em>列ã®é …ç›®ã¯ã©ã†ã„ã†æ„味ã§ã™ã‹ï¼Ÿ</strong> +</p> +<p> +脆弱性ã®è©³ç´°ã®è¡¨ã§ã€Œå‚ç…§ã€<em></em>列ã«è¨˜è¼‰ã—ãŸé …ç›®ã«ã¯ã€ãã®å‚照番å·ãŒå±žã™çµ„織を示ã™æŽ¥é 辞をå«ã‚ã¦ã„ã‚‹å ´åˆãŒã‚ã‚Šã¾ã™ã€‚ +</p> +<table> + <colgroup><col width="25%" /> + <col width="75%" /> + </colgroup><tbody><tr> + <th>接é 辞</th> + <th>å‚ç…§</th> + </tr> + <tr> + <td>A-</td> + <td>Android ãƒã‚° ID</td> + </tr> + <tr> + <td>QC-</td> + <td>Qualcomm ã®å‚照番å·</td> + </tr> + <tr> + <td>M-</td> + <td>MediaTek ã®å‚照番å·</td> + </tr> + <tr> + <td>N-</td> + <td>NVIDIA ã®å‚照番å·</td> + </tr> + <tr> + <td>B-</td> + <td>Broadcom ã®å‚照番å·</td> + </tr> +</tbody></table> +<p id="asterisk"> +<strong>4. 「å‚ç…§ã€<em></em>列㮠Android ãƒã‚° ID ã®æ¨ªã«ã‚る「*ã€ã¯ã©ã†ã„ã†æ„味ã§ã™ã‹ï¼Ÿ</strong> +</p> +<p> +公開ã•ã‚Œã¦ã„ãªã„å•é¡Œã«ã¯ã€ã€Œå‚ç…§ã€<em></em>列㮠Android ãƒã‚° ID ã®æ¨ªã«ã€Œ*ã€ã‚’付ã‘ã¦ã„ã¾ã™ã€‚ã“ã®å•é¡Œã®ã‚¢ãƒƒãƒ—デートã¯ã€é€šå¸¸ã€<a href="https://developers.google.com/android/nexus/drivers">Google デベãƒãƒƒãƒ‘ー サイト</a>ã‹ã‚‰å…¥æ‰‹ã§ãã‚‹ Nexus 端末用最新ãƒã‚¤ãƒŠãƒª ドライãƒã«å«ã¾ã‚Œã¦ã„ã¾ã™ã€‚ +</p> +<p> +<strong>5. ã‚»ã‚ュリティã®è„†å¼±æ€§ãŒã€ã“ã®å…¬é–‹æƒ…å ±ã¨ Android ã®ã‚»ã‚ュリティã«é–¢ã™ã‚‹å…¬é–‹æƒ…å ±ã«åˆ†ã‘られã¦ã„ã‚‹ã®ã¯ãªãœã§ã™ã‹ï¼Ÿ</strong> +</p> +<p> +Android æ載端末ã®æœ€æ–°ã®ã‚»ã‚ュリティ パッãƒãƒ¬ãƒ™ãƒ«ã‚’宣言ã™ã‚‹ãŸã‚ã«ã¯ã€Android ã®ã‚»ã‚ュリティã«é–¢ã™ã‚‹å…¬é–‹æƒ…å ±ã«æŽ²è¼‰ã•ã‚Œã¦ã„ã‚‹ã‚»ã‚ュリティã®è„†å¼±æ€§ã¸ã®å¯¾å‡¦ãŒå¿…è¦ã§ã™ã€‚ãれ以外ã®ã€ã“ã®å…¬é–‹æƒ…å ±ãªã©ã«æŽ²è¼‰ã•ã‚Œã¦ã„ã‚‹ã‚»ã‚ュリティã®è„†å¼±æ€§ã¸ã®å¯¾å‡¦ã¯å¿…è¦ã‚ã‚Šã¾ã›ã‚“。 +</p> +<h2 id="versions">ãƒãƒ¼ã‚¸ãƒ§ãƒ³</h2> +<table> + <colgroup><col width="25%" /> + <col width="25%" /> + <col width="50%" /> + </colgroup><tbody><tr> + <th>ãƒãƒ¼ã‚¸ãƒ§ãƒ³</th> + <th>日付</th> + <th>メモ</th> + </tr> + <tr> + <td>1.0</td> + <td>2018 å¹´ 3 月 5 æ—¥</td> + <td>æƒ…å ±å…¬é–‹</td> + </tr> +</tbody></table> + +</body></html>
\ No newline at end of file diff --git a/ja/security/bulletin/pixel/2018.html b/ja/security/bulletin/pixel/2018.html index d86a4973..0fbbff3a 100644 --- a/ja/security/bulletin/pixel/2018.html +++ b/ja/security/bulletin/pixel/2018.html @@ -34,17 +34,43 @@ <th>ã‚»ã‚ュリティ パッãƒãƒ¬ãƒ™ãƒ«</th> </tr> <tr> - <td><a href="/security/bulletin/pixel/2018-01-01.html">2018 å¹´ 1 月</a></td> + <td><a href="/security/bulletin/pixel/2018-03-01.html">2018 å¹´ 3 月</a></td> <td>æº–å‚™ä¸ <!-- - <a href="/security/bulletin/pixel/2018-01-01.html">English</a> / - <a href="/security/bulletin/pixel/2018-01-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/pixel/2018-01-01.html?hl=ko">í•œêµì–´</a> / - <a href="/security/bulletin/pixel/2018-01-01.html?hl=ru">руÌÑÑкий</a> / - <a href="/security/bulletin/pixel/2018-01-01.html?hl=zh-cn">ä¸æ–‡ (ä¸å›½)</a> / - <a href="/security/bulletin/pixel/2018-01-01.html?hl=zh-tw">ä¸æ–‡ (å°ç£)</a> + <a href="/security/bulletin/pixel/2018-03-01.html">English</a> / + <a href="/security/bulletin/pixel/2018-03-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/pixel/2018-03-01.html?hl=ko">í•œêµì–´</a> / + <a href="/security/bulletin/pixel/2018-03-01.html?hl=ru">руÌÑÑкий</a> / + <a href="/security/bulletin/pixel/2018-03-01.html?hl=zh-cn">ä¸æ–‡ (ä¸å›½)</a> / + <a href="/security/bulletin/pixel/2018-03-01.html?hl=zh-tw">ä¸æ–‡ (å°ç£)</a> --> </td> + <td>2018 å¹´ 3 月</td> + <td>2018-03-05</td> + </tr> + <tr> + <td><a href="/security/bulletin/pixel/2018-02-01.html">2018 å¹´ 2 月</a></td> + <td> + <a href="/security/bulletin/pixel/2018-02-01.html">英語</a> / + <a href="/security/bulletin/pixel/2018-02-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/pixel/2018-02-01.html?hl=ko">í•œêµì–´</a> / + <a href="/security/bulletin/pixel/2018-02-01.html?hl=ru">руÌÑÑкий</a> / + <a href="/security/bulletin/pixel/2018-02-01.html?hl=zh-cn">ä¸æ–‡ï¼ˆä¸å›½ï¼‰</a> / + <a href="/security/bulletin/pixel/2018-02-01.html?hl=zh-tw">ä¸æ–‡ï¼ˆå°ç£ï¼‰</a> + </td> + <td>2018 å¹´ 2 月</td> + <td>2018-02-05</td> + </tr> + <tr> + <td><a href="/security/bulletin/pixel/2018-01-01.html">2018 å¹´ 1 月</a></td> + <td> + <a href="/security/bulletin/pixel/2018-01-01.html">英語</a> / + <a href="/security/bulletin/pixel/2018-01-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/pixel/2018-01-01.html?hl=ko">í•œêµì–´</a> / + <a href="/security/bulletin/pixel/2018-01-01.html?hl=ru">руÌÑÑкий</a> / + <a href="/security/bulletin/pixel/2018-01-01.html?hl=zh-cn">ä¸æ–‡ï¼ˆä¸å›½ï¼‰</a> / + <a href="/security/bulletin/pixel/2018-01-01.html?hl=zh-tw">ä¸æ–‡ï¼ˆå°ç£ï¼‰</a> + </td> <td>2018 å¹´ 1 月</td> <td>2018-01-05</td> </tr> diff --git a/ko/security/bulletin/2015-08-01.html b/ko/security/bulletin/2015-08-01.html index 59c91a88..c3964d1e 100644 --- a/ko/security/bulletin/2015-08-01.html +++ b/ko/security/bulletin/2015-08-01.html @@ -27,13 +27,13 @@ Nexus 펌웨어 ì´ë¯¸ì§€ë„ <a href="https://developers.google.com/android/nexus/images">Google ê°œë°œìž ì‚¬ì´íŠ¸</a>ì— ì¶œì‹œë˜ì—ˆìŠµë‹ˆë‹¤. 빌드 LMY48I ì´ìƒì—ì„œ ë‹¤ìŒ ë¬¸ì œê°€ í•´ê²°ë©ë‹ˆë‹¤. ì´ ë¬¸ì œì— ê´€í•œ ì•Œë¦¼ì€ 2015ë…„ 6ì›” 25ì¼ ì´ì „ì— íŒŒíŠ¸ë„ˆì—게 ì „ë‹¬ë˜ì—ˆìŠµë‹ˆë‹¤.</p> -<p>ì´ ì¤‘ 가장 심ê°í•œ ë¬¸ì œëŠ” 미디어 파ì¼ì„ ì²˜ë¦¬í• ë•Œ ì´ë©”ì¼ê³¼ +<p>ì´ ì¤‘ 가장 심ê°í•œ ë¬¸ì œëŠ” 미디어 파ì¼ì„ ì²˜ë¦¬í• ë•Œ ì´ë©”ì¼, 웹 íƒìƒ‰, MMS 등 여러 ë°©ë²•ì„ í†µí•´ ëŒ€ìƒ ê¸°ê¸°ì—ì„œ ì›ê²©ìœ¼ë¡œ 코드를 ì‹¤í–‰í• ìˆ˜ 있게 하는 심ê°í•œ 보안 취약성입니다. <a href="/security/overview/updates-resources.html#severity">심ê°ë„ í‰ê°€</a>는 개발 목ì 으로 í”Œëž«í¼ ë° ì„œë¹„ìŠ¤ 완화가 사용 중지ë˜ì–´ 있거나 -우회ë˜ëŠ” 경우 취약성 악용으로 ì¸í•´ ëŒ€ìƒ ê¸°ê¸°ê°€ -받는 ì˜í–¥ì„ 기준으로 ë‚´ë ¤ì§‘ë‹ˆë‹¤.</p> +ìš°íšŒì— ì„±ê³µí•œ 경우 취약성 악용으로 ì¸í•´ ëŒ€ìƒ ê¸°ê¸°ê°€ +ë°›ì„ ìˆ˜ 있는 ì˜í–¥ì„ 기준으로 ë‚´ë ¤ì§‘ë‹ˆë‹¤.</p> <h2 id="mitigations">완화</h2> @@ -48,12 +48,12 @@ Androidì—ì„œ 보안 ì·¨ì•½ì„±ì´ ì•…ìš©ë ê°€ëŠ¥ì„±ì„ ì¤„ì¼ ìˆ˜ </li><li> Android 보안팀ì—서는 ìœ í•´í• ìˆ˜ 있는 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ 설치ë ë•Œ ê²½ê³ ë¥¼ 보내는 앱 ì¸ì¦ ë° SafetyNetì„ ì‚¬ìš©í•˜ì—¬ 악용사례를 ì ê·¹ì 으로 모니터ë§í•©ë‹ˆë‹¤. Google Play ë‚´ì—ì„œ 기기 루팅 ë„구는 금지ë˜ì–´ 있습니다. Google Play -외부ì—ì„œ ì• í”Œë¦¬ì¼€ì´ì…˜ì„ 설치하는 사용ìžë¥¼ 보호하기 위해 앱 ì¸ì¦ì´ +외부ì—ì„œ ê°€ì ¸ì˜¨ ì• í”Œë¦¬ì¼€ì´ì…˜ì„ 설치하는 사용ìžë¥¼ 보호하기 위해 앱 ì¸ì¦ì´ 기본ì 으로 사용 ì„¤ì •ë˜ë©° ì•Œë ¤ì§„ 루팅 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ ê°ì§€ë˜ë©´ ê²½ê³ ë¥¼ 표시합니다. 앱 ì¸ì¦ì—서는 권한 승격 ì·¨ì•½ì„±ì„ ì•…ìš©í•˜ëŠ” 것으로 ì•Œë ¤ì§„ 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì„ ì‹ë³„í•˜ê³ ì°¨ë‹¨í•©ë‹ˆë‹¤. ì´ëŸ¬í•œ ì• í”Œë¦¬ì¼€ì´ì…˜ì´ ì´ë¯¸ ì„¤ì¹˜ëœ ê²½ìš° 앱 ì¸ì¦ì—ì„œ 사용ìžì—게 ì´ë¥¼ ì•Œë¦¬ê³ -ì• í”Œë¦¬ì¼€ì´ì…˜ ì‚ì œí•˜ë ¤ê³ ì‹œë„합니다. +ì• í”Œë¦¬ì¼€ì´ì…˜ ì‚ì œë¥¼ ì‹œë„합니다. </li><li> Google 행아웃과 ë©”ì‹ ì € ì• í”Œë¦¬ì¼€ì´ì…˜ì´ 미디어 서버와 ê°™ì€ ì·¨ì•½í•œ í”„ë¡œì„¸ìŠ¤ì— ë¯¸ë””ì–´ë¥¼ ìžë™ìœ¼ë¡œ ì „ë‹¬í•˜ì§€ ì•Šë„ë¡ ì—…ë°ì´íŠ¸ë˜ì—ˆìŠµë‹ˆë‹¤. @@ -77,7 +77,7 @@ Androidì—ì„œ 보안 ì·¨ì•½ì„±ì´ ì•…ìš©ë ê°€ëŠ¥ì„±ì„ ì¤„ì¼ ìˆ˜ </li><li> Artem Chaykin: CVE-2015-3843 </li></ul> -<p>*Wish는 <a href="https://www.google.com/about/appsecurity/android-rewards/">Android 보안 리워드</a>ì˜ ìµœì´ˆ 수혜ìžì´ê¸°ë„ 합니다.</p> +<p>*Wish는 <a href="https://www.google.com/about/appsecurity/android-rewards/">Android 보안 리워드</a>ì˜ ìµœì´ˆ 수ìƒìžìž…니다.</p> <h3 id="integer_overflows_during_mp4_atom_processing">MP4 Atom 처리 중 ì •ìˆ˜ 오버플로우</h3> @@ -92,11 +92,11 @@ Androidì—ì„œ 보안 ì·¨ì•½ì„±ì´ ì•…ìš©ë ê°€ëŠ¥ì„±ì„ ì¤„ì¼ ìˆ˜ <p>ì´ ë¬¸ì œëŠ” ì›ê²© 코드를 권한 있는 미디어 서버 서비스로 ì‹¤í–‰í• ê°€ëŠ¥ì„±ì´ ìžˆìœ¼ë¯€ë¡œ 심ê°ë„ 심ê°ìœ¼ë¡œ í‰ê°€ë©ë‹ˆë‹¤. 미디어 서버는 SELinuxë¡œ 보호ë˜ì§€ë§Œ 오디오 ë° ë™ì˜ìƒ ìŠ¤íŠ¸ë¦¼ë¿ ì•„ë‹ˆë¼ ë‹¤ì–‘í•œ 기기ì—ì„œ -타사 ì•±ì´ ì¼ë°˜ì 으로 ì•¡ì„¸ìŠ¤í• ìˆ˜ 없는 권한 있는 ì»¤ë„ ë“œë¼ì´ë²„ 기기 ë…¸ë“œì— -ì•¡ì„¸ìŠ¤í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” ì´ì „ì— ì‹¬ê°ë„ í‰ê°€ ê°€ì´ë“œë¼ì¸ì— -ë”°ë¼ ì‹¬ê°ë„ ë†’ìŒ ì·¨ì•½ì„±ìœ¼ë¡œ í‰ê°€ë˜ì—ˆìœ¼ë©° íŒŒíŠ¸ë„ˆì— ê·¸ë ‡ê²Œ -ë³´ê³ ë˜ì—ˆìŠµë‹ˆë‹¤. 하지만 2015ë…„ 6ì›”ì— ê²Œì‹œëœ ìƒˆë¡œìš´ ê°€ì´ë“œë¼ì¸ì— 따르면 -ì´ ë¬¸ì œì˜ ì‹¬ê°ë„는 심ê°ìž…니다.</p> +타사 ì•±ì´ ì¼ë°˜ì 으로 ì•¡ì„¸ìŠ¤í• ìˆ˜ 없는 권한 있는 ì»¤ë„ ë“œë¼ì´ë²„ +기기 ë…¸ë“œì— ì•¡ì„¸ìŠ¤í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” ì´ì „ì˜ ì‹¬ê°ë„ í‰ê°€ +ê°€ì´ë“œë¼ì¸ì— ë”°ë¼ ì‹¬ê°ë„ ë†’ìŒ ì·¨ì•½ì„±ìœ¼ë¡œ í‰ê°€ë˜ì—ˆìœ¼ë©° íŒŒíŠ¸ë„ˆì— +ê·¸ë ‡ê²Œ ë³´ê³ ë˜ì—ˆìŠµë‹ˆë‹¤. 하지만 2015ë…„ 6ì›”ì— ê²Œì‹œëœ ìƒˆë¡œìš´ +ê°€ì´ë“œë¼ì¸ì— 따르면 ì´ ë¬¸ì œì˜ ì‹¬ê°ë„는 심ê°ìž…니다.</p> <table> <tbody><tr> <th>CVE</th> @@ -125,11 +125,11 @@ SELinuxë¡œ 보호ë˜ì§€ë§Œ 오디오 ë° ë™ì˜ìƒ ìŠ¤íŠ¸ë¦¼ë¿ ì•„ë‹ˆë¼ ë‹¤ì–‘ <p>ì´ ë¬¸ì œëŠ” ì›ê²© 코드를 권한 있는 미디어 서버 서비스로 ì‹¤í–‰í• ê°€ëŠ¥ì„±ì´ ìžˆìœ¼ë¯€ë¡œ 심ê°ë„ 심ê°ìœ¼ë¡œ í‰ê°€ë©ë‹ˆë‹¤. 미디어 서버는 SELinuxë¡œ 보호ë˜ì§€ë§Œ 오디오 ë° ë™ì˜ìƒ ìŠ¤íŠ¸ë¦¼ë¿ ì•„ë‹ˆë¼ ë‹¤ì–‘í•œ 기기ì—ì„œ -타사 ì•±ì´ ì¼ë°˜ì 으로 ì•¡ì„¸ìŠ¤í• ìˆ˜ 없는 권한 있는 ì»¤ë„ ë“œë¼ì´ë²„ 기기 ë…¸ë“œì— -ì•¡ì„¸ìŠ¤í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” ì´ì „ì— ì‹¬ê°ë„ í‰ê°€ ê°€ì´ë“œë¼ì¸ì— -ë”°ë¼ ì‹¬ê°ë„ ë†’ìŒ ì·¨ì•½ì„±ìœ¼ë¡œ í‰ê°€ë˜ì—ˆìœ¼ë©° íŒŒíŠ¸ë„ˆì— ê·¸ë ‡ê²Œ -ë³´ê³ ë˜ì—ˆìŠµë‹ˆë‹¤. 하지만 2015ë…„ 6ì›”ì— ê²Œì‹œëœ ìƒˆë¡œìš´ ê°€ì´ë“œë¼ì¸ì— 따르면 -ì´ ë¬¸ì œì˜ ì‹¬ê°ë„는 심ê°ìž…니다.</p> +타사 ì•±ì´ ì¼ë°˜ì 으로 ì•¡ì„¸ìŠ¤í• ìˆ˜ 없는 권한 있는 ì»¤ë„ ë“œë¼ì´ë²„ +기기 ë…¸ë“œì— ì•¡ì„¸ìŠ¤í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” ì´ì „ì˜ ì‹¬ê°ë„ í‰ê°€ +ê°€ì´ë“œë¼ì¸ì— ë”°ë¼ ì‹¬ê°ë„ ë†’ìŒ ì·¨ì•½ì„±ìœ¼ë¡œ í‰ê°€ë˜ì—ˆìœ¼ë©° íŒŒíŠ¸ë„ˆì— +ê·¸ë ‡ê²Œ ë³´ê³ ë˜ì—ˆìŠµë‹ˆë‹¤. 하지만 2015ë…„ 6ì›”ì— ê²Œì‹œëœ ìƒˆë¡œìš´ +ê°€ì´ë“œë¼ì¸ì— 따르면 ì´ ë¬¸ì œì˜ ì‹¬ê°ë„는 심ê°ìž…니다.</p> <table> <tbody><tr> <th>CVE</th> @@ -161,9 +161,9 @@ SELinuxë¡œ 보호ë˜ì§€ë§Œ 오디오 ë° ë™ì˜ìƒ ìŠ¤íŠ¸ë¦¼ë¿ ì•„ë‹ˆë¼ ë‹¤ì–‘ 타사 ì•±ì´ ì¼ë°˜ì 으로 ì•¡ì„¸ìŠ¤í• ìˆ˜ 없는 권한 있는 ì»¤ë„ ë“œë¼ì´ë²„ 기기 ë…¸ë“œì— ì•¡ì„¸ìŠ¤í• ìˆ˜ 있습니다.</p> -<p>ì´ ë¬¸ì œëŠ” ì´ì „ì— ì‹¬ê°ë„ í‰ê°€ ê°€ì´ë“œë¼ì¸ì— ë”°ë¼ ì‹¬ê°ë„ ë†’ìŒ ì·¨ì•½ì„±ìœ¼ë¡œ -í‰ê°€ë˜ì—ˆìœ¼ë©° íŒŒíŠ¸ë„ˆì— ê·¸ë ‡ê²Œ ë³´ê³ ë˜ì—ˆìŠµë‹ˆë‹¤. 하지만 2015ë…„ 6ì›”ì— -ê²Œì‹œëœ ìƒˆë¡œìš´ ê°€ì´ë“œë¼ì¸ì— 따르면 ì´ ë¬¸ì œì˜ ì‹¬ê°ë„는 심ê°ìž…니다.</p> +<p>ì´ ë¬¸ì œëŠ” ì´ì „ì˜ ì‹¬ê°ë„ í‰ê°€ ê°€ì´ë“œë¼ì¸ì— ë”°ë¼ ì‹¬ê°ë„ ë†’ìŒ ì·¨ì•½ì„±ìœ¼ë¡œ +í‰ê°€ë˜ì—ˆìœ¼ë©° íŒŒíŠ¸ë„ˆì— ê·¸ë ‡ê²Œ ë³´ê³ ë˜ì—ˆìŠµë‹ˆë‹¤. 하지만 2015ë…„ 6ì›”ì— ê²Œì‹œëœ +새로운 ê°€ì´ë“œë¼ì¸ì— 따르면 ì´ ë¬¸ì œì˜ ì‹¬ê°ë„는 심ê°ìž…니다.</p> <table> <tbody><tr> <th>CVE</th> @@ -195,7 +195,7 @@ SELinuxë¡œ 보호ë˜ì§€ë§Œ 오디오 ë° ë™ì˜ìƒ ìŠ¤íŠ¸ë¦¼ë¿ ì•„ë‹ˆë¼ ë‹¤ì–‘ 타사 ì•±ì´ ì¼ë°˜ì 으로 ì•¡ì„¸ìŠ¤í• ìˆ˜ 없는 권한 있는 ì»¤ë„ ë“œë¼ì´ë²„ 기기 ë…¸ë“œì— ì•¡ì„¸ìŠ¤í• ìˆ˜ 있습니다.</p> -<p>ì´ ë¬¸ì œëŠ” ì´ì „ì— ì‹¬ê°ë„ í‰ê°€ ê°€ì´ë“œë¼ì¸ì— ë”°ë¼ ì‹¬ê°ë„ ë†’ìŒ ì·¨ì•½ì„±ìœ¼ë¡œ +<p>ì´ ë¬¸ì œëŠ” ì´ì „ì˜ ì‹¬ê°ë„ í‰ê°€ ê°€ì´ë“œë¼ì¸ì— ë”°ë¼ ì‹¬ê°ë„ ë†’ìŒ ì·¨ì•½ì„±ìœ¼ë¡œ í‰ê°€ë˜ì—ˆìœ¼ë©° íŒŒíŠ¸ë„ˆì— ê·¸ë ‡ê²Œ ë³´ê³ ë˜ì—ˆìŠµë‹ˆë‹¤. 하지만 2015ë…„ 6ì›”ì— ê²Œì‹œëœ ìƒˆë¡œìš´ ê°€ì´ë“œë¼ì¸ì— 따르면 ì´ ë¬¸ì œì˜ ì‹¬ê°ë„는 심ê°ìž…니다.</p> <table> @@ -227,11 +227,11 @@ SELinuxë¡œ 보호ë˜ì§€ë§Œ 오디오 ë° ë™ì˜ìƒ ìŠ¤íŠ¸ë¦¼ë¿ ì•„ë‹ˆë¼ ë‹¤ì–‘ <p>ì´ ë¬¸ì œëŠ” ì›ê²© 코드를 권한 있는 미디어 서버 서비스로 ì‹¤í–‰í• ê°€ëŠ¥ì„±ì´ ìžˆìœ¼ë¯€ë¡œ 심ê°ë„ 심ê°ìœ¼ë¡œ í‰ê°€ë©ë‹ˆë‹¤. 미디어 서버는 SELinuxë¡œ 보호ë˜ì§€ë§Œ 오디오 ë° ë™ì˜ìƒ ìŠ¤íŠ¸ë¦¼ë¿ ì•„ë‹ˆë¼ ë‹¤ì–‘í•œ 기기ì—ì„œ -타사 ì•±ì´ ì¼ë°˜ì 으로 ì•¡ì„¸ìŠ¤í• ìˆ˜ 없는 권한 있는 ì»¤ë„ ë“œë¼ì´ë²„ 기기 ë…¸ë“œì— -ì•¡ì„¸ìŠ¤í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” ì´ì „ì— ì‹¬ê°ë„ í‰ê°€ ê°€ì´ë“œë¼ì¸ì— -ë”°ë¼ ì‹¬ê°ë„ ë†’ìŒ ì·¨ì•½ì„±ìœ¼ë¡œ í‰ê°€ë˜ì—ˆìœ¼ë©° íŒŒíŠ¸ë„ˆì— ê·¸ë ‡ê²Œ -ë³´ê³ ë˜ì—ˆìŠµë‹ˆë‹¤. 하지만 2015ë…„ 6ì›”ì— ê²Œì‹œëœ ìƒˆë¡œìš´ ê°€ì´ë“œë¼ì¸ì— 따르면 -ì´ ë¬¸ì œì˜ ì‹¬ê°ë„는 심ê°ìž…니다.</p> +타사 ì•±ì´ ì¼ë°˜ì 으로 ì•¡ì„¸ìŠ¤í• ìˆ˜ 없는 권한 있는 ì»¤ë„ ë“œë¼ì´ë²„ +기기 ë…¸ë“œì— ì•¡ì„¸ìŠ¤í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” ì´ì „ì˜ ì‹¬ê°ë„ í‰ê°€ +ê°€ì´ë“œë¼ì¸ì— ë”°ë¼ ì‹¬ê°ë„ ë†’ìŒ ì·¨ì•½ì„±ìœ¼ë¡œ í‰ê°€ë˜ì—ˆìœ¼ë©° íŒŒíŠ¸ë„ˆì— +ê·¸ë ‡ê²Œ ë³´ê³ ë˜ì—ˆìŠµë‹ˆë‹¤. 하지만 2015ë…„ 6ì›”ì— ê²Œì‹œëœ ìƒˆë¡œìš´ +ê°€ì´ë“œë¼ì¸ì— 따르면 ì´ ë¬¸ì œì˜ ì‹¬ê°ë„는 심ê°ìž…니다.</p> <table> <tbody><tr> <th>CVE</th> @@ -262,7 +262,7 @@ libstagefrightì˜ ì •ìˆ˜ 오버플로우</h3> ê°€ëŠ¥ì„±ì´ ìžˆìœ¼ë¯€ë¡œ 심ê°ë„ 심ê°ìœ¼ë¡œ í‰ê°€ë©ë‹ˆë‹¤. 미디어 서버는 SELinuxë¡œ 보호ë˜ì§€ë§Œ 오디오 ë° ë™ì˜ìƒ ìŠ¤íŠ¸ë¦¼ë¿ ì•„ë‹ˆë¼ ë‹¤ì–‘í•œ 기기ì—ì„œ 타사 ì•±ì´ ì¼ë°˜ì 으로 ì•¡ì„¸ìŠ¤í• ìˆ˜ 없는 권한 있는 ì»¤ë„ ë“œë¼ì´ë²„ -기기 ë…¸ë“œì— ì•¡ì„¸ìŠ¤í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” ì´ì „ì— ì‹¬ê°ë„ í‰ê°€ +기기 ë…¸ë“œì— ì•¡ì„¸ìŠ¤í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” ì´ì „ì˜ ì‹¬ê°ë„ í‰ê°€ ê°€ì´ë“œë¼ì¸ì— ë”°ë¼ ì‹¬ê°ë„ ë†’ìŒ ì·¨ì•½ì„±ìœ¼ë¡œ í‰ê°€ë˜ì—ˆìœ¼ë©° íŒŒíŠ¸ë„ˆì— ê·¸ë ‡ê²Œ ë³´ê³ ë˜ì—ˆìŠµë‹ˆë‹¤. 하지만 2015ë…„ 6ì›”ì— ê²Œì‹œëœ ìƒˆë¡œìš´ ê°€ì´ë“œë¼ì¸ì— 따르면 ì´ ë¬¸ì œì˜ ì‹¬ê°ë„는 심ê°ìž…니다.</p> @@ -283,7 +283,7 @@ SELinuxë¡œ 보호ë˜ì§€ë§Œ 오디오 ë° ë™ì˜ìƒ ìŠ¤íŠ¸ë¦¼ë¿ ì•„ë‹ˆë¼ ë‹¤ì–‘ <h3 id="buffer_overflow_in_sonivox_parse_wave">Sonivox Parse_waveì˜ ë²„í¼ ì˜¤ë²„í”Œë¡œìš°</h3> -<p>Sonivoxì— XMF ë°ì´í„°ê°€ 처리ë˜ëŠ” ë™ì•ˆ 메모리 ì†ìƒì„ ì¼ìœ¼í‚¤ê³ +<p>Sonivoxì— XMF ë°ì´í„°ë¥¼ 처리하는 중 메모리 ì†ìƒì„ ì¼ìœ¼í‚¤ê³ ì›ê²© 코드를 미디어 서버 프로세스로 ì‹¤í–‰í• ìˆ˜ 있게 하는 ë²„í¼ ì˜¤ë²„í”Œë¡œìš° ê°€ëŠ¥ì„±ì´ ìžˆìŠµë‹ˆë‹¤.</p> @@ -295,7 +295,7 @@ SELinuxë¡œ 보호ë˜ì§€ë§Œ 오디오 ë° ë™ì˜ìƒ ìŠ¤íŠ¸ë¦¼ë¿ ì•„ë‹ˆë¼ ë‹¤ì–‘ ê°€ëŠ¥ì„±ì´ ìžˆìœ¼ë¯€ë¡œ 심ê°ë„ 심ê°ìœ¼ë¡œ í‰ê°€ë©ë‹ˆë‹¤. 미디어 서버는 SELinuxë¡œ 보호ë˜ì§€ë§Œ 오디오 ë° ë™ì˜ìƒ ìŠ¤íŠ¸ë¦¼ë¿ ì•„ë‹ˆë¼ ë‹¤ì–‘í•œ 기기ì—ì„œ 타사 ì•±ì´ ì¼ë°˜ì 으로 ì•¡ì„¸ìŠ¤í• ìˆ˜ 없는 권한 있는 ì»¤ë„ ë“œë¼ì´ë²„ -기기 ë…¸ë“œì— ì•¡ì„¸ìŠ¤í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” ì´ì „ì— ì‹¬ê°ë„ í‰ê°€ +기기 ë…¸ë“œì— ì•¡ì„¸ìŠ¤í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” ì´ì „ì˜ ì‹¬ê°ë„ í‰ê°€ ê°€ì´ë“œë¼ì¸ì— ë”°ë¼ ì‹¬ê°ë„ ë†’ìŒ ì·¨ì•½ì„±ìœ¼ë¡œ í‰ê°€ë˜ì—ˆìœ¼ë©° íŒŒíŠ¸ë„ˆì— ê·¸ë ‡ê²Œ ë³´ê³ ë˜ì—ˆìŠµë‹ˆë‹¤. 하지만 2015ë…„ 6ì›”ì— ê²Œì‹œëœ ìƒˆë¡œìš´ ê°€ì´ë“œë¼ì¸ì— 따르면 ì´ ë¬¸ì œì˜ ì‹¬ê°ë„는 심ê°ìž…니다.</p> @@ -331,7 +331,7 @@ SELinuxë¡œ 보호ë˜ì§€ë§Œ 오디오 ë° ë™ì˜ìƒ ìŠ¤íŠ¸ë¦¼ë¿ ì•„ë‹ˆë¼ ë‹¤ì–‘ 기기 ë…¸ë“œì— ì•¡ì„¸ìŠ¤í• ìˆ˜ 있습니다.</p> <p>처ìŒì— ì´ ë¬¸ì œëŠ” ì›ê²©ìœ¼ë¡œ ì•¡ì„¸ìŠ¤í• ìˆ˜ 없는 로컬 악용으로 ë³´ê³ ë˜ì—ˆìŠµë‹ˆë‹¤. -ì´ ë¬¸ì œëŠ” ì´ì „ì— ì‹¬ê°ë„ í‰ê°€ ê°€ì´ë“œë¼ì¸ì— ë”°ë¼ ì‹¬ê°ë„ 보통 취약성으로 +ì´ ë¬¸ì œëŠ” ì´ì „ì˜ ì‹¬ê°ë„ í‰ê°€ ê°€ì´ë“œë¼ì¸ì— ë”°ë¼ ì‹¬ê°ë„ 보통 취약성으로 í‰ê°€ë˜ì—ˆìœ¼ë©° íŒŒíŠ¸ë„ˆì— ê·¸ë ‡ê²Œ ë³´ê³ ë˜ì—ˆìŠµë‹ˆë‹¤. 하지만 2015ë…„ 6ì›”ì— ê²Œì‹œëœ ìƒˆë¡œìš´ ê°€ì´ë“œë¼ì¸ì— 따르면 ì´ ë¬¸ì œì˜ ì‹¬ê°ë„는 심ê°ìž…니다.</p> <table> @@ -483,7 +483,7 @@ SELinuxë¡œ 보호ë˜ì§€ë§Œ 오디오 ë° ë™ì˜ìƒ ìŠ¤íŠ¸ë¦¼ë¿ ì•„ë‹ˆë¼ ë‹¤ì–‘ 타사 ì•±ì´ ì¼ë°˜ì 으로 ì•¡ì„¸ìŠ¤í• ìˆ˜ 없는 권한 있는 ì»¤ë„ ë“œë¼ì´ë²„ 기기 ë…¸ë“œì— ì•¡ì„¸ìŠ¤í• ìˆ˜ 있습니다.</p> -<p>ì´ ë¬¸ì œëŠ” ì´ì „ì— ì‹¬ê°ë„ í‰ê°€ ê°€ì´ë“œë¼ì¸ì— ë”°ë¼ ì‹¬ê°ë„ 보통 취약성으로 +<p>ì´ ë¬¸ì œëŠ” ì´ì „ì˜ ì‹¬ê°ë„ í‰ê°€ ê°€ì´ë“œë¼ì¸ì— ë”°ë¼ ì‹¬ê°ë„ 보통 취약성으로 í‰ê°€ë˜ì—ˆìœ¼ë©° íŒŒíŠ¸ë„ˆì— ê·¸ë ‡ê²Œ ë³´ê³ ë˜ì—ˆìŠµë‹ˆë‹¤. 하지만 2015ë…„ 6ì›”ì— ê²Œì‹œëœ ìƒˆë¡œìš´ ê°€ì´ë“œë¼ì¸ì— 따르면 ì´ ë¬¸ì œëŠ” 심ê°ë„ ë†’ìŒ ì·¨ì•½ì„±ìž…ë‹ˆë‹¤.</p> <table> @@ -513,7 +513,7 @@ SELinuxë¡œ 보호ë˜ì§€ë§Œ 오디오 ë° ë™ì˜ìƒ ìŠ¤íŠ¸ë¦¼ë¿ ì•„ë‹ˆë¼ ë‹¤ì–‘ 타사 ì•±ì´ ì¼ë°˜ì 으로 ì•¡ì„¸ìŠ¤í• ìˆ˜ 없는 권한 있는 ì»¤ë„ ë“œë¼ì´ë²„ 기기 ë…¸ë“œì— ì•¡ì„¸ìŠ¤í• ìˆ˜ 있습니다.</p> -<p>ì´ ë¬¸ì œëŠ” ì´ì „ì— ì‹¬ê°ë„ í‰ê°€ ê°€ì´ë“œë¼ì¸ì— ë”°ë¼ ì‹¬ê°ë„ 보통 취약성으로 +<p>ì´ ë¬¸ì œëŠ” ì´ì „ì˜ ì‹¬ê°ë„ í‰ê°€ ê°€ì´ë“œë¼ì¸ì— ë”°ë¼ ì‹¬ê°ë„ 보통 취약성으로 í‰ê°€ë˜ì—ˆìœ¼ë©° íŒŒíŠ¸ë„ˆì— ê·¸ë ‡ê²Œ ë³´ê³ ë˜ì—ˆìŠµë‹ˆë‹¤. 하지만 2015ë…„ 6ì›”ì— ê²Œì‹œëœ ìƒˆë¡œìš´ ê°€ì´ë“œë¼ì¸ì— 따르면 ì´ ë¬¸ì œëŠ” 심ê°ë„ ë†’ìŒ ì·¨ì•½ì„±ìž…ë‹ˆë‹¤.</p> <table> diff --git a/ko/security/bulletin/2015-12-01.html b/ko/security/bulletin/2015-12-01.html index 9c9c6601..7a2b7f3a 100644 --- a/ko/security/bulletin/2015-12-01.html +++ b/ko/security/bulletin/2015-12-01.html @@ -42,8 +42,8 @@ Android 6.0ì—ì„œ ë¬¸ì œê°€ í•´ê²°ë˜ì—ˆìŠµë‹ˆë‹¤. ìžì„¸í•œ ë‚´ìš©ì€ <a href=" 기준으로 ë‚´ë ¤ì§‘ë‹ˆë‹¤.</p> <p>ì‹¤ì œ ê³ ê°ì´ 새로 ë³´ê³ ëœ ì´ëŸ¬í•œ ë¬¸ì œë¡œ ì¸í•´ 악용당했다는 ì‹ ê³ ëŠ” -ì ‘ìˆ˜ë˜ì§€ 않았습니다. SafetyNetê³¼ ê°™ì´ Android 플랫í¼ì˜ ë³´ì•ˆì„ ê°œì„ í•˜ëŠ” <a href="/security/enhancements/index.html">Android 보안 í”Œëž«í¼ ë³´í˜¸</a> ë° ì„œë¹„ìŠ¤ 보호 ê¸°ëŠ¥ì— ëŒ€í•´ ìžì„¸ížˆ ì•Œì•„ë³´ë ¤ë©´ <a href="#mitigations">완화</a> -ì„¹ì…˜ì„ ì°¸ì¡°í•˜ì„¸ìš”. ëª¨ë“ ê³ ê°ì€ 기기ì—ì„œ ì´ ì—…ë°ì´íŠ¸ë¥¼ 수ë½í•˜ëŠ” ê²ƒì´ +ì ‘ìˆ˜ë˜ì§€ 않았습니다. SafetyNetê³¼ ê°™ì´ Android 플랫í¼ì˜ ë³´ì•ˆì„ ê°œì„ í•˜ëŠ” <a href="/security/enhancements/index.html">Android 보안 í”Œëž«í¼ ë³´í˜¸</a> ë° ì„œë¹„ìŠ¤ 보호 ê¸°ëŠ¥ì— ê´€í•´ ìžì„¸ížˆ ì•Œì•„ë³´ë ¤ë©´ +<a href="#mitigations">완화</a> ì„¹ì…˜ì„ ì°¸ì¡°í•˜ì„¸ìš”. ëª¨ë“ ê³ ê°ì€ 기기ì—ì„œ ì´ ì—…ë°ì´íŠ¸ë¥¼ 수ë½í•˜ëŠ” ê²ƒì´ ì¢‹ìŠµë‹ˆë‹¤.</p> <h2 id="mitigations">완화</h2> @@ -54,17 +54,17 @@ Androidì—ì„œ 보안 ì·¨ì•½ì„±ì´ ì•…ìš©ë ê°€ëŠ¥ì„±ì„ ì¤„ì¼ ìˆ˜ <ul> <li> Android í”Œëž«í¼ ìµœì‹ ë²„ì „ì˜ í–¥ìƒëœ 기능으로 Androidì˜ ì—¬ëŸ¬ ë¬¸ì œë¥¼ -악용하기 ë”ìš± ì–´ë ¤ì›Œì¡ŒìŠµë‹ˆë‹¤. 가능한 경우 ëª¨ë“ ì‚¬ìš©ìžëŠ” -Android ìµœì‹ ë²„ì „ìœ¼ë¡œ ì—…ë°ì´íŠ¸í•˜ëŠ” ê²ƒì´ ì¢‹ìŠµë‹ˆë‹¤.</li> +악용하기 ë”ìš± ì–´ë ¤ì›Œì¡ŒìŠµë‹ˆë‹¤. 가능하다면 ëª¨ë“ ì‚¬ìš©ìžëŠ” ìµœì‹ ë²„ì „ì˜ Androidë¡œ +ì—…ë°ì´íŠ¸í•˜ëŠ” ê²ƒì´ ì¢‹ìŠµë‹ˆë‹¤.</li> <li> Android 보안팀ì—서는 ìœ í•´í• ìˆ˜ 있는 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ 설치ë ë•Œ ê²½ê³ ë¥¼ 보내는 앱 ì¸ì¦ ë° SafetyNetì„ ì‚¬ìš©í•˜ì—¬ 악용사례를 ì ê·¹ì 으로 모니터ë§í•©ë‹ˆë‹¤. Google Play ë‚´ì—ì„œ 기기 루팅 ë„구는 금지ë˜ì–´ 있습니다. Google Play 외부ì—ì„œ ì• í”Œë¦¬ì¼€ì´ì…˜ì„ 설치하는 사용ìžë¥¼ 보호하기 위해 앱 ì¸ì¦ì´ -기본ì 으로 사용 ì„¤ì •ë˜ë©° ì•Œë ¤ì§„ 루팅 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ ê°ì§€ë˜ë©´ ê²½ê³ ë¥¼ 표시합니다. 앱 ì¸ì¦ì€ -권한 승격 ì·¨ì•½ì„±ì„ ì•…ìš©í•˜ëŠ” 것으로 ì•Œë ¤ì§„ 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì„ -ì‹ë³„í•˜ê³ ì°¨ë‹¨í•©ë‹ˆë‹¤. ì´ëŸ¬í•œ -ì• í”Œë¦¬ì¼€ì´ì…˜ì´ ì´ë¯¸ ì„¤ì¹˜ëœ ê²½ìš° 앱 ì¸ì¦ì—ì„œ 사용ìžì—게 -ì´ë¥¼ ì•Œë¦¬ê³ ì• í”Œë¦¬ì¼€ì´ì…˜ ì‚ì œë¥¼ ì‹œë„합니다.</li> +기본ì 으로 사용 ì„¤ì •ë˜ë©° ì•Œë ¤ì§„ 루팅 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ ê°ì§€ë˜ë©´ ê²½ê³ ë¥¼ 표시합니다. 앱 +ì¸ì¦ì—서는 권한 승격 ì·¨ì•½ì„±ì„ ì•…ìš©í•˜ëŠ” 것으로 ì•Œë ¤ì§„ 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì„ +ì‹ë³„í•˜ê³ ì°¨ë‹¨í•©ë‹ˆë‹¤. ì´ëŸ¬í•œ ì• í”Œë¦¬ì¼€ì´ì…˜ì´ +ì´ë¯¸ ì„¤ì¹˜ëœ ê²½ìš° 앱 ì¸ì¦ì—ì„œ 사용ìžì—게 ì´ë¥¼ ì•Œë¦¬ê³ +ì• í”Œë¦¬ì¼€ì´ì…˜ ì‚ì œë¥¼ ì‹œë„합니다.</li> <li> Google 행아웃과 ë©”ì‹ ì € ì• í”Œë¦¬ì¼€ì´ì…˜ì€ 미디어 서버와 ê°™ì€ í”„ë¡œì„¸ìŠ¤ì— ë¯¸ë””ì–´ë¥¼ ìžë™ìœ¼ë¡œ ì „ë‹¬í•˜ì§€ 않습니다.</li> </ul> @@ -78,12 +78,12 @@ Android ìµœì‹ ë²„ì „ìœ¼ë¡œ ì—…ë°ì´íŠ¸í•˜ëŠ” ê²ƒì´ ì¢‹ìŠµë‹ˆë‹¤.</li> Barbella: CVE-2015-6616, CVE-2015-6617, CVE-2015-6623, CVE-2015-6626, CVE-2015-6619, CVE-2015-6633, CVE-2015-6634 </li><li> <a href="http://k33nteam.org/">KeenTeam</a>(<a href="https://twitter.com/k33nteam">@K33nTeam</a>)ì˜ Flanker(<a href="https://twitter.com/flanker_hqd">@flanker_hqd</a>): CVE-2015-6620 - </li><li> <a href="http://www.360.cn">Qihoo 360 Technology Co.Ltd</a>ì˜ Guang Gong(龚广)(<a href="https://twitter.com/oldfresher">@oldfresher</a>, higongguang@gmail.com): CVE-2015-6626 + </li><li> <a href="http://www.360.cn">Qihoo 360 Technology Co.Ltd</a>ì˜ Guang Gong(龚广)(<a href="https://twitter.com/oldfresher">@oldfresher</a>, higongguang@gmail.com) of : CVE-2015-6626 </li><li> EmberMitre Ltdì˜ Mark Carter(<a href="https://twitter.com/hanpingchinese">@hanpingchinese</a>): CVE-2015-6630 </li><li> MichaÅ‚ Bednarski(<a href="https://github.com/michalbednarski">https://github.com/michalbednarski</a>): CVE-2015-6621 </li><li> Google Project Zeroì˜ Natalie Silvanovich: CVE-2015-6616 </li><li> Trend Microì˜ Peter Pi: CVE-2015-6616, CVE-2015-6628 - </li><li> <a href="http://k33nteam.org/">KeenTeam</a>(<a href="https://twitter.com/k33nteam">@K33nTeam</a>)ì˜ Qidan He(<a href="https://twitter.com/flanker_hqd">@flanker_hqd</a>), Marco Grassi(<a href="https://twitter.com/marcograss">@marcograss</a>): CVE-2015-6622 + </li><li> <a href="http://k33nteam.org/">KeenTeam</a>(<a href="https://twitter.com/k33nteam">@K33nTeam</a>)ì˜ Qidan He(<a href="https://twitter.com/flanker_hqd">@flanker_hqd</a>), Marco Grassi (<a href="https://twitter.com/marcograss">@marcograss</a>): CVE-2015-6622 </li><li> Tzu-Yin(Nina) Tai: CVE-2015-6627 </li><li> 아르헨티나 부ì—노스아ì´ë ˆìŠ¤ Fundación Dr. Manuel Sadosky, Programa STICì˜ JoaquÃn Rinaudo(<a href="https://twitter.com/xeroxnir">@xeroxnir</a>): CVE-2015-6631 @@ -275,9 +275,9 @@ libstagefrightì˜ ê¶Œí•œ 승격 취약성</h3> <p>libstagefrightì— ë¡œì»¬ 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ 미디어 서버 서비스ì—ì„œ ìž„ì˜ì˜ 코드를 ì‹¤í–‰í• ìˆ˜ 있게 하는 여러 -ì·¨ì•½ì„±ì´ ìžˆìŠµë‹ˆë‹¤. ì´ ë¬¸ì œëŠ” <a href="http://developer.android.com/guide/topics/manifest/permission-element.html#plevel">서명</a> ë˜ëŠ” <a href="http://developer.android.com/guide/topics/manifest/permission-element.html#plevel">SignatureOrSystem</a> -권한과 ê°™ì´ íƒ€ì‚¬ ì• í”Œë¦¬ì¼€ì´ì…˜ì´ ì•¡ì„¸ìŠ¤í• ìˆ˜ 없는 ìŠ¹ê²©ëœ ê¶Œí•œì„ ë¶€ì—¬í•˜ëŠ” ë° -사용ë 수 있으므로 심ê°ë„ 높ìŒìœ¼ë¡œ í‰ê°€ë©ë‹ˆë‹¤.</p> +ì·¨ì•½ì„±ì´ ìžˆìŠµë‹ˆë‹¤. ì´ ë¬¸ì œëŠ” <a href="http://developer.android.com/guide/topics/manifest/permission-element.html#plevel">서명</a> ë˜ëŠ” <a href="http://developer.android.com/guide/topics/manifest/permission-element.html#plevel">SignatureOrSystem</a> 권한과 ê°™ì´ +타사 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ ì•¡ì„¸ìŠ¤í• ìˆ˜ 없는 ìŠ¹ê²©ëœ ê¶Œí•œì„ ë¶€ì—¬í•˜ëŠ” ë° ì‚¬ìš©ë 수 있으므로 +심ê°ë„ 높ìŒìœ¼ë¡œ í‰ê°€ë©ë‹ˆë‹¤.</p> <table> <tbody><tr> <th>CVE</th> @@ -306,9 +306,9 @@ SystemUIì˜ ê¶Œí•œ 승격 취약성</h3> <p>시계 ì• í”Œë¦¬ì¼€ì´ì…˜ì„ 사용하여 ì•ŒëžŒì„ ì„¤ì •í• ë•Œ SystemUI êµ¬ì„±ìš”ì†Œì˜ ì·¨ì•½ì„±ì´ ìŠ¹ê²©ëœ ê¶Œí•œ 수준ì—ì„œ ì• í”Œë¦¬ì¼€ì´ì…˜ì˜ ìž‘ì—… ìˆ˜í–‰ì„ í—ˆìš©í• ìˆ˜ -있습니다. ì´ ë¬¸ì œëŠ” <a href="http://developer.android.com/guide/topics/manifest/permission-element.html#plevel">서명</a> ë˜ëŠ” <a href="http://developer.android.com/guide/topics/manifest/permission-element.html#plevel">SignatureOrSystem</a> -권한과 ê°™ì´ íƒ€ì‚¬ ì• í”Œë¦¬ì¼€ì´ì…˜ì´ ì•¡ì„¸ìŠ¤í• ìˆ˜ 없는 ìŠ¹ê²©ëœ ê¶Œí•œì„ ë¶€ì—¬í•˜ëŠ” ë° -사용ë 수 있으므로 심ê°ë„ 높ìŒìœ¼ë¡œ í‰ê°€ë©ë‹ˆë‹¤.</p> +있습니다. ì´ ë¬¸ì œëŠ” <a href="http://developer.android.com/guide/topics/manifest/permission-element.html#plevel">서명</a> ë˜ëŠ” <a href="http://developer.android.com/guide/topics/manifest/permission-element.html#plevel">SignatureOrSystem</a> 권한과 ê°™ì´ +타사 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ ì•¡ì„¸ìŠ¤í• ìˆ˜ 없는 ìŠ¹ê²©ëœ ê¶Œí•œì„ ë¶€ì—¬í•˜ëŠ” ë° ì‚¬ìš©ë 수 있으므로 +심ê°ë„ 높ìŒìœ¼ë¡œ í‰ê°€ë©ë‹ˆë‹¤.</p> <table> <tbody><tr> <th>CVE</th> @@ -331,7 +331,8 @@ SystemUIì˜ ê¶Œí•œ 승격 취약성</h3> <p>Android 기본 í”„ë ˆìž„ì›Œí¬ ë¼ì´ë¸ŒëŸ¬ë¦¬ì˜ ì •ë³´ 공개 취약성으로 ì¸í•´ 공격ìžê°€ 플랫í¼ì„ 악용하기 ì–´ë µë„ë¡ ë§ˆë ¨ëœ ë³´ì•ˆ 장치를 ìš°íšŒí• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” <a href="http://developer.android.com/guide/topics/manifest/permission-element.html#plevel">서명</a> ë˜ëŠ” <a href="http://developer.android.com/guide/topics/manifest/permission-element.html#plevel">SignatureOrSystem</a> 권한과 ê°™ì´ -타사 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ ì•¡ì„¸ìŠ¤í• ìˆ˜ 없는 ìŠ¹ê²©ëœ ê¶Œí•œì„ ë¶€ì—¬í•˜ëŠ” ë° ì‚¬ìš©ë 수 있으므로 심ê°ë„ 높ìŒìœ¼ë¡œ í‰ê°€ë©ë‹ˆë‹¤.</p> +타사 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ ì•¡ì„¸ìŠ¤í• ìˆ˜ 없는 ìŠ¹ê²©ëœ ê¶Œí•œì„ ë¶€ì—¬í•˜ëŠ” ë° ì‚¬ìš©ë 수 있으므로 +심ê°ë„ 높ìŒìœ¼ë¡œ í‰ê°€ë©ë‹ˆë‹¤.</p> <table> <tbody><tr> <th>CVE</th> @@ -400,9 +401,9 @@ libstagefrightì˜ ì •ë³´ 공개 취약성</h3> <p>미디어 서버와 í†µì‹ í• ë•Œ 공격ìžê°€ 플랫í¼ì„ 악용하기 ì–´ë µë„ë¡ ë§ˆë ¨ëœ ë³´ì•ˆ 장치를 ìš°íšŒí• ìˆ˜ 있게 하는 -libstagefrightì˜ ì •ë³´ 공개 ì·¨ì•½ì„±ì´ ìžˆìŠµë‹ˆë‹¤. ì´ ë¬¸ì œëŠ” -<a href="http://developer.android.com/guide/topics/manifest/permission-element.html#plevel">서명</a> ë˜ëŠ” <a href="http://developer.android.com/guide/topics/manifest/permission-element.html#plevel">SignatureOrSystem</a> 권한과 ê°™ì´ -타사 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ ì•¡ì„¸ìŠ¤í• ìˆ˜ 없는 ìŠ¹ê²©ëœ ê¶Œí•œì„ ë¶€ì—¬í•˜ëŠ” ë° ì‚¬ìš©ë 수 있으므로 심ê°ë„ 높ìŒìœ¼ë¡œ í‰ê°€ë©ë‹ˆë‹¤.</p> +libstagefrightì˜ ì •ë³´ 공개 ì·¨ì•½ì„±ì´ ìžˆìŠµë‹ˆë‹¤. ì´ ë¬¸ì œëŠ” <a href="http://developer.android.com/guide/topics/manifest/permission-element.html#plevel">서명</a> ë˜ëŠ” +<a href="http://developer.android.com/guide/topics/manifest/permission-element.html#plevel">SignatureOrSystem</a> 권한과 ê°™ì´ íƒ€ì‚¬ ì• í”Œë¦¬ì¼€ì´ì…˜ì´ ì•¡ì„¸ìŠ¤í• ìˆ˜ 없는 +ìŠ¹ê²©ëœ ê¶Œí•œì„ ë¶€ì—¬í•˜ëŠ” ë° ì‚¬ìš©ë 수 있으므로 심ê°ë„ 높ìŒìœ¼ë¡œ í‰ê°€ë©ë‹ˆë‹¤.</p> <table> <tbody><tr> <th>CVE</th> @@ -462,8 +463,8 @@ libstagefrightì˜ ì •ë³´ 공개 ì·¨ì•½ì„±ì´ ìžˆìŠµë‹ˆë‹¤. ì´ ë¬¸ì œëŠ” <p>미디어 서버와 í†µì‹ í• ë•Œ 공격ìžê°€ 플랫í¼ì„ 악용하기 ì–´ë µë„ë¡ ë§ˆë ¨ëœ ë³´ì•ˆ 장치를 ìš°íšŒí• ìˆ˜ 있게 하는 -미디어 í”„ë ˆìž„ì›Œí¬ì˜ ì •ë³´ 공개 ì·¨ì•½ì„±ì´ ìžˆìŠµë‹ˆë‹¤. ì´ ë¬¸ì œëŠ” -<a href="http://developer.android.com/guide/topics/manifest/permission-element.html#plevel">서명</a> ë˜ëŠ” <a href="http://developer.android.com/guide/topics/manifest/permission-element.html#plevel">SignatureOrSystem</a> 권한과 ê°™ì´ íƒ€ì‚¬ ì• í”Œë¦¬ì¼€ì´ì…˜ì´ ì•¡ì„¸ìŠ¤í• ìˆ˜ 없는 +미디어 í”„ë ˆìž„ì›Œí¬ì˜ ì •ë³´ 공개 ì·¨ì•½ì„±ì´ ìžˆìŠµë‹ˆë‹¤. ì´ ë¬¸ì œëŠ” <a href="http://developer.android.com/guide/topics/manifest/permission-element.html#plevel">서명</a> +ë˜ëŠ” <a href="http://developer.android.com/guide/topics/manifest/permission-element.html#plevel">SignatureOrSystem</a> 권한과 ê°™ì´ íƒ€ì‚¬ ì• í”Œë¦¬ì¼€ì´ì…˜ì´ ì•¡ì„¸ìŠ¤í• ìˆ˜ 없는 ìŠ¹ê²©ëœ ê¶Œí•œì„ ë¶€ì—¬í•˜ëŠ” ë° ì‚¬ìš©ë 수 있으므로 심ê°ë„ 높ìŒìœ¼ë¡œ í‰ê°€ë©ë‹ˆë‹¤.</p> <table> <tbody><tr> @@ -484,9 +485,9 @@ libstagefrightì˜ ì •ë³´ 공개 ì·¨ì•½ì„±ì´ ìžˆìŠµë‹ˆë‹¤. ì´ ë¬¸ì œëŠ” <h3 id="information_disclosure_vulnerability_in_wi-fi">Wi-Fiì˜ ì •ë³´ 공개 취약성</h3> -<p>Wi-Fi êµ¬ì„±ìš”ì†Œì˜ ì·¨ì•½ì„±ìœ¼ë¡œ 공격ìžê°€ Wi-Fi 서비스 ì •ë³´ 공개를 ìœ ë°œí• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” <a href="http://developer.android.com/guide/topics/manifest/permission-element.html#plevel">서명</a> ë˜ëŠ” <a href="http://developer.android.com/guide/topics/manifest/permission-element.html#plevel">SignatureOrSystem</a> -권한과 ê°™ì´ íƒ€ì‚¬ ì• í”Œë¦¬ì¼€ì´ì…˜ì´ ì•¡ì„¸ìŠ¤í• ìˆ˜ 없는 ìŠ¹ê²©ëœ ê¶Œí•œì„ ë¶€ì—¬í•˜ëŠ” ë° ì‚¬ìš©ë 수 있으므로 심ê°ë„ 높ìŒìœ¼ë¡œ -í‰ê°€ë©ë‹ˆë‹¤.</p> +<p>Wi-Fi êµ¬ì„±ìš”ì†Œì˜ ì·¨ì•½ì„±ìœ¼ë¡œ 공격ìžê°€ Wi-Fi 서비스 ì •ë³´ 공개를 ìœ ë°œí• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” <a href="http://developer.android.com/guide/topics/manifest/permission-element.html#plevel">서명</a> +ë˜ëŠ” <a href="http://developer.android.com/guide/topics/manifest/permission-element.html#plevel">SignatureOrSystem</a> 권한과 ê°™ì´ íƒ€ì‚¬ ì• í”Œë¦¬ì¼€ì´ì…˜ì´ ì•¡ì„¸ìŠ¤í• ìˆ˜ 없는 ìŠ¹ê²©ëœ ê¶Œí•œì„ ë¶€ì—¬í•˜ëŠ” ë° ì‚¬ìš©ë 수 있으므로 +심ê°ë„ 높ìŒìœ¼ë¡œ í‰ê°€ë©ë‹ˆë‹¤.</p> <table> <tbody><tr> <th>CVE</th> diff --git a/ko/security/bulletin/2016-06-01.html b/ko/security/bulletin/2016-06-01.html index d2236553..af04d739 100644 --- a/ko/security/bulletin/2016-06-01.html +++ b/ko/security/bulletin/2016-06-01.html @@ -45,10 +45,10 @@ Nexus ë„움ë§</a>ì„ ì°¸ì¡°í•˜ì„¸ìš”.</p> <p>ì‹¤ì œ ê³ ê°ì´ 새로 ë³´ê³ ëœ ì´ëŸ¬í•œ ë¬¸ì œë¡œ ì¸í•´ 악용당했다는 ì‹ ê³ ëŠ” ì ‘ìˆ˜ë˜ì§€ 않았습니다. SafetyNetê³¼ ê°™ì´ -Android 플랫í¼ì˜ ë³´ì•ˆì„ ê°œì„ í•˜ëŠ” <a href="/security/enhancements/index.html">Android +Android 플랫í¼ì˜ ë³´ì•ˆì„ ê°œì„ í•˜ëŠ” <a href="/security/enhancements/index.html">Android 보안 í”Œëž«í¼ ë³´í˜¸</a> ë° -보안 í”Œëž«í¼ ë³´í˜¸</a> ë° ì„œë¹„ìŠ¤ 보호 ê¸°ëŠ¥ì— ê´€í•´ ìžì„¸ížˆ ì•Œì•„ë³´ë ¤ë©´ -<a href="#mitigations">Android ë° Google 서비스 완화</a> ì„¹ì…˜ì„ ì°¸ì¡°í•˜ì„¸ìš”.</p> +서비스 보호 ê¸°ëŠ¥ì— ê´€í•´ ìžì„¸ížˆ ì•Œì•„ë³´ë ¤ë©´ <a href="#mitigations"> +Android ë° Google 서비스 완화</a> ì„¹ì…˜ì„ ì°¸ì¡°í•˜ì„¸ìš”.</p> <p>ëª¨ë“ ê³ ê°ì€ 기기ì—ì„œ ì´ ì—…ë°ì´íŠ¸ë¥¼ 수ë½í•˜ëŠ” ê²ƒì´ ì¢‹ìŠµë‹ˆë‹¤.</p> @@ -87,7 +87,7 @@ Android 플랫í¼ì˜ ë³´ì•ˆì„ ê°œì„ í•˜ëŠ” <a href="/security/enhancements/inde <ul> <li> Tencent KeenLab(<a href="https://twitter.com/keen_lab">@keen_lab</a>)ì˜ - Di Shen(<a href="https://twitter.com/returnsme">@returnsme</a>): CVE-2016-2468 +Di Shen (<a href="https://twitter.com/returnsme">@returnsme</a>): CVE-2016-2468 </li><li> <a href="http://bits-please.blogspot.com">Gal Beniamini</a> (<a href="https://twitter.com/laginimaineb">@laginimaineb</a>): CVE-2016-2476 </li><li> Qihoo 360 Technology Co. Ltd. IceSword Labì˜ @@ -440,7 +440,7 @@ Qualcomm 사운드 ë“œë¼ì´ë²„ì˜ ê¶Œí•œ 승격 취약성</h3> <a href="http://developer.android.com/guide/topics/manifest/permission-element.html#plevel">서명</a> ë˜ëŠ” <a href="http://developer.android.com/guide/topics/manifest/permission-element.html#plevel">SignatureOrSystem</a> 권한과 ê°™ì´ íƒ€ì‚¬ ì• í”Œë¦¬ì¼€ì´ì…˜ì´ ì•¡ì„¸ìŠ¤í• ìˆ˜ 없는 ìŠ¹ê²©ëœ ê¶Œí•œìœ¼ë¡œì˜ -로컬 액세스를 부여하는 ë° ì‚¬ìš©ë 수 있으므로 심ê°ë„ 높ìŒìœ¼ë¡œ í‰ê°€ë©ë‹ˆë‹¤.</p> +로컬 액세스를 부여하는 ë° ì‚¬ìš©ë 수 있으므로 심ê°ë„ 높ìŒìœ¼ë¡œ í‰ê°€ë©ë‹ˆë‹¤..</p> <table> <colgroup><col width="19%" /> @@ -779,11 +779,11 @@ MediaTek ì „ì› ê´€ë¦¬ ë“œë¼ì´ë²„ì˜ ê¶Œí•œ 승격 취약성</h3> <h3 id="elevation_of_privilege_vulnerability_in_sd_card_emulation_layer"> SD ì¹´ë“œ ì—ë®¬ë ˆì´ì…˜ ë ˆì´ì–´ì˜ 권한 승격 취약성</h3> -<p>SD ì¹´ë“œ ì—ë®¬ë ˆì´ì…˜ ë ˆì´ì–´ì˜ 권한 승격 취약성으로 ì¸í•´ 로컬 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ ìŠ¹ê²©ëœ ì‹œìŠ¤í…œ ì• í”Œë¦¬ì¼€ì´ì…˜ 컨í…스트 ë‚´ì—ì„œ ìž„ì˜ì˜ 코드를 ì‹¤í–‰í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” -<a href="http://developer.android.com/guide/topics/manifest/permission-element.html#plevel">서명</a> +<p>SD ì¹´ë“œ ì—ë®¬ë ˆì´ì…˜ ë ˆì´ì–´ì˜ 권한 승격 취약성으로 ì¸í•´ 로컬 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ ìŠ¹ê²©ëœ ì‹œìŠ¤í…œ ì• í”Œë¦¬ì¼€ì´ì…˜ 컨í…스트 ë‚´ì—ì„œ ìž„ì˜ì˜ 코드를 ì‹¤í–‰í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” <a href="http://developer.android.com/guide/topics/manifest/permission-element.html#plevel">서명</a> ë˜ëŠ” <a href="http://developer.android.com/guide/topics/manifest/permission-element.html#plevel">SignatureOrSystem</a> -권한과 ê°™ì´ íƒ€ì‚¬ ì• í”Œë¦¬ì¼€ì´ì…˜ì´ ì•¡ì„¸ìŠ¤í• ìˆ˜ 없는 ìŠ¹ê²©ëœ ê¶Œí•œìœ¼ë¡œì˜ -로컬 액세스를 부여하는 ë° ì‚¬ìš©ë 수 있으므로 심ê°ë„ 높ìŒìœ¼ë¡œ í‰ê°€ë©ë‹ˆë‹¤.</p> +권한과 ê°™ì´ íƒ€ì‚¬ ì• í”Œë¦¬ì¼€ì´ì…˜ì´ ì•¡ì„¸ìŠ¤í• ìˆ˜ 없는 +ìŠ¹ê²©ëœ ê¶Œí•œìœ¼ë¡œì˜ ë¡œì»¬ 액세스를 부여하는 ë° ì‚¬ìš©ë 수 있으므로 +심ê°ë„ 높ìŒìœ¼ë¡œ í‰ê°€ë©ë‹ˆë‹¤.</p> <table> <colgroup><col width="19%" /> @@ -1008,7 +1008,7 @@ Qualcomm Wi-Fi ë“œë¼ì´ë²„ì˜ ì •ë³´ 공개 취약성</h3> <h2 id="common_questions_and_answers">ì¼ë°˜ì ì¸ ì§ˆë¬¸ ë° ë‹µë³€</h2> -<p>ì´ ì„¹ì…˜ì—서는 게시íŒì„ ì½ì€ ë’¤ ì œê¸°ë 수 있는 ì¼ë°˜ì ì¸ ì§ˆë¬¸ì— ëŒ€í•œ ë‹µë³€ì„ ì œì‹œí•©ë‹ˆë‹¤.</p> +<p>ì´ ì„¹ì…˜ì—서는 게시íŒì„ ì½ì€ ë’¤ ì œê¸°ë 수 있는 ì¼ë°˜ì ì¸ ì§ˆë¬¸ì˜ ë‹µë³€ì„ ì œì‹œí•©ë‹ˆë‹¤.</p> <p><strong>1. ë‚´ 기기가 ì—…ë°ì´íŠ¸ë˜ì–´ ì´ ë¬¸ì œê°€ í•´ê²°ë˜ì—ˆëŠ”지 어떻게 ì•Œ 수 있나요?</strong></p> diff --git a/ko/security/bulletin/2016-07-01.html b/ko/security/bulletin/2016-07-01.html index b17a8165..da787e67 100644 --- a/ko/security/bulletin/2016-07-01.html +++ b/ko/security/bulletin/2016-07-01.html @@ -36,16 +36,17 @@ Nexus 펌웨어 ì´ë¯¸ì§€ë„ <a href="https://developers.google.com/android/nexu <p>ì´ ì¤‘ 가장 심ê°í•œ ë¬¸ì œëŠ” 미디어 파ì¼ì„ ì²˜ë¦¬í• ë•Œ ì´ë©”ì¼, 웹 íƒìƒ‰, MMS 등 여러 ë°©ë²•ì„ í†µí•´ ëŒ€ìƒ ê¸°ê¸°ì—ì„œ -ì›ê²©ìœ¼ë¡œ 코드를 ì‹¤í–‰í• ìˆ˜ 있게 하는 심ê°í•œ 보안 취약성입니다. <a href="/security/overview/updates-resources.html#severity">심ê°ë„ í‰ê°€</a>는 +ì›ê²©ìœ¼ë¡œ 코드를 ì‹¤í–‰í• ìˆ˜ 있게 하는 심ê°í•œ 보안 취약성입니다. <a href="/security/overview/updates-resources.html#severity">심ê°ë„ +í‰ê°€</a>는 개발 목ì 으로 í”Œëž«í¼ ë° ì„œë¹„ìŠ¤ 완화를 ì‚¬ìš©í• ìˆ˜ 없거나 -ìš°íšŒì— ì„±ê³µí•œ 경우 취약성 악용으로 ì¸í•´ ëŒ€ìƒ ê¸°ê¸°ê°€ 받는 ì˜í–¥ì„ -기준으로 ë‚´ë ¤ì§‘ë‹ˆë‹¤.</p> +ìš°íšŒì— ì„±ê³µí•œ 경우 취약성 악용으로 ì¸í•´ ëŒ€ìƒ ê¸°ê¸°ê°€ +받는 ì˜í–¥ì„ 기준으로 ë‚´ë ¤ì§‘ë‹ˆë‹¤.</p> <p>ì‹¤ì œ ê³ ê°ì´ 새로 ë³´ê³ ëœ ì´ëŸ¬í•œ ë¬¸ì œë¡œ ì¸í•´ 악용당했다는 ì‹ ê³ ëŠ” -ì ‘ìˆ˜ë˜ì§€ 않았습니다. SafetyNetê³¼ ê°™ì´ -Android 플랫í¼ì˜ ë³´ì•ˆì„ ê°œì„ í•˜ëŠ” +ì ‘ìˆ˜ë˜ì§€ 않았습니다. SafetyNetê³¼ ê°™ì´ Android 플랫í¼ì˜ ë³´ì•ˆì„ ê°œì„ í•˜ëŠ” <a href="/security/enhancements/index.html">Android 보안 í”Œëž«í¼ ë³´í˜¸</a> ë° ì„œë¹„ìŠ¤ 보호 ê¸°ëŠ¥ì— ê´€í•´ ìžì„¸ížˆ ì•Œì•„ë³´ë ¤ë©´ -<a href="#mitigations">Android ë° Google 서비스 완화</a> ì„¹ì…˜ì„ ì°¸ì¡°í•˜ì„¸ìš”.</p> +<a href="#mitigations">Android ë° Google 서비스 완화</a> +ì„¹ì…˜ì„ ì°¸ì¡°í•˜ì„¸ìš”.</p> <p>ëª¨ë“ ê³ ê°ì€ 기기ì—ì„œ ì´ ì—…ë°ì´íŠ¸ë¥¼ 수ë½í•˜ëŠ” ê²ƒì´ ì¢‹ìŠµë‹ˆë‹¤.</p> <h2 id="announcements">공지사í•</h2> <ul> @@ -85,11 +86,11 @@ Android 플랫í¼ì˜ ë³´ì•ˆì„ ê°œì„ í•˜ëŠ” Google Play 외부ì—ì„œ ì• í”Œë¦¬ì¼€ì´ì…˜ì„ 설치하는 사용ìžì—게 특히 중요합니다. Google Play ë‚´ì—ì„œ 기기 루팅 ë„구는 금지ë˜ì–´ 있지만 사용ìžê°€ ì¶œì²˜ì— ìƒê´€ì—†ì´ 루팅 ì• í”Œë¦¬ì¼€ì´ì…˜ì„ ì„¤ì¹˜í•˜ë ¤ 하면 - 앱 ì¸ì¦ì´ ê²½ê³ ë¥¼ 표시합니다. ë˜í•œ 앱 ì¸ì¦ì€ + 앱 ì¸ì¦ì´ ê²½ê³ ë¥¼ 표시합니다. ë˜í•œ 앱 ì¸ì¦ì—서는 권한 승격 ì·¨ì•½ì„±ì„ ì•…ìš©í•˜ëŠ” 것으로 ì•Œë ¤ì§„ 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì„ ì‹ë³„í•˜ê³ ì°¨ë‹¨í•©ë‹ˆë‹¤. ì´ëŸ¬í•œ ì• í”Œë¦¬ì¼€ì´ì…˜ì´ ì´ë¯¸ ì„¤ì¹˜ëœ ê²½ìš° 앱 ì¸ì¦ì—ì„œ 사용ìžì—게 ì´ë¥¼ ì•Œë¦¬ê³ ê°ì§€ëœ ì• í”Œë¦¬ì¼€ì´ì…˜ì„ ì‚ì œí•˜ë ¤ê³ ì‹œë„합니다.</li> - <li>Google 행아웃과 ë©”ì‹ ì € ì• í”Œë¦¬ì¼€ì´ì…˜ì€ 미디어 서버와 ê°™ì€ í”„ë¡œì„¸ìŠ¤ì— + <li>Google 행아웃과 ë©”ì‹ ì € ì• í”Œë¦¬ì¼€ì´ì…˜ì—서는 미디어 서버와 ê°™ì€ í”„ë¡œì„¸ìŠ¤ì— ë¯¸ë””ì–´ë¥¼ ìžë™ìœ¼ë¡œ ì „ë‹¬í•˜ì§€ 않습니다.</li> </ul> @@ -101,7 +102,7 @@ Android 플랫í¼ì˜ ë³´ì•ˆì„ ê°œì„ í•˜ëŠ” </li><li>Googleì˜ Adam Powell: CVE-2016-3752 </li><li>Context Information Securityì˜ Alex Chapman, Paul Stone: CVE-2016-3763 </li><li><a href="https://www.e2e-assure.com/">e2e-assure</a>ì˜ - Andy Tyler(<a href="https://twitter.com/ticarpi">@ticarpi</a>): CVE-2016-2457 + Andy Tyler (<a href="https://twitter.com/ticarpi">@ticarpi</a>): CVE-2016-2457 </li><li>Google Project Zeroì˜ Ben Hawkes: CVE-2016-3775 </li><li><a href="http://c0reteam.org">C0RE Team</a>ì˜ Chiachih Wu(<a href="https://twitter.com/chiachih_wu">@chiachih_wu</a>), Yuan-Tsung Lo(<a href="mailto:computernik@gmail.com">computernik@gmail.com</a>), @@ -116,15 +117,15 @@ Android 플랫í¼ì˜ ë³´ì•ˆì„ ê°œì„ í•˜ëŠ” CVE-2016-3816, CVE-2016-3805, CVE-2016-3804, CVE-2016-3767, CVE-2016-3810, CVE-2016-3795, CVE-2016-3796 </li><li>Google AndroidíŒ€ì˜ Greg Kaiser: CVE-2016-3758 - </li><li><a href="http://www.360.com">Qihoo 360 Technology Co. Ltd.</a> - Mobile Safe Teamì˜ - Guang Gong(龚广)(<a href="https://twitter.com/oldfresher">@oldfresher</a>): CVE-2016-3764 + </li><li><a href="http://www.360.com">Qihoo 360 Technology Co. Ltd</a> Mobile Safe Teamì˜ + Guang Gong(龚广)(<a href="https://twitter.com/oldfresher">@oldfresher</a>) + : CVE-2016-3764 </li><li><a href="http://www.360.com">Qihoo 360 Technology Co. Ltd</a>. Alpha Teamì˜ Hao Chen, Guang Gong: CVE-2016-3792, CVE-2016-3768 </li><li><a href="http://www.cmcm.com">Cheetah Mobile</a> Security Research Labì˜ Hao Qin: CVE-2016-3754, CVE-2016-3766 - </li><li><a href="http://www.360.com">Qihoo 360 Technology Co. Ltd.</a> - IceSword Labì˜ Jianqiang Zhao(<a href="https://twitter.com/jianqiangzhao">@jianqiangzhao</a>), + </li><li><a href="http://www.360.com">Qihoo 360 Technology Co. Ltd</a> IceSword Labì˜ + Jianqiang Zhao(<a href="https://twitter.com/jianqiangzhao">@jianqiangzhao</a>) pjf(<a href="http://weibo.com/jfpan">weibo.com/jfpan</a>): CVE-2016-3814, CVE-2016-3802, CVE-2016-3769, CVE-2016-3807, CVE-2016-3808 </li><li>Googleì˜ Marco Nelissen: CVE-2016-3818 @@ -147,7 +148,7 @@ Android 플랫í¼ì˜ ë³´ì•ˆì„ ê°œì„ í•˜ëŠ” </li><li>Alibaba Inc.ì˜ Weichao Sun(<a href="https://twitter.com/sunblate">@sunblate</a>) : CVE-2016-2508, CVE-2016-3755 </li><li>Tencent KeenLab(<a href="https://twitter.com/keen_lab">@keen_lab</a>)ì˜ -Wen Niu(<a href="https://twitter.com/NWMonster">@NWMonster</a>): CVE-2016-3809 + Wen Niu(<a href="https://twitter.com/NWMonster">@NWMonster</a>) : CVE-2016-3809 </li><li>Tencent Security Platform Departmentì˜ Xiling Gong: CVE-2016-3745 </li><li>Chinese Academy of Sciences Institute of Software TCA Labì˜ Yacong Gu: CVE-2016-3761 @@ -171,9 +172,9 @@ AOSP ë³€ê²½ì‚¬í• ëª©ë¡ê³¼ ê°™ì´ ë¬¸ì œë¥¼ í•´ê²°í•œ 공개 변경사í•ì„ ë² <h3 id="remote-code-execution-vulnerability-in-mediaserver"> 미디어 ì„œë²„ì˜ ì›ê²© 코드 실행 취약성</h3> -<p>미디어 ì„œë²„ì˜ ì›ê²© 코드 실행 취약성으로 ì¸í•´ 특별히 ì œìž‘ëœ íŒŒì¼ì„ 사용하는 -공격ìžê°€ 미디어 íŒŒì¼ ë° ë°ì´í„° 처리 ì¤‘ì— ë©”ëª¨ë¦¬ ì†ìƒì„ ì¼ìœ¼í‚¬ 수 -있습니다. ì´ ë¬¸ì œëŠ” 미디어 서버 프로세스 ë‚´ì—ì„œ ì›ê²© 코드를 ì‹¤í–‰í• ê°€ëŠ¥ì„±ì´ ìžˆìœ¼ë¯€ë¡œ +<p>미디어 ì„œë²„ì˜ ì›ê²© 코드 실행 취약성으로 ì¸í•´ 특별히 ì œìž‘ëœ íŒŒì¼ì„ +사용하는 공격ìžê°€ 미디어 íŒŒì¼ ë° ë°ì´í„° 처리 ì¤‘ì— ë©”ëª¨ë¦¬ ì†ìƒì„ +ì¼ìœ¼í‚¬ 수 있습니다. ì´ ë¬¸ì œëŠ” 미디어 서버 프로세스 ë‚´ì—ì„œ ì›ê²© 코드를 ì‹¤í–‰í• ê°€ëŠ¥ì„±ì´ ìžˆìœ¼ë¯€ë¡œ 심ê°ë„ 심ê°ìœ¼ë¡œ í‰ê°€ë©ë‹ˆë‹¤. 미디어 서버 프로세스는 오디오와 ë™ì˜ìƒ ìŠ¤íŠ¸ë¦¼ë¿ ì•„ë‹ˆë¼ íƒ€ì‚¬ ì•±ì´ ì¼ë°˜ì 으로 ì•¡ì„¸ìŠ¤í• ìˆ˜ 없는 ê¶Œí•œì— ì•¡ì„¸ìŠ¤í• ìˆ˜ 있습니다.</p> @@ -374,8 +375,8 @@ libpngì˜ ê¶Œí•œ 승격 취약성</h3> <h3 id="elevation-of-privilege-vulnerability-in-mediaserver"> 미디어 ì„œë²„ì˜ ê¶Œí•œ 승격 취약성</h3> <p>미디어 ì„œë²„ì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ 로컬 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ ìŠ¹ê²©ëœ ì‹œìŠ¤í…œ ì• í”Œë¦¬ì¼€ì´ì…˜ 컨í…스트 ë‚´ì—ì„œ ìž„ì˜ì˜ 코드를 ì‹¤í–‰í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” -<a href="https://developer.android.com/guide/topics/manifest/permission-element.html#plevel">서명</a> ë˜ëŠ” -<a href="https://developer.android.com/guide/topics/manifest/permission-element.html#plevel">SignatureOrSystem</a> +<a href="https://developer.android.com/guide/topics/manifest/permission-element.html#plevel">서명</a> +ë˜ëŠ” <a href="https://developer.android.com/guide/topics/manifest/permission-element.html#plevel">SignatureOrSystem</a> 권한과 ê°™ì´ íƒ€ì‚¬ ì• í”Œë¦¬ì¼€ì´ì…˜ì´ ì•¡ì„¸ìŠ¤í• ìˆ˜ 없는 ìŠ¹ê²©ëœ ê¶Œí•œìœ¼ë¡œì˜ ë¡œì»¬ 액세스를 부여하는 ë° ì‚¬ìš©ë 수 있으므로 심ê°ë„ 높ìŒìœ¼ë¡œ í‰ê°€ë©ë‹ˆë‹¤.</p> @@ -1627,9 +1628,9 @@ Qualcomm USB ë“œë¼ì´ë²„ì˜ ê¶Œí•œ 승격 취약성</h3> <h3 id="elevation-of-privilege-vulnerability-in-qualcomm-wi-fi-driver"> Qualcomm Wi-Fi ë“œë¼ì´ë²„ì˜ ê¶Œí•œ 승격 취약성</h3> <p>Qualcomm Wi-Fi ë“œë¼ì´ë²„ì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ -로컬 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ ì»¤ë„ ì»¨í…스트 ë‚´ì—ì„œ ìž„ì˜ì˜ 코드를 ì‹¤í–‰í• ìˆ˜ -있습니다. ì´ ë¬¸ì œëŠ” ë¨¼ì € ê¶Œí•œì´ ì„¤ì •ëœ í”„ë¡œì„¸ìŠ¤ì— ì¹¨íˆ¬í•´ì•¼ë§Œ 실행 -가능하므로 심ê°ë„ 높ìŒìœ¼ë¡œ í‰ê°€ë©ë‹ˆë‹¤.</p> +로컬 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ ì»¤ë„ ì»¨í…스트 ë‚´ì—ì„œ ìž„ì˜ì˜ 코드를 +ì‹¤í–‰í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” ë¨¼ì € ê¶Œí•œì´ ì„¤ì •ëœ í”„ë¡œì„¸ìŠ¤ì— +침투해야만 실행 가능하므로 심ê°ë„ 높ìŒìœ¼ë¡œ í‰ê°€ë©ë‹ˆë‹¤.</p> <table> <colgroup><col width="19%" /> @@ -1658,7 +1659,7 @@ Qualcomm Wi-Fi ë“œë¼ì´ë²„ì˜ ê¶Œí•œ 승격 취약성</h3> Qualcomm ì¹´ë©”ë¼ ë“œë¼ì´ë²„ì˜ ê¶Œí•œ 승격 취약성</h3> <p>Qualcomm ì¹´ë©”ë¼ ë“œë¼ì´ë²„ì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ 로컬 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ ì»¤ë„ ì»¨í…스트 ë‚´ì—ì„œ ìž„ì˜ì˜ 코드를 -ì‹¤í–‰í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” ë¨¼ì € ê¶Œí•œì´ ì„¤ì •ëœ í”„ë¡œì„¸ìŠ¤ì— ì¹¨íˆ¬í•´ì•¼ë§Œ 실행 +ì‹¤í–‰í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” ë¨¼ì € ê¶Œí•œì´ ì„¤ì •ëœ ì ˆì°¨ì— ì¹¨íˆ¬í•´ì•¼ë§Œ 실행 가능하므로 심ê°ë„ 높ìŒìœ¼ë¡œ í‰ê°€ë©ë‹ˆë‹¤.</p> <table> @@ -1764,9 +1765,9 @@ MediaTek ì „ì› ë“œë¼ì´ë²„ì˜ ê¶Œí•œ 승격 취약성</h3> <h3 id="elevation-of-privilege-vulnerability-in-qualcomm-wi-fi-driver-2"> Qualcomm Wi-Fi ë“œë¼ì´ë²„ì˜ ê¶Œí•œ 승격 취약성</h3> <p>Qualcomm Wi-Fi ë“œë¼ì´ë²„ì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ -로컬 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ ì»¤ë„ ì»¨í…스트 ë‚´ì—ì„œ ìž„ì˜ì˜ 코드를 ì‹¤í–‰í• ìˆ˜ -있습니다. ì´ ë¬¸ì œëŠ” ë¨¼ì € ê¶Œí•œì´ ì„¤ì •ëœ í”„ë¡œì„¸ìŠ¤ì— ì¹¨íˆ¬í•´ì•¼ë§Œ 실행 -가능하므로 심ê°ë„ 높ìŒìœ¼ë¡œ í‰ê°€ë©ë‹ˆë‹¤.</p> +로컬 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ ì»¤ë„ ì»¨í…스트 ë‚´ì—ì„œ ìž„ì˜ì˜ 코드를 +ì‹¤í–‰í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” ë¨¼ì € ê¶Œí•œì´ ì„¤ì •ëœ í”„ë¡œì„¸ìŠ¤ì— +침투해야만 실행 가능하므로 심ê°ë„ 높ìŒìœ¼ë¡œ í‰ê°€ë©ë‹ˆë‹¤.</p> <table> <colgroup><col width="19%" /> @@ -2248,8 +2249,8 @@ MediaTek ë™ì˜ìƒ ì½”ë± ë“œë¼ì´ë²„ì˜ ì •ë³´ 공개 취약성</h3> Qualcomm USB ë“œë¼ì´ë²„ì˜ ì •ë³´ 공개 취약성</h3> <p>Qualcomm USB ë“œë¼ì´ë²„ì˜ ì •ë³´ 공개 취약성으로 ì¸í•´ 로컬 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ 권한 ìˆ˜ì¤€ì„ ë²—ì–´ë‚œ ë°ì´í„°ì— ì•¡ì„¸ìŠ¤í• ìˆ˜ 있습니다. -ì´ ë¬¸ì œëŠ” ë¨¼ì € ê¶Œí•œì´ ì„¤ì •ëœ ì ˆì°¨ì— ì¹¨íˆ¬í•´ì•¼ë§Œ -실행 가능하므로 심ê°ë„ 보통으로 í‰ê°€ë©ë‹ˆë‹¤.</p> +ì´ ë¬¸ì œëŠ” ë¨¼ì € ê¶Œí•œì´ ì„¤ì •ëœ ì ˆì°¨ì— ì¹¨íˆ¬í•´ì•¼ë§Œ 실행 가능하므로 +심ê°ë„ 보통으로 í‰ê°€ë©ë‹ˆë‹¤.</p> <table> <colgroup><col width="19%" /> @@ -2420,7 +2421,8 @@ Qualcomm 부트로ë”ì˜ ì„œë¹„ìŠ¤ 거부(DoS) 취약성</h3> </tr> </tbody></table> <h2 id="common-questions-and-answers">ì¼ë°˜ì ì¸ ì§ˆë¬¸ ë° ë‹µë³€</h2> -<p>ì´ ì„¹ì…˜ì—서는 게시íŒì„ ì½ì€ ë’¤ ì œê¸°ë 수 있는 ì¼ë°˜ì ì¸ ì§ˆë¬¸ì— ëŒ€í•œ ë‹µë³€ì„ ì œì‹œí•©ë‹ˆë‹¤.</p> +<p>ì´ ì„¹ì…˜ì—서는 게시íŒì„ ì½ì€ ë’¤ ì œê¸°ë 수 있는 ì¼ë°˜ì ì¸ ì§ˆë¬¸ì˜ ë‹µë³€ì„ +ì œì‹œí•©ë‹ˆë‹¤.</p> <p><strong>1. ë‚´ 기기가 ì—…ë°ì´íŠ¸ë˜ì–´ ì´ ë¬¸ì œê°€ í•´ê²°ë˜ì—ˆëŠ”지 어떻게 ì•Œ 수 있나요?</strong></p> <p>2016-07-01 보안 패치 문ìžì—´ 수준과 ê´€ë ¨ëœ ëª¨ë“ ë¬¸ì œëŠ” 2016-07-01 diff --git a/ko/security/bulletin/2016-08-01.html b/ko/security/bulletin/2016-08-01.html index ea9bb52f..9bef71a8 100644 --- a/ko/security/bulletin/2016-08-01.html +++ b/ko/security/bulletin/2016-08-01.html @@ -23,7 +23,7 @@ <p><em>2016ë…„ 8ì›” 1ì¼ ê²Œì‹œë¨ | 2016ë…„ 10ì›” 21ì¼ ì—…ë°ì´íŠ¸ë¨</em></p> <p> Android 보안 게시íŒì—서는 Android ê¸°ê¸°ì— ì˜í–¥ì„ 미치는 보안 취약성 -ì„¸ë¶€ì •ë³´ë¥¼ 다룹니다. 게시íŒê³¼ 함께 ë¬´ì„ ì—…ë°ì´íŠ¸ë¥¼ 통해 +ì„¸ë¶€ì •ë³´ë¥¼ 다룹니다. 게시íŒê³¼ 함께 ë¬´ì„ (OTA) ì—…ë°ì´íŠ¸ë¥¼ 통해 Nexus 기기 보안 ì—…ë°ì´íŠ¸ê°€ 출시ë˜ì—ˆìŠµë‹ˆë‹¤. ë˜í•œ Nexus 펌웨어 ì´ë¯¸ì§€ë„ <a href="https://developers.google.com/android/nexus/images">Google ê°œë°œìž ì‚¬ì´íŠ¸</a>ì— ì¶œì‹œë˜ì—ˆìŠµë‹ˆë‹¤. ë‹¤ìŒ ë¬¸ì œëŠ” 2016ë…„ 8ì›” 5ì¼ ë³´ì•ˆ 패치 수준 ì´ìƒì—ì„œ @@ -48,11 +48,11 @@ Nexus 펌웨어 ì´ë¯¸ì§€ë„ <a href="https://developers.google.com/android/nexu <p> ì‹¤ì œ ê³ ê°ì´ 새로 ë³´ê³ ëœ ì´ëŸ¬í•œ ë¬¸ì œë¡œ ì¸í•´ 악용당했다는 ì‹ ê³ ëŠ” ì ‘ìˆ˜ë˜ì§€ 않았습니다. SafetyNetê³¼ ê°™ì´ -Android 플랫í¼ì˜ -ë³´ì•ˆì„ ê°œì„ í•˜ëŠ” <a href="/security/enhancements/index.html">Android -보안 í”Œëž«í¼ ë³´í˜¸</a> -ë° ì„œë¹„ìŠ¤ 보호 ê¸°ëŠ¥ì— ê´€í•´ ìžì„¸ížˆ ì•Œì•„ë³´ë ¤ë©´ -<a href="#mitigations">Android ë° Google 서비스 완화</a> ì„¹ì…˜ì„ ì°¸ì¡°í•˜ì„¸ìš”. +Android 플랫í¼ì˜ ë³´ì•ˆì„ ê°œì„ í•˜ëŠ” +<a href="/security/enhancements/index.html">Android 보안 í”Œëž«í¼ ë³´í˜¸</a> ë° ì„œë¹„ìŠ¤ 보호 ê¸°ëŠ¥ì— ê´€í•´ +ìžì„¸ížˆ ì•Œì•„ë³´ë ¤ë©´ +<a href="#mitigations">Android ë° Google 서비스 완화</a> +ì„¹ì…˜ì„ ì°¸ì¡°í•˜ì„¸ìš”. </p> <p> ëª¨ë“ ê³ ê°ì€ 기기ì—ì„œ ì´ ì—…ë°ì´íŠ¸ë¥¼ 수ë½í•˜ëŠ” ê²ƒì´ ì¢‹ìŠµë‹ˆë‹¤. @@ -87,12 +87,12 @@ Android 플랫í¼ì˜ <li>Android í”Œëž«í¼ ìµœì‹ ë²„ì „ì˜ í–¥ìƒëœ 기능으로 Androidì˜ ì—¬ëŸ¬ ë¬¸ì œë¥¼ 악용하기가 ë”ìš± ì–´ë ¤ì›Œì¡ŒìŠµë‹ˆë‹¤. 가능하다면 ëª¨ë“ ì‚¬ìš©ìžëŠ” ìµœì‹ ë²„ì „ì˜ Androidë¡œ ì—…ë°ì´íŠ¸í•˜ëŠ” ê²ƒì´ ì¢‹ìŠµë‹ˆë‹¤.</li> -<li>Android 보안팀ì—서는 <a href="http://static.googleusercontent.com/media/source.android.com/en//security/reports/Google_Android_Security_PHA_classifications.pdf">ìœ í•´í• ìˆ˜ 있는 ì• í”Œë¦¬ì¼€ì´ì…˜</a>ì— ê´€í•´ -사용ìžì—게 ê²½ê³ ë¥¼ 보내는 <a href="http://static.googleusercontent.com/media/source.android.com/en//security/reports/Google_Android_Security_2015_Report_Final.pdf">앱 ì¸ì¦ ë° SafetyNet</a>ì„ ì‚¬ìš©í•˜ì—¬ -악용사례를 ì ê·¹ì 으로 모니터ë§í•©ë‹ˆë‹¤. 앱 ì¸ì¦ì€ <a href="http://www.android.com/gms">Google ëª¨ë°”ì¼ ì„œë¹„ìŠ¤</a>ê°€ ì ìš©ëœ ê¸°ê¸°ì— ê¸°ë³¸ì 으로 사용 ì„¤ì •ë˜ì–´ 있으며 Google Play 외부ì—ì„œ +<li>Android 보안팀ì—서는 <a href="http://static.googleusercontent.com/media/source.android.com/en//security/reports/Google_Android_Security_PHA_classifications.pdf">ìœ í•´í• ìˆ˜ 있는 ì• í”Œë¦¬ì¼€ì´ì…˜</a>ì— ê´€í•´ 사용ìžì—게 +ê²½ê³ ë¥¼ 보내는 <a href="http://static.googleusercontent.com/media/source.android.com/en//security/reports/Google_Android_Security_2015_Report_Final.pdf">앱 ì¸ì¦ ë° SafetyNet</a>ì„ ì‚¬ìš©í•˜ì—¬ 악용사례를 ì ê·¹ì 으로 +모니터ë§í•©ë‹ˆë‹¤. 앱 ì¸ì¦ì€ <a href="http://www.android.com/gms">Google ëª¨ë°”ì¼ ì„œë¹„ìŠ¤</a>ê°€ ì ìš©ëœ ê¸°ê¸°ì— ê¸°ë³¸ì 으로 사용 ì„¤ì •ë˜ì–´ 있으며 Google Play 외부ì—ì„œ ê°€ì ¸ì˜¨ ì• í”Œë¦¬ì¼€ì´ì…˜ì„ 설치하는 사용ìžì—게 특히 중요합니다. Google Play ë‚´ì—ì„œ 기기 루팅 ë„구는 금지ë˜ì–´ 있지만 -사용ìžê°€ ì¶œì²˜ì— ìƒê´€ì—†ì´ 루팅 ì• í”Œë¦¬ì¼€ì´ì…˜ì„ ì„¤ì¹˜í•˜ë ¤ 하면 +사용ìžê°€ ê°ì§€ëœ 루팅 ì• í”Œë¦¬ì¼€ì´ì…˜ì„ ì„¤ì¹˜í•˜ë ¤ 하면 ì¶œì²˜ì— ìƒê´€ì—†ì´ 앱 ì¸ì¦ì´ ê²½ê³ ë¥¼ 표시합니다. ë˜í•œ 앱 ì¸ì¦ì€ 권한 승격 ì·¨ì•½ì„±ì„ ì•…ìš©í•˜ëŠ” 것으로 ì•Œë ¤ì§„ 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì„ ì‹ë³„í•˜ê³ ì°¨ë‹¨í•©ë‹ˆë‹¤. ì´ëŸ¬í•œ ì• í”Œë¦¬ì¼€ì´ì…˜ì´ ì´ë¯¸ ì„¤ì¹˜ëœ ê²½ìš° 앱 ì¸ì¦ì—ì„œ 사용ìžì—게 @@ -112,9 +112,10 @@ CVE-2016-2504</li> <li><a href="http://c0reteam.org">C0RE Team</a>ì˜ Chiachih Wu(<a href="https://twitter.com/chiachih_wu">@chiachih_wu</a>), Mingjian Zhou(<a href="https://twitter.com/Mingjian_Zhou">@Mingjian_Zhou</a>), Xuxian Jiang: CVE-2016-3844</li> -<li><a href="http://c0reteam.org">C0RE Team</a>ì˜ Chiachih Wu(<a href="https://twitter.com/chiachih_wu">@chiachih_wu</a>), -Yuan-Tsung Lo(<a href="mailto:computernik@gmail.com">computernik@gmail.com)</a>, -Xuxian Jiang: CVE-2016-3857</li> +<li><a href="http://c0reteam.org">C0RE Team</a>ì˜ +Chiachih Wu(<a href="https://twitter.com/chiachih_wu">@chiachih_wu</a>), +Yuan-Tsung Lo(<a href="mailto:computernik@gmail.com">computernik@gmail.com)</a>, Xuxian Jiang +: CVE-2016-3857</li> <li>Googleì˜ David Benjamin, Kenny Root: CVE-2016-3840</li> <li><a href="http://jaq.alibaba.com">Alibaba ëª¨ë°”ì¼ ë³´ì•ˆíŒ€</a>ì˜ Dawei Peng(<a href="http://weibo.com/u/5622360291">Vinc3nt4H</a>): CVE-2016-3822</li> <li>Tencent KeenLab(<a href="https://twitter.com/keen_lab">@keen_lab</a>)ì˜ @@ -148,13 +149,13 @@ Altaf Shaik: CVE-2016-3831</li> <li>Vasily Vasiliev: CVE-2016-3819</li> <li>Alibaba Inc.ì˜ Weichao Sun(<a href="https://twitter.com/sunblate">@sunblate</a>) : CVE-2016-3827, CVE-2016-3828, CVE-2016-3829</li> -<li><a href="http://blog.trendmicro.com/trendlabs-security-intelligence/author/wishwu/">Trend Micro Inc</a>ì˜ Wish Wu(<a href="http://weibo.com/wishlinux">å´æ½æµ </a>) -(<a href="https://twitter.com/wish_wu">@wish_wu</a>): CVE-2016-3843</li> +<li><a href="http://blog.trendmicro.com/trendlabs-security-intelligence/author/wishwu/">Trend Micro Inc</a>ì˜ +Wish Wu(<a href="http://weibo.com/wishlinux">å´æ½æµ </a>)(<a href="https://twitter.com/wish_wu">@wish_wu</a>): CVE-2016-3843</li> <li>Tencent's Xuanwu LABì˜ Yongke Wang (<a href="https://twitter.com/rudykewang">@Rudykewang</a>): CVE-2016-3836</li> </ul> <p> -CVE-2016-3843 등과 ê°™ì€ ì·¨ì•½ì„±ì„ ì™„í™”í• ìˆ˜ 있ë„ë¡ +CVE-2016-3843ê³¼ ê°™ì€ ì·¨ì•½ì„± í´ëž˜ìŠ¤ë¥¼ ì™„í™”í• ìˆ˜ 있ë„ë¡ í”Œëž«í¼ ìˆ˜ì¤€ ì—…ë°ì´íŠ¸ì— ìˆ˜ê³ í•´ì£¼ì‹ Copperhead Securityì˜ Daniel Micay와 Googleì˜ Jeff Vander Stoep, Yabin Cuiì—게 ê°ì‚¬ë“œë¦½ë‹ˆë‹¤. ì´ë²ˆ 완화는 Grsecurityì˜ Brad Spenglerì˜ ìž‘ì—…ì„ ê¸°ë°˜ìœ¼ë¡œ 합니다. </p> @@ -175,8 +176,7 @@ AOSP ë³€ê²½ì‚¬í• ëª©ë¡ê³¼ ê°™ì´ ë¬¸ì œë¥¼ í•´ê²°í•œ 공개 변경사í•ì„ ë² <p> 미디어 ì„œë²„ì˜ ì›ê²© 코드 실행 취약성으로 ì¸í•´ 특별히 ì œìž‘ëœ íŒŒì¼ì„ 사용하는 공격ìžê°€ 미디어 íŒŒì¼ ë° ë°ì´í„° 처리 ì¤‘ì— ë©”ëª¨ë¦¬ ì†ìƒì„ -ì¼ìœ¼í‚¬ 수 있습니다. ì´ ë¬¸ì œëŠ” 미디어 서버 프로세스 ë‚´ì—ì„œ ì›ê²© 코드를 ì‹¤í–‰í• ê°€ëŠ¥ì„±ì´ ìžˆìœ¼ë¯€ë¡œ -심ê°ë„ 심ê°ìœ¼ë¡œ í‰ê°€ë©ë‹ˆë‹¤. 미디어 서버 프로세스는 +ì¼ìœ¼í‚¬ 수 있습니다. ì´ ë¬¸ì œëŠ” 미디어 서버 í”„ë¡œì„¸ìŠ¤ì˜ ì»¨í…스트 ë‚´ì—ì„œ ì›ê²© 코드를 ì‹¤í–‰í• ê°€ëŠ¥ì„±ì´ ìžˆìœ¼ë¯€ë¡œ 심ê°ë„ 심ê°ìœ¼ë¡œ í‰ê°€ë©ë‹ˆë‹¤. 미디어 서버 프로세스는 오디오와 ë™ì˜ìƒ ìŠ¤íŠ¸ë¦¼ë¿ ì•„ë‹ˆë¼ íƒ€ì‚¬ ì•±ì´ ì¼ë°˜ì 으로 ì•¡ì„¸ìŠ¤í• ìˆ˜ 없는 ê¶Œí•œì— ì•¡ì„¸ìŠ¤í• ìˆ˜ 있습니다. </p> @@ -233,7 +233,7 @@ AOSP ë³€ê²½ì‚¬í• ëª©ë¡ê³¼ ê°™ì´ ë¬¸ì œë¥¼ í•´ê²°í•œ 공개 변경사í•ì„ ë² libjheadì˜ ì›ê²© 코드 실행 취약성</h3> <p> libjheadì˜ ì›ê²© 코드 실행 취약성으로 ì¸í•´ 특별히 ì œìž‘ëœ íŒŒì¼ì„ 사용하는 -공격ìžê°€ ê¶Œí•œì´ ì„¤ì •ë˜ì§€ ì•Šì€ ì ˆì°¨ì˜ ì»¨í…스트 ë‚´ì—ì„œ ìž„ì˜ì˜ 코드를 ì‹¤í–‰í• ìˆ˜ +공격ìžê°€ ê¶Œí•œì´ ì„¤ì •ë˜ì§€ ì•Šì€ í”„ë¡œì„¸ìŠ¤ì˜ ì»¨í…스트 ë‚´ì—ì„œ ìž„ì˜ì˜ 코드를 ì‹¤í–‰í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” ì´ ë¼ì´ë¸ŒëŸ¬ë¦¬ë¥¼ 사용하는 ì• í”Œë¦¬ì¼€ì´ì…˜ì—ì„œ ì›ê²© 코드를 ì‹¤í–‰í• ê°€ëŠ¥ì„±ì´ ìžˆìœ¼ë¯€ë¡œ 심ê°ë„ 높ìŒìœ¼ë¡œ í‰ê°€ë©ë‹ˆë‹¤. </p> @@ -267,8 +267,8 @@ libjheadì˜ ì›ê²© 코드 실행 취약성으로 ì¸í•´ 특별히 ì œìž‘ëœ íŒŒì 미디어 ì„œë²„ì˜ ê¶Œí•œ 승격 취약성</h3> <p> 미디어 ì„œë²„ì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ 로컬 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ -ê¶Œí•œì´ ì„¤ì •ëœ ì ˆì°¨ì˜ ì»¨í…스트 ë‚´ì—ì„œ ìž„ì˜ì˜ 코드를 ì‹¤í–‰í• ìˆ˜ -있습니다. ì´ ë¬¸ì œëŠ” 보통 타사 ì• í”Œë¦¬ì¼€ì´ì…˜ì— ì•¡ì„¸ìŠ¤í• ìˆ˜ 없는 ìŠ¹ê²©ëœ +ê¶Œí•œì´ ì„¤ì •ëœ í”„ë¡œì„¸ìŠ¤ì˜ ì»¨í…스트 ë‚´ì—ì„œ ìž„ì˜ì˜ 코드를 ì‹¤í–‰í• ìˆ˜ +있습니다. ì´ ë¬¸ì œëŠ” 보통 타사 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ ì•¡ì„¸ìŠ¤í• ìˆ˜ 없는 ìŠ¹ê²©ëœ ê¶Œí•œìœ¼ë¡œì˜ ë¡œì»¬ 액세스를 부여하는 ë° ì‚¬ìš©ë 수 있으므로 심ê°ë„ 높ìŒìœ¼ë¡œ í‰ê°€ë©ë‹ˆë‹¤. </p> @@ -422,7 +422,7 @@ libjheadì˜ ì›ê²© 코드 실행 취약성으로 ì¸í•´ 특별히 ì œìž‘ëœ íŒŒì í”„ë ˆìž„ì›Œí¬ APIì˜ ê¶Œí•œ 승격 취약성</h3> <p> í”„ë ˆìž„ì›Œí¬ APIì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ 로컬 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ -다른 ì• í”Œë¦¬ì¼€ì´ì…˜ì˜ ì• í”Œë¦¬ì¼€ì´ì…˜ ë°ì´í„°ë¥¼ 분리하는 ìš´ì˜ì²´ì œ 보호를 +ì• í”Œë¦¬ì¼€ì´ì…˜ ë°ì´í„°ë¥¼ 다른 ì• í”Œë¦¬ì¼€ì´ì…˜ìœ¼ë¡œë¶€í„° 격리하는 ìš´ì˜ì²´ì œ 보호를 ìš°íšŒí• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” ì• í”Œë¦¬ì¼€ì´ì…˜ì˜ 권한 ìˆ˜ì¤€ì„ ë²—ì–´ë‚˜ëŠ” ë°ì´í„°ë¡œì˜ 액세스를 부여하는 ë° ì‚¬ìš©ë 수 있으므로 심ê°ë„ 보통으로 í‰ê°€ë©ë‹ˆë‹¤. </p> @@ -519,7 +519,7 @@ OpenSSLì˜ ì •ë³´ 공개 취약성으로 ì¸í•´ 로컬 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ </tr> </tbody></table> <p>* 지ì›ë˜ëŠ” Nexus ê¸°ê¸°ì— ì œê³µëœ ì—…ë°ì´íŠ¸ê°€ ëª¨ë‘ ì„¤ì¹˜ë˜ì—ˆë‹¤ë©´ ì´ëŸ¬í•œ -ì·¨ì•½ì„±ì— ì˜í–¥ì„ 받지 않습니다.</p> +ì·¨ì•½ì„±ì˜ ì˜í–¥ì„ 받지 않습니다.</p> <h3 id="information-disclosure-vulnerability-in-camera-apis"> ì¹´ë©”ë¼ APIì˜ ì •ë³´ 공개 취약성</h3> @@ -660,7 +660,7 @@ Wi-Fiì˜ ì •ë³´ 공개 취약성으로 ì¸í•´ 로컬 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì <p> 시스템 UIì˜ ì„œë¹„ìŠ¤ 거부 취약성으로 ì¸í•´ 로컬 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ ìž ê¸ˆ 화면ì—ì„œ 119 ì „í™”ë¥¼ 걸지 못하게 í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” -중요한 ê¸°ëŠ¥ì— ëŒ€í•œ ì›ê²© 서비스 거부 ê°€ëŠ¥ì„±ì´ ìžˆìœ¼ë¯€ë¡œ 심ê°ë„ 보통으로 +중요한 ê¸°ëŠ¥ì— ëŒ€í•œ 서비스 거부 ê°€ëŠ¥ì„±ì´ ìžˆìœ¼ë¯€ë¡œ 심ê°ë„ 보통으로 í‰ê°€ë©ë‹ˆë‹¤. </p> <table> @@ -694,7 +694,7 @@ Wi-Fiì˜ ì •ë³´ 공개 취약성으로 ì¸í•´ 로컬 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì <p> ë¸”ë£¨íˆ¬ìŠ¤ì˜ ì„œë¹„ìŠ¤ 거부 취약성으로 ì¸í•´ 로컬 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ 블루투스 기기ì—ì„œ 119 ì „í™”ë¥¼ 걸지 못하게 í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” -중요한 ê¸°ëŠ¥ì— ëŒ€í•œ ì›ê²© 서비스 거부 ê°€ëŠ¥ì„±ì´ ìžˆìœ¼ë¯€ë¡œ 심ê°ë„ 보통으로 +중요한 ê¸°ëŠ¥ì— ëŒ€í•œ 서비스 거부 ê°€ëŠ¥ì„±ì´ ìžˆìœ¼ë¯€ë¡œ 심ê°ë„ 보통으로 í‰ê°€ë©ë‹ˆë‹¤. </p> <table> @@ -737,7 +737,7 @@ AOSP ë³€ê²½ì‚¬í• ëª©ë¡ê³¼ ê°™ì´ ë¬¸ì œë¥¼ í•´ê²°í•œ 공개 변경사í•ì„ ë² <h3 id="remote-code-execution-vulnerability-in-qualcomm-wi-fi-driver"> Qualcomm Wi-Fi ë“œë¼ì´ë²„ì˜ ì›ê²© 코드 실행 취약성</h3> <p> -Qualcomm Wi-Fi ë“œë¼ì´ë²„ì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ ì›ê²© 공격ìžê°€ +Qualcomm Wi-Fi ë“œë¼ì´ë²„ì˜ ì›ê²© 코드 실행 취약성으로 ì¸í•´ ì›ê²© 공격ìžê°€ ì»¤ë„ ì»¨í…스트 ë‚´ì—ì„œ ìž„ì˜ì˜ 코드를 ì‹¤í–‰í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” ì˜êµ¬ì ì¸ ë¡œì»¬ 기기 ì†ìƒì„ ì¼ìœ¼í‚¬ ê°€ëŠ¥ì„±ì´ ìžˆìœ¼ë¯€ë¡œ 심ê°ë„ 심ê°ìœ¼ë¡œ @@ -750,7 +750,7 @@ Qualcomm Wi-Fi ë“œë¼ì´ë²„ì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ ì›ê²© ê³µê² <col width="23%" /> <col width="17%" /> </colgroup><tbody><tr> - <th>공통 취약성 ë° ë…¸ì¶œ</th> + <th>CVE</th> <th>참조</th> <th>심ê°ë„</th> <th>ì—…ë°ì´íŠ¸ëœ Nexus 기기</th> @@ -776,7 +776,7 @@ QC-CR#553941</a> ì›ê²© 코드 실행 취약성</h3> <p> Conscryptì˜ ì›ê²© 권한 실행 취약성으로 ì¸í•´ ì›ê²© 공격ìžê°€ ê¶Œí•œì´ ì„¤ì •ëœ -ì ˆì°¨ì˜ ì»¨í…스트 ë‚´ì—ì„œ ìž„ì˜ì˜ 코드를 ì‹¤í–‰í• ìˆ˜ 있습니다. +í”„ë¡œì„¸ìŠ¤ì˜ ì»¨í…스트 ë‚´ì—ì„œ ìž„ì˜ì˜ 코드를 ì‹¤í–‰í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” ì›ê²© 코드를 ì‹¤í–‰í• ê°€ëŠ¥ì„±ì´ ìžˆìœ¼ë¯€ë¡œ 심ê°ë„ 심ê°ìœ¼ë¡œ í‰ê°€ë©ë‹ˆë‹¤. </p> <table> @@ -787,7 +787,7 @@ Conscryptì˜ ì›ê²© 권한 실행 취약성으로 ì¸í•´ ì›ê²© 공격ìžê°€ 권 <col width="17%" /> <col width="17%" /> </colgroup><tbody><tr> - <th>공통 취약성 ë° ë…¸ì¶œ</th> + <th>CVE</th> <th>참조</th> <th>심ê°ë„</th> <th>ì—…ë°ì´íŠ¸ëœ Nexus 기기</th> @@ -808,8 +808,8 @@ Conscryptì˜ ì›ê²© 권한 실행 취약성으로 ì¸í•´ ì›ê²© 공격ìžê°€ 권 <h3 id="elevation-of-privilege-vulnerability-in-qualcomm-components"> Qualcomm êµ¬ì„±ìš”ì†Œì˜ ê¶Œí•œ 승격 취약성</h3> <p> -아래 í‘œì—는 부트로ë”, ì¹´ë©”ë¼ ë“œë¼ì´ë²„, ìºë¦í„° ë“œë¼ì´ë¸Œ, 네트워í¬, -사운드 ë“œë¼ì´ë²„ ë° ë™ì˜ìƒ ë“œë¼ì´ë²„를 비롯한 Qualcomm êµ¬ì„±ìš”ì†Œì— +아래 í‘œì—는 부트로ë”, ì¹´ë©”ë¼ ë“œë¼ì´ë²„, ìºë¦í„° ë“œë¼ì´ë²„, 네트워í¬, +사운드 ë“œë¼ì´ë²„, ë™ì˜ìƒ ë“œë¼ì´ë²„를 비롯한 Qualcomm êµ¬ì„±ìš”ì†Œì— ì˜í–¥ì„ 주는 보안 ì·¨ì•½ì„±ì´ í¬í•¨ë˜ì–´ 있습니다. </p> <p> @@ -824,7 +824,7 @@ Qualcomm êµ¬ì„±ìš”ì†Œì˜ ê¶Œí•œ 승격 취약성</h3> <col width="23%" /> <col width="17%" /> </colgroup><tbody><tr> - <th>공통 취약성 ë° ë…¸ì¶œ</th> + <th>CVE</th> <th>참조</th> <th>심ê°ë„</th> <th>ì—…ë°ì´íŠ¸ëœ Nexus 기기</th> @@ -1019,7 +1019,7 @@ QC-CR#547479</a> </p> </td> <td>높ìŒ</td> - <td>구글 넥서스 5</td> + <td>Nexus 5</td> <td>2014ë…„ 4ì›” 30ì¼</td> </tr> <tr> @@ -1172,7 +1172,7 @@ QC-CR#770548</a> <a href="https://us.codeaurora.org/cgit/quic/la//kernel/msm-3.10/commit/?id=51c39420e3a49d1a7f05a77c64369b7623088238"> QC-CR#766022</a></p></td> <td>높ìŒ</td> - <td>구글 넥서스 6</td> + <td>Nexus 6</td> <td>2015ë…„ 3ì›” 31ì¼</td> </tr> <tr> @@ -1192,7 +1192,7 @@ QC-CR#779021</a></p></td> <a href="https://us.codeaurora.org/cgit/quic/la//kernel/msm-3.10/commit/?id=e13ebd727d161db7003be6756e61283dce85fa3b"> QC-CR#792367</a></p></td> <td>높ìŒ</td> - <td>구글 넥서스 6</td> + <td>Nexus 6</td> <td>2015ë…„ 4ì›” 30ì¼</td> </tr> <tr> @@ -1212,7 +1212,7 @@ QC-CR#792473</a></p></td> <a href="https://us.codeaurora.org/cgit/quic/la//kernel/msm-3.10/commit/?id=9ec380c06bbd79493828fcc3c876d8a53fd3369f"> QC-CR#803246</a></p></td> <td>높ìŒ</td> - <td>구글 넥서스 6</td> + <td>Nexus 6</td> <td>2015ë…„ 6ì›” 30ì¼</td> </tr> <tr> @@ -1225,7 +1225,7 @@ QC-CR#794217</a></p> <a href="https://us.codeaurora.org/cgit/quic/la//kernel/msm/commit/?id=ad376e4053b87bd58f62f45b6df2c5544bc21aee"> QC-CR#836226</a></p></td> <td>높ìŒ</td> - <td>구글 넥서스 5</td> + <td>Nexus 5</td> <td>2015ë…„ 9ì›” 11ì¼</td> </tr> <tr> @@ -1235,7 +1235,7 @@ QC-CR#836226</a></p></td> <a href="https://us.codeaurora.org/cgit/quic/la/kernel/msm-3.10/commit/?id=c10f03f191307f7114af89933f2d91b830150094"> QC-CR#550061</a></p></td> <td>보통</td> - <td>구글 넥서스 5</td> + <td>Nexus 5</td> <td>2014ë…„ 3ì›” 13ì¼</td> </tr> <tr> @@ -1266,7 +1266,7 @@ QC-CR#529177</a></p></td> <col width="23%" /> <col width="17%" /> </colgroup><tbody><tr> - <th>공통 취약성 ë° ë…¸ì¶œ</th> + <th>CVE</th> <th>참조</th> <th>심ê°ë„</th> <th>ì—…ë°ì´íŠ¸ëœ Nexus 기기</th> @@ -1310,7 +1310,7 @@ Qualcomm GPU ë“œë¼ì´ë²„ì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ <col width="23%" /> <col width="17%" /> </colgroup><tbody><tr> - <th>공통 취약성 ë° ë…¸ì¶œ</th> + <th>CVE</th> <th>참조</th> <th>심ê°ë„</th> <th>ì—…ë°ì´íŠ¸ëœ Nexus 기기</th> @@ -1350,7 +1350,7 @@ Qualcomm 성능 êµ¬ì„±ìš”ì†Œì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ 기기를 ìˆ˜ë¦¬í•˜ë ¤ë©´ ìš´ì˜ì²´ì œë¥¼ 재설치해야 í• ìˆ˜ë„ ìžˆìŠµë‹ˆë‹¤. </p> <p class="note"> -<strong>ì°¸ê³ :</strong> ì´ ê²Œì‹œíŒ A-29119870ì— ì´ ì·¨ì•½ì„±ì„ ì™„í™”í•˜ê¸° 위해 ì œìž‘ëœ +<strong>ì°¸ê³ :</strong> ì´ ê²Œì‹œíŒ A-29119870ì— ì´ ì·¨ì•½ì„± í´ëž˜ìŠ¤ë¥¼ 완화하기 위해 ì œìž‘ëœ í”Œëž«í¼ ìˆ˜ì¤€ ì—…ë°ì´íŠ¸ê°€ 있습니다. </p> <table> @@ -1360,7 +1360,7 @@ Qualcomm 성능 êµ¬ì„±ìš”ì†Œì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ <col width="23%" /> <col width="17%" /> </colgroup><tbody><tr> - <th>공통 취약성 ë° ë…¸ì¶œ</th> + <th>CVE</th> <th>참조</th> <th>심ê°ë„</th> <th>ì—…ë°ì´íŠ¸ëœ Nexus 기기</th> @@ -1398,7 +1398,7 @@ Qualcomm 성능 êµ¬ì„±ìš”ì†Œì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ <col width="23%" /> <col width="17%" /> </colgroup><tbody><tr> - <th>공통 취약성 ë° ë…¸ì¶œ</th> + <th>CVE</th> <th>참조</th> <th>심ê°ë„</th> <th>ì—…ë°ì´íŠ¸ëœ Nexus 기기</th> @@ -1423,7 +1423,7 @@ Qualcomm 성능 êµ¬ì„±ìš”ì†Œì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ <p> ì»¤ë„ ë©”ëª¨ë¦¬ ì‹œìŠ¤í…œì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ 로컬 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ ì»¤ë„ ì»¨í…스트 ë‚´ì—ì„œ ìž„ì˜ì˜ 코드를 ì‹¤í–‰í• ìˆ˜ -있습니다. ì´ ë¬¸ì œëŠ” ë¨¼ì € ê¶Œí•œì´ ì„¤ì •ëœ ì ˆì°¨ì— ì¹¨íˆ¬í•´ì•¼ë§Œ 실행 +있습니다. ì´ ë¬¸ì œëŠ” ë¨¼ì € ê¶Œí•œì´ ì„¤ì •ëœ í”„ë¡œì„¸ìŠ¤ì— ì¹¨íˆ¬í•´ì•¼ë§Œ 실행 가능하므로 심ê°ë„ 높ìŒìœ¼ë¡œ í‰ê°€ë©ë‹ˆë‹¤. </p> <table> @@ -1433,7 +1433,7 @@ Qualcomm 성능 êµ¬ì„±ìš”ì†Œì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ <col width="23%" /> <col width="17%" /> </colgroup><tbody><tr> - <th>공통 취약성 ë° ë…¸ì¶œ</th> + <th>CVE</th> <th>참조</th> <th>심ê°ë„</th> <th>ì—…ë°ì´íŠ¸ëœ Nexus 기기</th> @@ -1446,7 +1446,7 @@ Qualcomm 성능 êµ¬ì„±ìš”ì†Œì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ <a href="http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4e7c22d447bb6d7e37bfe39ff658486ae78e8d77"> 업스트림 커ë„</a></p></td> <td>높ìŒ</td> - <td>넥서스 í”Œë ˆì´ì–´</td> + <td>Nexus Player</td> <td>2015ë…„ 2ì›” 13ì¼</td> </tr> <tr> @@ -1456,7 +1456,7 @@ Qualcomm 성능 êµ¬ì„±ìš”ì†Œì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ <a href="http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=8b8addf891de8a00e4d39fc32f93f7c5eb8feceb"> 업스트림 커ë„</a></p></td> <td>높ìŒ</td> - <td>넥서스 í”Œë ˆì´ì–´</td> + <td>Nexus Player</td> <td>2016ë…„ 3ì›” 25ì¼</td> </tr> </tbody></table> @@ -1466,7 +1466,7 @@ Qualcomm 성능 êµ¬ì„±ìš”ì†Œì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ <p> ì»¤ë„ ì‚¬ìš´ë“œ êµ¬ì„±ìš”ì†Œì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ 로컬 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ ì»¤ë„ ì»¨í…스트 ë‚´ì—ì„œ ìž„ì˜ì˜ 코드를 -ì‹¤í–‰í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” ë¨¼ì € ê¶Œí•œì´ ì„¤ì •ëœ ì ˆì°¨ì— +ì‹¤í–‰í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” ë¨¼ì € ê¶Œí•œì´ ì„¤ì •ëœ í”„ë¡œì„¸ìŠ¤ì— ì¹¨íˆ¬í•´ì•¼ë§Œ 실행 가능하므로 심ê°ë„ 높ìŒìœ¼ë¡œ í‰ê°€ë©ë‹ˆë‹¤. </p> <table> @@ -1476,7 +1476,7 @@ Qualcomm 성능 êµ¬ì„±ìš”ì†Œì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ <col width="23%" /> <col width="17%" /> </colgroup><tbody><tr> - <th>공통 취약성 ë° ë…¸ì¶œ</th> + <th>CVE</th> <th>참조</th> <th>심ê°ë„</th> <th>ì—…ë°ì´íŠ¸ëœ Nexus 기기</th> @@ -1519,7 +1519,7 @@ Qualcomm 성능 êµ¬ì„±ìš”ì†Œì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ <p> ì»¤ë„ íŒŒì¼ ì‹œìŠ¤í…œì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ 로컬 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ ì»¤ë„ ì»¨í…스트 ë‚´ì—ì„œ ìž„ì˜ì˜ 코드를 ì‹¤í–‰í• ìˆ˜ -있습니다. ì´ ë¬¸ì œëŠ” ë¨¼ì € ê¶Œí•œì´ ì„¤ì •ëœ ì ˆì°¨ì— ì¹¨íˆ¬í•´ì•¼ë§Œ 실행 +있습니다. ì´ ë¬¸ì œëŠ” ë¨¼ì € ê¶Œí•œì´ ì„¤ì •ëœ í”„ë¡œì„¸ìŠ¤ì— ì¹¨íˆ¬í•´ì•¼ë§Œ 실행 가능하므로 심ê°ë„ 높ìŒìœ¼ë¡œ í‰ê°€ë©ë‹ˆë‹¤. </p> <table> @@ -1529,7 +1529,7 @@ Qualcomm 성능 êµ¬ì„±ìš”ì†Œì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ <col width="23%" /> <col width="17%" /> </colgroup><tbody><tr> - <th>공통 취약성 ë° ë…¸ì¶œ</th> + <th>CVE</th> <th>참조</th> <th>심ê°ë„</th> <th>ì—…ë°ì´íŠ¸ëœ Nexus 기기</th> @@ -1551,7 +1551,7 @@ Qualcomm 성능 êµ¬ì„±ìš”ì†Œì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ 미디어 ì„œë²„ì˜ ê¶Œí•œ 승격 취약성</h3> <p> 미디어 ì„œë²„ì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ 로컬 악성 -ì• í”Œë¦¬ì¼€ì´ì…˜ì´ ê¶Œí•œì´ ì„¤ì •ëœ ì ˆì°¨ì˜ ì»¨í…스트 ë‚´ì—ì„œ ìž„ì˜ì˜ +ì• í”Œë¦¬ì¼€ì´ì…˜ì´ ê¶Œí•œì´ ì„¤ì •ëœ í”„ë¡œì„¸ìŠ¤ì˜ ì»¨í…스트 ë‚´ì—ì„œ ìž„ì˜ì˜ 코드를 ì‹¤í–‰í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” 타사 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ ì•¡ì„¸ìŠ¤í• ìˆ˜ 없는 ìŠ¹ê²©ëœ ê¶Œí•œìœ¼ë¡œì˜ ë¡œì»¬ 액세스를 부여하는 ë° ì‚¬ìš©ë 수 있으므로 심ê°ë„ 높ìŒìœ¼ë¡œ í‰ê°€ë©ë‹ˆë‹¤. @@ -1563,7 +1563,7 @@ Qualcomm 성능 êµ¬ì„±ìš”ì†Œì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ <col width="23%" /> <col width="17%" /> </colgroup><tbody><tr> - <th>공통 취약성 ë° ë…¸ì¶œ</th> + <th>CVE</th> <th>참조</th> <th>심ê°ë„</th> <th>ì—…ë°ì´íŠ¸ëœ Nexus 기기</th> @@ -1589,7 +1589,7 @@ N-CVE-2016-3844</p></td> <p> ì»¤ë„ ë™ì˜ìƒ ë“œë¼ì´ë²„ì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ 로컬 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ ì»¤ë„ ì»¨í…스트 ë‚´ì—ì„œ ìž„ì˜ì˜ -코드를 ì‹¤í–‰í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” ë¨¼ì € ê¶Œí•œì´ ì„¤ì •ëœ ì ˆì°¨ì— ì¹¨íˆ¬í•´ì•¼ë§Œ +코드를 ì‹¤í–‰í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” ë¨¼ì € ê¶Œí•œì´ ì„¤ì •ëœ í”„ë¡œì„¸ìŠ¤ì— ì¹¨íˆ¬í•´ì•¼ë§Œ 실행 가능하므로 심ê°ë„ 높ìŒìœ¼ë¡œ í‰ê°€ë©ë‹ˆë‹¤. </p> <table> @@ -1599,7 +1599,7 @@ N-CVE-2016-3844</p></td> <col width="23%" /> <col width="17%" /> </colgroup><tbody><tr> - <th>공통 취약성 ë° ë…¸ì¶œ</th> + <th>CVE</th> <th>참조</th> <th>심ê°ë„</th> <th>ì—…ë°ì´íŠ¸ëœ Nexus 기기</th> @@ -1609,7 +1609,7 @@ N-CVE-2016-3844</p></td> <td>CVE-2016-3845</td> <td>A-28399876*</td> <td>높ìŒ</td> - <td>구글 넥서스 5</td> + <td>Nexus 5</td> <td>2016ë…„ 4ì›” 20ì¼</td> </tr> </tbody></table> @@ -1624,7 +1624,7 @@ N-CVE-2016-3844</p></td> <p> ì§ë ¬ 주변기기 ì¸í„°íŽ˜ì´ìŠ¤ ë“œë¼ì´ë²„ì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ 로컬 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ ì»¤ë„ ì»¨í…스트 ë‚´ì—ì„œ ìž„ì˜ì˜ 코드를 -ì‹¤í–‰í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” ë¨¼ì € ê¶Œí•œì´ ì„¤ì •ëœ ì ˆì°¨ì— ì¹¨íˆ¬í•´ì•¼ë§Œ +ì‹¤í–‰í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” ë¨¼ì € ê¶Œí•œì´ ì„¤ì •ëœ í”„ë¡œì„¸ìŠ¤ì— ì¹¨íˆ¬í•´ì•¼ë§Œ 실행 가능하므로 심ê°ë„ 높ìŒìœ¼ë¡œ í‰ê°€ë©ë‹ˆë‹¤. </p> <table> @@ -1634,7 +1634,7 @@ N-CVE-2016-3844</p></td> <col width="23%" /> <col width="17%" /> </colgroup><tbody><tr> - <th>공통 취약성 ë° ë…¸ì¶œ</th> + <th>CVE</th> <th>참조</th> <th>심ê°ë„</th> <th>ì—…ë°ì´íŠ¸ëœ Nexus 기기</th> @@ -1659,7 +1659,7 @@ NVIDIA 미디어 ë“œë¼ì´ë²„ì˜ ê¶Œí•œ 승격 취약성</h3> <p> NVIDIA 미디어 ë“œë¼ì´ë²„ì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ 로컬 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ ì»¤ë„ ì»¨í…스트 ë‚´ì—ì„œ ìž„ì˜ì˜ -코드를 ì‹¤í–‰í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” ë¨¼ì € ê¶Œí•œì´ ì„¤ì •ëœ ì ˆì°¨ì— ì¹¨íˆ¬í•´ì•¼ë§Œ +코드를 ì‹¤í–‰í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” ë¨¼ì € ê¶Œí•œì´ ì„¤ì •ëœ í”„ë¡œì„¸ìŠ¤ì— ì¹¨íˆ¬í•´ì•¼ë§Œ 실행 가능하므로 심ê°ë„ 높ìŒìœ¼ë¡œ í‰ê°€ë©ë‹ˆë‹¤. </p> <table> @@ -1669,7 +1669,7 @@ NVIDIA 미디어 ë“œë¼ì´ë²„ì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ <col width="23%" /> <col width="17%" /> </colgroup><tbody><tr> - <th>공통 취약성 ë° ë…¸ì¶œ</th> + <th>CVE</th> <th>참조</th> <th>심ê°ë„</th> <th>ì—…ë°ì´íŠ¸ëœ Nexus 기기</th> @@ -1681,7 +1681,7 @@ NVIDIA 미디어 ë“œë¼ì´ë²„ì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ <p> N-CVE-2016-3847</p></td> <td>높ìŒ</td> - <td>넥서스 9</td> + <td>Nexus 9</td> <td>2016ë…„ 5ì›” 19ì¼</td> </tr> <tr> @@ -1690,7 +1690,7 @@ N-CVE-2016-3847</p></td> <p> N-CVE-2016-3848</p></td> <td>높ìŒ</td> - <td>넥서스 9</td> + <td>Nexus 9</td> <td>2016ë…„ 5ì›” 19ì¼</td> </tr> </tbody></table> @@ -1705,7 +1705,7 @@ ION ë“œë¼ì´ë²„ì˜ ê¶Œí•œ 승격 취약성</h3> <p> ION ë“œë¼ì´ë²„ì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ 로컬 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ ì»¤ë„ ì»¨í…스트 ë‚´ì—ì„œ ìž„ì˜ì˜ 코드를 -ì‹¤í–‰í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” ë¨¼ì € ê¶Œí•œì´ ì„¤ì •ëœ ì ˆì°¨ì— ì¹¨íˆ¬í•´ì•¼ë§Œ +ì‹¤í–‰í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” ë¨¼ì € ê¶Œí•œì´ ì„¤ì •ëœ í”„ë¡œì„¸ìŠ¤ì— ì¹¨íˆ¬í•´ì•¼ë§Œ 실행 가능하므로 심ê°ë„ 높ìŒìœ¼ë¡œ í‰ê°€ë©ë‹ˆë‹¤. </p> <table> @@ -1715,7 +1715,7 @@ ION ë“œë¼ì´ë²„ì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ 로컬 악성 <col width="23%" /> <col width="17%" /> </colgroup><tbody><tr> - <th>공통 취약성 ë° ë…¸ì¶œ</th> + <th>CVE</th> <th>참조</th> <th>심ê°ë„</th> <th>ì—…ë°ì´íŠ¸ëœ Nexus 기기</th> @@ -1740,7 +1740,7 @@ ION ë“œë¼ì´ë²„ì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ 로컬 악성 <p> Qualcomm 부트로ë”ì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ 로컬 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ ì»¤ë„ ì»¨í…스트 ë‚´ì—ì„œ ìž„ì˜ì˜ 코드를 -ì‹¤í–‰í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” ë¨¼ì € ê¶Œí•œì´ ì„¤ì •ëœ ì ˆì°¨ì— ì¹¨íˆ¬í•´ì•¼ë§Œ 실행 +ì‹¤í–‰í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” ë¨¼ì € ê¶Œí•œì´ ì„¤ì •ëœ í”„ë¡œì„¸ìŠ¤ì— ì¹¨íˆ¬í•´ì•¼ë§Œ 실행 가능하므로 심ê°ë„ 높ìŒìœ¼ë¡œ í‰ê°€ë©ë‹ˆë‹¤. </p> <table> @@ -1750,7 +1750,7 @@ Qualcomm 부트로ë”ì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ 로컬 <col width="26%" /> <col width="17%" /> </colgroup><tbody><tr> - <th>공통 취약성 ë° ë…¸ì¶œ</th> + <th>CVE</th> <th>참조</th> <th>심ê°ë„</th> <th>ì—…ë°ì´íŠ¸ëœ Nexus 기기</th> @@ -1788,7 +1788,7 @@ QC-CR#945164</a></p></td> <col width="17%" /> <col width="17%" /> </colgroup><tbody><tr> - <th>공통 취약성 ë° ë…¸ì¶œ</th> + <th>CVE</th> <th>참조</th> <th>심ê°ë„</th> <th>ì—…ë°ì´íŠ¸ëœ Nexus 기기</th> @@ -1815,8 +1815,7 @@ LG ì „ìž ë¶€íŠ¸ë¡œë”ì˜ ê¶Œí•œ 승격 취약성</h3> <p> LG ì „ìž ë¶€íŠ¸ë¡œë”ì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ 공격ìžê°€ ì»¤ë„ ì»¨í…스트 ë‚´ì—ì„œ ìž„ì˜ì˜ 코드를 ì‹¤í–‰í• ìˆ˜ 있습니다. -ì´ ë¬¸ì œëŠ” ë¨¼ì € ê¶Œí•œì´ ì„¤ì •ëœ ì ˆì°¨ì— ì¹¨íˆ¬í•´ì•¼ë§Œ 실행 가능하므로 심ê°ë„ 높ìŒìœ¼ë¡œ -í‰ê°€ë©ë‹ˆë‹¤. +ì´ ë¬¸ì œëŠ” ë¨¼ì € ê¶Œí•œì´ ì„¤ì •ëœ í”„ë¡œì„¸ìŠ¤ì— ì¹¨íˆ¬í•´ì•¼ë§Œ 실행 가능하므로 심ê°ë„ 높ìŒìœ¼ë¡œ í‰ê°€ë©ë‹ˆë‹¤. </p> <table> <colgroup><col width="19%" /> @@ -1825,7 +1824,7 @@ LG ì „ìž ë¶€íŠ¸ë¡œë”ì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ 공격ìžê°€ <col width="23%" /> <col width="17%" /> </colgroup><tbody><tr> - <th>공통 취약성 ë° ë…¸ì¶œ</th> + <th>CVE</th> <th>참조</th> <th>심ê°ë„</th> <th>ì—…ë°ì´íŠ¸ëœ Nexus 기기</th> @@ -1864,7 +1863,7 @@ Qualcomm êµ¬ì„±ìš”ì†Œì˜ ì •ë³´ 공개 취약성</h3> <col width="23%" /> <col width="17%" /> </colgroup><tbody><tr> - <th>공통 취약성 ë° ë…¸ì¶œ</th> + <th>CVE</th> <th>참조</th> <th>심ê°ë„</th> <th>ì—…ë°ì´íŠ¸ëœ Nexus 기기</th> @@ -1897,7 +1896,7 @@ QC-CR#786116</a></p></td> <a href="https://us.codeaurora.org/cgit/quic/la/kernel/msm-3.10/commit/?id=bfc6eee5e30a0c20bc37495233506f4f0cc4991d"> QC-CR#542223</a></p></td> <td>보통</td> - <td>구글 넥서스 5</td> + <td>Nexus 5</td> <td>2014ë…„ 3ì›” 27ì¼</td> </tr> <tr> @@ -1937,7 +1936,7 @@ QC-CR#551795</a></p></td> <a href="https://us.codeaurora.org/cgit/quic/la/kernel/msm-3.10/commit/?id=46135d80765cb70a914f02a6e7b6abe64679ec86"> QC-CR#563752</a></p></td> <td>보통</td> - <td>구글 넥서스 5</td> + <td>Nexus 5</td> <td>2014ë…„ 4ì›” 30ì¼</td> </tr> <tr> @@ -1957,7 +1956,7 @@ QC-CR#554575</a></p></td> <a href="https://us.codeaurora.org/cgit/quic/la//kernel/msm-3.10/commit/?id=8756624acb1e090b45baf07b2a8d0ebde114000e"> QC-CR#547910</a></p></td> <td>보통</td> - <td>구글 넥서스 5</td> + <td>Nexus 5</td> <td>2014ë…„ 7ì›” 3ì¼</td> </tr> <tr> @@ -1987,7 +1986,7 @@ QC-CR#570754</a></p></td> <col width="23%" /> <col width="17%" /> </colgroup><tbody><tr> - <th>공통 취약성 ë° ë…¸ì¶œ</th> + <th>CVE</th> <th>참조</th> <th>심ê°ë„</th> <th>ì—…ë°ì´íŠ¸ëœ Nexus 기기</th> @@ -2020,7 +2019,7 @@ MediaTek Wi-Fi ë“œë¼ì´ë²„ì˜ ì •ë³´ 공개 취약성으로 ì¸í•´ <col width="23%" /> <col width="17%" /> </colgroup><tbody><tr> - <th>공통 취약성 ë° ë…¸ì¶œ</th> + <th>CVE</th> <th>참조</th> <th>심ê°ë„</th> <th>ì—…ë°ì´íŠ¸ëœ Nexus 기기</th> @@ -2056,7 +2055,7 @@ USB ë“œë¼ì´ë²„ì˜ ì •ë³´ 공개 취약성으로 ì¸í•´ 로컬 악성 ì• í”Œë¦¬ <col width="23%" /> <col width="17%" /> </colgroup><tbody><tr> - <th>공통 취약성 ë° ë…¸ì¶œ</th> + <th>CVE</th> <th>참조</th> <th>심ê°ë„</th> <th>ì—…ë°ì´íŠ¸ëœ Nexus 기기</th> @@ -2126,7 +2125,7 @@ Google Play ì„œë¹„ìŠ¤ì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ 로컬 공격ìžê° <col width="17%" /> <col width="17%" /> </colgroup><tbody><tr> - <th>공통 취약성 ë° ë…¸ì¶œ</th> + <th>CVE</th> <th>참조</th> <th>심ê°ë„</th> <th>ì—…ë°ì´íŠ¸ëœ Nexus 기기</th> @@ -2165,7 +2164,7 @@ Google Play ì„œë¹„ìŠ¤ì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ 로컬 공격ìžê° <col width="18%" /> <col width="17%" /> </colgroup><tbody><tr> - <th>공통 취약성 ë° ë…¸ì¶œ</th> + <th>CVE</th> <th>참조</th> <th>심ê°ë„</th> <th>ì—…ë°ì´íŠ¸ëœ Nexus 기기</th> @@ -2187,7 +2186,7 @@ Google Play ì„œë¹„ìŠ¤ì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ 로컬 공격ìžê° ì»¤ë„ ë„¤íŠ¸ì›Œí¬ êµ¬ì„±ìš”ì†Œì˜ ì •ë³´ 공개 취약성</h3> <p> ì»¤ë„ ë„¤íŠ¸ì›Œí¬ êµ¬ì„±ìš”ì†Œì˜ ì •ë³´ 공개 취약성으로 ì¸í•´ 로컬 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ -권한 ìˆ˜ì¤€ì„ ë²—ì–´ë‚œ ë°ì´í„°ì— ì•¡ì„¸ìŠ¤í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” ë¨¼ì € ê¶Œí•œì´ ì„¤ì •ëœ ì ˆì°¨ì— ì¹¨íˆ¬í•´ì•¼ë§Œ +권한 ìˆ˜ì¤€ì„ ë²—ì–´ë‚œ ë°ì´í„°ì— ì•¡ì„¸ìŠ¤í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” ë¨¼ì € ê¶Œí•œì´ ì„¤ì •ëœ í”„ë¡œì„¸ìŠ¤ì— ì¹¨íˆ¬í•´ì•¼ë§Œ 실행 가능하므로 심ê°ë„ 보통으로 í‰ê°€ë©ë‹ˆë‹¤. </p> <table> @@ -2197,7 +2196,7 @@ Google Play ì„œë¹„ìŠ¤ì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ 로컬 공격ìžê° <col width="23%" /> <col width="17%" /> </colgroup><tbody><tr> - <th>공통 취약성 ë° ë…¸ì¶œ</th> + <th>CVE</th> <th>참조</th> <th>심ê°ë„</th> <th>ì—…ë°ì´íŠ¸ëœ Nexus 기기</th> @@ -2219,7 +2218,7 @@ Google Play ì„œë¹„ìŠ¤ì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ 로컬 공격ìžê° ì»¤ë„ ì‚¬ìš´ë“œ êµ¬ì„±ìš”ì†Œì˜ ì •ë³´ 공개 취약성</h3> <p> ì»¤ë„ ì‚¬ìš´ë“œ êµ¬ì„±ìš”ì†Œì˜ ì •ë³´ 공개 취약성으로 ì¸í•´ 로컬 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ -권한 ìˆ˜ì¤€ì„ ë²—ì–´ë‚œ ë°ì´í„°ì— ì•¡ì„¸ìŠ¤í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” ë¨¼ì € ê¶Œí•œì´ ì„¤ì •ëœ ì ˆì°¨ì— ì¹¨íˆ¬í•´ì•¼ë§Œ +권한 ìˆ˜ì¤€ì„ ë²—ì–´ë‚œ ë°ì´í„°ì— ì•¡ì„¸ìŠ¤í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” ë¨¼ì € ê¶Œí•œì´ ì„¤ì •ëœ í”„ë¡œì„¸ìŠ¤ì— ì¹¨íˆ¬í•´ì•¼ë§Œ 실행 가능하므로 심ê°ë„ 보통으로 í‰ê°€ë©ë‹ˆë‹¤. </p> <table> @@ -2398,7 +2397,7 @@ Android One, Nexus Player, Pixel C</li> <h2 id="revisions">ìˆ˜ì • ë‚´ì—</h2> <ul> - <li>2016ë…„ 8ì›” 1ì¼: 게시íŒì— 게시ë¨</li> + <li>2016ë…„ 8ì›” 1ì¼: 게시íŒì´ 게시ë¨</li> <li>2016ë…„ 8ì›” 2ì¼: 게시íŒì´ ìˆ˜ì •ë˜ì–´ AOSP ë§í¬ê°€ í¬í•¨ë¨</li> <li>2016ë…„ 8ì›” 16ì¼: CVE-2016-3856ì´ CVE-2016-2060으로 ìˆ˜ì •ë˜ê³ 참조 URLì´ ì—…ë°ì´íŠ¸ë¨</li> diff --git a/ko/security/bulletin/2016-10-01.html b/ko/security/bulletin/2016-10-01.html index 419be69d..f75f7214 100644 --- a/ko/security/bulletin/2016-10-01.html +++ b/ko/security/bulletin/2016-10-01.html @@ -55,9 +55,9 @@ Android 오픈소스 프로ì 트(AOSP) ì €ìž¥ì†Œì— ë°°í¬ë˜ì—ˆìŠµë‹ˆë‹¤. ì´ ì ‘ìˆ˜ë˜ì§€ 않았습니다. <a href="https://developer.android.com/training/safetynet/index.html">SafetyNet</a>ê³¼ ê°™ì´ Android 플랫í¼ì˜ ë³´ì•ˆì„ ê°œì„ í•˜ëŠ” <a href="/security/enhancements/index.html">Android -보안 í”Œëž«í¼ ë³´í˜¸</a> ë° ì„œë¹„ìŠ¤ 보호 ê¸°ëŠ¥ì— ê´€í•´ ìžì„¸ížˆ ì•Œì•„ë³´ë ¤ë©´ -<a href="#mitigations">Android ë° Google 서비스 완화</a> -ì„¹ì…˜ì„ ì°¸ì¡°í•˜ì„¸ìš”. +보안 í”Œëž«í¼ ë³´í˜¸</a> ë° ì„œë¹„ìŠ¤ 보호 ê¸°ëŠ¥ì— ê´€í•´ +ìžì„¸ížˆ ì•Œì•„ë³´ë ¤ë©´ <a href="#mitigations">Android ë° Google 서비스 완화</a> +ì„¹ì…˜ì„ ì°¸ì¡°í•˜ì„¸ìš” </p> <p> ëª¨ë“ ê³ ê°ì€ 기기ì—ì„œ ì´ ì—…ë°ì´íŠ¸ë¥¼ 수ë½í•˜ëŠ” ê²ƒì´ ì¢‹ìŠµë‹ˆë‹¤. @@ -119,18 +119,18 @@ Android 플랫í¼ì˜ ë³´ì•ˆì„ ê°œì„ í•˜ëŠ” CVE-2016-7117</li> <li>dosomder: CVE-2016-3931</li> <li>Trend Microì˜ Ecular Xu(å¾å¥): CVE-2016-3920</li> - <li>Qihoo 360 - Technology Co. Ltd. IceSword Labì˜ - Gengjia Chen(<a href="https://twitter.com/chengjia4574">@chengjia4574</a>), <a href="http://weibo.com/jfpan">pjf</a>: CVE-2016-6690, CVE-2016-3901, CVE-2016-6672, - CVE-2016-3940, CVE-2016-3935</li> + <li>Qihoo 360 Technology Co. Ltd. IceSword Labì˜ + Gengjia Chen(<a href="https://twitter.com/chengjia4574">@chengjia4574</a>), + <a href="http://weibo.com/jfpan">pjf</a>: CVE-2016-6690, CVE-2016-3901, CVE-2016-6672, CVE-2016-3940, + CVE-2016-3935</li> <li>UC Riversideì˜ <a href="mailto:hzhan033@ucr.edu">Hang Zhang</a>, <a href="mailto:dshe002@ucr.edu">Dongdong She</a>, <a href="mailto:zhiyunq@cs.ucr.edu">Zhiyun Qian</a>: CVE-2015-8950</li> <li>Qihoo 360 Technology Co. Ltd. Alpha íŒ€ì˜ Hao Chen: CVE-2016-3860</li> <li>Google Project Zeroì˜ Jann Horn: CVE-2016-3900, CVE-2016-3885</li> <li><a href="http://keybase.io/jasonrogena">Jason Rogena</a>: CVE-2016-3917</li> - <li>Qihoo 360 IceSword Labì˜ Jianqiang Zhao(<a href="https://twitter.com/jianqiangzhao">@jianqiangzhao</a>), - <a href="http://weibo.com/jfpan">pjf</a>: CVE-2016-6688, + <li>Qihoo 360 IceSword Labì˜ + Jianqiang Zhao(<a href="https://twitter.com/jianqiangzhao">@jianqiangzhao</a>), <a href="http://weibo.com/jfpan">pjf</a>: CVE-2016-6688, CVE-2016-6677, CVE-2016-6673, CVE-2016-6687, CVE-2016-6686, CVE-2016-6681, CVE-2016-6682, CVE-2016-3930</li> <li>Joshua Drake(<a href="https://twitter.com/jduck">@jduck</a>): @@ -139,9 +139,9 @@ Android 플랫í¼ì˜ ë³´ì•ˆì„ ê°œì„ í•˜ëŠ” <li>Google Project Zeroì˜ Mark Brand: CVE-2016-6689</li> <li><a href="https://github.com/michalbednarski">MichaÅ‚ Bednarski</a>: CVE-2016-3914, CVE-2016-6674, CVE-2016-3911, CVE-2016-3912</li> - <li><a href="http://c0reteam.org">C0RE Team</a>ì˜ - Mingjian Zhou(<a href="https://twitter.com/Mingjian_Zhou">@Mingjian_Zhou</a>), - Chiachih Wu (<a href="https://twitter.com/chiachih_wu">@chiachih_wu</a>), Xuxian Jiang: CVE-2016-3933, CVE-2016-3932</li> + <li><a href="http://c0reteam.org">C0RE Team</a>ì˜ Mingjian Zhou(<a href="https://twitter.com/Mingjian_Zhou">@Mingjian_Zhou</a>), + Chiachih Wu (<a href="https://twitter.com/chiachih_wu">@chiachih_wu</a>), Xuxian + Jiang: CVE-2016-3933, CVE-2016-3932</li> <li>Nightwatch Cybersecurity Research (<a href="https://twitter.com/nightwatchcyber">@nightwatchcyber</a>): CVE-2016-5348</li> <li>IBM Security X-Force ì—°êµ¬ì› Roee Hay: CVE-2016-6678</li> @@ -153,19 +153,19 @@ Android 플랫í¼ì˜ ë³´ì•ˆì„ ê°œì„ í•˜ëŠ” Seven Shen(<a href="https://twitter.com/lingtongshen">@lingtongshen</a>): CVE-2016-6685, CVE-2016-6683, CVE-2016-6680, CVE-2016-6679, CVE-2016-3903, CVE-2016-6693, CVE-2016-6694, CVE-2016-6695</li> - <li><a href="http://c0reteam.org">C0RE Team</a>ì˜ - <a href="mailto:vancouverdou@gmail.com">Wenke Dou</a>, Mingjian Zhou + <li><a href="http://c0reteam.org">C0RE Team</a>ì˜ <a href="mailto:vancouverdou@gmail.com">Wenke Dou</a>, Mingjian Zhou (<a href="https://twitter.com/Mingjian_Zhou">@Mingjian_Zhou</a>), Chiachih Wu - (<a href="https://twitter.com/chiachih_wu">@chiachih_wu</a>), Xuxian Jiang: CVE-2016-3909</li> + (<a href="https://twitter.com/chiachih_wu">@chiachih_wu</a>), Xuxian Jiang + : CVE-2016-3909</li> <li>Qihoo 360 Technology Co. Ltd. Alpha íŒ€ì˜ Wenlin Yang, Guang Gong(龚广)(<a href="https://twitter.com/oldfresher">@oldfresher</a>): CVE-2016-3918</li> - <li><a href="http://blog.trendmicro.com/trendlabs-security-intelligence/author/wishwu/">Trend Micro Inc.</a>ì˜ + <li><a href="http://blog.trendmicro.com/trendlabs-security-intelligence/author/wishwu/">Trend + Micro Inc.</a>ì˜ Wish Wu (<a href="http://weibo.com/wishlinux">å´æ½æµ </a>) - (<a href="https://twitter.com/wish_wu">@wish_wu)</a> - : CVE-2016-3924, CVE-2016-3915, CVE-2016-3916, CVE-2016-3910</li> + (<a href="https://twitter.com/wish_wu">@wish_wu)</a>: CVE-2016-3924, CVE-2016-3915, CVE-2016-3916, CVE-2016-3910</li> <li>Huawei, SCC, Eagleye íŒ€ì˜ Yong Shi: CVE-2016-3938</li> <li><a href="http://www.cmcm.com">Cheetah Mobile</a> Security Research Labì˜ - Zhanpeng Zhao(行之)(<a href="https://twitter.com/0xr0ot">@0xr0ot</a>): + Zhanpeng Zhao (行之) (<a href="https://twitter.com/0xr0ot">@0xr0ot</a>): CVE-2016-3908</li> </ul> @@ -861,8 +861,9 @@ MediaTek ë™ì˜ìƒ ë“œë¼ì´ë²„ì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ </tbody></table> <p> * ì´ ë¬¸ì œë¥¼ 해결하기 위한 패치는 공개ë˜ì–´ 있지 않습니다. ì—…ë°ì´íŠ¸ëŠ” -<a href="https://developers.google.com/android/nexus/drivers">Google ê°œë°œìž ì‚¬ì´íŠ¸</a>ì—ì„œ ì œê³µë˜ëŠ” Nexus 기기용 ìµœì‹ ë°”ì´ë„ˆë¦¬ -ë“œë¼ì´ë²„ì— í¬í•¨ë˜ì–´ 있습니다. +<a href="https://developers.google.com/android/nexus/drivers">Google ê°œë°œìž +사ì´íŠ¸</a>ì—ì„œ ì œê³µë˜ëŠ” +Nexus 기기용 ìµœì‹ ë°”ì´ë„ˆë¦¬ ë“œë¼ì´ë²„ì— í¬í•¨ë˜ì–´ 있습니다. </p> <h3 id="eopv-in-kernel-shared-memory-driver">ì»¤ë„ ê³µìœ ë©”ëª¨ë¦¬ ë“œë¼ì´ë²„ì˜ ê¶Œí•œ 승격 취약성</h3> <p> @@ -898,7 +899,9 @@ MediaTek ë™ì˜ìƒ ë“œë¼ì´ë²„ì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ <h3 id="vulnerabilities-in-qc-components"> Qualcomm êµ¬ì„±ìš”ì†Œì˜ ì·¨ì•½ì„±</h3> <p> -아래 í‘œì—는 Qualcomm êµ¬ì„±ìš”ì†Œì— ì˜í–¥ì„ 주는 보안 ì·¨ì•½ì„±ì´ í¬í•¨ë˜ì–´ 있으며 Qualcomm AMSS 2016ë…„ 3ì›” ë° Qualcomm AMSS 2016ë…„ 4ì›” 보안 게시íŒì— ìžì„¸ížˆ 설명ë˜ì–´ 있습니다. +아래 í‘œì—는 Qualcomm êµ¬ì„±ìš”ì†Œì— ì˜í–¥ì„ 주는 보안 ì·¨ì•½ì„±ì´ í¬í•¨ë˜ì–´ 있으며 +Qualcomm AMSS 2016ë…„ 3ì›” ë° Qualcomm AMSS 2016ë…„ 4ì›” 보안 게시íŒì— +ìžì„¸ížˆ 설명ë˜ì–´ 있습니다. </p> <table> <colgroup><col width="19%" /> @@ -937,8 +940,9 @@ Qualcomm êµ¬ì„±ìš”ì†Œì˜ ì·¨ì•½ì„±</h3> </tbody></table> <p> * ì´ ë¬¸ì œë¥¼ 해결하기 위한 패치는 공개ë˜ì–´ 있지 않습니다. ì—…ë°ì´íŠ¸ëŠ” -<a href="https://developers.google.com/android/nexus/drivers">Google ê°œë°œìž ì‚¬ì´íŠ¸</a>ì—ì„œ ì œê³µë˜ëŠ” Nexus 기기용 ìµœì‹ ë°”ì´ë„ˆë¦¬ -ë“œë¼ì´ë²„ì— í¬í•¨ë˜ì–´ 있습니다. +<a href="https://developers.google.com/android/nexus/drivers">Google ê°œë°œìž +사ì´íŠ¸</a>ì—ì„œ ì œê³µë˜ëŠ” +Nexus 기기용 ìµœì‹ ë°”ì´ë„ˆë¦¬ ë“œë¼ì´ë²„ì— í¬í•¨ë˜ì–´ 있습니다. </p> <h3 id="eopv-in-qualcomm-networking-component">Qualcomm ë„¤íŠ¸ì›Œí¬ êµ¬ì„±ìš”ì†Œì˜ ê¶Œí•œ 승격 취약성</h3> <p> @@ -969,7 +973,8 @@ Qualcomm ë„¤íŠ¸ì›Œí¬ êµ¬ì„±ìš”ì†Œì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ <td>2016ë…„ 2ì›” 4ì¼</td> </tr> </tbody></table> -<h3 id="eopv-in-nvidia-mmc-test-driver">NVIDIA MMC 테스트 ë“œë¼ì´ë¸Œì˜ 권한 승격 취약성</h3> +<h3 id="eopv-in-nvidia-mmc-test-driver">NVIDIA MMC 테스트 ë“œë¼ì´ë¸Œì˜ +권한 승격 취약성</h3> <p> NVIDIA MMC 테스트 ë“œë¼ì´ë¸Œì˜ 권한 승격 취약성으로 ì¸í•´ 로컬 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ 커ë„ì˜ ì»¨í…스트 ë‚´ì—ì„œ ìž„ì˜ì˜ 코드를 @@ -1000,8 +1005,9 @@ NVIDIA MMC 테스트 ë“œë¼ì´ë¸Œì˜ 권한 승격 취약성으로 ì¸í•´ </tbody></table> <p> * ì´ ë¬¸ì œë¥¼ 해결하기 위한 패치는 공개ë˜ì–´ 있지 않습니다. ì—…ë°ì´íŠ¸ëŠ” -<a href="https://developers.google.com/android/nexus/drivers">Google ê°œë°œìž ì‚¬ì´íŠ¸</a>ì—ì„œ ì œê³µë˜ëŠ” Nexus 기기용 ìµœì‹ ë°”ì´ë„ˆë¦¬ -ë“œë¼ì´ë²„ì— í¬í•¨ë˜ì–´ 있습니다. +<a href="https://developers.google.com/android/nexus/drivers">Google ê°œë°œìž +사ì´íŠ¸</a>ì—ì„œ ì œê³µë˜ëŠ” +Nexus 기기용 ìµœì‹ ë°”ì´ë„ˆë¦¬ ë“œë¼ì´ë²„ì— í¬í•¨ë˜ì–´ 있습니다. </p> <h3 id="eopv-in-qsee-communicator-driver">Qualcomm QSEE 커뮤니케ì´í„° ë“œë¼ì´ë²„ì˜ ê¶Œí•œ 승격 취약성</h3> <p> @@ -1073,10 +1079,12 @@ Qualcomm QSEE 커뮤니케ì´í„° ë“œë¼ì´ë²„ì˜ ê¶Œí•œ 승격 취약성으로 ì </tbody></table> <p> * ì´ ë¬¸ì œë¥¼ 해결하기 위한 패치는 공개ë˜ì–´ 있지 않습니다. ì—…ë°ì´íŠ¸ëŠ” -<a href="https://developers.google.com/android/nexus/drivers">Google ê°œë°œìž ì‚¬ì´íŠ¸</a>ì—ì„œ ì œê³µë˜ëŠ” Nexus 기기용 ìµœì‹ ë°”ì´ë„ˆë¦¬ -ë“œë¼ì´ë²„ì— í¬í•¨ë˜ì–´ 있습니다. +<a href="https://developers.google.com/android/nexus/drivers">Google ê°œë°œìž +사ì´íŠ¸</a>ì—ì„œ ì œê³µë˜ëŠ” +Nexus 기기용 ìµœì‹ ë°”ì´ë„ˆë¦¬ ë“œë¼ì´ë²„ì— í¬í•¨ë˜ì–´ 있습니다. </p> -<h3 id="eopv-in-qualcomm-camera-driver">Qualcomm ì¹´ë©”ë¼ ë“œë¼ì´ë²„ì˜ ê¶Œí•œ 승격 취약성</h3> +<h3 id="eopv-in-qualcomm-camera-driver">Qualcomm ì¹´ë©”ë¼ ë“œë¼ì´ë²„ì˜ +권한 승격 취약성</h3> <p> Qualcomm ì¹´ë©”ë¼ ë“œë¼ì´ë²„ì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ 로컬 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ ì»¤ë„ ì»¨í…스트 ë‚´ì—ì„œ ìž„ì˜ì˜ 코드를 @@ -1113,7 +1121,8 @@ Qualcomm ì¹´ë©”ë¼ ë“œë¼ì´ë²„ì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ <td>2016ë…„ 7ì›” 12ì¼</td> </tr> </tbody></table> -<h3 id="eopv-in-qualcomm-sound-driver">Qualcomm 사운드 ë“œë¼ì´ë²„ì˜ ê¶Œí•œ 승격 취약성</h3> +<h3 id="eopv-in-qualcomm-sound-driver">Qualcomm +사운드 ë“œë¼ì´ë²„ì˜ ê¶Œí•œ 승격 취약성</h3> <p> Qualcomm 사운드 ë“œë¼ì´ë²„ì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ 로컬 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ ì»¤ë„ ì»¨í…스트 ë‚´ì—ì„œ ìž„ì˜ì˜ 코드를 @@ -1143,7 +1152,8 @@ Qualcomm 사운드 ë“œë¼ì´ë²„ì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ <td>2016ë…„ 6ì›” 20ì¼</td> </tr> </tbody></table> -<h3 id="eopv-in-qualcomm-crypto-engine-driver">Qualcomm 암호화 엔진 ë“œë¼ì´ë²„ì˜ ê¶Œí•œ 승격 취약성</h3> +<h3 id="eopv-in-qualcomm-crypto-engine-driver">Qualcomm +암호화 엔진 ë“œë¼ì´ë²„ì˜ ê¶Œí•œ 승격 취약성</h3> <p> Qualcomm 암호화 엔진 ë“œë¼ì´ë²„ì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ 로컬 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ ì»¤ë„ ì»¨í…스트 ë‚´ì—ì„œ ìž„ì˜ì˜ 코드를 @@ -1220,10 +1230,12 @@ MediaTek ë™ì˜ìƒ ë“œë¼ì´ë²„ì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ </tbody></table> <p> * ì´ ë¬¸ì œë¥¼ 해결하기 위한 패치는 공개ë˜ì–´ 있지 않습니다. ì—…ë°ì´íŠ¸ëŠ” -<a href="https://developers.google.com/android/nexus/drivers">Google ê°œë°œìž ì‚¬ì´íŠ¸</a>ì—ì„œ ì œê³µë˜ëŠ” Nexus 기기용 ìµœì‹ ë°”ì´ë„ˆë¦¬ -ë“œë¼ì´ë²„ì— í¬í•¨ë˜ì–´ 있습니다. +<a href="https://developers.google.com/android/nexus/drivers">Google ê°œë°œìž +사ì´íŠ¸</a>ì—ì„œ ì œê³µë˜ëŠ” +Nexus 기기용 ìµœì‹ ë°”ì´ë„ˆë¦¬ ë“œë¼ì´ë²„ì— í¬í•¨ë˜ì–´ 있습니다. </p> -<h3 id="eopv-in-qualcomm-video-driver">Qualcomm ë™ì˜ìƒ ë“œë¼ì´ë²„ì˜ ê¶Œí•œ 승격 취약성</h3> +<h3 id="eopv-in-qualcomm-video-driver">Qualcomm +ë™ì˜ìƒ ë“œë¼ì´ë²„ì˜ ê¶Œí•œ 승격 취약성</h3> <p> Qualcomm ë™ì˜ìƒ ë“œë¼ì´ë²„ì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ 로컬 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ ì»¤ë„ ì»¨í…스트 ë‚´ì—ì„œ ìž„ì˜ì˜ 코드를 @@ -1298,8 +1310,9 @@ Synaptics 터치스í¬ë¦° ë“œë¼ì´ë²„ì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ </tbody></table> <p> * ì´ ë¬¸ì œë¥¼ 해결하기 위한 패치는 공개ë˜ì–´ 있지 않습니다. ì—…ë°ì´íŠ¸ëŠ” -<a href="https://developers.google.com/android/nexus/drivers">Google ê°œë°œìž ì‚¬ì´íŠ¸</a>ì—ì„œ ì œê³µë˜ëŠ” Nexus 기기용 ìµœì‹ ë°”ì´ë„ˆë¦¬ -ë“œë¼ì´ë²„ì— í¬í•¨ë˜ì–´ 있습니다. +<a href="https://developers.google.com/android/nexus/drivers">Google ê°œë°œìž +사ì´íŠ¸</a>ì—ì„œ ì œê³µë˜ëŠ” +Nexus 기기용 ìµœì‹ ë°”ì´ë„ˆë¦¬ ë“œë¼ì´ë²„ì— í¬í•¨ë˜ì–´ 있습니다. </p> <h3 id="eopv-in-nvidia-camera-driver">NVIDIA ì¹´ë©”ë¼ ë“œë¼ì´ë²„ì˜ ê¶Œí•œ 승격 취약성</h3> @@ -1333,8 +1346,9 @@ NVIDIA ì¹´ë©”ë¼ ë“œë¼ì´ë²„ì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ </tbody></table> <p> * ì´ ë¬¸ì œë¥¼ 해결하기 위한 패치는 공개ë˜ì–´ 있지 않습니다. ì—…ë°ì´íŠ¸ëŠ” -<a href="https://developers.google.com/android/nexus/drivers">Google ê°œë°œìž ì‚¬ì´íŠ¸</a>ì—ì„œ ì œê³µë˜ëŠ” Nexus 기기용 ìµœì‹ ë°”ì´ë„ˆë¦¬ -ë“œë¼ì´ë²„ì— í¬í•¨ë˜ì–´ 있습니다. +<a href="https://developers.google.com/android/nexus/drivers">Google ê°œë°œìž +사ì´íŠ¸</a>ì—ì„œ ì œê³µë˜ëŠ” +Nexus 기기용 ìµœì‹ ë°”ì´ë„ˆë¦¬ ë“œë¼ì´ë²„ì— í¬í•¨ë˜ì–´ 있습니다. </p> <h3 id="eopv-in-system_server">시스템 ì„œë²„ì˜ ê¶Œí•œ 승격 취약성</h3> <p> @@ -1367,8 +1381,9 @@ NVIDIA ì¹´ë©”ë¼ ë“œë¼ì´ë²„ì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ </tbody></table> <p> * ì´ ë¬¸ì œë¥¼ 해결하기 위한 패치는 공개ë˜ì–´ 있지 않습니다. ì—…ë°ì´íŠ¸ëŠ” -<a href="https://developers.google.com/android/nexus/drivers">Google ê°œë°œìž ì‚¬ì´íŠ¸</a>ì—ì„œ ì œê³µë˜ëŠ” Nexus 기기용 ìµœì‹ ë°”ì´ë„ˆë¦¬ -ë“œë¼ì´ë²„ì— í¬í•¨ë˜ì–´ 있습니다. +<a href="https://developers.google.com/android/nexus/drivers">Google ê°œë°œìž +사ì´íŠ¸</a>ì—ì„œ ì œê³µë˜ëŠ” +Nexus 기기용 ìµœì‹ ë°”ì´ë„ˆë¦¬ ë“œë¼ì´ë²„ì— í¬í•¨ë˜ì–´ 있습니다. </p> <h3 id="eopv-in-qualcomm-wi-fi-driver">Qualcomm Wi-Fi ë“œë¼ì´ë²„ì˜ ê¶Œí•œ 승격 취약성</h3> @@ -1454,7 +1469,8 @@ Qualcomm Wi-Fi ë“œë¼ì´ë²„ì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ <td>Google 사내용</td> </tr> </tbody></table> -<h3 id="information-disclosure-vulnerability-in-kernel-ion-subsystem">ì»¤ë„ ION 하위 ì‹œìŠ¤í…œì˜ ì •ë³´ 공개 취약성</h3> +<h3 id="information-disclosure-vulnerability-in-kernel-ion-subsystem">ì»¤ë„ ION +하위 ì‹œìŠ¤í…œì˜ ì •ë³´ 공개 취약성</h3> <p> ì»¤ë„ ION 하위 ì‹œìŠ¤í…œì˜ ì •ë³´ 공개 취약성으로 ì¸í•´ 로컬 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ 권한 ìˆ˜ì¤€ì„ ë²—ì–´ë‚œ ë°ì´í„°ì— ì•¡ì„¸ìŠ¤í• ìˆ˜ 있습니다. @@ -1515,8 +1531,9 @@ NVIDIA GPU ë“œë¼ì´ë²„ì˜ ì •ë³´ 공개 취약성으로 ì¸í•´ 로컬 악성 ì• </tbody></table> <p> * ì´ ë¬¸ì œë¥¼ 해결하기 위한 패치는 공개ë˜ì–´ 있지 않습니다. ì—…ë°ì´íŠ¸ëŠ” -<a href="https://developers.google.com/android/nexus/drivers">Google ê°œë°œìž ì‚¬ì´íŠ¸</a>ì—ì„œ ì œê³µë˜ëŠ” Nexus 기기용 ìµœì‹ ë°”ì´ë„ˆë¦¬ -ë“œë¼ì´ë²„ì— í¬í•¨ë˜ì–´ 있습니다. +<a href="https://developers.google.com/android/nexus/drivers">Google ê°œë°œìž +사ì´íŠ¸</a>ì—ì„œ ì œê³µë˜ëŠ” +Nexus 기기용 ìµœì‹ ë°”ì´ë„ˆë¦¬ ë“œë¼ì´ë²„ì— í¬í•¨ë˜ì–´ 있습니다. </p> <h3 id="eopv-in-qualcomm-character-driver">Qualcomm ìºë¦í„° ë“œë¼ì´ë²„ì˜ ê¶Œí•œ 승격 취약성</h3> @@ -1608,8 +1625,9 @@ Motorola USBNet ë“œë¼ì´ë²„ì˜ ì •ë³´ 공개 취약성으로 ì¸í•´ 로컬 ì•…ì </tbody></table> <p> * ì´ ë¬¸ì œë¥¼ 해결하기 위한 패치는 공개ë˜ì–´ 있지 않습니다. ì—…ë°ì´íŠ¸ëŠ” -<a href="https://developers.google.com/android/nexus/drivers">Google ê°œë°œìž ì‚¬ì´íŠ¸</a>ì—ì„œ ì œê³µë˜ëŠ” Nexus 기기용 ìµœì‹ ë°”ì´ë„ˆë¦¬ -ë“œë¼ì´ë²„ì— í¬í•¨ë˜ì–´ 있습니다. +<a href="https://developers.google.com/android/nexus/drivers">Google ê°œë°œìž +사ì´íŠ¸</a>ì—ì„œ ì œê³µë˜ëŠ” +Nexus 기기용 ìµœì‹ ë°”ì´ë„ˆë¦¬ ë“œë¼ì´ë²„ì— í¬í•¨ë˜ì–´ 있습니다. </p> <h3 id="information-disclosure-vulnerability-in-qualcomm-components">Qualcomm êµ¬ì„±ìš”ì†Œì˜ ì •ë³´ 공개 취약성</h3> @@ -1676,8 +1694,9 @@ Motorola USBNet ë“œë¼ì´ë²„ì˜ ì •ë³´ 공개 취약성으로 ì¸í•´ 로컬 ì•…ì </tbody></table> <p> * ì´ ë¬¸ì œë¥¼ 해결하기 위한 패치는 공개ë˜ì–´ 있지 않습니다. ì—…ë°ì´íŠ¸ëŠ” -<a href="https://developers.google.com/android/nexus/drivers">Google ê°œë°œìž ì‚¬ì´íŠ¸</a>ì—ì„œ ì œê³µë˜ëŠ” Nexus 기기용 ìµœì‹ ë°”ì´ë„ˆë¦¬ -ë“œë¼ì´ë²„ì— í¬í•¨ë˜ì–´ 있습니다. +<a href="https://developers.google.com/android/nexus/drivers">Google ê°œë°œìž +사ì´íŠ¸</a>ì—ì„œ ì œê³µë˜ëŠ” +Nexus 기기용 ìµœì‹ ë°”ì´ë„ˆë¦¬ ë“œë¼ì´ë²„ì— í¬í•¨ë˜ì–´ 있습니다. </p> <h3 id="information-disclosure-vulnerability-in-kernel-components">ì»¤ë„ êµ¬ì„±ìš”ì†Œì˜ ì •ë³´ 공개 취약성</h3> @@ -1731,8 +1750,9 @@ Binder, ë™ê¸°í™”, 블루투스, 사운드 ë“œë¼ì´ë²„를 í¬í•¨í•œ ì»¤ë„ êµ¬ì </tbody></table> <p> * ì´ ë¬¸ì œë¥¼ 해결하기 위한 패치는 공개ë˜ì–´ 있지 않습니다. ì—…ë°ì´íŠ¸ëŠ” -<a href="https://developers.google.com/android/nexus/drivers">Google ê°œë°œìž ì‚¬ì´íŠ¸</a>ì—ì„œ ì œê³µë˜ëŠ” Nexus 기기용 ìµœì‹ ë°”ì´ë„ˆë¦¬ -ë“œë¼ì´ë²„ì— í¬í•¨ë˜ì–´ 있습니다. +<a href="https://developers.google.com/android/nexus/drivers">Google ê°œë°œìž +사ì´íŠ¸</a>ì—ì„œ ì œê³µë˜ëŠ” +Nexus 기기용 ìµœì‹ ë°”ì´ë„ˆë¦¬ ë“œë¼ì´ë²„ì— í¬í•¨ë˜ì–´ 있습니다. </p> <h3 id="information-disclosure-vulnerability-in-nvidia-profiler">NVIDIA 프로파ì¼ëŸ¬ì˜ ì •ë³´ 공개 취약성</h3> @@ -1782,8 +1802,9 @@ NVIDIA 프로파ì¼ëŸ¬ì˜ ì •ë³´ 공개 취약성으로 ì¸í•´ 로컬 악성 ì• </tbody></table> <p> * ì´ ë¬¸ì œë¥¼ 해결하기 위한 패치는 공개ë˜ì–´ 있지 않습니다. ì—…ë°ì´íŠ¸ëŠ” -<a href="https://developers.google.com/android/nexus/drivers">Google ê°œë°œìž ì‚¬ì´íŠ¸</a>ì—ì„œ ì œê³µë˜ëŠ” Nexus 기기용 ìµœì‹ ë°”ì´ë„ˆë¦¬ -ë“œë¼ì´ë²„ì— í¬í•¨ë˜ì–´ 있습니다. +<a href="https://developers.google.com/android/nexus/drivers">Google ê°œë°œìž +사ì´íŠ¸</a>ì—ì„œ ì œê³µë˜ëŠ” +Nexus 기기용 ìµœì‹ ë°”ì´ë„ˆë¦¬ ë“œë¼ì´ë²„ì— í¬í•¨ë˜ì–´ 있습니다. </p> <h3 id="information-disclosure-vulnerability-in-kernel">커ë„ì˜ ì •ë³´ 공개 취약성</h3> @@ -1815,8 +1836,9 @@ NVIDIA 프로파ì¼ëŸ¬ì˜ ì •ë³´ 공개 취약성으로 ì¸í•´ 로컬 악성 ì• </tbody></table> <p> * ì´ ë¬¸ì œë¥¼ 해결하기 위한 패치는 공개ë˜ì–´ 있지 않습니다. ì—…ë°ì´íŠ¸ëŠ” -<a href="https://developers.google.com/android/nexus/drivers">Google ê°œë°œìž ì‚¬ì´íŠ¸</a>ì—ì„œ ì œê³µë˜ëŠ” Nexus 기기용 ìµœì‹ ë°”ì´ë„ˆë¦¬ -ë“œë¼ì´ë²„ì— í¬í•¨ë˜ì–´ 있습니다. +<a href="https://developers.google.com/android/nexus/drivers">Google ê°œë°œìž +사ì´íŠ¸</a>ì—ì„œ ì œê³µë˜ëŠ” +Nexus 기기용 ìµœì‹ ë°”ì´ë„ˆë¦¬ ë“œë¼ì´ë²„ì— í¬í•¨ë˜ì–´ 있습니다. </p> <h3 id="dosv-in-kernel-networking-subsystem">ì»¤ë„ ë„¤íŠ¸ì›Œí¬ í•˜ìœ„ ì‹œìŠ¤í…œì˜ ì„œë¹„ìŠ¤ 거부(DoS) 취약성</h3> @@ -1879,8 +1901,9 @@ TCP ì—°ê²°ì˜ ì•¡ì„¸ìŠ¤ë¥¼ ì°¨ë‹¨í•˜ê³ ì¼ì‹œì ì¸ ì›ê²© 서비스 거부를 </tbody></table> <p> * ì´ ë¬¸ì œë¥¼ 해결하기 위한 패치는 공개ë˜ì–´ 있지 않습니다. ì—…ë°ì´íŠ¸ëŠ” -<a href="https://developers.google.com/android/nexus/drivers">Google ê°œë°œìž ì‚¬ì´íŠ¸</a>ì—ì„œ ì œê³µë˜ëŠ” Nexus 기기용 ìµœì‹ ë°”ì´ë„ˆë¦¬ -ë“œë¼ì´ë²„ì— í¬í•¨ë˜ì–´ 있습니다. +<a href="https://developers.google.com/android/nexus/drivers">Google ê°œë°œìž +사ì´íŠ¸</a>ì—ì„œ ì œê³µë˜ëŠ” +Nexus 기기용 ìµœì‹ ë°”ì´ë„ˆë¦¬ ë“œë¼ì´ë²„ì— í¬í•¨ë˜ì–´ 있습니다. </p> <h3 id="vulnerabilities-in-qualcomm-components">Qualcomm êµ¬ì„±ìš”ì†Œì˜ ì·¨ì•½ì„±</h3> <p> @@ -1958,7 +1981,7 @@ TCP ì—°ê²°ì˜ ì•¡ì„¸ìŠ¤ë¥¼ ì°¨ë‹¨í•˜ê³ ì¼ì‹œì ì¸ ì›ê²© 서비스 거부를 </tbody></table> <h2 id="common-questions-and-answers">ì¼ë°˜ì ì¸ ì§ˆë¬¸ ë° ë‹µë³€</h2> <p> -ì´ ì„¹ì…˜ì—서는 게시íŒì„ ì½ì€ ë’¤ ì œê¸°ë 수 있는 ì¼ë°˜ì ì¸ ì§ˆë¬¸ì— ëŒ€í•œ ë‹µë³€ì„ ì œì‹œí•©ë‹ˆë‹¤. +ì´ ì„¹ì…˜ì—서는 게시íŒì„ ì½ì€ ë’¤ ì œê¸°ë 수 있는 ì¼ë°˜ì ì¸ ì§ˆë¬¸ì˜ ë‹µë³€ì„ ì œì‹œí•©ë‹ˆë‹¤. </p> <p> <strong>1. ë‚´ 기기가 ì—…ë°ì´íŠ¸ë˜ì–´ ì´ ë¬¸ì œê°€ í•´ê²°ë˜ì—ˆëŠ”지 어떻게 ì•Œ 수 있나요? @@ -2010,17 +2033,17 @@ TCP ì—°ê²°ì˜ ì•¡ì„¸ìŠ¤ë¥¼ ì°¨ë‹¨í•˜ê³ ì¼ì‹œì ì¸ ì›ê²© 서비스 거부를 <li><strong>ì¼ë¶€ Nexus 기기</strong>: ë¬¸ì œê°€ ì¼ë¶€ Nexus ê¸°ê¸°ì— ì˜í–¥ì„ 미치는 경우, ì˜í–¥ì„ 받는 Nexus 기기가 <em>ì—…ë°ì´íŠ¸ëœ Nexus 기기</em> ì—´ì— í‘œì‹œë©ë‹ˆë‹¤.</li> - <li><strong>Nexus 기기 해당 ì—†ìŒ</strong>: ë¬¸ì œê°€ Android 7.0 ì´ìƒì„ 실행하는 Nexus ê¸°ê¸°ì— - ì˜í–¥ì„ 미치지 않는 경우, í‘œì˜ <em>ì—…ë°ì´íŠ¸ëœ Nexus 기기</em> ì—´ì— - 'ì—†ìŒ'ì´ë¼ê³ 표시ë©ë‹ˆë‹¤.</li> + <li><strong>Nexus 기기 해당 ì—†ìŒ</strong>: ë¬¸ì œê°€ Android 7.0 ì´ìƒì„ 실행하는 + Nexus ê¸°ê¸°ì— ì˜í–¥ì„ 미치지 않는 경우, í‘œì˜ <em>ì—…ë°ì´íŠ¸ëœ Nexus + 기기</em> ì—´ì— 'ì—†ìŒ'ì´ë¼ê³ 표시ë©ë‹ˆë‹¤.</li> </ul> <p> <strong>4. 참조 ì—´ì˜ í•ëª©ì´ 매핑하는 대ìƒì€ 무엇ì¸ê°€ìš”?</strong> </p> <p> -취약성 ì„¸ë¶€ì •ë³´ í‘œì˜ <em>참조</em> ì—´ì— ìžˆëŠ” í•ëª©ì€ 참조 ê°’ì´ ì†í•œ -ì¡°ì§ì„ 나타내는 ì ‘ë‘어를 í¬í•¨í• 수 있습니다. ì´ëŸ¬í•œ ì ‘ë‘어는 -다ìŒê³¼ ê°™ì´ ë§¤í•‘ë©ë‹ˆë‹¤. +취약성 ì„¸ë¶€ì •ë³´ í‘œì˜ <em>참조</em> ì—´ì— ìžˆëŠ” í•ëª©ì€ +참조 ê°’ì´ ì†í•œ ì¡°ì§ì„ 나타내는 ì ‘ë‘어를 í¬í•¨í• 수 +있습니다. ì´ ì ‘ë‘어는 다ìŒê³¼ ê°™ì´ ë§¤í•‘ë©ë‹ˆë‹¤. </p> <table> <tbody><tr> diff --git a/ko/security/bulletin/2016.html b/ko/security/bulletin/2016.html index 3c44aada..c6377136 100644 --- a/ko/security/bulletin/2016.html +++ b/ko/security/bulletin/2016.html @@ -37,9 +37,9 @@ <tr> <td><a href="2016-12-01.html">2016ë…„ 12ì›”</a></td> <td> - <a href="/security/bulletin/2016-12-01.html?hl=ko">í•œêµì–´</a> / + <a href="/security/bulletin/2016-12-01.html">í•œêµì–´</a> / <a href="/security/bulletin/2016-12-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/2016-12-01.html">English</a> / + <a href="/security/bulletin/2016-12-01.html?hl=ko">English</a> / <a href="/security/bulletin/2016-12-01.html?hl=ru">руÌÑÑкий</a> / <a href="/security/bulletin/2016-12-01.html?hl=zh-cn">ä¸æ–‡Â (ä¸å›½)</a> / <a href="/security/bulletin/2016-12-01.html?hl=zh-tw">ä¸æ–‡Â (å°ç£)</a> @@ -51,9 +51,9 @@ <tr> <td><a href="/security/bulletin/2016-11-01.html">2016ë…„ 11ì›”</a></td> <td> - <a href="/security/bulletin/2016-11-01.html?hl=ko">í•œêµì–´</a> / + <a href="/security/bulletin/2016-11-01.html">í•œêµì–´</a> / <a href="/security/bulletin/2016-11-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/2016-11-01.html">English</a> / + <a href="/security/bulletin/2016-11-01.html?hl=ko">English</a> / <a href="/security/bulletin/2016-11-01.html?hl=ru">руÌÑÑкий</a> / <a href="/security/bulletin/2016-11-01.html?hl=zh-cn">ä¸æ–‡Â (ä¸å›½)</a> / <a href="/security/bulletin/2016-11-01.html?hl=zh-tw">ä¸æ–‡Â (å°ç£)</a> @@ -66,9 +66,9 @@ <tr> <td><a href="/security/bulletin/2016-10-01.html">2016ë…„ 10ì›”</a></td> <td> - <a href="/security/bulletin/2016-10-01.html?hl=ko">í•œêµì–´</a> / + <a href="/security/bulletin/2016-10-01.html">í•œêµì–´</a> / <a href="/security/bulletin/2016-10-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/2016-10-01.html">English</a> / + <a href="/security/bulletin/2016-10-01.html?hl=ko">English</a> / <a href="/security/bulletin/2016-10-01.html?hl=ru">руÌÑÑкий</a> / <a href="/security/bulletin/2016-10-01.html?hl=zh-cn">ä¸æ–‡Â (ä¸å›½)</a> / <a href="/security/bulletin/2016-10-01.html?hl=zh-tw">ä¸æ–‡Â (å°ç£)</a> @@ -80,9 +80,9 @@ <tr> <td><a href="/security/bulletin/2016-09-01.html">2016ë…„ 9ì›”</a></td> <td> - <a href="/security/bulletin/2016-09-01.html?hl=ko">í•œêµì–´</a> / + <a href="/security/bulletin/2016-09-01.html">í•œêµì–´</a> / <a href="/security/bulletin/2016-09-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/2016-09-01.html">English</a> / + <a href="/security/bulletin/2016-09-01.html?hl=ko">English</a> / <a href="/security/bulletin/2016-09-01.html?hl=ru">руÌÑÑкий</a> / <a href="/security/bulletin/2016-09-01.html?hl=zh-cn">ä¸æ–‡Â (ä¸å›½)</a> / <a href="/security/bulletin/2016-09-01.html?hl=zh-tw">ä¸æ–‡Â (å°ç£)</a> @@ -95,9 +95,9 @@ <tr> <td><a href="/security/bulletin/2016-08-01.html">2016ë…„ 8ì›”</a></td> <td> - <a href="/security/bulletin/2016-08-01.html?hl=ko">í•œêµì–´</a> / + <a href="/security/bulletin/2016-08-01.html">í•œêµì–´</a> / <a href="/security/bulletin/2016-08-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/2016-08-01.html">English</a> / + <a href="/security/bulletin/2016-08-01.html?hl=ko">English</a> / <a href="/security/bulletin/2016-08-01.html?hl=ru">руÌÑÑкий</a> / <a href="/security/bulletin/2016-08-01.html?hl=zh-cn">ä¸æ–‡Â (ä¸å›½)</a> / <a href="/security/bulletin/2016-08-01.html?hl=zh-tw">ä¸æ–‡Â (å°ç£)</a> @@ -109,9 +109,9 @@ <tr> <td><a href="/security/bulletin/2016-07-01.html">2016ë…„ 7ì›”</a></td> <td> - <a href="/security/bulletin/2016-07-01.html?hl=ko">í•œêµì–´</a> / + <a href="/security/bulletin/2016-07-01.html">í•œêµì–´</a> / <a href="/security/bulletin/2016-07-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/2016-07-01.html">English</a> / + <a href="/security/bulletin/2016-07-01.html?hl=ko">English</a> / <a href="/security/bulletin/2016-07-01.html?hl=ru">руÌÑÑкий</a> / <a href="/security/bulletin/2016-07-01.html?hl=zh-cn">ä¸æ–‡Â (ä¸å›½)</a> / <a href="/security/bulletin/2016-07-01.html?hl=zh-tw">ä¸æ–‡Â (å°ç£)</a> @@ -123,9 +123,9 @@ <tr> <td><a href="/security/bulletin/2016-06-01.html">2016ë…„ 6ì›”</a></td> <td> - <a href="/security/bulletin/2016-06-01.html?hl=ko">í•œêµì–´</a> / + <a href="/security/bulletin/2016-06-01.html">í•œêµì–´</a> / <a href="/security/bulletin/2016-06-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/2016-06-01.html">English</a> / + <a href="/security/bulletin/2016-06-01.html?hl=ko">English</a> / <a href="/security/bulletin/2016-06-01.html?hl=ru">руÌÑÑкий</a> / <a href="/security/bulletin/2016-06-01.html?hl=zh-cn">ä¸æ–‡Â (ä¸å›½)</a> / <a href="/security/bulletin/2016-06-01.html?hl=zh-tw">ä¸æ–‡Â (å°ç£)</a> @@ -136,9 +136,9 @@ <tr> <td><a href="/security/bulletin/2016-05-01.html">2016ë…„ 5ì›”</a></td> <td> - <a href="/security/bulletin/2016-05-01.html?hl=ko">í•œêµì–´</a> / + <a href="/security/bulletin/2016-05-01.html">í•œêµì–´</a> / <a href="/security/bulletin/2016-05-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/2016-05-01.html">English</a> / + <a href="/security/bulletin/2016-05-01.html?hl=ko">English</a> / <a href="/security/bulletin/2016-05-01.html?hl=ru">руÌÑÑкий</a> / <a href="/security/bulletin/2016-05-01.html?hl=zh-cn">ä¸æ–‡Â (ä¸å›½)</a> / <a href="/security/bulletin/2016-05-01.html?hl=zh-tw">ä¸æ–‡Â (å°ç£)</a> @@ -149,9 +149,9 @@ <tr> <td><a href="/security/bulletin/2016-04-02.html">2016ë…„ 4ì›”</a></td> <td> - <a href="/security/bulletin/2016-04-01.html?hl=ko">í•œêµì–´</a> / + <a href="/security/bulletin/2016-04-02.html">í•œêµì–´</a> / <a href="/security/bulletin/2016-04-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/2016-04-02.html">English</a> / + <a href="/security/bulletin/2016-04-01.html?hl=ko">English</a> / <a href="/security/bulletin/2016-04-01.html?hl=ru">руÌÑÑкий</a> / <a href="/security/bulletin/2016-04-01.html?hl=zh-cn">ä¸æ–‡Â (ä¸å›½)</a> / <a href="/security/bulletin/2016-04-01.html?hl=zh-tw">ä¸æ–‡Â (å°ç£)</a> @@ -162,9 +162,9 @@ <tr> <td><a href="/security/bulletin/2016-03-01.html">2016ë…„ 3ì›”</a></td> <td> - <a href="/security/bulletin/2016-03-01.html?hl=ko">í•œêµì–´</a> / + <a href="/security/bulletin/2016-03-01.html">í•œêµì–´</a> / <a href="/security/bulletin/2016-03-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/2016-03-01.html">English</a> / + <a href="/security/bulletin/2016-03-01.html?hl=ko">English</a> / <a href="/security/bulletin/2016-03-01.html?hl=ru">руÌÑÑкий</a> / <a href="/security/bulletin/2016-03-01.html?hl=zh-cn">ä¸æ–‡Â (ä¸å›½)</a> / <a href="/security/bulletin/2016-03-01.html?hl=zh-tw">ä¸æ–‡Â (å°ç£)</a> @@ -175,9 +175,9 @@ <tr> <td><a href="/security/bulletin/2016-02-01.html">2016ë…„ 2ì›”</a></td> <td> - <a href="/security/bulletin/2016-02-01.html?hl=ko">í•œêµì–´</a> / + <a href="/security/bulletin/2016-02-01.html">í•œêµì–´</a> / <a href="/security/bulletin/2016-02-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/2016-02-01.html">English</a> / + <a href="/security/bulletin/2016-02-01.html?hl=ko">English</a> / <a href="/security/bulletin/2016-02-01.html?hl=ru">руÌÑÑкий</a> / <a href="/security/bulletin/2016-02-01.html?hl=zh-cn">ä¸æ–‡Â (ä¸å›½)</a> / <a href="/security/bulletin/2016-02-01.html?hl=zh-tw">ä¸æ–‡Â (å°ç£)</a> @@ -188,9 +188,9 @@ <tr> <td><a href="/security/bulletin/2016-01-01.html">2016ë…„ 1ì›”</a></td> <td> - <a href="/security/bulletin/2016-01-01.html?hl=ko">í•œêµì–´</a> / + <a href="/security/bulletin/2016-01-01.html">í•œêµì–´</a> / <a href="/security/bulletin/2016-01-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/2016-01-01.html">English</a> / + <a href="/security/bulletin/2016-01-01.html?hl=ko">English</a> / <a href="/security/bulletin/2016-01-01.html?hl=ru">руÌÑÑкий</a> / <a href="/security/bulletin/2016-01-01.html?hl=zh-cn">ä¸æ–‡Â (ä¸å›½)</a> / <a href="/security/bulletin/2016-01-01.html?hl=zh-tw">ä¸æ–‡Â (å°ç£)</a> diff --git a/ko/security/bulletin/2017-01-01.html b/ko/security/bulletin/2017-01-01.html index 73e55bdd..051efdc9 100644 --- a/ko/security/bulletin/2017-01-01.html +++ b/ko/security/bulletin/2017-01-01.html @@ -38,23 +38,24 @@ Google 기기 보안 ì—…ë°ì´íŠ¸ê°€ 출시ë˜ì—ˆìŠµë‹ˆë‹¤. Google 기기 펌웨 <p>ì´ ì¤‘ 가장 심ê°í•œ ë¬¸ì œëŠ” 미디어 파ì¼ì„ ì²˜ë¦¬í• ë•Œ ì´ë©”ì¼, 웹 íƒìƒ‰, MMS 등 여러 ë°©ë²•ì„ í†µí•´ ëŒ€ìƒ ê¸°ê¸°ì—ì„œ -ì›ê²©ìœ¼ë¡œ 코드를 ì‹¤í–‰í• ìˆ˜ 있게 하는 심ê°í•œ 보안 취약성입니다. <a href="/security/overview/updates-resources.html#severity">심ê°ë„ í‰ê°€</a>는 +ì›ê²©ìœ¼ë¡œ 코드를 ì‹¤í–‰í• ìˆ˜ 있게 하는 심ê°í•œ 보안 취약성입니다. <a href="/security/overview/updates-resources.html#severity">심ê°ë„ +í‰ê°€</a>는 개발 목ì 으로 í”Œëž«í¼ ë° ì„œë¹„ìŠ¤ 완화를 ì‚¬ìš©í• ìˆ˜ 없거나 -ìš°íšŒì— ì„±ê³µí•œ 경우 취약성 악용으로 ì¸í•´ ëŒ€ìƒ ê¸°ê¸°ê°€ 받는 ì˜í–¥ì„ -기준으로 ë‚´ë ¤ì§‘ë‹ˆë‹¤.</p> +ìš°íšŒì— ì„±ê³µí•œ 경우 취약성 악용으로 ì¸í•´ ëŒ€ìƒ ê¸°ê¸°ê°€ +받는 ì˜í–¥ì„ 기준으로 ë‚´ë ¤ì§‘ë‹ˆë‹¤.</p> <p>ì‹¤ì œ ê³ ê°ì´ 새로 ë³´ê³ ëœ ì´ëŸ¬í•œ ë¬¸ì œë¡œ ì¸í•´ 악용당했다는 ì‹ ê³ ëŠ” -ì ‘ìˆ˜ë˜ì§€ 않았습니다. <a href="https://developer.android.com/training/safetynet/index.html">SafetyNet</a>ê³¼ ê°™ì´ Android 플랫í¼ì˜ ë³´ì•ˆì„ -ê°œì„ í•˜ëŠ” <a href="/security/enhancements/index.html">Android 보안 í”Œëž«í¼ ë³´í˜¸</a> ë° -서비스 보호 ê¸°ëŠ¥ì— ê´€í•´ ìžì„¸ížˆ ì•Œì•„ë³´ë ¤ë©´ -<a href="#mitigations">Android ë° Google 서비스 완화</a> ì„¹ì…˜ì„ ì°¸ì¡°í•˜ì„¸ìš”.</p> +ì ‘ìˆ˜ë˜ì§€ 않았습니다. <a href="https://developer.android.com/training/safetynet/index.html">SafetyNet</a>ê³¼ ê°™ì´ Android 플랫í¼ì˜ ë³´ì•ˆì„ ê°œì„ í•˜ëŠ” +<a href="/security/enhancements/index.html">Android 보안 í”Œëž«í¼ ë³´í˜¸</a> ë° ì„œë¹„ìŠ¤ 보호 ê¸°ëŠ¥ì— ê´€í•´ ìžì„¸ížˆ ì•Œì•„ë³´ë ¤ë©´ +<a href="#mitigations">Android ë° Google 서비스 +완화</a> ì„¹ì…˜ì„ ì°¸ì¡°í•˜ì„¸ìš”.</p> <p>ëª¨ë“ ê³ ê°ì€ 기기ì—ì„œ ì´ ì—…ë°ì´íŠ¸ë¥¼ 수ë½í•˜ëŠ” ê²ƒì´ ì¢‹ìŠµë‹ˆë‹¤.</p> <h2 id="announcements">공지사í•</h2> <ul> - <li>ì´ ê²Œì‹œíŒì—는 Android 파트너가 ëª¨ë“ Android 기기ì—ì„œ ìœ ì‚¬í•˜ê²Œ ë°œìƒí•˜ëŠ” - 취약성 ë¬¸ì œì˜ ì¼ë¶€ë¥¼ ë”ìš± ë¹ ë¥´ê³ ìœ ì—°í•˜ê²Œ 해결하기 위한 + <li>ì´ ê²Œì‹œíŒì—는 Android 파트너가 ëª¨ë“ Android 기기ì—ì„œ ìœ ì‚¬í•˜ê²Œ + ë°œìƒí•˜ëŠ” 취약성 ë¬¸ì œì˜ ì¼ë¶€ë¥¼ ë”ìš± ë¹ ë¥´ê³ ìœ ì—°í•˜ê²Œ 해결하기 위한 ë‘ ê°€ì§€ 보안 패치 수준 문ìžì—´ì´ í¬í•¨ë˜ì–´ 있습니다. ìžì„¸í•œ ë‚´ìš©ì€ <a href="#common-questions-and-answers">ì¼ë°˜ì ì¸ ì§ˆë¬¸ ë° ë‹µë³€</a>ì„ ì°¸ì¡°í•˜ì„¸ìš”. <ul> @@ -95,11 +96,11 @@ Google 기기 보안 ì—…ë°ì´íŠ¸ê°€ 출시ë˜ì—ˆìŠµë‹ˆë‹¤. Google 기기 펌웨 있으며 Google Play 외부ì—ì„œ ì• í”Œë¦¬ì¼€ì´ì…˜ì„ 설치하는 사용ìžì—게 특히 중요합니다. Google Play ë‚´ì—ì„œ 기기 루팅 ë„구는 금지ë˜ì–´ 있지만 사용ìžê°€ ê°ì§€ëœ 루팅 ì• í”Œë¦¬ì¼€ì´ì…˜ì„ ì„¤ì¹˜í•˜ë ¤ 하면 ì¶œì²˜ì— ìƒê´€ì—†ì´ - 앱 ì¸ì¦ì´ ê²½ê³ ë¥¼ 표시합니다. ë˜í•œ 앱 ì¸ì¦ì€ + 앱 ì¸ì¦ì´ ê²½ê³ ë¥¼ 표시합니다. ë˜í•œ 앱 ì¸ì¦ì—서는 권한 승격 ì·¨ì•½ì„±ì„ ì•…ìš©í•˜ëŠ” 것으로 ì•Œë ¤ì§„ 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì„ ì‹ë³„í•˜ê³ ì°¨ë‹¨í•©ë‹ˆë‹¤. ì´ëŸ¬í•œ ì• í”Œë¦¬ì¼€ì´ì…˜ì´ ì´ë¯¸ ì„¤ì¹˜ëœ ê²½ìš° 앱 ì¸ì¦ì—ì„œ 사용ìžì—게 ì´ë¥¼ ì•Œë¦¬ê³ ê°ì§€ëœ ì• í”Œë¦¬ì¼€ì´ì…˜ì„ ì‚ì œí•˜ë ¤ê³ ì‹œë„합니다.</li> - <li>Google 행아웃과 ë©”ì‹ ì € ì• í”Œë¦¬ì¼€ì´ì…˜ì€ 미디어 서버와 ê°™ì€ í”„ë¡œì„¸ìŠ¤ì— + <li>Google 행아웃과 ë©”ì‹ ì € ì• í”Œë¦¬ì¼€ì´ì…˜ì—서는 미디어 서버와 ê°™ì€ í”„ë¡œì„¸ìŠ¤ì— ë¯¸ë””ì–´ë¥¼ ìžë™ìœ¼ë¡œ ì „ë‹¬í•˜ì§€ 않습니다.</li> </ul> <h2 id="acknowledgements">ê°ì‚¬ì˜ ë§ì”€</h2> @@ -111,7 +112,7 @@ Google 기기 보안 ì—…ë°ì´íŠ¸ê°€ 출시ë˜ì—ˆìŠµë‹ˆë‹¤. Google 기기 펌웨 Daxing Guo(<a href="https://twitter.com/freener0">@freener0</a>): CVE-2017-0386</li> <li><a href="mailto:derrek.haxx@gmail.com">derrek</a>(<a href="https://twitter.com/derrekr6">@derrekr6</a>): CVE-2017-0392</li> <li>Tencent KeenLab(<a href="https://twitter.com/keen_lab">@keen_lab</a>)ì˜ - Di Shen (<a href="https://twitter.com/returnsme">@returnsme</a>): CVE-2016-8412, +Di Shen(<a href="https://twitter.com/returnsme">@returnsme</a>): CVE-2016-8412, CVE-2016-8444, CVE-2016-8427, CVE-2017-0403</li> <li>Shellphish Grill Teamì˜ donfos(Aravind Machiry), UC Santa Barbara: CVE-2016-8448, CVE-2016-8470, CVE-2016-8471, CVE-2016-8472</li> @@ -121,7 +122,7 @@ Google 기기 보안 ì—…ë°ì´íŠ¸ê°€ 출시ë˜ì—ˆìŠµë‹ˆë‹¤. Google 기기 펌웨 <a href="http://weibo.com/jfpan">pjf</a>: CVE-2016-8464</li> <li>Google WebM팀: CVE-2017-0393</li> <li><a href="http://www.360.com">Qihoo 360 Technology Co. Ltd.</a> Alpha Teamì˜ - Guang Gong (龚广)(<a href="http://twitter.com/oldfresher">@oldfresher</a>): +Guang Gong(龚广)(<a href="http://twitter.com/oldfresher">@oldfresher</a>): CVE-2017-0387</li> <li>Qihoo 360 Technology Co. Ltd Alpha Teamì˜ Hao Chen, Guang Gong: CVE-2016-8415, CVE-2016-8454, CVE-2016-8455, CVE-2016-8456, CVE-2016-8457, @@ -140,12 +141,13 @@ Google 기기 보안 ì—…ë°ì´íŠ¸ê°€ 출시ë˜ì—ˆìŠµë‹ˆë‹¤. Google 기기 펌웨 <li>Trend Micro Mobile Threat Research Teamì˜ Seven Shen(<a href="https://twitter.com/lingtongshen">@lingtongshen</a>): CVE-2016-8466</li> <li>Stephen Morrow: CVE-2017-0389</li> - <li><a href="http://www.trendmicro.com">Trend Micro</a> Mobile Threat - Research Teamì˜ V.E.O(<a href="https://twitter.com/vysea">@VYSEa</a>): + <li><a href="http://www.trendmicro.com">Trend Micro</a> Mobile Threat Research Teamì˜ + V.E.O(<a href="https://twitter.com/vysea">@VYSEa</a>): CVE-2017-0381</li> <li>Alibaba Inc.ì˜ Weichao Sun(<a href="https://twitter.com/sunblate">@sunblate</a>): CVE-2017-0391</li> - <li><a href="http://c0reteam.org">C0RE Team</a>ì˜ <a href="mailto:vancouverdou@gmail.com">Wenke Dou</a>, Chiachih Wu(<a href="https://twitter.com/chiachih_wu">@chiachih_wu</a>), Xuxian Jiang: CVE-2017-0402, CVE-2017-0398</li> + <li><a href="http://c0reteam.org">C0RE Team</a>ì˜ <a href="mailto:vancouverdou@gmail.com">Wenke Dou</a>, Chiachih Wu(<a href="https://twitter.com/chiachih_wu">@chiachih_wu</a>), +Xuxian Jiang: CVE-2017-0402, CVE-2017-0398</li> <li><a href="http://c0reteam.org">C0RE Team</a>ì˜ <a href="mailto:vancouverdou@gmail.com">Wenke Dou</a>, <a href="mailto:arnow117@gmail.com">Hanxiang Wen</a>, Chiachih Wu(<a href="https://twitter.com/chiachih_wu">@chiachih_wu</a>), Xuxian Jiang: CVE-2017-0400</li> <li><a href="http://c0reteam.org">C0RE Team</a>ì˜ <a href="mailto:vancouverdou@gmail.com">Wenke Dou</a>, <a href="mailto:hlhan@bupt.edu.cn">Hongli Han</a>, Chiachih Wu(<a href="https://twitter.com/chiachih_wu">@chiachih_wu</a>), Xuxian Jiang: CVE-2017-0384, CVE-2017-0385</li> <li><a href="http://c0reteam.org">C0RE Team</a>ì˜ <a href="mailto:vancouverdou@gmail.com">Wenke Dou</a>, Yuqi Lu(<a href="https://twitter.com/nikos233__">@nikos233</a>), Chiachih Wu(<a href="https://twitter.com/chiachih_wu">@chiachih_wu</a>), Xuxian Jiang: CVE-2017-0401</li> @@ -159,7 +161,7 @@ Google 기기 보안 ì—…ë°ì´íŠ¸ê°€ 출시ë˜ì—ˆìŠµë‹ˆë‹¤. Google 기기 펌웨 <li>Tencent Security Platform Departmentì˜ Yuxiang Li(<a href="https://twitter.com/xbalien29">@Xbalien29</a>): CVE-2017-0395</li> <li><a href="http://www.cmcm.com/">Cheetah Mobile</a> Security Research Labì˜ - Zhanpeng Zhao (行之)(<a href="https://twitter.com/0xr0ot">@0xr0ot</a>): +Zhanpeng Zhao(行之)(<a href="https://twitter.com/0xr0ot">@0xr0ot</a>): CVE-2016-8451</li> </ul> <p>ì´ ê²Œì‹œíŒ ì œìž‘ì— ì°¸ì—¬í•´ ì£¼ì‹ ë‹¤ìŒ ì—°êµ¬ì›ë¶„ë“¤ê»˜ë„ @@ -366,7 +368,7 @@ libnl ë¼ì´ë¸ŒëŸ¬ë¦¬ì˜ 권한 승격 취약성으로 ì¸í•´ 로컬 악성 ì• í <p> 미디어 ì„œë²„ì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ 로컬 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ ê¶Œí•œì´ ì„¤ì •ëœ ì ˆì°¨ì˜ ì»¨í…스트 ë‚´ì—ì„œ ìž„ì˜ì˜ 코드를 ì‹¤í–‰í• ìˆ˜ -있습니다. ì´ ë¬¸ì œëŠ” 보통 타사 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ ì•¡ì„¸ìŠ¤í• ìˆ˜ 없는 ìŠ¹ê²©ëœ +있습니다. ì´ ë¬¸ì œëŠ” 보통 타사 ì• í”Œë¦¬ì¼€ì´ì…˜ì— ì•¡ì„¸ìŠ¤í• ìˆ˜ 없는 ìŠ¹ê²©ëœ ê¶Œí•œìœ¼ë¡œì˜ ë¡œì»¬ 액세스를 부여하는 ë° ì‚¬ìš©ë 수 있으므로 심ê°ë„ 높ìŒìœ¼ë¡œ í‰ê°€ë©ë‹ˆë‹¤. </p> @@ -861,7 +863,7 @@ QC-CR#1000546</a></td> 권한 승격 취약성</h3> <p> NVIDIA GPU ë“œë¼ì´ë²„ì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ -로컬 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ 커ë„ì˜ ì»¨í…스트 ë‚´ì—ì„œ ìž„ì˜ì˜ 코드를 +로컬 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ ì»¤ë„ ì»¨í…스트 ë‚´ì—ì„œ ìž„ì˜ì˜ 코드를 ì‹¤í–‰í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” ì˜êµ¬ì ì¸ ë¡œì»¬ 기기 ì†ìƒì„ ì¼ìœ¼í‚¬ ê°€ëŠ¥ì„±ì´ ìžˆìœ¼ë¯€ë¡œ 심ê°ë„ 심ê°ìœ¼ë¡œ í‰ê°€ë˜ë©°, 기기를 ìˆ˜ë¦¬í•˜ë ¤ë©´ ìš´ì˜ì²´ì œë¥¼ 재설치해야 í• ìˆ˜ë„ ìžˆìŠµë‹ˆë‹¤. @@ -1047,7 +1049,7 @@ QC-CR#1081855</a></td> 권한 승격 취약성</h3> <p> NVIDIA GPU ë“œë¼ì´ë²„ì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ -로컬 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ 커ë„ì˜ ì»¨í…스트 ë‚´ì—ì„œ ìž„ì˜ì˜ 코드를 +로컬 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ ì»¤ë„ ì»¨í…스트 ë‚´ì—ì„œ ìž„ì˜ì˜ 코드를 ì‹¤í–‰í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” ì˜êµ¬ì ì¸ ë¡œì»¬ 기기 ì†ìƒì„ ì¼ìœ¼í‚¬ ê°€ëŠ¥ì„±ì´ ìžˆìœ¼ë¯€ë¡œ 심ê°ë„ 심ê°ìœ¼ë¡œ í‰ê°€ë˜ë©°, 기기를 ìˆ˜ë¦¬í•˜ë ¤ë©´ ìš´ì˜ì²´ì œë¥¼ 재설치해야 í• ìˆ˜ë„ ìžˆìŠµë‹ˆë‹¤. @@ -1342,9 +1344,9 @@ QC-CR#1071891</a></td> 권한 승격 취약성</h3> <p> Qualcomm Wi-Fi ë“œë¼ì´ë²„ì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ -로컬 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ ì»¤ë„ ì»¨í…스트 ë‚´ì—ì„œ ìž„ì˜ì˜ 코드를 ì‹¤í–‰í• ìˆ˜ -있습니다. ì´ ë¬¸ì œëŠ” ë¨¼ì € ê¶Œí•œì´ ì„¤ì •ëœ í”„ë¡œì„¸ìŠ¤ì— ì¹¨íˆ¬í•´ì•¼ë§Œ 실행 -가능하므로 심ê°ë„ 높ìŒìœ¼ë¡œ í‰ê°€ë©ë‹ˆë‹¤. +로컬 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ ì»¤ë„ ì»¨í…스트 ë‚´ì—ì„œ ìž„ì˜ì˜ 코드를 +ì‹¤í–‰í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” ë¨¼ì € ê¶Œí•œì´ ì„¤ì •ëœ í”„ë¡œì„¸ìŠ¤ì— +침투해야만 실행 가능하므로 심ê°ë„ 높ìŒìœ¼ë¡œ í‰ê°€ë©ë‹ˆë‹¤. </p> <table> @@ -1414,7 +1416,7 @@ NVIDIA GPU ë“œë¼ì´ë²„ì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ <p> Qualcomm 사운드 ë“œë¼ì´ë²„ì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ 로컬 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ ì»¤ë„ ì»¨í…스트 ë‚´ì—ì„œ ìž„ì˜ì˜ 코드를 -ì‹¤í–‰í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” ë¨¼ì € ê¶Œí•œì´ ì„¤ì •ëœ ì ˆì°¨ì— ì¹¨íˆ¬í•´ì•¼ë§Œ 실행 +ì‹¤í–‰í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” ë¨¼ì € ê¶Œí•œì´ ì„¤ì •ëœ í”„ë¡œì„¸ìŠ¤ì— ì¹¨íˆ¬í•´ì•¼ë§Œ 실행 가능하므로 심ê°ë„ 높ìŒìœ¼ë¡œ í‰ê°€ë©ë‹ˆë‹¤. </p> @@ -1446,8 +1448,8 @@ QC-CR#880388</a></td> 권한 승격 취약성</h3> <p> Synaptics 터치스í¬ë¦° ë“œë¼ì´ë²„ì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ -로컬 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ 커ë„ì˜ ì»¨í…스트 ë‚´ì—ì„œ ìž„ì˜ì˜ 코드를 -ì‹¤í–‰í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” ë¨¼ì € ê¶Œí•œì´ ì„¤ì •ëœ í”„ë¡œì„¸ìŠ¤ì— ì¹¨íˆ¬í•´ì•¼ë§Œ 실행 +로컬 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ ì»¤ë„ ì»¨í…스트 ë‚´ì—ì„œ ìž„ì˜ì˜ 코드를 +ì‹¤í–‰í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” ë¨¼ì € ê¶Œí•œì´ ì„¤ì •ëœ ì ˆì°¨ì— ì¹¨íˆ¬í•´ì•¼ë§Œ 실행 가능하므로 심ê°ë„ 높ìŒìœ¼ë¡œ í‰ê°€ë©ë‹ˆë‹¤. </p> @@ -1520,7 +1522,7 @@ Synaptics 터치스í¬ë¦° ë“œë¼ì´ë²„ì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ 권한 승격 취약성</h3> <p> ì»¤ë„ ì„±ëŠ¥ 하위 ì‹œìŠ¤í…œì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ 로컬 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ -ì»¤ë„ ì»¨í…스트 ë‚´ì—ì„œ ìž„ì˜ì˜ 코드를 ì‹¤í–‰í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” ë¨¼ì € ê¶Œí•œì´ ì„¤ì •ëœ ì ˆì°¨ì— ì¹¨íˆ¬í•´ì•¼ë§Œ 실행 +ì»¤ë„ ì»¨í…스트 ë‚´ì—ì„œ ìž„ì˜ì˜ 코드를 ì‹¤í–‰í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” ë¨¼ì € ê¶Œí•œì´ ì„¤ì •ëœ í”„ë¡œì„¸ìŠ¤ì— ì¹¨íˆ¬í•´ì•¼ë§Œ 실행 가능하므로 심ê°ë„ 높ìŒìœ¼ë¡œ í‰ê°€ë©ë‹ˆë‹¤. </p> @@ -1558,8 +1560,8 @@ Player, Pixel, Pixel XL</td> <p> ì»¤ë„ ì‚¬ìš´ë“œ 하위 ì‹œìŠ¤í…œì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ 로컬 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ ì»¤ë„ ì»¨í…스트 ë‚´ì—ì„œ ìž„ì˜ì˜ 코드를 -ì‹¤í–‰í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” ë¨¼ì € ê¶Œí•œì´ ì„¤ì •ëœ ì ˆì°¨ì— ì¹¨íˆ¬í•´ì•¼ë§Œ 실행 -가능하므로 심ê°ë„ 높ìŒìœ¼ë¡œ í‰ê°€ë©ë‹ˆë‹¤. +ì‹¤í–‰í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” ë¨¼ì € ê¶Œí•œì´ ì„¤ì •ëœ +í”„ë¡œì„¸ìŠ¤ì— ì¹¨íˆ¬í•´ì•¼ë§Œ 실행 가능하므로 심ê°ë„ 높ìŒìœ¼ë¡œ í‰ê°€ë©ë‹ˆë‹¤. </p> <table> @@ -1595,9 +1597,9 @@ XL</td> 권한 승격 취약성</h3> <p> Qualcomm Wi-Fi ë“œë¼ì´ë²„ì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ -로컬 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ ì»¤ë„ ì»¨í…스트 ë‚´ì—ì„œ ìž„ì˜ì˜ 코드를 ì‹¤í–‰í• ìˆ˜ -있습니다. ì´ ë¬¸ì œëŠ” ë¨¼ì € ê¶Œí•œì´ ì„¤ì •ëœ í”„ë¡œì„¸ìŠ¤ì— ì¹¨íˆ¬í•´ì•¼ë§Œ 실행 -가능하므로 심ê°ë„ 높ìŒìœ¼ë¡œ í‰ê°€ë©ë‹ˆë‹¤. +로컬 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ ì»¤ë„ ì»¨í…스트 ë‚´ì—ì„œ ìž„ì˜ì˜ 코드를 +ì‹¤í–‰í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” ë¨¼ì € ê¶Œí•œì´ ì„¤ì •ëœ í”„ë¡œì„¸ìŠ¤ì— +침투해야만 실행 가능하므로 심ê°ë„ 높ìŒìœ¼ë¡œ í‰ê°€ë©ë‹ˆë‹¤. </p> <table> @@ -1696,7 +1698,7 @@ Player</td> <p> Broadcom Wi-Fi ë“œë¼ì´ë²„ì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ 로컬 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ ì»¤ë„ ì»¨í…스트 ë‚´ì—ì„œ ìž„ì˜ì˜ 코드를 ì‹¤í–‰í• ìˆ˜ -있습니다. ì´ ë¬¸ì œëŠ” ë¨¼ì € ê¶Œí•œì´ ì„¤ì •ëœ ì ˆì°¨ì— ì¹¨íˆ¬í•´ì•¼ë§Œ 실행 +있습니다. ì´ ë¬¸ì œëŠ” ë¨¼ì € ê¶Œí•œì´ ì„¤ì •ëœ í”„ë¡œì„¸ìŠ¤ì— ì¹¨íˆ¬í•´ì•¼ë§Œ 실행 가능하므로 심ê°ë„ 높ìŒìœ¼ë¡œ í‰ê°€ë©ë‹ˆë‹¤. </p> @@ -1766,8 +1768,8 @@ Broadcom Wi-Fi ë“œë¼ì´ë²„ì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ 권한 승격 취약성</h3> <p> Synaptics 터치스í¬ë¦° ë“œë¼ì´ë²„ì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ -로컬 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ 커ë„ì˜ ì»¨í…스트 ë‚´ì—ì„œ ìž„ì˜ì˜ 코드를 -ì‹¤í–‰í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” ë¨¼ì € ê¶Œí•œì´ ì„¤ì •ëœ í”„ë¡œì„¸ìŠ¤ì— ì¹¨íˆ¬í•´ì•¼ë§Œ 실행 +로컬 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ ì»¤ë„ ì»¨í…스트 ë‚´ì—ì„œ ìž„ì˜ì˜ 코드를 +ì‹¤í–‰í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” ë¨¼ì € ê¶Œí•œì´ ì„¤ì •ëœ ì ˆì°¨ì— ì¹¨íˆ¬í•´ì•¼ë§Œ 실행 가능하므로 심ê°ë„ 높ìŒìœ¼ë¡œ í‰ê°€ë©ë‹ˆë‹¤. </p> @@ -1958,8 +1960,8 @@ QC-CR#586855</a></td> 권한 승격 취약성</h3> <p> Broadcom Wi-Fi ë“œë¼ì´ë²„ì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ -로컬 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ ì»¤ë„ ì»¨í…스트 ë‚´ì—ì„œ ìž„ì˜ì˜ 코드를 ì‹¤í–‰í• ìˆ˜ -있습니다. ì´ ë¬¸ì œëŠ” ë¨¼ì € ê¶Œí•œì´ ì„¤ì •ëœ ì ˆì°¨ì— ì¹¨íˆ¬í•´ì•¼ë§Œ +로컬 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ ì»¤ë„ ì»¨í…스트 ë‚´ì—ì„œ ìž„ì˜ì˜ 코드를 +ì‹¤í–‰í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” ë¨¼ì € ê¶Œí•œì´ ì„¤ì •ëœ ì ˆì°¨ì— ì¹¨íˆ¬í•´ì•¼ë§Œ 실행 가능하며 현재 í”Œëž«í¼ êµ¬ì„±ìœ¼ë¡œ ì™„í™”í• ìˆ˜ 있으므로 심ê°ë„ 보통으로 í‰ê°€ë©ë‹ˆë‹¤. </p> @@ -2324,7 +2326,7 @@ HTC ì¸í’‹ ë“œë¼ì´ë²„ì˜ ì •ë³´ 공개 취약성으로 ì¸í•´ 로컬 악성 ì• </tbody></table> <h2 id="common-questions-and-answers">ì¼ë°˜ì ì¸ ì§ˆë¬¸ ë° ë‹µë³€</h2> -<p>ì´ ì„¹ì…˜ì—서는 게시íŒì„ ì½ì€ ë’¤ ì œê¸°ë 수 있는 ì¼ë°˜ì ì¸ ì§ˆë¬¸ì— ëŒ€í•œ ë‹µë³€ì„ ì œì‹œí•©ë‹ˆë‹¤.</p> +<p>ì´ ì„¹ì…˜ì—서는 게시íŒì„ ì½ì€ ë’¤ ì œê¸°ë 수 있는 ì¼ë°˜ì ì¸ ì§ˆë¬¸ì˜ ë‹µë³€ì„ ì œì‹œí•©ë‹ˆë‹¤.</p> <p><strong>1. ë‚´ 기기가 ì—…ë°ì´íŠ¸ë˜ì–´ ì´ ë¬¸ì œê°€ í•´ê²°ë˜ì—ˆëŠ”지 어떻게 ì•Œ 수 있나요? </strong></p> @@ -2347,7 +2349,8 @@ HTC ì¸í’‹ ë“œë¼ì´ë²„ì˜ ì •ë³´ 공개 취약성으로 ì¸í•´ 로컬 악성 ì• <p><strong>2. ì´ ê²Œì‹œíŒì— ë‘ ê°€ì§€ 보안 패치 ìˆ˜ì¤€ì´ ìžˆëŠ” ì´ìœ ê°€ 무엇ì¸ê°€ìš”?</strong></p> <p>ì´ ê²Œì‹œíŒì—는 Android 파트너가 ëª¨ë“ Android 기기ì—ì„œ ìœ ì‚¬í•˜ê²Œ ë°œìƒí•˜ëŠ” -취약성 ë¬¸ì œì˜ ì¼ë¶€ë¥¼ ë”ìš± ë¹ ë¥´ê³ ìœ ì—°í•˜ê²Œ 해결하ë„ë¡ í•˜ê¸° 위해 ë‘ ê°€ì§€ 보안 패치 ìˆ˜ì¤€ì´ í¬í•¨ë˜ì–´ 있습니다. Android 파트너는 ì´ ê²Œì‹œíŒì— ì–¸ê¸‰ëœ ë¬¸ì œë¥¼ ëª¨ë‘ ìˆ˜ì •í•˜ê³ +취약성 ë¬¸ì œì˜ ì¼ë¶€ë¥¼ ë”ìš± ë¹ ë¥´ê³ ìœ ì—°í•˜ê²Œ 해결하기 위한 +ë‘ ê°€ì§€ 보안 패치 ìˆ˜ì¤€ì´ í¬í•¨ë˜ì–´ 있습니다. Android 파트너는 ì´ ê²Œì‹œíŒì— ì–¸ê¸‰ëœ ë¬¸ì œë¥¼ ëª¨ë‘ ìˆ˜ì •í•˜ê³ ìµœì‹ ë³´ì•ˆ 패치 ìˆ˜ì¤€ì„ ì‚¬ìš©í•˜ëŠ” ê²ƒì´ ì¢‹ìŠµë‹ˆë‹¤.</p> <ul> <li>2017ë…„ 1ì›” 1ì¼ ë³´ì•ˆ 패치 ìˆ˜ì¤€ì„ ì‚¬ìš©í•˜ëŠ” 기기는 ì´ ë³´ì•ˆ 패치 수준과 @@ -2369,9 +2372,9 @@ HTC ì¸í’‹ ë“œë¼ì´ë²„ì˜ ì •ë³´ 공개 취약성으로 ì¸í•´ 로컬 악성 ì• <ul> <li><strong>ëª¨ë“ Google 기기</strong>: ë¬¸ì œê°€ ëª¨ë“ Google 기기 ë° Pixel ê¸°ê¸°ì— ì˜í–¥ì„ 미치는 경우, í‘œì˜ <em>ì—…ë°ì´íŠ¸ëœ Google 기기</em> ì—´ì— - '모ë‘'ë¼ê³ 표시ë©ë‹ˆë‹¤. '모ë‘'ì—는 다ìŒê³¼ ê°™ì€ <a href="https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices">지ì›ë˜ëŠ” 기기</a>ê°€ í¬í•¨ë©ë‹ˆë‹¤. - Nexus 5X, Nexus 6, Nexus 6P, Nexus 9, Android One, Nexus Player, - Pixel C, Pixel, Pixel XL.</li> + '모ë‘'ë¼ê³ 표시ë©ë‹ˆë‹¤. '모ë‘'ì—는 다ìŒê³¼ ê°™ì€ <a href="https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices">지ì›ë˜ëŠ” + 기기</a>ê°€ í¬í•¨ë©ë‹ˆë‹¤. Nexus 5X, Nexus 6, Nexus 6P, Nexus 9, Android One, + Nexus Player, Pixel C, Pixel, Pixel XL</li> <li><strong>ì¼ë¶€ Google 기기</strong>: ë¬¸ì œê°€ ì¼ë¶€ Google ê¸°ê¸°ì— ì˜í–¥ì„ 미치는 경우, ì˜í–¥ì„ 받는 Google 기기가 <em>ì—…ë°ì´íŠ¸ëœ Google 기기</em> ì—´ì— í‘œì‹œë©ë‹ˆë‹¤.</li> @@ -2381,9 +2384,9 @@ HTC ì¸í’‹ ë“œë¼ì´ë²„ì˜ ì •ë³´ 공개 취약성으로 ì¸í•´ 로컬 악성 ì• </ul> <p><strong>4. 참조 ì—´ì˜ í•ëª©ì´ 매핑하는 대ìƒì€ 무엇ì¸ê°€ìš”?</strong></p> -<p>취약성 ì„¸ë¶€ì •ë³´ í‘œì˜ <em>참조</em> ì—´ì— ìžˆëŠ” í•ëª©ì€ 참조 ê°’ì´ ì†í•œ -ì¡°ì§ì„ 나타내는 ì ‘ë‘어를 í¬í•¨í• 수 있습니다. ì´ëŸ¬í•œ ì ‘ë‘어는 -다ìŒê³¼ ê°™ì´ ë§¤í•‘ë©ë‹ˆë‹¤.</p> +<p>취약성 ì„¸ë¶€ì •ë³´ í‘œì˜ <em>참조</em> ì—´ì— ìžˆëŠ” í•ëª©ì€ +참조 ê°’ì´ ì†í•œ ì¡°ì§ì„ 나타내는 ì ‘ë‘어를 í¬í•¨í• 수 +있습니다. ì´ ì ‘ë‘어는 다ìŒê³¼ ê°™ì´ ë§¤í•‘ë©ë‹ˆë‹¤.</p> <table> <tbody><tr> diff --git a/ko/security/bulletin/2017-03-01.html b/ko/security/bulletin/2017-03-01.html index 5ccfa027..a1a5ec63 100644 --- a/ko/security/bulletin/2017-03-01.html +++ b/ko/security/bulletin/2017-03-01.html @@ -40,9 +40,9 @@ Android 오픈소스 프로ì 트(AOSP) ì €ìž¥ì†Œì— ë°°í¬ë˜ì—ˆìœ¼ë©° ì´ ê²Œì 받는 ì˜í–¥ì„ 기준으로 ë‚´ë ¤ì§‘ë‹ˆë‹¤.</p> <p>ì‹¤ì œ ê³ ê°ì´ 새로 ë³´ê³ ëœ ì´ëŸ¬í•œ ë¬¸ì œë¡œ ì¸í•´ 악용당했다는 ì‹ ê³ ëŠ” ì ‘ìˆ˜ë˜ì§€ 않았습니다. <a href="https://developer.android.com/training/safetynet/index.html">SafetyNet</a>ê³¼ ê°™ì´ -Android 플랫í¼ì˜ ë³´ì•ˆì„ ê°œì„ í•˜ëŠ” <a href="/security/enhancements/index.html">Android -보안 í”Œëž«í¼ ë³´í˜¸</a> ë° ì„œë¹„ìŠ¤ 보호 ê¸°ëŠ¥ì— ê´€í•´ ìžì„¸ížˆ ì•Œì•„ë³´ë ¤ë©´ -<a href="#mitigations">Android ë° Google 서비스 완화</a> ì„¹ì…˜ì„ ì°¸ì¡°í•˜ì„¸ìš”.</p> +Android 플랫í¼ì˜ ë³´ì•ˆì„ ê°œì„ í•˜ëŠ” <a href="/security/enhancements/index.html">Android 보안 í”Œëž«í¼ ë³´í˜¸</a> +ë° ì„œë¹„ìŠ¤ 보호 ê¸°ëŠ¥ì— ê´€í•´ ìžì„¸ížˆ ì•Œì•„ë³´ë ¤ë©´ <a href="#mitigations"> +Android ë° Google 서비스 완화</a> ì„¹ì…˜ì„ ì°¸ì¡°í•˜ì„¸ìš”.</p> <p>ëª¨ë“ ê³ ê°ì€ 기기ì—ì„œ ì´ ì—…ë°ì´íŠ¸ë¥¼ 수ë½í•˜ëŠ” ê²ƒì´ ì¢‹ìŠµë‹ˆë‹¤.</p> <h2 id="announcements">공지사í•</h2> <ul> @@ -72,9 +72,9 @@ Android 플랫í¼ì˜ ë³´ì•ˆì„ ê°œì„ í•˜ëŠ” <a href="/security/enhancements/inde <li>Android í”Œëž«í¼ ìµœì‹ ë²„ì „ì˜ í–¥ìƒëœ 기능으로 Androidì˜ ì—¬ëŸ¬ ë¬¸ì œë¥¼ 악용하기가 ë”ìš± ì–´ë ¤ì›Œì¡ŒìŠµë‹ˆë‹¤. 가능하다면 ëª¨ë“ ì‚¬ìš©ìžëŠ” ìµœì‹ ë²„ì „ì˜ Androidë¡œ ì—…ë°ì´íŠ¸í•˜ëŠ” ê²ƒì´ ì¢‹ìŠµë‹ˆë‹¤.</li> -<li>Android 보안팀ì—서는 <a href="http://static.googleusercontent.com/media/source.android.com/en//security/reports/Google_Android_Security_PHA_classifications.pdf">ìœ í•´í• ìˆ˜ 있는 ì• í”Œë¦¬ì¼€ì´ì…˜</a>ì— ê´€í•´ -사용ìžì—게 ê²½ê³ ë¥¼ 보내는 <a href="http://static.googleusercontent.com/media/source.android.com/en//security/reports/Google_Android_Security_2015_Report_Final.pdf">앱 ì¸ì¦ ë° SafetyNet</a>ì„ ì‚¬ìš©í•˜ì—¬ -악용사례를 ì ê·¹ì 으로 모니터ë§í•©ë‹ˆë‹¤. 앱 ì¸ì¦ì€ <a href="http://www.android.com/gms">Google ëª¨ë°”ì¼ ì„œë¹„ìŠ¤</a>ê°€ ì ìš©ëœ ê¸°ê¸°ì— ê¸°ë³¸ì 으로 사용 ì„¤ì •ë˜ì–´ 있으며 Google Play 외부ì—ì„œ +<li>Android 보안팀ì—서는 <a href="http://static.googleusercontent.com/media/source.android.com/en//security/reports/Google_Android_Security_PHA_classifications.pdf">ìœ í•´í• ìˆ˜ 있는 ì• í”Œë¦¬ì¼€ì´ì…˜</a>ì— ê´€í•´ 사용ìžì—게 +ê²½ê³ ë¥¼ 보내는 <a href="http://static.googleusercontent.com/media/source.android.com/en//security/reports/Google_Android_Security_2015_Report_Final.pdf">앱 ì¸ì¦ ë° SafetyNet</a>ì„ ì‚¬ìš©í•˜ì—¬ 악용사례를 ì ê·¹ì 으로 +모니터ë§í•©ë‹ˆë‹¤. 앱 ì¸ì¦ì€ <a href="http://www.android.com/gms">Google ëª¨ë°”ì¼ ì„œë¹„ìŠ¤</a>ê°€ ì ìš©ëœ ê¸°ê¸°ì— ê¸°ë³¸ì 으로 사용 ì„¤ì •ë˜ì–´ 있으며 Google Play 외부ì—ì„œ ì• í”Œë¦¬ì¼€ì´ì…˜ì„ 설치하는 사용ìžì—게 특히 중요합니다. Google Play ë‚´ì—ì„œ 기기 루팅 ë„구는 금지ë˜ì–´ 있지만 사용ìžê°€ ê°ì§€ëœ 루팅 ì• í”Œë¦¬ì¼€ì´ì…˜ì„ ì„¤ì¹˜í•˜ë ¤ 하면 ì¶œì²˜ì— ìƒê´€ì—†ì´ @@ -99,10 +99,10 @@ CVE-2017-0460 CVE-2016-8477, CVE-2017-0531 </li><li><a href="mailto:derrek.haxx@gmail.com">derrek</a>(<a href="https://twitter.com/derrekr6">@derrekr6</a>), <a href="mailto:sbauer@plzdonthack.me">Scott Bauer</a>(<a href="https://twitter.com/ScottyBauer1">@ScottyBauer1</a>): CVE-2017-0521 </li><li>Tencent KeenLab(<a href="https://twitter.com/keen_lab">@keen_lab</a>)ì˜ -Di Shen(<a href="https://twitter.com/returnsme">@returnsme</a>): CVE-2017-0334, +Di Shen (<a href="https://twitter.com/returnsme">@returnsme</a>): CVE-2017-0334, CVE-2017-0456, CVE-2017-0457, CVE-2017-0525 -</li><li><a href="http://www.ms509.com">MS509Team</a>ì˜ En He(<a href="https://twitter.com/heeeeen4x">@heeeeen4x</a>), -Bo Liu: CVE-2017-0490 +</li><li><a href="http://www.ms509.com">MS509Team</a>ì˜ +En He(<a href="https://twitter.com/heeeeen4x">@heeeeen4x</a>), Bo Liu: CVE-2017-0490 </li><li>Qihoo 360 Technology Co. Ltd. IceSword Labì˜ Gengjia Chen(<a href="https://twitter.com/chengjia4574">@chengjia4574</a>), <a href="http://weibo.com/jfpan">pjf</a>: CVE-2017-0500, CVE-2017-0501, CVE-2017-0502, CVE-2017-0503, @@ -145,7 +145,7 @@ Seven Shen(<a href="https://twitter.com/lingtongshen">@lingtongshen</a>): CVE-20 </li><li>Googleì˜ Svetoslav Ganov: CVE-2017-0492 </li><li><a href="http://c0reteam.org">C0RE Team</a>ì˜ <a href="mailto:segfault5514@gmail.com">Tong Lin</a>, <a href="mailto:computernik@gmail.com">Yuan-Tsung Lo</a>, Xuxian Jiang: CVE-2017-0333 </li><li><a href="http://www.trendmicro.com">Trend Micro</a> <a href="http://blog.trendmicro.com/trendlabs-security-intelligence/category/mobile">Mobile Threat Response Team</a>ì˜ -V.E.O(<a href="https://twitter.com/vysea">@VYSEa</a>): +V.E.O (<a href="https://twitter.com/vysea">@VYSEa</a>): CVE-2017-0466, CVE-2017-0467, CVE-2017-0468, CVE-2017-0469, CVE-2017-0470, CVE-2017-0471, CVE-2017-0472, CVE-2017-0473, CVE-2017-0482, CVE-2017-0484, CVE-2017-0485, CVE-2017-0486, CVE-2017-0487, CVE-2017-0494, CVE-2017-0495 @@ -153,10 +153,10 @@ CVE-2017-0485, CVE-2017-0486, CVE-2017-0487, CVE-2017-0494, CVE-2017-0495 Wish Wu(å´æ½æµ æ¤å½¼)(<a href="https://twitter.com/wish_wu">@wish_wu</a>): CVE-2017-0477 </li><li>Qihoo 360 Technology Co. Ltd. Vulpecker Teamì˜ Yu Pan: CVE-2017-0517, CVE-2017-0532 -</li><li><a href="http://c0reteam.org">C0RE Team</a>ì˜ <a href="mailto:computernik@gmail.com">Yuan-Tsung Lo</a>, -Xuxian Jiang: CVE-2017-0526, CVE-2017-0527 -</li><li><a href="http://c0reteam.org">C0RE Team</a>ì˜ Yuqi Lu(<a href="https://twitter.com/nikos233__">@nikos233</a>), <a href="mailto:vancouverdou@gmail.com">Wenke Dou</a>, <a href="mailto:shaodacheng2016@gmail.com">Dacheng Shao</a>, Mingjian Zhou(<a href="https://twitter.com/Mingjian_Zhou">@Mingjian_Zhou</a>), Xuxian -Jiang: CVE-2017-0483</li> +</li><li><a href="http://c0reteam.org">C0RE Team</a>ì˜ +<a href="mailto:computernik@gmail.com">Yuan-Tsung Lo</a>, Xuxian Jiang: CVE-2017-0526, CVE-2017-0527 +</li><li><a href="http://c0reteam.org">C0RE Team</a>ì˜ Yuqi Lu(<a href="https://twitter.com/nikos233__">@nikos233</a>), <a href="mailto:vancouverdou@gmail.com">Wenke Dou</a>, <a href="mailto:shaodacheng2016@gmail.com">Dacheng Shao</a>, Mingjian Zhou(<a href="https://twitter.com/Mingjian_Zhou">@Mingjian_Zhou</a>), Xuxian Jiang +: CVE-2017-0483</li> <li>Qihoo 360 Technology Co. Ltd. Chengdu Security Response Centerì˜ Zinuo Han(<a href="https://weibo.com/ele7enxxh">weibo.com/ele7enxxh</a>): CVE-2017-0475, CVE-2017-0497 @@ -482,11 +482,11 @@ CVE-2017-0475, CVE-2017-0497 <h3 id="eop-in-audioserver">오디오 ì„œë²„ì˜ ê¶Œí•œ 승격 취약성</h3> -<p>오디오 ì„œë²„ì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ 로컬 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ -ê¶Œí•œì´ ì„¤ì •ëœ í”„ë¡œì„¸ìŠ¤ì˜ ì»¨í…스트 ë‚´ì—ì„œ ìž„ì˜ì˜ 코드를 ì‹¤í–‰í• ìˆ˜ -있습니다. ì´ ë¬¸ì œëŠ” 보통 타사 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ ì•¡ì„¸ìŠ¤í• ìˆ˜ 없는 ìŠ¹ê²©ëœ -ê¶Œí•œìœ¼ë¡œì˜ ë¡œì»¬ 액세스 ê¶Œí•œì„ í™•ë³´í•˜ëŠ” ë° ì‚¬ìš©ë 수 있으므로 심ê°ë„ 높ìŒìœ¼ë¡œ -í‰ê°€ë©ë‹ˆë‹¤.</p> +<p>오디오 ì„œë²„ì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ 로컬 악성 +ì• í”Œë¦¬ì¼€ì´ì…˜ì´ ê¶Œí•œì´ ì„¤ì •ëœ ì ˆì°¨ì˜ ì»¨í…스트 ë‚´ì—ì„œ ìž„ì˜ì˜ +코드를 ì‹¤í–‰í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” 보통 타사 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ +ì•¡ì„¸ìŠ¤í• ìˆ˜ 없는 ìŠ¹ê²©ëœ ê¶Œí•œìœ¼ë¡œì˜ ë¡œì»¬ 액세스 ê¶Œí•œì„ í™•ë³´í•˜ëŠ” ë° +사용ë 수 있으므로 심ê°ë„ 높ìŒìœ¼ë¡œ í‰ê°€ë©ë‹ˆë‹¤.</p> <table> <colgroup><col width="18%" /> @@ -852,11 +852,11 @@ CVE-2017-0475, CVE-2017-0497 <td>2016ë…„ 9ì›” 14ì¼</td> </tr> </tbody></table> -<p>* ì´ ë¬¸ì œë¥¼ 해결하기 위한 패치는 공개ë˜ì§€ 않습니다. ì—…ë°ì´íŠ¸ëŠ” +<p>* ì´ ë¬¸ì œë¥¼ 해결하기 위한 패치는 공개ë˜ì–´ 있지 않습니다. ì—…ë°ì´íŠ¸ëŠ” <a href="https://developers.google.com/android/nexus/drivers">Google ê°œë°œìž ì‚¬ì´íŠ¸</a>ì—ì„œ ì œê³µë˜ëŠ” Google 기기용 ìµœì‹ ë°”ì´ë„ˆë¦¬ ë“œë¼ì´ë²„ì— í¬í•¨ë˜ì–´ 있습니다.</p> -<p>** 지ì›ë˜ëŠ” Android 7.0 ì´ìƒ Google ê¸°ê¸°ì— ì œê³µëœ ì—…ë°ì´íŠ¸ê°€ ëª¨ë‘ -설치ë˜ì—ˆë‹¤ë©´ ì´ëŸ¬í•œ ì·¨ì•½ì„±ì˜ ì˜í–¥ì„ 받지 않습니다</p> +<p>** 지ì›ë˜ëŠ” Android 7.0 ì´ìƒ Google ê¸°ê¸°ì— ì œê³µëœ ì—…ë°ì´íŠ¸ê°€ ëª¨ë‘ ì„¤ì¹˜ë˜ì—ˆë‹¤ë©´ ì´ëŸ¬í•œ +ì·¨ì•½ì„±ì˜ ì˜í–¥ì„ 받지 않습니다.</p> <h3 id="dos-in-mediaserver-2">미디어 ì„œë²„ì˜ ì„œë¹„ìŠ¤ 거부(DoS) 취약성</h3> @@ -960,9 +960,8 @@ Google ê³„ì • 로그ì¸ì„ 요구하ë„ë¡ ì„¤ì •í• ìˆ˜ 있습니다. ì´ ë¬¸ì <p>ë‹¤ìŒ ì„¹ì…˜ì—서는 2017-03-05 패치 ìˆ˜ì¤€ì— ì ìš©ë˜ëŠ” ê° ë³´ì•ˆ ì·¨ì•½ì„±ì— ê´€í•´ ìžì„¸ížˆ 알아볼 수 있습니다. 여기ì—는 ë¬¸ì œ 설명, 심ê°ë„ 근거 ë° CVE, ê´€ë ¨ 참조, 심ê°ë„, ì—…ë°ì´íŠ¸ëœ Google 기기, ì—…ë°ì´íŠ¸ëœ -AOSP ë²„ì „(해당하는 경우), ì‹ ê³ ëœ ë‚ ì§œê°€ í¬í•¨ëœ 표가 ì œì‹œë©ë‹ˆë‹¤. 가능한 경우 -AOSP ë³€ê²½ì‚¬í• ëª©ë¡ê³¼ ê°™ì´ ë¬¸ì œë¥¼ í•´ê²°í•œ 공개 변경사í•ì„ 버그 IDì— -연결합니다. í•˜ë‚˜ì˜ ë²„ê·¸ì™€ ê´€ë ¨ëœ ë³€ê²½ì‚¬í•ì´ 여러 ê°œì¸ ê²½ìš° 추가 +AOSP ë²„ì „(해당하는 경우), ì‹ ê³ ëœ ë‚ ì§œê°€ í¬í•¨ëœ 표가 ì œì‹œë©ë‹ˆë‹¤. 가능한 경우 AOSP ë³€ê²½ì‚¬í• ëª©ë¡ê³¼ ê°™ì´ ë¬¸ì œë¥¼ í•´ê²°í•œ +공개 변경사í•ì„ 버그 IDì— ì—°ê²°í•©ë‹ˆë‹¤. í•˜ë‚˜ì˜ ë²„ê·¸ì™€ ê´€ë ¨ëœ ë³€ê²½ì‚¬í•ì´ 여러 ê°œì¸ ê²½ìš° 추가 참조가 버그 ID 다ìŒì— 오는 ë²ˆí˜¸ì— ì—°ê²°ë˜ì–´ 있습니다.</p> <h3 id="eop-in-mediatek-components">MediaTek êµ¬ì„±ìš”ì†Œì˜ ê¶Œí•œ 승격 @@ -1044,7 +1043,7 @@ AOSP ë³€ê²½ì‚¬í• ëª©ë¡ê³¼ ê°™ì´ ë¬¸ì œë¥¼ í•´ê²°í•œ 공개 변경사í•ì„ ë² <td>2016ë…„ 10ì›” 18ì¼</td> </tr> </tbody></table> -<p>* ì´ ë¬¸ì œë¥¼ 해결하기 위한 패치는 공개ë˜ì§€ 않습니다. ì—…ë°ì´íŠ¸ëŠ” +<p>* ì´ ë¬¸ì œë¥¼ 해결하기 위한 패치는 공개ë˜ì–´ 있지 않습니다. ì—…ë°ì´íŠ¸ëŠ” <a href="https://developers.google.com/android/nexus/drivers">Google ê°œë°œìž ì‚¬ì´íŠ¸</a>ì—ì„œ ì œê³µë˜ëŠ” Nexus 기기용 ìµœì‹ ë°”ì´ë„ˆë¦¬ ë“œë¼ì´ë²„ì— í¬í•¨ë˜ì–´ 있습니다.</p> @@ -1054,7 +1053,7 @@ AOSP ë³€ê²½ì‚¬í• ëª©ë¡ê³¼ ê°™ì´ ë¬¸ì œë¥¼ í•´ê²°í•œ 공개 변경사í•ì„ ë² <h3 id="eop-in-nvidia-gpu-driver">NVIDIA GPU ë“œë¼ì´ë²„ì˜ ê¶Œí•œ 승격 취약성</h3> <p>NVIDIA GPU ë“œë¼ì´ë²„ì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ -로컬 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ 커ë„ì˜ ì»¨í…스트 ë‚´ì—ì„œ ìž„ì˜ì˜ 코드를 +로컬 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ ì»¤ë„ ì»¨í…스트 ë‚´ì—ì„œ ìž„ì˜ì˜ 코드를 ì‹¤í–‰í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” ì˜êµ¬ì ì¸ ë¡œì»¬ 기기 ì†ìƒì„ ì¼ìœ¼í‚¬ ê°€ëŠ¥ì„±ì´ ìžˆìœ¼ë¯€ë¡œ 심ê°ë„ 심ê°ìœ¼ë¡œ í‰ê°€ë˜ë©°, 기기를 ìˆ˜ë¦¬í•˜ë ¤ë©´ ìš´ì˜ì²´ì œë¥¼ 재설치해야 í• ìˆ˜ë„ ìžˆìŠµë‹ˆë‹¤.</p> @@ -1113,7 +1112,7 @@ AOSP ë³€ê²½ì‚¬í• ëª©ë¡ê³¼ ê°™ì´ ë¬¸ì œë¥¼ í•´ê²°í•œ 공개 변경사í•ì„ ë² <td>Google 사내용</td> </tr> </tbody></table> -<p>* ì´ ë¬¸ì œë¥¼ 해결하기 위한 패치는 공개ë˜ì§€ 않습니다. ì—…ë°ì´íŠ¸ëŠ” +<p>* ì´ ë¬¸ì œë¥¼ 해결하기 위한 패치는 공개ë˜ì–´ 있지 않습니다. ì—…ë°ì´íŠ¸ëŠ” <a href="https://developers.google.com/android/nexus/drivers">Google ê°œë°œìž ì‚¬ì´íŠ¸</a>ì—ì„œ ì œê³µë˜ëŠ” Nexus 기기용 ìµœì‹ ë°”ì´ë„ˆë¦¬ ë“œë¼ì´ë²„ì— í¬í•¨ë˜ì–´ 있습니다.</p> @@ -1155,7 +1154,7 @@ C, Pixel, Pixel XL</td> <td>2016ë…„ 12ì›” 28ì¼</td> </tr> </tbody></table> -<p>* ì´ ë¬¸ì œë¥¼ 해결하기 위한 패치는 공개ë˜ì§€ 않습니다. ì—…ë°ì´íŠ¸ëŠ” +<p>* ì´ ë¬¸ì œë¥¼ 해결하기 위한 패치는 공개ë˜ì–´ 있지 않습니다. ì—…ë°ì´íŠ¸ëŠ” <a href="https://developers.google.com/android/nexus/drivers">Google ê°œë°œìž ì‚¬ì´íŠ¸</a>ì—ì„œ ì œê³µë˜ëŠ” Nexus 기기용 ìµœì‹ ë°”ì´ë„ˆë¦¬ ë“œë¼ì´ë²„ì— í¬í•¨ë˜ì–´ 있습니다.</p> @@ -1190,12 +1189,12 @@ C, Pixel, Pixel XL</td> <td>2016ë…„ 10ì›” 12ì¼</td> </tr> </tbody></table> -<p>* ì´ ë¬¸ì œë¥¼ 해결하기 위한 패치는 공개ë˜ì§€ 않습니다. ì—…ë°ì´íŠ¸ëŠ” +<p>* ì´ ë¬¸ì œë¥¼ 해결하기 위한 패치는 공개ë˜ì–´ 있지 않습니다. ì—…ë°ì´íŠ¸ëŠ” <a href="https://developers.google.com/android/nexus/drivers">Google ê°œë°œìž ì‚¬ì´íŠ¸</a>ì—ì„œ ì œê³µë˜ëŠ” Nexus 기기용 ìµœì‹ ë°”ì´ë„ˆë¦¬ ë“œë¼ì´ë²„ì— í¬í•¨ë˜ì–´ 있습니다.</p> -<p>** 지ì›ë˜ëŠ” Android 7.0 ì´ìƒ Google ê¸°ê¸°ì— ì œê³µëœ ì—…ë°ì´íŠ¸ê°€ ëª¨ë‘ -설치ë˜ì—ˆë‹¤ë©´ ì´ëŸ¬í•œ ì·¨ì•½ì„±ì˜ ì˜í–¥ì„ 받지 않습니다</p> +<p>** 지ì›ë˜ëŠ” Android 7.0 ì´ìƒ Google ê¸°ê¸°ì— ì œê³µëœ ì—…ë°ì´íŠ¸ê°€ ëª¨ë‘ ì„¤ì¹˜ë˜ì—ˆë‹¤ë©´ ì´ëŸ¬í•œ +ì·¨ì•½ì„±ì˜ ì˜í–¥ì„ 받지 않습니다.</p> <h3 id="eop-in-kernel-fiq-debugger">ì»¤ë„ FIQ ë””ë²„ê±°ì˜ ê¶Œí•œ 승격 취약성</h3> @@ -1226,7 +1225,7 @@ C, Pixel, Pixel XL</td> <td>2016ë…„ 10ì›” 25ì¼</td> </tr> </tbody></table> -<p>* ì´ ë¬¸ì œë¥¼ 해결하기 위한 패치는 공개ë˜ì§€ 않습니다. ì—…ë°ì´íŠ¸ëŠ” +<p>* ì´ ë¬¸ì œë¥¼ 해결하기 위한 패치는 공개ë˜ì–´ 있지 않습니다. ì—…ë°ì´íŠ¸ëŠ” <a href="https://developers.google.com/android/nexus/drivers">Google ê°œë°œìž ì‚¬ì´íŠ¸</a>ì—ì„œ ì œê³µë˜ëŠ” Nexus 기기용 ìµœì‹ ë°”ì´ë„ˆë¦¬ ë“œë¼ì´ë²„ì— í¬í•¨ë˜ì–´ 있습니다.</p> @@ -1261,7 +1260,7 @@ C, Pixel, Pixel XL</td> <td>2016ë…„ 9ì›” 29ì¼</td> </tr> </tbody></table> -<p>* ì´ ë¬¸ì œë¥¼ 해결하기 위한 패치는 공개ë˜ì§€ 않습니다. ì—…ë°ì´íŠ¸ëŠ” +<p>* ì´ ë¬¸ì œë¥¼ 해결하기 위한 패치는 공개ë˜ì–´ 있지 않습니다. ì—…ë°ì´íŠ¸ëŠ” <a href="https://developers.google.com/android/nexus/drivers">Google ê°œë°œìž ì‚¬ì´íŠ¸</a>ì—ì„œ ì œê³µë˜ëŠ” Nexus 기기용 ìµœì‹ ë°”ì´ë„ˆë¦¬ ë“œë¼ì´ë²„ì— í¬í•¨ë˜ì–´ 있습니다.</p> @@ -1362,7 +1361,7 @@ AMSS 2016ë…„ 9ì›” 보안 게시íŒì— ìžì„¸ížˆ 설명ë˜ì–´ 있습니다.</p> </tr> </tbody></table> <p>* ì´ ì·¨ì•½ì„±ì˜ ì‹¬ê°ë„ ë“±ê¸‰ì€ ê³µê¸‰ì—…ì²´ì—ì„œ ê²°ì •í•œ 것입니다.</p> -<p>* ì´ ë¬¸ì œë¥¼ 해결하기 위한 패치는 공개ë˜ì§€ 않습니다. ì—…ë°ì´íŠ¸ëŠ” +<p>* ì´ ë¬¸ì œë¥¼ 해결하기 위한 패치는 공개ë˜ì–´ 있지 않습니다. ì—…ë°ì´íŠ¸ëŠ” <a href="https://developers.google.com/android/nexus/drivers">Google ê°œë°œìž ì‚¬ì´íŠ¸</a>ì—ì„œ ì œê³µë˜ëŠ” Nexus 기기용 ìµœì‹ ë°”ì´ë„ˆë¦¬ ë“œë¼ì´ë²„ì— í¬í•¨ë˜ì–´ 있습니다.</p> @@ -1373,8 +1372,8 @@ AMSS 2016ë…„ 9ì›” 보안 게시íŒì— ìžì„¸ížˆ 설명ë˜ì–´ 있습니다.</p> 하위 ì‹œìŠ¤í…œì˜ ê¶Œí•œ 승격 취약성</h3> <p>ì»¤ë„ ë„¤íŠ¸ì›Œí¬ í•˜ìœ„ ì‹œìŠ¤í…œì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ 로컬 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ ì»¤ë„ ì»¨í…스트 ë‚´ì—ì„œ ìž„ì˜ì˜ 코드를 -ì‹¤í–‰í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” ë¨¼ì € ê¶Œí•œì´ ì„¤ì •ëœ í”„ë¡œì„¸ìŠ¤ì— -침투해야만 실행 가능하므로 심ê°ë„ 높ìŒìœ¼ë¡œ í‰ê°€ë©ë‹ˆë‹¤.</p> +ì‹¤í–‰í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” ë¨¼ì € ê¶Œí•œì´ ì„¤ì •ëœ í”„ë¡œì„¸ìŠ¤ì— ì¹¨íˆ¬í•´ì•¼ë§Œ 실행 +가능하므로 심ê°ë„ 높ìŒìœ¼ë¡œ í‰ê°€ë©ë‹ˆë‹¤.</p> <table> <colgroup><col width="19%" /> @@ -1440,7 +1439,7 @@ C, Pixel, Pixel XL</td> <td>2016ë…„ 10ì›” 21ì¼</td> </tr> </tbody></table> -<p>* ì´ ë¬¸ì œë¥¼ 해결하기 위한 패치는 공개ë˜ì§€ 않습니다. ì—…ë°ì´íŠ¸ëŠ” +<p>* ì´ ë¬¸ì œë¥¼ 해결하기 위한 패치는 공개ë˜ì–´ 있지 않습니다. ì—…ë°ì´íŠ¸ëŠ” <a href="https://developers.google.com/android/nexus/drivers">Google ê°œë°œìž ì‚¬ì´íŠ¸</a>ì—ì„œ ì œê³µë˜ëŠ” Nexus 기기용 ìµœì‹ ë°”ì´ë„ˆë¦¬ ë“œë¼ì´ë²„ì— í¬í•¨ë˜ì–´ 있습니다.</p> @@ -1474,7 +1473,7 @@ C, Pixel, Pixel XL</td> <td>2016ë…„ 10ì›” 22ì¼</td> </tr> </tbody></table> -<p>* ì´ ë¬¸ì œë¥¼ 해결하기 위한 패치는 공개ë˜ì§€ 않습니다. ì—…ë°ì´íŠ¸ëŠ” +<p>* ì´ ë¬¸ì œë¥¼ 해결하기 위한 패치는 공개ë˜ì–´ 있지 않습니다. ì—…ë°ì´íŠ¸ëŠ” <a href="https://developers.google.com/android/nexus/drivers">Google ê°œë°œìž ì‚¬ì´íŠ¸</a>ì—ì„œ ì œê³µë˜ëŠ” Nexus 기기용 ìµœì‹ ë°”ì´ë„ˆë¦¬ ë“œë¼ì´ë²„ì— í¬í•¨ë˜ì–´ 있습니다.</p> @@ -1485,8 +1484,8 @@ C, Pixel, Pixel XL</td> 권한 승격 취약성</h3> <p>Qualcomm ADSPRPC ë“œë¼ì´ë²„ì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ 로컬 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ ì»¤ë„ ì»¨í…스트 ë‚´ì—ì„œ ìž„ì˜ì˜ 코드를 -ì‹¤í–‰í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” ë¨¼ì € ê¶Œí•œì´ ì„¤ì •ëœ í”„ë¡œì„¸ìŠ¤ì— -침투해야만 실행 가능하므로 심ê°ë„ 높ìŒìœ¼ë¡œ í‰ê°€ë©ë‹ˆë‹¤.</p> +ì‹¤í–‰í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” ë¨¼ì € ê¶Œí•œì´ ì„¤ì •ëœ í”„ë¡œì„¸ìŠ¤ì— ì¹¨íˆ¬í•´ì•¼ë§Œ 실행 +가능하므로 심ê°ë„ 높ìŒìœ¼ë¡œ í‰ê°€ë©ë‹ˆë‹¤.</p> <table> <colgroup><col width="19%" /> @@ -1511,7 +1510,7 @@ C, Pixel, Pixel XL</td> <td>2016ë…„ 9ì›” 22ì¼</td> </tr> </tbody></table> -<p>* ì´ ë¬¸ì œë¥¼ 해결하기 위한 패치는 공개ë˜ì§€ 않습니다. ì—…ë°ì´íŠ¸ëŠ” +<p>* ì´ ë¬¸ì œë¥¼ 해결하기 위한 패치는 공개ë˜ì–´ 있지 않습니다. ì—…ë°ì´íŠ¸ëŠ” <a href="https://developers.google.com/android/nexus/drivers">Google ê°œë°œìž ì‚¬ì´íŠ¸</a>ì—ì„œ ì œê³µë˜ëŠ” Nexus 기기용 ìµœì‹ ë°”ì´ë„ˆë¦¬ ë“œë¼ì´ë²„ì— í¬í•¨ë˜ì–´ 있습니다.</p> @@ -1553,7 +1552,7 @@ C, Pixel, Pixel XL</td> <td>2016ë…„ 10ì›” 24ì¼</td> </tr> </tbody></table> -<p>* ì´ ë¬¸ì œë¥¼ 해결하기 위한 패치는 공개ë˜ì§€ 않습니다. ì—…ë°ì´íŠ¸ëŠ” +<p>* ì´ ë¬¸ì œë¥¼ 해결하기 위한 패치는 공개ë˜ì–´ 있지 않습니다. ì—…ë°ì´íŠ¸ëŠ” <a href="https://developers.google.com/android/nexus/drivers">Google ê°œë°œìž ì‚¬ì´íŠ¸</a>ì—ì„œ ì œê³µë˜ëŠ” Nexus 기기용 ìµœì‹ ë°”ì´ë„ˆë¦¬ ë“œë¼ì´ë²„ì— í¬í•¨ë˜ì–´ 있습니다.</p> @@ -1562,8 +1561,8 @@ C, Pixel, Pixel XL</td> 엔진 ë“œë¼ì´ë²„ì˜ ê¶Œí•œ 승격 취약성</h3> <p>Qualcomm 암호화 엔진 ë“œë¼ì´ë²„ì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ 로컬 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ ì»¤ë„ ì»¨í…스트 ë‚´ì—ì„œ ìž„ì˜ì˜ 코드를 -ì‹¤í–‰í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” ë¨¼ì € ê¶Œí•œì´ ì„¤ì •ëœ í”„ë¡œì„¸ìŠ¤ì— -침투해야만 실행 가능하므로 심ê°ë„ 높ìŒìœ¼ë¡œ í‰ê°€ë©ë‹ˆë‹¤.</p> +ì‹¤í–‰í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” ë¨¼ì € ê¶Œí•œì´ ì„¤ì •ëœ í”„ë¡œì„¸ìŠ¤ì— ì¹¨íˆ¬í•´ì•¼ë§Œ 실행 +가능하므로 심ê°ë„ 높ìŒìœ¼ë¡œ í‰ê°€ë©ë‹ˆë‹¤.</p> <table> <colgroup><col width="19%" /> @@ -1658,7 +1657,7 @@ QC-CR#1097709</a></td> <td>2016ë…„ 11ì›” 15ì¼</td> </tr> </tbody></table> -<p>* ì´ ë¬¸ì œë¥¼ 해결하기 위한 패치는 공개ë˜ì§€ 않습니다. ì—…ë°ì´íŠ¸ëŠ” +<p>* ì´ ë¬¸ì œë¥¼ 해결하기 위한 패치는 공개ë˜ì–´ 있지 않습니다. ì—…ë°ì´íŠ¸ëŠ” <a href="https://developers.google.com/android/nexus/drivers">Google ê°œë°œìž ì‚¬ì´íŠ¸</a>ì—ì„œ ì œê³µë˜ëŠ” Nexus 기기용 ìµœì‹ ë°”ì´ë„ˆë¦¬ ë“œë¼ì´ë²„ì— í¬í•¨ë˜ì–´ 있습니다.</p> @@ -1669,8 +1668,8 @@ QC-CR#1097709</a></td> 권한 승격 취약성</h3> <p>Qualcomm Wi-Fi ë“œë¼ì´ë²„ì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ 로컬 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ ì»¤ë„ ì»¨í…스트 ë‚´ì—ì„œ ìž„ì˜ì˜ 코드를 -ì‹¤í–‰í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” ë¨¼ì € ê¶Œí•œì´ ì„¤ì •ëœ í”„ë¡œì„¸ìŠ¤ì— -침투해야만 실행 가능하므로 심ê°ë„ 높ìŒìœ¼ë¡œ í‰ê°€ë©ë‹ˆë‹¤.</p> +ì‹¤í–‰í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” ë¨¼ì € ê¶Œí•œì´ ì„¤ì •ëœ í”„ë¡œì„¸ìŠ¤ì— ì¹¨íˆ¬í•´ì•¼ë§Œ 실행 +가능하므로 심ê°ë„ 높ìŒìœ¼ë¡œ í‰ê°€ë©ë‹ˆë‹¤.</p> <table> <colgroup><col width="19%" /> @@ -1719,7 +1718,7 @@ QC-CR#1096945</a></td> <h3 id="eop-in-synaptics-touchscreen-driver">Synaptics 터치스í¬ë¦° ë“œë¼ì´ë²„ì˜ ê¶Œí•œ 승격 취약성</h3> <p>Synaptics 터치스í¬ë¦° ë“œë¼ì´ë²„ì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ -로컬 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ 커ë„ì˜ ì»¨í…스트 ë‚´ì—ì„œ ìž„ì˜ì˜ 코드를 +로컬 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ ì»¤ë„ ì»¨í…스트 ë‚´ì—ì„œ ìž„ì˜ì˜ 코드를 ì‹¤í–‰í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” ë¨¼ì € ê¶Œí•œì´ ì„¤ì •ëœ í”„ë¡œì„¸ìŠ¤ì— ì¹¨íˆ¬í•´ì•¼ë§Œ 실행 가능하므로 심ê°ë„ 높ìŒìœ¼ë¡œ í‰ê°€ë©ë‹ˆë‹¤.</p> @@ -1744,7 +1743,7 @@ QC-CR#1096945</a></td> <td>2016ë…„ 11ì›” 18ì¼</td> </tr> </tbody></table> -<p>* ì´ ë¬¸ì œë¥¼ 해결하기 위한 패치는 공개ë˜ì§€ 않습니다. ì—…ë°ì´íŠ¸ëŠ” +<p>* ì´ ë¬¸ì œë¥¼ 해결하기 위한 패치는 공개ë˜ì–´ 있지 않습니다. ì—…ë°ì´íŠ¸ëŠ” <a href="https://developers.google.com/android/nexus/drivers">Google ê°œë°œìž ì‚¬ì´íŠ¸</a>ì—ì„œ ì œê³µë˜ëŠ” Nexus 기기용 ìµœì‹ ë°”ì´ë„ˆë¦¬ ë“œë¼ì´ë²„ì— í¬í•¨ë˜ì–´ 있습니다.</p> @@ -1786,7 +1785,7 @@ QC-CR#1096945</a></td> <td>2016ë…„ 11ì›” 25ì¼</td> </tr> </tbody></table> -<p>* ì´ ë¬¸ì œë¥¼ 해결하기 위한 패치는 공개ë˜ì§€ 않습니다. ì—…ë°ì´íŠ¸ëŠ” +<p>* ì´ ë¬¸ì œë¥¼ 해결하기 위한 패치는 공개ë˜ì–´ 있지 않습니다. ì—…ë°ì´íŠ¸ëŠ” <a href="https://developers.google.com/android/nexus/drivers">Google ê°œë°œìž ì‚¬ì´íŠ¸</a>ì—ì„œ ì œê³µë˜ëŠ” Nexus 기기용 ìµœì‹ ë°”ì´ë„ˆë¦¬ ë“œë¼ì´ë²„ì— í¬í•¨ë˜ì–´ 있습니다.</p> @@ -1795,8 +1794,8 @@ QC-CR#1096945</a></td> 권한 승격 취약성</h3> <p>HTC 센서 허브 ë“œë¼ì´ë²„ì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ 로컬 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ 커ë„ì˜ ì»¨í…스트 ë‚´ì—ì„œ ìž„ì˜ì˜ 코드를 -ì‹¤í–‰í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” ë¨¼ì € ê¶Œí•œì´ ì„¤ì •ëœ í”„ë¡œì„¸ìŠ¤ì— -침투해야만 실행 가능하므로 심ê°ë„ 높ìŒìœ¼ë¡œ í‰ê°€ë©ë‹ˆë‹¤.</p> +ì‹¤í–‰í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” ë¨¼ì € ê¶Œí•œì´ ì„¤ì •ëœ í”„ë¡œì„¸ìŠ¤ì— ì¹¨íˆ¬í•´ì•¼ë§Œ 실행 +가능하므로 심ê°ë„ 높ìŒìœ¼ë¡œ í‰ê°€ë©ë‹ˆë‹¤.</p> <table> <colgroup><col width="19%" /> @@ -1826,7 +1825,7 @@ QC-CR#1096945</a></td> <td>2016ë…„ 12ì›” 25ì¼</td> </tr> </tbody></table> -<p>* ì´ ë¬¸ì œë¥¼ 해결하기 위한 패치는 공개ë˜ì§€ 않습니다. ì—…ë°ì´íŠ¸ëŠ” +<p>* ì´ ë¬¸ì œë¥¼ 해결하기 위한 패치는 공개ë˜ì–´ 있지 않습니다. ì—…ë°ì´íŠ¸ëŠ” <a href="https://developers.google.com/android/nexus/drivers">Google ê°œë°œìž ì‚¬ì´íŠ¸</a>ì—ì„œ ì œê³µë˜ëŠ” Nexus 기기용 ìµœì‹ ë°”ì´ë„ˆë¦¬ ë“œë¼ì´ë²„ì— í¬í•¨ë˜ì–´ 있습니다.</p> @@ -1834,7 +1833,7 @@ QC-CR#1096945</a></td> <h3 id="eop-in-nvidia-gpu-driver-2">NVIDIA GPU ë“œë¼ì´ë²„ì˜ ê¶Œí•œ 승격 취약성</h3> <p>NVIDIA GPU ë“œë¼ì´ë²„ì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ -로컬 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ 커ë„ì˜ ì»¨í…스트 ë‚´ì—ì„œ ìž„ì˜ì˜ 코드를 +로컬 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ ì»¤ë„ ì»¨í…스트 ë‚´ì—ì„œ ìž„ì˜ì˜ 코드를 ì‹¤í–‰í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” ì˜êµ¬ì ì¸ ë¡œì»¬ 기기 ì†ìƒì„ ì¼ìœ¼í‚¬ ê°€ëŠ¥ì„±ì´ ìžˆìœ¼ë¯€ë¡œ 심ê°ë„ 심ê°ìœ¼ë¡œ í‰ê°€ë˜ë©°, 기기를 ìˆ˜ë¦¬í•˜ë ¤ë©´ ìš´ì˜ì²´ì œë¥¼ 재설치해야 í• ìˆ˜ë„ ìžˆìŠµë‹ˆë‹¤.</p> @@ -1861,7 +1860,7 @@ QC-CR#1096945</a></td> <td>2016ë…„ 11ì›” 28ì¼</td> </tr> </tbody></table> -<p>* ì´ ë¬¸ì œë¥¼ 해결하기 위한 패치는 공개ë˜ì§€ 않습니다. ì—…ë°ì´íŠ¸ëŠ” +<p>* ì´ ë¬¸ì œë¥¼ 해결하기 위한 패치는 공개ë˜ì–´ 있지 않습니다. ì—…ë°ì´íŠ¸ëŠ” <a href="https://developers.google.com/android/nexus/drivers">Google ê°œë°œìž ì‚¬ì´íŠ¸</a>ì—ì„œ ì œê³µë˜ëŠ” Nexus 기기용 ìµœì‹ ë°”ì´ë„ˆë¦¬ ë“œë¼ì´ë²„ì— í¬í•¨ë˜ì–´ 있습니다.</p> @@ -1906,7 +1905,7 @@ QC-CR#1101792</a></td> <td>Google 사내용</td> </tr> </tbody></table> -<p>* ì´ ë¬¸ì œë¥¼ 해결하기 위한 패치는 공개ë˜ì§€ 않습니다. ì—…ë°ì´íŠ¸ëŠ” +<p>* ì´ ë¬¸ì œë¥¼ 해결하기 위한 패치는 공개ë˜ì–´ 있지 않습니다. ì—…ë°ì´íŠ¸ëŠ” <a href="https://developers.google.com/android/nexus/drivers">Google ê°œë°œìž ì‚¬ì´íŠ¸</a>ì—ì„œ ì œê³µë˜ëŠ” Nexus 기기용 ìµœì‹ ë°”ì´ë„ˆë¦¬ ë“œë¼ì´ë²„ì— í¬í•¨ë˜ì–´ 있습니다.</p> @@ -1939,7 +1938,7 @@ QC-CR#1101792</a></td> <td>2016ë…„ 12ì›” 4ì¼</td> </tr> </tbody></table> -<p>* ì´ ë¬¸ì œë¥¼ 해결하기 위한 패치는 공개ë˜ì§€ 않습니다. ì—…ë°ì´íŠ¸ëŠ” +<p>* ì´ ë¬¸ì œë¥¼ 해결하기 위한 패치는 공개ë˜ì–´ 있지 않습니다. ì—…ë°ì´íŠ¸ëŠ” <a href="https://developers.google.com/android/nexus/drivers">Google ê°œë°œìž ì‚¬ì´íŠ¸</a>ì—ì„œ ì œê³µë˜ëŠ” Nexus 기기용 ìµœì‹ ë°”ì´ë„ˆë¦¬ ë“œë¼ì´ë²„ì— í¬í•¨ë˜ì–´ 있습니다.</p> @@ -2046,7 +2045,7 @@ QC-CR#1094140</a></td> <td>2016ë…„ 4ì›” 27ì¼</td> </tr> </tbody></table> -<p>* ì´ ë¬¸ì œë¥¼ 해결하기 위한 패치는 공개ë˜ì§€ 않습니다. ì—…ë°ì´íŠ¸ëŠ” +<p>* ì´ ë¬¸ì œë¥¼ 해결하기 위한 패치는 공개ë˜ì–´ 있지 않습니다. ì—…ë°ì´íŠ¸ëŠ” <a href="https://developers.google.com/android/nexus/drivers">Google ê°œë°œìž ì‚¬ì´íŠ¸</a>ì—ì„œ ì œê³µë˜ëŠ” Nexus 기기용 ìµœì‹ ë°”ì´ë„ˆë¦¬ ë“œë¼ì´ë²„ì— í¬í•¨ë˜ì–´ 있습니다.</p> @@ -2153,7 +2152,7 @@ QC-CR#1035099</a></td> <td>Google 사내용</td> </tr> </tbody></table> -<p>* ì´ ë¬¸ì œë¥¼ 해결하기 위한 패치는 공개ë˜ì§€ 않습니다. ì—…ë°ì´íŠ¸ëŠ” +<p>* ì´ ë¬¸ì œë¥¼ 해결하기 위한 패치는 공개ë˜ì–´ 있지 않습니다. ì—…ë°ì´íŠ¸ëŠ” <a href="https://developers.google.com/android/nexus/drivers">Google ê°œë°œìž ì‚¬ì´íŠ¸</a>ì—ì„œ ì œê³µë˜ëŠ” Nexus 기기용 ìµœì‹ ë°”ì´ë„ˆë¦¬ ë“œë¼ì´ë²„ì— í¬í•¨ë˜ì–´ 있습니다.</p> @@ -2225,8 +2224,8 @@ QC-CR#1088824</a></td> ì •ë³´ 공개 취약성</h3> <p>Qualcomm Wi-Fi ë“œë¼ì´ë²„ì˜ ì •ë³´ 공개 취약성으로 ì¸í•´ 로컬 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ 권한 ìˆ˜ì¤€ì„ ë²—ì–´ë‚œ ë°ì´í„°ì— -ì•¡ì„¸ìŠ¤í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” ë¨¼ì € -ê¶Œí•œì´ ì„¤ì •ëœ í”„ë¡œì„¸ìŠ¤ì— ì¹¨íˆ¬í•´ì•¼ë§Œ 실행 가능하므로 심ê°ë„ 보통으로 í‰ê°€ë©ë‹ˆë‹¤.</p> +ì•¡ì„¸ìŠ¤í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” ë¨¼ì € ê¶Œí•œì´ ì„¤ì •ëœ í”„ë¡œì„¸ìŠ¤ì— ì¹¨íˆ¬í•´ì•¼ë§Œ +실행 가능하므로 심ê°ë„ 보통으로 í‰ê°€ë©ë‹ˆë‹¤.</p> <table> <colgroup><col width="19%" /> @@ -2299,7 +2298,7 @@ QC-CR#1087469</a></td> <td>2016ë…„ 10ì›” 22ì¼</td> </tr> </tbody></table> -<p>* ì´ ë¬¸ì œë¥¼ 해결하기 위한 패치는 공개ë˜ì§€ 않습니다. ì—…ë°ì´íŠ¸ëŠ” +<p>* ì´ ë¬¸ì œë¥¼ 해결하기 위한 패치는 공개ë˜ì–´ 있지 않습니다. ì—…ë°ì´íŠ¸ëŠ” <a href="https://developers.google.com/android/nexus/drivers">Google ê°œë°œìž ì‚¬ì´íŠ¸</a>ì—ì„œ ì œê³µë˜ëŠ” Nexus 기기용 ìµœì‹ ë°”ì´ë„ˆë¦¬ ë“œë¼ì´ë²„ì— í¬í•¨ë˜ì–´ 있습니다.</p> @@ -2433,7 +2432,7 @@ QC-CR#1090007</a> <td>2016ë…„ 12ì›” 11ì¼</td> </tr> </tbody></table> -<p>* ì´ ë¬¸ì œë¥¼ 해결하기 위한 패치는 공개ë˜ì§€ 않습니다. ì—…ë°ì´íŠ¸ëŠ” +<p>* ì´ ë¬¸ì œë¥¼ 해결하기 위한 패치는 공개ë˜ì–´ 있지 않습니다. ì—…ë°ì´íŠ¸ëŠ” <a href="https://developers.google.com/android/nexus/drivers">Google ê°œë°œìž ì‚¬ì´íŠ¸</a>ì—ì„œ ì œê³µë˜ëŠ” Nexus 기기용 ìµœì‹ ë°”ì´ë„ˆë¦¬ ë“œë¼ì´ë²„ì— í¬í•¨ë˜ì–´ 있습니다.</p> @@ -2442,7 +2441,7 @@ QC-CR#1090007</a> ë“œë¼ì´ë²„ì˜ ì •ë³´ 공개 취약성</h3> <p>Synaptics 터치스í¬ë¦° ë“œë¼ì´ë²„ì˜ ì •ë³´ 공개 취약성으로 ì¸í•´ 로컬 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ 권한 ìˆ˜ì¤€ì„ ë²—ì–´ë‚œ ë°ì´í„°ì— -ì•¡ì„¸ìŠ¤í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” ë¨¼ì € ê¶Œí•œì´ ì„¤ì •ëœ í”„ë¡œì„¸ìŠ¤ì— ì¹¨íˆ¬í•´ì•¼ë§Œ +ì•¡ì„¸ìŠ¤í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” ë¨¼ì € ê¶Œí•œì´ ì„¤ì •ëœ ì ˆì°¨ì— ì¹¨íˆ¬í•´ì•¼ë§Œ 실행 가능하므로 심ê°ë„ 보통으로 í‰ê°€ë©ë‹ˆë‹¤.</p> <table> @@ -2466,7 +2465,7 @@ QC-CR#1090007</a> <td>2016ë…„ 12ì›” 12ì¼</td> </tr> </tbody></table> -<p>* ì´ ë¬¸ì œë¥¼ 해결하기 위한 패치는 공개ë˜ì§€ 않습니다. ì—…ë°ì´íŠ¸ëŠ” +<p>* ì´ ë¬¸ì œë¥¼ 해결하기 위한 패치는 공개ë˜ì–´ 있지 않습니다. ì—…ë°ì´íŠ¸ëŠ” <a href="https://developers.google.com/android/nexus/drivers">Google ê°œë°œìž ì‚¬ì´íŠ¸</a>ì—ì„œ ì œê³µë˜ëŠ” Nexus 기기용 ìµœì‹ ë°”ì´ë„ˆë¦¬ ë“œë¼ì´ë²„ì— í¬í•¨ë˜ì–´ 있습니다.</p> @@ -2499,7 +2498,7 @@ QC-CR#1090007</a> <td>Google 사내용</td> </tr> </tbody></table> -<p>* ì´ ë¬¸ì œë¥¼ 해결하기 위한 패치는 공개ë˜ì§€ 않습니다. ì—…ë°ì´íŠ¸ëŠ” +<p>* ì´ ë¬¸ì œë¥¼ 해결하기 위한 패치는 공개ë˜ì–´ 있지 않습니다. ì—…ë°ì´íŠ¸ëŠ” <a href="https://developers.google.com/android/nexus/drivers">Google ê°œë°œìž ì‚¬ì´íŠ¸</a>ì—ì„œ ì œê³µë˜ëŠ” Nexus 기기용 ìµœì‹ ë°”ì´ë„ˆë¦¬ ë“œë¼ì´ë²„ì— í¬í•¨ë˜ì–´ 있습니다.</p> @@ -2533,12 +2532,12 @@ QC-CR#1090007</a> <td>2016ë…„ 11ì›” 10ì¼</td> </tr> </tbody></table> -<p>* ì´ ë¬¸ì œë¥¼ 해결하기 위한 패치는 공개ë˜ì§€ 않습니다. ì—…ë°ì´íŠ¸ëŠ” +<p>* ì´ ë¬¸ì œë¥¼ 해결하기 위한 패치는 공개ë˜ì–´ 있지 않습니다. ì—…ë°ì´íŠ¸ëŠ” <a href="https://developers.google.com/android/nexus/drivers">Google ê°œë°œìž ì‚¬ì´íŠ¸</a>ì—ì„œ ì œê³µë˜ëŠ” Nexus 기기용 ìµœì‹ ë°”ì´ë„ˆë¦¬ ë“œë¼ì´ë²„ì— í¬í•¨ë˜ì–´ 있습니다.</p> <h2 id="common-questions-and-answers">ì¼ë°˜ì ì¸ ì§ˆë¬¸ ë° ë‹µë³€</h2> -<p>ì´ ì„¹ì…˜ì—서는 게시íŒì„ ì½ì€ ë’¤ ì œê¸°ë 수 있는 ì¼ë°˜ì ì¸ ì§ˆë¬¸ì— ëŒ€í•œ ë‹µë³€ì„ ì œì‹œí•©ë‹ˆë‹¤.</p> +<p>ì´ ì„¹ì…˜ì—서는 게시íŒì„ ì½ì€ ë’¤ ì œê¸°ë 수 있는 ì¼ë°˜ì ì¸ ì§ˆë¬¸ì˜ ë‹µë³€ì„ ì œì‹œí•©ë‹ˆë‹¤.</p> <p><strong>1. ë‚´ 기기가 ì—…ë°ì´íŠ¸ë˜ì–´ ì´ ë¬¸ì œê°€ í•´ê²°ë˜ì—ˆëŠ”지 어떻게 ì•Œ 수 있나요? </strong></p> <p>ê¸°ê¸°ì˜ ë³´ì•ˆ 패치 ìˆ˜ì¤€ì„ í™•ì¸í•˜ëŠ” ë°©ë²•ì„ ì•Œì•„ë³´ë ¤ë©´ @@ -2559,7 +2558,8 @@ QC-CR#1090007</a> </ul> <p><strong>2 ì´ ê²Œì‹œíŒì— ë‘ ê°€ì§€ 보안 패치 ìˆ˜ì¤€ì´ ìžˆëŠ” ì´ìœ ê°€ 무엇ì¸ê°€ìš”?</strong></p> <p>ì´ ê²Œì‹œíŒì—는 Android 파트너가 ëª¨ë“ Android 기기ì—ì„œ ìœ ì‚¬í•˜ê²Œ ë°œìƒí•˜ëŠ” -취약성 ë¬¸ì œì˜ ì¼ë¶€ë¥¼ ë”ìš± ë¹ ë¥´ê³ ìœ ì—°í•˜ê²Œ 해결하ë„ë¡ í•˜ê¸° 위해 ë‘ ê°€ì§€ 보안 패치 ìˆ˜ì¤€ì´ í¬í•¨ë˜ì–´ 있습니다. Android 파트너는 ì´ ê²Œì‹œíŒì— ì–¸ê¸‰ëœ ë¬¸ì œë¥¼ ëª¨ë‘ ìˆ˜ì •í•˜ê³ +취약성 ë¬¸ì œì˜ ì¼ë¶€ë¥¼ ë”ìš± ë¹ ë¥´ê³ ìœ ì—°í•˜ê²Œ 해결하기 위한 +ë‘ ê°€ì§€ 보안 패치 ìˆ˜ì¤€ì´ í¬í•¨ë˜ì–´ 있습니다. Android 파트너는 ì´ ê²Œì‹œíŒì— ì–¸ê¸‰ëœ ë¬¸ì œë¥¼ ëª¨ë‘ ìˆ˜ì •í•˜ê³ ìµœì‹ ë³´ì•ˆ 패치 ìˆ˜ì¤€ì„ ì‚¬ìš©í•˜ëŠ” ê²ƒì´ ì¢‹ìŠµë‹ˆë‹¤.</p> <ul> <li>2017ë…„ 3ì›” 1ì¼ ë³´ì•ˆ 패치 ìˆ˜ì¤€ì„ ì‚¬ìš©í•˜ëŠ” 기기는 ì´ ë³´ì•ˆ 패치 수준과 @@ -2584,15 +2584,16 @@ QC-CR#1090007</a> 기기</a>ê°€ í¬í•¨ë©ë‹ˆë‹¤. Nexus 5X, Nexus 6, Nexus 6P, Nexus 9, Android One, Nexus Player, Pixel C, Pixel, Pixel XL</li> <li><strong>ì¼ë¶€ Google 기기</strong>: ë¬¸ì œê°€ ì¼ë¶€ Google ê¸°ê¸°ì— ì˜í–¥ì„ 미치는 경우, -ì˜í–¥ì„ 받는 Google 기기가 <em>ì—…ë°ì´íŠ¸ëœ Google 기기</em> ì—´ì— í‘œì‹œë©ë‹ˆë‹¤.</li> +ì˜í–¥ì„ 받는 Google 기기가 <em>ì—…ë°ì´íŠ¸ëœ Google 기기</em> ì—´ì— +표시ë©ë‹ˆë‹¤.</li> <li><strong>Google 기기 해당 ì—†ìŒ</strong>: ë¬¸ì œê°€ Android 7.0ì„ ì‹¤í–‰í•˜ëŠ” Google ê¸°ê¸°ì— ì˜í–¥ì„ 미치지 않는 경우, í‘œì˜ <em>ì—…ë°ì´íŠ¸ëœ Google 기기</em> ì—´ì— 'ì—†ìŒ'ì´ë¼ê³ 표시ë©ë‹ˆë‹¤. </li> </ul> <p><strong>4. 참조 ì—´ì˜ í•ëª©ì´ 매핑하는 대ìƒì€ 무엇ì¸ê°€ìš”?</strong></p> -<p>취약성 ì„¸ë¶€ì •ë³´ í‘œì˜ <em>참조</em> ì—´ì— ìžˆëŠ” í•ëª©ì€ 참조 ê°’ì´ ì†í•œ -ì¡°ì§ì„ 나타내는 ì ‘ë‘어를 í¬í•¨í• 수 있습니다. ì´ëŸ¬í•œ ì ‘ë‘어는 -다ìŒê³¼ ê°™ì´ ë§¤í•‘ë©ë‹ˆë‹¤.</p> +<p>취약성 ì„¸ë¶€ì •ë³´ í‘œì˜ <em>참조</em> ì—´ì— ìžˆëŠ” í•ëª©ì€ +참조 ê°’ì´ ì†í•œ ì¡°ì§ì„ 나타내는 ì ‘ë‘어를 í¬í•¨í• 수 +있습니다. ì´ ì ‘ë‘어는 다ìŒê³¼ ê°™ì´ ë§¤í•‘ë©ë‹ˆë‹¤.</p> <table> <tbody><tr> <th>ì ‘ë‘ì–´</th> diff --git a/ko/security/bulletin/2017-05-01.html b/ko/security/bulletin/2017-05-01.html index fc25af2e..834ee2d6 100644 --- a/ko/security/bulletin/2017-05-01.html +++ b/ko/security/bulletin/2017-05-01.html @@ -42,10 +42,10 @@ Android 오픈소스 프로ì 트(AOSP) ì €ìž¥ì†Œì— ë°°í¬ë˜ì—ˆìœ¼ë©° ì´ ê²Œì 기준으로 ë‚´ë ¤ì§‘ë‹ˆë‹¤.</p> <p>ì‹¤ì œ ê³ ê°ì´ 새로 ë³´ê³ ëœ ì´ëŸ¬í•œ ë¬¸ì œë¡œ ì¸í•´ 악용당했다는 ì‹ ê³ ëŠ” -ì ‘ìˆ˜ë˜ì§€ 않았습니다. <a href="https://developer.android.com/training/safetynet/index.html">SafetyNet</a>ê³¼ ê°™ì´ -Android 플랫í¼ì˜ ë³´ì•ˆì„ ê°œì„ í•˜ëŠ” <a href="/security/enhancements/index.html">Android -보안 í”Œëž«í¼ ë³´í˜¸</a> ë° ì„œë¹„ìŠ¤ 보호 ê¸°ëŠ¥ì— ê´€í•´ ìžì„¸ížˆ ì•Œì•„ë³´ë ¤ë©´ -<a href="#mitigations">Android ë° Google 서비스 완화</a> ì„¹ì…˜ì„ ì°¸ì¡°í•˜ì„¸ìš”.</p> +ì ‘ìˆ˜ë˜ì§€ 않았습니다. <a href="https://developer.android.com/training/safetynet/index.html">SafetyNet</a>ê³¼ ê°™ì´ Android 플랫í¼ì˜ ë³´ì•ˆì„ ê°œì„ í•˜ëŠ” +<a href="/security/enhancements/index.html">Android 보안 í”Œëž«í¼ ë³´í˜¸</a> ë° ì„œë¹„ìŠ¤ 보호 ê¸°ëŠ¥ì— ê´€í•´ ìžì„¸ížˆ ì•Œì•„ë³´ë ¤ë©´ +<a href="#mitigations">Android ë° Google 서비스 +완화</a> ì„¹ì…˜ì„ ì°¸ì¡°í•˜ì„¸ìš”.</p> <p>ëª¨ë“ ê³ ê°ì€ 기기ì—ì„œ ì´ ì—…ë°ì´íŠ¸ë¥¼ 수ë½í•˜ëŠ” ê²ƒì´ ì¢‹ìŠµë‹ˆë‹¤.</p> <h2 id="announcements">공지사í•</h2> @@ -101,8 +101,8 @@ Play ë‚´ì—ì„œ 기기 루팅 ë„구는 금지ë˜ì–´ 있지만 Di Shen(<a href="https://twitter.com/returnsme">@returnsme</a>): CVE-2016-10287</li> <li>Trend Microì˜ Ecular Xu(å¾å¥): CVE-2017-0599, CVE-2017-0635</li> -<li><a href="http://www.ms509.com">MS509Team</a>ì˜ En He(<a href="https://twitter.com/heeeeen4x">@heeeeen4x</a>), -Bo Liu: CVE-2017-0601</li> +<li><a href="http://www.ms509.com">MS509Team</a>ì˜ +En He(<a href="https://twitter.com/heeeeen4x">@heeeeen4x</a>), Bo Liu: CVE-2017-0601</li> <li><a href="https://twrp.me/">Team Win Recovery Project</a>ì˜ Ethan Yonker: CVE-2017-0493</li> <li>Qihoo 360 Technology Co. Ltd @@ -112,8 +112,9 @@ CVE-2017-0624, CVE-2017-0616, CVE-2017-0617, CVE-2016-10294, CVE-2016-10295, CVE-2016-10296</li> <li>Tencent PC Managerì˜ godzheng(郑文选 <a href="https://twitter.com/virtualseekers">@VirtualSeekers</a>): CVE-2017-0602</li> -<li><a href="http://tuncay2.web.engr.illinois.edu">University of Illinois at Urbana-Champaign</a>ì˜ -<a href="https://www.linkedin.com/in/g%C3%BCliz-seray-tuncay-952a1b9/">Güliz Seray Tuncay</a>: CVE-2017-0593</li> +<li><a href="http://tuncay2.web.engr.illinois.edu">University of Illinois atUrbana-Champaign</a>ì˜ +<a href="https://www.linkedin.com/in/g%C3%BCliz-seray-tuncay-952a1b9/">Güliz +Seray Tuncay</a>: CVE-2017-0593</li> <li>Qihoo 360 Technology Co. Ltd. Alpha Teamì˜ Hao Chen, Guang Gong: CVE-2016-10283</li> <li>Xiaomi Incì˜ Juhu Nie, Yang Cheng, Nan Li, Qiwu Huang: CVE-2016-10276</li> @@ -128,8 +129,8 @@ Chao Yang, Yang song: CVE-2016-10281, CVE-2016-10280</li> <li><a href="mailto:sbauer@plzdonthack.me">Scott Bauer</a>(<a href="https://twitter.com/ScottyBauer1">@ScottyBauer1</a>): CVE-2016-10274</li> <li><a href="http://c0reteam.org">C0RE Team</a>ì˜ <a href="mailto:segfault5514@gmail.com">Tong Lin</a>, <a href="mailto:computernik@gmail.com">Yuan-Tsung Lo</a>, Xuxian Jiang: CVE-2016-10291</li> <li>Vasily Vasiliev: CVE-2017-0589</li> -<li><a href="http://www.trendmicro.com">Trend Micro</a> <a href="http://blog.trendmicro.com/trendlabs-security-intelligence/category/mobile">Mobile -Threat Response Team</a>ì˜ V.E.O(<a href="https://twitter.com/vysea">@VYSEa</a>): +<li><a href="http://www.trendmicro.com">Trend Micro</a> <a href="http://blog.trendmicro.com/trendlabs-security-intelligence/category/mobile">Mobile Threat Response Team</a>ì˜ +V.E.O(<a href="https://twitter.com/vysea">@VYSEa</a>): CVE-2017-0590, CVE-2017-0587, CVE-2017-0600</li> <li>Tencent Security Platform Departmentì˜ Xiling Gong: CVE-2017-0597</li> <li>360 Marvel Teamì˜ Xingyuan Lin: CVE-2017-0627</li> @@ -169,7 +170,7 @@ AOSP ë²„ì „(해당하는 경우), ì‹ ê³ ëœ ë‚ ì§œê°€ í¬í•¨ëœ 표가 ì œì‹œë© <col width="18%" /> <col width="17%" /> </colgroup><tbody><tr> - <th>공통 취약성 ë° ë…¸ì¶œ</th> + <th>CVE</th> <th>참조</th> <th>심ê°ë„</th> <th>ì—…ë°ì´íŠ¸ëœ Google 기기</th> @@ -180,7 +181,7 @@ AOSP ë²„ì „(해당하는 경우), ì‹ ê³ ëœ ë‚ ì§œê°€ í¬í•¨ëœ 표가 ì œì‹œë© <td>CVE-2017-0587</td> <td><a href="https://android.googlesource.com/platform/external/libmpeg2/+/a86eb798d077b9b25c8f8c77e3c02c2f287c1ce7">A-35219737</a></td> <td>심ê°</td> - <td>ì „ì²´</td> + <td>모ë‘</td> <td>6.0, 6.0.1, 7.0, 7.1.1, 7.1.2</td> <td>2017ë…„ 1ì›” 4ì¼</td> </tr> @@ -204,7 +205,7 @@ AOSP ë²„ì „(해당하는 경우), ì‹ ê³ ëœ ë‚ ì§œê°€ í¬í•¨ëœ 표가 ì œì‹œë© <td>CVE-2017-0590</td> <td><a href="https://android.googlesource.com/platform/external/libhevc/+/45c97f878bee15cd97262fe7f57ecea71990fed7">A-35039946</a></td> <td>심ê°</td> - <td>ì „ì²´</td> + <td>모ë‘</td> <td>5.0.2, 5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2</td> <td>2017ë…„ 2ì›” 6ì¼</td> </tr> @@ -326,7 +327,7 @@ AOSP ë²„ì „(해당하는 경우), ì‹ ê³ ëœ ë‚ ì§œê°€ í¬í•¨ëœ 표가 ì œì‹œë© <col width="18%" /> <col width="17%" /> </colgroup><tbody><tr> - <th>공통 취약성 ë° ë…¸ì¶œ</th> + <th>CVE</th> <th>참조</th> <th>심ê°ë„</th> <th>ì—…ë°ì´íŠ¸ëœ Google 기기</th> @@ -649,7 +650,7 @@ AOSP ë²„ì „(해당하는 경우), ì‹ ê³ ëœ ë‚ ì§œê°€ í¬í•¨ëœ 표가 ì œì‹œë© <td>CVE-2015-7555</td> <td><a href="https://android.googlesource.com/platform/external/giflib/+/dc07290edccc2c3fc4062da835306f809cea1fdc">A-34697653</a></td> <td>심ê°</td> - <td>ì „ì²´</td> + <td>모ë‘</td> <td>4.4.4, 5.0.2, 5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2</td> <td>2016ë…„ 4ì›” 13ì¼</td> </tr> @@ -1124,7 +1125,7 @@ QC-CR#1090237</a></td> 권한 승격 취약성</h3> <p>ì»¤ë„ ì„±ëŠ¥ 하위 ì‹œìŠ¤í…œì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ 로컬 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ -ì»¤ë„ ì»¨í…스트 ë‚´ì—ì„œ ìž„ì˜ì˜ 코드를 ì‹¤í–‰í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” ë¨¼ì € ê¶Œí•œì´ ì„¤ì •ëœ ì ˆì°¨ì— ì¹¨íˆ¬í•´ì•¼ë§Œ 실행 +ì»¤ë„ ì»¨í…스트 ë‚´ì—ì„œ ìž„ì˜ì˜ 코드를 ì‹¤í–‰í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” ë¨¼ì € ê¶Œí•œì´ ì„¤ì •ëœ í”„ë¡œì„¸ìŠ¤ì— ì¹¨íˆ¬í•´ì•¼ë§Œ 실행 가능하므로 심ê°ë„ 높ìŒìœ¼ë¡œ í‰ê°€ë©ë‹ˆë‹¤.</p> <table> @@ -1157,7 +1158,7 @@ One, Nexus Player</td> <p>Qualcomm 사운드 ë“œë¼ì´ë²„ì˜ ê¶Œí•œ 승격 취약성으로 ì¸í•´ 로컬 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ ì»¤ë„ ì»¨í…스트 ë‚´ì—ì„œ ìž„ì˜ì˜ 코드를 -ì‹¤í–‰í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” ë¨¼ì € ê¶Œí•œì´ ì„¤ì •ëœ ì ˆì°¨ì— ì¹¨íˆ¬í•´ì•¼ë§Œ 실행 +ì‹¤í–‰í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” ë¨¼ì € ê¶Œí•œì´ ì„¤ì •ëœ í”„ë¡œì„¸ìŠ¤ì— ì¹¨íˆ¬í•´ì•¼ë§Œ 실행 가능하므로 심ê°ë„ 높ìŒìœ¼ë¡œ í‰ê°€ë©ë‹ˆë‹¤.</p> <table> @@ -2390,8 +2391,8 @@ QC-CR#1093232</a></td> <p>Qualcomm 사운드 ë“œë¼ì´ë²„ì˜ ì •ë³´ 공개 취약성으로 ì¸í•´ 로컬 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ 권한 ìˆ˜ì¤€ì„ ë²—ì–´ë‚œ ë°ì´í„°ì— -ì•¡ì„¸ìŠ¤í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” ë¨¼ì € ê¶Œí•œì´ ì„¤ì •ëœ ì ˆì°¨ì— ì¹¨íˆ¬í•´ì•¼ë§Œ -실행 가능하므로 심ê°ë„ 보통으로 í‰ê°€ë©ë‹ˆë‹¤.</p> +ì•¡ì„¸ìŠ¤í• ìˆ˜ 있습니다. ì´ ë¬¸ì œëŠ” ë¨¼ì € +ê¶Œí•œì´ ì„¤ì •ëœ í”„ë¡œì„¸ìŠ¤ì— ì¹¨íˆ¬í•´ì•¼ë§Œ 실행 가능하므로 심ê°ë„ 보통으로 í‰ê°€ë©ë‹ˆë‹¤.</p> <table> <colgroup><col width="19%" /> @@ -2822,8 +2823,8 @@ Qualcomm AMSS 보안 게시íŒì„ 통해 ë°°í¬ë˜ì—ˆìŠµë‹ˆë‹¤. ê° ì·¨ì•½ì„±ì˜ '모ë‘'ë¼ê³ 표시ë©ë‹ˆë‹¤. '모ë‘'ì—는 다ìŒê³¼ ê°™ì€ <a href="https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices">지ì›ë˜ëŠ” 기기</a>ê°€ í¬í•¨ë©ë‹ˆë‹¤. Nexus 5X, Nexus 6, Nexus 6P, Nexus 9, Android One, Nexus Player, Pixel C, Pixel, Pixel XL</li> <li><strong>ì¼ë¶€ Google 기기</strong>: ë¬¸ì œê°€ ëª¨ë“ Google ê¸°ê¸°ì— ì˜í–¥ì„ 미치는 ê²ƒì´ -ì•„ë‹Œ 경우, ì˜í–¥ì„ 받는 Google 기기가 <em>ì—…ë°ì´íŠ¸ëœ Google 기기</em> ì—´ì— -표시ë©ë‹ˆë‹¤.</li> +ì•„ë‹Œ 경우, ì˜í–¥ì„ 받는 Google 기기가 <em>ì—…ë°ì´íŠ¸ëœ Google 기기 ì—´ì— +표시ë©ë‹ˆë‹¤.</em></li> <li><strong>Google 기기 해당 ì—†ìŒ</strong>: ë¬¸ì œê°€ Android 7.0ì„ ì‹¤í–‰í•˜ëŠ” Google ê¸°ê¸°ì— ì˜í–¥ì„ 미치지 않는 경우, í‘œì˜ <em>ì—…ë°ì´íŠ¸ëœ Google 기기</em> ì—´ì— 'ì—†ìŒ'ì´ë¼ê³ 표시ë©ë‹ˆë‹¤. </li> diff --git a/ko/security/bulletin/2017-11-01.html b/ko/security/bulletin/2017-11-01.html index 0826c8fa..3ca693de 100644 --- a/ko/security/bulletin/2017-11-01.html +++ b/ko/security/bulletin/2017-11-01.html @@ -71,8 +71,8 @@ AOSP ì™¸ë¶€ì˜ íŒ¨ì¹˜ ë§í¬ë„ í¬í•¨ë˜ì–´ 있습니다. </ul> <h2 id="mitigations">Android ë° Google 서비스 완화</h2> <p> -다ìŒì€ <a href="/security/enhancements/index.html">Android 보안 플랫í¼</a> -ë° <a href="//www.android.com/play-protect">Google Play 프로í…트</a>와 ê°™ì€ ì„œë¹„ìŠ¤ 보호 기능ì—ì„œ ì œê³µí•˜ëŠ” ì™„í™”ì— ê´€í•œ 요약입니다. ì´ëŸ¬í•œ +다ìŒì€ <a href="/security/enhancements/index.html">Android 보안 플랫í¼</a> ë° <a href="//www.android.com/play-protect">Google Play 프로í…트</a>와 ê°™ì€ +서비스 보호 기능ì—ì„œ ì œê³µí•˜ëŠ” ì™„í™”ì— ê´€í•œ 요약입니다. ì´ëŸ¬í•œ ê¸°ëŠ¥ì„ í†µí•´ Androidì—ì„œ 보안 ì·¨ì•½ì„±ì´ ì•…ìš©ë ê°€ëŠ¥ì„±ì„ ì¤„ìž…ë‹ˆë‹¤. </p> @@ -91,8 +91,8 @@ AOSP ì™¸ë¶€ì˜ íŒ¨ì¹˜ ë§í¬ë„ í¬í•¨ë˜ì–´ 있습니다. <p> ë‹¤ìŒ ì„¹ì…˜ì—서는 2017-11-01 패치 ìˆ˜ì¤€ì— ì ìš©ë˜ëŠ” ê° ë³´ì•ˆ ì·¨ì•½ì„±ì— ê´€í•´ ìžì„¸ížˆ 알아볼 수 있습니다. ì·¨ì•½ì„±ì€ ì˜í–¥ì„ 받는 -구성요소 ì•„ëž˜ì— ë¶„ë¥˜ë˜ì–´ 있습니다. 여기ì—는 ë¬¸ì œ 설명 ë° -CVE, ê´€ë ¨ 참조, <a href="#type">취약성 ìœ í˜•</a>, <a href="/security/overview/updates-resources.html#severity">심ê°ë„</a>, ì—…ë°ì´íŠ¸ëœ AOSP ë²„ì „(해당하는 경우)ì´ +구성요소 ì•„ëž˜ì— ë¶„ë¥˜ë˜ì–´ 있습니다. 여기ì—는 ë¬¸ì œ 설명 ë° CVE, +ê´€ë ¨ 참조, <a href="#type">취약성 ìœ í˜•</a>, <a href="/security/overview/updates-resources.html#severity">심ê°ë„</a>, ì—…ë°ì´íŠ¸ëœ AOSP ë²„ì „(해당하는 경우)ì´ í¬í•¨ëœ 표가 ì œì‹œë©ë‹ˆë‹¤. 가능한 경우 AOSP ë³€ê²½ì‚¬í• ëª©ë¡ê³¼ ê°™ì´ ë¬¸ì œë¥¼ í•´ê²°í•œ 공개 변경사í•ì„ 버그 IDì— ì—°ê²°í•©ë‹ˆë‹¤. í•˜ë‚˜ì˜ ë²„ê·¸ì™€ ê´€ë ¨ëœ ë³€ê²½ì‚¬í•ì´ 여러 ê°œì¸ ê²½ìš° 추가 참조가 버그 ID 다ìŒì— 오는 @@ -566,7 +566,7 @@ Android ë²„ì „ í™•ì¸ ë° ì—…ë°ì´íŠ¸</a>를 참조하세요. <li>2017-11-01 보안 패치 ìˆ˜ì¤€ì„ ì‚¬ìš©í•˜ëŠ” 기기는 ì´ ë³´ì•ˆ 패치 수준과 ê´€ë ¨ëœ ëª¨ë“ ë¬¸ì œì™€ ì´ì „ 보안 게시íŒì— ë³´ê³ ëœ ëª¨ë“ ë¬¸ì œì˜ ìˆ˜ì •ì‚¬í•ì„ í¬í•¨í•´ì•¼ 합니다.</li> - <li>2017-11-05 보안 패치 ìˆ˜ì¤€ì„ ì‚¬ìš©í•˜ëŠ” 기기는 2017-11-01 보안 패치 수준과 + <li>2017-11-05 보안 패치 ìˆ˜ì¤€ì„ ì‚¬ìš©í•˜ëŠ” 기기는 ì´ ë³´ì•ˆ 패치 수준 ë° 2017-11-01 보안 패치 수준과 ê´€ë ¨ëœ ëª¨ë“ ë¬¸ì œì™€ ì´ì „ 보안 게시íŒì— ë³´ê³ ëœ ëª¨ë“ ë¬¸ì œì˜ ìˆ˜ì •ì‚¬í•ì„ í¬í•¨í•´ì•¼ 합니다.</li> <li>2017-11-06 ì´í›„ì˜ ë³´ì•ˆ 패치 ìˆ˜ì¤€ì„ ì‚¬ìš©í•˜ëŠ” 기기는 ì´ ë³´ì•ˆ 게시íŒê³¼ @@ -608,7 +608,7 @@ Android ë²„ì „ í™•ì¸ ë° ì—…ë°ì´íŠ¸</a>를 참조하세요. <td>서비스 거부</td> </tr> <tr> - <td>해당 ì—†ìŒ</td> + <td>N/A</td> <td>분류 ì—†ìŒ</td> </tr> </tbody></table> @@ -667,8 +667,7 @@ Android ë²„ì „ í™•ì¸ ë° ì—…ë°ì´íŠ¸</a>를 참조하세요. Android ê¸°ê¸°ì˜ ìµœì‹ ë³´ì•ˆ 패치 ìˆ˜ì¤€ì„ ì„ ì–¸í•˜ëŠ” ë° í•„ìš”í•©ë‹ˆë‹¤. 기기/파트너 보안 게시íŒì— ì„¤ëª…ëœ ê²ƒê³¼ ê°™ì€ ì¶”ê°€ 보안 ì·¨ì•½ì„±ì€ ë³´ì•ˆ 패치 ìˆ˜ì¤€ì„ ì„ ì–¸í•˜ëŠ” ë° í•„ìš”í•˜ì§€ 않습니다. -Android 기기 ë° ì¹©ì…‹ ì œì¡°ì—…ì²´ëŠ” -<a href="//security.samsungmobile.com/securityUpdate.smsb">삼성</a>, <a href="//lgsecurity.lge.com/security_updates.html">LGE</a>, ë˜ëŠ” <a href="/security/bulletin/pixel/">Pixel&hairsp;/&hairsp;Nexus</a> +Android 기기 ë° ì¹©ì…‹ ì œì¡°ì—…ì²´ëŠ” <a href="//security.samsungmobile.com/securityUpdate.smsb">삼성</a>, <a href="//lgsecurity.lge.com/security_updates.html">LGE</a>, ë˜ëŠ” <a href="/security/bulletin/pixel/">Pixel&hairsp;/&hairsp;Nexus</a> 보안 게시íŒê³¼ ê°™ì€ ìžì²´ 보안 웹사ì´íŠ¸ë¥¼ 통해 ê¸°ê¸°ì˜ ë‹¤ë¥¸ ìˆ˜ì •ì‚¬í•ì´ 있는지를 설명하는 ê²ƒì´ ì¢‹ìŠµë‹ˆë‹¤. </p> diff --git a/ko/security/bulletin/2018-01-01.html b/ko/security/bulletin/2018-01-01.html index 46c9906a..8aa3a0ad 100644 --- a/ko/security/bulletin/2018-01-01.html +++ b/ko/security/bulletin/2018-01-01.html @@ -19,7 +19,7 @@ See the License for the specific language governing permissions and limitations under the License. --> -<p><em>2018ë…„ 1ì›” 2ì¼ì— 게시ë¨</em></p> +<p><em>2018ë…„ 1ì›” 2ì¼ ê²Œì‹œë¨ | 2018ë…„ 1ì›” 29ì¼ ì—…ë°ì´íŠ¸ë¨</em></p> <p> Android 보안 게시íŒì—서는 Android ê¸°ê¸°ì— ì˜í–¥ì„ 미치는 보안 취약성 @@ -29,12 +29,10 @@ Android 보안 게시íŒì—서는 Android ê¸°ê¸°ì— ì˜í–¥ì„ 미치는 보안 ì 확ì¸í•˜ì„¸ìš”. </p> <p> -Android 파트너ì—게는 게시ë˜ê¸° 최소 í•œ 달 ì „ì— ëª¨ë“ ë¬¸ì œ ê´€ë ¨ ì•Œë¦¼ì´ -ì „ë‹¬ë˜ì—ˆìŠµë‹ˆë‹¤. -ì´ëŸ¬í•œ ë¬¸ì œì˜ í•´ê²°ì„ ìœ„í•œ 소스 코드 패치는 향후 48시간 ë™ì•ˆ -Android 오픈소스 프로ì 트(AOSP) ì €ìž¥ì†Œì— ë°°í¬ë©ë‹ˆë‹¤. 패치를 ì‚¬ìš©í• ìˆ˜ 있게 ë˜ë©´ AOSP -ë§í¬ì™€ 함께 ì´ ê²Œì‹œíŒì„ ìˆ˜ì •í•˜ê² ìŠµë‹ˆë‹¤. -</p> +Android 파트너ì—게는 게시ë˜ê¸° 최소 í•œ 달 ì „ì— ëª¨ë“ ë¬¸ì œ ê´€ë ¨ ì•Œë¦¼ì´ ì „ë‹¬ë˜ì—ˆìŠµë‹ˆë‹¤. +ì´ëŸ¬í•œ ë¬¸ì œë¥¼ 해결하기 위한 소스 코드 패치는 Android 오픈소스 +프로ì 트(AOSP) ì €ìž¥ì†Œì— ë°°í¬ë˜ì—ˆìœ¼ë©° ì´ ê²Œì‹œíŒì—ë„ ë§í¬ë˜ì–´ 있습니다. ì´ ê²Œì‹œíŒì—는 +AOSP ì™¸ë¶€ì— ìžˆëŠ” 패치로 ì—°ê²°ë˜ëŠ” ë§í¬ë„ í¬í•¨ë˜ì–´ 있습니다.</p> <p> ì´ëŸ¬í•œ ë¬¸ì œ 중 가장 심ê°í•œ ê²ƒì€ ë¯¸ë””ì–´ í”„ë ˆìž„ì›Œí¬ì˜ 심ê°í•œ 보안 취약성으로, 특별히 ì œìž‘ëœ íŒŒì¼ì„ 사용하는 ì›ê²© 공격ìžê°€ ê¶Œí•œì´ ì„¤ì •ëœ í”„ë¡œì„¸ìŠ¤ì˜ ì»¨í…스트 @@ -47,8 +45,8 @@ Android 오픈소스 프로ì 트(AOSP) ì €ìž¥ì†Œì— ë°°í¬ë©ë‹ˆë‹¤. 패치를 ì‹¤ì œ ê³ ê°ì´ 새로 ë³´ê³ ëœ ì´ëŸ¬í•œ ë¬¸ì œë¡œ ì¸í•´ 악용당했다는 ì‹ ê³ ëŠ” ì ‘ìˆ˜ë˜ì§€ 않았습니다. Android 플랫í¼ì˜ ë³´ì•ˆì„ ê°œì„ í•˜ëŠ” <a href="/security/enhancements/index.html">Android 보안 í”Œëž«í¼ ë³´í˜¸</a> ë° Google Play 프로í…íŠ¸ì— ê´€í•´ -ìžì„¸ížˆ ì•Œì•„ë³´ë ¤ë©´ <a href="#mitigations">Android ë° Google Play 프로í…트 완화 -</a> ì„¹ì…˜ì„ ì°¸ì¡°í•˜ì„¸ìš”. +ìžì„¸ížˆ ì•Œì•„ë³´ë ¤ë©´ <a href="#mitigations">Android ë° Google Play 프로í…트 완화</a> +ì„¹ì…˜ì„ ì°¸ì¡°í•˜ì„¸ìš”. </p> <p> <strong>ì°¸ê³ :</strong> Google ê¸°ê¸°ì˜ ìµœì‹ ë¬´ì„ ì—…ë°ì´íŠ¸(OTA) ë° íŽŒì›¨ì–´ ì´ë¯¸ì§€ ê´€ë ¨ ì •ë³´ëŠ” @@ -56,6 +54,24 @@ Android 오픈소스 프로ì 트(AOSP) ì €ìž¥ì†Œì— ë°°í¬ë©ë‹ˆë‹¤. 패치를 보안 게시íŒì„ 참조하세요. </p> <h2 id="announcements">공지사í•</h2> +<aside class="note"> +<p><strong>ì°¸ê³ :</strong> í”„ë¡œì„¸ì„œì˜ ì¶”ë¡ ì 실행과 ê´€ë ¨ëœ ì¼ë ¨ì˜ +취약성 CVE-2017-5715, CVE-2017-5753, CVE-2017-5754ê°€ +공개ë˜ì—ˆìŠµë‹ˆë‹¤ Android는 ARM 기반 Android 기기ì—ì„œ +무단 ì •ë³´ 공개를 허용하는 ì´ëŸ¬í•œ ì·¨ì•½ì„±ì˜ ì„±ê³µì ì¸ +ë³µì œë¥¼ ì¸ì‹í•˜ì§€ 못합니다. +</p> +<p> +보호를 강화하기 위해 ì´ ê²Œì‹œíŒì— í¬í•¨ëœ CVE-2017-13218ì˜ +ì—…ë°ì´íŠ¸ëŠ” ê³ ì •ë°€ 타ì´ë¨¸ë¡œì˜ 액세스를 줄ì´ë©°, +ì´ë¥¼ 통해 ARM í”„ë¡œì„¸ì„œì˜ ëª¨ë“ ì•Œë ¤ì§„ ë³€í˜•ì˜ ì‚¬ì´ë“œ ì±„ë„ ê³µê²©(예: +CVE-2017-5715, CVE-2017-5753, CVE-2017-5754)ì„ ì œí•œí• ìˆ˜ 있습니다. +</p> +<p>Android 사용ìžëŠ” 기기ì—ì„œ 사용 가능한 보안 ì—…ë°ì´íŠ¸ë¥¼ 수ë½í•˜ëŠ” +ê²ƒì´ ì¢‹ìŠµë‹ˆë‹¤. ìžì„¸í•œ ë‚´ìš©ì€ +<a href="https://security.googleblog.com/2018/01/todays-cpu-vulnerability-what-you-need.html">Google +보안 블로그</a>를 참조하세요.</p> +</aside> <p> Googleì—서는 새로운 <a href="/security/bulletin/pixel/">Pixel&hairsp;/&hairsp;Nexus 보안 @@ -74,9 +90,9 @@ Googleì—서는 새로운 <li>Android í”Œëž«í¼ ìµœì‹ ë²„ì „ì˜ í–¥ìƒëœ 기능으로 Androidì˜ ì—¬ëŸ¬ ë¬¸ì œë¥¼ 악용하기가 ë”ìš± ì–´ë ¤ì›Œì¡ŒìŠµë‹ˆë‹¤. 가능하다면 ëª¨ë“ ì‚¬ìš©ìžëŠ” ìµœì‹ ë²„ì „ì˜ Androidë¡œ ì—…ë°ì´íŠ¸í•˜ëŠ” ê²ƒì´ ì¢‹ìŠµë‹ˆë‹¤. -</li><li>Android 보안팀ì—서는 <a href="https://www.android.com/play-protect">Google Play 프로í…트</a> -를 통해 악용사례를 ì ê·¹ì 으로 모니터ë§í•˜ê³ <a href="/security/reports/Google_Android_Security_PHA_classifications.pdf">ìž ìž¬ì 으로 ìœ í•´í•œ ì• í”Œë¦¬ì¼€ì´ì…˜ -</a>ì— ê´€í•´ 사용ìžì—게 ê²½ê³ ë¥¼ 보냅니다. Google Play 프로í…트는 +</li><li>Android 보안팀ì—서는 <a href="https://www.android.com/play-protect">Google Play 프로í…트</a>를 통해 +악용사례를 ì ê·¹ì 으로 모니터ë§í•˜ê³ <a href="/security/reports/Google_Android_Security_PHA_classifications.pdf">ìœ í•´í• ìˆ˜ 있는 +ì• í”Œë¦¬ì¼€ì´ì…˜</a>ì— ê´€í•´ 사용ìžì—게 ê²½ê³ ë¥¼ 보냅니다. Google Play 프로í…트는 <a href="http://www.android.com/gms">Google ëª¨ë°”ì¼ ì„œë¹„ìŠ¤</a>ê°€ ì ìš©ëœ ê¸°ê¸°ì— ê¸°ë³¸ì 으로 사용 ì„¤ì •ë˜ì–´ 있으며 Google Play 외부ì—ì„œ ê°€ì ¸ì˜¨ ì•±ì„ ì„¤ì¹˜í•˜ëŠ” 사용ìžì—게 특히 중요합니다.</li></ul> <h2 id="2018-01-01-security-patch-level—vulnerability-details">2018-01-01 @@ -85,10 +101,10 @@ Google Play 외부ì—ì„œ ê°€ì ¸ì˜¨ ì•±ì„ ì„¤ì¹˜í•˜ëŠ” 사용ìžì—게 특히 ì¤ ë‹¤ìŒ ì„¹ì…˜ì—서는 2018-01-01 패치 ìˆ˜ì¤€ì— ì ìš©ë˜ëŠ” ê° ë³´ì•ˆ ì·¨ì•½ì„±ì— ê´€í•´ ìžì„¸ížˆ 알아볼 수 있습니다. ì·¨ì•½ì„±ì€ ì˜í–¥ì„ 받는 구성요소 ì•„ëž˜ì— ë¶„ë¥˜ë˜ì–´ 있습니다. 여기ì—는 ë¬¸ì œ 설명 ë° -CVE, ê´€ë ¨ 참조, <a href="#type">취약성 ìœ í˜•</a>, <a href="/security/overview/updates-resources.html#severity">심ê°ë„</a>, ì—…ë°ì´íŠ¸ëœ -AOSP ë²„ì „(해당하는 경우)ì´ -í¬í•¨ëœ 표가 -ì œì‹œë©ë‹ˆë‹¤. 가능한 경우 AOSP ë³€ê²½ì‚¬í• ëª©ë¡ê³¼ ê°™ì´ +CVE, ê´€ë ¨ 참조, <a href="#type">취약성 +ìœ í˜•</a>, +<a href="/security/overview/updates-resources.html#severity">심ê°ë„</a>, +ì—…ë°ì´íŠ¸ëœ AOSP ë²„ì „(해당하는 경우)ì´ í¬í•¨ëœ 표가 ì œì‹œë©ë‹ˆë‹¤. 가능한 경우 AOSP ë³€ê²½ì‚¬í• ëª©ë¡ê³¼ ê°™ì´ ë¬¸ì œë¥¼ í•´ê²°í•œ 공개 변경사í•ì„ 버그 IDì— ì—°ê²°í•©ë‹ˆë‹¤. í•˜ë‚˜ì˜ ë²„ê·¸ì™€ ê´€ë ¨ëœ ë³€ê²½ì‚¬í•ì´ 여러 ê°œì¸ ê²½ìš° 추가 참조가 버그 ID 다ìŒì— 오는 ë²ˆí˜¸ì— ì—°ê²°ë©ë‹ˆë‹¤. @@ -112,7 +128,8 @@ AOSP ë²„ì „(해당하는 경우)ì´ </tr> <tr> <td>CVE-2017-13176</td> - <td>A-68341964</td> + <td><a href="https://android.googlesource.com/platform/frameworks/base/+/4afa0352d6c1046f9e9b67fbf0011bcd751fcbb5"> + A-68341964</a></td> <td>EoP</td> <td>높ìŒ</td> <td>5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> @@ -120,8 +137,8 @@ AOSP ë²„ì „(해당하는 경우)ì´ </tbody></table> <h3 id="media-framework">미디어 í”„ë ˆìž„ì›Œí¬</h3> -<p>ì´ ì„¹ì…˜ì˜ ê°€ìž¥ 심ê°í•œ 취약성으로 ì¸í•´ 특별히 ì œìž‘ëœ íŒŒì¼ì„ 사용하는 ì›ê²© 공격ìžê°€ -ê¶Œí•œì´ ì„¤ì •ëœ í”„ë¡œì„¸ìŠ¤ì˜ ì»¨í…스트 ë‚´ì—ì„œ ìž„ì˜ì˜ 코드를 +<p>ì´ ì„¹ì…˜ì˜ ê°€ìž¥ 심ê°í•œ 취약성으로 ì¸í•´ 특별히 ì œìž‘ëœ íŒŒì¼ì„ 사용하는 +ì›ê²© 공격ìžê°€ ê¶Œí•œì´ ì„¤ì •ëœ í”„ë¡œì„¸ìŠ¤ì˜ ì»¨í…스트 ë‚´ì—ì„œ ìž„ì˜ì˜ 코드를 ì‹¤í–‰í• ìˆ˜ 있습니다.</p> <table> @@ -138,109 +155,124 @@ AOSP ë²„ì „(해당하는 경우)ì´ <th>ì—…ë°ì´íŠ¸ëœ AOSP ë²„ì „</th> </tr> <tr> - <td>CVE-2017-13177</td> - <td>A-68320413</td> - <td>RCE</td> - <td>심ê°</td> - <td>5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + <td>CVE-2017-13177</td> + <td><a href="https://android.googlesource.com/platform/external/libhevc/+/b686bb2df155fd1f55220d56f38cc0033afe278c"> + A-68320413</a></td> + <td>RCE</td> + <td>심ê°</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-13178</td> - <td>A-66969281</td> - <td>RCE</td> - <td>심ê°</td> - <td>6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + <td>CVE-2017-13178</td> + <td><a href="https://android.googlesource.com/platform/frameworks/av/+/646a18fef28d19ba5beb6a2e1c00ac4c2663a10b"> + A-66969281</a></td> + <td>RCE</td> + <td>심ê°</td> + <td>6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> </tr> <tr> - <td>CVE-2017-13179</td> - <td>A-66969193</td> - <td>RCE</td> - <td>심ê°</td> - <td>6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + <td>CVE-2017-13179</td> + <td><a href="https://android.googlesource.com/platform/frameworks/av/+/47d4b33b504e14e98420943f771a9aecd6d09516"> + A-66969193</a></td> + <td>RCE</td> + <td>심ê°</td> + <td>6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> </tr> <tr> - <td>CVE-2017-13180</td> - <td>A-66969349</td> - <td>EoP</td> - <td>높ìŒ</td> - <td>6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + <td>CVE-2017-13180</td> + <td><a href="https://android.googlesource.com/platform/frameworks/av/+/cf1e36f93fc8776e3a8109149424babeee7f8382"> + A-66969349</a></td> + <td>EoP</td> + <td>높ìŒ</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-13181</td> - <td>A-67864232</td> - <td>EoP</td> - <td>높ìŒ</td> - <td>7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + <td>CVE-2017-13181</td> + <td><a href="https://android.googlesource.com/platform/frameworks/base/+/d64e9594d3d73c613010ca9fafc7af9782e9225d"> + A-67864232</a></td> + <td>EoP</td> + <td>높ìŒ</td> + <td>7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> </tr> <tr> - <td>CVE-2017-13182</td> - <td>A-67737022</td> - <td>EoP</td> - <td>높ìŒ</td> - <td>8.0, 8.1</td> + <td>CVE-2017-13182</td> + <td><a href="https://android.googlesource.com/platform/frameworks/av/+/f1652e1b9f1d2840c79b6bf784d1befe40f4799e"> + A-67737022</a></td> + <td>EoP</td> + <td>높ìŒ</td> + <td>8.0, 8.1</td> </tr> <tr> - <td>CVE-2017-13184</td> - <td>A-65483324</td> - <td>EoP</td> - <td>높ìŒ</td> - <td>8.0, 8.1</td> + <td>CVE-2017-13184</td> + <td><a href="https://android.googlesource.com/platform/frameworks/native/+/16392a119661fd1da750d4d4e8e03442578bc543"> + A-65483324</a></td> + <td>EoP</td> + <td>높ìŒ</td> + <td>8.0, 8.1</td> </tr> <tr> - <td>CVE-2017-0855</td> - <td>A-64452857</td> - <td>DoS</td> - <td>높ìŒ</td> - <td>5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0</td> + <td>CVE-2017-0855</td> + <td><a href="https://android.googlesource.com/platform/frameworks/av/+/d7d6df849cec9d0a9c1fd0d9957a1b8edef361b7"> + A-64452857</a></td> + <td>DoS</td> + <td>높ìŒ</td> + <td>5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0</td> </tr> <tr> - <td>CVE-2017-13191</td> - <td>A-64380403</td> - <td>DoS</td> - <td>높ìŒ</td> - <td>5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + <td>CVE-2017-13191</td> + <td><a href="https://android.googlesource.com/platform/external/libhevc/+/f5b2fa243b4c45a4cd885e85f49ae548ab88c264"> + A-64380403</a></td> + <td>DoS</td> + <td>높ìŒ</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-13192</td> - <td>A-64380202</td> - <td>DoS</td> - <td>높ìŒ</td> - <td>5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + <td>CVE-2017-13192</td> + <td><a href="https://android.googlesource.com/platform/external/libhevc/+/52ca619511acbd542d843df1f92f858ce13048a5"> + A-64380202</a></td> + <td>DoS</td> + <td>높ìŒ</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-13193</td> - <td>A-65718319</td> - <td>DoS</td> - <td>높ìŒ</td> - <td>5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + <td>CVE-2017-13193</td> + <td><a href="https://android.googlesource.com/platform/external/libhevc/+/b3f31e493ef6fa886989198da9787807635eaae2"> + A-65718319</a></td> + <td>DoS</td> + <td>높ìŒ</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-13195</td> - <td>A-65398821</td> - <td>DoS</td> - <td>높ìŒ</td> - <td>5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + <td>CVE-2017-13195</td> + <td><a href="https://android.googlesource.com/platform/external/libhevc/+/066e3b1f9c954d95045bc9d33d2cdc9df419784f"> + A-65398821</a></td> + <td>DoS</td> + <td>높ìŒ</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-13196</td> - <td>A-63522067</td> - <td>DoS</td> - <td>높ìŒ</td> - <td>5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + <td>CVE-2017-13196</td> + <td><a href="https://android.googlesource.com/platform/external/libhevc/+/f5b2fa243b4c45a4cd885e85f49ae548ab88c264"> + A-63522067</a></td> + <td>DoS</td> + <td>높ìŒ</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-13197</td> - <td>A-64784973</td> - <td>DoS</td> - <td>높ìŒ</td> - <td>6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + <td>CVE-2017-13197</td> + <td><a href="https://android.googlesource.com/platform/external/libhevc/+/0a714d3a14d256c6a5675d6fbd975ca26e9bc471"> + A-64784973</a></td> + <td>DoS</td> + <td>높ìŒ</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-13199</td> - <td>A-33846679</td> - <td>DoS</td> - <td>높ìŒ</td> - <td>8.0, 8.1</td> + <td>CVE-2017-13199</td> + <td><a href="https://android.googlesource.com/platform/frameworks/base/+/42b2e419b48a26d2ba599d87e3a2a02c4aa625f4"> + A-33846679</a></td> + <td>DoS</td> + <td>높ìŒ</td> + <td>8.0, 8.1</td> </tr> </tbody></table> @@ -263,32 +295,38 @@ AOSP ë²„ì „(해당하는 경우)ì´ <th>ì—…ë°ì´íŠ¸ëœ AOSP ë²„ì „</th> </tr> <tr> - <td>CVE-2017-13208</td> - <td>A-67474440</td> - <td>RCE</td> - <td>심ê°</td> - <td>5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + <td>CVE-2017-13208</td> + <td><a href="https://android.googlesource.com/platform/system/core/+/b71335264a7c3629f80b7bf1f87375c75c42d868"> + A-67474440</a></td> + <td>RCE</td> + <td>심ê°</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-13209</td> - <td>A-68217907</td> - <td>EoP</td> - <td>높ìŒ</td> - <td>8.0, 8.1</td> + <td>CVE-2017-13209</td> + <td><a href="https://android.googlesource.com/platform/system/libhidl/+/a4d0252ab5b6f6cc52a221538e1536c5b55c1fa7"> + A-68217907</a> +[<a href="https://android.googlesource.com/platform/system/tools/hidl/+/8539fc8ac94d5c92ef9df33675844ab294f68d61">2</a>] +[<a href="https://android.googlesource.com/platform/system/hwservicemanager/+/e1b4a889e8b84f5c13b76333d4de90dbe102a0de">3</a>]</td> + <td>EoP</td> + <td>높ìŒ</td> + <td>8.0, 8.1</td> </tr> <tr> - <td>CVE-2017-13210</td> - <td>A-67782345</td> - <td>EoP</td> - <td>높ìŒ</td> - <td>5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + <td>CVE-2017-13210</td> + <td><a href="https://android.googlesource.com/platform/system/media/+/e770e378dc8e2320679272234285456ca2244a62"> + A-67782345</a></td> + <td>EoP</td> + <td>높ìŒ</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-13211</td> - <td>A-65174158</td> - <td>DoS</td> - <td>높ìŒ</td> - <td>8.0</td> + <td>CVE-2017-13211</td> + <td><a href="https://android.googlesource.com/platform/system/bt/+/181144a50114c824cfe3cdfd695c11a074673a5e"> + A-65174158</a></td> + <td>DoS</td> + <td>높ìŒ</td> + <td>8.0</td> </tr> </tbody></table> @@ -333,7 +371,7 @@ AOSP ë³€ê²½ì‚¬í• ëª©ë¡ê³¼ ê°™ì´ ë¬¸ì œë¥¼ í•´ê²°í•œ 공개 변경사í•ì„ ë² <h3 id="kernel-components">ì»¤ë„ êµ¬ì„±ìš”ì†Œ</h3> <p>ì´ ì„¹ì…˜ì˜ ê°€ìž¥ 심ê°í•œ 취약성으로 ì¸í•´ 로컬 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ -ê¶Œí•œì´ ì„¤ì •ëœ í”„ë¡œì„¸ìŠ¤ ë‚´ì—ì„œ ìž„ì˜ì˜ 코드를 ì‹¤í–‰í• ìˆ˜ +ê¶Œí•œì´ ì„¤ì •ëœ í”„ë¡œì„¸ìŠ¤ì˜ ì»¨í…스트 ë‚´ì—ì„œ ìž„ì˜ì˜ 코드를 ì‹¤í–‰í• ìˆ˜ 있습니다.</p> <table> @@ -379,7 +417,7 @@ AOSP ë³€ê²½ì‚¬í• ëª©ë¡ê³¼ ê°™ì´ ë¬¸ì œë¥¼ í•´ê²°í•œ 공개 변경사í•ì„ ë² <td>A-68266545<a href="#asterisk">*</a></td> <td>ID</td> <td>높ìŒ</td> - <td>Timers</td> + <td>ê³ ì •ë°€ 타ì´ë¨¸</td> </tr> </tbody></table> @@ -437,37 +475,9 @@ AOSP ë³€ê²½ì‚¬í• ëª©ë¡ê³¼ ê°™ì´ ë¬¸ì œë¥¼ í•´ê²°í•œ 공개 변경사í•ì„ ë² </tr> </tbody></table> -<h3 id="mediatek-components">MediaTek 구성요소</h3> -<p>ì´ ì„¹ì…˜ì˜ ê°€ìž¥ 심ê°í•œ 취약성으로 ì¸í•´ 로컬 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ -ê¶Œí•œì´ ì„¤ì •ëœ í”„ë¡œì„¸ìŠ¤ ë‚´ì—ì„œ ìž„ì˜ì˜ 코드를 ì‹¤í–‰í• ìˆ˜ -있습니다.</p> - -<table> - <colgroup><col width="17%" /> - <col width="19%" /> - <col width="9%" /> - <col width="14%" /> - <col width="39%" /> - </colgroup><tbody><tr> - <th>CVE</th> - <th>참조</th> - <th>ìœ í˜•</th> - <th>심ê°ë„</th> - <th>구성요소</th> - </tr> - <tr> - <td>CVE-2017-13225</td> - <td>A-38308024<a href="#asterisk">*</a><br /> - M-ALPS03495789</td> - <td>EoP</td> - <td>높ìŒ</td> - <td>MTK 미디어</td> - </tr> -</tbody></table> - <h3 id="nvidia-components">NVIDIA 구성요소</h3> <p>ì´ ì„¹ì…˜ì˜ ê°€ìž¥ 심ê°í•œ 취약성으로 ì¸í•´ 로컬 악성 ì• í”Œë¦¬ì¼€ì´ì…˜ì´ -ê¶Œí•œì´ ì„¤ì •ëœ í”„ë¡œì„¸ìŠ¤ ë‚´ì—ì„œ ìž„ì˜ì˜ 코드를 ì‹¤í–‰í• ìˆ˜ +ê¶Œí•œì´ ì„¤ì •ëœ í”„ë¡œì„¸ìŠ¤ì˜ ì»¨í…스트 ë‚´ì—ì„œ ìž„ì˜ì˜ 코드를 ì‹¤í–‰í• ìˆ˜ 있습니다.</p> <table> @@ -534,8 +544,9 @@ QC-CR#2060780</a></td> <h3 id="qualcomm-closed-source-components">Qualcomm 비공개 소스 구성요소</h3> <p>ë‹¤ìŒ ì·¨ì•½ì„±ì€ Qualcomm êµ¬ì„±ìš”ì†Œì— ì˜í–¥ì„ 주며 Qualcomm AMSS -보안 ê²Œì‹œíŒ ë˜ëŠ” 보안 ì•ŒëžŒì— ìžì„¸ížˆ 설명ë˜ì–´ -있습니다. ì´ëŸ¬í•œ ë¬¸ì œì˜ ì‹¬ê°ë„ í‰ê°€ëŠ” Qualcommì—ì„œ ì§ì ‘ ì œê³µí•©ë‹ˆë‹¤.</p> +보안 ê²Œì‹œíŒ ë˜ëŠ” 보안 ì•Œë¦¼ì— ìžì„¸ížˆ 설명ë˜ì–´ +있습니다. ì´ëŸ¬í•œ ë¬¸ì œì˜ ì‹¬ê°ë„ í‰ê°€ëŠ” Qualcommì—ì„œ ì§ì ‘ +ì œê³µí•©ë‹ˆë‹¤.</p> <table> <colgroup><col width="17%" /> @@ -603,7 +614,8 @@ QC-CR#2060780</a></td> <h2 id="common-questions-and-answers">ì¼ë°˜ì ì¸ ì§ˆë¬¸ ë° ë‹µë³€</h2> <p> -ì´ ì„¹ì…˜ì—서는 게시íŒì„ ì½ì€ ë’¤ ì œê¸°ë 수 있는 ì¼ë°˜ì ì¸ ì§ˆë¬¸ì— ëŒ€í•œ ë‹µë³€ì„ ì œì‹œí•©ë‹ˆë‹¤. +ì´ ì„¹ì…˜ì—서는 게시íŒì„ ì½ì€ ë’¤ ì œê¸°ë 수 있는 ì¼ë°˜ì ì¸ ì§ˆë¬¸ì˜ ë‹µë³€ì„ +ì œì‹œí•©ë‹ˆë‹¤. </p> <p> <strong>1. ë‚´ 기기가 ì—…ë°ì´íŠ¸ë˜ì–´ ì´ ë¬¸ì œê°€ í•´ê²°ë˜ì—ˆëŠ”지 어떻게 ì•Œ 수 있나요? @@ -632,7 +644,8 @@ Android ë²„ì „ í™•ì¸ ë° ì—…ë°ì´íŠ¸</a>를 참조하세요. </p> <p> ì´ ê²Œì‹œíŒì—는 Android 파트너가 ëª¨ë“ Android 기기ì—ì„œ ìœ ì‚¬í•˜ê²Œ ë°œìƒí•˜ëŠ” -취약성 ë¬¸ì œì˜ ì¼ë¶€ë¥¼ ë”ìš± ë¹ ë¥´ê³ ìœ ì—°í•˜ê²Œ 해결하ë„ë¡ í•˜ê¸° 위해 ë‘ ê°€ì§€ 보안 패치 ìˆ˜ì¤€ì´ í¬í•¨ë˜ì–´ 있습니다. Android 파트너는 ì´ ê²Œì‹œíŒì— ì–¸ê¸‰ëœ ë¬¸ì œë¥¼ ëª¨ë‘ ìˆ˜ì •í•˜ê³ +취약성 ë¬¸ì œì˜ ì¼ë¶€ë¥¼ ë”ìš± ë¹ ë¥´ê³ ìœ ì—°í•˜ê²Œ 해결하기 위한 +ë‘ ê°€ì§€ 보안 패치 ìˆ˜ì¤€ì´ í¬í•¨ë˜ì–´ 있습니다. Android 파트너는 ì´ ê²Œì‹œíŒì— ì–¸ê¸‰ëœ ë¬¸ì œë¥¼ ëª¨ë‘ ìˆ˜ì •í•˜ê³ ìµœì‹ ë³´ì•ˆ 패치 ìˆ˜ì¤€ì„ ì‚¬ìš©í•˜ëŠ” ê²ƒì´ ì¢‹ìŠµë‹ˆë‹¤. </p> <ul> @@ -678,7 +691,7 @@ Android ë²„ì „ í™•ì¸ ë° ì—…ë°ì´íŠ¸</a>를 참조하세요. <td>서비스 거부</td> </tr> <tr> - <td>해당 ì—†ìŒ</td> + <td>N/A</td> <td>분류 ì—†ìŒ</td> </tr> </tbody></table> @@ -687,7 +700,8 @@ Android ë²„ì „ í™•ì¸ ë° ì—…ë°ì´íŠ¸</a>를 참조하세요. </p> <p> 취약성 ì„¸ë¶€ì •ë³´ í‘œì˜ <em>참조</em> ì—´ì— ìžˆëŠ” í•ëª©ì€ 참조 ê°’ì´ ì†í•œ -ì¡°ì§ì„ 나타내는 ì ‘ë‘어를 í¬í•¨í• 수 있습니다. +ì¡°ì§ì„ 나타내는 ì ‘ë‘어를 í¬í•¨í• 수 +있습니다. </p> <table> <colgroup><col width="25%" /> @@ -738,25 +752,40 @@ Android ê¸°ê¸°ì˜ ìµœì‹ ë³´ì•ˆ 패치 ìˆ˜ì¤€ì„ ì„ ì–¸í•˜ëŠ” ë° í•„ìš”í•©ë‹ˆë‹ ê¸°ê¸°/파트너 보안 게시íŒì— ì„¤ëª…ëœ ê²ƒê³¼ ê°™ì€ ì¶”ê°€ 보안 ì·¨ì•½ì„±ì€ ë³´ì•ˆ 패치 ìˆ˜ì¤€ì„ ì„ ì–¸í•˜ëŠ” ë° í•„ìš”í•˜ì§€ 않습니다. Android 기기 ë° ì¹©ì…‹ ì œì¡°ì—…ì²´ëŠ” -<a href="https://security.samsungmobile.com/securityUpdate.smsb">삼성</a>, <a href="https://lgsecurity.lge.com/security_updates.html">LGE</a>, ë˜ëŠ” <a href="/security/bulletin/pixel/">Pixel&hairsp;/&hairsp;Nexus</a> -보안 게시íŒê³¼ ê°™ì€ ê° ì—…ì²´ì˜ ë³´ì•ˆ 웹사ì´íŠ¸ë¥¼ 통해 ê¸°ê¸°ì˜ ë‹¤ë¥¸ ìˆ˜ì •ì‚¬í•ì´ +<a href="https://security.samsungmobile.com/securityUpdate.smsb">삼성</a>, <a href="https://lgsecurity.lge.com/security_updates.html">LGE</a> ë˜ëŠ” <a href="/security/bulletin/pixel/">Pixel&hairsp;/&hairsp;Nexus</a> +보안 게시íŒê³¼ ê°™ì€ ìžì²´ 보안 웹사ì´íŠ¸ë¥¼ 통해 ê¸°ê¸°ì˜ ë‹¤ë¥¸ ìˆ˜ì •ì‚¬í•ì´ 있는지를 설명하는 ê²ƒì´ ì¢‹ìŠµë‹ˆë‹¤. </p> <h2 id="versions">ë²„ì „</h2> <table> - <colgroup><col width="25%" /> + <colgroup><col width="15%" /> <col width="25%" /> - <col width="50%" /> + <col width="60%" /> </colgroup><tbody><tr> <th>ë²„ì „</th> <th>ë‚ ì§œ</th> - <th>ì°¸ê³ ì‚¬í•</th> + <th>ì°¸ê³ </th> </tr> <tr> <td>1.0</td> <td>2018ë…„ 1ì›” 2ì¼</td> <td>게시íŒì´ 게시ë¨</td> </tr> -</tbody></table> + <tr> + <td>1.1</td> + <td>2018ë…„ 1ì›” 3ì¼</td> + <td>게시íŒì´ ì—…ë°ì´íŠ¸ë˜ì–´ CVE-2017-13218ì— ê´€í•œ 공지사í•ì´ í¬í•¨ë¨</td> + </tr> + <tr> + <td>1.2</td> + <td>2018ë…„ 1ì›” 5ì¼</td> + <td>게시íŒì´ ìˆ˜ì •ë˜ì–´ AOSP ë§í¬ í¬í•¨ë¨</td> + </tr> + <tr> + <td>1.3</td> + <td>2018ë…„ 1ì›” 29ì¼</td> + <td>CVE-2017-13225ê°€ <a href="/security/bulletin/pixel/">Pixel / Nexus + 보안 게시íŒ</a>으로 ì´ë™í•¨</td> +</tr></tbody></table> </body></html>
\ No newline at end of file diff --git a/ko/security/bulletin/pixel/2017-10-01.html b/ko/security/bulletin/pixel/2017-10-01.html index 823c28d2..11235348 100644 --- a/ko/security/bulletin/pixel/2017-10-01.html +++ b/ko/security/bulletin/pixel/2017-10-01.html @@ -21,7 +21,8 @@ --> <p><em>2017ë…„ 10ì›” 2ì¼ ê²Œì‹œë¨ | 2017ë…„ 10ì›” 3ì¼ ì—…ë°ì´íŠ¸ë¨</em></p> -<p>Pixel&hairsp;/&hairsp;Nexus 보안 게시íŒì—서는 +<p>Pixel&hairsp;/&hairsp;Nexus +보안 게시íŒì—서는 <a href="https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices">지ì›ë˜ëŠ” Google Pixel ë° Nexus 기기</a>(Google 기기)ì— ì˜í–¥ì„ 미치는 보안 취약성 ì„¸ë¶€ì •ë³´ë¥¼ 다룹니다. Google ê¸°ê¸°ì˜ ê²½ìš° @@ -544,7 +545,8 @@ QC-CR#2016076</a></td> <p>ì´ë²ˆ 달ì—는 기능 패치는 í¬í•¨ë˜ì§€ 않았습니다.</p> <h2 id="questions">ì¼ë°˜ì ì¸ ì§ˆë¬¸ ë° ë‹µë³€</h2> -<p>ì´ ì„¹ì…˜ì—서는 게시íŒì„ ì½ì€ ë’¤ ì œê¸°ë 수 있는 ì¼ë°˜ì ì¸ ì§ˆë¬¸ì— ëŒ€í•œ ë‹µë³€ì„ ì œì‹œí•©ë‹ˆë‹¤.</p> +<p>ì´ ì„¹ì…˜ì—서는 게시íŒì„ ì½ì€ ë’¤ ì œê¸°ë 수 있는 ì¼ë°˜ì ì¸ ì§ˆë¬¸ì˜ ë‹µë³€ì„ +ì œì‹œí•©ë‹ˆë‹¤.</p> <p><strong>1. ë‚´ 기기가 ì—…ë°ì´íŠ¸ë˜ì–´ ì´ ë¬¸ì œê°€ í•´ê²°ë˜ì—ˆëŠ”지 어떻게 ì•Œ 수 있나요? </strong></p> @@ -585,14 +587,15 @@ QC-CR#2016076</a></td> <td>서비스 거부</td> </tr> <tr> - <td>해당 ì—†ìŒ</td> + <td>N/A</td> <td>분류 ì—†ìŒ</td> </tr> </tbody></table> <p><strong>3. <em>참조</em> ì—´ì˜ í•ëª©ì€ ë¬´ì—‡ì„ ì˜ë¯¸í•˜ë‚˜ìš”?</strong></p> <p>취약성 ì„¸ë¶€ì •ë³´ í‘œì˜ <em>참조</em> ì—´ì— ìžˆëŠ” í•ëª©ì€ 참조 ê°’ì´ ì†í•œ -ì¡°ì§ì„ 나타내는 ì ‘ë‘어를 í¬í•¨í• 수 있습니다.</p> +ì¡°ì§ì„ 나타내는 ì ‘ë‘어를 í¬í•¨í• 수 +있습니다.</p> <table> <colgroup><col width="25%" /> @@ -626,8 +629,10 @@ QC-CR#2016076</a></td> <p id="asterisk"><strong>4. <em>참조</em> ì—´ì—ì„œ Android 버그 ID ì˜†ì— ìžˆëŠ” * 표시는 ë¬´ì—‡ì„ ì˜ë¯¸í•˜ë‚˜ìš”?</strong></p> -<p>공개ë˜ì§€ ì•Šì€ ë¬¸ì œëŠ” <em>참조</em> ì—´ì˜ Android 버그 ID ì˜†ì— * 표시가 있습니다. ì¼ë°˜ì 으로 해당 ë¬¸ì œì˜ ì—…ë°ì´íŠ¸ëŠ” <a href="https://developers.google.com/android/nexus/drivers">Google ê°œë°œìž ì‚¬ì´íŠ¸</a>ì—ì„œ -ì œê³µí•˜ëŠ” Nexus 기기용 ìµœì‹ ë°”ì´ë„ˆë¦¬ ë“œë¼ì´ë²„ì— í¬í•¨ë˜ì–´ 있습니다.</p> +<p>공개ë˜ì§€ ì•Šì€ ë¬¸ì œëŠ” <em>참조</em> ì—´ì˜ Android 버그 ID ì˜†ì— * 표시가 +있습니다. ì¼ë°˜ì 으로 ì´ëŸ¬í•œ ë¬¸ì œì— ê´€í•œ ì—…ë°ì´íŠ¸ëŠ” <a href="https://developers.google.com/android/nexus/drivers">Google ê°œë°œìž ì‚¬ì´íŠ¸</a>ì—ì„œ +ì œê³µë˜ëŠ” Nexus 기기용 ìµœì‹ ë°”ì´ë„ˆë¦¬ ë“œë¼ì´ë²„ì— í¬í•¨ë˜ì–´ +있습니다.</p> <p id="split"> <strong>5 보안 ì·¨ì•½ì„±ì´ ì´ ê²Œì‹œíŒê³¼ Android 보안 게시íŒì— @@ -648,7 +653,7 @@ Android ê¸°ê¸°ì˜ ìµœì‹ ë³´ì•ˆ 패치 ìˆ˜ì¤€ì„ ì„ ì–¸í•˜ëŠ” ë° í•„ìš”í•©ë‹ˆë‹ </colgroup><tbody><tr> <th>ë²„ì „</th> <th>ë‚ ì§œ</th> - <th>메모</th> + <th>ì°¸ê³ </th> </tr> <tr> <td>1.0</td> diff --git a/ko/security/bulletin/pixel/2018-03-01.html b/ko/security/bulletin/pixel/2018-03-01.html new file mode 100644 index 00000000..ba333b85 --- /dev/null +++ b/ko/security/bulletin/pixel/2018-03-01.html @@ -0,0 +1,694 @@ +<html devsite><head> + <title>Pixel / Nexus 보안 게시íŒâ€”2018ë…„ 3ì›”</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>2018ë…„ 3ì›” 5ì¼ ê²Œì‹œë¨</em></p> + +<p> +Pixel&hairsp;/&hairsp;Nexus 보안 게시íŒì—서는 +<a href="https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices">지ì›ë˜ëŠ” Google Pixel ë° Nexus 기기</a>(Google 기기)ì— ì˜í–¥ì„ 미치는 +보안 취약성 ë° ê¸°ëŠ¥ ê°œì„ ì„ +ìžì„¸ížˆ 다룹니다. Google ê¸°ê¸°ì˜ ê²½ìš° +2018-03-05 보안 패치 수준 ì´ìƒì—ì„œ +ì´ ê²Œì‹œíŒì— ì–¸ê¸‰ëœ ëª¨ë“ ë¬¸ì œì™€ <a href="/security/bulletin/2018-03-01">2018ë…„ +3ì›” Android 보안 게시íŒ</a>ì˜ ëª¨ë“ ë¬¸ì œë¥¼ 해결했습니다. ê¸°ê¸°ì˜ ë³´ì•ˆ 패치 ìˆ˜ì¤€ì„ +확ì¸í•˜ëŠ” ë°©ë²•ì€ <a href="https://support.google.com/pixelphone/answer/4457705">Android +ë²„ì „ í™•ì¸ ë° ì—…ë°ì´íŠ¸</a>를 참조하세요.</p> +<p> +지ì›ë˜ëŠ” ëª¨ë“ Google 기기는 2018-03-05 패치 수준으로 +ì—…ë°ì´íŠ¸ë©ë‹ˆë‹¤. ëª¨ë“ ê³ ê°ì€ 기기ì—ì„œ ì´ ì—…ë°ì´íŠ¸ë¥¼ 수ë½í•˜ëŠ” ê²ƒì´ ì¢‹ìŠµë‹ˆë‹¤. +</p> +<p class="note"> +<strong>ì°¸ê³ :</strong> Google 기기 펌웨어 ì´ë¯¸ì§€ëŠ” +<a href="https://developers.google.com/android/nexus/images">Google ê°œë°œìž +사ì´íŠ¸</a>ì— ìžˆìŠµë‹ˆë‹¤. +</p> + +<h2 id="announcements">공지사í•</h2> +<p><a href="/security/bulletin/2018-03-01">2018ë…„ 3ì›” Android 보안 게시íŒ</a> +ì— ì„¤ëª…ëœ ë³´ì•ˆ 취약성 외ì—ë„ +Google 기기ì—는 아래 ì„¤ëª…ëœ ë³´ì•ˆ 취약성과 ê´€ë ¨ëœ íŒ¨ì¹˜ë„ +í¬í•¨ë˜ì–´ 있습니다. 파트너ì—게는 ì ì–´ë„ 1개월 ì „ì— ì´ëŸ¬í•œ ë¬¸ì œì™€ ê´€ë ¨í•´ ì•Œë¦¼ì´ ì „ì†¡ë˜ì—ˆìœ¼ë©° +ì´ëŸ¬í•œ 패치를 기기 ì—…ë°ì´íŠ¸ì˜ ì¼ë¶€ë¡œ í¬í•¨í•˜ë„ë¡ ì„ íƒí• 수 있습니다.</p> + +<h2 id="security-patches">보안 패치</h2> +<p> +ì·¨ì•½ì„±ì€ ì˜í–¥ì„ 받는 구성요소 ì•„ëž˜ì— ë¶„ë¥˜ë˜ì–´ 있습니다. 여기ì—는 +ë¬¸ì œ 설명 ë° CVE, ê´€ë ¨ 참조, +<a href="#type">취약성 ìœ í˜•</a>, +<a href="https://source.android.com/security/overview/updates-resources.html#severity">심ê°ë„</a>, +ì—…ë°ì´íŠ¸ëœ AOSP ë²„ì „(해당하는 경우)ì´ í¬í•¨ëœ 표가 ì œì‹œë©ë‹ˆë‹¤. 가능한 경우 +AOSP ë³€ê²½ì‚¬í• ëª©ë¡ê³¼ ê°™ì´ ë¬¸ì œë¥¼ í•´ê²°í•œ 공개 변경사í•ì„ +버그 IDì— ì—°ê²°í•©ë‹ˆë‹¤. í•˜ë‚˜ì˜ ë²„ê·¸ì™€ ê´€ë ¨ëœ ë³€ê²½ì‚¬í•ì´ 여러 ê°œì¸ ê²½ìš° 추가 +참조가 버그 ID 다ìŒì— 오는 ë²ˆí˜¸ì— ì—°ê²°ë©ë‹ˆë‹¤. +</p> + +<h3 id="framework">í”„ë ˆìž„ì›Œí¬</h3> + +<table> + <colgroup><col width="17%" /> + <col width="19%" /> + <col width="9%" /> + <col width="14%" /> + <col width="39%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>참조</th> + <th>ìœ í˜•</th> + <th>심ê°ë„</th> + <th>ì—…ë°ì´íŠ¸ëœ AOSP ë²„ì „</th> + </tr> + <tr> + <td>CVE-2017-13263</td> + <td>A-69383160</td> + <td>EoP</td> + <td>보통</td> + <td>8.0, 8.1</td> + </tr> +</tbody></table> + +<h3 id="media-framework">미디어 í”„ë ˆìž„ì›Œí¬</h3> + +<table> + <colgroup><col width="17%" /> + <col width="19%" /> + <col width="9%" /> + <col width="14%" /> + <col width="39%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>참조</th> + <th>ìœ í˜•</th> + <th>심ê°ë„</th> + <th>ì—…ë°ì´íŠ¸ëœ AOSP ë²„ì „</th> + </tr> + <tr> + <td rowspan="2">CVE-2017-13264</td> + <td rowspan="2">A-70294343</td> + <td>NSI</td> + <td>NSI</td> + <td>7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + </tr> + <tr> + <td>DoS</td> + <td>높ìŒ</td> + <td>6.0, 6.0.1</td> + </tr> + <tr> + <td rowspan="2">CVE-2017-13254</td> + <td rowspan="2">A-70239507</td> + <td>NSI</td> + <td>NSI</td> + <td>7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + </tr> + <tr> + <td>DoS</td> + <td>높ìŒ</td> + <td>5.1.1, 6.0, 6.0.1</td> + </tr> +</tbody></table> + +<h3 id="system">시스템</h3> + +<table> + <colgroup><col width="17%" /> + <col width="19%" /> + <col width="9%" /> + <col width="14%" /> + <col width="39%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>참조</th> + <th>ìœ í˜•</th> + <th>심ê°ë„</th> + <th>ì—…ë°ì´íŠ¸ëœ AOSP ë²„ì „</th> + </tr> + <tr> + <td>CVE-2017-13265</td> + <td>A-36232423</td> + <td>EoP</td> + <td>보통</td> + <td>7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + </tr> + <tr> + <td>CVE-2017-13266</td> + <td>A-69478941</td> + <td>EoP</td> + <td>보통</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-13268</td> + <td>A-67058064</td> + <td>ID</td> + <td>보통</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-13269</td> + <td>A-68818034</td> + <td>ID</td> + <td>보통</td> + <td>5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + </tr> +</tbody></table> + +<h3 id="kernel-components">ì»¤ë„ êµ¬ì„±ìš”ì†Œ</h3> + +<table> + <colgroup><col width="17%" /> + <col width="19%" /> + <col width="9%" /> + <col width="14%" /> + <col width="39%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>참조</th> + <th>ìœ í˜•</th> + <th>심ê°ë„</th> + <th>구성요소</th> + </tr> + <tr> + <td>CVE-2017-5754</td> + <td>A-69856074<a href="#asterisk">*</a></td> + <td>ID</td> + <td>높ìŒ</td> + <td>메모리 매핑</td> + </tr> + <tr> + <td>CVE-2017-13270</td> + <td>A-69474744<a href="#asterisk">*</a></td> + <td>EoP</td> + <td>보통</td> + <td>Mnh_sm ë“œë¼ì´ë²„</td> + </tr> + <tr> + <td>CVE-2017-13271</td> + <td>A-69006799<a href="#asterisk">*</a></td> + <td>EoP</td> + <td>보통</td> + <td>Mnh_sm ë“œë¼ì´ë²„</td> + </tr> + <tr> + <td>CVE-2017-16527</td> + <td>A-69051382<br /> +<a href="https://github.com/torvalds/linux/commit/124751d5e63c823092060074bd0abaae61aaa9c4"> +업스트림 커ë„</a></td> + <td>EoP</td> + <td>보통</td> + <td>USB 사운드 ë“œë¼ì´ë²„</td> + </tr> + <tr> + <td>CVE-2017-15649</td> + <td>A-69160446<br /> +<a href="http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=008ba2a13f2d04c947adc536d19debb8fe66f110"> +업스트림 커ë„</a> +[<a href="http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4971613c1639d8e5f102c4e797c3bf8f83a5a69e">2</a>]</td> + <td>EoP</td> + <td>보통</td> + <td>ë„¤íŠ¸ì›Œí¬ ë“œë¼ì´ë²„</td> + </tr> + <tr> + <td>CVE-2017-1000111</td> + <td>A-68806121<br /> +<a href="http://patchwork.ozlabs.org/patch/800274/">업스트림 커ë„</a></td> + <td>EoP</td> + <td>보통</td> + <td>ë„¤íŠ¸ì›Œí¬ ë“œë¼ì´ë²„</td> + </tr> +</tbody></table> + +<h3 id="nvidia-components">NVIDIA 구성요소</h3> + +<table> + <colgroup><col width="17%" /> + <col width="19%" /> + <col width="9%" /> + <col width="14%" /> + <col width="39%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>참조</th> + <th>ìœ í˜•</th> + <th>심ê°ë„</th> + <th>구성요소</th> + </tr> + <tr> + <td>CVE-2017-6287</td> + <td>A-64893264<a href="#asterisk">*</a><br /> + N-CVE-2017-6287</td> + <td>ID</td> + <td>보통</td> + <td>미디어 í”„ë ˆìž„ì›Œí¬</td> + </tr> + <tr> + <td>CVE-2017-6285</td> + <td>A-64893156<a href="#asterisk">*</a><br /> + N-CVE-2017-6285</td> + <td>ID</td> + <td>보통</td> + <td>미디어 í”„ë ˆìž„ì›Œí¬</td> + </tr> + <tr> + <td>CVE-2017-6288</td> + <td>A-65482562<a href="#asterisk">*</a><br /> + N-CVE-2017-6288</td> + <td>ID</td> + <td>보통</td> + <td>미디어 í”„ë ˆìž„ì›Œí¬</td> + </tr> +</tbody></table> + +<h3 id="qualcomm-components">Qualcomm 구성요소</h3> + +<table> + <colgroup><col width="17%" /> + <col width="19%" /> + <col width="9%" /> + <col width="14%" /> + <col width="39%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>참조</th> + <th>ìœ í˜•</th> + <th>심ê°ë„</th> + <th>구성요소</th> + </tr> + <tr> + <td>CVE-2017-18061</td> + <td>A-70237701<br /> +<a href="https://source.codeaurora.org/quic/la/kernel/msm-3.18/commit/?id=b65cf2a007e88fe86dbd6d3269682fc585a4130f"> +QC-CR#2117246</a></td> + <td>EoP</td> + <td>보통</td> + <td>Wil6210</td> + </tr> + <tr> + <td>CVE-2017-18050</td> + <td>A-70237697<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=63b57442d65dfdb4b4634ff32059b1bca8c72fb7"> +QC-CR#2119443</a></td> + <td>EoP</td> + <td>보통</td> + <td>Wma 관리</td> + </tr> + <tr> + <td>CVE-2017-18054</td> + <td>A-70237694<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=6eefc756612e39fab49ff719b3dc9b94def53396"> +QC-CR#2119432</a></td> + <td>EoP</td> + <td>보통</td> + <td>Wma</td> + </tr> + <tr> + <td>CVE-2017-18055</td> + <td>A-70237693<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=50a0554d12cff58b3ffbd51d3194304244b87023"> +QC-CR#2119430</a></td> + <td>EoP</td> + <td>보통</td> + <td>Wma</td> + </tr> + <tr> + <td>CVE-2017-18065</td> + <td>A-70237685<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=a8bc0f90ef49ea0aee90047a17772e4eebff259a"> +QC-CR#2113423</a></td> + <td>EoP</td> + <td>보통</td> + <td>Wma</td> + </tr> + <tr> + <td>CVE-2017-18066</td> + <td>A-70235107<br /> +<a href="https://source.codeaurora.org/quic/la/kernel/msm-3.18/commit/?id=ff11f44c0c10c94170f03a8698f73f7e08b74625"> +QC-CR#2107976</a></td> + <td>EoP</td> + <td>보통</td> + <td>ì „ì› ë“œë¼ì´ë²„</td> + </tr> + <tr> + <td>CVE-2017-18062</td> + <td>A-68992451<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=d7927eb7c9c2d79a3e24cddd1e9447ab98bf6700"> +QC-CR#2115375</a></td> + <td>EoP</td> + <td>보통</td> + <td>Wma</td> + </tr> + <tr> + <td>CVE-2018-3561</td> + <td>A-68870904<a href="#asterisk">*</a><br /> + QC-CR#2068569</td> + <td>EoP</td> + <td>보통</td> + <td>Diagchar</td> + </tr> + <tr> + <td>CVE-2018-3560</td> + <td>A-68664502<a href="#asterisk">*</a><br /> + QC-CR#2142216</td> + <td>EoP</td> + <td>보통</td> + <td>Qdsp6v2 사운드 ë“œë¼ì´ë²„</td> + </tr> + <tr> + <td>CVE-2017-15834</td> + <td>A-70237704<br /> +<a href="https://source.codeaurora.org/quic/la/kernel/msm-3.18/commit/?id=2e1b54e38f1516e70d9f6581c4f1ee935effb903"> +QC-CR#2111858</a></td> + <td>EoP</td> + <td>보통</td> + <td>Diagchar</td> + </tr> + <tr> + <td>CVE-2017-15833</td> + <td>A-70237702<br /> +<a href="https://source.codeaurora.org/quic/la/kernel/msm-3.10/commit/?id=51ce6aec73d80e1f1fcc9c7fa71e9c2fcbdbc0fd"> +QC-CR#2059835</a></td> + <td>EoP</td> + <td>보통</td> + <td>ì „ì› ë“œë¼ì´ë²„</td> + </tr> + <tr> + <td>CVE-2017-15831</td> + <td>A-70237687<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=31e6a657320e4299c659e3d57d38a89afe8c1ce1"> +QC-CR#2114255</a></td> + <td>EoP</td> + <td>보통</td> + <td>Wma</td> + </tr> + <tr> + <td>CVE-2017-15830</td> + <td>A-70237719<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=8a7a2a9c5d203e3395811963061c79d3bc257ebe"> +QC-CR#2120725</a></td> + <td>EoP</td> + <td>보통</td> + <td>sme ë“œë¼ì´ë²„</td> + </tr> + <tr> + <td>CVE-2017-14889</td> + <td>A-70237700<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=e11e9dc8298dc0632050cacce96e9652d017f755"> +QC-CR#2119803</a></td> + <td>EoP</td> + <td>보통</td> + <td>Wma</td> + </tr> + <tr> + <td>CVE-2017-14887</td> + <td>A-70237715<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=4ce28e7c85f89e2c3555ec840b6adda47bd5dab0"> +QC-CR#2119673</a></td> + <td>EoP</td> + <td>보통</td> + <td>WLAN</td> + </tr> + <tr> + <td>CVE-2017-14879</td> + <td>A-63851638<a href="#asterisk">*</a><br /> + QC-CR#2056307</td> + <td>EoP</td> + <td>보통</td> + <td>IPA</td> + </tr> + <tr> + <td>CVE-2017-11082</td> + <td>A-66937387<br /> +<a href="https://www.codeaurora.org/gitweb/quic/la/?p=kernel/msm-3.10.git;a=commit;h=2d4f8cd8d11f8fb1491a20d7e316cc0fd03eeb59"> +QC-CR#2071560</a></td> + <td>EoP</td> + <td>보통</td> + <td>WLAN</td> + </tr> + <tr> + <td>CVE-2017-11074</td> + <td>A-68940798<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/prima/commit/?id=f5ae7b35c90f14b7e66b3a91d4fb247563a8a22b"> +QC-CR#2049138</a></td> + <td>EoP</td> + <td>보통</td> + <td>WLAN</td> + </tr> + <tr> + <td>CVE-2017-18052</td> + <td>A-70237712<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=c04c4870bd86a5f878553d7acf207388f3d6c3bd"> +QC-CR#2119439</a></td> + <td>ID</td> + <td>보통</td> + <td>WLAN</td> + </tr> + <tr> + <td>CVE-2017-18057</td> + <td>A-70237709<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=24d41d2bd3d98325b3800345f4ba27a334b3894b"> +QC-CR#2119403</a></td> + <td>ID</td> + <td>보통</td> + <td>WLAN</td> + </tr> + <tr> + <td>CVE-2017-18059</td> + <td>A-70237708<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=217705da7726002ffe61dad51a6c9cc97c52f649"> +QC-CR#2119399</a></td> + <td>ID</td> + <td>보통</td> + <td>WLAN</td> + </tr> + <tr> + <td>CVE-2017-18060</td> + <td>A-70237707<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=f3d81bd0b3cb992c214d94196b33168b02589c6b"> +QC-CR#2119394</a></td> + <td>ID</td> + <td>보통</td> + <td>WLAN</td> + </tr> + <tr> + <td>CVE-2017-18051</td> + <td>A-70237696<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=38fba6a9f6ca3c7bf0c4c1bd84fa2b89fbcaeb93"> +QC-CR#2119442</a></td> + <td>ID</td> + <td>보통</td> + <td>WLAN</td> + </tr> + <tr> + <td>CVE-2017-18053</td> + <td>A-70237695<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=da1c6e996ac7635c202296e31118f088f9427947"> +QC-CR#2119434</a></td> + <td>ID</td> + <td>보통</td> + <td>WLAN</td> + </tr> + <tr> + <td>CVE-2017-18058</td> + <td>A-70237690<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=d6d42a10d4abf09299cdfacdd8aed5c26731b5ff"> +QC-CR#2119401</a></td> + <td>ID</td> + <td>보통</td> + <td>WLAN</td> + </tr> + <tr> + <td>CVE-2017-15855</td> + <td>A-38232131<a href="#asterisk">*</a><br /> + QC-CR#2139514</td> + <td>ID</td> + <td>보통</td> + <td>Camera_v2 ë“œë¼ì´ë²„</td> + </tr> + <tr> + <td>CVE-2017-15814</td> + <td>A-64836865<a href="#asterisk">*</a><br /> + QC-CR#2092793</td> + <td>ID</td> + <td>보통</td> + <td>Camera_v2 ë“œë¼ì´ë²„</td> + </tr> +</tbody></table> + +<h2 id="functional-updates">기능 ì—…ë°ì´íŠ¸</h2> +<p> +ë‹¤ìŒ ì—…ë°ì´íŠ¸ëŠ” ì˜í–¥ì„ ë°›ì€ Pixel 기기ì—ì„œ Pixel ê¸°ê¸°ì˜ ë³´ì•ˆê³¼ +ê´€ë ¨ë˜ì§€ ì•Šì€ ê¸°ëŠ¥ ë¬¸ì œë¥¼ 해결하기 위해 í¬í•¨ë˜ì—ˆìŠµë‹ˆë‹¤. í‘œì—는 블루투스나 +ëª¨ë°”ì¼ ë°ì´í„° 등 ì˜í–¥ì„ ë°›ì€ ì¹´í…Œê³ ë¦¬ ë° ë¬¸ì œ 요약 등 ê´€ë ¨ 참조 사í•ì´ +í¬í•¨ë˜ì–´ 있습니다. +</p> + +<table> + <tbody><tr> + <th>참조</th> + <th>ì¹´í…Œê³ ë¦¬</th> + <th>ê°œì„ ì‚¬í•</th> + <th>기기</th> + </tr> + <tr> + <td>A-70491468</td> + <td>성능</td> + <td>지문으로 ìž ê¸ˆ í•´ì œ ì‹œ ì ˆì „ 모드 í•´ì œ 성능 ê°œì„ </td> + <td>Pixel 2, Pixel 2 XL</td> + </tr> + <tr> + <td>A-69307875</td> + <td>오디오</td> + <td>ë™ì˜ìƒ 녹화 ì‹œ 오디오 성능 ê°œì„ </td> + <td>Pixel 2 XL</td> + </tr> + <tr> + <td>A-70641186</td> + <td>ë³´ê³ ì„œ</td> + <td>오류 ë³´ê³ ê°œì„ </td> + <td>Pixel 2, Pixel 2 XL</td> + </tr> +</tbody></table> + +<h2 id="common-questions-and-answers">ì¼ë°˜ì ì¸ ì§ˆë¬¸ ë° ë‹µë³€</h2> +<p> +ì´ ì„¹ì…˜ì—서는 게시íŒì„ ì½ì€ ë’¤ ì œê¸°ë 수 있는 ì¼ë°˜ì ì¸ ì§ˆë¬¸ì˜ ë‹µë³€ì„ +ì œì‹œí•©ë‹ˆë‹¤. +</p> +<p> +<strong>1. ë‚´ 기기가 ì—…ë°ì´íŠ¸ë˜ì–´ ì´ ë¬¸ì œê°€ í•´ê²°ë˜ì—ˆëŠ”지 어떻게 ì•Œ 수 있나요? +</strong> +</p> +<p> +2018-03-05 보안 패치 수준 ë° ê·¸ ì´ì „ì˜ ëª¨ë“ íŒ¨ì¹˜ 수준과 ê´€ë ¨ëœ +ëª¨ë“ ë¬¸ì œëŠ” 2018-03-05 보안 패치 수준 ì´ìƒì—ì„œ í•´ê²°ë˜ì—ˆìŠµë‹ˆë‹¤. ê¸°ê¸°ì˜ ë³´ì•ˆ 패치 ìˆ˜ì¤€ì„ í™•ì¸í•˜ëŠ” +ë°©ë²•ì„ +ì•Œì•„ë³´ë ¤ë©´ <a href="https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices">Pixel ë° Nexus ì—…ë°ì´íŠ¸ ì¼ì •</a>ì˜ +안내를 참조하세요. +</p> +<p id="type"> +<strong>2. <em>ìœ í˜•</em> ì—´ì˜ í•ëª©ì€ ë¬´ì—‡ì„ ì˜ë¯¸í•˜ë‚˜ìš”?</strong> +</p> +<p> +취약성 ì„¸ë¶€ì •ë³´ í‘œì˜ <em>ìœ í˜•</em> ì—´ì— ìžˆëŠ” í•ëª©ì€ +보안 취약성 분류를 참조합니다. +</p> +<table> + <colgroup><col width="25%" /> + <col width="75%" /> + </colgroup><tbody><tr> + <th>약어</th> + <th>ì •ì˜</th> + </tr> + <tr> + <td>RCE</td> + <td>ì›ê²© 코드 실행</td> + </tr> + <tr> + <td>EoP</td> + <td>권한 승격</td> + </tr> + <tr> + <td>ID</td> + <td>ì •ë³´ 공개</td> + </tr> + <tr> + <td>DoS</td> + <td>서비스 거부</td> + </tr> + <tr> + <td>N/A</td> + <td>분류 ì—†ìŒ</td> + </tr> +</tbody></table> +<p> +<strong>3. <em>참조</em> ì—´ì˜ í•ëª©ì€ ë¬´ì—‡ì„ ì˜ë¯¸í•˜ë‚˜ìš”?</strong> +</p> +<p> +취약성 ì„¸ë¶€ì •ë³´ í‘œì˜ <em>참조</em> ì—´ì— ìžˆëŠ” í•ëª©ì€ 참조 ê°’ì´ ì†í•œ +ì¡°ì§ì„ 나타내는 ì ‘ë‘어를 í¬í•¨í• 수 +있습니다. +</p> +<table> + <colgroup><col width="25%" /> + <col width="75%" /> + </colgroup><tbody><tr> + <th>ì ‘ë‘ì–´</th> + <th>참조</th> + </tr> + <tr> + <td>A-</td> + <td>Android 버그 ID</td> + </tr> + <tr> + <td>QC-</td> + <td>Qualcomm 참조 번호</td> + </tr> + <tr> + <td>M-</td> + <td>MediaTek 참조 번호</td> + </tr> + <tr> + <td>N-</td> + <td>NVIDIA 참조 번호</td> + </tr> + <tr> + <td>B-</td> + <td>Broadcom 참조 번호</td> + </tr> +</tbody></table> +<p id="asterisk"> +<strong>4. <em>참조</em> ì—´ì—ì„œ Android 버그 ID ì˜†ì— ìžˆëŠ” * 표시는 +ë¬´ì—‡ì„ ì˜ë¯¸í•˜ë‚˜ìš”?</strong> +</p> +<p> +공개ë˜ì§€ ì•Šì€ ë¬¸ì œëŠ” <em>참조</em> ì—´ì˜ Android 버그 ID ì˜†ì— * 표시가 +있습니다. ì¼ë°˜ì 으로 ì´ëŸ¬í•œ ë¬¸ì œì— ê´€í•œ ì—…ë°ì´íŠ¸ëŠ” <a href="https://developers.google.com/android/nexus/drivers">Google ê°œë°œìž ì‚¬ì´íŠ¸</a>ì—ì„œ +ì œê³µë˜ëŠ” Nexus 기기용 ìµœì‹ ë°”ì´ë„ˆë¦¬ ë“œë¼ì´ë²„ì— í¬í•¨ë˜ì–´ +있습니다. +</p> +<p> +<strong>5 보안 ì·¨ì•½ì„±ì´ ì´ ê²Œì‹œíŒê³¼ Android 보안 게시íŒì— ë‚˜ë‰˜ì–´ì ¸ 있는 ì´ìœ ê°€ +무엇ì¸ê°€ìš”?</strong> +</p> +<p> +Android 보안 게시íŒì— 설명ë˜ì–´ 있는 보안 ì·¨ì•½ì„±ì€ +Android ê¸°ê¸°ì˜ ìµœì‹ ë³´ì•ˆ 패치 ìˆ˜ì¤€ì„ ì„ ì–¸í•˜ëŠ” ë° +필요합니다. ì´ ê²Œì‹œíŒì— ì„¤ëª…ëœ ê²ƒê³¼ ê°™ì€ ì¶”ê°€ì ì¸ ë³´ì•ˆ ì·¨ì•½ì„±ì€ +보안 패치 ìˆ˜ì¤€ì„ ì„ ì–¸í•˜ëŠ” ë° í•„ìš”í•˜ì§€ 않습니다. +</p> +<h2 id="versions">ë²„ì „</h2> +<table> + <colgroup><col width="25%" /> + <col width="25%" /> + <col width="50%" /> + </colgroup><tbody><tr> + <th>ë²„ì „</th> + <th>ë‚ ì§œ</th> + <th>ì°¸ê³ </th> + </tr> + <tr> + <td>1.0</td> + <td>2018ë…„ 3ì›” 5ì¼</td> + <td>게시íŒì´ 게시ë¨</td> + </tr> +</tbody></table> + +</body></html>
\ No newline at end of file diff --git a/ko/security/bulletin/pixel/2018.html b/ko/security/bulletin/pixel/2018.html index 5f020470..4d0336a5 100644 --- a/ko/security/bulletin/pixel/2018.html +++ b/ko/security/bulletin/pixel/2018.html @@ -37,17 +37,43 @@ <th>보안 패치 수준</th> </tr> <tr> - <td><a href="/security/bulletin/pixel/2018-01-01.html">2018ë…„ 1ì›”</a></td> + <td><a href="/security/bulletin/pixel/2018-03-01.html">2018ë…„ 3ì›”</a></td> <td>출시 ì˜ˆì • <!-- - <a href="/security/bulletin/pixel/2018-01-01.html">English</a> / - <a href="/security/bulletin/pixel/2018-01-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/pixel/2018-01-01.html?hl=ko">í•œêµì–´</a> / - <a href="/security/bulletin/pixel/2018-01-01.html?hl=ru">руÌÑÑкий</a> / - <a href="/security/bulletin/pixel/2018-01-01.html?hl=zh-cn">ä¸æ–‡ (ä¸å›½)</a> / - <a href="/security/bulletin/pixel/2018-01-01.html?hl=zh-tw">ä¸æ–‡ (å°ç£)</a> + <a href="/security/bulletin/pixel/2018-03-01.html">English</a> / + <a href="/security/bulletin/pixel/2018-03-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/pixel/2018-03-01.html?hl=ko">í•œêµì–´</a> / + <a href="/security/bulletin/pixel/2018-03-01.html?hl=ru">руÌÑÑкий</a> / + <a href="/security/bulletin/pixel/2018-03-01.html?hl=zh-cn">ä¸æ–‡ (ä¸å›½)</a> / + <a href="/security/bulletin/pixel/2018-03-01.html?hl=zh-tw">ä¸æ–‡ (å°ç£)</a> --> </td> + <td>2018ë…„ 3ì›”</td> + <td>2018-03-05</td> + </tr> + <tr> + <td><a href="/security/bulletin/pixel/2018-02-01.html">2018ë…„ 2ì›”</a></td> + <td> + <a href="/security/bulletin/pixel/2018-02-01.html">í•œêµì–´</a> / + <a href="/security/bulletin/pixel/2018-02-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/pixel/2018-02-01.html?hl=ko">English</a> / + <a href="/security/bulletin/pixel/2018-02-01.html?hl=ru">руÌÑÑкий</a> / + <a href="/security/bulletin/pixel/2018-02-01.html?hl=zh-cn">ä¸æ–‡Â (ä¸å›½)</a> / + <a href="/security/bulletin/pixel/2018-02-01.html?hl=zh-tw">ä¸æ–‡Â (å°ç£)</a> + </td> + <td>2018ë…„ 2ì›”</td> + <td>2018-02-05</td> + </tr> + <tr> + <td><a href="/security/bulletin/pixel/2018-01-01.html">2018ë…„ 1ì›”</a></td> + <td> + <a href="/security/bulletin/pixel/2018-01-01.html">í•œêµì–´</a> / + <a href="/security/bulletin/pixel/2018-01-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/pixel/2018-01-01.html?hl=ko">English</a> / + <a href="/security/bulletin/pixel/2018-01-01.html?hl=ru">руÌÑÑкий</a> / + <a href="/security/bulletin/pixel/2018-01-01.html?hl=zh-cn">ä¸æ–‡Â (ä¸å›½)</a> / + <a href="/security/bulletin/pixel/2018-01-01.html?hl=zh-tw">ä¸æ–‡Â (å°ç£)</a> + </td> <td>2018ë…„ 1ì›”</td> <td>2018-01-05</td> </tr> diff --git a/ru/security/bulletin/2015-12-01.html b/ru/security/bulletin/2015-12-01.html index f42d05f5..ff6f478a 100644 --- a/ru/security/bulletin/2015-12-01.html +++ b/ru/security/bulletin/2015-12-01.html @@ -100,7 +100,7 @@ mediaserver.</p> <th>CVE</th> <th>Ошибки Ñо ÑÑылками на AOSP</th> <th>Уровень ÑерьезноÑти</th> - <th>ВерÑии, получившие обновление ÑиÑтемы безопаÑноÑти</th> + <th>Обновленные верÑии</th> <th>Дата ÑÐ¾Ð¾Ð±Ñ‰ÐµÐ½Ð¸Ñ Ð¾Ð± ошибке</th> </tr> <tr> @@ -138,17 +138,13 @@ mediaserver.</p> <h3 id="remote_code_execution_vulnerability_in_skia">Удаленное выполнение кода через Skia</h3> -<p>УÑзвимоÑÑ‚ÑŒ Skia позволÑет во Ð²Ñ€ÐµÐ¼Ñ Ð¾Ð±Ñ€Ð°Ð±Ð¾Ñ‚ÐºÐ¸ Ñпециально Ñозданного медиафайла -нарушить целоÑтноÑÑ‚ÑŒ информации в памÑти и удаленно выполнить код -в привилегированном процеÑÑе. УÑзвимоÑти приÑвоен критичеÑкий уровень, -поÑкольку она позволÑет удаленно выполнÑÑ‚ÑŒ код на пораженном уÑтройÑтве (например, при работе Ñ Ñлектронной почтой, проÑмотре Ñайтов в Интернете -или обработке медиафайлов MMS).</p> +<p>УÑзвимоÑÑ‚ÑŒ позволÑет во Ð²Ñ€ÐµÐ¼Ñ Ð¾Ð±Ñ€Ð°Ð±Ð¾Ñ‚ÐºÐ¸ Ñпециально Ñозданного медиафайла нарушить целоÑтноÑÑ‚ÑŒ информации в памÑти и удаленно выполнить код в привилегированном процеÑÑе. Проблеме приÑвоен критичеÑкий уровень, поÑкольку из-за нее можно удаленно выполнÑÑ‚ÑŒ код на пораженном уÑтройÑтве (например, при проÑмотре Ñайтов в Интернете, обработке медиафайлов MMS и работе Ñ Ñлектронной почтой).</p> <table> <tbody><tr> <th>CVE</th> <th>Ошибки Ñо ÑÑылками на AOSP</th> <th>Уровень ÑерьезноÑти</th> - <th>ВерÑии, получившие обновление ÑиÑтемы безопаÑноÑти</th> + <th>Обновленные верÑии</th> <th>Дата ÑÐ¾Ð¾Ð±Ñ‰ÐµÐ½Ð¸Ñ Ð¾Ð± ошибке</th> </tr> <tr> @@ -171,7 +167,7 @@ mediaserver.</p> <th>CVE</th> <th>Ошибки Ñо ÑÑылками на AOSP</th> <th>Уровень ÑерьезноÑти</th> - <th>ВерÑии, получившие обновление ÑиÑтемы безопаÑноÑти</th> + <th>Обновленные верÑии</th> <th>Дата ÑÐ¾Ð¾Ð±Ñ‰ÐµÐ½Ð¸Ñ Ð¾Ð± ошибке</th> </tr> <tr> @@ -198,7 +194,7 @@ mediaserver.</p> <th>CVE</th> <th>Ошибки Ñо ÑÑылками на AOSP</th> <th>Уровень ÑерьезноÑти</th> - <th>ВерÑии, получившие обновление ÑиÑтемы безопаÑноÑти</th> + <th>Обновленные верÑии</th> <th>Дата ÑÐ¾Ð¾Ð±Ñ‰ÐµÐ½Ð¸Ñ Ð¾Ð± ошибке</th> </tr> <tr> @@ -234,7 +230,7 @@ mediaserver.</p> <th>CVE</th> <th>Ошибка </th> <th>Уровень ÑерьезноÑти</th> - <th>ВерÑии, получившие обновление ÑиÑтемы безопаÑноÑти</th> + <th>Обновленные верÑии</th> <th>Дата ÑÐ¾Ð¾Ð±Ñ‰ÐµÐ½Ð¸Ñ Ð¾Ð± ошибке</th> </tr> <tr> @@ -257,7 +253,7 @@ mediaserver.</p> <th>CVE</th> <th>Ошибки Ñо ÑÑылками на AOSP</th> <th>Уровень ÑерьезноÑти</th> - <th>ВерÑии, получившие обновление ÑиÑтемы безопаÑноÑти</th> + <th>Обновленные верÑии</th> <th>Дата ÑÐ¾Ð¾Ð±Ñ‰ÐµÐ½Ð¸Ñ Ð¾Ð± ошибке</th> </tr> <tr> @@ -286,7 +282,7 @@ mediaserver.</p> <th>CVE</th> <th>Ошибки Ñо ÑÑылками на AOSP</th> <th>Уровень ÑерьезноÑти</th> - <th>ВерÑии, получившие обновление ÑиÑтемы безопаÑноÑти</th> + <th>Обновленные верÑии</th> <th>Дата ÑÐ¾Ð¾Ð±Ñ‰ÐµÐ½Ð¸Ñ Ð¾Ð± ошибке</th> </tr> <tr> @@ -302,13 +298,13 @@ mediaserver.</p> <p>УÑзвимоÑÑ‚ÑŒ библиотеки фреймворков Android позволÑет обойти защиту, предотвращающую атаки на платформу, и раÑкрыть конфиденциальную -информацию. Проблеме приÑвоен выÑокий уровень ÑерьезноÑти, поÑкольку Ñ ÐµÐµ помощью можно также получить разрешениÑ, недоÑтупные Ñторонним приложениÑм (например, <a href="http://developer.android.com/guide/topics/manifest/permission-element.html#plevel">Signature</a> и <a href="http://developer.android.com/guide/topics/manifest/permission-element.html#plevel">SignatureOrSystem</a>).</p> +информацию. Проблеме приÑвоен выÑокий уровень ÑерьезноÑти, поÑкольку из-за нее можно также получить разрешениÑ, недоÑтупные Ñторонним приложениÑм (например, <a href="http://developer.android.com/guide/topics/manifest/permission-element.html#plevel">Signature</a> и <a href="http://developer.android.com/guide/topics/manifest/permission-element.html#plevel">SignatureOrSystem</a>).</p> <table> <tbody><tr> <th>CVE</th> <th>Ошибки Ñо ÑÑылками на AOSP</th> <th>Уровень ÑерьезноÑти</th> - <th>ВерÑии, получившие обновление ÑиÑтемы безопаÑноÑти</th> + <th>Обновленные верÑии</th> <th>Дата ÑÐ¾Ð¾Ð±Ñ‰ÐµÐ½Ð¸Ñ Ð¾Ð± ошибке</th> </tr> <tr> @@ -330,7 +326,7 @@ mediaserver.</p> <th>CVE</th> <th>Ошибки Ñо ÑÑылками на AOSP</th> <th>Уровень ÑерьезноÑти</th> - <th>ВерÑии, получившие обновление ÑиÑтемы безопаÑноÑти</th> + <th>Обновленные верÑии</th> <th>Дата ÑÐ¾Ð¾Ð±Ñ‰ÐµÐ½Ð¸Ñ Ð¾Ð± ошибке</th> </tr> <tr> @@ -351,7 +347,7 @@ mediaserver.</p> <th>CVE</th> <th>Ошибки Ñо ÑÑылками на AOSP</th> <th>Уровень ÑерьезноÑти</th> - <th>ВерÑии, получившие обновление ÑиÑтемы безопаÑноÑти</th> + <th>Обновленные верÑии</th> <th>Дата ÑÐ¾Ð¾Ð±Ñ‰ÐµÐ½Ð¸Ñ Ð¾Ð± ошибке</th> </tr> <tr> @@ -374,7 +370,7 @@ mediaserver.</p> <th>CVE</th> <th>Ошибки Ñо ÑÑылками на AOSP</th> <th>Уровень ÑерьезноÑти</th> - <th>ВерÑии, получившие обновление ÑиÑтемы безопаÑноÑти</th> + <th>Обновленные верÑии</th> <th>Дата ÑÐ¾Ð¾Ð±Ñ‰ÐµÐ½Ð¸Ñ Ð¾Ð± ошибке</th> </tr> <tr> @@ -409,7 +405,7 @@ mediaserver.</p> <th>CVE</th> <th>Ошибки Ñо ÑÑылками на AOSP</th> <th>Уровень ÑерьезноÑти</th> - <th>ВерÑии, получившие обновление ÑиÑтемы безопаÑноÑти</th> + <th>Обновленные верÑии</th> <th>Дата ÑÐ¾Ð¾Ð±Ñ‰ÐµÐ½Ð¸Ñ Ð¾Ð± ошибке</th> </tr> <tr> @@ -431,7 +427,7 @@ mediaserver.</p> <th>CVE</th> <th>Ошибки Ñо ÑÑылками на AOSP</th> <th>Уровень ÑерьезноÑти</th> - <th>ВерÑии, получившие обновление ÑиÑтемы безопаÑноÑти</th> + <th>Обновленные верÑии</th> <th>Дата ÑÐ¾Ð¾Ð±Ñ‰ÐµÐ½Ð¸Ñ Ð¾Ð± ошибке</th> </tr> <tr> @@ -452,7 +448,7 @@ mediaserver.</p> <th>CVE</th> <th>Ошибки Ñо ÑÑылками на AOSP</th> <th>Уровень ÑерьезноÑти</th> - <th>ВерÑии, получившие обновление ÑиÑтемы безопаÑноÑти</th> + <th>Обновленные верÑии</th> <th>Дата ÑÐ¾Ð¾Ð±Ñ‰ÐµÐ½Ð¸Ñ Ð¾Ð± ошибке</th> </tr> <tr> @@ -473,7 +469,7 @@ mediaserver.</p> <th>CVE</th> <th>Ошибки Ñо ÑÑылками на AOSP</th> <th>Уровень ÑерьезноÑти</th> - <th>ВерÑии, получившие обновление ÑиÑтемы безопаÑноÑти</th> + <th>Обновленные верÑии</th> <th>Дата ÑÐ¾Ð¾Ð±Ñ‰ÐµÐ½Ð¸Ñ Ð¾Ð± ошибке</th> </tr> <tr> @@ -494,7 +490,7 @@ mediaserver.</p> <th>CVE</th> <th>Ошибки Ñо ÑÑылками на AOSP</th> <th>Уровень ÑерьезноÑти</th> - <th>ВерÑии, получившие обновление ÑиÑтемы безопаÑноÑти</th> + <th>Обновленные верÑии</th> <th>Дата ÑÐ¾Ð¾Ð±Ñ‰ÐµÐ½Ð¸Ñ Ð¾Ð± ошибке</th> </tr> <tr> diff --git a/ru/security/bulletin/2016-07-01.html b/ru/security/bulletin/2016-07-01.html index 8da4bd08..dae33788 100644 --- a/ru/security/bulletin/2016-07-01.html +++ b/ru/security/bulletin/2016-07-01.html @@ -96,14 +96,8 @@ <h3 id="remote-code-execution-vulnerability-in-mediaserver"> Удаленное выполнение кода через mediaserver</h3> -<p>УÑзвимоÑÑ‚ÑŒ позволÑет злоумышленнику нарушить целоÑтноÑÑ‚ÑŒ информации -в памÑти при обработке медиафайлов и данных в Ñпециально Ñозданном файле. Проблеме приÑвоен критичеÑкий уровень ÑерьезноÑти из-за возможноÑти -удаленного Ð²Ñ‹Ð¿Ð¾Ð»Ð½ÐµÐ½Ð¸Ñ ÐºÐ¾Ð´Ð° в контекÑте процеÑÑа mediaserver. У него еÑÑ‚ÑŒ доÑтуп -к аудио- и видеопотокам, а также к привилегиÑм, закрытым Ð´Ð»Ñ Ñторонних -приложений.</p> -<p>УÑÐ·Ð²Ð¸Ð¼Ð°Ñ Ñ„ÑƒÐ½ÐºÑ†Ð¸Ñ ÑвлÑетÑÑ Ð¾Ñновной ÑоÑтавлÑющей ОС. Многие Ð¿Ñ€Ð¸Ð»Ð¾Ð¶ÐµÐ½Ð¸Ñ -позволÑÑŽÑ‚ контенту, оÑобенно MMS-ÑообщениÑм и воÑпроизводимым -в браузере медиафайлам, диÑтанционно обращатьÑÑ Ðº ней.</p> +<p>УÑзвимоÑÑ‚ÑŒ позволÑет злоумышленнику Ñ Ð¿Ð¾Ð¼Ð¾Ñ‰ÑŒÑŽ Ñпециально Ñозданного файла нарушить целоÑтноÑÑ‚ÑŒ информации в памÑти при обработке медиафайлов и данных. Проблеме приÑвоен критичеÑкий уровень ÑерьезноÑти из-за возможноÑти удаленного Ð²Ñ‹Ð¿Ð¾Ð»Ð½ÐµÐ½Ð¸Ñ ÐºÐ¾Ð´Ð° в контекÑте процеÑÑа mediaserver. У него еÑÑ‚ÑŒ доÑтуп к аудио- и видеопотокам, а также к привилегиÑм, закрытым Ð´Ð»Ñ Ñторонних приложений.</p> +<p>УÑÐ·Ð²Ð¸Ð¼Ð°Ñ Ñ„ÑƒÐ½ÐºÑ†Ð¸Ñ ÑвлÑетÑÑ Ð¾Ñновной ÑоÑтавлÑющей ОС. Многие Ð¿Ñ€Ð¸Ð»Ð¾Ð¶ÐµÐ½Ð¸Ñ Ð¿Ð¾Ð·Ð²Ð¾Ð»ÑÑŽÑ‚ контенту, оÑобенно MMS-ÑообщениÑм и воÑпроизводимым в браузере медиафайлам, диÑтанционно обращатьÑÑ Ðº ней.</p> <table> <colgroup><col width="19%" /> @@ -951,8 +945,7 @@ <h3 id="elevation-of-privilege-vulnerability-in-qualcomm-gpu-driver"> Повышение привилегий через драйвер Qualcomm Ð´Ð»Ñ Ð³Ñ€Ð°Ñ„Ð¸Ñ‡ÐµÑкого процеÑÑора</h3> -<p>УÑзвимоÑÑ‚ÑŒ позволÑет локальному вредоноÑному ПО выполнÑÑ‚ÑŒ произвольный -код в контекÑте Ñдра. Ей приÑвоен критичеÑкий уровень ÑерьезноÑти, поÑкольку из-за нее нарушаетÑÑ Ñ€Ð°Ð±Ð¾Ñ‚Ð° ÑиÑтемы безопаÑноÑти. Возможно, Ð´Ð»Ñ ÑƒÑÑ‚Ñ€Ð°Ð½ÐµÐ½Ð¸Ñ Ð¿Ñ€Ð¾Ð±Ð»ÐµÐ¼Ñ‹ потребуетÑÑ Ð¿ÐµÑ€ÐµÑƒÑтановить ОС.</p> +<p>УÑзвимоÑÑ‚ÑŒ позволÑет локальному вредоноÑному ПО выполнÑÑ‚ÑŒ произвольный код в контекÑте Ñдра. Ей приÑвоен критичеÑкий уровень ÑерьезноÑти, поÑкольку из-за нее нарушаетÑÑ Ñ€Ð°Ð±Ð¾Ñ‚Ð° ÑиÑтемы безопаÑноÑти. Возможно, Ð´Ð»Ñ ÑƒÑÑ‚Ñ€Ð°Ð½ÐµÐ½Ð¸Ñ Ð¿Ñ€Ð¾Ð±Ð»ÐµÐ¼Ñ‹ потребуетÑÑ Ð¿ÐµÑ€ÐµÑƒÑтановить ОС.</p> <table> <colgroup><col width="19%" /> @@ -1494,8 +1487,7 @@ <h3 id="elevation-of-privilege-vulnerability-in-qualcomm-wi-fi-driver"> Повышение привилегий через Wi-Fi-драйвер Qualcomm</h3> -<p>УÑзвимоÑÑ‚ÑŒ позволÑет локальному вредоноÑному ПО выполнÑÑ‚ÑŒ произвольный -код в контекÑте Ñдра. Проблеме приÑвоен выÑокий уровень ÑерьезноÑти, поÑкольку уÑзвимоÑÑ‚ÑŒ требует Ñначала нарушить защиту привилегированного процеÑÑа.</p> +<p>УÑзвимоÑÑ‚ÑŒ позволÑет локальному вредоноÑному ПО выполнÑÑ‚ÑŒ произвольный код в контекÑте Ñдра. Проблеме приÑвоен выÑокий уровень ÑерьезноÑти, поÑкольку уÑзвимоÑÑ‚ÑŒ требует Ñначала нарушить защиту привилегированного процеÑÑа.</p> <table> <colgroup><col width="19%" /> @@ -1522,8 +1514,7 @@ <h3 id="elevation-of-privilege-vulnerability-in-qualcomm-camera-driver"> Повышение привилегий через драйвер Qualcomm Ð´Ð»Ñ ÐºÐ°Ð¼ÐµÑ€Ñ‹</h3> -<p>УÑзвимоÑÑ‚ÑŒ позволÑет локальному вредоноÑному ПО выполнÑÑ‚ÑŒ произвольный -код в контекÑте Ñдра. Проблеме приÑвоен выÑокий уровень ÑерьезноÑти, поÑкольку уÑзвимоÑÑ‚ÑŒ требует Ñначала нарушить защиту привилегированного процеÑÑа.</p> +<p>УÑзвимоÑÑ‚ÑŒ позволÑет локальному вредоноÑному ПО выполнÑÑ‚ÑŒ произвольный код в контекÑте Ñдра. Проблеме приÑвоен выÑокий уровень ÑерьезноÑти, поÑкольку уÑзвимоÑÑ‚ÑŒ требует Ñначала нарушить защиту привилегированного процеÑÑа.</p> <table> <colgroup><col width="19%" /> @@ -1552,8 +1543,7 @@ <h3 id="elevation-of-privilege-vulnerability-in-nvidia-camera-driver"> Повышение привилегий через драйвер NVIDIA Ð´Ð»Ñ ÐºÐ°Ð¼ÐµÑ€Ñ‹</h3> <p>УÑзвимоÑÑ‚ÑŒ позволÑет локальному вредоноÑному ПО выполнÑÑ‚ÑŒ произвольный -код в контекÑте Ñдра. Проблеме приÑвоен выÑокий уровень ÑерьезноÑти, поÑкольку -уÑзвимоÑÑ‚ÑŒ требует Ñначала нарушить защиту привилегированного процеÑÑа.</p> +код в контекÑте Ñдра. Проблеме приÑвоен выÑокий уровень ÑерьезноÑти, поÑкольку уÑзвимоÑÑ‚ÑŒ требует Ñначала нарушить защиту привилегированного процеÑÑа.</p> <table> <colgroup><col width="19%" /> @@ -1603,7 +1593,7 @@ <td>A-28085222*<br /> M-ALPS02677244</td> <td>Ð’Ñ‹Ñокий</td> - <td>Android One</td> + <td>Android One</td> <td>7Â Ð°Ð¿Ñ€ÐµÐ»Ñ 2016 г.</td> </tr> <tr> @@ -1611,7 +1601,7 @@ <td>A-29008443*<br /> M-ALPS02677244</td> <td>Ð’Ñ‹Ñокий</td> - <td>Android One</td> + <td>Android One</td> <td>7Â Ð°Ð¿Ñ€ÐµÐ»Ñ 2016 г.</td> </tr> </tbody></table> @@ -1619,8 +1609,7 @@ <h3 id="elevation-of-privilege-vulnerability-in-qualcomm-wi-fi-driver-2"> Повышение привилегий через Wi-Fi-драйвер Qualcomm</h3> -<p>УÑзвимоÑÑ‚ÑŒ позволÑет локальному вредоноÑному ПО выполнÑÑ‚ÑŒ произвольный -код в контекÑте Ñдра. Проблеме приÑвоен выÑокий уровень ÑерьезноÑти, поÑкольку уÑзвимоÑÑ‚ÑŒ требует Ñначала нарушить защиту привилегированного процеÑÑа.</p> +<p>УÑзвимоÑÑ‚ÑŒ позволÑет локальному вредоноÑному ПО выполнÑÑ‚ÑŒ произвольный код в контекÑте Ñдра. Проблеме приÑвоен выÑокий уровень ÑерьезноÑти, поÑкольку уÑзвимоÑÑ‚ÑŒ требует Ñначала нарушить защиту привилегированного процеÑÑа.</p> <table> <colgroup><col width="19%" /> @@ -1670,7 +1659,7 @@ <td>A-28174490*<br /> M-ALPS02703105</td> <td>Ð’Ñ‹Ñокий</td> - <td>Android One</td> + <td>Android One</td> <td>11Â Ð°Ð¿Ñ€ÐµÐ»Ñ 2016 г.</td> </tr> </tbody></table> @@ -1699,7 +1688,7 @@ <td>A-28175025*<br /> M-ALPS02693738</td> <td>Ð’Ñ‹Ñокий</td> - <td>Android One</td> + <td>Android One</td> <td>11Â Ð°Ð¿Ñ€ÐµÐ»Ñ 2016 г.</td> </tr> <tr> @@ -1707,7 +1696,7 @@ <td>A-28175027*<br /> M-ALPS02693739</td> <td>Ð’Ñ‹Ñокий</td> - <td>Android One</td> + <td>Android One</td> <td>11Â Ð°Ð¿Ñ€ÐµÐ»Ñ 2016 г.</td> </tr> </tbody></table> @@ -1745,9 +1734,7 @@ <h3 id="elevation-of-privilege-vulnerability-in-kernel-file-system-2"> Повышение привилегий через файловую ÑиÑтему Ñдра</h3> -<p>УÑзвимоÑÑ‚ÑŒ позволÑет локальному вредоноÑному ПО выполнÑÑ‚ÑŒ произвольный -код в контекÑте Ñдра. Проблеме приÑвоен выÑокий уровень ÑерьезноÑти, поÑкольку -уÑзвимоÑÑ‚ÑŒ требует Ñначала нарушить защиту привилегированного процеÑÑа.</p> +<p>УÑзвимоÑÑ‚ÑŒ позволÑет локальному вредоноÑному ПО выполнÑÑ‚ÑŒ произвольный код в контекÑте Ñдра. Проблеме приÑвоен выÑокий уровень ÑерьезноÑти, поÑкольку уÑзвимоÑÑ‚ÑŒ требует Ñначала нарушить защиту привилегированного процеÑÑа.</p> <table> <colgroup><col width="19%" /> @@ -1996,7 +1983,7 @@ <td>A-28175522*<br /> M-ALPS02694389</td> <td>Ð’Ñ‹Ñокий</td> - <td>Android One</td> + <td>Android One</td> <td>12Â Ð°Ð¿Ñ€ÐµÐ»Ñ 2016 г.</td> </tr> </tbody></table> diff --git a/ru/security/bulletin/2016-08-01.html b/ru/security/bulletin/2016-08-01.html index a51723a7..212a2136 100644 --- a/ru/security/bulletin/2016-08-01.html +++ b/ru/security/bulletin/2016-08-01.html @@ -56,8 +56,7 @@ </p> <ul> <li>ИÑпользование многих уÑзвимоÑтей затруднÑетÑÑ Ð² новых -верÑиÑÑ… Android, поÑтому мы рекомендуем вÑем пользователÑм -Ñвоевременно обновлÑÑ‚ÑŒ ÑиÑтему.</li> +верÑиÑÑ… Android, поÑтому мы рекомендуем вÑем пользователÑм Ñвоевременно обновлÑÑ‚ÑŒ ÑиÑтему.</li> <li>Команда, Ð¾Ñ‚Ð²ÐµÑ‡Ð°ÑŽÑ‰Ð°Ñ Ð·Ð° безопаÑноÑÑ‚ÑŒ Android, активно отÑлеживает Ð·Ð»Ð¾ÑƒÐ¿Ð¾Ñ‚Ñ€ÐµÐ±Ð»ÐµÐ½Ð¸Ñ Ñ Ð¿Ð¾Ð¼Ð¾Ñ‰ÑŒÑŽ <a href="http://static.googleusercontent.com/media/source.android.com/en//security/reports/Google_Android_Security_2015_Report_Final.pdf">Проверки приложений и SafetyNet</a>. Ðти ÑервиÑÑ‹ предупреждают Ð¿Ð¾Ð»ÑŒÐ·Ð¾Ð²Ð°Ñ‚ÐµÐ»Ñ Ð¾Ð± уÑтановке <a href="http://static.googleusercontent.com/media/source.android.com/en//security/reports/Google_Android_Security_PHA_classifications.pdf">потенциально опаÑных приложений</a>. Проверка приложений включена по умолчанию на вÑех уÑтройÑтвах Ñ <a href="http://www.android.com/gms">мобильными ÑервиÑами Google</a>. Она оÑобенно важна, еÑли пользователь уÑтанавливает ПО из Ñторонних иÑточников. Ð¥Ð¾Ñ‚Ñ Ð² Google Play инÑтрументы Ð´Ð»Ñ Ñ€ÑƒÑ‚Ð¸Ð½Ð³Ð° запрещены, они могут вÑтречатьÑÑ Ð² других магазинах. ЕÑли пользователь решает @@ -114,8 +113,7 @@ Mobile Security Group: CVE-2016-3845.</li> <h3 id="remote-code-execution-vulnerability-in-mediaserver"> Удаленное выполнение кода через mediaserver</h3> <p> -УÑзвимоÑÑ‚ÑŒ позволÑет злоумышленнику нарушить целоÑтноÑÑ‚ÑŒ информации -в памÑти при обработке медиафайлов и данных в Ñпециально Ñозданном файле. Проблеме приÑвоен критичеÑкий уровень ÑерьезноÑти из-за возможноÑти удаленного Ð²Ñ‹Ð¿Ð¾Ð»Ð½ÐµÐ½Ð¸Ñ ÐºÐ¾Ð´Ð° в контекÑте процеÑÑа mediaserver. У него еÑÑ‚ÑŒ доÑтуп к аудио- и видеопотокам, а также к привилегиÑм, закрытым Ð´Ð»Ñ Ñторонних приложений. +УÑзвимоÑÑ‚ÑŒ позволÑет злоумышленнику Ñ Ð¿Ð¾Ð¼Ð¾Ñ‰ÑŒÑŽ Ñпециально Ñозданного файла нарушить целоÑтноÑÑ‚ÑŒ информации в памÑти при обработке медиафайлов и данных. Проблеме приÑвоен критичеÑкий уровень ÑерьезноÑти из-за возможноÑти удаленного Ð²Ñ‹Ð¿Ð¾Ð»Ð½ÐµÐ½Ð¸Ñ ÐºÐ¾Ð´Ð° в контекÑте процеÑÑа mediaserver. У него еÑÑ‚ÑŒ доÑтуп к аудио- и видеопотокам, а также к привилегиÑм, закрытым Ð´Ð»Ñ Ñторонних приложений. </p> <p> УÑÐ·Ð²Ð¸Ð¼Ð°Ñ Ñ„ÑƒÐ½ÐºÑ†Ð¸Ñ ÑвлÑетÑÑ Ð¾Ñновной ÑоÑтавлÑющей ОС. Многие Ð¿Ñ€Ð¸Ð»Ð¾Ð¶ÐµÐ½Ð¸Ñ Ð¿Ð¾Ð·Ð²Ð¾Ð»ÑÑŽÑ‚ контенту, оÑобенно MMS-ÑообщениÑм и воÑпроизводимым в браузере медиафайлам, диÑтанционно обращатьÑÑ Ðº ней. @@ -128,7 +126,7 @@ Mobile Security Group: CVE-2016-3845.</li> <col width="17%" /> <col width="17%" /> </colgroup><tbody><tr> - <th>Common Vulnerabilities and Exposures</th> + <th>CVE</th> <th>СÑылки</th> <th>Уровень ÑерьезноÑти</th> <th>Обновленные уÑтройÑтва Nexus</th> @@ -177,7 +175,7 @@ Mobile Security Group: CVE-2016-3845.</li> <col width="17%" /> <col width="17%" /> </colgroup><tbody><tr> - <th>Common Vulnerabilities and Exposures</th> + <th>CVE</th> <th>СÑылки</th> <th>Уровень ÑерьезноÑти</th> <th>Обновленные уÑтройÑтва Nexus</th> @@ -208,7 +206,7 @@ Mobile Security Group: CVE-2016-3845.</li> <col width="17%" /> <col width="17%" /> </colgroup><tbody><tr> - <th>Common Vulnerabilities and Exposures</th> + <th>CVE</th> <th>СÑылки</th> <th>Уровень ÑерьезноÑти</th> <th>Обновленные уÑтройÑтва Nexus</th> @@ -266,7 +264,7 @@ Mobile Security Group: CVE-2016-3845.</li> <col width="17%" /> <col width="17%" /> </colgroup><tbody><tr> - <th>Common Vulnerabilities and Exposures</th> + <th>CVE</th> <th>СÑылки</th> <th>Уровень ÑерьезноÑти</th> <th>Обновленные уÑтройÑтва Nexus</th> @@ -324,7 +322,7 @@ Mobile Security Group: CVE-2016-3845.</li> <col width="17%" /> <col width="17%" /> </colgroup><tbody><tr> - <th>Common Vulnerabilities and Exposures</th> + <th>CVE</th> <th>СÑылки</th> <th>Уровень ÑерьезноÑти</th> <th>Обновленные уÑтройÑтва Nexus</th> @@ -356,7 +354,7 @@ Mobile Security Group: CVE-2016-3845.</li> <col width="18%" /> <col width="17%" /> </colgroup><tbody><tr> - <th>Common Vulnerabilities and Exposures</th> + <th>CVE</th> <th>СÑылки</th> <th>Уровень ÑерьезноÑти</th> <th>Обновленные уÑтройÑтва Nexus</th> @@ -388,7 +386,7 @@ Mobile Security Group: CVE-2016-3845.</li> <col width="17%" /> <col width="18%" /> </colgroup><tbody><tr> - <th>Common Vulnerabilities and Exposures</th> + <th>CVE</th> <th>СÑылки</th> <th>Уровень ÑерьезноÑти</th> <th>Обновленные уÑтройÑтва Nexus</th> @@ -419,7 +417,7 @@ Mobile Security Group: CVE-2016-3845.</li> <col width="17%" /> <col width="17%" /> </colgroup><tbody><tr> - <th>Common Vulnerabilities and Exposures</th> + <th>CVE</th> <th>СÑылки</th> <th>Уровень ÑерьезноÑти</th> <th>Обновленные уÑтройÑтва Nexus</th> @@ -450,7 +448,7 @@ Mobile Security Group: CVE-2016-3845.</li> <col width="18%" /> <col width="17%" /> </colgroup><tbody><tr> - <th>Common Vulnerabilities and Exposures</th> + <th>CVE</th> <th>СÑылки</th> <th>Уровень ÑерьезноÑти</th> <th>Обновленные уÑтройÑтва Nexus</th> @@ -512,7 +510,7 @@ Mobile Security Group: CVE-2016-3845.</li> <col width="17%" /> <col width="17%" /> </colgroup><tbody><tr> - <th>Common Vulnerabilities and Exposures</th> + <th>CVE</th> <th>СÑылки</th> <th>Уровень ÑерьезноÑти</th> <th>Обновленные уÑтройÑтва Nexus</th> @@ -543,7 +541,7 @@ Mobile Security Group: CVE-2016-3845.</li> <col width="17%" /> <col width="17%" /> </colgroup><tbody><tr> - <th>Common Vulnerabilities and Exposures</th> + <th>CVE</th> <th>СÑылки</th> <th>Уровень ÑерьезноÑти</th> <th>Обновленные уÑтройÑтва Nexus</th> @@ -574,8 +572,8 @@ Mobile Security Group: CVE-2016-3845.</li> <col width="17%" /> <col width="17%" /> </colgroup><tbody><tr> - <th>Common Vulnerabilities and Exposures</th> - <th>Референт</th> + <th>CVE</th> + <th>СÑылки</th> <th>Уровень ÑерьезноÑти</th> <th>Обновленные уÑтройÑтва Nexus</th> <th>Обновленные верÑии AOSP</th> @@ -605,8 +603,8 @@ Mobile Security Group: CVE-2016-3845.</li> <col width="18%" /> <col width="17%" /> </colgroup><tbody><tr> - <th>Common Vulnerabilities and Exposures</th> - <th>Референт</th> + <th>CVE</th> + <th>СÑылки</th> <th>Уровень ÑерьезноÑти</th> <th>Обновленные уÑтройÑтва Nexus</th> <th>Обновленные верÑии AOSP</th> @@ -676,7 +674,7 @@ QC-CR#553941</a> <col width="17%" /> <col width="17%" /> </colgroup><tbody><tr> - <th>Common Vulnerabilities and Exposures</th> + <th>CVE</th> <th>СÑылки</th> <th>Уровень ÑерьезноÑти</th> <th>Обновленные уÑтройÑтва Nexus</th> @@ -830,7 +828,7 @@ QC-CR#590721</a> </p> </td> <td>Ð’Ñ‹Ñокий</td> - <td>Google Nexus 5</td> + <td>Nexus 5</td> <td>31 марта 2014 г.</td> </tr> <tr> @@ -902,7 +900,7 @@ QC-CR#547479</a> </p> </td> <td>Ð’Ñ‹Ñокий</td> - <td>Google Nexus 5</td> + <td>Nexus 5</td> <td>30Â Ð°Ð¿Ñ€ÐµÐ»Ñ 2014 г.</td> </tr> <tr> @@ -914,7 +912,7 @@ QC-CR#524490</a> </p> </td> <td>Ð’Ñ‹Ñокий</td> - <td>Google Nexus 5</td> + <td>Nexus 5</td> <td>30Â Ð°Ð¿Ñ€ÐµÐ»Ñ 2014 г.</td> </tr> <tr> @@ -984,7 +982,7 @@ QC-CR#562261</a> </p> </td> <td>Ð’Ñ‹Ñокий</td> - <td>Google Nexus 5</td> + <td>Nexus 5</td> <td>30Â Ð°Ð¿Ñ€ÐµÐ»Ñ 2014 г.</td> </tr> <tr> @@ -1031,7 +1029,7 @@ QC-CR#642735</a> QC-CR#674712</a> </p></td> <td>Ð’Ñ‹Ñокий</td> - <td>Google Nexus 5</td> + <td>Nexus 5</td> <td>31 октÑÐ±Ñ€Ñ 2014 г.</td> </tr> <tr> @@ -1053,7 +1051,7 @@ QC-CR#770548</a> <a href="https://us.codeaurora.org/cgit/quic/la//kernel/msm-3.10/commit/?id=51c39420e3a49d1a7f05a77c64369b7623088238"> QC-CR#766022</a></p></td> <td>Ð’Ñ‹Ñокий</td> - <td>Google Nexus 6</td> + <td>Nexus 6</td> <td>31 марта 2015 г.</td> </tr> <tr> @@ -1073,7 +1071,7 @@ QC-CR#779021</a></p></td> <a href="https://us.codeaurora.org/cgit/quic/la//kernel/msm-3.10/commit/?id=e13ebd727d161db7003be6756e61283dce85fa3b"> QC-CR#792367</a></p></td> <td>Ð’Ñ‹Ñокий</td> - <td>Google Nexus 6</td> + <td>Nexus 6</td> <td>30Â Ð°Ð¿Ñ€ÐµÐ»Ñ 2015 г.</td> </tr> <tr> @@ -1093,7 +1091,7 @@ QC-CR#792473</a></p></td> <a href="https://us.codeaurora.org/cgit/quic/la//kernel/msm-3.10/commit/?id=9ec380c06bbd79493828fcc3c876d8a53fd3369f"> QC-CR#803246</a></p></td> <td>Ð’Ñ‹Ñокий</td> - <td>Google Nexus 6</td> + <td>Nexus 6</td> <td>30Â Ð¸ÑŽÐ½Ñ 2015 г.</td> </tr> <tr> @@ -1106,7 +1104,7 @@ QC-CR#794217</a></p> <a href="https://us.codeaurora.org/cgit/quic/la//kernel/msm/commit/?id=ad376e4053b87bd58f62f45b6df2c5544bc21aee"> QC-CR#836226</a></p></td> <td>Ð’Ñ‹Ñокий</td> - <td>Google Nexus 5</td> + <td>Nexus 5</td> <td>11 ÑентÑÐ±Ñ€Ñ 2015 г.</td> </tr> <tr> @@ -1116,7 +1114,7 @@ QC-CR#836226</a></p></td> <a href="https://us.codeaurora.org/cgit/quic/la/kernel/msm-3.10/commit/?id=c10f03f191307f7114af89933f2d91b830150094"> QC-CR#550061</a></p></td> <td>Средний</td> - <td>Google Nexus 5</td> + <td>Nexus 5</td> <td>13 марта 2014 г.</td> </tr> <tr> @@ -1143,8 +1141,8 @@ QC-CR#529177</a></p></td> <col width="23%" /> <col width="17%" /> </colgroup><tbody><tr> - <th>Common Vulnerabilities and Exposures</th> - <th>Референт</th> + <th>CVE</th> + <th>СÑылки</th> <th>Уровень ÑерьезноÑти</th> <th>Обновленные уÑтройÑтва Nexus</th> <th>Дата ÑÐ¾Ð¾Ð±Ñ‰ÐµÐ½Ð¸Ñ Ð¾Ð± ошибке</th> @@ -1183,8 +1181,8 @@ Upstream kernel</a></p></td> <col width="23%" /> <col width="17%" /> </colgroup><tbody><tr> - <th>Common Vulnerabilities and Exposures</th> - <th>Референт</th> + <th>CVE</th> + <th>СÑылки</th> <th>Уровень ÑерьезноÑти</th> <th>Обновленные уÑтройÑтва Nexus</th> <th>Дата ÑÐ¾Ð¾Ð±Ñ‰ÐµÐ½Ð¸Ñ Ð¾Ð± ошибке</th> @@ -1226,8 +1224,8 @@ Upstream kernel</a></p></td> <col width="23%" /> <col width="17%" /> </colgroup><tbody><tr> - <th>Common Vulnerabilities and Exposures</th> - <th>Референт</th> + <th>CVE</th> + <th>СÑылки</th> <th>Уровень ÑерьезноÑти</th> <th>Обновленные уÑтройÑтва Nexus</th> <th>Дата ÑÐ¾Ð¾Ð±Ñ‰ÐµÐ½Ð¸Ñ Ð¾Ð± ошибке</th> @@ -1247,7 +1245,7 @@ Upstream kernel</a></p></td> </p> <h3 id="elevation-of-privilege-vulnerability-in-kernel"> -Повышение привилегий через Ядро операционной ÑиÑтемы</h3> +Повышение привилегий через Ñдро</h3> <p> УÑзвимоÑÑ‚ÑŒ позволÑет локальному вредоноÑному ПО выполнÑÑ‚ÑŒ произвольный код в контекÑте Ñдра. Ей приÑвоен критичеÑкий уровень ÑерьезноÑти, поÑкольку из-за нее нарушаетÑÑ Ñ€Ð°Ð±Ð¾Ñ‚Ð° ÑиÑтемы безопаÑноÑти. Возможно, Ð´Ð»Ñ ÑƒÑÑ‚Ñ€Ð°Ð½ÐµÐ½Ð¸Ñ Ð¿Ñ€Ð¾Ð±Ð»ÐµÐ¼Ñ‹ потребуетÑÑ Ð¿ÐµÑ€ÐµÑƒÑтановить ОС. </p> @@ -1258,8 +1256,8 @@ Upstream kernel</a></p></td> <col width="23%" /> <col width="17%" /> </colgroup><tbody><tr> - <th>Common Vulnerabilities and Exposures</th> - <th>Референт</th> + <th>CVE</th> + <th>СÑылки</th> <th>Уровень ÑерьезноÑти</th> <th>Обновленные уÑтройÑтва Nexus</th> <th>Дата ÑÐ¾Ð¾Ð±Ñ‰ÐµÐ½Ð¸Ñ Ð¾Ð± ошибке</th> @@ -1328,8 +1326,8 @@ Upstream kernel</a></p></td> <col width="23%" /> <col width="17%" /> </colgroup><tbody><tr> - <th>Common Vulnerabilities and Exposures</th> - <th>Референт</th> + <th>CVE</th> + <th>СÑылки</th> <th>Уровень ÑерьезноÑти</th> <th>Обновленные уÑтройÑтва Nexus</th> <th>Дата ÑÐ¾Ð¾Ð±Ñ‰ÐµÐ½Ð¸Ñ Ð¾Ð± ошибке</th> @@ -1378,8 +1376,8 @@ Upstream kernel</a></p></td> <col width="23%" /> <col width="17%" /> </colgroup><tbody><tr> - <th>Common Vulnerabilities and Exposures</th> - <th>Референт</th> + <th>CVE</th> + <th>СÑылки</th> <th>Уровень ÑерьезноÑти</th> <th>Обновленные уÑтройÑтва Nexus</th> <th>Дата ÑÐ¾Ð¾Ð±Ñ‰ÐµÐ½Ð¸Ñ Ð¾Ð± ошибке</th> @@ -1408,8 +1406,8 @@ Upstream kernel</a></p></td> <col width="23%" /> <col width="17%" /> </colgroup><tbody><tr> - <th>Common Vulnerabilities and Exposures</th> - <th>Референт</th> + <th>CVE</th> + <th>СÑылки</th> <th>Уровень ÑерьезноÑти</th> <th>Обновленные уÑтройÑтва Nexus</th> <th>Дата ÑÐ¾Ð¾Ð±Ñ‰ÐµÐ½Ð¸Ñ Ð¾Ð± ошибке</th> @@ -1428,7 +1426,7 @@ N-CVE-2016-3844</p></td> *ИÑправление не опубликовано. Обновление ÑодержитÑÑ Ð² поÑледних бинарных драйверах Ð´Ð»Ñ ÑƒÑтройÑтв Nexus, которые можно Ñкачать на <a href="https://developers.google.com/android/nexus/drivers">Ñайте Ð´Ð»Ñ Ñ€Ð°Ð·Ñ€Ð°Ð±Ð¾Ñ‚Ñ‡Ð¸ÐºÐ¾Ð²</a>. </p> -<h3>Повышение привилегий через видеодрайвер Ядро операционной ÑиÑтемы</h3> +<h3>Повышение привилегий через видеодрайвер Ñдра</h3> <p> УÑзвимоÑÑ‚ÑŒ позволÑет локальному вредоноÑному ПО выполнÑÑ‚ÑŒ произвольный код в контекÑте Ñдра. Проблеме приÑвоен выÑокий уровень ÑерьезноÑти, поÑкольку уÑзвимоÑÑ‚ÑŒ требует Ñначала нарушить защиту привилегированного процеÑÑа. </p> @@ -1439,8 +1437,8 @@ N-CVE-2016-3844</p></td> <col width="23%" /> <col width="17%" /> </colgroup><tbody><tr> - <th>Common Vulnerabilities and Exposures</th> - <th>Референт</th> + <th>CVE</th> + <th>СÑылки</th> <th>Уровень ÑерьезноÑти</th> <th>Обновленные уÑтройÑтва Nexus</th> <th>Дата ÑÐ¾Ð¾Ð±Ñ‰ÐµÐ½Ð¸Ñ Ð¾Ð± ошибке</th> @@ -1449,7 +1447,7 @@ N-CVE-2016-3844</p></td> <td>CVE-2016-3845</td> <td>A-28399876*</td> <td>Ð’Ñ‹Ñокий</td> - <td>Google Nexus 5</td> + <td>Nexus 5</td> <td>20Â Ð°Ð¿Ñ€ÐµÐ»Ñ 2016 г.</td> </tr> </tbody></table> @@ -1469,8 +1467,8 @@ N-CVE-2016-3844</p></td> <col width="23%" /> <col width="17%" /> </colgroup><tbody><tr> - <th>Common Vulnerabilities and Exposures</th> - <th>Референт</th> + <th>CVE</th> + <th>СÑылки</th> <th>Уровень ÑерьезноÑти</th> <th>Обновленные уÑтройÑтва Nexus</th> <th>Дата ÑÐ¾Ð¾Ð±Ñ‰ÐµÐ½Ð¸Ñ Ð¾Ð± ошибке</th> @@ -1499,8 +1497,8 @@ N-CVE-2016-3844</p></td> <col width="23%" /> <col width="17%" /> </colgroup><tbody><tr> - <th>Common Vulnerabilities and Exposures</th> - <th>Референт</th> + <th>CVE</th> + <th>СÑылки</th> <th>Уровень ÑерьезноÑти</th> <th>Обновленные уÑтройÑтва Nexus</th> <th>Дата ÑÐ¾Ð¾Ð±Ñ‰ÐµÐ½Ð¸Ñ Ð¾Ð± ошибке</th> @@ -1540,8 +1538,8 @@ N-CVE-2016-3848</p></td> <col width="23%" /> <col width="17%" /> </colgroup><tbody><tr> - <th>Common Vulnerabilities and Exposures</th> - <th>Референт</th> + <th>CVE</th> + <th>СÑылки</th> <th>Уровень ÑерьезноÑти</th> <th>Обновленные уÑтройÑтва Nexus</th> <th>Дата ÑÐ¾Ð¾Ð±Ñ‰ÐµÐ½Ð¸Ñ Ð¾Ð± ошибке</th> @@ -1569,8 +1567,8 @@ N-CVE-2016-3848</p></td> <col width="26%" /> <col width="17%" /> </colgroup><tbody><tr> - <th>Common Vulnerabilities and Exposures</th> - <th>Референт</th> + <th>CVE</th> + <th>СÑылки</th> <th>Уровень ÑерьезноÑти</th> <th>Обновленные уÑтройÑтва Nexus</th> <th>Дата ÑÐ¾Ð¾Ð±Ñ‰ÐµÐ½Ð¸Ñ Ð¾Ð± ошибке</th> @@ -1603,7 +1601,7 @@ QC-CR#945164</a></p></td> <col width="17%" /> <col width="17%" /> </colgroup><tbody><tr> - <th>Common Vulnerabilities and Exposures</th> + <th>CVE</th> <th>СÑылки</th> <th>Уровень ÑерьезноÑти</th> <th>Обновленные уÑтройÑтва Nexus</th> @@ -1702,7 +1700,7 @@ QC-CR#786116</a></p></td> <a href="https://us.codeaurora.org/cgit/quic/la/kernel/msm-3.10/commit/?id=bfc6eee5e30a0c20bc37495233506f4f0cc4991d"> QC-CR#542223</a></p></td> <td>Средний</td> - <td>Google Nexus 5</td> + <td>Nexus 5</td> <td>27 марта 2014 г.</td> </tr> <tr> diff --git a/ru/security/bulletin/2016-10-01.html b/ru/security/bulletin/2016-10-01.html index 7c3a30e1..7580c70c 100644 --- a/ru/security/bulletin/2016-10-01.html +++ b/ru/security/bulletin/2016-10-01.html @@ -24,17 +24,14 @@ </p> <p> Ð’ Ñтом бюллетене ÑодержитÑÑ Ð¸Ð½Ñ„Ð¾Ñ€Ð¼Ð°Ñ†Ð¸Ñ Ð¾Ð± уÑзвимоÑÑ‚ÑÑ… в защите -уÑтройÑтв Android. К его выходу мы выпуÑтили автоматичеÑкое обновление -ÑиÑтемы безопаÑноÑти Ð´Ð»Ñ ÑƒÑтройÑтв Nexus и опубликовали образы вÑтроенного ПО Nexus на <a href="https://developers.google.com/android/nexus/images">Ñайте Ð´Ð»Ñ Ñ€Ð°Ð·Ñ€Ð°Ð±Ð¾Ñ‚Ñ‡Ð¸ÐºÐ¾Ð²</a>. Ð’Ñе актуальные проблемы, +уÑтройÑтв Android. К его выходу мы выпуÑтили автоматичеÑкое обновление ÑиÑтемы безопаÑноÑти Ð´Ð»Ñ ÑƒÑтройÑтв Nexus и опубликовали образы вÑтроенного ПО Nexus на <a href="https://developers.google.com/android/nexus/images">Ñайте Ð´Ð»Ñ Ñ€Ð°Ð·Ñ€Ð°Ð±Ð¾Ñ‚Ñ‡Ð¸ÐºÐ¾Ð²</a>. Ð’Ñе актуальные проблемы, перечиÑленные здеÑÑŒ, уÑтранены в иÑправлении от 5 октÑÐ±Ñ€Ñ 2016 года или более новом. Информацию о том, как проверить Ð¾Ð±Ð½Ð¾Ð²Ð»ÐµÐ½Ð¸Ñ ÑиÑтемы безопаÑноÑти, можно найти в <a href="https://support.google.com/nexus/answer/4457705#nexus_devices">Справочном центре</a>. Ðа поддерживаемые уÑтройÑтва Nexus будет уÑтановлено единое автоматичеÑкое обновление ÑиÑтемы безопаÑноÑти от 5 октÑÐ±Ñ€Ñ 2016 года. </p> <p> -Мы Ñообщили партнерам об уÑзвимоÑÑ‚ÑÑ… 6 ÑентÑÐ±Ñ€Ñ 2016 года или ранее. - ИÑÐ¿Ñ€Ð°Ð²Ð»ÐµÐ½Ð¸Ñ Ð¿Ñ€Ð¾Ð±Ð»ÐµÐ¼ загружены в хранилище Android Open Source Project (AOSP). -Ð’ Ñтом бюллетене также приведены ÑÑылки на иÑÐ¿Ñ€Ð°Ð²Ð»ÐµÐ½Ð¸Ñ Ð²Ð½Ðµ AOSP. +Мы Ñообщили партнерам об уÑзвимоÑÑ‚ÑÑ… 6 ÑентÑÐ±Ñ€Ñ 2016 года или ранее. ИÑÐ¿Ñ€Ð°Ð²Ð»ÐµÐ½Ð¸Ñ Ð¿Ñ€Ð¾Ð±Ð»ÐµÐ¼ загружены в хранилище Android Open Source Project (AOSP). Ð’ Ñтом бюллетене также приведены ÑÑылки на иÑÐ¿Ñ€Ð°Ð²Ð»ÐµÐ½Ð¸Ñ Ð²Ð½Ðµ AOSP. </p> <p> Ðаиболее Ñерьезные из уÑзвимоÑтей имеют критичеÑкий уровень и позволÑÑŽÑ‚ удаленно выполнÑÑ‚ÑŒ код в контекÑте Ñдра, из-за чего нарушаетÑÑ Ñ€Ð°Ð±Ð¾Ñ‚Ð° ÑиÑтемы безопаÑноÑти. Возможно, Ð´Ð»Ñ ÑƒÑÑ‚Ñ€Ð°Ð½ÐµÐ½Ð¸Ñ Ñ‚Ð°ÐºÐ¸Ñ… проблем потребуетÑÑ Ð¿ÐµÑ€ÐµÑƒÑтановить ОС. <a href="/security/overview/updates-resources.html#severity">Уровень ÑерьезноÑти</a> завиÑит от того, какой ущерб будет нанеÑен уÑтройÑтву при атаке Ñ Ð¸Ñпользованием уÑзвимоÑти, еÑли ÑредÑтва защиты будут отключены разработчиком или взломаны. @@ -65,11 +62,7 @@ <ul> <li>ИÑпользование многих уÑзвимоÑтей затруднÑетÑÑ Ð² новых верÑиÑÑ… Android, поÑтому мы рекомендуем вÑем пользователÑм Ñвоевременно обновлÑÑ‚ÑŒ ÑиÑтему.</li> - <li>Команда, Ð¾Ñ‚Ð²ÐµÑ‡Ð°ÑŽÑ‰Ð°Ñ Ð·Ð° безопаÑноÑÑ‚ÑŒ Android, активно отÑлеживает Ð·Ð»Ð¾ÑƒÐ¿Ð¾Ñ‚Ñ€ÐµÐ±Ð»ÐµÐ½Ð¸Ñ Ñ Ð¿Ð¾Ð¼Ð¾Ñ‰ÑŒÑŽ <a href="http://static.googleusercontent.com/media/source.android.com/en//security/reports/Google_Android_Security_2015_Report_Final.pdf">Проверки приложений и SafetyNet</a>. Ðти ÑервиÑÑ‹ предупреждают Ð¿Ð¾Ð»ÑŒÐ·Ð¾Ð²Ð°Ñ‚ÐµÐ»Ñ Ð¾Ð± уÑтановке <a href="http://static.googleusercontent.com/media/source.android.com/en//security/reports/Google_Android_Security_PHA_classifications.pdf">потенциально опаÑных приложений</a>. Проверка приложений включена по умолчанию на вÑех уÑтройÑтвах Ñ <a href="http://www.android.com/gms">мобильными ÑервиÑами Google</a>. Она оÑобенно важна, еÑли пользователь уÑтанавливает ПО из Ñторонних иÑточников. Ð¥Ð¾Ñ‚Ñ Ð² - Google Play инÑтрументы Ð´Ð»Ñ Ñ€ÑƒÑ‚Ð¸Ð½Ð³Ð° запрещены, - они могут вÑтречатьÑÑ Ð² других магазинах. ЕÑли пользователь решает - уÑтановить такое приложение. Проверка предупреждает об Ñтом. - Кроме того, она пытаетÑÑ Ð¸Ð´ÐµÐ½Ñ‚Ð¸Ñ„Ð¸Ñ†Ð¸Ñ€Ð¾Ð²Ð°Ñ‚ÑŒ извеÑтное вредоноÑное ПО, иÑпользующее уÑзвимоÑÑ‚ÑŒ Ð´Ð»Ñ Ð¿Ð¾Ð²Ñ‹ÑˆÐµÐ½Ð¸Ñ Ð¿Ñ€Ð¸Ð²Ð¸Ð»ÐµÐ³Ð¸Ð¹, и блокировать его уÑтановку. ЕÑли подобное ПО уже еÑÑ‚ÑŒ на уÑтройÑтве, ÑиÑтема уведомит об Ñтом Ð¿Ð¾Ð»ÑŒÐ·Ð¾Ð²Ð°Ñ‚ÐµÐ»Ñ Ð¸ попытаетÑÑ ÑƒÐ´Ð°Ð»Ð¸Ñ‚ÑŒ приложение.</li> + <li>Команда, Ð¾Ñ‚Ð²ÐµÑ‡Ð°ÑŽÑ‰Ð°Ñ Ð·Ð° безопаÑноÑÑ‚ÑŒ Android, активно отÑлеживает Ð·Ð»Ð¾ÑƒÐ¿Ð¾Ñ‚Ñ€ÐµÐ±Ð»ÐµÐ½Ð¸Ñ Ñ Ð¿Ð¾Ð¼Ð¾Ñ‰ÑŒÑŽ <a href="http://static.googleusercontent.com/media/source.android.com/en//security/reports/Google_Android_Security_2015_Report_Final.pdf">Проверки приложений и SafetyNet</a>. Ðти ÑервиÑÑ‹ предупреждают Ð¿Ð¾Ð»ÑŒÐ·Ð¾Ð²Ð°Ñ‚ÐµÐ»Ñ Ð¾Ð± уÑтановке <a href="http://static.googleusercontent.com/media/source.android.com/en//security/reports/Google_Android_Security_PHA_classifications.pdf">потенциально опаÑных приложений</a>. Проверка приложений включена по умолчанию на вÑех уÑтройÑтвах Ñ <a href="http://www.android.com/gms">мобильными ÑервиÑами Google</a>. Она оÑобенно важна, еÑли пользователь уÑтанавливает ПО из Ñторонних иÑточников. Ð¥Ð¾Ñ‚Ñ Ð² Google Play инÑтрументы Ð´Ð»Ñ Ñ€ÑƒÑ‚Ð¸Ð½Ð³Ð° запрещены, они могут вÑтречатьÑÑ Ð² других магазинах. ЕÑли пользователь решает уÑтановить такое приложение, Проверка предупреждает об Ñтом. Кроме того, она пытаетÑÑ Ð¸Ð´ÐµÐ½Ñ‚Ð¸Ñ„Ð¸Ñ†Ð¸Ñ€Ð¾Ð²Ð°Ñ‚ÑŒ извеÑтное вредоноÑное ПО, иÑпользующее уÑзвимоÑÑ‚ÑŒ Ð´Ð»Ñ Ð¿Ð¾Ð²Ñ‹ÑˆÐµÐ½Ð¸Ñ Ð¿Ñ€Ð¸Ð²Ð¸Ð»ÐµÐ³Ð¸Ð¹, и блокировать его уÑтановку. ЕÑли подобное ПО уже еÑÑ‚ÑŒ на уÑтройÑтве, ÑиÑтема уведомит об Ñтом Ð¿Ð¾Ð»ÑŒÐ·Ð¾Ð²Ð°Ñ‚ÐµÐ»Ñ Ð¸ попытаетÑÑ ÑƒÐ´Ð°Ð»Ð¸Ñ‚ÑŒ приложение.</li> <li>ÐŸÑ€Ð¸Ð»Ð¾Ð¶ÐµÐ½Ð¸Ñ Google Hangouts и Messenger не передают медиафайлы таким процеÑÑам, как mediaserver, автоматичеÑки.</li> </ul> <h2 id="acknowledgements">БлагодарноÑти</h2> @@ -108,14 +101,12 @@ <h2 id="2016-10-01-details">ОпиÑание уÑзвимоÑтей (обновление ÑиÑтемы безопаÑноÑти 2016-10-01)</h2> <p> -Ð’ Ñтом разделе вы найдете подробную информацию обо вÑех уÑзвимоÑÑ‚ÑÑ…, уÑтраненных в обновлении ÑиÑтемы безопаÑноÑти 2016-10-01: опиÑание и обоÑнование ÑерьезноÑти, таблицу Ñ CVE, ÑÑылками, уровнем ÑерьезноÑти, уÑзвимыми уÑтройÑтвами Nexus и верÑиÑми AOSP (при наличии), а также датой ÑÐ¾Ð¾Ð±Ñ‰ÐµÐ½Ð¸Ñ Ð¾Ð± ошибке. Где возможно, мы приведем оÑновную ÑÑылку на опубликованное -изменение, ÑвÑзанное Ñ Ð¸Ð´ÐµÐ½Ñ‚Ð¸Ñ„Ð¸ÐºÐ°Ñ‚Ð¾Ñ€Ð¾Ð¼ ошибки (например, ÑпиÑок AOSP), и дополнительные ÑÑылки в квадратных Ñкобках. +Ð’ Ñтом разделе вы найдете подробную информацию обо вÑех уÑзвимоÑÑ‚ÑÑ…, уÑтраненных в обновлении ÑиÑтемы безопаÑноÑти 2016-10-01: опиÑание и обоÑнование ÑерьезноÑти, таблицу Ñ CVE, ÑÑылками, уровнем ÑерьезноÑти, уÑзвимыми уÑтройÑтвами Nexus и верÑиÑми AOSP (при наличии), а также датой ÑÐ¾Ð¾Ð±Ñ‰ÐµÐ½Ð¸Ñ Ð¾Ð± ошибке. Где возможно, мы приведем оÑновную ÑÑылку на опубликованное изменение, ÑвÑзанное Ñ Ð¸Ð´ÐµÐ½Ñ‚Ð¸Ñ„Ð¸ÐºÐ°Ñ‚Ð¾Ñ€Ð¾Ð¼ ошибки (например, ÑпиÑок AOSP), и дополнительные ÑÑылки в квадратных Ñкобках. </p> <h3 id="eopv-in-servicemanager">Повышение привилегий через ServiceManager</h3> <p> УÑзвимоÑÑ‚ÑŒ позволÑет локальному вредоноÑному ПО региÑтрировать произвольные -ÑервиÑÑ‹ от имени привилегированного процеÑÑа, такого как system_server. УÑзвимоÑти приÑвоен выÑокий уровень -ÑерьезноÑти из-за возможноÑти подмены ÑервиÑов. +ÑервиÑÑ‹ от имени привилегированного процеÑÑа, такого как system_server. УÑзвимоÑти приÑвоен выÑокий уровень ÑерьезноÑти из-за возможноÑти подмены ÑервиÑов. </p> <table> <colgroup><col width="18%" /> @@ -249,7 +240,7 @@ </tbody></table> <h3 id="eopv-in-framework-apis">Повышение привилегий через Framework API</h3> <p> -УÑзвимоÑÑ‚ÑŒ позволÑет локальному вредоноÑному ПО выполнÑÑ‚ÑŒ произвольный код в контекÑте привилегированного процеÑÑа. Проблеме приÑвоен выÑокий уровень ÑерьезноÑти, поÑкольку из-за нее можно получить разрешениÑ, недоÑтупные Ñторонним приложениÑм. +УÑзвимоÑÑ‚ÑŒ позволÑет локальному вредоноÑному ПО выполнÑÑ‚ÑŒ произвольный код в контекÑте привилегированного процеÑÑа. Проблеме приÑвоен выÑокий уровень ÑерьезноÑти, поÑкольку Ñ ÐµÐµ помощью можно получить привилегии, недоÑтупные Ñторонним приложениÑм. </p> <table> <colgroup><col width="18%" /> @@ -276,9 +267,9 @@ <td>17Â Ð¸ÑŽÐ»Ñ 2016 г.</td> </tr> </tbody></table> -<h3 id="eopv-in-telephony">Повышение привилегий через телефонную ÑвÑзь</h3> +<h3 id="eopv-in-telephony">Повышение привилегий через поÑтавщик телефонной ÑвÑзи</h3> <p> -УÑзвимоÑÑ‚ÑŒ позволÑет локальному вредоноÑному ПО выполнÑÑ‚ÑŒ произвольный код в контекÑте привилегированного процеÑÑа. Проблеме приÑвоен выÑокий уровень ÑерьезноÑти, поÑкольку из-за нее можно получить разрешениÑ, недоÑтупные Ñторонним приложениÑм. +УÑзвимоÑÑ‚ÑŒ позволÑет локальному вредоноÑному ПО выполнÑÑ‚ÑŒ произвольный код в контекÑте привилегированного процеÑÑа. Проблеме приÑвоен выÑокий уровень ÑерьезноÑти, поÑкольку Ñ ÐµÐµ помощью можно получить привилегии, недоÑтупные Ñторонним приложениÑм. </p> <table> <colgroup><col width="18%" /> @@ -307,7 +298,7 @@ </tbody></table> <h3 id="eopv-in-camera-service">Повышение привилегий через ÑÐµÑ€Ð²Ð¸Ñ ÐºÐ°Ð¼ÐµÑ€Ñ‹</h3> <p> -УÑзвимоÑÑ‚ÑŒ позволÑет локальному вредоноÑному ПО выполнÑÑ‚ÑŒ произвольный код в контекÑте привилегированного процеÑÑа. Проблеме приÑвоен выÑокий уровень ÑерьезноÑти, поÑкольку из-за нее можно получить разрешениÑ, недоÑтупные Ñторонним приложениÑм. +УÑзвимоÑÑ‚ÑŒ позволÑет локальному вредоноÑному ПО выполнÑÑ‚ÑŒ произвольный код в контекÑте привилегированного процеÑÑа. Проблеме приÑвоен выÑокий уровень ÑерьезноÑти, поÑкольку Ñ ÐµÐµ помощью можно получить привилегии, недоÑтупные Ñторонним приложениÑм. </p> <table> <colgroup><col width="18%" /> @@ -372,9 +363,9 @@ <td>5 авгуÑта 2016 г.</td> </tr> </tbody></table> -<h3 id="information-disclosure-vulnerability-in-aosp-mail">РаÑкрытие информации через почтового клиента AOSP</h3> +<h3 id="information-disclosure-vulnerability-in-aosp-mail">РаÑкрытие информации через почтовый клиент AOSP</h3> <p> -УÑзвимоÑÑ‚ÑŒ позволÑет локальному вредоноÑному ПО обходить защиту ОС, обеÑпечивающую раздельное хранение данных приложений. Из-за Ñтого проблеме приÑвоен выÑокий уровень ÑерьезноÑти. +УÑзвимоÑÑ‚ÑŒ позволÑет локальному вредоноÑному ПО обходить защиту ОС, обеÑпечивающую раздельное хранение данных приложений. Проблеме приÑвоен выÑокий уровень ÑерьезноÑти, поÑкольку из-за нее можно получить неÑанкционированный доÑтуп к информации. </p> <table> <colgroup><col width="18%" /> @@ -403,7 +394,7 @@ </tbody></table> <h3 id="dosv-in-wi-fi">Отказ в обÑлуживании в Wi-Fi</h3> <p> -УÑзвимоÑÑ‚ÑŒ позволÑет находÑщемуÑÑ Ð¿Ð¾Ð±Ð»Ð¸Ð·Ð¾Ñти злоумышленнику иÑпользовать уÑтройÑтво Ð´Ð»Ñ ÑÐ¾Ð·Ð´Ð°Ð½Ð¸Ñ Ñ‚Ð¾Ñ‡ÐºÐ¸ доÑтупа и вызывать его перезагрузку. Проблеме приÑвоен выÑокий уровень ÑерьезноÑти, поÑкольку она приводит к временному отказу в обÑлуживании. +УÑзвимоÑÑ‚ÑŒ вызывает перезагрузку уÑтройÑтва, находÑщегоÑÑ Ð² зоне дейÑÑ‚Ð²Ð¸Ñ Ñпециально Ñозданной точки доÑтупа. Проблеме приÑвоен выÑокий уровень ÑерьезноÑти, поÑкольку она приводит к временному отказу в обÑлуживании. </p> <table> <colgroup><col width="18%" /> @@ -517,7 +508,7 @@ <td>25Â Ð¸ÑŽÐ½Ñ 2016 г.</td> </tr> </tbody></table> -<h3 id="eopv-in-telephony-2">Повышение привилегий через телефонную ÑвÑзь</h3> +<h3 id="eopv-in-telephony-2">Повышение привилегий через поÑтавщик телефонной ÑвÑзи</h3> <p> УÑзвимоÑÑ‚ÑŒ позволÑет локальному вредоноÑному ПО выполнÑÑ‚ÑŒ произвольный код в контекÑте привилегированного процеÑÑа. Проблеме приÑвоен Ñредний уровень ÑерьезноÑти, поÑкольку уÑзвимоÑÑ‚ÑŒ требует Ñначала нарушить защиту привилегированного процеÑÑа. </p> @@ -548,7 +539,7 @@ </tbody></table> <h3 id="eopv-in-accessibility-services">Повышение привилегий через ÑÐµÑ€Ð²Ð¸Ñ Ñпециальных возможноÑтей</h3> <p> -УÑзвимоÑÑ‚ÑŒ позволÑет локальному вредоноÑному ПО Ñоздавать ÑÐ¾Ð±Ñ‹Ñ‚Ð¸Ñ ÐºÐ°Ñаний Ñкрана. Из-за Ñтого можно получать Ñ€Ð°Ð·Ñ€ÐµÑˆÐµÐ½Ð¸Ñ Ð² диалоговом окне без ÑоглаÑÐ¸Ñ Ð¿Ð¾Ð»ÑŒÐ·Ð¾Ð²Ð°Ñ‚ÐµÐ»Ñ. Проблеме приÑвоен Ñредний уровень ÑерьезноÑти, поÑкольку из-за нее можно обойти обÑзательные Ñ‚Ñ€ÐµÐ±Ð¾Ð²Ð°Ð½Ð¸Ñ Ðº взаимодейÑтвию Ñ Ð¿Ð¾Ð»ÑŒÐ·Ð¾Ð²Ð°Ñ‚ÐµÐ»ÐµÐ¼ (например, ÑвÑзанные Ñ Ð¿Ð¾Ð»ÑƒÑ‡ÐµÐ½Ð¸ÐµÐ¼ доÑтупа к функциÑм, которые обычно требуют Ñ€Ð°Ð·Ñ€ÐµÑˆÐµÐ½Ð¸Ñ Ð¸Ð»Ð¸ должны быть запущены пользователем). +УÑзвимоÑÑ‚ÑŒ позволÑет локальному вредоноÑному ПО Ñоздавать ÑÐ¾Ð±Ñ‹Ñ‚Ð¸Ñ ÐºÐ°Ñаний Ñкрана. Из-за Ñтого можно получать Ñ€Ð°Ð·Ñ€ÐµÑˆÐµÐ½Ð¸Ñ Ð² диалоговых окнах без Ñвного ÑоглаÑÐ¸Ñ Ð¿Ð¾Ð»ÑŒÐ·Ð¾Ð²Ð°Ñ‚ÐµÐ»Ñ. Проблеме приÑвоен Ñредний уровень ÑерьезноÑти, поÑкольку из-за нее можно обойти Ñ‚Ñ€ÐµÐ±Ð¾Ð²Ð°Ð½Ð¸Ñ Ðº взаимодейÑтвию Ñ Ð¿Ð¾Ð»ÑŒÐ·Ð¾Ð²Ð°Ñ‚ÐµÐ»ÐµÐ¼ (ÑвÑзанные Ñ Ð¿Ð¾Ð»ÑƒÑ‡ÐµÐ½Ð¸ÐµÐ¼ доÑтупа к функциÑм, которые обычно должны быть разрешены или запущены пользователем). </p> <table> <colgroup><col width="18%" /> @@ -635,15 +626,11 @@ </tbody></table> <h2 id="2016-10-05-details">ОпиÑание уÑзвимоÑтей (обновление ÑиÑтемы безопаÑноÑти 2016-10-05)</h2> <p> -Ð’ Ñтом разделе вы найдете подробную информацию обо вÑех уÑзвимоÑÑ‚ÑÑ…, уÑтраненных в обновлении ÑиÑтемы безопаÑноÑти 2016-10-05: опиÑание и обоÑнование ÑерьезноÑти, таблицу Ñ CVE, ÑÑылками, уровнем ÑерьезноÑти, уÑзвимыми уÑтройÑтвами Nexus и верÑиÑми AOSP (при наличии), а также датой ÑÐ¾Ð¾Ð±Ñ‰ÐµÐ½Ð¸Ñ Ð¾Ð± ошибке. Где возможно, мы приведем оÑновную ÑÑылку на опубликованное -изменение, ÑвÑзанное Ñ Ð¸Ð´ÐµÐ½Ñ‚Ð¸Ñ„Ð¸ÐºÐ°Ñ‚Ð¾Ñ€Ð¾Ð¼ ошибки (например, ÑпиÑок AOSP), и дополнительные ÑÑылки в квадратных Ñкобках. +Ð’ Ñтом разделе вы найдете подробную информацию обо вÑех уÑзвимоÑÑ‚ÑÑ…, уÑтраненных в обновлении ÑиÑтемы безопаÑноÑти 2016-10-05: опиÑание и обоÑнование ÑерьезноÑти, таблицу Ñ CVE, ÑÑылками, уровнем ÑерьезноÑти, уÑзвимыми уÑтройÑтвами Nexus и верÑиÑми AOSP (при наличии), а также датой ÑÐ¾Ð¾Ð±Ñ‰ÐµÐ½Ð¸Ñ Ð¾Ð± ошибке. Где возможно, мы приведем оÑновную ÑÑылку на опубликованное изменение, ÑвÑзанное Ñ Ð¸Ð´ÐµÐ½Ñ‚Ð¸Ñ„Ð¸ÐºÐ°Ñ‚Ð¾Ñ€Ð¾Ð¼ ошибки (например, ÑпиÑок AOSP), и дополнительные ÑÑылки в квадратных Ñкобках. </p> <h3 id="remote-code-execution-vulnerability-in-kernel-asn-1-decoder">Удаленное выполнение кода через декодер ASN.1 Ñдра</h3> <p> -УÑзвимоÑÑ‚ÑŒ позволÑет локальному вредоноÑному ПО выполнÑÑ‚ÑŒ произвольный -код в контекÑте Ñдра. Ей приÑвоен критичеÑкий уровень ÑерьезноÑти, поÑкольку -из-за нее нарушаетÑÑ Ñ€Ð°Ð±Ð¾Ñ‚Ð° ÑиÑтемы безопаÑноÑти. Возможно, Ð´Ð»Ñ ÑƒÑÑ‚Ñ€Ð°Ð½ÐµÐ½Ð¸Ñ -проблемы потребуетÑÑ Ð¿ÐµÑ€ÐµÑƒÑтановить ОС. +УÑзвимоÑÑ‚ÑŒ позволÑет локальному вредоноÑному ПО выполнÑÑ‚ÑŒ произвольный код в контекÑте Ñдра. Ей приÑвоен критичеÑкий уровень ÑерьезноÑти, поÑкольку из-за нее нарушаетÑÑ Ñ€Ð°Ð±Ð¾Ñ‚Ð° ÑиÑтемы безопаÑноÑти. Возможно, Ð´Ð»Ñ ÑƒÑÑ‚Ñ€Ð°Ð½ÐµÐ½Ð¸Ñ Ð¿Ñ€Ð¾Ð±Ð»ÐµÐ¼Ñ‹ потребуетÑÑ Ð¿ÐµÑ€ÐµÑƒÑтановить ОС. </p> <table> <colgroup><col width="19%" /> @@ -696,10 +683,7 @@ </tbody></table> <h3 id="eopv-in-mediatek-video-driver">Повышение привилегий через видеодрайвер MediaTek</h3> <p> -УÑзвимоÑÑ‚ÑŒ позволÑет локальному вредоноÑному ПО выполнÑÑ‚ÑŒ произвольный -код в контекÑте Ñдра. Ей приÑвоен критичеÑкий уровень ÑерьезноÑти, поÑкольку -из-за нее нарушаетÑÑ Ñ€Ð°Ð±Ð¾Ñ‚Ð° ÑиÑтемы безопаÑноÑти. Возможно, Ð´Ð»Ñ ÑƒÑÑ‚Ñ€Ð°Ð½ÐµÐ½Ð¸Ñ -проблемы потребуетÑÑ Ð¿ÐµÑ€ÐµÑƒÑтановить ОС. +УÑзвимоÑÑ‚ÑŒ позволÑет локальному вредоноÑному ПО выполнÑÑ‚ÑŒ произвольный код в контекÑте Ñдра. Ей приÑвоен критичеÑкий уровень ÑерьезноÑти, поÑкольку из-за нее нарушаетÑÑ Ñ€Ð°Ð±Ð¾Ñ‚Ð° ÑиÑтемы безопаÑноÑти. Возможно, Ð´Ð»Ñ ÑƒÑÑ‚Ñ€Ð°Ð½ÐµÐ½Ð¸Ñ Ð¿Ñ€Ð¾Ð±Ð»ÐµÐ¼Ñ‹ потребуетÑÑ Ð¿ÐµÑ€ÐµÑƒÑтановить ОС. </p> <table> <colgroup><col width="19%" /> @@ -728,10 +712,7 @@ </p> <h3 id="eopv-in-kernel-shared-memory-driver">Повышение привилегий через драйвер Ñ€Ð°Ð·Ð´ÐµÐ»ÐµÐ½Ð¸Ñ Ð¿Ð°Ð¼Ñти Ñдра</h3> <p> -УÑзвимоÑÑ‚ÑŒ позволÑет локальному вредоноÑному ПО выполнÑÑ‚ÑŒ произвольный -код в контекÑте Ñдра. Ей приÑвоен критичеÑкий уровень ÑерьезноÑти, поÑкольку -из-за нее нарушаетÑÑ Ñ€Ð°Ð±Ð¾Ñ‚Ð° ÑиÑтемы безопаÑноÑти. Возможно, Ð´Ð»Ñ ÑƒÑÑ‚Ñ€Ð°Ð½ÐµÐ½Ð¸Ñ -проблемы потребуетÑÑ Ð¿ÐµÑ€ÐµÑƒÑтановить ОС. +УÑзвимоÑÑ‚ÑŒ позволÑет локальному вредоноÑному ПО выполнÑÑ‚ÑŒ произвольный код в контекÑте Ñдра. Ей приÑвоен критичеÑкий уровень ÑерьезноÑти, поÑкольку из-за нее нарушаетÑÑ Ñ€Ð°Ð±Ð¾Ñ‚Ð° ÑиÑтемы безопаÑноÑти. Возможно, Ð´Ð»Ñ ÑƒÑÑ‚Ñ€Ð°Ð½ÐµÐ½Ð¸Ñ Ð¿Ñ€Ð¾Ð±Ð»ÐµÐ¼Ñ‹ потребуетÑÑ Ð¿ÐµÑ€ÐµÑƒÑтановить ОС. </p> <table> <colgroup><col width="19%" /> @@ -759,9 +740,7 @@ <h3 id="vulnerabilities-in-qc-components"> УÑзвимоÑти в компонентах Qualcomm</h3> <p> -Ð’ таблице ниже перечиÑлены уÑзвимоÑти ÑиÑтемы безопаÑноÑти, затрагивающие -компоненты Qualcomm, которые детально опиÑаны в бюллетенÑÑ… по безопаÑноÑти -Qualcomm AMSS за март и апрель 2016 года. +Ð’ таблице ниже перечиÑлены уÑзвимоÑти ÑиÑтемы безопаÑноÑти, затрагивающие компоненты Qualcomm, которые детально опиÑаны в бюллетенÑÑ… по безопаÑноÑти Qualcomm AMSS за март и апрель 2016 года. </p> <table> <colgroup><col width="19%" /> @@ -803,9 +782,7 @@ Qualcomm AMSS за март и апрель 2016 года. </p> <h3 id="eopv-in-qualcomm-networking-component">Повышение привилегий через Ñетевой компонент Qualcomm</h3> <p> -УÑзвимоÑÑ‚ÑŒ позволÑет локальному вредоноÑному ПО выполнÑÑ‚ÑŒ произвольный -код в контекÑте Ñдра. Проблеме приÑвоен выÑокий уровень ÑерьезноÑти, поÑкольку -уÑзвимоÑÑ‚ÑŒ требует Ñначала нарушить защиту привилегированного процеÑÑа. +УÑзвимоÑÑ‚ÑŒ позволÑет локальному вредоноÑному ПО выполнÑÑ‚ÑŒ произвольный код в контекÑте Ñдра. Проблеме приÑвоен выÑокий уровень ÑерьезноÑти, поÑкольку уÑзвимоÑÑ‚ÑŒ требует Ñначала нарушить защиту привилегированного процеÑÑа. </p> <table> <colgroup><col width="19%" /> @@ -831,9 +808,7 @@ Qualcomm AMSS за март и апрель 2016 года. </tbody></table> <h3 id="eopv-in-nvidia-mmc-test-driver">Повышение привилегий через драйвер NVIDIA Ð´Ð»Ñ Ñ‚ÐµÑÑ‚Ð¸Ñ€Ð¾Ð²Ð°Ð½Ð¸Ñ MMC</h3> <p> -УÑзвимоÑÑ‚ÑŒ позволÑет локальному вредоноÑному ПО выполнÑÑ‚ÑŒ произвольный -код в контекÑте Ñдра. Проблеме приÑвоен выÑокий уровень ÑерьезноÑти, поÑкольку -уÑзвимоÑÑ‚ÑŒ требует Ñначала нарушить защиту привилегированного процеÑÑа. +УÑзвимоÑÑ‚ÑŒ позволÑет локальному вредоноÑному ПО выполнÑÑ‚ÑŒ произвольный код в контекÑте Ñдра. Проблеме приÑвоен выÑокий уровень ÑерьезноÑти, поÑкольку уÑзвимоÑÑ‚ÑŒ требует Ñначала нарушить защиту привилегированного процеÑÑа. </p> <table> <colgroup><col width="19%" /> @@ -862,9 +837,7 @@ Qualcomm AMSS за март и апрель 2016 года. </p> <h3 id="eopv-in-qsee-communicator-driver">Повышение привилегий через драйвер Qualcomm Ð´Ð»Ñ QSEE Communicator</h3> <p> -УÑзвимоÑÑ‚ÑŒ позволÑет локальному вредоноÑному ПО выполнÑÑ‚ÑŒ произвольный -код в контекÑте Ñдра. Проблеме приÑвоен выÑокий уровень ÑерьезноÑти, поÑкольку -уÑзвимоÑÑ‚ÑŒ требует Ñначала нарушить защиту привилегированного процеÑÑа. +УÑзвимоÑÑ‚ÑŒ позволÑет локальному вредоноÑному ПО выполнÑÑ‚ÑŒ произвольный код в контекÑте Ñдра. Проблеме приÑвоен выÑокий уровень ÑерьезноÑти, поÑкольку уÑзвимоÑÑ‚ÑŒ требует Ñначала нарушить защиту привилегированного процеÑÑа. </p> <table> <colgroup><col width="19%" /> @@ -961,8 +934,7 @@ Qualcomm AMSS за март и апрель 2016 года. </tbody></table> <h3 id="eopv-in-qualcomm-sound-driver">Повышение привилегий через аудиодрайвер Qualcomm</h3> <p> -УÑзвимоÑÑ‚ÑŒ позволÑет локальному вредоноÑному ПО выполнÑÑ‚ÑŒ произвольный -код в контекÑте Ñдра. Проблеме приÑвоен выÑокий уровень ÑерьезноÑти, поÑкольку уÑзвимоÑÑ‚ÑŒ требует Ñначала нарушить защиту привилегированного процеÑÑа. +УÑзвимоÑÑ‚ÑŒ позволÑет локальному вредоноÑному ПО выполнÑÑ‚ÑŒ произвольный код в контекÑте Ñдра. Проблеме приÑвоен выÑокий уровень ÑерьезноÑти, поÑкольку уÑзвимоÑÑ‚ÑŒ требует Ñначала нарушить защиту привилегированного процеÑÑа. </p> <table> <colgroup><col width="19%" /> @@ -987,11 +959,9 @@ Qualcomm AMSS за март и апрель 2016 года. <td>20Â Ð¸ÑŽÐ½Ñ 2016 г.</td> </tr> </tbody></table> -<h3 id="eopv-in-qualcomm-crypto-engine-driver">Повышение привилегий через драйвер Qualcomm Ð´Ð»Ñ ÑˆÐ¸Ñ„Ñ€Ð¾Ð²Ð°Ð½Ð¸Ñ</h3> +<h3 id="eopv-in-qualcomm-crypto-engine-driver">Повышение привилегий через драйвер ÑˆÐ¸Ñ„Ñ€Ð¾Ð²Ð°Ð½Ð¸Ñ Qualcomm</h3> <p> -УÑзвимоÑÑ‚ÑŒ позволÑет локальному вредоноÑному ПО выполнÑÑ‚ÑŒ произвольный -код в контекÑте Ñдра. Проблеме приÑвоен выÑокий уровень ÑерьезноÑти, поÑкольку -уÑзвимоÑÑ‚ÑŒ требует Ñначала нарушить защиту привилегированного процеÑÑа. +УÑзвимоÑÑ‚ÑŒ позволÑет локальному вредоноÑному ПО выполнÑÑ‚ÑŒ произвольный код в контекÑте Ñдра. Проблеме приÑвоен выÑокий уровень ÑерьезноÑти, поÑкольку уÑзвимоÑÑ‚ÑŒ требует Ñначала нарушить защиту привилегированного процеÑÑа. </p> <table> <colgroup><col width="19%" /> @@ -1025,8 +995,7 @@ Qualcomm AMSS за март и апрель 2016 года. </tbody></table> <h3 id="eopv-in-mediatek-video-driver-2">Повышение привилегий через видеодрайвер MediaTek</h3> <p> -УÑзвимоÑÑ‚ÑŒ позволÑет локальному вредоноÑному ПО выполнÑÑ‚ÑŒ произвольный -код в контекÑте Ñдра. Проблеме приÑвоен выÑокий уровень ÑерьезноÑти, поÑкольку уÑзвимоÑÑ‚ÑŒ требует Ñначала нарушить защиту привилегированного процеÑÑа. +УÑзвимоÑÑ‚ÑŒ позволÑет локальному вредоноÑному ПО выполнÑÑ‚ÑŒ произвольный код в контекÑте Ñдра. Проблеме приÑвоен выÑокий уровень ÑерьезноÑти, поÑкольку уÑзвимоÑÑ‚ÑŒ требует Ñначала нарушить защиту привилегированного процеÑÑа. </p> <table> <colgroup><col width="19%" /> @@ -1063,8 +1032,7 @@ Qualcomm AMSS за март и апрель 2016 года. </p> <h3 id="eopv-in-qualcomm-video-driver">Повышение привилегий через видеодрайвер Qualcomm</h3> <p> -УÑзвимоÑÑ‚ÑŒ позволÑет локальному вредоноÑному ПО выполнÑÑ‚ÑŒ произвольный -код в контекÑте Ñдра. Проблеме приÑвоен выÑокий уровень ÑерьезноÑти, поÑкольку уÑзвимоÑÑ‚ÑŒ требует Ñначала нарушить защиту привилегированного процеÑÑа. +УÑзвимоÑÑ‚ÑŒ позволÑет локальному вредоноÑному ПО выполнÑÑ‚ÑŒ произвольный код в контекÑте Ñдра. Проблеме приÑвоен выÑокий уровень ÑерьезноÑти, поÑкольку уÑзвимоÑÑ‚ÑŒ требует Ñначала нарушить защиту привилегированного процеÑÑа. </p> <table> <colgroup><col width="19%" /> @@ -1098,8 +1066,7 @@ Qualcomm AMSS за март и апрель 2016 года. </tbody></table> <h3 id="eopv-in-synaptics-touchscreen-driver">Повышение привилегий через драйвер ÑенÑорного Ñкрана Synaptics</h3> <p> -УÑзвимоÑÑ‚ÑŒ позволÑет локальному вредоноÑному ПО выполнÑÑ‚ÑŒ произвольный -код в контекÑте Ñдра. Проблеме приÑвоен выÑокий уровень ÑерьезноÑти, поÑкольку уÑзвимоÑÑ‚ÑŒ требует Ñначала нарушить защиту привилегированного процеÑÑа. +УÑзвимоÑÑ‚ÑŒ позволÑет локальному вредоноÑному ПО выполнÑÑ‚ÑŒ произвольный код в контекÑте Ñдра. Проблеме приÑвоен выÑокий уровень ÑерьезноÑти, поÑкольку уÑзвимоÑÑ‚ÑŒ требует Ñначала нарушить защиту привилегированного процеÑÑа. </p> <table> <colgroup><col width="19%" /> @@ -1163,10 +1130,7 @@ Qualcomm AMSS за март и апрель 2016 года. </p> <h3 id="eopv-in-system_server">Повышение привилегий через system_server</h3> <p> -УÑзвимоÑÑ‚ÑŒ позволÑет локальному вредоноÑному ПО выполнÑÑ‚ÑŒ произвольный -код в контекÑте привилегированного процеÑÑа. Проблеме приÑвоен выÑокий -уровень ÑерьезноÑти, поÑкольку Ñ ÐµÐµ помощью можно получить привилегии, -недоÑтупные Ñторонним приложениÑм. +УÑзвимоÑÑ‚ÑŒ позволÑет локальному вредоноÑному ПО выполнÑÑ‚ÑŒ произвольный код в контекÑте привилегированного процеÑÑа. Проблеме приÑвоен выÑокий уровень ÑерьезноÑти, поÑкольку Ñ ÐµÐµ помощью можно получить привилегии, недоÑтупные Ñторонним приложениÑм. </p> <table> <colgroup><col width="19%" /> @@ -1327,10 +1291,7 @@ Qualcomm AMSS за март и апрель 2016 года. </p> <h3 id="eopv-in-qualcomm-character-driver">Повышение привилегий через Ñимвольный драйвер Qualcomm</h3> <p> -УÑзвимоÑÑ‚ÑŒ позволÑет локальному вредоноÑному ПО выполнÑÑ‚ÑŒ произвольный -код в контекÑте Ñдра. Проблеме приÑвоен Ñредний уровень ÑерьезноÑти, поÑкольку -уÑзвимоÑÑ‚ÑŒ требует Ñначала нарушить защиту привилегированного процеÑÑа. -Также уÑзвимый код в текущий момент недоÑтупен. +УÑзвимоÑÑ‚ÑŒ позволÑет локальному вредоноÑному ПО выполнÑÑ‚ÑŒ произвольный код в контекÑте Ñдра. Проблеме приÑвоен Ñредний уровень ÑерьезноÑти, поÑкольку уÑзвимоÑÑ‚ÑŒ требует Ñначала нарушить защиту привилегированного процеÑÑа, а уÑзвимый код в текущий момент недоÑтупен. </p> <table> <colgroup><col width="19%" /> @@ -1410,7 +1371,7 @@ Qualcomm AMSS за март и апрель 2016 года. </p> <h3 id="information-disclosure-vulnerability-in-qualcomm-components">РаÑкрытие информации через компоненты Qualcomm</h3> <p> -УÑзвимоÑÑ‚ÑŒ позволÑет локальному вредоноÑному ПО получать неÑанкционированный доÑтуп к данным. Проблеме приÑвоен Ñредний уровень ÑерьезноÑти, поÑкольку уÑзвимоÑÑ‚ÑŒ требует Ñначала нарушить защиту привилегированного процеÑÑа. +УÑзвимоÑÑ‚ÑŒ в компонентах Qualcomm (в том чиÑле аудиодрайвере, драйвере IPA и Wi-Fi-драйвере) позволÑет локальному вредоноÑному ПО получать неÑанкционированный доÑтуп к данным. Проблеме приÑвоен Ñредний уровень ÑерьезноÑти, поÑкольку уÑзвимоÑÑ‚ÑŒ требует Ñначала нарушить защиту привилегированного процеÑÑа. </p> <table> <colgroup><col width="19%" /> @@ -1471,10 +1432,7 @@ Qualcomm AMSS за март и апрель 2016 года. </p> <h3 id="information-disclosure-vulnerability-in-kernel-components">РаÑкрытие информации через компоненты Ñдра</h3> <p> -УÑзвимоÑÑ‚ÑŒ позволÑет локальному вредоноÑному ПО получать -неÑанкционированный доÑтуп к данным. Проблеме приÑвоен Ñредний уровень -ÑерьезноÑти, поÑкольку уÑзвимоÑÑ‚ÑŒ требует Ñначала нарушить защиту -привилегированного процеÑÑа. +УÑзвимоÑÑ‚ÑŒ позволÑет локальному вредоноÑному ПО получать неÑанкционированный доÑтуп к данным. Проблеме приÑвоен Ñредний уровень ÑерьезноÑти, поÑкольку уÑзвимоÑÑ‚ÑŒ требует Ñначала нарушить защиту привилегированного процеÑÑа. </p> <table> <colgroup><col width="19%" /> @@ -1523,11 +1481,8 @@ Qualcomm AMSS за март и апрель 2016 года. </p> <h3 id="information-disclosure-vulnerability-in-nvidia-profiler">РаÑкрытие информации через профилировщик NVIDIA</h3> <p> -УÑзвимоÑÑ‚ÑŒ позволÑет локальному вредоноÑному ПО получать -неÑанкционированный доÑтуп к данным. -Проблеме приÑвоен Ñредний -уровень ÑерьезноÑти, поÑкольку уÑзвимоÑÑ‚ÑŒ требует Ñначала -нарушить защиту привилегированного процеÑÑа. +УÑзвимоÑÑ‚ÑŒ позволÑет локальному вредоноÑному ПО получать неÑанкционированный доÑтуп к данным. +Проблеме приÑвоен Ñредний уровень ÑерьезноÑти, поÑкольку уÑзвимоÑÑ‚ÑŒ требует Ñначала нарушить защиту привилегированного процеÑÑа. </p> <table> <colgroup><col width="19%" /> @@ -1572,10 +1527,7 @@ Qualcomm AMSS за март и апрель 2016 года. </p> <h3 id="information-disclosure-vulnerability-in-kernel">РаÑкрытие информации через Ñдро</h3> <p> -УÑзвимоÑÑ‚ÑŒ позволÑет локальному вредоноÑному ПО получать -неÑанкционированный доÑтуп к данным. Проблеме приÑвоен Ñредний -уровень ÑерьезноÑти, поÑкольку уÑзвимоÑÑ‚ÑŒ требует Ñначала -нарушить защиту привилегированного процеÑÑа. +УÑзвимоÑÑ‚ÑŒ позволÑет локальному вредоноÑному ПО получать неÑанкционированный доÑтуп к данным. Проблеме приÑвоен Ñредний уровень ÑерьезноÑти, поÑкольку уÑзвимоÑÑ‚ÑŒ требует Ñначала нарушить защиту привилегированного процеÑÑа. </p> <table> <colgroup><col width="19%" /> @@ -1603,9 +1555,7 @@ Qualcomm AMSS за март и апрель 2016 года. </p> <h3 id="dosv-in-kernel-networking-subsystem">Отказ в обÑлуживании в Ñетевой подÑиÑтеме Ñдра</h3> <p> -УÑзвимоÑÑ‚ÑŒ позволÑет злоумышленнику заблокировать доÑтуп к ÑоединениÑм по TCP, -а также вызвать временный отказ в обÑлуживании. Из-за Ñтого проблеме приÑвоен -Ñредний уровень ÑерьезноÑти. +УÑзвимоÑÑ‚ÑŒ позволÑет злоумышленнику блокировать доÑтуп к ÑоединениÑм по TCP, а также вызывать временный отказ в обÑлуживании. Из-за Ñтого проблеме приÑвоен Ñредний уровень ÑерьезноÑти. </p> <table> <colgroup><col width="19%" /> @@ -1632,9 +1582,7 @@ Qualcomm AMSS за март и апрель 2016 года. </tbody></table> <h3 id="dosv-in-kernel-sound-driver">Отказ в обÑлуживании в аудиодрайвере Ñдра</h3> <p> -УÑзвимоÑÑ‚ÑŒ позволÑет локальному вредоноÑному ПО выполнÑÑ‚ÑŒ перезагрузку -уÑтройÑтва. Ей приÑвоен низкий уровень ÑерьезноÑти, поÑкольку она приводит -к временному отказу в обÑлуживании. +УÑзвимоÑÑ‚ÑŒ позволÑет локальному вредоноÑному ПО выполнÑÑ‚ÑŒ перезагрузку уÑтройÑтва. Ей приÑвоен низкий уровень ÑерьезноÑти, поÑкольку она приводит к временному отказу в обÑлуживании. </p> <table> <colgroup><col width="19%" /> @@ -1736,8 +1684,7 @@ Qualcomm AMSS за март и апрель 2016 года. </tbody></table> <h2 id="common-questions-and-answers">ЧаÑто задаваемые вопроÑÑ‹</h2> <p> -Ð’ Ñтом разделе мы отвечаем на вопроÑÑ‹, которые могут возникнуть -поÑле Ð¿Ñ€Ð¾Ñ‡Ñ‚ÐµÐ½Ð¸Ñ Ð±ÑŽÐ»Ð»ÐµÑ‚ÐµÐ½Ñ. +Ð’ Ñтом разделе мы отвечаем на вопроÑÑ‹, которые могут возникнуть поÑле Ð¿Ñ€Ð¾Ñ‡Ñ‚ÐµÐ½Ð¸Ñ Ð±ÑŽÐ»Ð»ÐµÑ‚ÐµÐ½Ñ. </p> <p> <strong>1. Как определить, уÑтановлено ли на уÑтройÑтво обновление, в котором уÑтранены перечиÑленные проблемы? @@ -1746,11 +1693,7 @@ Qualcomm AMSS за март и апрель 2016 года. <p> Ð’ иÑправлении от 1 октÑÐ±Ñ€Ñ 2016 года уÑтранены вÑе проблемы, ÑвÑзанные Ñ Ð¾Ð±Ð½Ð¾Ð²Ð»ÐµÐ½Ð¸ÐµÐ¼ 2016-10-01. Ð’ иÑправлении от 5 октÑÐ±Ñ€Ñ 2016 года или более новом -уÑтранены вÑе проблемы, ÑвÑзанные Ñ Ð¾Ð±Ð½Ð¾Ð²Ð»ÐµÐ½Ð¸ÐµÐ¼ 2016-10-05. Информацию о том, как узнать дату поÑледнего Ð¾Ð±Ð½Ð¾Ð²Ð»ÐµÐ½Ð¸Ñ ÑиÑтемы безопаÑноÑти, можно найти в <a href="https://support.google.com/nexus/answer/4457705">Справочном центре</a>. -Производители уÑтройÑтв, позволÑющие уÑтановить Ñти обновлениÑ, должны -приÑвоить им уровень -[ro.build.version.security_patch]:[2016-10-01] или -[ro.build.version.security_patch]:[2016-10-05]. +уÑтранены вÑе проблемы, ÑвÑзанные Ñ Ð¾Ð±Ð½Ð¾Ð²Ð»ÐµÐ½Ð¸ÐµÐ¼ 2016-10-05. Информацию о том, как узнать дату поÑледнего Ð¾Ð±Ð½Ð¾Ð²Ð»ÐµÐ½Ð¸Ñ ÑиÑтемы безопаÑноÑти, можно найти в <a href="https://support.google.com/nexus/answer/4457705">Справочном центре</a>. Производители уÑтройÑтв, позволÑющие уÑтановить Ñти обновлениÑ, должны приÑвоить им уровень [ro.build.version.security_patch]:[2016-10-01] или [ro.build.version.security_patch]:[2016-10-05]. </p> <p> <strong>2. Почему в Ñтом бюллетене говоритÑÑ Ð¾ двух обновлениÑÑ… ÑиÑтемы безопаÑноÑти?</strong> diff --git a/ru/security/bulletin/2017-01-01.html b/ru/security/bulletin/2017-01-01.html index c8a55695..b32525df 100644 --- a/ru/security/bulletin/2017-01-01.html +++ b/ru/security/bulletin/2017-01-01.html @@ -259,7 +259,7 @@ </tbody></table> <h3 id="eop-in-mediaserver">Повышение привилегий через mediaserver</h3> <p> -УÑзвимоÑÑ‚ÑŒ позволÑет локальному вредоноÑному ПО выполнÑÑ‚ÑŒ произвольный код в контекÑте привилегированного процеÑÑа. Проблеме приÑвоен выÑокий уровень ÑерьезноÑти, поÑкольку Ñ ÐµÐµ помощью можно получить привилегии, недоÑтупные Ñторонним приложениÑм. +УÑзвимоÑÑ‚ÑŒ позволÑет локальному вредоноÑному ПО выполнÑÑ‚ÑŒ произвольный код в контекÑте привилегированного процеÑÑа. Проблеме приÑвоен выÑокий уровень ÑерьезноÑти, поÑкольку из-за нее можно получить разрешениÑ, недоÑтупные Ñторонним приложениÑм. </p> <table> <colgroup><col width="18%" /> @@ -1955,8 +1955,7 @@ Upstream kernel</a></td> </tbody></table> <h2 id="common-questions-and-answers">ЧаÑто задаваемые вопроÑÑ‹</h2> -<p>Ð’ Ñтом разделе мы отвечаем на вопроÑÑ‹, которые могут возникнуть -поÑле Ð¿Ñ€Ð¾Ñ‡Ñ‚ÐµÐ½Ð¸Ñ Ð±ÑŽÐ»Ð»ÐµÑ‚ÐµÐ½Ñ.</p> +<p>Ð’ Ñтом разделе мы отвечаем на вопроÑÑ‹, которые могут возникнуть поÑле Ð¿Ñ€Ð¾Ñ‡Ñ‚ÐµÐ½Ð¸Ñ Ð±ÑŽÐ»Ð»ÐµÑ‚ÐµÐ½Ñ.</p> <p><strong>1. Как определить, уÑтановлено ли на уÑтройÑтво обновление, в котором уÑтранены перечиÑленные проблемы? </strong></p> diff --git a/ru/security/bulletin/2017-03-01.html b/ru/security/bulletin/2017-03-01.html index 8e2667d5..f1034a18 100644 --- a/ru/security/bulletin/2017-03-01.html +++ b/ru/security/bulletin/2017-03-01.html @@ -121,8 +121,7 @@ <h3 id="rce-in-mediaserver-">Удаленное выполнение кода через mediaserver </h3> -<p>УÑзвимоÑÑ‚ÑŒ позволÑет злоумышленнику нарушить целоÑтноÑÑ‚ÑŒ информации -в памÑти при обработке медиафайлов и данных в Ñпециально Ñозданном файле. Проблеме приÑвоен критичеÑкий уровень ÑерьезноÑти из-за возможноÑти удаленного Ð²Ñ‹Ð¿Ð¾Ð»Ð½ÐµÐ½Ð¸Ñ ÐºÐ¾Ð´Ð° в контекÑте процеÑÑа mediaserver.</p> +<p>УÑзвимоÑÑ‚ÑŒ позволÑет злоумышленнику Ñ Ð¿Ð¾Ð¼Ð¾Ñ‰ÑŒÑŽ Ñпециально Ñозданного файла нарушить целоÑтноÑÑ‚ÑŒ информации в памÑти при обработке медиафайлов и данных. Проблеме приÑвоен критичеÑкий уровень ÑерьезноÑти из-за возможноÑти удаленного Ð²Ñ‹Ð¿Ð¾Ð»Ð½ÐµÐ½Ð¸Ñ ÐºÐ¾Ð´Ð° в контекÑте процеÑÑа mediaserver.</p> <table> <colgroup><col width="18%" /> @@ -369,7 +368,7 @@ </tbody></table> <h3 id="eop-in-audioserver">Повышение привилегий через audioserver</h3> -<p>УÑзвимоÑÑ‚ÑŒ позволÑет локальному вредоноÑному ПО выполнÑÑ‚ÑŒ произвольный код в контекÑте привилегированного процеÑÑа. Проблеме приÑвоен выÑокий уровень ÑерьезноÑти, поÑкольку Ñ ÐµÐµ помощью можно получить привилегии, недоÑтупные Ñторонним приложениÑм.</p> +<p>УÑзвимоÑÑ‚ÑŒ позволÑет локальному вредоноÑному ПО выполнÑÑ‚ÑŒ произвольный код в контекÑте привилегированного процеÑÑа. Проблеме приÑвоен выÑокий уровень ÑерьезноÑти, поÑкольку из-за нее можно получить разрешениÑ, недоÑтупные Ñторонним приложениÑм.</p> <table> <colgroup><col width="18%" /> @@ -2104,8 +2103,7 @@ QC-CR#518731</a></td> </tbody></table> <p>*ИÑправление не опубликовано. Обновление ÑодержитÑÑ Ð² поÑледних бинарных драйверах Ð´Ð»Ñ ÑƒÑтройÑтв Nexus, которые можно Ñкачать на <a href="https://developers.google.com/android/nexus/drivers">Ñайте Ð´Ð»Ñ Ñ€Ð°Ð·Ñ€Ð°Ð±Ð¾Ñ‚Ñ‡Ð¸ÐºÐ¾Ð²</a>.</p> <h2 id="common-questions-and-answers">ЧаÑто задаваемые вопроÑÑ‹</h2> -<p>Ð’ Ñтом разделе мы отвечаем на вопроÑÑ‹, которые могут возникнуть -поÑле Ð¿Ñ€Ð¾Ñ‡Ñ‚ÐµÐ½Ð¸Ñ Ð±ÑŽÐ»Ð»ÐµÑ‚ÐµÐ½Ñ.</p> +<p>Ð’ Ñтом разделе мы отвечаем на вопроÑÑ‹, которые могут возникнуть поÑле Ð¿Ñ€Ð¾Ñ‡Ñ‚ÐµÐ½Ð¸Ñ Ð±ÑŽÐ»Ð»ÐµÑ‚ÐµÐ½Ñ.</p> <p><strong>1. Как определить, уÑтановлено ли на уÑтройÑтво обновление, в котором уÑтранены перечиÑленные проблемы? </strong></p> <p>Информацию о том, как проверить Ð¾Ð±Ð½Ð¾Ð²Ð»ÐµÐ½Ð¸Ñ ÑиÑтемы безопаÑноÑти, можно найти в <a href="https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices">Справочном центре</a>.</p> diff --git a/ru/security/bulletin/2017-05-01.html b/ru/security/bulletin/2017-05-01.html index 1b19b005..bf05a039 100644 --- a/ru/security/bulletin/2017-05-01.html +++ b/ru/security/bulletin/2017-05-01.html @@ -32,7 +32,7 @@ <p>У Ð½Ð°Ñ Ð½ÐµÑ‚ информации о том, что обнаруженные уÑзвимоÑти ÑкÑплуатировалиÑÑŒ. Ð’ разделе <a href="#mitigations">Предотвращение атак</a> опиÑываетÑÑ, как <a href="/security/enhancements/index.html">платформа безопаÑноÑти</a> и ÑредÑтва защиты ÑервиÑов, например <a href="https://developer.android.com/training/safetynet/index.html">SafetyNet</a>, помогают Ñнизить вероÑтноÑÑ‚ÑŒ атак на Android.</p> <p>Мы рекомендуем вÑем пользователÑм уÑтановить перечиÑленные здеÑÑŒ обновлениÑ.</p> -<h2 id="announcements">УведомлениÑ</h2> +<h2 id="announcements">ОбъÑвлениÑ</h2> <ul> <li>Мы включили в Ñтот бюллетень ÑÐ²ÐµÐ´ÐµÐ½Ð¸Ñ Ð¾ двух обновлениÑÑ…, чтобы помочь нашим партнерам как можно Ñкорее уÑтранить уÑзвимоÑти, затрагивающие вÑе уÑтройÑтва Android. Дополнительную информацию вы найдете в разделе <a href="#common-questions-and-answers">ЧаÑто задаваемые вопроÑÑ‹</a>. <ul> @@ -49,8 +49,7 @@ <ul> <li>ИÑпользование многих уÑзвимоÑтей затруднÑетÑÑ Ð² новых -верÑиÑÑ… Android, поÑтому мы рекомендуем вÑем пользователÑм -Ñвоевременно обновлÑÑ‚ÑŒ ÑиÑтему.</li> +верÑиÑÑ… Android, поÑтому мы рекомендуем вÑем пользователÑм Ñвоевременно обновлÑÑ‚ÑŒ ÑиÑтему.</li> <li>Команда, Ð¾Ñ‚Ð²ÐµÑ‡Ð°ÑŽÑ‰Ð°Ñ Ð·Ð° безопаÑноÑÑ‚ÑŒ Android, активно отÑлеживает Ð·Ð»Ð¾ÑƒÐ¿Ð¾Ñ‚Ñ€ÐµÐ±Ð»ÐµÐ½Ð¸Ñ Ñ Ð¿Ð¾Ð¼Ð¾Ñ‰ÑŒÑŽ <a href="/security/reports/Google_Android_Security_2016_Report_Final.pdf">Проверки приложений и SafetyNet</a>. Ðти ÑервиÑÑ‹ предупреждают Ð¿Ð¾Ð»ÑŒÐ·Ð¾Ð²Ð°Ñ‚ÐµÐ»Ñ Ð¾Ð± уÑтановке <a href="/security/reports/Google_Android_Security_PHA_classifications.pdf">потенциально опаÑных приложений</a>. Проверка приложений включена по умолчанию на вÑех уÑтройÑтвах Ñ <a href="http://www.android.com/gms">мобильными ÑервиÑами Google</a>. Она оÑобенно важна, еÑли пользователь уÑтанавливает ПО из Ñторонних иÑточников. Ð¥Ð¾Ñ‚Ñ Ð² Google Play инÑтрументы Ð´Ð»Ñ Ñ€ÑƒÑ‚Ð¸Ð½Ð³Ð° запрещены, они могут вÑтречатьÑÑ Ð² других магазинах. ЕÑли пользователь решает уÑтановить такое приложение, Проверка предупреждает об Ñтом. Кроме того, она пытаетÑÑ Ð¸Ð´ÐµÐ½Ñ‚Ð¸Ñ„Ð¸Ñ†Ð¸Ñ€Ð¾Ð²Ð°Ñ‚ÑŒ извеÑтное вредоноÑное ПО, иÑпользующее уÑзвимоÑÑ‚ÑŒ Ð´Ð»Ñ Ð¿Ð¾Ð²Ñ‹ÑˆÐµÐ½Ð¸Ñ Ð¿Ñ€Ð¸Ð²Ð¸Ð»ÐµÐ³Ð¸Ð¹, и блокировать его уÑтановку. ЕÑли подобное ПО уже еÑÑ‚ÑŒ на уÑтройÑтве, ÑиÑтема уведомит об Ñтом Ð¿Ð¾Ð»ÑŒÐ·Ð¾Ð²Ð°Ñ‚ÐµÐ»Ñ Ð¸ попытаетÑÑ ÑƒÐ´Ð°Ð»Ð¸Ñ‚ÑŒ приложение.</li> <li>ÐŸÑ€Ð¸Ð»Ð¾Ð¶ÐµÐ½Ð¸Ñ Google Hangouts и Messenger не передают медиафайлы таким процеÑÑам, как mediaserver, автоматичеÑки.</li> </ul> @@ -102,7 +101,7 @@ <col width="18%" /> <col width="17%" /> </colgroup><tbody><tr> - <th>Common Vulnerabilities and Exposures</th> + <th>CVE</th> <th>СÑылки</th> <th>Уровень ÑерьезноÑти</th> <th>Обновленные уÑтройÑтва Google</th> @@ -171,8 +170,8 @@ <col width="18%" /> <col width="17%" /> </colgroup><tbody><tr> - <th>Common Vulnerabilities and Exposures</th> - <th>Референт</th> + <th>CVE</th> + <th>СÑылки</th> <th>Уровень ÑерьезноÑти</th> <th>Обновленные уÑтройÑтва Google</th> <th>Обновленные верÑии AOSP</th> @@ -200,8 +199,8 @@ <col width="18%" /> <col width="17%" /> </colgroup><tbody><tr> - <th>Common Vulnerabilities and Exposures</th> - <th>Референт</th> + <th>CVE</th> + <th>СÑылки</th> <th>Уровень ÑерьезноÑти</th> <th>Обновленные уÑтройÑтва Google</th> <th>Обновленные верÑии AOSP</th> @@ -235,7 +234,7 @@ <h3 id="eop-in-audioserver">Повышение привилегий через audioserver</h3> -<p>УÑзвимоÑÑ‚ÑŒ позволÑет локальному вредоноÑному ПО выполнÑÑ‚ÑŒ произвольный код в контекÑте привилегированного процеÑÑа. Проблеме приÑвоен выÑокий уровень ÑерьезноÑти, поÑкольку Ñ ÐµÐµ помощью можно получить привилегии, недоÑтупные Ñторонним приложениÑм.</p> +<p>УÑзвимоÑÑ‚ÑŒ позволÑет локальному вредоноÑному ПО выполнÑÑ‚ÑŒ произвольный код в контекÑте привилегированного процеÑÑа. Проблеме приÑвоен выÑокий уровень ÑерьезноÑти, поÑкольку из-за нее можно получить разрешениÑ, недоÑтупные Ñторонним приложениÑм.</p> <table> <colgroup><col width="18%" /> @@ -2411,8 +2410,8 @@ QC-CR#832915</a></td> <table> <tbody><tr> - <th>ПриÑтавка</th> - <th>Референт</th> + <th>ПрефикÑ</th> + <th>Значение</th> </tr> <tr> <td>A-</td> diff --git a/ru/security/bulletin/2017-11-01.html b/ru/security/bulletin/2017-11-01.html index f2948d45..2985c4d9 100644 --- a/ru/security/bulletin/2017-11-01.html +++ b/ru/security/bulletin/2017-11-01.html @@ -47,7 +47,7 @@ </p> <ul> <li>Ð’ новых верÑиÑÑ… Android Ñложнее иÑпользовать многие уÑзвимоÑти, поÑтому мы рекомендуем вÑем пользователÑм Ñвоевременно обновлÑÑ‚ÑŒ ÑиÑтему.</li> - <li>Команда, Ð¾Ñ‚Ð²ÐµÑ‡Ð°ÑŽÑ‰Ð°Ñ Ð·Ð° безопаÑноÑÑ‚ÑŒ Android, активно отÑлеживает Ð·Ð»Ð¾ÑƒÐ¿Ð¾Ñ‚Ñ€ÐµÐ±Ð»ÐµÐ½Ð¸Ñ Ñ Ð¿Ð¾Ð¼Ð¾Ñ‰ÑŒÑŽ <a href="//www.android.com/play-protect">Google Play Защиты</a> и предупреждает пользователей об уÑтановке <a href="/security/reports/Google_Android_Security_PHA_classifications.pdf">потенциально опаÑных приложений</a>. Google Play Защита включена по умолчанию на вÑех уÑтройÑтвах Ñ <a href="//www.android.com/gms">ÑервиÑами Google Ð´Ð»Ñ Ð¼Ð¾Ð±Ð¸Ð»ÑŒÐ½Ñ‹Ñ… уÑтройÑтв</a>. Она оÑобенно важна, еÑли пользователь уÑтанавливает ПО из Ñторонних иÑточников.</li> + <li>Команда, Ð¾Ñ‚Ð²ÐµÑ‡Ð°ÑŽÑ‰Ð°Ñ Ð·Ð° безопаÑноÑÑ‚ÑŒ Android, Ñ Ð¿Ð¾Ð¼Ð¾Ñ‰ÑŒÑŽ <a href="//www.android.com/play-protect">Google Play Защиты</a> активно отÑлеживает Ð·Ð»Ð¾ÑƒÐ¿Ð¾Ñ‚Ñ€ÐµÐ±Ð»ÐµÐ½Ð¸Ñ Ð¸ предупреждает пользователей об уÑтановке <a href="/security/reports/Google_Android_Security_PHA_classifications.pdf">потенциально опаÑных приложений</a>. Google Play Защита включена по умолчанию на вÑех уÑтройÑтвах Ñ <a href="//www.android.com/gms">ÑервиÑами Google Ð´Ð»Ñ Ð¼Ð¾Ð±Ð¸Ð»ÑŒÐ½Ñ‹Ñ… уÑтройÑтв</a>. Она оÑобенно важна, еÑли пользователь уÑтанавливает ПО из Ñторонних иÑточников.</li> </ul> <h2 id="2017-11-01-details">ОпиÑание уÑзвимоÑтей (обновление ÑиÑтемы безопаÑноÑти 2017-11-01)</h2> <p> @@ -484,7 +484,7 @@ QC-CR#2055629</a></td> <strong>3. Что означают ÑÐ¾ÐºÑ€Ð°Ñ‰ÐµÐ½Ð¸Ñ Ð² Ñтолбце <em>Тип</em>?</strong> </p> <p> -Ð’ Ñтом Ñтолбце указан<em></em> тип уÑзвимоÑти по Ñледующей клаÑÑификации: +Ð’ Ñтом Ñтолбце указан тип уÑзвимоÑти по Ñледующей клаÑÑификации:<em></em> </p> <table> <colgroup><col width="25%" /> @@ -549,10 +549,10 @@ QC-CR#2055629</a></td> </tr> </tbody></table> <p id="asterisk"> -<strong>5. Что означает значок * Ñ€Ñдом Ñ Ð¸Ð´ÐµÐ½Ñ‚Ð¸Ñ„Ð¸ÐºÐ°Ñ‚Ð¾Ñ€Ð¾Ð¼ ошибки Android в Ñтолбце <em>СÑылки</em>?</strong> +<strong>5. Что означает Ñимвол * Ñ€Ñдом Ñ Ð¸Ð´ÐµÐ½Ñ‚Ð¸Ñ„Ð¸ÐºÐ°Ñ‚Ð¾Ñ€Ð¾Ð¼ ошибки Android в Ñтолбце <em>СÑылки</em>?</strong> </p> <p> -Значок * говорит о том, что иÑправление Ð´Ð»Ñ ÑƒÑзвимоÑти не опубликовано<em></em>. Ðеобходимое обновление ÑодержитÑÑ Ð² поÑледних бинарных драйверах Ð´Ð»Ñ ÑƒÑтройÑтв Nexus, которые можно Ñкачать на <a href="//developers.google.com/android/nexus/drivers">Ñайте Ð´Ð»Ñ Ñ€Ð°Ð·Ñ€Ð°Ð±Ð¾Ñ‚Ñ‡Ð¸ÐºÐ¾Ð²</a>. +Символ * означает, что иÑправление Ð´Ð»Ñ ÑƒÑзвимоÑти не опубликовано.<em></em> Ðеобходимое обновление ÑодержитÑÑ Ð² поÑледних бинарных драйверах Ð´Ð»Ñ ÑƒÑтройÑтв Nexus, которые можно Ñкачать на <a href="//developers.google.com/android/nexus/drivers">Ñайте Ð´Ð»Ñ Ñ€Ð°Ð·Ñ€Ð°Ð±Ð¾Ñ‚Ñ‡Ð¸ÐºÐ¾Ð²</a>. </p> <p> <strong>6. Почему теперь одни уÑзвимоÑти опиÑываютÑÑ Ð² Ñтих бюллетенÑÑ…, а другие – в бюллетенÑÑ… по безопаÑноÑти Pixel  и Nexus, а также в оÑтальных бюллетенÑÑ… партнеров?</strong> diff --git a/ru/security/bulletin/2018-01-01.html b/ru/security/bulletin/2018-01-01.html index ab0097c3..e0293a81 100644 --- a/ru/security/bulletin/2018-01-01.html +++ b/ru/security/bulletin/2018-01-01.html @@ -19,15 +19,14 @@ See the License for the specific language governing permissions and limitations under the License. --> -<p><em>Опубликовано 2 ÑÐ½Ð²Ð°Ñ€Ñ 2018 г.</em></p> +<p><em>Опубликовано 2 ÑÐ½Ð²Ð°Ñ€Ñ 2018 г. | Обновлено 29 ÑÐ½Ð²Ð°Ñ€Ñ 2018 г.</em></p> <p> Ð’ Ñтом бюллетене ÑодержитÑÑ Ð¸Ð½Ñ„Ð¾Ñ€Ð¼Ð°Ñ†Ð¸Ñ Ð¾Ð± уÑзвимоÑÑ‚ÑÑ… в защите уÑтройÑтв Android. Ð’Ñе актуальные проблемы, перечиÑленные здеÑÑŒ, уÑтранены в иÑправлении от 5 ÑÐ½Ð²Ð°Ñ€Ñ 2018 года или более новом. Информацию о том, как проверить Ð¾Ð±Ð½Ð¾Ð²Ð»ÐµÐ½Ð¸Ñ ÑиÑтемы безопаÑноÑти, можно найти в <a href="https://support.google.com/pixelphone/answer/4457705">Справочном центре</a>. </p> <p> Мы Ñообщили партнерам обо вÑех проблемах по крайней мере за меÑÑц до выхода бюллетенÑ. -ИÑÐ¿Ñ€Ð°Ð²Ð»ÐµÐ½Ð¸Ñ ÑƒÑзвимоÑтей будут добавлены в хранилище Android Open Source Project (AOSP) в течение 48 чаÑов. СÑылки на AOSP поÑвÑÑ‚ÑÑ Ð² Ñтом бюллетене позже. -</p> +ИÑÐ¿Ñ€Ð°Ð²Ð»ÐµÐ½Ð¸Ñ ÑƒÑзвимоÑтей доÑтупны в хранилище Android Open Source Project (AOSP). Ð’ Ñтом бюллетене также приведены ÑÑылки на иÑÐ¿Ñ€Ð°Ð²Ð»ÐµÐ½Ð¸Ñ Ð²Ð½Ðµ AOSP.</p> <p> Ð¡Ð°Ð¼Ð°Ñ ÑÐµÑ€ÑŒÐµÐ·Ð½Ð°Ñ Ð¸Ð· Ñтих проблем – критичеÑÐºÐ°Ñ ÑƒÑзвимоÑÑ‚ÑŒ в Media Framework, ÐºÐ¾Ñ‚Ð¾Ñ€Ð°Ñ Ð¿Ð¾Ð·Ð²Ð¾Ð»Ñет злоумышленнику выполнÑÑ‚ÑŒ произвольный код в контекÑте привилегированного процеÑÑа Ñ Ð¿Ð¾Ð¼Ð¾Ñ‰ÑŒÑŽ Ñпециально Ñозданного файла. <a href="/security/overview/updates-resources.html#severity">Уровень ÑерьезноÑти</a> завиÑит от того, какой ущерб будет нанеÑен уÑтройÑтву при атаке Ñ Ð¸Ñпользованием уÑзвимоÑти, еÑли ÑредÑтва защиты будут отключены разработчиком или взломаны. </p> @@ -38,6 +37,14 @@ <strong>Примечание.</strong> Ð˜Ð½Ñ„Ð¾Ñ€Ð¼Ð°Ñ†Ð¸Ñ Ð¾ поÑледних автоматичеÑких обновлениÑÑ… (OTA) и образах вÑтроенного ПО Ð´Ð»Ñ ÑƒÑтройÑтв Google приведена в бюллетене по безопаÑноÑти Pixel  и Nexus за Ñнварь 2018 года. </p> <h2 id="announcements">ОбъÑвлениÑ</h2> +<aside class="note"> +<p><strong>Примечание.</strong> Опубликована Ð¸Ð½Ñ„Ð¾Ñ€Ð¼Ð°Ñ†Ð¸Ñ Ð¾Ð± уÑзвимоÑÑ‚ÑÑ… CVE-2017-5715, CVE-2017-5753 и CVE-2017-5754, которые ÑвÑзаны Ñ ÑƒÐ¿Ñ€ÐµÐ¶Ð´Ð°ÑŽÑ‰Ð¸Ð¼ иÑполнением команд в процеÑÑорах. У Ð½Ð°Ñ Ð½ÐµÑ‚ информации об уÑпешном воÑпроизведении Ñтих уÑзвимоÑтей, которое привело бы к неÑанкционированному раÑкрытию информации на уÑтройÑтвах Android Ñ Ð¿Ñ€Ð¾Ñ†ÐµÑÑором ARM. +</p> +<p> +Чтобы обеÑпечить дополнительную защиту, мы включили в Ñтот бюллетень обновление, ÑвÑзанное Ñ ÑƒÑзвимоÑтью CVE-2017-13218. Оно ограничивает доÑтуп к выÑокоточным таймерам, что препÑÑ‚Ñтвует атакам по Ñторонним каналам (например, при иÑпользовании уÑзвимоÑтей CVE-2017-5715, CVE-2017-5753 и CVE-2017-5754) на вÑех извеÑтных процеÑÑорах ARM. +</p> +<p>Мы рекомендуем вÑем пользователÑм уÑтановить доÑтупные Ð¾Ð±Ð½Ð¾Ð²Ð»ÐµÐ½Ð¸Ñ ÑиÑтемы безопаÑноÑти. <a href="https://security.googleblog.com/2018/01/todays-cpu-vulnerability-what-you-need.html">Подробнее…</a></p> +</aside> <p> Мы начали выпуÑкать новый <a href="/security/bulletin/pixel/">бюллетень по безопаÑноÑти Pixel  и Nexus</a>, в котором ÑодержитÑÑ Ð¸Ð½Ñ„Ð¾Ñ€Ð¼Ð°Ñ†Ð¸Ñ Ð¾ дополнительных уÑзвимоÑÑ‚ÑÑ… в защите и улучшениÑÑ… функциональных возможноÑтей уÑтройÑтв Pixel и Nexus. Производители могут включить их в Ð¾Ð±Ð½Ð¾Ð²Ð»ÐµÐ½Ð¸Ñ Ð´Ð»Ñ Ñвоих уÑтройÑтв Android. Дополнительную информацию вы найдете в разделе <a href="#common-questions-and-answers">ЧаÑто задаваемые вопроÑÑ‹</a>. </p> @@ -70,7 +77,8 @@ </tr> <tr> <td>CVE-2017-13176</td> - <td>A-68341964</td> + <td><a href="https://android.googlesource.com/platform/frameworks/base/+/4afa0352d6c1046f9e9b67fbf0011bcd751fcbb5"> + A-68341964</a></td> <td>ПП</td> <td>Ð’Ñ‹Ñокий</td> <td>5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> @@ -94,109 +102,124 @@ <th>Обновленные верÑии AOSP</th> </tr> <tr> - <td>CVE-2017-13177</td> - <td>A-68320413</td> - <td>УВК</td> - <td>КритичеÑкий</td> - <td>5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + <td>CVE-2017-13177</td> + <td><a href="https://android.googlesource.com/platform/external/libhevc/+/b686bb2df155fd1f55220d56f38cc0033afe278c"> + A-68320413</a></td> + <td>УВК</td> + <td>КритичеÑкий</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-13178</td> - <td>A-66969281</td> - <td>УВК</td> - <td>КритичеÑкий</td> - <td>6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + <td>CVE-2017-13178</td> + <td><a href="https://android.googlesource.com/platform/frameworks/av/+/646a18fef28d19ba5beb6a2e1c00ac4c2663a10b"> + A-66969281</a></td> + <td>УВК</td> + <td>КритичеÑкий</td> + <td>6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> </tr> <tr> - <td>CVE-2017-13179</td> - <td>A-66969193</td> - <td>УВК</td> - <td>КритичеÑкий</td> - <td>6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + <td>CVE-2017-13179</td> + <td><a href="https://android.googlesource.com/platform/frameworks/av/+/47d4b33b504e14e98420943f771a9aecd6d09516"> + A-66969193</a></td> + <td>УВК</td> + <td>КритичеÑкий</td> + <td>6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> </tr> <tr> - <td>CVE-2017-13180</td> - <td>A-66969349</td> - <td>ПП</td> - <td>Ð’Ñ‹Ñокий</td> - <td>6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + <td>CVE-2017-13180</td> + <td><a href="https://android.googlesource.com/platform/frameworks/av/+/cf1e36f93fc8776e3a8109149424babeee7f8382"> + A-66969349</a></td> + <td>ПП</td> + <td>Ð’Ñ‹Ñокий</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-13181</td> - <td>A-67864232</td> - <td>ПП</td> - <td>Ð’Ñ‹Ñокий</td> - <td>7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + <td>CVE-2017-13181</td> + <td><a href="https://android.googlesource.com/platform/frameworks/base/+/d64e9594d3d73c613010ca9fafc7af9782e9225d"> + A-67864232</a></td> + <td>ПП</td> + <td>Ð’Ñ‹Ñокий</td> + <td>7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> </tr> <tr> - <td>CVE-2017-13182</td> - <td>A-67737022</td> - <td>ПП</td> - <td>Ð’Ñ‹Ñокий</td> - <td>8.0, 8.1</td> + <td>CVE-2017-13182</td> + <td><a href="https://android.googlesource.com/platform/frameworks/av/+/f1652e1b9f1d2840c79b6bf784d1befe40f4799e"> + A-67737022</a></td> + <td>ПП</td> + <td>Ð’Ñ‹Ñокий</td> + <td>8.0, 8.1</td> </tr> <tr> - <td>CVE-2017-13184</td> - <td>A-65483324</td> - <td>ПП</td> - <td>Ð’Ñ‹Ñокий</td> - <td>8.0, 8.1</td> + <td>CVE-2017-13184</td> + <td><a href="https://android.googlesource.com/platform/frameworks/native/+/16392a119661fd1da750d4d4e8e03442578bc543"> + A-65483324</a></td> + <td>ПП</td> + <td>Ð’Ñ‹Ñокий</td> + <td>8.0, 8.1</td> </tr> <tr> - <td>CVE-2017-0855</td> - <td>A-64452857</td> - <td>ОО</td> - <td>Ð’Ñ‹Ñокий</td> - <td>5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0</td> + <td>CVE-2017-0855</td> + <td><a href="https://android.googlesource.com/platform/frameworks/av/+/d7d6df849cec9d0a9c1fd0d9957a1b8edef361b7"> + A-64452857</a></td> + <td>ОО</td> + <td>Ð’Ñ‹Ñокий</td> + <td>5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0</td> </tr> <tr> - <td>CVE-2017-13191</td> - <td>A-64380403</td> - <td>ОО</td> - <td>Ð’Ñ‹Ñокий</td> - <td>5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + <td>CVE-2017-13191</td> + <td><a href="https://android.googlesource.com/platform/external/libhevc/+/f5b2fa243b4c45a4cd885e85f49ae548ab88c264"> + A-64380403</a></td> + <td>ОО</td> + <td>Ð’Ñ‹Ñокий</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-13192</td> - <td>A-64380202</td> - <td>ОО</td> - <td>Ð’Ñ‹Ñокий</td> - <td>5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + <td>CVE-2017-13192</td> + <td><a href="https://android.googlesource.com/platform/external/libhevc/+/52ca619511acbd542d843df1f92f858ce13048a5"> + A-64380202</a></td> + <td>ОО</td> + <td>Ð’Ñ‹Ñокий</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-13193</td> - <td>A-65718319</td> - <td>ОО</td> - <td>Ð’Ñ‹Ñокий</td> - <td>5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + <td>CVE-2017-13193</td> + <td><a href="https://android.googlesource.com/platform/external/libhevc/+/b3f31e493ef6fa886989198da9787807635eaae2"> + A-65718319</a></td> + <td>ОО</td> + <td>Ð’Ñ‹Ñокий</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-13195</td> - <td>A-65398821</td> - <td>ОО</td> - <td>Ð’Ñ‹Ñокий</td> - <td>5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + <td>CVE-2017-13195</td> + <td><a href="https://android.googlesource.com/platform/external/libhevc/+/066e3b1f9c954d95045bc9d33d2cdc9df419784f"> + A-65398821</a></td> + <td>ОО</td> + <td>Ð’Ñ‹Ñокий</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-13196</td> - <td>A-63522067</td> - <td>ОО</td> - <td>Ð’Ñ‹Ñокий</td> - <td>5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + <td>CVE-2017-13196</td> + <td><a href="https://android.googlesource.com/platform/external/libhevc/+/f5b2fa243b4c45a4cd885e85f49ae548ab88c264"> + A-63522067</a></td> + <td>ОО</td> + <td>Ð’Ñ‹Ñокий</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-13197</td> - <td>A-64784973</td> - <td>ОО</td> - <td>Ð’Ñ‹Ñокий</td> - <td>6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + <td>CVE-2017-13197</td> + <td><a href="https://android.googlesource.com/platform/external/libhevc/+/0a714d3a14d256c6a5675d6fbd975ca26e9bc471"> + A-64784973</a></td> + <td>ОО</td> + <td>Ð’Ñ‹Ñокий</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-13199</td> - <td>A-33846679</td> - <td>ОО</td> - <td>Ð’Ñ‹Ñокий</td> - <td>8.0, 8.1</td> + <td>CVE-2017-13199</td> + <td><a href="https://android.googlesource.com/platform/frameworks/base/+/42b2e419b48a26d2ba599d87e3a2a02c4aa625f4"> + A-33846679</a></td> + <td>ОО</td> + <td>Ð’Ñ‹Ñокий</td> + <td>8.0, 8.1</td> </tr> </tbody></table> @@ -217,32 +240,35 @@ <th>Обновленные верÑии AOSP</th> </tr> <tr> - <td>CVE-2017-13208</td> - <td>A-67474440</td> - <td>УВК</td> - <td>КритичеÑкий</td> - <td>5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + <td>CVE-2017-13208</td> + <td><a href="https://android.googlesource.com/platform/system/core/+/b71335264a7c3629f80b7bf1f87375c75c42d868"> + A-67474440</a></td> + <td>УВК</td> + <td>КритичеÑкий</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-13209</td> - <td>A-68217907</td> - <td>ПП</td> - <td>Ð’Ñ‹Ñокий</td> - <td>8.0, 8.1</td> + <td>CVE-2017-13209</td> + <td><a href="https://android.googlesource.com/platform/system/libhidl/+/a4d0252ab5b6f6cc52a221538e1536c5b55c1fa7">A-68217907</a> [<a href="https://android.googlesource.com/platform/system/tools/hidl/+/8539fc8ac94d5c92ef9df33675844ab294f68d61">2</a>] [<a href="https://android.googlesource.com/platform/system/hwservicemanager/+/e1b4a889e8b84f5c13b76333d4de90dbe102a0de">3</a>]</td> + <td>ПП</td> + <td>Ð’Ñ‹Ñокий</td> + <td>8.0, 8.1</td> </tr> <tr> - <td>CVE-2017-13210</td> - <td>A-67782345</td> - <td>ПП</td> - <td>Ð’Ñ‹Ñокий</td> - <td>5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + <td>CVE-2017-13210</td> + <td><a href="https://android.googlesource.com/platform/system/media/+/e770e378dc8e2320679272234285456ca2244a62"> + A-67782345</a></td> + <td>ПП</td> + <td>Ð’Ñ‹Ñокий</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-13211</td> - <td>A-65174158</td> - <td>ОО</td> - <td>Ð’Ñ‹Ñокий</td> - <td>8.0</td> + <td>CVE-2017-13211</td> + <td><a href="https://android.googlesource.com/platform/system/bt/+/181144a50114c824cfe3cdfd695c11a074673a5e"> + A-65174158</a></td> + <td>ОО</td> + <td>Ð’Ñ‹Ñокий</td> + <td>8.0</td> </tr> </tbody></table> @@ -322,7 +348,7 @@ Upstream kernel</a></td> <td>A-68266545<a href="#asterisk">*</a></td> <td>РИ</td> <td>Ð’Ñ‹Ñокий</td> - <td>Таймеры</td> + <td>Ð’Ñ‹Ñокоточные таймеры</td> </tr> </tbody></table> @@ -376,32 +402,6 @@ Upstream kernel</a></td> </tr> </tbody></table> -<h3 id="mediatek-components">Компоненты MediaTek</h3> -<p>Ð¡Ð°Ð¼Ð°Ñ ÑÐµÑ€ÑŒÐµÐ·Ð½Ð°Ñ ÑƒÑзвимоÑÑ‚ÑŒ позволÑет локальному вредоноÑному ПО выполнÑÑ‚ÑŒ произвольный код в контекÑте привилегированного процеÑÑа.</p> - -<table> - <colgroup><col width="17%" /> - <col width="19%" /> - <col width="9%" /> - <col width="14%" /> - <col width="39%" /> - </colgroup><tbody><tr> - <th>CVE</th> - <th>СÑылки</th> - <th>Тип</th> - <th>Уровень ÑерьезноÑти</th> - <th>Компонент</th> - </tr> - <tr> - <td>CVE-2017-13225</td> - <td>A-38308024<a href="#asterisk">*</a><br /> - M-ALPS03495789</td> - <td>ПП</td> - <td>Ð’Ñ‹Ñокий</td> - <td>MTK Media</td> - </tr> -</tbody></table> - <h3 id="nvidia-components">Компоненты NVIDIA</h3> <p>Ð¡Ð°Ð¼Ð°Ñ ÑÐµÑ€ÑŒÐµÐ·Ð½Ð°Ñ ÑƒÑзвимоÑÑ‚ÑŒ позволÑет локальному вредоноÑному ПО выполнÑÑ‚ÑŒ произвольный код в контекÑте привилегированного процеÑÑа.</p> @@ -650,9 +650,9 @@ QC-CR#2060780</a></td> </p> <h2 id="versions">ВерÑии</h2> <table> - <colgroup><col width="25%" /> + <colgroup><col width="15%" /> <col width="25%" /> - <col width="50%" /> + <col width="60%" /> </colgroup><tbody><tr> <th>ВерÑиÑ</th> <th>Дата</th> @@ -663,6 +663,20 @@ QC-CR#2060780</a></td> <td>2 ÑÐ½Ð²Ð°Ñ€Ñ 2018 г.</td> <td>Бюллетень опубликован.</td> </tr> -</tbody></table> + <tr> + <td>1.1</td> + <td>3 ÑÐ½Ð²Ð°Ñ€Ñ 2018 г.</td> + <td>Ð’ раздел объÑвлений добавлена Ð¸Ð½Ñ„Ð¾Ñ€Ð¼Ð°Ñ†Ð¸Ñ Ð¾Ð± уÑзвимоÑти CVE-2017-13218.</td> + </tr> + <tr> + <td>1.2</td> + <td>5 ÑÐ½Ð²Ð°Ñ€Ñ 2018 г.</td> + <td>Добавлены ÑÑылки на AOSP.</td> + </tr> + <tr> + <td>1.3</td> + <td>29 ÑÐ½Ð²Ð°Ñ€Ñ 2018 г.</td> + <td>Ð¡Ð²ÐµÐ´ÐµÐ½Ð¸Ñ Ð¾Ð± уÑзвимоÑти CVE-2017-13225 перенеÑены в <a href="/security/bulletin/pixel/">бюллетень по безопаÑноÑти Pixel  и Nexus</a>.</td> +</tr></tbody></table> </body></html>
\ No newline at end of file diff --git a/ru/security/bulletin/pixel/2017-10-01.html b/ru/security/bulletin/pixel/2017-10-01.html index f6996bc2..b7df3e76 100644 --- a/ru/security/bulletin/pixel/2017-10-01.html +++ b/ru/security/bulletin/pixel/2017-10-01.html @@ -528,7 +528,7 @@ QC-CR#2016076</a></td> <p id="type"> <strong>2. Что означают ÑÐ¾ÐºÑ€Ð°Ñ‰ÐµÐ½Ð¸Ñ Ð² Ñтолбце <em>Тип</em>?</strong></p> -<p>Ð’ Ñтом Ñтолбце указан<em></em> тип уÑзвимоÑти по Ñледующей клаÑÑификации:</p> +<p>Ð’ Ñтом Ñтолбце указан тип уÑзвимоÑти по Ñледующей клаÑÑификации:<em></em></p> <table> <colgroup><col width="25%" /> @@ -593,7 +593,7 @@ QC-CR#2016076</a></td> <p id="asterisk"><strong>4. Что означает значок * Ñ€Ñдом Ñ Ð¸Ð´ÐµÐ½Ñ‚Ð¸Ñ„Ð¸ÐºÐ°Ñ‚Ð¾Ñ€Ð¾Ð¼ ошибки Android в Ñтолбце <em>СÑылки</em>?</strong></p> -<p>Значок * означает, что иÑправление Ð´Ð»Ñ ÑƒÑзвимоÑти не опубликовано<em></em>. Ðеобходимое обновление ÑодержитÑÑ Ð² поÑледних бинарных драйверах Ð´Ð»Ñ ÑƒÑтройÑтв Nexus, которые можно Ñкачать на <a href="https://developers.google.com/android/nexus/drivers">Ñайте Ð´Ð»Ñ Ñ€Ð°Ð·Ñ€Ð°Ð±Ð¾Ñ‚Ñ‡Ð¸ÐºÐ¾Ð²</a>.</p> +<p>Символ * означает, что иÑправление Ð´Ð»Ñ ÑƒÑзвимоÑти не опубликовано.<em></em> Ðеобходимое обновление ÑодержитÑÑ Ð² поÑледних бинарных драйверах Ð´Ð»Ñ ÑƒÑтройÑтв Nexus, которые можно Ñкачать на <a href="https://developers.google.com/android/nexus/drivers">Ñайте Ð´Ð»Ñ Ñ€Ð°Ð·Ñ€Ð°Ð±Ð¾Ñ‚Ñ‡Ð¸ÐºÐ¾Ð²</a>.</p> <p id="split"> <strong>5. Почему теперь одни уÑзвимоÑти опиÑываютÑÑ Ð² Ñтом бюллетене, а другие – в бюллетенÑÑ… по безопаÑноÑти Android?</strong> diff --git a/ru/security/bulletin/pixel/2018-03-01.html b/ru/security/bulletin/pixel/2018-03-01.html new file mode 100644 index 00000000..92510f82 --- /dev/null +++ b/ru/security/bulletin/pixel/2018-03-01.html @@ -0,0 +1,651 @@ +<html devsite><head> + <title>Бюллетень по безопаÑноÑти Pixel и Nexus – март 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>Опубликовано 5 марта 2018 г.</em></p> + +<p> +Ð’ Ñтом бюллетене ÑодержитÑÑ Ð¸Ð½Ñ„Ð¾Ñ€Ð¼Ð°Ñ†Ð¸Ñ Ð¾Ð± уÑзвимоÑÑ‚ÑÑ… в защите и об улучшениÑÑ… функциональных возможноÑтей <a href="https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices">поддерживаемых уÑтройÑтв Pixel и Nexus</a> (уÑтройÑтва Google). Ð’Ñе проблемы, перечиÑленные здеÑÑŒ и в <a href="/security/bulletin/2018-03-01">бюллетене по безопаÑноÑти Android</a> за март 2018 года, уÑтранены в иÑправлении от 5 марта 2018 года или более новом. Информацию о том, как проверить Ð¾Ð±Ð½Ð¾Ð²Ð»ÐµÐ½Ð¸Ñ ÑиÑтемы безопаÑноÑти, можно найти в <a href="https://support.google.com/pixelphone/answer/4457705">Справочном центре</a>.</p> +<p> +Поддерживаемые уÑтройÑтва Google получат обновление ÑиÑтемы безопаÑноÑти 2018-03-05. Мы рекомендуем вÑем пользователÑм уÑтановить перечиÑленные здеÑÑŒ обновлениÑ. +</p> +<p class="note"> +<strong>Примечание.</strong> Образы вÑтроенного ПО Ð´Ð»Ñ ÑƒÑтройÑтв Google находÑÑ‚ÑÑ Ð½Ð° <a href="https://developers.google.com/android/nexus/images">Ñайте Ð´Ð»Ñ Ñ€Ð°Ð·Ñ€Ð°Ð±Ð¾Ñ‚Ñ‡Ð¸ÐºÐ¾Ð²</a>. +</p> + +<h2 id="announcements">ОбъÑвлениÑ</h2> +<p>Помимо иÑправлений уÑзвимоÑтей, опиÑанных в <a href="/security/bulletin/2018-03-01">бюллетене по безопаÑноÑти Android</a> за март 2018 года, Ð¾Ð±Ð½Ð¾Ð²Ð»ÐµÐ½Ð¸Ñ Ð´Ð»Ñ ÑƒÑтройÑтв Google Ñодержат также иÑÐ¿Ñ€Ð°Ð²Ð»ÐµÐ½Ð¸Ñ Ð¿Ñ€Ð¾Ð±Ð»ÐµÐ¼, перечиÑленных ниже. Мы Ñообщили партнерам об Ñтих проблемах по крайней мере меÑÑц назад. Они могут включить их иÑÐ¿Ñ€Ð°Ð²Ð»ÐµÐ½Ð¸Ñ Ð² Ñвои Ð¾Ð±Ð½Ð¾Ð²Ð»ÐµÐ½Ð¸Ñ Ð±ÐµÐ·Ð¾Ð¿Ð°ÑноÑти.</p> + +<h2 id="security-patches">ÐžÐ±Ð½Ð¾Ð²Ð»ÐµÐ½Ð¸Ñ ÑиÑтемы безопаÑноÑти</h2> +<p> +УÑзвимоÑти Ñгруппированы по компонентам, которые они затрагивают. Ð”Ð»Ñ ÐºÐ°Ð¶Ð´Ð¾Ð³Ð¾ приведены опиÑание и таблица Ñ CVE, ÑÑылками, <a href="#type">типом</a>, <a href="https://source.android.com/security/overview/updates-resources.html#severity">уровнем ÑерьезноÑти</a>, а также верÑиÑми AOSP (при наличии). Где возможно, мы приводим оÑновную ÑÑылку на опубликованное изменение, ÑвÑзанное Ñ Ð¸Ð´ÐµÐ½Ñ‚Ð¸Ñ„Ð¸ÐºÐ°Ñ‚Ð¾Ñ€Ð¾Ð¼ ошибки (например, ÑпиÑок AOSP), и дополнительные ÑÑылки в квадратных Ñкобках. +</p> + +<h3 id="framework">Framework</h3> + +<table> + <colgroup><col width="17%" /> + <col width="19%" /> + <col width="9%" /> + <col width="14%" /> + <col width="39%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>СÑылки</th> + <th>Тип</th> + <th>Уровень ÑерьезноÑти</th> + <th>Обновленные верÑии AOSP</th> + </tr> + <tr> + <td>CVE-2017-13263</td> + <td>A-69383160</td> + <td>ПП</td> + <td>Средний</td> + <td>8.0, 8.1</td> + </tr> +</tbody></table> + +<h3 id="media-framework">Media Framework</h3> + +<table> + <colgroup><col width="17%" /> + <col width="19%" /> + <col width="9%" /> + <col width="14%" /> + <col width="39%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>СÑылки</th> + <th>Тип</th> + <th>Уровень ÑерьезноÑти</th> + <th>Обновленные верÑии AOSP</th> + </tr> + <tr> + <td rowspan="2">CVE-2017-13264</td> + <td rowspan="2">A-70294343</td> + <td>NSI</td> + <td>NSI</td> + <td>7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + </tr> + <tr> + <td>ОО</td> + <td>Ð’Ñ‹Ñокий</td> + <td>6.0, 6.0.1</td> + </tr> + <tr> + <td rowspan="2">CVE-2017-13254</td> + <td rowspan="2">A-70239507</td> + <td>NSI</td> + <td>NSI</td> + <td>7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + </tr> + <tr> + <td>ОО</td> + <td>Ð’Ñ‹Ñокий</td> + <td>5.1.1, 6.0, 6.0.1</td> + </tr> +</tbody></table> + +<h3 id="system">СиÑтема</h3> + +<table> + <colgroup><col width="17%" /> + <col width="19%" /> + <col width="9%" /> + <col width="14%" /> + <col width="39%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>СÑылки</th> + <th>Тип</th> + <th>Уровень ÑерьезноÑти</th> + <th>Обновленные верÑии AOSP</th> + </tr> + <tr> + <td>CVE-2017-13265</td> + <td>A-36232423</td> + <td>ПП</td> + <td>Средний</td> + <td>7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + </tr> + <tr> + <td>CVE-2017-13266</td> + <td>A-69478941</td> + <td>ПП</td> + <td>Средний</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-13268</td> + <td>A-67058064</td> + <td>РИ</td> + <td>Средний</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-13269</td> + <td>A-68818034</td> + <td>РИ</td> + <td>Средний</td> + <td>5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + </tr> +</tbody></table> + +<h3 id="kernel-components">Компоненты Ñдра</h3> + +<table> + <colgroup><col width="17%" /> + <col width="19%" /> + <col width="9%" /> + <col width="14%" /> + <col width="39%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>СÑылки</th> + <th>Тип</th> + <th>Уровень ÑерьезноÑти</th> + <th>Компонент</th> + </tr> + <tr> + <td>CVE-2017-5754</td> + <td>A-69856074<a href="#asterisk">*</a></td> + <td>РИ</td> + <td>Ð’Ñ‹Ñокий</td> + <td>Отображение файлов в памÑÑ‚ÑŒ</td> + </tr> + <tr> + <td>CVE-2017-13270</td> + <td>A-69474744<a href="#asterisk">*</a></td> + <td>ПП</td> + <td>Средний</td> + <td>Драйвер Mnh_sm</td> + </tr> + <tr> + <td>CVE-2017-13271</td> + <td>A-69006799<a href="#asterisk">*</a></td> + <td>ПП</td> + <td>Средний</td> + <td>Драйвер Mnh_sm</td> + </tr> + <tr> + <td>CVE-2017-16527</td> + <td>A-69051382<br /> +<a href="https://github.com/torvalds/linux/commit/124751d5e63c823092060074bd0abaae61aaa9c4"> +Upstream kernel</a></td> + <td>ПП</td> + <td>Средний</td> + <td>USB-аудиодрайвер</td> + </tr> + <tr> + <td>CVE-2017-15649</td> + <td>A-69160446<br /> +<a href="http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=008ba2a13f2d04c947adc536d19debb8fe66f110">Upstream kernel</a> [<a href="http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4971613c1639d8e5f102c4e797c3bf8f83a5a69e">2</a>]</td> + <td>ПП</td> + <td>Средний</td> + <td>Сетевой драйвер</td> + </tr> + <tr> + <td>CVE-2017-1000111</td> + <td>A-68806121<br /> +<a href="http://patchwork.ozlabs.org/patch/800274/">Upstream kernel</a></td> + <td>ПП</td> + <td>Средний</td> + <td>Сетевой драйвер</td> + </tr> +</tbody></table> + +<h3 id="nvidia-components">Компоненты NVIDIA</h3> + +<table> + <colgroup><col width="17%" /> + <col width="19%" /> + <col width="9%" /> + <col width="14%" /> + <col width="39%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>СÑылки</th> + <th>Тип</th> + <th>Уровень ÑерьезноÑти</th> + <th>Компонент</th> + </tr> + <tr> + <td>CVE-2017-6287</td> + <td>A-64893264<a href="#asterisk">*</a><br /> + N-CVE-2017-6287</td> + <td>РИ</td> + <td>Средний</td> + <td>Media Framework</td> + </tr> + <tr> + <td>CVE-2017-6285</td> + <td>A-64893156<a href="#asterisk">*</a><br /> + N-CVE-2017-6285</td> + <td>РИ</td> + <td>Средний</td> + <td>Media Framework</td> + </tr> + <tr> + <td>CVE-2017-6288</td> + <td>A-65482562<a href="#asterisk">*</a><br /> + N-CVE-2017-6288</td> + <td>РИ</td> + <td>Средний</td> + <td>Media Framework</td> + </tr> +</tbody></table> + +<h3 id="qualcomm-components">Компоненты Qualcomm</h3> + +<table> + <colgroup><col width="17%" /> + <col width="19%" /> + <col width="9%" /> + <col width="14%" /> + <col width="39%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>СÑылки</th> + <th>Тип</th> + <th>Уровень ÑерьезноÑти</th> + <th>Компонент</th> + </tr> + <tr> + <td>CVE-2017-18061</td> + <td>A-70237701<br /> +<a href="https://source.codeaurora.org/quic/la/kernel/msm-3.18/commit/?id=b65cf2a007e88fe86dbd6d3269682fc585a4130f"> +QC-CR#2117246</a></td> + <td>ПП</td> + <td>Средний</td> + <td>Wil6210</td> + </tr> + <tr> + <td>CVE-2017-18050</td> + <td>A-70237697<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=63b57442d65dfdb4b4634ff32059b1bca8c72fb7"> +QC-CR#2119443</a></td> + <td>ПП</td> + <td>Средний</td> + <td>Управление wma</td> + </tr> + <tr> + <td>CVE-2017-18054</td> + <td>A-70237694<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=6eefc756612e39fab49ff719b3dc9b94def53396"> +QC-CR#2119432</a></td> + <td>ПП</td> + <td>Средний</td> + <td>Wma</td> + </tr> + <tr> + <td>CVE-2017-18055</td> + <td>A-70237693<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=50a0554d12cff58b3ffbd51d3194304244b87023"> +QC-CR#2119430</a></td> + <td>ПП</td> + <td>Средний</td> + <td>Wma</td> + </tr> + <tr> + <td>CVE-2017-18065</td> + <td>A-70237685<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=a8bc0f90ef49ea0aee90047a17772e4eebff259a"> +QC-CR#2113423</a></td> + <td>ПП</td> + <td>Средний</td> + <td>Wma</td> + </tr> + <tr> + <td>CVE-2017-18066</td> + <td>A-70235107<br /> +<a href="https://source.codeaurora.org/quic/la/kernel/msm-3.18/commit/?id=ff11f44c0c10c94170f03a8698f73f7e08b74625"> +QC-CR#2107976</a></td> + <td>ПП</td> + <td>Средний</td> + <td>Драйвер питаниÑ</td> + </tr> + <tr> + <td>CVE-2017-18062</td> + <td>A-68992451<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=d7927eb7c9c2d79a3e24cddd1e9447ab98bf6700"> +QC-CR#2115375</a></td> + <td>ПП</td> + <td>Средний</td> + <td>Wma</td> + </tr> + <tr> + <td>CVE-2018-3561</td> + <td>A-68870904<a href="#asterisk">*</a><br /> + QC-CR#2068569</td> + <td>ПП</td> + <td>Средний</td> + <td>Diagchar</td> + </tr> + <tr> + <td>CVE-2018-3560</td> + <td>A-68664502<a href="#asterisk">*</a><br /> + QC-CR#2142216</td> + <td>ПП</td> + <td>Средний</td> + <td>Ðудиодрайвер Qdsp6v2</td> + </tr> + <tr> + <td>CVE-2017-15834</td> + <td>A-70237704<br /> +<a href="https://source.codeaurora.org/quic/la/kernel/msm-3.18/commit/?id=2e1b54e38f1516e70d9f6581c4f1ee935effb903"> +QC-CR#2111858</a></td> + <td>ПП</td> + <td>Средний</td> + <td>Diagchar</td> + </tr> + <tr> + <td>CVE-2017-15833</td> + <td>A-70237702<br /> +<a href="https://source.codeaurora.org/quic/la/kernel/msm-3.10/commit/?id=51ce6aec73d80e1f1fcc9c7fa71e9c2fcbdbc0fd"> +QC-CR#2059835</a></td> + <td>ПП</td> + <td>Средний</td> + <td>Драйвер питаниÑ</td> + </tr> + <tr> + <td>CVE-2017-15831</td> + <td>A-70237687<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=31e6a657320e4299c659e3d57d38a89afe8c1ce1"> +QC-CR#2114255</a></td> + <td>ПП</td> + <td>Средний</td> + <td>Wma</td> + </tr> + <tr> + <td>CVE-2017-15830</td> + <td>A-70237719<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=8a7a2a9c5d203e3395811963061c79d3bc257ebe"> +QC-CR#2120725</a></td> + <td>ПП</td> + <td>Средний</td> + <td>Драйвер sme</td> + </tr> + <tr> + <td>CVE-2017-14889</td> + <td>A-70237700<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=e11e9dc8298dc0632050cacce96e9652d017f755"> +QC-CR#2119803</a></td> + <td>ПП</td> + <td>Средний</td> + <td>Wma</td> + </tr> + <tr> + <td>CVE-2017-14887</td> + <td>A-70237715<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=4ce28e7c85f89e2c3555ec840b6adda47bd5dab0"> +QC-CR#2119673</a></td> + <td>ПП</td> + <td>Средний</td> + <td>WLAN</td> + </tr> + <tr> + <td>CVE-2017-14879</td> + <td>A-63851638<a href="#asterisk">*</a><br /> + QC-CR#2056307</td> + <td>ПП</td> + <td>Средний</td> + <td>IPA</td> + </tr> + <tr> + <td>CVE-2017-11082</td> + <td>A-66937387<br /> +<a href="https://www.codeaurora.org/gitweb/quic/la/?p=kernel/msm-3.10.git;a=commit;h=2d4f8cd8d11f8fb1491a20d7e316cc0fd03eeb59"> +QC-CR#2071560</a></td> + <td>ПП</td> + <td>Средний</td> + <td>WLAN</td> + </tr> + <tr> + <td>CVE-2017-11074</td> + <td>A-68940798<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/prima/commit/?id=f5ae7b35c90f14b7e66b3a91d4fb247563a8a22b"> +QC-CR#2049138</a></td> + <td>ПП</td> + <td>Средний</td> + <td>WLAN</td> + </tr> + <tr> + <td>CVE-2017-18052</td> + <td>A-70237712<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=c04c4870bd86a5f878553d7acf207388f3d6c3bd"> +QC-CR#2119439</a></td> + <td>РИ</td> + <td>Средний</td> + <td>WLAN</td> + </tr> + <tr> + <td>CVE-2017-18057</td> + <td>A-70237709<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=24d41d2bd3d98325b3800345f4ba27a334b3894b"> +QC-CR#2119403</a></td> + <td>РИ</td> + <td>Средний</td> + <td>WLAN</td> + </tr> + <tr> + <td>CVE-2017-18059</td> + <td>A-70237708<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=217705da7726002ffe61dad51a6c9cc97c52f649"> +QC-CR#2119399</a></td> + <td>РИ</td> + <td>Средний</td> + <td>WLAN</td> + </tr> + <tr> + <td>CVE-2017-18060</td> + <td>A-70237707<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=f3d81bd0b3cb992c214d94196b33168b02589c6b"> +QC-CR#2119394</a></td> + <td>РИ</td> + <td>Средний</td> + <td>WLAN</td> + </tr> + <tr> + <td>CVE-2017-18051</td> + <td>A-70237696<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=38fba6a9f6ca3c7bf0c4c1bd84fa2b89fbcaeb93"> +QC-CR#2119442</a></td> + <td>РИ</td> + <td>Средний</td> + <td>WLAN</td> + </tr> + <tr> + <td>CVE-2017-18053</td> + <td>A-70237695<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=da1c6e996ac7635c202296e31118f088f9427947"> +QC-CR#2119434</a></td> + <td>РИ</td> + <td>Средний</td> + <td>WLAN</td> + </tr> + <tr> + <td>CVE-2017-18058</td> + <td>A-70237690<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=d6d42a10d4abf09299cdfacdd8aed5c26731b5ff"> +QC-CR#2119401</a></td> + <td>РИ</td> + <td>Средний</td> + <td>WLAN</td> + </tr> + <tr> + <td>CVE-2017-15855</td> + <td>A-38232131<a href="#asterisk">*</a><br /> + QC-CR#2139514</td> + <td>РИ</td> + <td>Средний</td> + <td>Драйвер Camera_v2</td> + </tr> + <tr> + <td>CVE-2017-15814</td> + <td>A-64836865<a href="#asterisk">*</a><br /> + QC-CR#2092793</td> + <td>РИ</td> + <td>Средний</td> + <td>Драйвер Camera_v2</td> + </tr> +</tbody></table> + +<h2 id="functional-updates">Ð£Ð»ÑƒÑ‡ÑˆÐµÐ½Ð¸Ñ Ñ„ÑƒÐ½ÐºÑ†Ð¸Ð¾Ð½Ð°Ð»ÑŒÐ½Ñ‹Ñ… возможноÑтей</h2> +<p> +Ð’ Ñти Ð¾Ð±Ð½Ð¾Ð²Ð»ÐµÐ½Ð¸Ñ Ð²ÐºÐ»ÑŽÑ‡ÐµÐ½Ñ‹ иÑÐ¿Ñ€Ð°Ð²Ð»ÐµÐ½Ð¸Ñ Ð¿Ñ€Ð¾Ð±Ð»ÐµÐ¼, каÑающихÑÑ Ñ„ÑƒÐ½ÐºÑ†Ð¸Ð¾Ð½Ð°Ð»ÑŒÐ½Ñ‹Ñ… возможноÑтей уÑтройÑтв Pixel. Они не ÑвÑзаны Ñ ÑƒÑзвимоÑÑ‚Ñми в защите. Ð’ таблице приведены ÑÑылки, ÐºÐ°Ñ‚ÐµÐ³Ð¾Ñ€Ð¸Ñ Ð¾Ð±Ð½Ð¾Ð²Ð»ÐµÐ½Ð¸Ñ, например Bluetooth или мобильный Интернет, и опиÑание улучшениÑ. +</p> + +<table> + <tbody><tr> + <th>СÑылки</th> + <th>КатегориÑ</th> + <th>ОпиÑание</th> + <th>УÑтройÑтва</th> + </tr> + <tr> + <td>A-70491468</td> + <td>ПроизводительноÑÑ‚ÑŒ</td> + <td>Улучшено включение Ñкрана при разблокировке Ñ Ð¿Ð¾Ð¼Ð¾Ñ‰ÑŒÑŽ отпечатка пальца.</td> + <td>Pixel 2, Pixel 2XL</td> + </tr> + <tr> + <td>A-69307875</td> + <td>Ðудио</td> + <td>Улучшено качеÑтво аудиозапиÑи при видеоÑъемке.</td> + <td>Pixel 2XL</td> + </tr> + <tr> + <td>A-70641186</td> + <td>Отчеты</td> + <td>Улучшены отчеты о ÑбоÑÑ….</td> + <td>Pixel 2, Pixel 2XL</td> + </tr> +</tbody></table> + +<h2 id="common-questions-and-answers">ЧаÑто задаваемые вопроÑÑ‹</h2> +<p> +Ð’ Ñтом разделе мы отвечаем на вопроÑÑ‹, которые могут возникнуть поÑле Ð¿Ñ€Ð¾Ñ‡Ñ‚ÐµÐ½Ð¸Ñ Ð±ÑŽÐ»Ð»ÐµÑ‚ÐµÐ½Ñ. +</p> +<p> +<strong>1. Как определить, уÑтановлено ли на уÑтройÑтво обновление, в котором уÑтранены перечиÑленные проблемы? +</strong> +</p> +<p> +Ð’ иÑправлении от 5 марта 2018 года или более новом уÑтранены вÑе проблемы, ÑвÑзанные Ñ Ð¾Ð±Ð½Ð¾Ð²Ð»ÐµÐ½Ð¸ÐµÐ¼ 2018-03-05. Информацию о том, как проверить Ð¾Ð±Ð½Ð¾Ð²Ð»ÐµÐ½Ð¸Ñ ÑиÑтемы безопаÑноÑти, можно найти в <a href="https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices">Справочном центре</a>. +</p> +<p id="type"> +<strong>2. Что означают ÑÐ¾ÐºÑ€Ð°Ñ‰ÐµÐ½Ð¸Ñ Ð² Ñтолбце <em>Тип</em>?</strong> +</p> +<p> +Ð’ Ñтом Ñтолбце указан тип уÑзвимоÑти по Ñледующей клаÑÑификации:<em></em> +</p> +<table> + <colgroup><col width="25%" /> + <col width="75%" /> + </colgroup><tbody><tr> + <th>Сокращение</th> + <th>ОпиÑание</th> + </tr> + <tr> + <td>УВК</td> + <td>Удаленное выполнение кода</td> + </tr> + <tr> + <td>ПП</td> + <td>Повышение привилегий</td> + </tr> + <tr> + <td>РИ</td> + <td>РаÑкрытие информации</td> + </tr> + <tr> + <td>ОО</td> + <td>Отказ в обÑлуживании</td> + </tr> + <tr> + <td>Ð/Д</td> + <td>КлаÑÑÐ¸Ñ„Ð¸ÐºÐ°Ñ†Ð¸Ñ Ð½ÐµÐ´Ð¾Ñтупна</td> + </tr> +</tbody></table> +<p> +<strong>3. Ðа что указывают запиÑи в Ñтолбце <em>СÑылки</em>?</strong> +</p> +<p> +Ð’ таблицах Ñ Ð¾Ð¿Ð¸Ñанием уÑзвимоÑтей еÑÑ‚ÑŒ Ñтолбец <em>СÑылки</em>. ÐšÐ°Ð¶Ð´Ð°Ñ Ð·Ð°Ð¿Ð¸ÑÑŒ в нем может Ñодержать префикÑ, указывающий на иÑточник ÑÑылки, а именно: +</p> +<table> + <colgroup><col width="25%" /> + <col width="75%" /> + </colgroup><tbody><tr> + <th>ПрефикÑ</th> + <th>Значение</th> + </tr> + <tr> + <td>A-</td> + <td>Идентификатор ошибки Android</td> + </tr> + <tr> + <td>QC-</td> + <td>СÑылочный номер Qualcomm</td> + </tr> + <tr> + <td>M-</td> + <td>СÑылочный номер MediaTek</td> + </tr> + <tr> + <td>N-</td> + <td>СÑылочный номер NVIDIA</td> + </tr> + <tr> + <td>B-</td> + <td>СÑылочный номер Broadcom</td> + </tr> +</tbody></table> +<p id="asterisk"> +<strong>4. Что означает значок * Ñ€Ñдом Ñ Ð¸Ð´ÐµÐ½Ñ‚Ð¸Ñ„Ð¸ÐºÐ°Ñ‚Ð¾Ñ€Ð¾Ð¼ ошибки Android в Ñтолбце <em>СÑылки</em>?</strong> +</p> +<p> +Символ * означает, что иÑправление Ð´Ð»Ñ ÑƒÑзвимоÑти не опубликовано.<em></em> Ðеобходимое обновление ÑодержитÑÑ Ð² поÑледних бинарных драйверах Ð´Ð»Ñ ÑƒÑтройÑтв Nexus, которые можно Ñкачать на <a href="https://developers.google.com/android/nexus/drivers">Ñайте Ð´Ð»Ñ Ñ€Ð°Ð·Ñ€Ð°Ð±Ð¾Ñ‚Ñ‡Ð¸ÐºÐ¾Ð²</a>. +</p> +<p> +<strong>5. Почему теперь одни уÑзвимоÑти опиÑываютÑÑ Ð² Ñтом бюллетене, а другие – в бюллетенÑÑ… по безопаÑноÑти Android?</strong> +</p> +<p> +Ð’ бюллетене по безопаÑноÑти Android опиÑаны уÑзвимоÑти, которые необходимо уÑтранить в поÑледнем обновлении ÑиÑтемы безопаÑноÑти Ð´Ð»Ñ ÑƒÑтройÑтв Android. Решать дополнительные проблемы, перечиÑленные здеÑÑŒ, Ð´Ð»Ñ Ñтого не требуетÑÑ. +</p> +<h2 id="versions">ВерÑии</h2> +<table> + <colgroup><col width="25%" /> + <col width="25%" /> + <col width="50%" /> + </colgroup><tbody><tr> + <th>ВерÑиÑ</th> + <th>Дата</th> + <th>ПримечаниÑ</th> + </tr> + <tr> + <td>1.0</td> + <td>5 марта 2018 г.</td> + <td>Бюллетень опубликован.</td> + </tr> +</tbody></table> + +</body></html>
\ No newline at end of file diff --git a/ru/security/bulletin/pixel/2018.html b/ru/security/bulletin/pixel/2018.html index e969c997..36a4edba 100644 --- a/ru/security/bulletin/pixel/2018.html +++ b/ru/security/bulletin/pixel/2018.html @@ -34,16 +34,42 @@ <th>Обновление ÑиÑтемы безопаÑноÑти</th> </tr> <tr> - <td><a href="/security/bulletin/pixel/2018-01-01.html">Январь 2018 г.</a></td> + <td><a href="/security/bulletin/pixel/2018-03-01.html">Март 2018 г.</a></td> <td>ГотовитÑÑ Ðº публикации <!-- - <a href="/security/bulletin/pixel/2018-01-01.html">English</a> / - <a href="/security/bulletin/pixel/2018-01-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/pixel/2018-01-01.html?hl=ko">í•œêµì–´</a> / - <a href="/security/bulletin/pixel/2018-01-01.html?hl=ru">руÌÑÑкий</a> / - <a href="/security/bulletin/pixel/2018-01-01.html?hl=zh-cn">ä¸æ–‡ (ä¸å›½)</a> / - <a href="/security/bulletin/pixel/2018-01-01.html?hl=zh-tw">ä¸æ–‡ (å°ç£)</a> + <a href="/security/bulletin/pixel/2018-03-01.html">English</a> / + <a href="/security/bulletin/pixel/2018-03-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/pixel/2018-03-01.html?hl=ko">í•œêµì–´</a> / + <a href="/security/bulletin/pixel/2018-03-01.html?hl=ru">руÌÑÑкий</a> / + <a href="/security/bulletin/pixel/2018-03-01.html?hl=zh-cn">ä¸æ–‡ (ä¸å›½)</a> / + <a href="/security/bulletin/pixel/2018-03-01.html?hl=zh-tw">ä¸æ–‡ (å°ç£)</a> --> </td> + <td>Март 2018 г.</td> + <td>2018-03-05</td> + </tr> + <tr> + <td><a href="/security/bulletin/pixel/2018-02-01.html">Февраль 2018 г.</a></td> + <td> + <a href="/security/bulletin/pixel/2018-02-01.html">English</a> / +<a href="/security/bulletin/pixel/2018-02-01.html?hl=ja">日本語</a> / +<a href="/security/bulletin/pixel/2018-02-01.html?hl=ko">í•œêµì–´</a> / +<a href="/security/bulletin/pixel/2018-02-01.html?hl=ru">руÑÑкий</a> / +<a href="/security/bulletin/pixel/2018-02-01.html?hl=zh-cn">ä¸æ–‡Â (ä¸å›½)</a> / +<a href="/security/bulletin/pixel/2018-02-01.html?hl=zh-tw">ä¸æ–‡Â (å°ç£)</a> + </td> + <td>Февраль 2018 г.</td> + <td>2018-02-05</td> + </tr> + <tr> + <td><a href="/security/bulletin/pixel/2018-01-01.html">Январь 2018 г.</a></td> + <td> + <a href="/security/bulletin/pixel/2018-01-01.html">English</a> / +<a href="/security/bulletin/pixel/2018-01-01.html?hl=ja">日本語</a> / +<a href="/security/bulletin/pixel/2018-01-01.html?hl=ko">í•œêµì–´</a> / +<a href="/security/bulletin/pixel/2018-01-01.html?hl=ru">руÑÑкий</a> / +<a href="/security/bulletin/pixel/2018-01-01.html?hl=zh-cn">ä¸æ–‡Â (ä¸å›½)</a> / +<a href="/security/bulletin/pixel/2018-01-01.html?hl=zh-tw">ä¸æ–‡Â (å°ç£)</a> + </td> <td>Январь 2018 г.</td> <td>2018-01-05</td> </tr> diff --git a/zh-cn/_book.yaml b/zh-cn/_book.yaml index 3a319893..b17b73a1 100644 --- a/zh-cn/_book.yaml +++ b/zh-cn/_book.yaml @@ -2,70 +2,70 @@ upper_tabs: - lower_tabs: other: - contents: + - path: /setup/ + title: 概览 - section: - - path: /setup/ - title: 概览 - - path: /setup/code-lines + - path: /setup/start/codelines title: 代ç è¡Œã€åˆ†æ”¯å’Œç‰ˆæœ¬ - - path: /setup/build-numbers + - path: /setup/start/build-numbers title: 代å·ã€æ ‡ç¾å’Œç‰ˆæœ¬å· - - path: /setup/roles + - path: /setup/start/roles title: 项目角色 - - path: /setup/brands + - path: /setup/start/brands title: å“牌使用准则 - - path: /setup/licenses + - path: /setup/start/licenses title: è®¸å¯ - - path: /setup/faqs + - path: /setup/start/faqs title: 常è§é—®é¢˜è§£ç” - - path: /setup/site-updates + - path: /setup/start/site-updates title: ç½‘ç«™åŠ¨æ€ title: 开始使用 - section: - - path: /setup/requirements + - path: /setup/build/requirements title: è¦æ±‚ - - path: /setup/initializing + - path: /setup/build/initializing title: æ建编译环境 - - path: /setup/downloading + - path: /setup/build/downloading title: 下载æºä»£ç - - path: /setup/building + - path: /setup/build/building title: 准备编译 - - path: /setup/jack + - path: /setup/build/jack title: 使用 Jack 编译 - - path: /setup/devices + - path: /setup/build/devices title: 使用å‚考开å‘æ¿ - - path: /setup/running + - path: /setup/build/running title: è¿è¡Œç‰ˆæœ¬ - - path: /setup/building-kernels + - path: /setup/build/building-kernels title: ç¼–è¯‘å†…æ ¸ - - path: /setup/known-issues + - path: /setup/build/known-issues title: 已知问题 title: 下载和编译 - section: - - path: /setup/developing + - path: /setup/develop/ title: 概览 - - path: /setup/using-repo + - path: /setup/develop/repo title: 使用 Repo - - path: /setup/add-device + - path: /setup/develop/new-device title: æ·»åŠ æ–°è®¾å¤‡ - - path: /setup/64-bit-builds + - path: /setup/develop/64-bit-builds title: 了解 64 ä½ç‰ˆæœ¬ title: å¼€å‘ - section: - - path: /setup/contributing + - path: /setup/contribute/ title: 概览 - - path: /setup/life-of-a-patch + - path: /setup/contribute/life-of-a-patch title: è¡¥ä¸ç¨‹åºçš„生命周期 - - path: /setup/submit-patches + - path: /setup/contribute/submit-patches title: æ交补ä¸ç¨‹åº - - path: /setup/view-patches + - path: /setup/contribute/view-patches title: 查看补ä¸ç¨‹åº - - path: /setup/life-of-a-bug + - path: /setup/contribute/life-of-a-bug title: Bug 的生命周期 - - path: /setup/report-bugs + - path: /setup/contribute/report-bugs title: 报告 Bug - - path: /setup/read-bug-reports + - path: /setup/contribute/read-bug-reports title: 阅读 Bug 报告 - - path: /setup/code-style + - path: /setup/contribute/code-style title: Java 代ç æ ·å¼è§„则 title: åšå‡ºè´¡çŒ® - path: /setup/community @@ -85,6 +85,8 @@ upper_tabs: title: 实现安全性 - path: /security/overview/updates-resources title: æ›´æ–°å’Œèµ„æº + - path: /security/overview/reports + title: 报告 - section: - path: /security/enhancements/ title: 概览 @@ -976,21 +978,7 @@ upper_tabs: - path: /reference/tradefed/ title: 软件包索引 title: 测试基础架构 - - section: - - path: /devices/tech/vts/ - title: 概览 - - path: /devices/tech/test_infra/tradefed/fundamentals/vts - title: 使用 VTS 进行系统测试 - - path: /devices/tech/vts/setup - title: VTS ä¿¡æ¯ä¸å¿ƒè®¾ç½® - - path: /devices/tech/vts/database - title: VTS ä¿¡æ¯ä¸å¿ƒæ•°æ®åº“ - - path: /devices/tech/vts/ui - title: VTS ä¿¡æ¯ä¸å¿ƒç•Œé¢ - - path: /devices/tech/vts/performance - title: 性能测试 - title: 供应商测试套件 (VTS) - name: 调整 + name: 微调 name: 调整 - lower_tabs: other: @@ -1043,6 +1031,20 @@ upper_tabs: title: 兼容性测试套件 - path: /compatibility/contact-us title: 与我们è”ç³» + - section: + - path: /compatibility/vts/ + title: 概览 + - path: /compatibility/vts/systems + title: 使用 VTS 进行系统测试 + - path: /compatibility/vts/setup + title: VTS ä¿¡æ¯ä¸å¿ƒè®¾ç½® + - path: /compatibility/vts/database + title: VTS ä¿¡æ¯ä¸å¿ƒæ•°æ®åº“ + - path: /compatibility/vts/ui + title: VTS ä¿¡æ¯ä¸å¿ƒç•Œé¢ + - path: /compatibility/vts/performance + title: 性能测试 + title: 供应商测试套件 (VTS) name: 兼容性 name: 兼容性 - lower_tabs: diff --git a/zh-cn/_index.yaml b/zh-cn/_index.yaml index ff30e0de..1a4025d6 100644 --- a/zh-cn/_index.yaml +++ b/zh-cn/_index.yaml @@ -54,6 +54,12 @@ landing_page: image_path: /images/android_stack.png - heading: æ–°é—» items: + - heading: 2017 å¹´ Android 年度回顾 + description: > + 2017 å¹´ Android 安全年度回顾介ç»äº† 2017 å¹´ Android 安全方é¢æ‰€å‘生的一切。 + buttons: + - label: 2018 å¹´ 3 月 15 æ—¥ + path: /security/overview/reports - heading: 3 月安全公告 description: > 2018 å¹´ 3 月的 Android å’Œ Pixel/Nexus 安全公告已ç»å‘布，其ä¸æ供了与 3 月安全更新补ä¸ç›¸å…³çš„ä¿¡æ¯ã€‚ @@ -67,12 +73,6 @@ landing_page: buttons: - label: 2018 å¹´ 1 月 19 æ—¥ path: /devices/tech/dalvik/dalvik-bytecode - - heading: Android 8.1 版说明 - description: > - Android 8.1 版现已推出，其ä¸æ供了许多é¢å‘è®¾å¤‡åˆ¶é€ å•†ä»¥åŠä¸ªäººç”¨æˆ·çš„新功能。 - buttons: - - label: 2017 å¹´ 12 月 5 æ—¥ - path: /setup/site-updates#Dec-2017 - classname: devsite-landing-row-100 tf-row-centered items: - buttons: diff --git a/zh-cn/compatibility/cts/audio-framework.html b/zh-cn/compatibility/cts/audio-framework.html index a592cbe7..f4e17252 100644 --- a/zh-cn/compatibility/cts/audio-framework.html +++ b/zh-cn/compatibility/cts/audio-framework.html @@ -20,7 +20,7 @@ limitations under the License. --> -<p>这套新测试需è¦äººä¸ºå¹²é¢„，并会用到一些外部硬件，包括<a href="#loopback_latency">回环æ’头</a>ã€<a href="#audio_frequency_speaker_test">USB å‚照麦克风</a>å’Œ<a href="#audio_frequency_microphone_test">外部扬声器</a>。对于没有 3.5 毫米 (â…›") 耳机端å£çš„è®¾å¤‡ï¼Œç”¨æˆ·å°†èƒ½å¤Ÿè·³è¿‡æµ‹è¯•å¹¶å°†å…¶æ ‡è®°ä¸ºæˆåŠŸã€‚有关详情，请å‚阅以下部分。</p> +<p>这套新测试需è¦äººä¸ºå¹²é¢„，并会用到一些外部硬件（包括<a href="#loopback_latency">回环æ’头</a>ã€<a href="#audio_frequency_speaker_test">USB å‚照麦克风</a>å’Œ<a href="#audio_frequency_microphone_test">外部扬声器</a>）。对于没有 3.5 毫米 (â…›") 耳机端å£çš„è®¾å¤‡ï¼Œç”¨æˆ·å°†èƒ½å¤Ÿè·³è¿‡æµ‹è¯•å¹¶å°†å…¶æ ‡è®°ä¸ºæˆåŠŸã€‚有关详情，请å‚阅以下部分。</p> <h2 id="loopback_latency">回环æ’头延迟测试</h2> @@ -330,8 +330,7 @@ </td> </tr> <tr> - <td>按通过（仅在æˆåŠŸæ—¶å¯ç”¨ï¼‰æˆ–失败按钮以记录结果。 -如果 DUT 未定义音频频å“未处ç†åŠŸèƒ½ï¼Œåˆ™éœ€è¦è¿è¡Œæµ‹è¯•ï¼Œä½†ä¸å¼ºåˆ¶è¦æ±‚在所有测é‡ä¸å‡æˆåŠŸã€‚ + <td>按通过（仅在æˆåŠŸæ—¶å¯ç”¨ï¼‰æˆ–失败按钮以记录结果。如果 DUT 未定义音频频å“未处ç†åŠŸèƒ½ï¼Œåˆ™éœ€è¦è¿è¡Œæµ‹è¯•ï¼Œä½†ä¸å¼ºåˆ¶è¦æ±‚在所有测é‡ä¸å‡æˆåŠŸã€‚ </td> <td> <img src="/compatibility/cts/images/audio-framework53.png" alt="测试已通过" title="测试已通过"/> diff --git a/zh-cn/compatibility/cts/setup.html b/zh-cn/compatibility/cts/setup.html index 33826948..874127f7 100644 --- a/zh-cn/compatibility/cts/setup.html +++ b/zh-cn/compatibility/cts/setup.html @@ -140,7 +140,7 @@ ro.product.first_api_level=21 <p class="warning"><strong>è¦å‘Šï¼š</strong>这将清空设备ä¸çš„所有用户数æ®ã€‚</p> </li><li>将设备的è¯è¨€è®¾ç½®ä¸ºè‹±è¯ï¼ˆ<strong>美国</strong>）：<strong>设置 > è¯è¨€å’Œè¾“入法 > è¯è¨€</strong> </li><li>如果设备具有 GPS 或 WLAN/移动网络功能，则打开ä½ç½®ä¿¡æ¯è®¾ç½®ï¼š<strong>设置 > ä½ç½®ä¿¡æ¯ > å¼€å¯</strong> - </li><li>连接到满足以下è¦æ±‚çš„ WLAN ç½‘ç»œï¼šæ”¯æŒ IPv6，å¯ä»¥å°†è¢«æµ‹è®¾å¤‡ (DUT) 视为隔离的客户端（请å‚阅上文的<a href="#physical_environment">物ç†çŽ¯å¢ƒ</a>部分），并å¯ä»¥è¿žæŽ¥åˆ°äº’è”网：<strong>设置 > WLAN</strong><em></em> + </li><li>连接到满足以下è¦æ±‚çš„ WLAN ç½‘ç»œï¼šæ”¯æŒ IPv6，å¯ä»¥å°†è¢«æµ‹è®¾å¤‡ (DUT) 视为隔离的客户端<em></em>（请å‚阅上文的<a href="#physical_environment">物ç†çŽ¯å¢ƒ</a>部分），并å¯è¿žæŽ¥åˆ°äº’è”网：<strong>设置 > WLAN</strong> </li><li>ç¡®ä¿è®¾å¤‡ä¸Šæœªè®¾ç½®é”定图案或密ç ：<strong>设置 > 安全 > å±å¹•é”定 > æ— </strong> </li><li>在设备上å¯ç”¨ <strong>USB 调试</strong>：<strong>设置 > å¼€å‘者选项 > USB 调试</strong>。 <p class="note"><strong>注æ„：</strong>在 Android 4.2 åŠæ›´é«˜ç‰ˆæœ¬ä¸ï¼Œé»˜è®¤æƒ…况下会éšè—<strong>å¼€å‘者选项</strong>。è¦æ˜¾ç¤ºè¿™äº›é€‰é¡¹ï¼Œè¯·ä¾æ¬¡è½¬åˆ°<strong>设置 > 关于手机</strong>，然åŽç‚¹æŒ‰<strong>版本å·</strong>七次。返回上一å±å¹•ä»¥æŸ¥æ‰¾<strong>å¼€å‘者选项</strong>。è¦æŸ¥çœ‹å…¶ä»–详细信æ¯ï¼Œè¯·å‚阅<a href="http://developer.android.com/studio/run/device.html#developer-device-options">å¯ç”¨è®¾å¤‡ä¸Šçš„å¼€å‘者选项</a>。</p> @@ -156,7 +156,7 @@ ro.product.first_api_level=21 <p class="note"><strong>注æ„：</strong>对于 CTS 版本 2.1 R2 至 4.2 R4ï¼Œè¯·é€šè¿‡ä»¥ä¸‹å‘½ä»¤è®¾ç½®æ‚¨çš„è®¾å¤‡ï¼ˆæˆ–æ¨¡æ‹Ÿå™¨ï¼‰ï¼Œä»¥ä¾¿æ‰§è¡Œæ— éšœç¢æµ‹è¯•ï¼š<br /> <code>adb install -r android-cts/repository/testcases/CtsDelegatingAccessibilityService.apk</code><br /> 在设备上，ä¾æ¬¡å¯ç”¨ï¼š<strong>设置 > æ— éšœç¢ > æ— éšœç¢ > Delegating Accessibility Service</strong></p> -<p class="note"><strong>注æ„</strong>：对于 7.0 之å‰çš„ CTS 版本，请在声明 <code>android.software.device_admin</code> 的设备上，使用以下命令设置您的设备，以便执行设备管ç†æµ‹è¯•ï¼š<br /> +<p class="note"><strong>注æ„：</strong>对于 7.0 之å‰çš„ CTS 版本，请在声明 <code>android.software.device_admin</code> 的设备上，使用以下命令设置您的设备，以便执行设备管ç†æµ‹è¯•ï¼š<br /> <code>adb install -r android-cts/repository/testcases/CtsDeviceAdmin.apk</code><br /> </p><p> ä¾æ¬¡é€‰æ‹©â€œè®¾ç½®â€>“安全â€>“设备管ç†å™¨â€ï¼Œç„¶åŽå¯ç”¨ä¸¤ä¸ª <code>android.deviceadmin.cts.CtsDeviceAdminReceiver*</code> 设备管ç†å™¨ã€‚ç¡®ä¿ <code>android.deviceadmin.cts.CtsDeviceAdminDeactivatedReceiver</code> å’Œä»»ä½•å…¶ä»–é¢„åŠ è½½çš„è®¾å¤‡ç®¡ç†å™¨å‡ä¿æŒåœç”¨çŠ¶æ€ã€‚ diff --git a/zh-cn/compatibility/vts/database.html b/zh-cn/compatibility/vts/database.html new file mode 100644 index 00000000..f3370fe7 --- /dev/null +++ b/zh-cn/compatibility/vts/database.html @@ -0,0 +1,118 @@ +<html devsite><head> + <title>VTS ä¿¡æ¯ä¸å¿ƒæ•°æ®åº“</title> + <meta name="project_path" value="/_project.yaml"/> + <meta name="book_path" value="/_book.yaml"/> + </head> + <body> + <!-- + Copyright 2017 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 + + http://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> +è¦æƒ³ä¸ºä¸€ä¸ªå¯æ‰©å±•ã€æ€§èƒ½å“越且高度çµæ´»çš„æŒç»é›†æˆä¿¡æ¯ä¸å¿ƒæ供支æŒï¼Œå°±å¿…须在充分了解数æ®åº“功能的å‰æ下精心设计 VTS ä¿¡æ¯ä¸å¿ƒåŽç«¯ã€‚ +<a href="https://cloud.google.com/datastore/docs/" class="external">Google Cloud Datastore</a> 是一个 NoSQL æ•°æ®åº“，æ供事务性 ACID ä¿è¯ï¼Œå¯ç¡®ä¿æœ€ç»ˆä¸€è‡´æ€§ä»¥åŠå®žä½“组内的高一致性。ä¸è¿‡ï¼Œå…¶ç»“构与 SQL æ•°æ®åº“（甚至是 Cloud Bigtable）大相径åºï¼Œå› 为它使用的是ç§ç±»ã€å®žä½“和属性（而éžè¡¨æ ¼ã€è¡Œå’Œå•å…ƒæ ¼ï¼‰ã€‚ +</p> +<p> +以下部分将概è¦ä»‹ç»ç”¨äºŽä¸º VTS ä¿¡æ¯ä¸å¿ƒç½‘络æœåŠ¡åˆ›å»ºé«˜æ•ˆåŽç«¯çš„æ•°æ®ç»“构和查询模å¼ã€‚ +</p> + +<h2 id="entities">实体</h2> +<p> +以下实体会å˜å‚¨æ¥è‡ª VTS 测试è¿è¡Œçš„摘è¦å’Œèµ„æºï¼š +</p> +<ul> +<li><strong>测试实体</strong>。测试实体会å˜å‚¨ä¸Žç‰¹å®šæµ‹è¯•çš„测试è¿è¡Œç›¸å…³çš„元数æ®ã€‚测试实体的键是测试å称，其属性包括自è¦æŠ¥ä½œä¸šå¯¹å…¶è¿›è¡Œæ›´æ–°ä»¥æ¥çš„失败计数ã€é€šè¿‡è®¡æ•°å’Œæµ‹è¯•ç”¨ä¾‹ä¸æ–情况列表。</li> +<li><strong>测试è¿è¡Œå®žä½“</strong>。测试è¿è¡Œå®žä½“包å«ç”±ç‰¹å®šæµ‹è¯•çš„è¿è¡Œäº§ç”Ÿçš„元数æ®ã€‚它必须å˜å‚¨ä»¥ä¸‹ä¿¡æ¯ï¼šæµ‹è¯•çš„开始时间戳和结æŸæ—¶é—´æˆ³ã€æµ‹è¯•ç‰ˆæœ¬å·ã€é€šè¿‡åŠå¤±è´¥çš„测试用例数ã€è¿è¡Œç±»åž‹ï¼ˆå¦‚æ交å‰ã€æ交åŽæˆ–本地）ã€æ—¥å¿—链接列表ã€ä¸»æœºå称以åŠè¦†ç›–率摘è¦è®¡æ•°ã€‚</li> +<li><strong>设备信æ¯å®žä½“</strong>。设备信æ¯å®žä½“包å«æœ‰å…³æµ‹è¯•è¿è¡ŒæœŸé—´æ‰€ç”¨è®¾å¤‡çš„详细信æ¯ã€‚具体而言，它包å«è®¾å¤‡ç‰ˆæœ¬å·ã€äº§å“å称ã€ç¼–è¯‘ç›®æ ‡ã€åˆ†æ”¯å’Œ ABI ä¿¡æ¯ã€‚系统会将该实体与测试è¿è¡Œå®žä½“分开å˜å‚¨ï¼Œä»¥ä¾¿é€šè¿‡ä¸€å¯¹å¤šçš„æ–¹å¼æ”¯æŒå¤šè®¾å¤‡æµ‹è¯•è¿è¡Œã€‚</li> +<li><strong>分æžç‚¹è¿è¡Œå®žä½“</strong>。分æžç‚¹è¿è¡Œå®žä½“会汇总在测试è¿è¡Œä¸é’ˆå¯¹ç‰¹å®šåˆ†æžç‚¹æ”¶é›†çš„æ•°æ®ã€‚它会é˜æ˜Žåˆ†æžæ•°æ®çš„è½´æ ‡ç¾ã€åˆ†æžç‚¹å称ã€å€¼ã€ç±»åž‹å’Œå›žå½’模å¼ã€‚</li> +<li><strong>覆盖率实体</strong>。覆盖率实体会é˜æ˜Žé’ˆå¯¹ä¸€ä¸ªæ–‡ä»¶æ”¶é›†çš„覆盖率数æ®ã€‚å®ƒåŒ…å« GIT 项目信æ¯ã€æ–‡ä»¶è·¯å¾„以åŠæºæ–‡ä»¶ä¸æ¯è¡Œçš„覆盖率计数列表。</li> +<li><strong>测试用例è¿è¡Œå®žä½“</strong>。测试用例è¿è¡Œå®žä½“会é˜æ˜Žæ¥è‡ªæµ‹è¯•è¿è¡Œçš„特定测试用例的结果，包括测试用例å称åŠå…¶ç»“果。</li> +<li><strong>用户收è—实体</strong>。æ¯ä»½ç”¨æˆ·è®¢é˜…都å¯é‡‡ç”¨ä»¥ä¸‹å®žä½“表示：包å«å¯¹æµ‹è¯•çš„引用以åŠç”± App 引擎用户æœåŠ¡ç”Ÿæˆçš„用户 IDã€‚è¿™æ ·ä¾¿å¯å®žçŽ°é«˜æ•ˆçš„åŒå‘查询（å³ï¼šæŸ¥è¯¢è®¢é˜…æŸé¡¹æµ‹è¯•çš„所有用户以åŠæŸä¸ªç”¨æˆ·æ”¶è—的所有测试）。</li> +</ul> + +<h2 id="entity-grouping">实体分组</h2> +<p> +æ¯ä¸ªæµ‹è¯•æ¨¡å—éƒ½è¡¨ç¤ºä¸€ä¸ªå®žä½“ç»„çš„æ ¹ã€‚æµ‹è¯•è¿è¡Œå®žä½“既是该组的å项，也是与å„自的测试和测试è¿è¡Œç¥–先实体相关的设备实体ã€åˆ†æžç‚¹å®žä½“和覆盖率实体的父项。 +</p> + +<img src="images/treble_vts_dash_entity_ancestry.png"/> +<figcaption><strong>图 1</strong>. æµ‹è¯•å®žä½“ç¥–å…ˆæ ‘çŠ¶å›¾ã€‚</figcaption> + +<p class="key-point"><strong>è¦ç‚¹</strong>：设计祖先实体关系时，您必须在æ供高效且一致的查询机制与éµå®ˆç”±æ•°æ®åº“强制实施的é™åˆ¶ä¹‹é—´å–得平衡。 +</p> + +<h3 id="benefits">优势</h3> +<p> +对一致性的è¦æ±‚æ—¢å¯ç¡®ä¿åŽç»çš„æ“作在事务æ交之å‰æ— 法得知其影å“，也å¯ç¡®ä¿å½“å‰çš„æ“作å¯ä»¥äº†è§£è¿‡åŽ»çš„事务。在 Cloud Datastore ä¸ï¼Œå®žä½“分组å¯åœ¨ç»„内创建具有很高的读写一致性的岛（在这ç§æƒ…况下，å³æ˜¯ä¸Žæµ‹è¯•æ¨¡å—相关的所有测试è¿è¡Œå’Œæ•°æ®ï¼‰ã€‚实体分组具有以下优势： +</p> +<ul> +<li>å¯å°†è¦æŠ¥ä½œä¸šå¯¹æµ‹è¯•æ¨¡å—状æ€çš„读å–和更新视为原åæ“作</li> +<li>å¯åœ¨æµ‹è¯•æ¨¡å—ä¸ä»¥æœ‰ä¿è¯çš„一致视图呈现测试用例结果</li> +<li>å¯åœ¨ç¥–å…ˆå®žä½“æ ‘ä¸æ›´å¿«é€Ÿåœ°æŸ¥è¯¢</li> +</ul> + +<h3 id="limitations">é™åˆ¶</h3> +<p> +ä¸å»ºè®®ä»¥è¶…过æ¯ç§’ 1 个实体的速度å‘å®žä½“ç»„å†™å…¥å®žä½“ï¼Œå› ä¸ºè¿‡å¿«çš„å†™å…¥æ“作å¯èƒ½ä¼šè¢«æ‹’ç»ã€‚åªè¦è¦æŠ¥ä½œä¸šå’Œä¸Šä¼ æ“作以ä¸è¶…过æ¯ç§’ 1 次写入的速度å‘生，结构就是稳定的，并且å¯ä»¥ä¿è¯å¾ˆé«˜çš„一致性。 +</p> +<p> +å½’æ ¹ç»“åº•ï¼Œæ¯ä¸ªæµ‹è¯•æ¨¡å—æ¯ç§’ 1 次写入的上é™æ˜¯åˆç†çš„ï¼Œå› ä¸ºæµ‹è¯•è¿è¡Œé€šå¸¸éƒ½éœ€è¦è‡³å°‘ 1 分钟的时间（包括 VTS 框架的开销）；除éžåŒæ—¶åœ¨è¶…过 60 å°ä¸åŒçš„主机上一致地执行æŸé¡¹æµ‹è¯•ï¼Œå¦åˆ™ä¸ä¼šå‡ºçŽ°å†™å…¥ç“¶é¢ˆé—®é¢˜ã€‚æ¤å¤–，鉴于æ¯ä¸ªæ¨¡å—都是测试计划（通常需è¦è¿è¡Œ 1 å°æ—¶ä»¥ä¸Šï¼‰çš„一部分，瓶颈问题就更ä¸å¯èƒ½ä¼šå‡ºçŽ°äº†ã€‚å³ä½¿å› 多å°ä¸»æœºåŒæ—¶è¿è¡Œæµ‹è¯•è€Œå¯¼è‡´å¯¹ç›¸åŒä¸»æœºçš„写入æ“作çŸæ—¶æš´å¢žï¼Œä¹Ÿèƒ½è½»æ¾å¤„ç†ç›¸å…³å¼‚常情况（例如，通过æ•èŽ·å†™å…¥é”™è¯¯å¹¶é‡è¯•ï¼‰ã€‚ +</p> + +<h3 id="scaling">扩展规模时的注æ„事项</h3> +<p> +测试è¿è¡Œå¹¶ä¸ä¸€å®šéœ€è¦å°†æµ‹è¯•ä½œä¸ºçˆ¶é¡¹ï¼ˆä¾‹å¦‚，它å¯ä»¥ä½¿ç”¨å…¶ä»–键，并将测试å称和测试开始时间作为属性）；虽然这ä»ä¼šå®žçŽ°æœ€ç»ˆä¸€è‡´æ€§ï¼Œå´ç‰ºç‰²äº†é«˜ä¸€è‡´æ€§ã€‚例如，è¦æŠ¥ä½œä¸šå¯èƒ½æ— 法查看测试模å—ä¸æœ€è¿‘执行的å„项测试è¿è¡Œçš„相互一致快照；这æ„味ç€ï¼Œå…¨å±€çŠ¶æ€å¯èƒ½æ— 法完全准确地æ述测试è¿è¡Œçš„åºåˆ—。这也å¯èƒ½ä¼šå½±å“测试è¿è¡Œåœ¨å•ä¸ªæµ‹è¯•æ¨¡å—ä¸çš„显示（未必是è¿è¡Œåºåˆ—çš„ä¸€è‡´å¿«ç…§ï¼‰ã€‚æœ€ç»ˆï¼Œå¿«ç…§ä¼šæ˜¯ä¸€è‡´çš„ï¼Œä½†æ— æ³•ä¿è¯æœ€æ–°æ•°æ®äº¦æ˜¯å¦‚æ¤ã€‚ +</p> + +<h2 id="test-cases">测试用例</h2> +<p> +å¦ä¸€ä¸ªæ½œåœ¨ç“¶é¢ˆæ˜¯å…·æœ‰å¾ˆå¤šæµ‹è¯•ç”¨ä¾‹çš„大型测试。两项æ“作é™åˆ¶åˆ†åˆ«æ˜¯ï¼šå®žä½“组内的写入åžåé‡ä¸Šé™ä¸ºæ¯ç§’ 1 个，事务大å°ä¸Šé™ä¸º 500 个实体。 +</p> +<p> +一ç§æ–¹æ³•æ˜¯æŒ‡å®šä¸€ä¸ªå°†æµ‹è¯•è¿è¡Œä½œä¸ºç¥–先实体的测试用例（类似于覆盖率数æ®ã€åˆ†æžæ•°æ®å’Œè®¾å¤‡ä¿¡æ¯çš„å˜å‚¨æ–¹å¼ï¼‰ï¼š +</p> +<img src="images/treble_vts_descend_not.png"/> +<figcaption><strong>图 2</strong>. æºè‡ªæµ‹è¯•è¿è¡Œçš„测试用例（ä¸æŽ¨è）。</figcaption> + +<p>虽然这ç§æ–¹æ³•å¯ä»¥æ供原åæ€§å’Œä¸€è‡´æ€§ï¼Œä½†ä¹Ÿä¼šå¯¹æµ‹è¯•æ–½åŠ è¯¸å¤šå¼ºç¡¬é™åˆ¶ï¼šå¦‚果事务的上é™æ˜¯ 500 个实体，则测试的测试用例数ä¸å¾—超过 498 个（å‡è®¾æ— 覆盖率数æ®æˆ–分æžæ•°æ®ï¼‰ã€‚如果测试è¦è¶…过这一é™åˆ¶ï¼Œå•ä¸ªäº‹åŠ¡ä¾¿æ— 法一次性写入所有测试用例结果，而如果将测试用例分到ä¸åŒçš„事务ä¸ï¼Œåˆ™å¯èƒ½ä¼šè¶…出æ¯ç§’ 1 次è¿ä»£çš„实体组写入åžåé‡ä¸Šé™ã€‚由于这ç§è§£å†³æ–¹æ¡ˆæ— 法在ä¸å½±å“性能的å‰æä¸‹å¾ˆå¥½åœ°æ‰©å±•ï¼Œå› æ¤ä¸å»ºè®®ä½¿ç”¨ã€‚ +</p> + +<p> +ä¸è¿‡ï¼Œæ‚¨å¯ä»¥å•ç‹¬å˜å‚¨æµ‹è¯•ç”¨ä¾‹å¹¶å°†å…¶é”®æ供给测试è¿è¡Œï¼Œè€Œæ— 需将测试用例结果作为测试è¿è¡Œçš„å项进行å˜å‚¨ï¼ˆæµ‹è¯•è¿è¡ŒåŒ…å«å…¶æµ‹è¯•ç”¨ä¾‹å®žä½“çš„æ ‡è¯†ç¬¦åˆ—è¡¨ï¼‰ï¼š +</p> + +<img src="images/treble_vts_descend.png"/> +<figcaption><strong>图 3</strong>. å•ç‹¬å˜å‚¨çš„测试用例（推è）。</figcaption> + +<p> +ä¹ä¸€çœ‹ï¼Œè¿™ä¼¼ä¹Žç ´å了对较高一致性的ä¿è¯ã€‚ä¸è¿‡ï¼Œå¦‚果客户端具有测试è¿è¡Œå®žä½“å’Œæµ‹è¯•ç”¨ä¾‹æ ‡è¯†ç¬¦åˆ—è¡¨ï¼Œåˆ™æ— éœ€æž„å»ºæŸ¥è¯¢ï¼›å®ƒå¯ä»¥ç›´æŽ¥æŒ‰æ ‡è¯†ç¬¦èŽ·å–测试用例，而这ç§æ–¹æ³•å§‹ç»ˆéƒ½èƒ½ä¿è¯ä¸€è‡´æ€§ã€‚è¿™ç§æ–¹æ³•å¤§å¤§å‡è½»äº†å¯¹æµ‹è¯•è¿è¡Œå¯å…·æœ‰çš„测试用例数的é™åˆ¶ï¼ŒåŒæ—¶ä¹Ÿå¯åœ¨ä¸ä¼šå¯¼è‡´å®žä½“组内过多写入的情况下获得很高的一致性。 +</p> + +<h2 id="patterns">æ•°æ®è®¿é—®æ¨¡å¼</h2> +<p> +VTS ä¿¡æ¯ä¸å¿ƒé‡‡ç”¨ä»¥ä¸‹æ•°æ®è®¿é—®æ¨¡å¼ï¼š +</p> +<ul> +<li><strong>用户收è—</strong>。您å¯é€šè¿‡ä»¥ä¸‹æ–¹å¼æŸ¥è¯¢ç”¨æˆ·æ”¶è—：在将特定 App Engine 用户对象作为属性的用户收è—实体上使用ç‰å¼è¿‡æ»¤å™¨ã€‚</li> +<li><strong>测试列表</strong>。测试列表是对测试实体的简å•æŸ¥è¯¢ã€‚è¦æƒ³å‡å°‘呈现首页所需的带宽，您å¯ä½¿ç”¨ä¼°æµ‹å€¼æ¥ä½“现通过计数和失败计数，以便略过包å«å¤±è´¥çš„测试用例 ID 以åŠè¦æŠ¥ä½œä¸šæ‰€ç”¨çš„其他元数æ®çš„潜在长列表。</li> +<li><strong>测试è¿è¡Œ</strong>。è¦æƒ³æŸ¥è¯¢æµ‹è¯•è¿è¡Œå®žä½“，除了需è¦å¯¹é”®ï¼ˆæ—¶é—´æˆ³ï¼‰è¿›è¡ŒæŽ’åºï¼Œæ‚¨å¯èƒ½è¿˜éœ€è¦å¯¹æµ‹è¯•è¿è¡Œå±žæ€§ï¼ˆå¦‚版本å·ã€é€šè¿‡è®¡æ•°ç‰ï¼‰è¿›è¡Œè¿‡æ»¤ã€‚使用测试实体键执行祖先查询会使读å–结果具有很高的一致性。æ¤æ—¶ï¼Œæ‰€æœ‰æµ‹è¯•ç”¨ä¾‹ç»“æžœå‡å¯é€šè¿‡ä½¿ç”¨å˜å‚¨åœ¨æµ‹è¯•è¿è¡Œå±žæ€§ä¸çš„ ID 列表进行检索；数æ®å˜å‚¨åŒºèŽ·å–æ“作的性质亦å¯ä¿è¯ç›¸å…³ç»“果会具有很高的一致性。</li> +<li><strong>分æžæ•°æ®å’Œè¦†ç›–率数æ®</strong>。查询与æŸé¡¹æµ‹è¯•ç›¸å…³çš„分æžæ•°æ®æˆ–覆盖率数æ®æ—¶ï¼Œæ‚¨æ— 需检索任何其他测试è¿è¡Œæ•°æ®ï¼ˆä¾‹å¦‚，其他分æž/覆盖率数æ®ã€æµ‹è¯•ç”¨ä¾‹æ•°æ®ç‰ï¼‰ã€‚您既å¯å€ŸåŠ©ä½¿ç”¨æµ‹è¯•å’Œæµ‹è¯•è¿è¡Œå®žä½“键的祖先查询æ¥æ£€ç´¢æµ‹è¯•è¿è¡ŒæœŸé—´è®°å½•çš„所有分æžç‚¹ï¼Œä¹Ÿå¯é€šè¿‡æŒ‰åˆ†æžç‚¹å称或文件å过滤æ¥æ£€ç´¢å•ä¸ªåˆ†æžå®žä½“或覆盖率实体。鉴于祖先查询的性质，这ç§æ“作å¯ç¡®ä¿å¾ˆé«˜çš„一致性。</li> +</ul> + +<p> +有关这些数æ®æ¨¡å¼çš„实际界é¢å’Œå±å¹•æˆªå›¾çš„详细信æ¯ï¼Œè¯·å‚阅 <a href="ui.html">VTS ä¿¡æ¯ä¸å¿ƒç•Œé¢</a>。 +</p> + +</body></html>
\ No newline at end of file diff --git a/zh-cn/compatibility/vts/index.html b/zh-cn/compatibility/vts/index.html new file mode 100644 index 00000000..c995465c --- /dev/null +++ b/zh-cn/compatibility/vts/index.html @@ -0,0 +1,37 @@ +<html devsite><head> + <title>供应商测试套件 (VTS) 和基础架构</title> + <meta name="project_path" value="/_project.yaml"/> + <meta name="book_path" value="/_book.yaml"/> + </head> + <body> + <!-- + Copyright 2017 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 + + http://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>Android 供应商测试套件 (VTS) æ供了大é‡ç”¨äºŽ Android 测试的新功能，对由测试驱动的开å‘æµç¨‹èµ·åˆ°äº†ä¿ƒè¿›ä½œç”¨ã€‚为帮助 Android å¼€å‘社区与测试数æ®è¿›è¡Œäº¤äº’，Android O æ供了以下测试资æºï¼š</p> +<ul> +<li><a href="systems.html">使用 VTS 进行系统测试</a>。介ç»å¦‚何使用 VTS æ¥æµ‹è¯• Android 原生系统的实现情况ã€è®¾ç½®æµ‹è¯•çŽ¯å¢ƒï¼Œç„¶åŽä½¿ç”¨ VTS 方案æ¥æµ‹è¯•è¡¥ä¸ç¨‹åºã€‚</li> +<li><strong>VTS ä¿¡æ¯ä¸å¿ƒ</strong>。基于网页的界é¢ï¼Œç”¨äºŽæŸ¥çœ‹ VTS 结果，具体包括：<ul> + <li><a href="database.html">ä¿¡æ¯ä¸å¿ƒæ•°æ®åº“</a>。一个å¯ä¸ºæŒç»é›†æˆä¿¡æ¯ä¸å¿ƒæ供支æŒçš„å¯æ‰©å±•åŽç«¯ã€‚</li> + <li><a href="ui.html">ä¿¡æ¯ä¸å¿ƒç•Œé¢</a>。一个利用 Material Design 有效显示与测试结果ã€åˆ†æžå’Œè¦†ç›–率相关的信æ¯çš„统一界é¢ã€‚</li> + <li><a href="setup.html">ä¿¡æ¯ä¸å¿ƒè®¾ç½®</a>。有关如何设置和é…ç½® VTS ä¿¡æ¯ä¸å¿ƒçš„说明。</li> + </ul> +</li> +<li><a href="performance.html">binder å’Œ hwbinder 性能测试</a>。用于衡é‡åžåé‡å’Œå»¶è¿Ÿçš„工具。</li> +</ul> + +<p>如需了解详情，请å‚阅 developer.android.com 上的 <a href="https://codelabs.developers.google.com/codelabs/android-vts/#0" class="external">Android VTS v8.0 Codelab</a> å’Œ Google Developers æ供的 <a href="https://www.youtube.com/watch?v=7BX7oSHc7nk&list=PLWz5rJ2EKKc9JOMtoWWMJHFHgvXDoThva" class="external">Android VTS 产å“视频</a>。</p> + +</body></html>
\ No newline at end of file diff --git a/zh-cn/compatibility/vts/performance.html b/zh-cn/compatibility/vts/performance.html new file mode 100644 index 00000000..cd62aff1 --- /dev/null +++ b/zh-cn/compatibility/vts/performance.html @@ -0,0 +1,363 @@ +<html devsite><head> + <title>性能测试</title> + <meta name="project_path" value="/_project.yaml"/> + <meta name="book_path" value="/_book.yaml"/> + </head> + <body> + <!-- + Copyright 2017 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 + + http://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>Android 8.0 ä¸åŒ…å«ç”¨äºŽæµ‹è¯•åžåé‡å’Œå»¶è¿Ÿçš„ binder å’Œ hwbinder 性能测试。虽然有很多场景都å¯ç”¨äºŽæ£€æµ‹å¯å¯Ÿè§‰çš„性能问题，但è¿è¡Œæ¤ç±»åœºæ™¯å¯èƒ½ä¼šæ¯”较耗时，而且相应结果通常è¦åˆ°é›†æˆå®Œç³»ç»Ÿä¹‹åŽæ‰å¯èŽ·å¾—。借助 Android O ä¸æ供的性能测试，您å¯æ›´è½»æ¾åœ°åœ¨å¼€å‘过程ä¸è¿›è¡Œæµ‹è¯•ã€åŠæ—©å‘现严é‡é—®é¢˜ä»¥åŠæ”¹å–„用户体验。</p> + +<p>性能测试包括以下四个类别：</p> +<ul> +<li>binder åžåé‡ï¼ˆåœ¨ <code>system/libhwbinder/vts/performance/Benchmark_binder.cpp</code> ä¸æ供）</li> +<li>binder 延迟（在 <code>frameworks/native/libs/binder/tests/schd-dbg.cpp</code> ä¸æ供）</li> +<li>hwbinder åžåé‡ï¼ˆåœ¨ <code>system/libhwbinder/vts/performance/Benchmark.cpp</code> ä¸æ供）</li> +<li>hwbinder 延迟（在 <code>system/libhwbinder/vts/performance/Latency.cpp</code> ä¸æ供）</li> +</ul> + +<h2 id="about">关于 binder å’Œ hwbinder</h2> +<p>binder å’Œ hwbinder 都是 Android 进程间通信 (IPC) 基础架构，它们共用åŒä¸€ä¸ª Linux 驱动程åºï¼Œä½†åœ¨æœ¬è´¨ä¸Šå…·æœ‰ä»¥ä¸‹ä¸åŒä¹‹å¤„：</p> + +<table> +<tbody><tr> +<th>æ–¹é¢</th> +<th>binder</th> +<th>hwbinder</th> +</tr> + +<tr> +<td>用途</td> +<td>为框架æ供通用型 IPC 方案</td> +<td>与硬件通信</td> +</tr> + +<tr> +<td>属性</td> +<td>专门针对 Android 框架使用情景åšäº†ä¼˜åŒ–</td> +<td>开销少，延迟低</td> +</tr> + +<tr> +<td>更改å‰å°/åŽå°çš„调度ç–ç•¥</td> +<td>会</td> +<td>ä¸ä¼š</td> +</tr> + +<tr> +<td>ä¼ é€’å‚æ•°</td> +<td>使用由 Parcel 对象支æŒçš„åºåˆ—化</td> +<td>使用分散缓冲区，é¿å…å› å¤åˆ¶ Parcel åºåˆ—化所需数æ®è€Œäº§ç”Ÿå¼€é”€</td> +</tr> + +<tr> +<td>继承优先级</td> +<td>ä¸ä¼š</td> +<td>会</td> +</tr> + +</tbody></table> + +<h3 id="transactions">binder å’Œ hwbinder 进程</h3> +<p>Systrace å¯è§†åŒ–工具会以如下方å¼æ˜¾ç¤ºäº‹åŠ¡ï¼š</p> +<img src="images/treble_systrace_binder_processes.png"/> +<figcaption><strong>图 1.</strong> binder 进程的 Systrace å¯è§†åŒ–。</figcaption> + +<p>在上述示例ä¸ï¼š</p> +<ul> +<li>å›› (4) 个 schd-dbg 进程是客户端进程。</li> +<li>å›› (4) 个 binder 进程是æœåŠ¡å™¨è¿›ç¨‹ï¼ˆå称以 <strong>Binder</strong> 开头，且以åºåˆ—å·ç»“尾）。</li> +<li>æ¯ä¸ªå®¢æˆ·ç«¯è¿›ç¨‹å§‹ç»ˆéƒ½ä¼šä¸ŽæŸä¸ªæœåŠ¡å™¨è¿›ç¨‹ï¼ˆä¾›å…¶å®¢æˆ·ç«¯ä¸“用）é…对。</li> +<li>所有客户端-æœåŠ¡å™¨è¿›ç¨‹å¯¹å‡ç”±å†…æ ¸åŒæ—¶å•ç‹¬è°ƒåº¦ã€‚</li> +</ul> + +<p>在 CPU 1 ä¸ï¼Œæ“ä½œç³»ç»Ÿå†…æ ¸ä¼šè¿è¡Œå®¢æˆ·ç«¯ä»¥å‘出请求。然åŽï¼Œå®ƒä¼šå°½å¯èƒ½åœ°ä½¿ç”¨åŒä¸€ CPU 唤醒æœåŠ¡å™¨è¿›ç¨‹ã€å¤„ç†è¯·æ±‚，并会在处ç†å®Œè¯·æ±‚åŽåˆ‡æ¢å›žåŽŸçŽ¯å¢ƒã€‚</p> + +<h3 id="throughput-diffs">åžåé‡å’Œå»¶è¿Ÿ</h3> +<p>在ç†æƒ³çš„事务ä¸ï¼Œç”±äºŽå®¢æˆ·ç«¯è¿›ç¨‹å’ŒæœåŠ¡å™¨è¿›ç¨‹å¯ä»¥æ— ç¼åˆ‡æ¢ï¼Œåžåé‡æµ‹è¯•å’Œå»¶è¿Ÿæµ‹è¯•åœ¨ç”Ÿæˆçš„ä¿¡æ¯æ–¹é¢ä¸ä¼šæœ‰å¾ˆå¤§å·®å¼‚。ä¸è¿‡ï¼Œå¦‚æžœæ“ä½œç³»ç»Ÿå†…æ ¸åœ¨å¤„ç†æ¥è‡ªç¡¬ä»¶çš„ä¸æ–请求 (IRQ)ã€ç‰å¾…é”定，或åªæ˜¯é€‰æ‹©ä¸ç«‹å³å¤„ç†ä¿¡æ¯ï¼Œåˆ™å¯èƒ½ä¼šå½¢æˆå»¶è¿Ÿæ°”泡。</p> + +<img src="images/treble_latency_bubble.png"/> +<figcaption><strong>图 2.</strong> å› åžåé‡æµ‹è¯•ç»“果和延迟测试结果之间的差异而形æˆçš„延迟气泡。</figcaption> + +<p>åžåé‡æµ‹è¯•ä¼šç”Ÿæˆå¾ˆå¤šå…·æœ‰ä¸åŒæœ‰æ•ˆè´Ÿè·é‡çš„äº‹åŠ¡ï¼Œå› æ¤å¯ä»¥å¾ˆå¥½åœ°ä¼°ç®—常规事务时间（在最ç†æƒ³çš„æƒ…å†µä¸‹ï¼‰ä»¥åŠ binder å¯è¾¾åˆ°çš„最大åžåé‡ã€‚</p> + +<p>相比之下，延迟测试ä¸ä¼šå¯¹æœ‰æ•ˆè´Ÿè·æ‰§è¡Œä»»ä½•æ“作，以最大é™åº¦åœ°å‡å°‘常规事务时间。我们å¯ä»¥åˆ©ç”¨äº‹åŠ¡æ—¶é—´æ¥ä¼°ç®— binder 开销ã€å¯¹æœ€å的情况进行信æ¯ç»Ÿè®¡ï¼Œå¹¶è®¡ç®—那些在延迟方é¢è¾¾åˆ°æŒ‡å®šæˆªæ¢æ—¶é—´çš„事务所å 的比例。</p> + +<h3 id="priority-inversions">处ç†ä¼˜å…ˆçº§å€’ç½®</h3> +<p>如果优先级较高的线程在逻辑上需è¦ç‰å¾…优先级较低的线程，就会出现优先级倒置的问题。实时 (RT) 应用å˜åœ¨ä¼˜å…ˆçº§å€’置问题：</p> + +<img src="images/treble_priority_inv_rta.png"/> +<figcaption><strong>图 3.</strong> 实时应用ä¸çš„优先级倒置。</figcaption> + +<p>如果æŸä¸ªçº¿ç¨‹ä½¿ç”¨ Linux å®Œå…¨å…¬å¹³çš„è°ƒåº¦ç¨‹åº (CFS) 进行调度，则å³ä½¿å…¶ä»–线程的优先级较高，该线程也总会有机会è¿è¡Œã€‚å› æ¤ï¼Œé‡‡ç”¨ CFS 调度的应用会将优先级倒置作为一ç§é¢„期行为（而éžé—®é¢˜ï¼‰æ¥å¤„ç†ã€‚ä¸è¿‡ï¼Œå¦‚æžœ Android 框架需è¦ä½¿ç”¨ RT 调度，以ä¿è¯ä¼˜å…ˆçº§è¾ƒé«˜çš„线程的æƒé™ï¼Œåˆ™å¿…须先解决优先级倒置问题。</p> + +<p>binder 事务ä¸çš„优先级倒置示例（RT 线程在ç‰å¾… binder 线程æä¾›æœåŠ¡æ—¶åœ¨é€»è¾‘上被其他 CFS 线程阻塞）：</p> +<img src="images/treble_priority_inv_rta_blocked.png"/> +<figcaption><strong>图 4.</strong> 优先级倒置；被阻塞的实时线程。</figcaption> + +<p>è¦é¿å…出现阻塞情况，您å¯ä»¥åœ¨ binder 线程处ç†æ¥è‡ª RT 客户端的请求时，使用优先级继承暂时将 binder 线程å‡çº§åˆ° RT 线程。请注æ„，RT 调度的资æºæœ‰é™ï¼Œåº”谨慎使用。在具有 N 个 CPU 的系统ä¸ï¼Œå½“å‰ RT 线程的数é‡ä¸Šé™ä¹Ÿä¸º N；如果所有 CPU å‡å·²è¢«å…¶ä»– RT 线程å 用，则é¢å¤–çš„ RT 线程å¯èƒ½éœ€è¦ç‰å¾…ï¼ˆå› æ¤å°†è¶…出其截æ¢æ—¶é—´ï¼‰ã€‚<em></em><em></em></p> + +<p>è¦è§£å†³æ‰€æœ‰å¯èƒ½å‡ºçŽ°çš„优先级倒置问题，您å¯ä»¥é’ˆå¯¹ binder å’Œ hwbinder 使用优先级继承。ä¸è¿‡ï¼Œç”±äºŽ binder å¹¿æ³›ç”¨äºŽæ•´ä¸ªç³»ç»Ÿï¼Œå› æ¤ä¸º binder 事务å¯ç”¨ä¼˜å…ˆçº§ç»§æ‰¿å¯èƒ½ä¼šä½¿ç³»ç»Ÿä¸çš„ RT 线程数超过其所能处ç†çš„线程数。</p> + +<h2 id="throughput">è¿è¡Œåžåé‡æµ‹è¯•</h2> +<p>åžåé‡æµ‹è¯•æ˜¯é’ˆå¯¹ binder/hwbinder 事务åžåé‡è€Œè¿è¡Œçš„。在未过载的系统ä¸ï¼Œå»¶è¿Ÿæ°”泡很少，而且åªè¦è¿ä»£çš„次数足够多，就å¯ä»¥æ¶ˆé™¤å…¶å½±å“。</p> + +<ul> +<li><strong>binder</strong> åžåé‡æµ‹è¯•ä½äºŽ <code>system/libhwbinder/vts/performance/Benchmark_binder.cpp</code> 下。</li> +<li><strong>hwbinder</strong> åžåé‡æµ‹è¯•ä½äºŽ <code>system/libhwbinder/vts/performance/Benchmark.cpp</code> 下。</li> +</ul> + +<h3 id="throughput-results">测试结果</h3> +<p>针对使用ä¸åŒæœ‰æ•ˆè´Ÿè·é‡çš„事务的åžåé‡æµ‹è¯•ç»“果示例：</p> + +<pre class="prettyprint"> +Benchmark Time CPU Iterations +--------------------------------------------------------------------- +BM_sendVec_binderize/4 70302 ns 32820 ns 21054 +BM_sendVec_binderize/8 69974 ns 32700 ns 21296 +BM_sendVec_binderize/16 70079 ns 32750 ns 21365 +BM_sendVec_binderize/32 69907 ns 32686 ns 21310 +BM_sendVec_binderize/64 70338 ns 32810 ns 21398 +BM_sendVec_binderize/128 70012 ns 32768 ns 21377 +BM_sendVec_binderize/256 69836 ns 32740 ns 21329 +BM_sendVec_binderize/512 69986 ns 32830 ns 21296 +BM_sendVec_binderize/1024 69714 ns 32757 ns 21319 +BM_sendVec_binderize/2k 75002 ns 34520 ns 20305 +BM_sendVec_binderize/4k 81955 ns 39116 ns 17895 +BM_sendVec_binderize/8k 95316 ns 45710 ns 15350 +BM_sendVec_binderize/16k 112751 ns 54417 ns 12679 +BM_sendVec_binderize/32k 146642 ns 71339 ns 9901 +BM_sendVec_binderize/64k 214796 ns 104665 ns 6495 +</pre> + +<ul> +<li><strong>时间</strong>表示实时测é‡çš„往返延迟时间。 +</li> +<li><strong>CPU</strong> 表示调度 CPU 以进行测试的累计时间。</li> +<li><strong>è¿ä»£</strong>表示执行测试函数的次数。</li> +</ul> + +<p>以 8 å—节的有效负è·ä¸ºä¾‹ï¼š</p> + +<pre class="prettyprint"> +BM_sendVec_binderize/8 69974 ns 32700 ns 21296 +</pre> +<p>… binder å¯ä»¥è¾¾åˆ°çš„最大åžåé‡çš„计算公å¼ä¸ºï¼š</p> +<p><em>8 å—节有效负è·çš„最大åžåé‡ = (8 * 21296)/69974 ~= 2.423 b/ns ~= 2.268 Gb/s</em></p> + +<h3 id="throughput-options">测试选项</h3> +<p>è¦èŽ·å¾— .json æ ¼å¼çš„结果，请使用 <code>--benchmark_format=json</code> å‚æ•°è¿è¡Œæµ‹è¯•ï¼š</p> + +<pre class="prettyprint"> +<code class="devsite-terminal">libhwbinder_benchmark --benchmark_format=json</code> +{ + "context": { + "date": "2017-05-17 08:32:47", + "num_cpus": 4, + "mhz_per_cpu": 19, + "cpu_scaling_enabled": true, + "library_build_type": "release" + }, + "benchmarks": [ + { + "name": "BM_sendVec_binderize/4", + "iterations": 32342, + "real_time": 47809, + "cpu_time": 21906, + "time_unit": "ns" + }, + …. +} +</pre> + +<h2 id="latency">è¿è¡Œå»¶è¿Ÿæµ‹è¯•</h2> +<p>延迟测试å¯æµ‹é‡ä»¥ä¸‹äº‹é¡¹æ‰€èŠ±è´¹çš„时间：客户端开始åˆå§‹åŒ–事务ã€åˆ‡æ¢åˆ°æœåŠ¡å™¨è¿›ç¨‹è¿›è¡Œå¤„ç†ï¼Œä»¥åŠæŽ¥æ”¶ç»“果。æ¤å¤–，该测试还会查找å¯å¯¹äº‹åŠ¡å»¶è¿Ÿäº§ç”Ÿè´Ÿé¢å½±å“的已知ä¸è‰¯è°ƒåº¦ç¨‹åºè¡Œä¸ºï¼Œä¾‹å¦‚，调度程åºä¸æ”¯æŒä¼˜å…ˆçº§ç»§æ‰¿æˆ–ä¸æŽ¥å—åŒæ¥æ ‡è®°ã€‚</p> + +<ul> +<li>binder 延迟测试ä½äºŽ <code>frameworks/native/libs/binder/tests/schd-dbg.cpp</code> 下。</li> +<li>hwbinder 延迟测试ä½äºŽ <code>system/libhwbinder/vts/performance/Latency.cpp</code> 下。</li> +</ul> + +<h3 id="latency-results">测试结果</h3> +<p>测试结果（.json æ ¼å¼ï¼‰å°†æ˜¾ç¤ºæœ‰å…³å¹³å‡/最佳/最差延迟以åŠè¶…出截æ¢æ—¶é—´çš„次数的统计信æ¯ã€‚</p> + +<h3 id="latency-options">测试选项</h3> +<p>延迟测试采用以下选项：</p> + +<table> +<tbody><tr> +<th>命令</th> +<th>说明</th> +</tr> + +<tr> +<td><code>-i <em>value</em></code></td> +<td>指定è¿ä»£æ¬¡æ•°ã€‚</td> +</tr> + +<tr> +<td><code>-pair <em>value</em></code></td> +<td>指定进程对的数é‡ã€‚</td> +</tr> + +<tr> +<td><code>-deadline_us 2500</code></td> +<td>指定截æ¢æ—¶é—´ï¼ˆä»¥å¾®ç§’为å•ä½ï¼‰ã€‚</td> +</tr> + +<tr> +<td><code>-v</code></td> +<td>获å–详细的（调试）输出。</td> +</tr> + +<tr> +<td><code>-trace</code></td> +<td>在达到截æ¢æ—¶é—´æ—¶æš‚åœè·Ÿè¸ªã€‚</td> +</tr> + +</tbody></table> + +<p>ä»¥ä¸‹å‡ ä¸ªéƒ¨åˆ†ä¼šè¯¦ç»†ä»‹ç»æ¯ä¸ªé€‰é¡¹ï¼Œè¯´æ˜Žç›¸å…³ä½¿ç”¨æƒ…况，并æ供示例结果。</p> + +<h4 id="iterations">指定è¿ä»£</h4> +<p>具有大é‡è¿ä»£æ¬¡æ•°å¹¶åœç”¨äº†è¯¦ç»†è¾“出功能的结果示例：</p> + +<pre class="prettyprint"> +<code class="devsite-terminal">libhwbinder_latency -i 5000 -pair 3</code> +{ +"cfg":{"pair":3,"iterations":5000,"deadline_us":2500}, +"P0":{"SYNC":"GOOD","S":9352,"I":10000,"R":0.9352, + "other_ms":{ "avg":0.2 , "wst":2.8 , "bst":0.053, "miss":2, "meetR":0.9996}, + "fifo_ms": { "avg":0.16, "wst":1.5 , "bst":0.067, "miss":0, "meetR":1} +}, +"P1":{"SYNC":"GOOD","S":9334,"I":10000,"R":0.9334, + "other_ms":{ "avg":0.19, "wst":2.9 , "bst":0.055, "miss":2, "meetR":0.9996}, + "fifo_ms": { "avg":0.16, "wst":3.1 , "bst":0.066, "miss":1, "meetR":0.9998} +}, +"P2":{"SYNC":"GOOD","S":9369,"I":10000,"R":0.9369, + "other_ms":{ "avg":0.19, "wst":4.8 , "bst":0.055, "miss":6, "meetR":0.9988}, + "fifo_ms": { "avg":0.15, "wst":1.8 , "bst":0.067, "miss":0, "meetR":1} +}, +"inheritance": "PASS" +} +</pre> +<p>这些测试结果会显示以下信æ¯ï¼š</p> + +<dl> +<dt><strong><code>"pair":3</code></strong></dt> +<dd>创建一个客户端和æœåŠ¡å™¨å¯¹ã€‚</dd> + +<dt><strong><code>"iterations": 5000</code></strong></dt> +<dd>包括 5000 次è¿ä»£ã€‚</dd> + +<dt><strong><code>"deadline_us":2500</code></strong></dt> +<dd>截æ¢æ—¶é—´ä¸º 2500 微秒（2.5 毫秒）；大多数事务都应达到该值。</dd> + +<dt><strong><code>"I": 10000</code></strong></dt> +<dd>å•æ¬¡æµ‹è¯•è¿ä»£åŒ…括两 (2) 项事务：<ul> + <li>一项按照æ£å¸¸ä¼˜å…ˆçº§ (<code>CFS other</code>) 处ç†çš„事务</li> + <li>一项按照实时优先级 (<code>RT-fifo</code>) 处ç†çš„事务</li> +</ul>5000 次è¿ä»£ç›¸å½“于共计 10000 项事务。</dd> + +<dt><strong><code>"S": 9352</code></strong></dt> +<dd>9352 项事务会在åŒä¸€ä¸ª CPU ä¸è¿›è¡ŒåŒæ¥ã€‚</dd> + +<dt><strong><code>"R": 0.9352</code></strong></dt> +<dd>表示客户端和æœåŠ¡å™¨åœ¨åŒä¸€ä¸ª CPU ä¸ä¸€èµ·åŒæ¥çš„比例。</dd> + +<dt><strong><code>"other_ms":{ "avg":0.2 , "wst":2.8 , "bst":0.053, "miss":2, +"meetR":0.9996}</code></strong></dt> +<dd>ç”±æ£å¸¸ä¼˜å…ˆçº§è°ƒç”¨ç¨‹åºåˆ†å‘çš„æ‰€æœ‰äº‹åŠ¡çš„å¹³å‡ (<code>avg</code>)ã€æœ€å·® (<code>wst</code>) 和最佳 (<code>bst</code>) 情况。两个事务 <code>miss</code> 截æ¢æ—¶é—´ï¼Œä½¿å¾—è¾¾æ ‡çŽ‡ä¸º (<code>meetR</code>) 0.9996。</dd> + +<dt><strong><code>"fifo_ms": { "avg":0.16, "wst":1.5 , "bst":0.067, "miss":0, +"meetR":1}</code></strong></dt> +<dd>类似于 <code>other_ms</code>，但适用于由具有 <code>rt_fifo</code> 优先级的客户端分å‘的事务。<code>fifo_ms</code> 的结果很å¯èƒ½ï¼ˆä½†ä¸éœ€è¦ï¼‰ä¼˜äºŽ <code>other_ms</code>，且 <code>avg</code> å’Œ <code>wst</code> 值较低，而 <code>meetR</code> 则较高（如果考虑åŽå°ä¸çš„è´Ÿè·ï¼Œå…¶å·®å¼‚å¯èƒ½ä¼šæ›´å¤§ï¼‰ã€‚</dd> + +</dl> + +<p class="note"><strong>注æ„</strong>：åŽå°è´Ÿè·å¯èƒ½ä¼šå½±å“延迟测试ä¸çš„åžåé‡ç»“果和 <code>other_ms</code> 元组。åªè¦åŽå°è´Ÿè·çš„优先级低于 <code>RT-fifo</code>，就å¯èƒ½åªæœ‰ <code>fifo_ms</code> 会显示类似的结果。</p> + +<h4 id="pair-values">指定对值</h4> +<p>æ¯ä¸ªå®¢æˆ·ç«¯è¿›ç¨‹éƒ½ä¼šä¸Žå…¶ä¸“用的æœåŠ¡å™¨è¿›ç¨‹é…对，且æ¯ä¸€å¯¹éƒ½å¯èƒ½ä¼šç‹¬ç«‹è°ƒåº¦åˆ°ä»»ä½• CPU。ä¸è¿‡ï¼Œåªè¦åŒæ¥æ ‡è®°æ˜¯ <code>honor</code>，事务期间应该就ä¸ä¼šå‡ºçŽ° CPU è¿ç§»çš„情况。</p> + +<p>ç¡®ä¿ç³»ç»Ÿæ²¡æœ‰è¿‡è½½ï¼è™½ç„¶è¿‡è½½ç³»ç»Ÿä¸å»¶è¿Ÿè¾ƒé«˜æ˜¯æ£å¸¸çŽ°è±¡ï¼Œä½†æ˜¯é’ˆå¯¹è¿‡è½½ç³»ç»Ÿçš„测试结果并ä¸èƒ½æ供有用的信æ¯ã€‚è¦æµ‹è¯•åŽ‹åŠ›è¾ƒé«˜çš„系统，请使用 <code>-pair +#cpu-1</code>（或谨慎使用 <code>-pair #cpu</code>）。使用 <code>-pair <em>n</em></code> å’Œ <code><em>n</em> > #cpu</code> 进行测试会使系统过载，并生æˆæ— 用信æ¯ã€‚</p> + +<h4 id="deadline-values">指定截æ¢æ—¶é—´å€¼</h4> +<p>ç»è¿‡å¤§é‡ç”¨æˆ·åœºæ™¯æµ‹è¯•ï¼ˆåœ¨åˆæ ¼äº§å“上è¿è¡Œå»¶è¿Ÿæµ‹è¯•ï¼‰ï¼Œæˆ‘们决定将 2.5 毫秒定为需è¦æ»¡è¶³çš„截æ¢æ—¶é—´è¦æ±‚。对于具有更高è¦æ±‚的新应用（如æ¯ç§’ 1000 å¼ ç…§ç‰‡ï¼‰ï¼Œæ¤æˆªæ¢æ—¶é—´å€¼å°†å‘生å˜åŒ–。</p> + +<h4 id="verbose">指定详细输出</h4> +<p>使用 <code>-v</code> 选项显示详细输出。例如：</p> + +<pre class="devsite-click-to-copy"> +<code class="devsite-terminal">libhwbinder_latency -i 1 -v</code> + +<div style="color: orange">-------------------------------------------------- +service pid: 8674 tid: 8674 cpu: 1 +SCHED_OTHER 0</div> +-------------------------------------------------- +main pid: 8673 tid: 8673 cpu: 1 + +-------------------------------------------------- +client pid: 8677 tid: 8677 cpu: 0 +SCHED_OTHER 0 + +<div style="color: blue">-------------------------------------------------- +fifo-caller pid: 8677 tid: 8678 cpu: 0 +SCHED_FIFO 99 + +-------------------------------------------------- +hwbinder pid: 8674 tid: 8676 cpu: 0 +??? 99</div> +<div style="color: green">-------------------------------------------------- +other-caller pid: 8677 tid: 8677 cpu: 0 +SCHED_OTHER 0 + +-------------------------------------------------- +hwbinder pid: 8674 tid: 8676 cpu: 0 +SCHED_OTHER 0</div> +</pre> + +<ul> +<li><font style="color:orange">æœåŠ¡çº¿ç¨‹</font>使用 <code>SCHED_OTHER</code> 优先级创建，且与 <code>pid +8674</code> 一起在 <code>CPU:1</code> ä¸è¿è¡Œã€‚</li> +<li>éšåŽï¼Œ<font style="color:blue">第一个事务</font>ç”± <code>fifo-caller</code> å¯åŠ¨ã€‚为处ç†è¯¥äº‹åŠ¡ï¼Œhwbinder 会将æœåŠ¡å™¨ (<code>pid: 8674 tid: 8676</code>) 的优先级å‡çº§åˆ° 99，并使用瞬æ€è°ƒåº¦ç±»åˆ«ï¼ˆè¾“出为 <code>???</code>ï¼‰å¯¹å…¶è¿›è¡Œæ ‡è®°ã€‚æŽ¥ä¸‹æ¥ï¼Œè°ƒåº¦ç¨‹åºä¼šå°†æœåŠ¡å™¨è¿›ç¨‹ç½®äºŽ <code>CPU:0</code> ä¸ï¼Œä»¥è¿è¡Œè¯¥è¿›ç¨‹å¹¶å°†å®ƒä¸Žå…¶å®¢æˆ·ç«¯ä½¿ç”¨çš„åŒä¸€ CPU 进行åŒæ¥ã€‚</li> +<li><font style="color:green">第二个事务</font>调用程åºçš„优先级为 <code>SCHED_OTHER</code>。æœåŠ¡å™¨è‡ªè¡Œé™çº§å¹¶ä¸ºä¼˜å…ˆçº§ä¸º <code>SCHED_OTHER</code> 的调用程åºæä¾›æœåŠ¡ã€‚</li> +</ul> + +<h4 id="trace">使用跟踪记录进行调试</h4> +<p>您å¯ä»¥æŒ‡å®š <code>-trace</code> 选项æ¥è°ƒè¯•å»¶è¿Ÿé—®é¢˜ã€‚使用该选项时，延迟测试会在检测到ä¸è‰¯å»¶è¿Ÿæ—¶åœæ¢è·Ÿè¸ªæ—¥å¿—记录。例如：</p> + +<pre class="prettyprint"> +<code class="devsite-terminal">atrace --async_start -b 8000 -c sched idle workq binder_driver sync freq</code> +<code class="devsite-terminal">libhwbinder_latency -deadline_us 50000 -trace -i 50000 -pair 3</code> +deadline triggered: halt &mp; stop trace +log:/sys/kernel/debug/tracing/trace +</pre> + +<p>以下组件å¯èƒ½ä¼šå½±å“延迟：</p> + +<ul> +<li><strong>Android 编译模å¼</strong>。Eng 模å¼é€šå¸¸æ¯” Userdebug 模å¼é€Ÿåº¦æ…¢ã€‚</li> +<li><strong>框架</strong>。框架æœåŠ¡å¦‚何使用 <code>ioctl</code> æ¥é…ç½® binder？</li> +<li><strong>binder 驱动程åº</strong>。驱动程åºæ˜¯å¦æ”¯æŒç²¾ç»†é”定？驱动程åºæ˜¯å¦åŒ…å«æ‰€æœ‰æ€§èƒ½è°ƒæ•´è¡¥ä¸ç¨‹åºï¼Ÿ</li> +<li><strong>å†…æ ¸ç‰ˆæœ¬</strong>ã€‚å†…æ ¸çš„å®žæ—¶æ€§èƒ½è¶Šå¥½ï¼Œç»“æžœå°±è¶Šå¥½ã€‚</li> +<li><strong>å†…æ ¸é…ç½®</strong>ã€‚å†…æ ¸é…置是å¦åŒ…å« <code>DEBUG_PREEMPT</code> å’Œ <code>DEBUG_SPIN_LOCK</code> ç‰ <code>DEBUG</code> é…置？</li> +<li><strong>å†…æ ¸è°ƒåº¦ç¨‹åº</strong>ã€‚å†…æ ¸ä¸æ˜¯å¦å…·æœ‰ Energy-Aware è°ƒåº¦ç¨‹åº (EAS) æˆ–å¼‚æž„å¤šå¤„ç† (HMP) 调度程åºï¼Ÿæœ‰æ²¡æœ‰å†…æ ¸é©±åŠ¨ç¨‹åºï¼ˆ<code>cpu-freq</code> 驱动程åºã€<code>cpu-idle</code> 驱动程åºã€<code>cpu-hotplug</code> ç‰ï¼‰ä¼šå½±å“调度程åºï¼Ÿ</li> +</ul> + +</body></html>
\ No newline at end of file diff --git a/zh-cn/compatibility/vts/setup.html b/zh-cn/compatibility/vts/setup.html new file mode 100644 index 00000000..d6d6bfaa --- /dev/null +++ b/zh-cn/compatibility/vts/setup.html @@ -0,0 +1,126 @@ +<html devsite><head> + <title>VTS ä¿¡æ¯ä¸å¿ƒè®¾ç½®</title> + <meta name="project_path" value="/_project.yaml"/> + <meta name="book_path" value="/_book.yaml"/> + </head> + <body> + <!-- + Copyright 2017 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 + + http://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> +VTS ä¿¡æ¯ä¸å¿ƒæ供了用于查看æ¥è‡ª VTS æŒç»é›†æˆç³»ç»Ÿçš„测试结果的用户åŽç«¯å’Œç•Œé¢ (UI)。它利用测试状æ€é€šçŸ¥ç‰å·¥å…·ä¸ºç”±æµ‹è¯•é©±åŠ¨çš„å¼€å‘æ供支æŒï¼Œå¸®åŠ©å¼€å‘者在开å‘周期ä¸æ‰¾å‡ºå˜åœ¨å›žå½’问题的方é¢å¹¶åŠ 以预防（包括测试监控和分类支æŒï¼‰ã€‚ +</p> + +<p> +VTS ä¿¡æ¯ä¸å¿ƒçš„ç•Œé¢æ”¯æŒ VTS 基础架构æ供的功能（如原生代ç 覆盖），并通过æŒç»çš„性能监控，å助开å‘ç»è¿‡ä¼˜åŒ–且性能å“越的工具。 +</p> + +<h2 id="requirements">è¦æ±‚</h2> +<p> +è¦ä½¿ç”¨ VTS ä¿¡æ¯ä¸å¿ƒï¼Œæ‚¨å¿…须使用以下æœåŠ¡ï¼š +</p> +<ul> +<li><a href="https://maven.apache.org/" class="external">Apache Maven</a>，用于编译和部署</li> +<li><a href="https://cloud.google.com/appengine" class="external">Google Cloud App Engine</a>，用于网络æœåŠ¡æ‰˜ç®¡</li> +<li><a href="https://cloud.google.com/datastore/docs/" class="external">Google Cloud Datastore</a>，用于å˜å‚¨</li> +<li><a href="http://www.stackdriver.com/" class="external">Google Stackdriver</a>，用于监控</li> +</ul> + +<p> +è¦æŸ¥çœ‹<a href="ui.html#coverage">测试覆盖率</a>，您需è¦ä½¿ç”¨ä¸€ä¸ªä¸Žæºä»£ç æœåŠ¡å™¨ï¼ˆå¦‚ Gerrit）对接的 REST APIï¼Œè¿™æ ·ç½‘ç»œæœåŠ¡å°±å¯ä»¥æ ¹æ®çŽ°æœ‰è®¿é—®æŽ§åˆ¶åˆ—表æå–原始æºä»£ç 。 +</p> + +<h2 id="arch">架构</h2> +<p>VTS ä¿¡æ¯ä¸å¿ƒé‡‡ç”¨ä»¥ä¸‹æž¶æž„：</p> +<img src="images/treble_vts_dash_arch.png" title="VTS ä¿¡æ¯ä¸å¿ƒæž¶æž„"/> +<figcaption><strong>图 1</strong>. VTS ä¿¡æ¯ä¸å¿ƒæž¶æž„。</figcaption> + +<p>测试状æ€ç»“果通过 REST 接å£æŒç»ä¸Šä¼ 到 Cloud Datastore æ•°æ®åº“。VTS è¿è¡Œç¨‹åºä¼šè‡ªåŠ¨å¤„ç†ç»“果并利用 Protobuf æ ¼å¼å°†å®ƒä»¬åºåˆ—化。 +</p> +<p>网络 servlet 是用户的主è¦è®¿é—®ç‚¹ï¼Œå¯ä¼ é€å’Œå¤„ç†æ¥è‡ª Datastore æ•°æ®åº“çš„æ•°æ®ã€‚servlet åŒ…æ‹¬ï¼šç”¨äºŽä¼ é€æ‰€æœ‰æµ‹è¯•çš„ä¸»è¦ servlet；用于管ç†ç”¨æˆ·æ”¶è—çš„å好 servlet；用于填充测试表的结果 servlet；用于准备分æžæ•°æ®çš„图表 servlet；以åŠç”¨äºŽå‡†å¤‡å®¢æˆ·ç«¯çš„覆盖率数æ®çš„覆盖率 servlet。 +</p> +<p>æ¯ä¸ªæµ‹è¯•æ¨¡å—都有å„自的 Datastore ç¥–å…ˆå®žä½“æ ‘ï¼Œä¸”æµ‹è¯•ç»“æžœä¼šæ ¹æ®æµ‹è¯•å¼€å§‹æ—¶é—´çš„ Unix 时间戳编入索引。数æ®åº“ä¸çš„覆盖率数æ®ä¼šä½œä¸ºè®¡æ•°çŸ¢é‡ï¼ˆå³åŽŸå§‹æºä»£ç 文件ä¸çš„æ¯ä¸€è¡Œçš„计数矢é‡ï¼‰ä»¥åŠç”¨äºŽä»Žæºä»£ç æœåŠ¡å™¨æå‰æºä»£ç 的识别信æ¯éšæµ‹è¯•ç»“果一起å˜å‚¨ã€‚ +</p> +<p>通知æœåŠ¡è¿è¡Œæ—¶ä¼šä½¿ç”¨ä»»åŠ¡é˜Ÿåˆ—ã€è¯†åˆ«æµ‹è¯•ç”¨ä¾‹çŠ¶æ€å˜åŒ–以åŠå‘订阅者å‘出通知。状æ€ä¿¡æ¯å˜å‚¨åœ¨çŠ¶æ€è¡¨ä¸ï¼Œä»¥è·Ÿè¸ªæ•°æ®æ–°é²œåº¦å’ŒçŽ°æœ‰æ•…éšœã€‚è¿™æ ·ä¸€æ¥ï¼Œé€šçŸ¥æœåŠ¡ä¾¿å¯ä»¥æ供有关å„个测试用例故障和修å¤æƒ…况的丰富信æ¯ã€‚ +</p> + +<h2 id="code-structure">代ç 结构</h2> +<p>VTS ä¿¡æ¯ä¸å¿ƒåŸºæœ¬ç»„件包括在 Java ä¸å®žçŽ°çš„ servletã€å‰ç«¯ JSPã€CSS æ ·å¼è¡¨å’Œé…置文件。以下列表详细介ç»äº†è¿™äº›ç»„件的ä½ç½®å’Œè¯´æ˜Žï¼ˆæ‰€æœ‰è·¯å¾„å‡æŒ‡ç›¸å¯¹äºŽ <code>test/vts/web/dashboard</code> 的路径）：</p> +<ul> +<li><code>pom.xml</code><br />å…¶ä¸å®šä¹‰äº†çŽ¯å¢ƒå˜é‡å’Œä¾èµ–关系的设置文件。</li> +<li><code>src/main/java/com/android/vts/api/</code><br />包å«é€šè¿‡ REST 与数æ®è¿›è¡Œäº¤äº’的端点。</li> +<li><code>src/main/java/com/android/vts/entity/</code><br />åŒ…å« Datastore 实体的 Java 模型。</li> +<li><code>src/main/java/com/android/vts/proto/</code><br />包å«ç”¨äºŽ Protobuf çš„ Java 文件，其ä¸åŒ…括 <code>VtsReportMessage.java</code>（用于说明 VTS 测试结果的 Protobuf 类型的 Java 实现）。</li> +<li><code>src/main/java/com/android/vts/servlet/</code><br />包å«ç”¨äºŽ servlet çš„ Java 文件。</li> +<li><code>src/main/java/com/android/vts/util/</code><br />包å«ç”¨äºŽ servlet 所用实用函数和类的 Java 文件。</li> +<li><code>src/test/java/com/android/vts/</code><br />åŒ…å« servlet å’Œ utils çš„ç•Œé¢æµ‹è¯•ã€‚</li> +<li><code>src/main/webapp/</code><br />包å«ä¸Žç•Œé¢ç›¸å…³çš„文件（JSPã€CSSã€XML）：<ul> + <li><code>js/</code>：包å«ç½‘页使用的 JavaScript 文件。</li> + <li><code>WEB-INF/</code>：包å«é…置和界é¢æ–‡ä»¶ã€‚</li> + <li><code>jsp/</code>：包å«æ¯ä¸ªç½‘页的 JSP 文件。</li> + </ul> +</li> +<li><code>appengine-web.xml</code><br />环境å˜é‡åœ¨å…¶ä¸åŠ 载到å˜é‡ä¸çš„设置文件。</li> +<li><code>web.xml</code><br />å…¶ä¸å®šä¹‰äº† servlet æ˜ å°„å’Œå®‰å…¨é™åˆ¶çš„设置文件。</li> +<li><code>cron.xml</code><br />用于定义预定任务（å³é€šçŸ¥æœåŠ¡ï¼‰çš„设置文件。</li> +</ul> + +<h2 id="setup">设置信æ¯ä¸å¿ƒ</h2> +<p>è¦è®¾ç½® VTS ä¿¡æ¯ä¸å¿ƒï¼Œè¯·æ‰§è¡Œä»¥ä¸‹æ“作：</p> +<ol> +<li>创建 Google Cloud App Engine 项目，然åŽé€šè¿‡å®‰è£…以下å„项æ¥è®¾ç½®éƒ¨ç½²ä¸»æœºï¼š + <ul> + <li>Java 8</li> + <li>Google App Engine SDK</li> + <li>Maven</li> + </ul> +</li> +<li>在 Google Cloud API Manager ä¸ç”Ÿæˆ OAuth 2.0 客户端 ID。</li> +<li>创建æœåŠ¡å¸å·å’Œå¯†é’¥æ–‡ä»¶ã€‚</li> +<li>将电å邮件地å€æ·»åŠ 到 App Engine Email API 授æƒå‘件人列表。 +</li> +<li>设置 Google Analytics（分æžï¼‰å¸å·ã€‚</li> +<li>在信æ¯ä¸å¿ƒ <code>pom.xml</code> ä¸æŒ‡å®šçŽ¯å¢ƒå˜é‡ï¼š + <ul> + <li>使用 OAuth 2.0 ID（在第 2 æ¥ä¸ç”Ÿæˆï¼‰è®¾ç½®å®¢æˆ·ç«¯ ID。</li> + <li>使用密钥文件（在第 3 æ¥ä¸åˆ›å»ºï¼‰ä¸åŒ…å«çš„æ ‡è¯†ç¬¦è®¾ç½®æœåŠ¡å®¢æˆ·ç«¯ ID。</li> + <li>指定用于å‘é€æ醒的å‘件人电å邮件地å€ï¼ˆåœ¨ç¬¬ 4 æ¥ä¸æ·»åŠ ）。</li> + <li>指定将å‘å…¶å‘é€æ‰€æœ‰ç”µå邮件的电å邮件域å。</li> + <li>指定 Gerrit REST æœåŠ¡å™¨çš„地å€ã€‚</li> + <li>指定è¦ç”¨äºŽ Gerrit REST æœåŠ¡å™¨çš„ OAuth 2.0 范围。</li> + <li>指定 Google Analytics（分æžï¼‰ID（在第 5 æ¥ä¸è®¾ç½®ï¼‰ã€‚</li> + <li>编译和部署项目。</li> + </ul> +</li> +<li>在终端è¿è¡Œ <code>mvn clean appengine:update</code>。</li> +</ol> + +<p> +è¦è¯¦ç»†äº†è§£ä¿¡æ¯ä¸å¿ƒè®¾ç½®å’Œé…置，请å‚阅 <a href="https://codelabs.developers.google.com/codelabs/android-vts" class="external">Android VTS 代ç 实验室</a>。 +</p> + +<h2 id="security">安全注æ„事项</h2> +<p>è¦èŽ·å–å…¨é¢çš„覆盖率信æ¯ï¼Œéœ€è¦ç”¨åˆ°åŽŸå§‹æºä»£ç 。 +ä¸è¿‡ï¼Œéƒ¨åˆ†ä»£ç å¯èƒ½å±žäºŽæ•æ„Ÿä¿¡æ¯ï¼Œå‘å…¶æ·»åŠ é¢å¤–的网关å¯èƒ½ä¼šå¯¼è‡´çŽ°æœ‰è®¿é—®æŽ§åˆ¶åˆ—表é到利用。 +</p> +<p> +为了消除这ç§éšæ‚£ï¼Œä¿¡æ¯ä¸å¿ƒä¼šç›´æŽ¥å¤„ç†è¦†ç›–率矢é‡ï¼ˆå³æ‰§è¡Œè®¡æ•°çš„矢é‡ï¼›è¯¥çŸ¢é‡ä¼šæ˜ 射到æºä»£ç 文件ä¸çš„相应行），而ä¸æ˜¯æ供包å«è¦†ç›–率信æ¯çš„æºä»£ç 。除了覆盖率矢é‡ï¼Œä¿¡æ¯ä¸å¿ƒè¿˜ä¼šæŽ¥æ”¶ Git 项目å称和路径，以便客户端å¯ä»¥é€šè¿‡å¤–部æºä»£ç API æå–代ç 。客户端æµè§ˆå™¨æ”¶åˆ°è¿™äº›ä¿¡æ¯åŽï¼Œä¼šä½¿ç”¨ JavaScript çš„è·¨æºèµ„æºå…±äº« (CORS) æ¥æŸ¥è¯¢æºä»£ç æœåŠ¡å™¨æ˜¯å¦æœ‰ç›¸åº”的原始æºä»£ç ；收到的代ç 会与覆盖率矢é‡ç»“åˆä½¿ç”¨ä»¥ä¾¿åœ¨æµè§ˆå™¨ä¸æ˜¾ç¤ºè¿™ç§ä¿¡æ¯ã€‚ +</p> +<p> +è¿™ç§ç›´æŽ¥çš„方法ä¸ä¼šæ‰©å¤§å—攻击é¢ï¼Œå› 为信æ¯ä¸å¿ƒä¼šåˆ©ç”¨ç”¨æˆ·çš„ Cookie 对外部æœåŠ¡è¿›è¡Œèº«ä»½éªŒè¯ï¼ˆè¿™æ„味ç€æ— æƒç›´æŽ¥è®¿é—®æºä»£ç çš„ç”¨æˆ·å°†æ— æ³•åˆ©ç”¨ä¿¡æ¯ä¸å¿ƒæ¥æŸ¥çœ‹æ•æ„Ÿä¿¡æ¯ï¼‰ã€‚ +</p> + +</body></html>
\ No newline at end of file diff --git a/zh-cn/compatibility/vts/systems.html b/zh-cn/compatibility/vts/systems.html new file mode 100644 index 00000000..cf8a9dfd --- /dev/null +++ b/zh-cn/compatibility/vts/systems.html @@ -0,0 +1,96 @@ +<html devsite><head> + <title>使用 VTS 进行系统测试</title> + <meta name="project_path" value="/_project.yaml"/> + <meta name="book_path" value="/_book.yaml"/> + </head> + <body> + <!-- + Copyright 2017 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 + + http://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>供应商测试套件 (VTS) 会自动执行 HAL å’Œ OS å†…æ ¸æµ‹è¯•ã€‚è¦ä½¿ç”¨ VTS 测试 Android 原生系统的实现情况，请设置一个测试环境，然åŽä½¿ç”¨ VTS 计划测试相应补ä¸ã€‚</p> + +<h2 id="establish">建立测试环境</h2> +<p>è¦è®¾ç½®æµ‹è¯•çŽ¯å¢ƒï¼Œè¯·æŒ‰ä»¥ä¸‹æ¥éª¤æ“作：</p> +<ol> +<li>安装 Python å¼€å‘工具包： +<pre class="devsite-terminal devsite-click-to-copy"> +sudo apt-get install python-dev +</pre> +</li> +<li>安装å议缓冲区工具（适用于 Python）： +<pre class="devsite-click-to-copy"> +<code class="devsite-terminal">sudo apt-get install python-protobuf</code> +<code class="devsite-terminal">sudo apt-get install protobuf-compiler</code> +</pre> +</li> +<li>安装 Python 虚拟环境相关工具： +<pre class="devsite-click-to-copy"> +<code class="devsite-terminal">sudo apt-get install python-virtualenv</code> +<code class="devsite-terminal">sudo apt-get install python-pip</code> +</pre> +</li> +</ol> + +<h2 id="test">测试补ä¸</h2> +<p>è¦æµ‹è¯•è¡¥ä¸ï¼Œè¯·æŒ‰ä»¥ä¸‹æ¥éª¤æ“作：</p> +<ol> +<li>构建 VTS 主机端软件包： +<pre class="devsite-click-to-copy"> +<code class="devsite-terminal">. build/envsetup.sh</code> +<code class="devsite-terminal">lunch aosp_arm64-userdebug</code> +<code class="devsite-terminal">make vts -j</code> +</pre> +</li> +<li>è¿è¡Œé»˜è®¤çš„ VTS 测试： +<pre class="devsite-click-to-copy"> +<code class="devsite-terminal">vts-tradefed</code> +tf> run vts // where vts is the test plan name +</pre> +</li> +</ol> + +<h2 id="plans">VTS 计划</h2> +<p>å¯ç”¨çš„ VTS 测试计划包括：</p> + +<table> +<thead> +<tr> +<th>命令</th> +<th>说明</th> +</tr> +</thead> +<tbody> +<tr> +<td>> run vts</td> +<td>适用于默认的 VTS 测试</td> +</tr> +<tr> +<td>> run vts-hal</td> +<td>适用于默认的 VTS HAL（硬件抽象层）测试</td> +</tr> +<tr> +<td>> run vts-kernel</td> +<td>适用于默认的 VTS å†…æ ¸æµ‹è¯•</td> +</tr> +</tbody> +</table> + +<p>è¦æŸ¥çœ‹æ‰€æœ‰è®¡åˆ’的列表，请å‚阅 <code><a href="https://android.googlesource.com/platform/test/vts/+/master/tools/vts-tradefed/res/config/plans.md">/test/vts/tools/vts-tradefed/res/config.md</a></code>。</p> + +<h2 id="support">支æŒ</h2> +<p>您å¯ä»¥åœ¨ <code><a href=" https://android.googlesource.com/platform/test/vts/+/master/README.md">/test/vts/doc</a></code> 下查看用户手册。有关 VTS çš„é—®é¢˜ï¼Œè¯·åŠ å…¥ <a href="https://groups.google.com/forum/#!forum/android-vts">android-vts@googlegroups.com</a> 网上论å›ã€‚</p> + +</body></html>
\ No newline at end of file diff --git a/zh-cn/compatibility/vts/ui.html b/zh-cn/compatibility/vts/ui.html new file mode 100644 index 00000000..7b976ec2 --- /dev/null +++ b/zh-cn/compatibility/vts/ui.html @@ -0,0 +1,113 @@ +<html devsite><head> + <title>VTS ä¿¡æ¯ä¸å¿ƒç•Œé¢</title> + <meta name="project_path" value="/_project.yaml"/> + <meta name="book_path" value="/_book.yaml"/> + </head> + <body> + <!-- + Copyright 2017 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 + + http://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> +VTS ä¿¡æ¯ä¸å¿ƒæ供了一个利用 Material Design 有效显示与测试结果ã€åˆ†æžå’Œè¦†ç›–率相关的信æ¯çš„统一界é¢ã€‚ä¿¡æ¯ä¸å¿ƒæ ·å¼ä½¿ç”¨ Materialize CSS å’Œ jQueryUI ç‰å¼€æ”¾æºä»£ç JavaScript 库æ¥å¤„ç†ç”± Google App 引擎ä¸çš„ Java Servlet ä¼ é€çš„æ•°æ®ã€‚ +</p> + +<h2>ä¿¡æ¯ä¸å¿ƒé¦–页</h2> +<p> +ä¿¡æ¯ä¸å¿ƒé¦–页会显示相应用户已å‘收è—夹ä¸æ·»åŠ 的一系列测试套件。 +</p> +<img src="images/treble_vts_ui_main.png" title="VTS ä¿¡æ¯ä¸å¿ƒç€é™†é¡µ"/> +<figcaption><strong>图 1.</strong> VTS ä¿¡æ¯ä¸å¿ƒ - 首页。</figcaption> + +<p> +用户å¯åœ¨æ¤åˆ—表ä¸æ‰§è¡Œä»¥ä¸‹æ“作： +</p> +<ul> +<li>选择æŸä¸ªæµ‹è¯•å¥—件以查看该套件的结果。 +</li><li>点击<strong>全部显示</strong>以查看所有 VTS 测试å称。 +</li><li>选择<strong>编辑</strong>å›¾æ ‡ä»¥ä¿®æ”¹â€œæ”¶è—夹â€åˆ—表。<br /> +<img src="images/treble_vts_ui_favorites.png" title="VTS ä¿¡æ¯ä¸å¿ƒæ”¶è—夹"/> +<figcaption><strong>图 2.</strong> VTS ä¿¡æ¯ä¸å¿ƒ - 编辑“收è—夹â€é¡µé¢ã€‚</figcaption></li> +</ul> + +<h2 id="test-results">测试结果</h2> +<p> +测试结果会显示有关所选测试套件的最新信æ¯ï¼Œå…¶ä¸åŒ…括分æžç‚¹åˆ—表ã€æµ‹è¯•ç”¨ä¾‹ç»“果（按时间顺åºæŽ’åˆ—ï¼‰è¡¨æ ¼ï¼Œä»¥åŠç”¨æ¥æ˜¾ç¤ºæœ€æ–°è¿è¡Œç»“果细分的饼图（用户å¯é€šè¿‡å‘å³ç¿»é¡µæ¥åŠ 载先å‰çš„æ•°æ®ï¼‰ã€‚ +</p> + +<img src="images/treble_vts_ui_results.png" title="VTS ä¿¡æ¯ä¸å¿ƒç»“æžœ"/> +<figcaption><strong>图 3.</strong> VTS ä¿¡æ¯ä¸å¿ƒ - 测试结果。</figcaption> + +<p> +用户å¯é€šè¿‡ä½¿ç”¨æŸ¥è¯¢æˆ–修改测试类型（æ交å‰å’Œ/或æ交åŽï¼‰æ¥è¿‡æ»¤æ•°æ®ã€‚æœç´¢æŸ¥è¯¢æ”¯æŒé€šç”¨ä»¤ç‰Œå’Œç‰¹å®šäºŽå—段的é™å®šç¬¦ï¼›å—支æŒçš„æœç´¢å—段包括：设备版本å·ã€åˆ†æ”¯ã€ç›®æ ‡å称ã€è®¾å¤‡å称和测试版本å·ã€‚这些å—段å‡éœ€ä½¿ç”¨ä»¥ä¸‹æ ¼å¼è¿›è¡ŒæŒ‡å®šï¼šFIELD-ID<var></var>="SEARCH QUERY<var></var>"。引å·ç”¨äºŽå°†å¤šä¸ªå—è¯ä½œä¸ºå•ä¸ªä»¤ç‰Œä¸Žåˆ—ä¸çš„相应数æ®åŒ¹é…。 +</p> + +<h2 id="profiling">æ•°æ®åˆ†æž</h2> +<p> +用户å¯é€šè¿‡é€‰æ‹©ä¸€ä¸ªåˆ†æžç‚¹ï¼Œåœ¨<strong>线形图</strong>或<strong>直方图</strong>（示例如下）ä¸æŸ¥çœ‹è¯¥ç‚¹å¯¹åº”çš„é‡åŒ–æ•°æ®çš„交互å¼è§†å›¾ã€‚默认情况下，该视图会显示最新信æ¯ï¼›ç”¨æˆ·å¯ä»¥ä½¿ç”¨æ—¥æœŸé€‰æ‹©å™¨åŠ 载特定时间范围内的信æ¯ã€‚ +</p> +<img src="images/treble_vts_ui_performance.png" title="VTS ä¿¡æ¯ä¸å¿ƒæ€§èƒ½"/> +<figcaption><strong>图 4.</strong> VTS ä¿¡æ¯ä¸å¿ƒ - 性能线形图。 +</figcaption> +<p> +线形图会显示æŸä¸ªæ— åºæ€§èƒ½å€¼é›†åˆä¸çš„æ•°æ®ï¼›å½“æŸé¡¹æ€§èƒ½æµ‹è¯•ç”Ÿæˆä¸€ä¸ªä¸Žæ€§èƒ½å€¼ï¼ˆä¼šéšå¦ä¸€ä¸ªå˜é‡ï¼ˆå¦‚åžåé‡æˆ–ä¿¡æ¯å¤§å°ï¼‰è€Œå˜åŒ–并与之形æˆå‡½æ•°å…³ç³»ï¼‰å¯¹åº”的矢é‡æ—¶ï¼Œè¯¥å›¾ä¼šéžå¸¸æœ‰ç”¨ã€‚ +</p> +<img src="images/treble_vts_ui_histogram.png" title="VTS ä¿¡æ¯ä¸å¿ƒç›´æ–¹å›¾"/> +<figcaption><strong>图 5.</strong> VTS ä¿¡æ¯ä¸å¿ƒ - 性能直方图。</figcaption> + +<h2 id="coverage">测试覆盖率</h2> +<p> +用户å¯é€šè¿‡æµ‹è¯•ç»“æžœä¸çš„覆盖率百分比链接查看覆盖率信æ¯ã€‚ +</p> +<img src="images/treble_vts_ui_coverage.png" title="VTS ä¿¡æ¯ä¸å¿ƒè¦†ç›–率"/> +<figcaption> +<strong>图 6.</strong> VTS ä¿¡æ¯ä¸å¿ƒ - 覆盖率百分比。</figcaption> + +<p> +对于æ¯ä¸ªæµ‹è¯•ç”¨ä¾‹å’Œæºæ–‡ä»¶ï¼Œç”¨æˆ·éƒ½å¯æ ¹æ®æ‰€é€‰æµ‹è¯•æ供的覆盖率，查看一个包å«ç”¨ä¸åŒé¢œè‰²æ ‡è¯†çš„æºä»£ç çš„å¯æ‰©å±•å…ƒç´ ： +</p> +<img src="images/treble_vts_ui_coverage_source.png" title="VTS ä¿¡æ¯ä¸å¿ƒè¦†ç›–率æºä»£ç "/> +<figcaption> +<strong>图 7.</strong> VTS ä¿¡æ¯ä¸å¿ƒ - 覆盖率æºä»£ç 。</figcaption> + +<ul> +<li>未覆盖的行用<font style="color:red">红色</font>çªå‡ºæ˜¾ç¤ºã€‚</li> +<li>已覆盖的行用<font style="color:green">绿色</font>çªå‡ºæ˜¾ç¤ºã€‚</li> +<li>ä¸å¯æ‰§è¡Œçš„è¡Œ<strong>未ç€è‰²</strong>。</li> +</ul> + +<p> +覆盖率信æ¯å¯åˆ†ä¸ºä¸åŒçš„部分，具体å–决于其在è¿è¡Œæ—¶çš„æ供方å¼ã€‚测试å¯é€šè¿‡ä»¥ä¸‹æ–¹å¼ä¸Šä¼ 覆盖率信æ¯ï¼š +</p> +<ul> +<li><strong>按函数</strong>。å„éƒ¨åˆ†çš„æ ‡é¢˜å‡é‡‡ç”¨â€œCoverage: FUNCTION-NAME<var></var>â€æ ¼å¼ã€‚</li> +<li><strong>总计</strong>（在测试è¿è¡Œç»“æŸæ—¶æ供）。åªæ˜¾ç¤º 1 ä¸ªæ ‡é¢˜ï¼šâ€œCoverage: Allâ€ã€‚</li> +</ul> + +<p> +ä¿¡æ¯ä¸å¿ƒä¼šä»Žä½¿ç”¨å¼€æ”¾æºä»£ç <a href="https://gerrit-review.googlesource.com/Documentation/rest-api.html" class="external">Gerrit REST API</a> çš„æœåŠ¡å™¨å¤„获å–æºä»£ç 客户端。 +</p> + +<h2 id="monitor">监控和测试</h2> +<p> +VTS ä¿¡æ¯ä¸å¿ƒæ供以下监控和å•å…ƒæµ‹è¯•ã€‚ +</p> +<ul> +<li><strong>测试电å邮件è¦æŠ¥</strong>。è¦æŠ¥å‡æ˜¯åœ¨ä»¥ä¸¤ (2) 分钟的固定时间间隔执行的 Cron 作业ä¸è¿›è¡Œé…ç½®ã€‚è¯¥ä½œä¸šä¼šè¯»å– VTS 状æ€è¡¨ï¼Œä»¥ç¡®å®šæ–°æ•°æ®æ˜¯å¦å·²ä¸Šä¼ 到æ¯ä¸ªè¡¨æ ¼ä¸ - 方法是：检查测试的原始数æ®ä¸Šä¼ 时间戳是å¦æ¯”上次状æ€æ›´æ–°æ—¶é—´æˆ³æ–°ã€‚å¦‚æžœä¸Šä¼ æ—¶é—´æˆ³è¾ƒæ–°ï¼Œè¯¥ä½œä¸šä¾¿ä¼šæŸ¥è¯¢å½“å‰åŽŸå§‹æ•°æ®ä¸Šä¼ ä¸åŒ…å«çš„æ–°æ•°æ®ï¼ˆä¸Žä¸Šæ¬¡åŽŸå§‹æ•°æ®ä¸Šä¼ 相较而言）。系统会确定新的测试用例失败ã€æŒç»çš„测试用例失败ã€çž¬æ€æµ‹è¯•ç”¨ä¾‹å¤±è´¥ã€æµ‹è¯•ç”¨ä¾‹ä¿®å¤å’Œæ— 效的测试，然åŽå°†è¿™äº›ä¿¡æ¯ä»¥ç”µåé‚®ä»¶çš„æ ¼å¼å‘é€ç»™å„项测试的订阅者。</li> +<li><strong>网络æœåŠ¡è¿è¡ŒçŠ¶å†µ</strong>。Google Stackdriver 集æˆäº† Google App 引擎，å¯è½»æ¾ç›‘控 VTS ä¿¡æ¯ä¸å¿ƒã€‚您既å¯ä½¿ç”¨ç®€å•çš„è¿è¡Œæ—¶é—´æ£€æŸ¥æ¥éªŒè¯ç½‘页能å¦è¢«è®¿é—®ï¼Œä¹Ÿå¯åˆ›å»ºå…¶ä»–测试æ¥æ£€æŸ¥æ¯ä¸ªç½‘页ã€servlet 或数æ®åº“ä¸çš„延迟情况。这些检查å¯ç¡®ä¿ä¿¡æ¯ä¸å¿ƒå§‹ç»ˆå¤„于å¯è®¿é—®çš„状æ€ï¼ˆå¦åˆ™å°†é€šçŸ¥ç®¡ç†å‘˜ï¼‰ã€‚</li> +<li><strong>Google Cloud Analytics</strong>。通过在页é¢é…置（pom.xml 文件）ä¸æŒ‡å®šæœ‰æ•ˆçš„ Google Cloud Analytics ID，您å¯ä»¥å°† VTS ä¿¡æ¯ä¸å¿ƒé¡µé¢ä¸Ž Google Cloud Analytics 集æˆã€‚集æˆåŽï¼Œæ‚¨ä¾¿èƒ½å¤Ÿæ›´å…¨é¢åœ°åˆ†æžç½‘页用途ã€ç”¨æˆ·äº’动ã€ä½ç½®ã€ä¼šè¯ç»Ÿè®¡ä¿¡æ¯ç‰ã€‚</li> +</ul> + +</body></html>
\ No newline at end of file diff --git a/zh-cn/devices/architecture/dto/multiple.html b/zh-cn/devices/architecture/dto/multiple.html index 2f1a9a26..aea67172 100644 --- a/zh-cn/devices/architecture/dto/multiple.html +++ b/zh-cn/devices/architecture/dto/multiple.html @@ -20,7 +20,7 @@ limitations under the License. --> -<p>很多 SoC ä¾›åº”å•†å’ŒåŽŸå§‹è®¾è®¡åˆ¶é€ å•† (ODM) 都支æŒåœ¨ä¸€å°è®¾å¤‡ä¸Šä½¿ç”¨å¤šä¸ª DTï¼Œä»Žè€Œä½¿ä¸€ä¸ªæ˜ åƒèƒ½å¤Ÿä¸ºå¤šä¸ª SKU/é…ç½®æ供支æŒã€‚在这ç§æƒ…å†µä¸‹ï¼Œå¼•å¯¼åŠ è½½ç¨‹åºä¼šåœ¨è¿è¡Œæ—¶è¯†åˆ«ç¡¬ä»¶ï¼Œå¹¶åŠ 载相应的 DT：</p> +<p>很多 SoC 供应商和 ODM 都支æŒåœ¨ä¸€å°è®¾å¤‡ä¸Šä½¿ç”¨å¤šä¸ª DTï¼Œä»Žè€Œä½¿ä¸€ä¸ªæ˜ åƒèƒ½å¤Ÿä¸ºå¤šä¸ª SKU/é…ç½®æ供支æŒã€‚在这ç§æƒ…å†µä¸‹ï¼Œå¼•å¯¼åŠ è½½ç¨‹åºä¼šåœ¨è¿è¡Œæ—¶è¯†åˆ«ç¡¬ä»¶ï¼Œå¹¶åŠ 载相应的 DT：</p> <p><img src="../images/treble_dto_multiple_dt.png"/></p> <figcaption><strong>图 1</strong> å¼•å¯¼åŠ è½½ç¨‹åºä¸çš„å¤šä¸ªè®¾å¤‡æ ‘å åŠ å±‚ã€‚</figcaption> @@ -36,11 +36,12 @@ <p>å¼•å¯¼åŠ è½½ç¨‹åºåº”该能够：</p> <ul> -<li>è¯»å– SoC ID 并选择相应的主 DT，并</li> -<li>读å–æ¿ ID 并选择相应的å åŠ DT。</li> +<li>è¯»å– SoC ID å¹¶é€‰æ‹©ç›¸åº”çš„ä¸»è®¾å¤‡æ ‘ï¼Œå¹¶</li> +<li>读å–æ¿ ID 并选择相应的å åŠ è®¾å¤‡æ ‘ã€‚ +</li> </ul> -<p>仅选择一个主 DT 和一个å åŠ DT 以便在è¿è¡Œæ—¶ä½¿ç”¨ï¼Œå¹¶ä¸”所选择的对必须是兼容的。</p> +<p>åªèƒ½é€‰æ‹©ä¸€ä¸ªä¸» DT 供在è¿è¡Œæ—¶ä½¿ç”¨ã€‚å¯é€‰æ‹©å¤šä¸ªå åŠ DT，但它们必须与选定的主 DT 兼容。使用多个å åŠ å±‚æœ‰åŠ©äºŽé¿å… DTBO 分区内的æ¯å—æ¿ä¸Šéƒ½å˜å‚¨ä¸€ä¸ªå åŠ å±‚ï¼Œå¹¶èƒ½è®©å¼•å¯¼åŠ è½½ç¨‹åºæ ¹æ®æ¿ ID 或通过探测外设æ¥ç¡®å®šæ‰€éœ€å åŠ å±‚çš„åé›†ã€‚ä¾‹å¦‚ï¼Œæ¿ A å¯èƒ½éœ€è¦é€šè¿‡å åŠ å±‚ 1ã€3 å’Œ 5 æ·»åŠ çš„è®¾å¤‡ï¼Œè€Œæ¿ B å¯èƒ½éœ€è¦é€šè¿‡å åŠ å±‚ 1ã€4 å’Œ 5 æ·»åŠ çš„è®¾å¤‡ã€‚</p> <h2 id="partition">分区</h2> <p>è¦è¿›è¡Œåˆ†åŒºï¼Œè¯·åœ¨é—ªå˜ä¸ç¡®å®šå¼•å¯¼åŠ 载程åºåœ¨è¿è¡Œæ—¶å¯è®¿é—®å’Œå¯ä¿¡çš„ä½ç½®ï¼Œä»¥å˜å‚¨ DTB å’Œ DTBOï¼ˆå¼•å¯¼åŠ è½½ç¨‹åºå¿…须能够在匹é…的进程ä¸æ‰¾åˆ°è¿™äº›æ–‡ä»¶ï¼‰ã€‚请记ä½ï¼ŒDTB å’Œ DTBO ä¸èƒ½å˜åœ¨äºŽåŒä¸€ä¸ªåˆ†åŒºä¸ã€‚如果您的 DTB/DTBO ä½äºŽ <code>dtb</code>/<code>dtbo</code> 分区ä¸ï¼Œè¯·ä½¿ç”¨ <a href="/devices/architecture/dto/partitions.html">DTB/DTBO åˆ†åŒºæ ¼å¼</a>ä¸è¯¦ç»†åˆ—å‡ºçš„è¡¨ç»“æž„å’Œå¤´æ–‡ä»¶æ ¼å¼ã€‚</p> diff --git a/zh-cn/devices/architecture/hidl-cpp/functions.html b/zh-cn/devices/architecture/hidl-cpp/functions.html index 841fcabe..af7e3aba 100644 --- a/zh-cn/devices/architecture/hidl-cpp/functions.html +++ b/zh-cn/devices/architecture/hidl-cpp/functions.html @@ -55,7 +55,7 @@ Return<uint32_t> someMethod() { }; </pre> -<p>å¦å¤–，您还å¯ä»¥ä½¿ç”¨ <code>Return<*>::withDefault</code> 方法。æ¤æ–¹æ³•ä¼šåœ¨è¿”回值为 <code>! isOk()</code> 的情况下æ供一个值。æ¤æ–¹æ³•è¿˜ä¼šè‡ªåŠ¨å°†è¿”å›žå¯¹è±¡æ ‡è®°ä¸ºæ£å¸¸ï¼Œä»¥å…客户端进程é到终æ¢ã€‚</p> +<p>å¦å¤–，您还å¯ä»¥ä½¿ç”¨ <code>Return<*>::withDefault</code> 方法。æ¤æ–¹æ³•ä¼šåœ¨è¿”回值为 <code>!isOk()</code> 的情况下æ供一个值。æ¤æ–¹æ³•è¿˜ä¼šè‡ªåŠ¨å°†è¿”å›žå¯¹è±¡æ ‡è®°ä¸ºæ£å¸¸ï¼Œä»¥å…客户端进程é到终æ¢ã€‚</p> <h3 id="return-callback">使用回调å‚数返回</h3> <p>回调å¯ä»¥å°† HIDL å‡½æ•°çš„è¿”å›žå€¼å›žä¼ ç»™è°ƒç”¨æ–¹ã€‚å›žè°ƒçš„åŽŸåž‹æ˜¯ <code>std::function</code> 对象，其å‚数（从 <code>generates</code> è¯å¥ä¸èŽ·å–ï¼‰ä¼šæ˜ å°„åˆ° C++ 类型。它的返回值为 void（回调本身并ä¸ä¼šè¿”回任何值）。</p> diff --git a/zh-cn/devices/architecture/hidl-java/index.html b/zh-cn/devices/architecture/hidl-java/index.html index c1905a05..2d8820d5 100644 --- a/zh-cn/devices/architecture/hidl-java/index.html +++ b/zh-cn/devices/architecture/hidl-java/index.html @@ -20,7 +20,7 @@ limitations under the License. --> -<p>Android O 对 Android æ“作系统进行了é‡æ–°æž¶æž„，在独立于设备的 Android å¹³å°ä¸Žç‰¹å®šäºŽè®¾å¤‡å’Œä¾›åº”商的代ç 之间定义了清晰的接å£ã€‚ +<p>Android O 对 Android æ“作系统的架构é‡æ–°è¿›è¡Œäº†è®¾è®¡ï¼Œä»¥åœ¨ç‹¬ç«‹äºŽè®¾å¤‡çš„ Android å¹³å°ä¸Žç‰¹å®šäºŽè®¾å¤‡å’Œä¾›åº”商的代ç 之间定义清晰的接å£ã€‚ Android å·²ç»ä»¥ HAL 接å£çš„å½¢å¼ï¼ˆåœ¨ <code>hardware/libhardware</code> ä¸å®šä¹‰ä¸º C æ ‡å¤´ï¼‰å®šä¹‰äº†è®¸å¤šæ¤ç±»æŽ¥å£ã€‚HIDL 将这些 HAL 接å£æ›¿æ¢ä¸ºç¨³å®šçš„带版本接å£ï¼Œå¯ä»¥é‡‡ç”¨ Java（如下所述），也å¯ä»¥æ˜¯é‡‡ç”¨ <a href="/devices/architecture/hidl-cpp/index.html">C++</a> 的客户端和æœåŠ¡å™¨ç«¯ HIDL 接å£ã€‚</p> <p>HIDL 接å£ä¸»è¦é€šè¿‡æœ¬æœºä»£ç ä½¿ç”¨ï¼Œå› æ¤ HIDL 专注于自动生æˆé«˜æ•ˆçš„ C++ 代ç 。ä¸è¿‡ï¼ŒHIDL 接å£ä¹Ÿå¿…须能够直接通过 Java ä½¿ç”¨ï¼Œå› ä¸ºæœ‰äº› Android å系统（如 Telephony）很å¯èƒ½å…·æœ‰ Java HIDL 接å£ã€‚</p> @@ -97,7 +97,7 @@ hidl-gen -o /tmp -Ljava \ import android.hardware.foo.V1_0.IFoo; import android.hardware.foo.V1_0.IFooCallback.Stub; .... -class FooCallback extends IFoo.Stub { +class FooCallback extends IFooCallback.Stub { // implement methods } .... diff --git a/zh-cn/devices/architecture/hidl/hashing.html b/zh-cn/devices/architecture/hidl/hashing.html index f9565eb4..e5f475f4 100644 --- a/zh-cn/devices/architecture/hidl/hashing.html +++ b/zh-cn/devices/architecture/hidl/hashing.html @@ -45,7 +45,7 @@ c84da9f5...f8ea2648 vendor.awesome.foo@1.0::types 822998d7...74d63b8c vendor.awesome.foo@1.0::IFoo </pre> -<p class="note"><strong>注æ„</strong>：为了便于跟踪å„个哈希的æ¥æºï¼ŒGoogle å°† HIDL <code>current.txt</code> 文件分为ä¸åŒçš„部分：第一部分列出在 Android O ä¸å‘布的接å£æ–‡ä»¶ï¼›ç¬¬äºŒéƒ¨åˆ†åˆ—出在 Android O MR1 ä¸å‘布的接å£æ–‡ä»¶ã€‚<em></em><em></em>我们强烈建议在您的 <code>current.txt</code> 文件ä¸ä½¿ç”¨ç±»ä¼¼å¸ƒå±€ã€‚</p> +<p class="note"><strong>注æ„</strong>：为了便于跟踪å„个哈希的æ¥æºï¼ŒGoogle å°† HIDL <code>current.txt</code> 文件分为ä¸åŒçš„部分：第一部分列出在 Android O ä¸å‘布的接å£æ–‡ä»¶ï¼Œç¬¬äºŒéƒ¨åˆ†åˆ—出在 Android O MR1 ä¸å‘布的接å£æ–‡ä»¶ã€‚<em></em><em></em>我们强烈建议在您的 <code>current.txt</code> 文件ä¸ä½¿ç”¨ç±»ä¼¼å¸ƒå±€ã€‚</p> <h2 id="hidl-gen">使用 hidl-gen æ·»åŠ å“ˆå¸Œ</h2> <p>您å¯ä»¥æ‰‹åŠ¨å°†å“ˆå¸Œæ·»åŠ 到 <code>current.txt</code> 文件ä¸ï¼Œä¹Ÿå¯ä»¥ä½¿ç”¨ <code>hidl-gen</code> æ·»åŠ ã€‚ä»¥ä¸‹ä»£ç 段æ供了å¯ä¸Ž <code>hidl-gen</code> æé…使用æ¥ç®¡ç† <code>current.txt</code> 文件的命令示例（哈希已缩çŸï¼‰ï¼š</p> diff --git a/zh-cn/devices/architecture/hidl/services.html b/zh-cn/devices/architecture/hidl/services.html index 8e4d0f1f..b12d24ab 100644 --- a/zh-cn/devices/architecture/hidl/services.html +++ b/zh-cn/devices/architecture/hidl/services.html @@ -57,7 +57,7 @@ V1_1.IFooService; alternateService = 1_1.IFooService.getService("another", true <li>替æ¢å…¶ <code>serviceDied()</code> 方法。</li> <li>实例化 <code>hidl_death_recipient</code> å类的对象。 </li> -<li>在è¦ç›‘控的æœåŠ¡ä¸Šè°ƒç”¨ <code>linkToDeath()</code> æ–¹æ³•ï¼Œå¹¶ä¼ å…¥ <code>IDeathRecipient</code> 的接å£å¯¹è±¡ã€‚</li> +<li>在è¦ç›‘控的æœåŠ¡ä¸Šè°ƒç”¨ <code>linkToDeath()</code> æ–¹æ³•ï¼Œå¹¶ä¼ å…¥ <code>IDeathRecipient</code> 的接å£å¯¹è±¡ã€‚请注æ„，æ¤æ–¹æ³•å¹¶ä¸å…·å¤‡åœ¨å…¶ä¸Šè°ƒç”¨å®ƒçš„终æ¢æŽ¥æ”¶æ–¹æˆ–代ç†çš„所有æƒã€‚</li> </ol> <p>伪代ç 示例（C++ å’Œ Java 类似）：</p> diff --git a/zh-cn/devices/architecture/hidl/versioning.html b/zh-cn/devices/architecture/hidl/versioning.html index f43c2f0a..78b7c5c2 100644 --- a/zh-cn/devices/architecture/hidl/versioning.html +++ b/zh-cn/devices/architecture/hidl/versioning.html @@ -130,7 +130,7 @@ interface IQuux { <p><code>Bar</code> 的完全é™å®šå称为 <code>android.hardware.example@1.0::IQuux.Foo.Bar</code>。</p> -<p>在上述两ç§æƒ…况下，åªæœ‰åœ¨ <code>Foo</code> 的声明范围内æ‰èƒ½ä½¿ç”¨ <code>Bar</code> æ¥å¼•ç”¨ <code>Bar</code>。在软件包级或接å£çº§ï¼Œå¿…须通过 <code>Bar</code>:<code>Foo</code><code>Foo. æ¥å¼•ç”¨ Bar</code>，如上述方法 <code>doSomething</code> 的声明ä¸æ‰€ç¤ºã€‚或者，您å¯ä»¥æ›´è¯¦ç»†åœ°å°†è¯¥æ–¹æ³•å£°æ˜Žä¸ºï¼š</p> +<p>在上述两ç§æƒ…况下，åªæœ‰åœ¨ <code>Foo</code> 的声明范围内æ‰èƒ½ä½¿ç”¨ <code>Bar</code> æ¥å¼•ç”¨ <code>Bar</code>。在软件包级或接å£çº§ï¼Œå¿…须通过 <code>Foo</code>:<code>Foo.<code>Bar</code> æ¥å¼•ç”¨ Bar</code>，如上述方法 <code>doSomething</code> 的声明ä¸æ‰€ç¤ºã€‚或者，您å¯ä»¥æ›´è¯¦ç»†åœ°å°†è¯¥æ–¹æ³•å£°æ˜Žä¸ºï¼š</p> <pre class="prettyprint"> // IQuux.hal @@ -210,8 +210,7 @@ struct ExtendedNfcData { </pre> <h3 id="rule3">规则 3</h3> -<p>如果规则 2 未能生æˆåŒ¹é…项（UDT 未在当å‰è½¯ä»¶åŒ…ä¸å®šä¹‰ï¼‰ï¼ŒHIDL 编译器会扫æ所有导入的软件包，查找是å¦æœ‰åŒ¹é…项。 -以上é¢çš„示例æ¥è¯´ï¼Œå‡è®¾ <code>ExtendedNfcData</code> 是在 <code>1.1</code> 版本的软件包 <code>android.hardware.nfc</code> ä¸å£°æ˜Žçš„，<code>1.1</code> 按预期导入 <code>1.0</code>（请å‚阅<a href="#package-ext">软件包级扩展</a>），且定义仅指定 UDT å称：</p> +<p>如果规则 2 未能生æˆåŒ¹é…项（UDT 未在当å‰è½¯ä»¶åŒ…ä¸å®šä¹‰ï¼‰ï¼ŒHIDL 编译器会扫æ所有导入的软件包，查找是å¦æœ‰åŒ¹é…项。以上é¢çš„示例æ¥è¯´ï¼Œå‡è®¾ <code>ExtendedNfcData</code> 是在 <code>1.1</code> 版本的软件包 <code>android.hardware.nfc</code> ä¸å£°æ˜Žçš„，<code>1.1</code> 按预期导入 <code>1.0</code>（请å‚阅<a href="#package-ext">软件包级扩展</a>），且定义仅指定 UDT å称：</p> <pre class="prettyprint"> struct ExtendedNfcData { @@ -329,7 +328,7 @@ interface IQuux { <td><p>以下å„项å‡ä¸º true：</p> <ol> -<li>“以å‰çš„ minor 版本有效â€ï¼š<code>package@major.(minor-1)</code> 必须已定义，并且éµå¾ªç›¸åŒçš„规则 A（从 <code>package@major.0</code> 到 <code>package@major.(major-2)</code> å‡æœªå®šä¹‰ï¼‰æˆ–规则 B（如果它是从 <code>@major.(major-2)</code> å‡çº§è€Œæ¥ï¼‰ï¼› +<li>“以å‰çš„ minor 版本有效â€ï¼š<code>package@major.(minor-1)</code> 必须已定义，并且éµå¾ªç›¸åŒçš„规则 A（从 <code>package@major.0</code> 到 <code>package@major.(minor-2)</code> å‡æœªå®šä¹‰ï¼‰æˆ–规则 B（如果它是从 <code>@major.(minor-2)</code> å‡çº§è€Œæ¥ï¼‰ï¼› <br /><br /> å’Œ <br /><br /> @@ -405,8 +404,7 @@ enum Color : @1.0::Brightness { HW_GREEN, RAINBOW }; <p>ä¸è¿‡ï¼Œæœ‰ä¸€ç§ç±»åž‹çš„关系ç»è¿‡ä¸¥æ ¼å®šä¹‰ï¼Œä¸”必须强制执行，å³è½¯ä»¶åŒ…级å‘åŽå…¼å®¹çš„继承。<em></em>在这ç§æƒ…况下，父级软件包是被继承的软件包，而å软件包是扩展父级的软件包。<em></em><em></em>软件包级å‘åŽå…¼å®¹çš„继承规则如下：</p> <ol> -<li>父级软件包的所有接å£éƒ½ä¼šè¢«å软件包ä¸çš„接å£ç»§æ‰¿ã€‚</li> -<li>父级软件包ä¸çš„所有数æ®ç±»åž‹å‡ä¼šåŒ…å«åœ¨æ–°è½¯ä»¶åŒ…ä¸ï¼Œå¹¶ä¸”å¯ç”±æ¥è‡ªæ—§è½¯ä»¶åŒ…ä¸çš„方法（å¯èƒ½ç»è¿‡äº†é‡æ–°å®žçŽ°ï¼‰æ¥å¤„ç†ã€‚</li> +<li>父级软件包的所有顶级接å£éƒ½ä¼šè¢«å级软件包ä¸çš„接å£ç»§æ‰¿ã€‚</li> <li>新接å£ä¹Ÿå¯ä»¥æ·»åŠ 到新软件包ä¸ï¼ˆä¸Žå…¶ä»–软件包ä¸å…¶ä»–接å£çš„关系ä¸å—é™åˆ¶ï¼‰ã€‚</li> <li>æ–°æ•°æ®ç±»åž‹ä¹Ÿå¯ä»¥æ·»åŠ 到新软件包ä¸ï¼Œä»¥ä¾›å‡çº§çš„现有接å£çš„新方法使用，或供新接å£ä½¿ç”¨ã€‚</li> </ol> diff --git a/zh-cn/devices/architecture/kernel/modular-kernels.html b/zh-cn/devices/architecture/kernel/modular-kernels.html index d473c9a0..7145d2a4 100644 --- a/zh-cn/devices/architecture/kernel/modular-kernels.html +++ b/zh-cn/devices/architecture/kernel/modular-kernels.html @@ -56,7 +56,7 @@ CONFIG_MODULE_SIG=y CONFIG_MODULE_SIG_FORCE=y </pre> -<p>在需è¦æ”¯æŒéªŒè¯å¯åŠ¨çš„设备上，Android è¦æ±‚å†…æ ¸æ¨¡å—ä½äºŽå¯ç”¨ dm-verity 的分区ä¸ã€‚模å—ç¾å并éžå¼ºåˆ¶æ€§è¦æ±‚，也ä¸ä¼šè¿›è¡Œæµ‹è¯•ï¼›ä¸è¿‡ï¼Œå¦‚有需è¦ï¼ŒODM 也å¯ä»¥å¯ç”¨æ¨¡å—ç¾å，但å‰æ是 ODM 拥有å¯ç¡®ä¿æœªæ¥ç‹¬ç«‹å†…æ ¸å’Œæ–‡ä»¶ç³»ç»Ÿ OTA 更新的密钥ç¾å以åŠæ‰€éœ€çš„其他基础架构。</p> +<p>在需è¦æ”¯æŒéªŒè¯å¯åŠ¨çš„设备上，Android è¦æ±‚å†…æ ¸æ¨¡å—ä½äºŽå¯ç”¨ dm-verity 的分区ä¸ã€‚模å—ç¾å并éžå¼ºåˆ¶æ€§è¦æ±‚，也ä¸ä¼šè¿›è¡Œæµ‹è¯•ï¼›ä¸è¿‡ï¼Œå¦‚有需è¦ï¼ŒODM 也å¯ä»¥å¯ç”¨æ¨¡å—ç¾å，但å‰æ是 ODM 拥有所需的密钥ç¾ååŠå…¶ä»–基础架构，以确ä¿æœªæ¥å¯è¿›è¡Œç‹¬ç«‹çš„å†…æ ¸å’Œæ–‡ä»¶ç³»ç»Ÿ OTA 更新。</p> <h3 id="file-locations">文件ä½ç½®</h3> <p>Android 7.x åŠæ›´æ—©ç‰ˆæœ¬å¯¹å†…æ ¸æ¨¡å—（包括对 <code>insmod</code> å’Œ <code>rmmod</code> 的支æŒï¼‰æ²¡æœ‰å¼ºåˆ¶è¦æ±‚，而 Android 8.0 建议在生æ€ç³»ç»Ÿä¸ä½¿ç”¨å†…æ ¸æ¨¡å—。下表显示了 Android çš„ 3 ç§å¯åŠ¨æ¨¡å¼æ‰€éœ€çš„æ¿ä¸“用外设设备支æŒï¼š</p> @@ -194,7 +194,7 @@ on early-init <h3 id="early-mounting-partitions-vboot-1-0">æå‰è£…载分区 (VBoot 1.0)</h3> <p>使用 VBoot 1.0 æå‰è£…载分区的è¦æ±‚包括：</p> <ol> -<li>设备节点路径必须在 <em>fstab</em> å’Œè®¾å¤‡æ ‘æ¡ç›®ä¸ä½¿ç”¨å…¶ by-name 符å·é“¾æŽ¥ã€‚<code>fstab</code>例如，确ä¿å¯¹åˆ†åŒºè¿›è¡Œå‘½å且设备节点为 <code>/dev/block/…./by-name/{system,vendor,odm}</code>，而ä¸æ˜¯ä½¿ç”¨ <code>/dev/block/mmcblk0pX</code> 指定分区。 +<li>设备节点路径必须在 <code>fstab</code> å’Œè®¾å¤‡æ ‘æ¡ç›®ä¸ä½¿ç”¨å…¶ by-name 符å·é“¾æŽ¥ã€‚<em></em>例如，确ä¿å¯¹åˆ†åŒºè¿›è¡Œå‘½å且设备节点为 <code>/dev/block/…./by-name/{system,vendor,odm}</code>，而ä¸æ˜¯ä½¿ç”¨ <code>/dev/block/mmcblk0pX</code> 指定分区。 </li> <li>在产å“的设备é…ç½®ä¸ï¼ˆå³ <code>device/<em>oem</em>/<em>project</em>/device.mk</code> ä¸ï¼‰ä¸ºäº§å“ <code>PRODUCT_{SYSTEM,VENDOR}_VERITY_PARTITION</code> å’Œ <code>CUSTOM_IMAGE_VERITY_BLOCK_DEVICE</code> 指定的路径必须与 <code>fstab</code>/è®¾å¤‡æ ‘æ¡ç›®ä¸æŒ‡å®š by-name 的相应å—设备节点相匹é…。<em></em>例如：<pre class="prettyprint"> PRODUCT_SYSTEM_VERITY_PARTITION := /dev/block/…./by-name/system @@ -389,7 +389,7 @@ fstab æ¡ç›®é‡‡å–以下形å¼ï¼š</p> <h2 id="device-tree-overlay-support-bootloader">è®¾å¤‡æ ‘å åŠ å±‚æ”¯æŒï¼ˆå¼•å¯¼åŠ 载程åºï¼‰</h2> <p> -<a href="/devices/architecture/dto/">è®¾å¤‡æ ‘å åŠ å±‚</a> (DTO) 旨在扩展现有<a href="https://events.linuxfoundation.org/sites/events/files/slides/petazzoni-device-tree-dummies.pdf" class="external">æ‰å¹³åŒ–è®¾å¤‡æ ‘ (FDT)</a> 的实现，以便在è¿è¡Œæ—¶ç”¨æˆ·ç©ºé—´å¯é€šè¿‡åŠ 载修改了原始数æ®çš„é¢å¤–å åŠ å±‚ FDT æ¥ä¿®æ”¹å†…æ ¸ä¸çš„åˆå§‹è®¾å¤‡æ ‘æ•°æ®ã€‚Android ä¸éœ€è¦æ¥è‡ªç”¨æˆ·ç©ºé—´çš„ DT Blob è¿è¡Œæ—¶æ›´æ–°ï¼Œè€Œæ˜¯å»ºè®®ä¾›åº”商借助 <code>libfdt</code>/<code>libufdt</code> åœ¨å¼•å¯¼åŠ è½½ç¨‹åºä¸æ·»åŠ è®¾å¤‡æ ‘è¡¥ä¸ç¨‹åºã€‚</p> +<a href="/devices/architecture/dto/">è®¾å¤‡æ ‘å åŠ å±‚</a> (DTO) 旨在扩展现有<a href="https://events.linuxfoundation.org/sites/events/files/slides/petazzoni-device-tree-dummies.pdf" class="external">æ‰å¹³åŒ–è®¾å¤‡æ ‘ (FDT)</a> 的实现，以便用户空间（在è¿è¡Œæ—¶ï¼‰å¯é€šè¿‡åŠ 载修改了原始数æ®çš„é¢å¤–å åŠ å±‚ FDT æ¥ä¿®æ”¹å†…æ ¸ä¸çš„åˆå§‹è®¾å¤‡æ ‘æ•°æ®ã€‚Android ä¸éœ€è¦æ¥è‡ªç”¨æˆ·ç©ºé—´çš„ DT Blob è¿è¡Œæ—¶æ›´æ–°ï¼Œè€Œæ˜¯å»ºè®®ä¾›åº”商借助 <code>libfdt</code>/<code>libufdt</code> åœ¨å¼•å¯¼åŠ è½½ç¨‹åºä¸æ·»åŠ è®¾å¤‡æ ‘è¡¥ä¸ç¨‹åºã€‚</p> <p>在 Android 7.x åŠæ›´æ—©ç‰ˆæœ¬ä¸ï¼ŒAndroid ä¸è¦æ±‚æä¾›è®¾å¤‡æ ‘æ”¯æŒï¼ŒåŒæ—¶ï¼Œæ²¡æœ‰é’ˆå¯¹ä¾›åº”商如何将 DT Blob ä¼ é€’ç»™å†…æ ¸æˆ–åœ¨ä½•å¤„å˜å‚¨è¿™äº› Blob æ供相关建议。ä¸è¿‡ï¼ŒAndroid 8.0 建议æä¾›æ¤ç±»æ”¯æŒï¼Œä»¥å°†å†…æ ¸çš„æ¿ä¸“å±žéƒ¨åˆ†å’Œä»…é™ SoC 访问的部分区分开æ¥ã€‚</p> diff --git a/zh-cn/devices/audio/latency_measurements.html b/zh-cn/devices/audio/latency_measurements.html index 8edee0ad..28d6f195 100644 --- a/zh-cn/devices/audio/latency_measurements.html +++ b/zh-cn/devices/audio/latency_measurements.html @@ -1,5 +1,5 @@ <html devsite><head> - <title>音频延迟时间测é‡</title> + <title>音频延迟衡é‡</title> <meta name="project_path" value="/_project.yaml"/> <meta name="book_path" value="/_book.yaml"/> </head> @@ -20,7 +20,7 @@ limitations under the License. --> -<p><a href="http://en.wikipedia.org/wiki/Latency_%28engineering%29">延迟时间</a>是一项é‡è¦çš„ç³»ç»Ÿæ€§èƒ½æŒ‡æ ‡ã€‚<a href="latency.html">音频延迟时间</a>æŒ‡æ ‡æœ‰å¤šç§ç±»åž‹ï¼Œå…¶ä¸ä¸€ä¸ªå¾ˆå®žç”¨ä¸”易于ç†è§£çš„æŒ‡æ ‡æ˜¯<a href="latency_measure.html#measuringRoundTrip">往返延迟时间</a>ã€‚æ ¹æ®è¯¥æŒ‡æ ‡çš„定义，音频延迟时间是指音频信å·è¿›å…¥ç§»åŠ¨è®¾å¤‡çš„输入设备，由应用处ç†å™¨ä¸Šè¿è¡Œçš„应用进行处ç†ï¼Œç„¶åŽé€€å‡ºè¾“出设备，这整个过程所花费的时间。</p> +<p><a href="http://en.wikipedia.org/wiki/Latency_%28engineering%29">延迟时间</a>是一项é‡è¦çš„ç³»ç»Ÿæ€§èƒ½æŒ‡æ ‡ã€‚<a href="latency.html">音频延迟时间</a>æŒ‡æ ‡æœ‰å¤šç§ç±»åž‹ï¼Œå…¶ä¸ä¸€ä¸ªå¾ˆå®žç”¨ä¸”易于ç†è§£çš„æŒ‡æ ‡æ˜¯<a href="latency_measure.html#measuringRoundTrip">往返延迟时间</a>ã€‚æ ¹æ®è¯¥æŒ‡æ ‡çš„定义，往返延迟时间是指音频信å·è¿›å…¥ç§»åŠ¨è®¾å¤‡çš„输入组件，由应用处ç†å™¨ä¸Šè¿è¡Œçš„应用进行处ç†ï¼Œç„¶åŽä»Žè¾“å‡ºç»„ä»¶ä¼ å‡ºï¼Œè¿™æ•´ä¸ªè¿‡ç¨‹æ‰€èŠ±è´¹çš„æ—¶é—´ã€‚</p> <img src="images/round_trip_on_device.png" alt="设备上的往返音频延迟时间" id="figure1"/> <p class="img-caption"><strong>图 1. </strong> 设备上的往返音频延迟时间：T<sub>output</sub> - T<sub>input</sub></p> @@ -41,7 +41,7 @@ <h2 id="how">如何测é‡</h2> -<p>我们使用 <a href="loopback.html">Dr. Rick O'Rang 音频环回软件狗</a>å’Œ<a href="latency_measure.html#larsenTest">音频å馈（拉尔森效应）测试</a>得出了本页列出的测é‡ç»“果。测é‡å‡è®¾åº”用信å·å¤„ç†æŠ€æœ¯å¢žåŠ 了零算法延迟时间和近零计算延迟时间。</p> +<p>我们使用 <a href="loopback.html">Dr. Rick O'Rang 音频环回软件狗</a>å’Œ<a href="latency_measure.html#larsenTest">音频å馈（拉尔森效应）测试</a>得出了本页列出的测é‡ç»“果。测é‡å‡è®¾åº”用信å·å¤„ç†æŠ€æœ¯çš„算法延迟时间为零，并且计算延迟时间接近零。</p> <p>我们通过耳机连接器æ¥æµ‹é‡å¾€è¿”å»¶è¿Ÿæ—¶é—´æœ‰ä»¥ä¸‹å‡ ä¸ªåŽŸå› ï¼š</p> <img src="images/round_trip_via_headset_connector.png" alt="通过耳机连接器测é‡çš„往返延迟时间" id="figure2"/> @@ -54,7 +54,7 @@ <p>在有些情况下，设备上的麦克风和扬声器延迟时间确实会带æ¥å½±å“，但这通常是针对å•å‘延迟而ä¸æ˜¯å¾€è¿”延迟。<em></em><a href="latency_measure.html#measuringOutput">测é‡è¾“出设备延迟时间</a>å’Œ<a href="latency_measure.html#measuringInput">测é‡è¾“入设备延迟时间</a>ä¸ä»‹ç»äº†æµ‹é‡å•å‘延迟时间的相关技巧。</p> -<h2 id="measurements">测é‡ç»“果示例</h2> +<h2 id="examples">测é‡ç»“果示例</h2> <p>下é¢åˆ—出的是特定于æŸä¸ª<a href="/setup/build-numbers.html">版本å·</a>的测é‡ç»“果。设备按åˆå§‹ç‰ˆæœ¬å’Œå¹³å°ç‰ˆæœ¬çš„大致顺åºåˆ—出；您也å¯ä»¥<a href="#chart">查看图表ä¸çš„延迟时间</a>。测试应用会使用 Android 原生音频 API（基于 OpenSL ES）。</p> diff --git a/zh-cn/devices/audio/terminology.html b/zh-cn/devices/audio/terminology.html index 910c1415..e0e3f4ac 100644 --- a/zh-cn/devices/audio/terminology.html +++ b/zh-cn/devices/audio/terminology.html @@ -447,7 +447,7 @@ Android 声音æœåŠ¡å™¨å®žçŽ°ç”¨ä¾‹ã€‚AudioFlinger 在 mediaserver 进程ä¸è¿è <dt>音频焦点</dt> <dd> -跨多个独立应用管ç†éŸ³é¢‘互动的 API 集。如需了解详情，请å‚阅<a href="http://developer.android.com/training/managing-audio/audio-focus.html">管ç†éŸ³é¢‘焦点</a>以åŠä¸Žç„¦ç‚¹ç›¸å…³çš„方法和 <a href="http://developer.android.com/reference/android/media/AudioManager.html">android.media.AudioManager</a> 的常é‡ã€‚ +跨多个独立应用管ç†éŸ³é¢‘互动的 API 集。如需了解详情，请å‚阅<a href="http://developer.android.com/training/managing-audio/audio-focus.html">管ç†éŸ³é¢‘焦点</a>ä»¥åŠ <a href="http://developer.android.com/reference/android/media/AudioManager.html">android.media.AudioManager</a> 的与焦点相关的方法和常é‡ã€‚ </dd> <dt>AudioMixer</dt> diff --git a/zh-cn/devices/camera/index.html b/zh-cn/devices/camera/index.html index f2855c55..6bb05251 100644 --- a/zh-cn/devices/camera/index.html +++ b/zh-cn/devices/camera/index.html @@ -100,7 +100,8 @@ PRODUCT_COPY_FILES += \ <device>/<company>/<device>/media_codecs.xml:system/etc/media_codecs.xml </pre></li> -<li>è¦å°†ç›¸æœºåº”用包å«åœ¨æ‚¨è®¾å¤‡çš„ç³»ç»Ÿæ˜ åƒä¸ï¼Œè¯·åœ¨è®¾å¤‡çš„ <code>device/<company>/<device>/device.mk</code> Makefile ä¸çš„ <code>PRODUCT_PACKAGES</code> å˜é‡ä¸æŒ‡å®šè¯¥åº”用：<pre class="devsite-click-to-copy"> +<li>è¦å°†ç›¸æœºåº”用包å«åœ¨æ‚¨è®¾å¤‡çš„ç³»ç»Ÿæ˜ åƒä¸ï¼Œè¯·åœ¨è®¾å¤‡çš„ <code>device/<company>/<device>/device.mk</code> Makefile ä¸çš„ <code>PRODUCT_PACKAGES</code> å˜é‡ä¸æŒ‡å®šè¯¥åº”用： +<pre class="devsite-click-to-copy"> PRODUCT_PACKAGES := \ Gallery2 \ ... diff --git a/zh-cn/devices/camera/versioning.html b/zh-cn/devices/camera/versioning.html index 7e2a92c9..600606b2 100644 --- a/zh-cn/devices/camera/versioning.html +++ b/zh-cn/devices/camera/versioning.html @@ -119,7 +119,7 @@ <ul> <li>若在 HAL1 上，则ä¸å— cameraservice 移动的影å“，并且<strong>ä¸éœ€è¦ä¾›åº”商更新</strong>。</li> -<li>若在 HAL3 上，则å—到 cameraservice 移动的影å“，但<strong>ä¸éœ€è¦ä¾›åº”商更新</strong>：<em></em> +<li>若在 HAL3 上，则会å—到 cameraservice 移动的影å“，但<strong>ä¸éœ€è¦ä¾›åº”商更新</strong>：<em></em> <p><img src="images/ape_camera_n_api2_hal3.png" alt="HAL2 上 API2 ä¸çš„ Android 7.0 ç›¸æœºå’Œåª’ä½“å †æ ˆ" id="figure1"/></p> <p class="img-caption"><strong>图 3. </strong>HAL3 上 API2 ä¸çš„ Android 7.0 ç›¸æœºå’Œåª’ä½“å †æ ˆã€‚</p> </li> @@ -131,7 +131,7 @@ <ul> <li><strong>常规</strong>。由于 IPC，设备需è¦é¢å¤–带宽，这å¯èƒ½ä¼šå½±å“对时间æ•æ„Ÿçš„相机使用情况，例如高速视频录制。供应商å¯ä»¥é€šè¿‡è¿è¡Œ <code>android.hardware.camera2.cts.PerformanceTest</code> å’Œ Google 相机应用进行 120/240 FPS 高速视频录制，以衡é‡å®žé™…å½±å“。设备还需è¦å°‘é‡é¢å¤–çš„ RAM æ¥åˆ›å»ºæ–°è¿›ç¨‹ã€‚</li> <li><strong>在视频缓冲区ä¸ä¼ 递元数æ®</strong>ï¼ˆä»…é™ HAL1）。<em></em>如果 HAL1 在视频缓冲区ä¸å˜å‚¨å…ƒæ•°æ®è€Œéžå®žé™…çš„ YUV 帧数æ®ï¼Œåˆ™ HAL 必须使用 <code>kMetadataBufferTypeNativeHandleSource</code> 作为元数æ®ç¼“冲区类型，并在视频缓冲区ä¸ä¼ 递 <code>VideoNativeHandleMetadata</code>（<code>kMetadataBufferTypeCameraSource</code> 在 Android 7.0 ä¸ä¸å†å—支æŒï¼‰ã€‚通过 <code>VideoNativeHandleMetadata</code>，相机和媒体框架能够æ£ç¡®åœ°å¯¹åŽŸç”Ÿå¥æŸ„进行åºåˆ—化和ååºåˆ—åŒ–ï¼Œä»Žè€Œåœ¨è¿›ç¨‹ä¹‹é—´ä¼ é€’è§†é¢‘ç¼“å†²åŒºã€‚</li> -<li><strong>缓冲区å¥æŸ„地å€ä¸ä¸€å®šå§‹ç»ˆå˜å‚¨ç›¸åŒçš„缓冲区</strong>ï¼ˆä»…é™ HAL3）。<em></em>对于æ¯ä¸ªæ•èŽ·è¯·æ±‚，HAL3 会获å–缓冲区å¥æŸ„的地å€ã€‚HAL ä¸èƒ½ä½¿ç”¨åœ°å€æ¥è¯†åˆ«ç¼“å†²åŒºï¼Œå› ä¸ºåœ°å€å¯èƒ½ä¼šåœ¨ HAL 返回缓冲区之åŽå˜å‚¨å¦ä¸€ä¸ªç¼“冲区å¥æŸ„。您必须更新 HAL，以便使用缓冲区å¥æŸ„æ¥æ ‡è¯†ç¼“冲区。例如：HAL 接收缓冲区å¥æŸ„åœ°å€ A，该地å€å˜å‚¨ç¼“冲区å¥æŸ„ A。在 HAL 返回缓冲区å¥æŸ„ A 之åŽï¼Œç¼“冲区å¥æŸ„åœ°å€ A å¯èƒ½åœ¨ HAL 下次接收到它时å˜å‚¨ç¼“冲区å¥æŸ„ B。</li> +<li><strong>缓冲区å¥æŸ„地å€å¹¶ä¸æ€»æ˜¯å˜å‚¨ç›¸åŒçš„缓冲区</strong>ï¼ˆä»…é™ HAL3）。<em></em>对于æ¯ä¸ªæ•èŽ·è¯·æ±‚，HAL3 会获å–缓冲区å¥æŸ„的地å€ã€‚HAL ä¸èƒ½ä½¿ç”¨åœ°å€æ¥è¯†åˆ«ç¼“å†²åŒºï¼Œå› ä¸ºåœ°å€å¯èƒ½ä¼šåœ¨ HAL 返回缓冲区之åŽå˜å‚¨å¦ä¸€ä¸ªç¼“冲区å¥æŸ„。您必须更新 HAL，以便使用缓冲区å¥æŸ„æ¥æ ‡è¯†ç¼“冲区。例如：HAL 接收缓冲区å¥æŸ„åœ°å€ A，该地å€å˜å‚¨ç¼“冲区å¥æŸ„ A。在 HAL 返回缓冲区å¥æŸ„ A 之åŽï¼Œç¼“冲区å¥æŸ„åœ°å€ A å¯èƒ½åœ¨ HAL 下次接收到它时å˜å‚¨ç¼“冲区å¥æŸ„ B。</li> <li><strong>更新用于 cameraserver çš„ SELinux ç–ç•¥</strong>。如果设备特定的 SELinux ç–ç•¥å‘ mediaserver 授予è¿è¡Œç›¸æœºçš„æƒé™ï¼Œåˆ™æ‚¨å¿…须更新 SELinux ç–略，以授予 cameraserver æ£ç¡®çš„æƒé™ã€‚我们建议ä¸è¦ä¸º cameraserver å¤åˆ¶ mediaserver çš„ SELinux ç–ç•¥ï¼ˆå› ä¸º mediaserver å’Œ cameraserver 通常需è¦ç³»ç»Ÿä¸çš„ä¸åŒèµ„æºï¼‰ã€‚Cameraserver 应仅具有执行相机功能所需的æƒé™ï¼Œå¹¶ä¸” mediaserver ä¸ä»»ä½•ä¸å¿…è¦çš„相机相关æƒé™å‡åº”被移除。<p></p> <h3 id="hardening_validation">验è¯</h3> diff --git a/zh-cn/devices/media/oem.html b/zh-cn/devices/media/oem.html index 02f2d34d..da274f4c 100644 --- a/zh-cn/devices/media/oem.html +++ b/zh-cn/devices/media/oem.html @@ -97,7 +97,8 @@ following codecs' concurrent instances limit in /etc/media_codecs.xml: <ol> <li>首先使用 cts-tradefed è¿è¡Œæµ‹è¯•ã€‚鉴于 Android 性能的波动性，建议多次è¿è¡Œæµ‹è¯•ä»¥èŽ·å¾—更准确的最å°å€¼å’Œæœ€å¤§å€¼ã€‚ </li><li>使用æ供的 <a href="https://android.googlesource.com/platform/cts/+/marshmallow-cts-dev/tools/cts-media/get_achievable_rates.py">get_achievable_rates.py</a> è„šæœ¬ç”Ÿæˆ XML 文件。 - </li><li>å°† XML 文件放置在以下ä½ç½®ï¼š<code>/etc/media_codecs_performance.xml</code><br />通常通过将 XML 文件放置在设备项目 (device/<vendor>/<product>) ä¸å¹¶å°† <code>PRODUCT_COPY_FILES</code> è¡Œæ·»åŠ åˆ° <code>device.mk</code> æ¥å®Œæˆæ¤è¿‡ç¨‹ï¼Œå¦‚下所示：<em></em><em></em> + </li><li>å°† XML 文件放置在以下ä½ç½®ï¼š<code>/etc/media_codecs_performance.xml</code><br /> +为了完æˆæ¤è¿‡ç¨‹ï¼Œæ‚¨é€šå¸¸éœ€è¦å°† XML 文件放置在设备项目 (device/<vendor><product>) ä¸å¹¶å°† <code>PRODUCT_COPY_FILES</code> è¡Œæ·»åŠ åˆ° <code>device.mk</code> ä¸ï¼Œå¦‚下所示：<em></em><em></em> <pre class="devsite-click-to-copy"> PRODUCT_COPY_FILES += \ ... diff --git a/zh-cn/devices/sensors/batching.html b/zh-cn/devices/sensors/batching.html index 13bee9bd..52efd81c 100644 --- a/zh-cn/devices/sensors/batching.html +++ b/zh-cn/devices/sensors/batching.html @@ -68,7 +68,7 @@ 在挂起模å¼ä¸‹ï¼Œ<code>max_report_latency</code> 对éžå”¤é†’ FIFO 没有影å“。</p> <p>当唤醒 FIFO å˜æ»¡æ—¶ï¼Œæˆ–者当其ä¸ä¸€ä¸ªå”¤é†’ä¼ æ„Ÿå™¨çš„ <code>max_report_latency</code> 已过时，硬件必须唤醒 SoC 并报告数æ®ã€‚</p> <p>在这两ç§æƒ…况下（唤醒和éžå”¤é†’），åªè¦ SoC 退出挂起模å¼ï¼Œå³ä½¿ä¸€äº›ä¼ 感器的 <code>max_report_latency</code> 未过，也会产生一个包å«æ‰€æœ‰ FIFO 内容的批处ç†ã€‚è¿™æ ·å¯æœ€å¤§é™åº¦åœ°é™ä½Ž SoC å†æ¬¡æŒ‚起而必须é‡æ–°å°†å…¶å”¤é†’的风险。这进而å¯ä»¥æœ€å¤§é™åº¦åœ°é™ä½ŽåŠŸè€—。</p> -<p>*ä¸å…许驱动程åºæŒæœ‰å”¤é†’é”定的一个明显例外情况是，在 <code>max_report_latency</code> å°äºŽ 1 秒时，å¯ç”¨<a href="report-modes.html#continuous">è¿žç»æŠ¥å‘Šæ¨¡å¼</a>çš„å”¤é†’ä¼ æ„Ÿå™¨ã€‚åœ¨æ¤æƒ…况下，驱动程åºå¯ä»¥æŒæœ‰å”¤é†’é”ï¼Œè¿™æ˜¯å› ä¸º SoC 在进入挂起模å¼å‰ä¼šè¢«å”¤é†’äº‹ä»¶å”¤é†’ï¼Œå› æ¤æ²¡æœ‰æœºä¼šè¿›å…¥æŒ‚起模å¼ã€‚</p> +<p>*ä¸å…许驱动程åºæŒæœ‰å”¤é†’é”定的一个明显例外情况是，在 <code>max_report_latency</code> å°äºŽ 1 秒的情况下å¯ç”¨ä½¿ç”¨<a href="report-modes.html#continuous">è¿žç»æŠ¥å‘Šæ¨¡å¼</a>çš„å”¤é†’ä¼ æ„Ÿå™¨ã€‚åœ¨æ¤æƒ…况下，驱动程åºå¯ä»¥æŒæœ‰å”¤é†’é”ï¼Œè¿™æ˜¯å› ä¸º SoC 在进入挂起模å¼å‰ä¼šè¢«å”¤é†’äº‹ä»¶å”¤é†’ï¼Œå› æ¤æ²¡æœ‰æœºä¼šè¿›å…¥æŒ‚起模å¼ã€‚</p> <h2 id="precautions_to_take_when_batching_wake-up_sensors">批处ç†å”¤é†’ä¼ æ„Ÿå™¨æ—¶çš„æ³¨æ„事项</h2> <p>æ ¹æ®è®¾å¤‡ä¸åŒï¼ŒSoC å¯èƒ½éœ€è¦å‡ 毫秒æ‰èƒ½å®Œå…¨é€€å‡ºæŒ‚起模å¼å¹¶å¼€å§‹åˆ·æ–° FIFOã€‚å› æ¤å¿…须在 FIFO ä¸åˆ†é…足够的头空间，æ‰èƒ½è®©è®¾å¤‡å®Œå…¨é€€å‡ºæŒ‚起状æ€ï¼Œè€Œä¸é€ æˆå”¤é†’ FIFO 溢出。ä¸å¾—丢失任何事件，并且必须éµç…§ <code>max_report_latency</code>。</p> <h2 id="precautions_to_take_when_batching_non-wake-up_on-change_sensors">批处ç†é‡‡ç”¨ On-change 触å‘æ–¹å¼çš„éžå”¤é†’ä¼ æ„Ÿå™¨æ—¶çš„æ³¨æ„事项</h2> diff --git a/zh-cn/devices/sensors/hal-interface.html b/zh-cn/devices/sensors/hal-interface.html index 89c05590..3891ffd5 100644 --- a/zh-cn/devices/sensors/hal-interface.html +++ b/zh-cn/devices/sensors/hal-interface.html @@ -131,7 +131,7 @@ int (*setDelay)( <p>刷写异æ¥å‘生（å³è¯¥å‡½æ•°å¿…须立å³è¿”回）。如果实现将一个 FIFO ç”¨äºŽå¤šä¸ªä¼ æ„Ÿå™¨ï¼Œåˆ™åˆ·å†™è¯¥ FIFOï¼Œå¹¶ä¸”ä»…ä¸ºæŒ‡å®šä¼ æ„Ÿå™¨æ·»åŠ åˆ·å†™å®Œæˆäº‹ä»¶ã€‚</p> <p>å¦‚æžœæŒ‡å®šä¼ æ„Ÿå™¨æ²¡æœ‰ FIFOï¼ˆæ— æ³•ç¼“å†²ï¼‰ï¼Œæˆ–è€…å¦‚æžœ FIFO 在调用时为空，则 <code>flush</code> ä»å¿…é¡»æ“作æˆåŠŸå¹¶ä¸ºè¯¥ä¼ 感器å‘é€åˆ·å†™å®Œæˆäº‹ä»¶ã€‚这适用于除å•æ¬¡ä¼ æ„Ÿå™¨ä»¥å¤–çš„æ‰€æœ‰ä¼ æ„Ÿå™¨ã€‚</p> <p>当调用 <code>flush</code> 时，å³ä½¿è¯¥ä¼ 感器的 FIFO ä¸å·²ç»å˜åœ¨åˆ·å†™äº‹ä»¶ï¼Œä¹Ÿå¿…é¡»å¦å¤–åˆ›å»ºä¸€ä¸ªåˆ·å†™äº‹ä»¶å¹¶å°†å…¶æ·»åŠ åˆ° FIFO 的末尾，并且必须刷写 FIFO。<code>flush</code> 调用的次数必须ç‰äºŽåˆ›å»ºçš„刷写完æˆäº‹ä»¶æ•°ã€‚</p> -<p><code>flush</code> ä¸é€‚用于<a href="report-modes.html#one-shot">å•æ¬¡</a>ä¼ æ„Ÿå™¨ã€‚å¦‚æžœ <code>sensor_handle</code> 指å‘的是å•æ¬¡ä¼ 感器，则 <code>flush</code> 必须返回 <code>-EINVAL</code>，并且ä¸ç”Ÿæˆä»»ä½•åˆ·å†™å®Œæˆå…ƒæ•°æ®äº‹ä»¶ã€‚</p> +<p><code>flush</code> ä¸é€‚用于<a href="report-modes.html#one-shot">å•æ¬¡</a>ä¼ æ„Ÿå™¨ã€‚å¦‚æžœ <code>sensor_handle</code> 引用的是å•æ¬¡ä¼ 感器，则 <code>flush</code> 必须返回 <code>-EINVAL</code>，并且ä¸ç”Ÿæˆä»»ä½•åˆ·å†™å®Œæˆå…ƒæ•°æ®äº‹ä»¶ã€‚</p> <p>如果æ“作æˆåŠŸï¼Œè¯¥å‡½æ•°è¿”回 0ï¼›å¦‚æžœæŒ‡å®šçš„ä¼ æ„Ÿå™¨æ˜¯å•æ¬¡ä¼ 感器或未å¯ç”¨ï¼Œåˆ™è¿”回 <code>-EINVAL</code>；其他情况，返回表示错误的负数。</p> <h2 id="poll">poll()</h2> <pre class="prettyprint">int (*poll)(struct sensors_poll_device_t *dev, sensors_event_t* data, int @@ -164,9 +164,9 @@ int (*setDelay)( <p><strong>power</strong>：å¯ç”¨ä¼ 感器的功耗æˆæœ¬ï¼Œä»¥æ¯«å®‰ä¸ºå•ä½ã€‚该å—æ®µå€¼å‡ ä¹Žå§‹ç»ˆå¤§äºŽåº•å±‚ä¼ æ„Ÿå™¨çš„ç›¸å…³æ•°æ®è¡¨ä¸æŠ¥å‘Šçš„功耗。è¦äº†è§£è¯¦æƒ…，请å‚阅<a href="sensor-types.html#base_sensors_=_not_equal_to_physical_sensors">åŸºç¡€ä¼ æ„Ÿå™¨ä¸ç‰äºŽç‰©ç†ä¼ 感器</a>è¿™ç¯‡æ–‡ç« ï¼›è¦è¯¦ç»†äº†è§£å¦‚何测é‡ä¼ 感器的功耗，请å‚阅<a href="power-use.html#power_measurement_process">功率测é‡è¿‡ç¨‹</a>ã€‚å¦‚æžœä¼ æ„Ÿå™¨çš„åŠŸè€—å–决于设备是å¦æ£åœ¨ç§»åŠ¨ï¼Œåˆ™ <code>power</code> å—段ä¸æŠ¥å‘Šçš„值是移动时的功耗。</p> <p><strong>minDelay</strong>：对于连ç»ä¼ æ„Ÿå™¨ï¼ŒæŒ‡å¯¹åº”äºŽä¼ æ„Ÿå™¨æ”¯æŒçš„æœ€å¿«é€ŸçŽ‡çš„é‡‡æ ·å‘¨æœŸï¼ˆä»¥å¾®ç§’ä¸ºå•ä½ï¼‰ã€‚è¦è¯¦ç»†äº†è§£è¯¥å€¼æ˜¯å¦‚何使用的，请å‚阅 <a href="#sampling_period_ns">sampling_period_ns</a>。请注æ„，<code>minDelay</code> 以微秒为å•ä½ï¼Œè€Œ <code>sampling_period_ns</code> 以纳秒为å•ä½ã€‚对于å˜åŒ–和特殊报告模å¼ä¼ 感器，除éžå¦è¡ŒæŒ‡å®šï¼Œå¦åˆ™ <code>minDelay</code> 必须为 0。对于å•æ¬¡ä¼ 感器，该值必须为 -1。</p> <p><strong>maxDelay</strong>：对于连ç»å’Œå˜åŒ–模å¼ä¼ æ„Ÿå™¨ï¼ŒæŒ‡å¯¹åº”äºŽä¼ æ„Ÿå™¨æ”¯æŒçš„æœ€æ…¢é€ŸçŽ‡çš„é‡‡æ ·å‘¨æœŸï¼ˆä»¥å¾®ç§’ä¸ºå•ä½ï¼‰ã€‚è¦è¯¦ç»†äº†è§£è¯¥å€¼æ˜¯å¦‚何使用的，请å‚阅 <a href="#sampling_period_ns">sampling_period_ns</a>。请注æ„，<code>maxDelay</code> 以微秒为å•ä½ï¼Œè€Œ <code>sampling_period_ns</code> 以纳秒为å•ä½ã€‚对于特殊和å•æ¬¡ä¼ 感器，<code>maxDelay</code> 必须为 0。</p> -<p><strong>fifoReservedEventCount</strong>：硬件 FIFO ä¸ä¸ºè¯¥ä¼ 感器ä¿ç•™çš„äº‹ä»¶æ•°ã€‚å¦‚æžœè¯¥ä¼ æ„Ÿå™¨æœ‰ä¸“å±žçš„ FIFO，则 <code>fifoReservedEventCount</code> 是该专属 FIFO 的大å°ã€‚如果该 FIFO ä¸Žå…¶ä»–ä¼ æ„Ÿå™¨å…±ç”¨ï¼Œåˆ™ <code>fifoReservedEventCount</code> æ˜¯ä¸ºè¯¥ä¼ æ„Ÿå™¨ä¿ç•™çš„ FIFO 部分的大å°ã€‚对于大多数共享 FIFO 的系统以åŠæ²¡æœ‰ç¡¬ä»¶ FIFO 的系统，该值为 0。</p> +<p><strong>fifoReservedEventCount</strong>：硬件 FIFO ä¸ä¸ºè¯¥ä¼ 感器ä¿ç•™çš„äº‹ä»¶æ•°ã€‚å¦‚æžœè¯¥ä¼ æ„Ÿå™¨æœ‰ä¸“å±žçš„ FIFO，则 <code>fifoReservedEventCount</code> 是该专属 FIFO 的大å°ã€‚å¦‚æžœè¯¥ä¼ æ„Ÿå™¨ä¸Žå…¶ä»–ä¼ æ„Ÿå™¨å…±ç”¨ FIFO，则 <code>fifoReservedEventCount</code> æ˜¯ä¸ºè¯¥ä¼ æ„Ÿå™¨ä¿ç•™çš„ FIFO 部分的大å°ã€‚对于大多数共享 FIFO 的系统以åŠæ²¡æœ‰ç¡¬ä»¶ FIFO 的系统，该值为 0。</p> <p><strong>fifoMaxEventCount</strong>：FIFO ä¸å¯ä¸ºè¯¥ä¼ 感器å˜å‚¨çš„最大事件数。该值总是大于或ç‰äºŽ <code>fifoReservedEventCount</code>。该值用于估计在å‡è®¾ä¸æ¿€æ´»ä»»ä½•å…¶ä»–ä¼ æ„Ÿå™¨çš„æƒ…å†µä¸‹ï¼Œä»¥ç‰¹å®šé€ŸçŽ‡æ³¨å†Œåˆ°ä¼ æ„Ÿå™¨æ—¶ FIFO 多快会被填满。对于没有硬件 FIFO 的系统，<code>fifoMaxEventCount</code> 为 0。è¦äº†è§£è¯¦æƒ…，请å‚阅<a href="batching.html">批é‡å¤„ç†</a>。</p> -<p>å¯¹äºŽå®˜æ–¹ä¼ æ„Ÿå™¨ç±»åž‹çš„ä¼ æ„Ÿå™¨ï¼Œä¸€äº›å—段会被框架覆盖。例如，<a href="sensor-types.html#accelerometer">åŠ é€Ÿåº¦è®¡</a>ä¼ æ„Ÿå™¨è¢«å¼ºåˆ¶ä½¿ç”¨è¿žç»æŠ¥å‘Šæ¨¡å¼ï¼Œè€Œ<a href="sensor-types.html#heart_rate">心率</a>ç›‘æµ‹å™¨åˆ™è¢«å¼ºåˆ¶å— <code>SENSOR_PERMISSION_BODY_SENSORS</code> æƒé™çš„ä¿æŠ¤ã€‚</p> +<p>å¯¹äºŽå®˜æ–¹ä¼ æ„Ÿå™¨ç±»åž‹çš„ä¼ æ„Ÿå™¨ï¼Œä¸€äº›å—段会被框架覆盖。例如，强制è¦æ±‚<a href="sensor-types.html#accelerometer">åŠ é€Ÿåº¦è®¡</a>ä¼ æ„Ÿå™¨ä½¿ç”¨è¿žç»æŠ¥å‘Šæ¨¡å¼ï¼Œå¹¶å¼ºåˆ¶è¦æ±‚<a href="sensor-types.html#heart_rate">心率</a>ç›‘æµ‹å™¨å— <code>SENSOR_PERMISSION_BODY_SENSORS</code> æƒé™çš„ä¿æŠ¤ã€‚</p> <h2 id="sensors_event_t">sensors_event_t</h2> <p>ç”± Android ä¼ æ„Ÿå™¨ç”Ÿæˆå¹¶é€šè¿‡ <a href="#poll">poll</a> å‡½æ•°æŠ¥å‘Šçš„ä¼ æ„Ÿå™¨äº‹ä»¶å±žäºŽ <code>type sensors_event_t</code>。以下是 <code>sensors_event_t</code> 的一些é‡è¦å—段：</p> <p><strong>version</strong>：必须是 <code>sizeof(struct sensors_event_t)</code>。</p> diff --git a/zh-cn/devices/sensors/index.html b/zh-cn/devices/sensors/index.html index c2cde4b3..d453ebaf 100644 --- a/zh-cn/devices/sensors/index.html +++ b/zh-cn/devices/sensors/index.html @@ -55,7 +55,7 @@ <ul> <li>å¯ä»¥å˜åœ¨å‡ 个相åŒç±»åž‹çš„ä¼ æ„Ÿå™¨ã€‚ä¾‹å¦‚ï¼Œä¸¤ä¸ªè¿‘ç¨‹ä¼ æ„Ÿå™¨æˆ–ä¸¤ä¸ªåŠ é€Ÿåº¦è®¡ã€‚</li> <li>ç»å¤§å¤šæ•°åº”用仅会请求给定类型的å•ä¸ªä¼ æ„Ÿå™¨ã€‚ä¾‹å¦‚ï¼Œè¯·æ±‚é»˜è®¤åŠ é€Ÿåº¦è®¡çš„åº”ç”¨å°†èŽ·å¾—åˆ—è¡¨ä¸çš„ç¬¬ä¸€ä¸ªåŠ é€Ÿåº¦è®¡ã€‚</li> - <li>ä¼ æ„Ÿå™¨é€šå¸¸ç”±<a href="suspend-mode.html#wake-up_sensors">唤醒</a>å’Œ<a href="suspend-mode.html#non-wake-up_sensors">éžå”¤é†’</a>对定义，两ç§ä¼ 感器共享åŒä¸€ç±»åž‹ï¼Œä½†å…¶å”¤é†’特性ä¸åŒã€‚</li> + <li>ä¼ æ„Ÿå™¨é€šå¸¸ç”±<a href="suspend-mode.html#wake-up_sensors">唤醒</a>å’Œ<a href="suspend-mode.html#non-wake-up_sensors">éžå”¤é†’</a>对进行定义，两ç§ä¼ 感器会共用åŒä¸€ç±»åž‹ï¼Œä½†å…¶å”¤é†’特性ä¸åŒã€‚</li> </ul> </li> </ul> @@ -110,7 +110,7 @@ <ul> <li><a href="/compatibility/android-cdd.pdf">https://source.android.com/compatibility/android-cdd.pdf</a></li> <li>æŸ¥çœ‹æœ‰å…³ä¼ æ„Ÿå™¨çš„éƒ¨åˆ†ã€‚</li> - <li>CDD çš„è¦æ±‚很宽æ¾ï¼Œå› æ¤æ»¡è¶³ CDD è¦æ±‚ä¸è¶³ä»¥ç¡®ä¿ä¼ 感器质é‡ä¼šå¾ˆé«˜ã€‚</li> + <li>CDD çš„è¦æ±‚很宽æ¾ï¼Œå› æ¤æ»¡è¶³ CDD è¦æ±‚ä¸è¶³ä»¥ç¡®ä¿ä¼ 感器的质é‡å¾ˆé«˜ã€‚</li> </ul> </li> </ul> diff --git a/zh-cn/devices/sensors/sensor-types.html b/zh-cn/devices/sensors/sensor-types.html index dbedb825..bc306675 100644 --- a/zh-cn/devices/sensors/sensor-types.html +++ b/zh-cn/devices/sensors/sensor-types.html @@ -99,7 +99,7 @@ <p>ä»…å½“ä¼ æ„Ÿå™¨å·²ç¦ç”¨æ—¶ï¼Œæ‰å¯æ›´æ–°åå·®æ ¡å‡†å’Œå°ºåº¦æ ¡å‡†ï¼Œä»¥é¿å…æµå¼ä¼ 输时出现值激增。</p> <p>åŠ é€Ÿåº¦è®¡è¿˜é€šè¿‡ <code>sensors_event_t.acceleration.status</code> 报告其预测的读数精度。è¦è¯¦ç»†äº†è§£æ¤å—段的å¯èƒ½å€¼ï¼Œè¯·å‚阅 <a href="https://developer.android.com/reference/android/hardware/SensorManager.html">SensorManager</a> çš„ <a href="https://developer.android.com/reference/android/hardware/SensorManager.html#SENSOR_STATUS_ACCURACY_HIGH"><code>SENSOR_STATUS_* </code></a>常é‡ã€‚</p> <h3 id="ambient_temperature">çŽ¯å¢ƒæ¸©åº¦ä¼ æ„Ÿå™¨</h3> -<p>报告模å¼ï¼š<em><a href="report-modes.html#on-change">按å˜åŒ–模å¼</a></em></p> +<p>报告模å¼ï¼š<em><a href="report-modes.html#on-change">å˜åŒ–模å¼</a></em></p> <p><code>getDefaultSensor(SENSOR_TYPE_AMBIENT_TEMPERATURE)</code> 会返回一个éžå”¤é†’ä¼ æ„Ÿå™¨<em></em></p> <p>è¯¥ä¼ æ„Ÿå™¨å¯æ供环境（室内）温度，å•ä½æ˜¯æ‘„æ°åº¦ã€‚</p> <h3 id="magnetic_field_sensor">ç£åœºä¼ 感器</h3> @@ -136,12 +136,12 @@ <p>以æ¯åˆ†é’Ÿå¿ƒè·³æ¬¡æ•° (BPM) 表示的当å‰å¿ƒçŽ‡åœ¨ <code>sensors_event_t.heart_rate.bpm</code> ä¸æŠ¥å‘Šï¼Œè€Œä¼ 感器的状æ€åœ¨ <code>sensors_event_t.heart_rate.status</code> ä¸æŠ¥å‘Šã€‚è¦è¯¦ç»†äº†è§£æ¤å—段的å¯èƒ½å€¼ï¼Œè¯·å‚阅 <a href="https://developer.android.com/reference/android/hardware/SensorManager.html">SensorManager</a> çš„ <a href="https://developer.android.com/reference/android/hardware/SensorManager.html#SENSOR_STATUS_ACCURACY_HIGH"><code>SENSOR_STATUS_*</code></a> 常é‡ã€‚特别是在第一次激活时，除éžç³»ç»Ÿå·²çŸ¥è®¾å¤‡æœªéšèº«æºå¸¦ï¼Œå¦åˆ™é¦–次事件的状æ€å—段必须设置为 <code>SENSOR_STATUS_UNRELIABLE</code>ã€‚å› ä¸ºä¼ æ„Ÿå™¨é‡‡ç”¨å˜åŒ–模å¼ï¼Œå½“且仅当 <code>heart_rate.bpm</code> 或 <code>heart_rate.status</code> 自上次事件åŽå·²å‘生å˜åŒ–æ—¶æ‰ä¼šè§¦å‘事件。事件生æˆé€Ÿåº¦ä¸ä¼šå¤§äºŽæ¯éš” <code>sampling_period</code> 一次。</p> <p><code>sensor_t.requiredPermission</code> 始终是 <code>SENSOR_PERMISSION_BODY_SENSORS</code>。</p> <h3 id="light">å…‰çº¿ä¼ æ„Ÿå™¨</h3> -<p>报告模å¼ï¼š<em><a href="report-modes.html#on-change">按å˜åŒ–模å¼</a></em></p> +<p>报告模å¼ï¼š<em><a href="report-modes.html#on-change">å˜åŒ–模å¼</a></em></p> <p><code>getDefaultSensor(SENSOR_TYPE_LIGHT)</code> 会返回一个éžå”¤é†’ä¼ æ„Ÿå™¨<em></em></p> <p>å…‰çº¿ä¼ æ„Ÿå™¨å¯æŠ¥å‘Šå½“å‰ç…§æ˜Žåº¦ï¼Œé‡‡ç”¨å›½é™…å•ä½å‹’å…‹æ–¯ (lux)。</p> <p>测é‡ç»“果在 <code>sensors_event_t.light</code> ä¸æŠ¥å‘Šã€‚</p> <h3 id="proximity">è¿‘ç¨‹ä¼ æ„Ÿå™¨</h3> -<p>报告模å¼ï¼š<em><a href="report-modes.html#on-change">按å˜åŒ–模å¼</a></em></p> +<p>报告模å¼ï¼š<em><a href="report-modes.html#on-change">å˜åŒ–模å¼</a></em></p> <p>é€šå¸¸å®šä¹‰ä¸ºå”¤é†’ä¼ æ„Ÿå™¨</p> <p><code>getDefaultSensor(SENSOR_TYPE_PROXIMITY)</code> ä¼šè¿”å›žä¸€ä¸ªå”¤é†’ä¼ æ„Ÿå™¨<em></em></p> <p>è¿‘ç¨‹ä¼ æ„Ÿå™¨å¯æŠ¥å‘Šä»Žä¼ 感器到最近的å¯è§è¡¨é¢çš„è·ç¦»ã€‚</p> @@ -159,7 +159,7 @@ </ul> <p>气压计通常用于估算高度å˜åŒ–。è¦ä¼°ç®—ç»å¯¹é«˜åº¦ï¼Œå¿…须将海平é¢åŽ‹åŠ›ï¼ˆéšå¤©æ°”å˜åŒ–）作为å‚照点。</p> <h3 id="relative_humidity">ç›¸å¯¹æ¹¿åº¦ä¼ æ„Ÿå™¨</h3> -<p>报告模å¼ï¼š<em><a href="report-modes.html#on-change">按å˜åŒ–模å¼</a></em></p> +<p>报告模å¼ï¼š<em><a href="report-modes.html#on-change">å˜åŒ–模å¼</a></em></p> <p><code>getDefaultSensor(SENSOR_TYPE_RELATIVE_HUMIDITY)</code> 会返回一个éžå”¤é†’ä¼ æ„Ÿå™¨<em></em></p> <p>ç›¸å¯¹æ¹¿åº¦ä¼ æ„Ÿå™¨ç”¨äºŽæµ‹é‡çŽ¯å¢ƒç©ºæ°”相对湿度，并返回百分比值。</p> @@ -310,7 +310,7 @@ <p>æ¯ä¸ªä¼ 感器事件在 <code>sensors_event_t.data[0]</code> ä¸æŠ¥å‘Š 1</p> <h3 id="step_detector">æ¥æµ‹å™¨</h3> <p>底层物ç†ä¼ æ„Ÿå™¨ï¼šåŠ é€Ÿåº¦è®¡ï¼ˆå¯èƒ½è¿˜æœ‰å…¶ä»–低功耗计é‡å™¨ï¼‰</p> -<p>报告模å¼ï¼š<em>特殊模å¼</em>（一æ¥è§¦å‘一个事件）<a href="report-modes.html#special"></a></p> +<p>报告模å¼ï¼š<a href="report-modes.html#special">特殊模å¼</a>（一æ¥è§¦å‘一个事件）<em></em></p> <p>低功耗</p> <p><code>getDefaultSensor(SENSOR_TYPE_STEP_DETECTOR)</code> 会返回一个éžå”¤é†’ä¼ æ„Ÿå™¨<em></em></p> <p>用户æ¯èµ°ä¸€æ¥ï¼Œæ¥æµ‹å™¨å°±è§¦å‘一个事件。</p> @@ -321,7 +321,7 @@ <p>æ¯ä¸ªä¼ 感器事件在 <code>sensors_event_t.data[0]</code> ä¸æŠ¥å‘Š 1</p> <h3 id="step_counter">计æ¥å™¨</h3> <p>底层物ç†ä¼ æ„Ÿå™¨ï¼šåŠ é€Ÿåº¦è®¡ï¼ˆå¯èƒ½è¿˜æœ‰å…¶ä»–低功耗计é‡å™¨ï¼‰</p> -<p>报告模å¼ï¼š<em><a href="report-modes.html#on-change">按å˜åŒ–模å¼</a></em></p> +<p>报告模å¼ï¼š<em><a href="report-modes.html#on-change">å˜åŒ–模å¼</a></em></p> <p>低功耗</p> <p><code>getDefaultSensor(SENSOR_TYPE_STEP_COUNTER)</code> 会返回一个éžå”¤é†’ä¼ æ„Ÿå™¨<em></em></p> <p>计æ¥å™¨æŠ¥å‘Šè‡ªæ¿€æ´»åŽä¸Šä¸€æ¬¡é‡æ–°å¯åŠ¨ä»¥æ¥ç”¨æˆ·è¡Œèµ°çš„æ¥æ•°ã€‚</p> @@ -423,7 +423,7 @@ </p> </div> <p>该定义与航空ä¸ä½¿ç”¨çš„å航ã€ä¿¯ä»°å’Œæ»šåŠ¨ä¸åŒï¼Œå…¶ä¸ X 轴沿飞机长边（机尾到机头）延伸。</p> -<p>æ–¹å‘ä¼ æ„Ÿå™¨è¿˜é€šè¿‡ sensors_event_t.orientation.status 报告其预测的度数精度。è¦è¯¦ç»†äº†è§£è¯¥å—段的å¯èƒ½å€¼ï¼Œè¯·å‚阅 <a href="https://developer.android.com/reference/android/hardware/SensorManager.html">SensorManager</a> çš„ <a href="https://developer.android.com/reference/android/hardware/SensorManager.html#SENSOR_STATUS_ACCURACY_HIGH">SENSOR_STATUS_</a>* 常é‡ã€‚</p> +<p>æ–¹å‘ä¼ æ„Ÿå™¨è¿˜é€šè¿‡ sensors_event_t.orientation.status 报告其预测的度数精度。è¦è¯¦ç»†äº†è§£æ¤å—段的å¯èƒ½å€¼ï¼Œè¯·å‚阅 <a href="https://developer.android.com/reference/android/hardware/SensorManager.html">SensorManager</a> çš„ <a href="https://developer.android.com/reference/android/hardware/SensorManager.html#SENSOR_STATUS_ACCURACY_HIGH">SENSOR_STATUS_</a>* 常é‡ã€‚</p> <h2 id="uncalibrated_sensors">æœªæ ¡å‡†ä¼ æ„Ÿå™¨</h2> <p>æœªæ ¡å‡†ä¼ æ„Ÿå™¨å¯æ供更多的原始结果，å¯èƒ½åŒ…括一些å差，还包å«æ ¡å‡†åŽæ›´æ£ç»“æžœä¸çš„少数“激增â€å€¼ã€‚一些应用å¯èƒ½æ›´å€¾å‘äºŽä½¿ç”¨è¿™äº›æœªæ ¡å‡†ç»“æžœï¼Œå› ä¸ºæ¤ç±»ç»“果更æµç•…ã€å¯é ã€‚ä¾‹å¦‚ï¼Œå¦‚æžœåº”ç”¨è¯•å›¾è‡ªå·±è¿›è¡Œä¼ æ„Ÿå™¨èžåˆï¼Œåˆ™å¼•å…¥æ ¡å‡†å¯èƒ½ä¼šä½¿ç»“果失真。</p> <h3 id="gyroscope_uncalibrated">æœªæ ¡å‡†é™€èžºä»ªä¼ æ„Ÿå™¨</h3> diff --git a/zh-cn/devices/tech/admin/multiuser-apps.html b/zh-cn/devices/tech/admin/multiuser-apps.html index 9f38e943..f15699bf 100644 --- a/zh-cn/devices/tech/admin/multiuser-apps.html +++ b/zh-cn/devices/tech/admin/multiuser-apps.html @@ -71,7 +71,7 @@ INTERACT_ACROSS_USERS_FULL (signature) </li><li><code>Context.bindServiceAsUser(Intent, …, UserHandle)</code> </li><li><code>Context.sendBroadcastAsUser(Intent, … , UserHandle)</code> </li><li><code>Context.startServiceAsUser(Intent, …, UserHandle) -UserHandle</code> å¯èƒ½æ˜¯æ˜¾å¼ç”¨æˆ·æˆ–特殊å¥æŸ„之一：<code>UserHandle.CURRENT</code> 或 <code>UserHandle.ALL</code>。<code>CURRENT</code> 表示当å‰å¤„于å‰å°çš„用户。如果您想å‘所有用户å‘é€å¹¿æ’，则å¯ä»¥ä½¿ç”¨ <code>ALL</code>。 +UserHandle</code> å¯èƒ½æ˜¯æ˜¾å¼ç”¨æˆ·æˆ–特殊å¥æŸ„之一：<code>UserHandle.CURRENT</code> 或 <code>UserHandle.ALL</code>。<code>CURRENT</code> 表示当å‰ä½äºŽå‰å°çš„用户。如果您想å‘所有用户å‘é€å¹¿æ’，则å¯ä»¥ä½¿ç”¨ <code>ALL</code>。 </li></ul> </li><li>è¦ä¸Žæ‚¨è‡ªå·±åº”用ä¸çš„组件通信，请使用： <code>(INTERACT_ACROSS_USERS)</code> diff --git a/zh-cn/devices/tech/admin/testing-provision.html b/zh-cn/devices/tech/admin/testing-provision.html index 4ca77664..749e01d7 100644 --- a/zh-cn/devices/tech/admin/testing-provision.html +++ b/zh-cn/devices/tech/admin/testing-provision.html @@ -204,12 +204,12 @@ TestRunner: java.lang.RuntimeException: Failed to load page: com.android.afwtest 这类错误通常是由之å‰çš„ç•Œé¢ç½‘é¡µæˆ–åŠ è½½å¤±è´¥çš„ç½‘é¡µä¸çš„é”™è¯¯æ‰€å¯¼è‡´ï¼Œå› æ¤ï¼Œè¯·å°è¯•åœ¨ logcat ä¸æ‰¾åˆ°å‡ºçŽ°è¯¥é”™è¯¯ä¹‹å‰çš„其他错误消æ¯ï¼Œç„¶åŽæŒ‰ç…§é…ç½®æµç¨‹æ‰‹åŠ¨é‡çŽ°è¯¥é”™è¯¯ã€‚</li> <li>如果测试包è¿è¡Œå¤±è´¥ï¼š <ul> -<li>系统会使用以下è¯æ³•å°†å±å¹•æˆªå›¾ä¿å˜åˆ° <code>out/host/linux-x86/afw-th/android-cts/repository/logs/<em>start-time</em></code>：<code>screenshot-test_<em>test_class_full_name</em>_<em>test_case_name</em>-<em>random_number</em>.png</code>。该信æ¯ä¹Ÿä¼šè®°å½•åœ¨ä¸»æœºæ—¥å¿—ä¸ã€‚</li> +<li>系统会使用下列è¯æ³•å°†å±å¹•æˆªå›¾ä¿å˜åˆ° <code>out/host/linux-x86/afw-th/android-cts/repository/logs/<em>start-time</em></code>：<code>screenshot-test_<em>test_class_full_name</em>_<em>test_case_name</em>-<em>random_number</em>.png</code>。该信æ¯ä¹Ÿä¼šè®°å½•åœ¨ä¸»æœºæ—¥å¿—ä¸ã€‚</li> <li>错误报告会以下列形å¼ä¿å˜åˆ° <code>out/host/linux-x86/afw-th/android-cts/repository/logs/<em>start-time</em></code>：<code>bug-<em>test_class_full_name</em>_<em>test_case_name</em>-<em>random_number</em>.zip</code>。 </li> </ul> </li> -<li>所有测试包å‡æ‰§è¡Œå®Œæ¯•åŽï¼Œå±å¹•æˆªå›¾ä¼šä»¥ <code>screenshot-<em>random_number</em>.png</code> çš„å½¢å¼ä¿å˜åˆ° <code>out/host/linux-x86/afw-th/android-cts/repository/logs/<em>start-time</em></code>。该信æ¯ä¹Ÿä¼šè®°å½•åœ¨ä¸»æœºæ—¥å¿—ä¸ã€‚</li> +<li>所有测试包å‡æ‰§è¡Œå®Œæ¯•åŽï¼Œç³»ç»Ÿä¼šæˆªå–å±å¹•æˆªå›¾ï¼Œå¹¶å°†å…¶ä»¥ä¸‹åˆ—å½¢å¼ä¿å˜åˆ° <code>out/host/linux-x86/afw-th/android-cts/repository/logs/<em>start-time</em></code>：<code>screenshot-<em>random_number</em>.png</code>。该信æ¯ä¹Ÿä¼šè®°å½•åœ¨ä¸»æœºæ—¥å¿—ä¸ã€‚</li> </ul> <h2 id="faq">常è§é—®é¢˜è§£ç”</h2> diff --git a/zh-cn/devices/tech/config/filesystem.html b/zh-cn/devices/tech/config/filesystem.html index 624d7ee3..da333bc6 100644 --- a/zh-cn/devices/tech/config/filesystem.html +++ b/zh-cn/devices/tech/config/filesystem.html @@ -37,7 +37,7 @@ <aside class="note"><strong>注æ„</strong>：虽然您ä»å¯ä»¥ä½¿ç”¨<a href="#older">旧版 Android ä¸çš„文件系统替æ¢æ–¹æ³•</a>，但ä¸èƒ½åŒæ—¶å†ä½¿ç”¨æ–°çš„ AID 机制。建议您尽å¯èƒ½ä½¿ç”¨æ–°çš„机制。</aside> <h2 id="adding-android-ids-aids">æ·»åŠ Android ID (AID)</h2> -<p>Android 8.0 从 Android å¼€æºé¡¹ç›® (AOSP) ä¸ç§»é™¤äº† <code>android_ids[]</code> æ•°ç»„ã€‚æ‰€æœ‰é€‚åˆ AID çš„åç§°éƒ½æ”¹ä¸ºåœ¨ç”Ÿæˆ Bionic <code>android_ids[]</code> 数组时从 <code>system/core/include/private/android_filesystem_config.h</code> æ ‡å¤´æ–‡ä»¶ç”Ÿæˆã€‚è¿™ç§æœºåˆ¶ä¼šæå–与 <code>AID_*</code> 匹é…的所有 <code>define</code>，且 <strong>*</strong> 会å˜ä¸ºå°å†™å称。</p> +<p>Android 8.0 从 Android å¼€æºé¡¹ç›® (AOSP) ä¸ç§»é™¤äº† <code>android_ids[]</code> æ•°ç»„ã€‚æ‰€æœ‰é€‚åˆ AID çš„åç§°éƒ½æ”¹ä¸ºåœ¨ç”Ÿæˆ Bionic <code>android_ids[]</code> 数组时从 <code>system/core/include/private/android_filesystem_config.h</code> æ ‡å¤´æ–‡ä»¶ç”Ÿæˆã€‚è¿™ç§æœºåˆ¶ä¼šæå–与 <code>define</code> 匹é…的所有 <code>AID_*</code>，且 <strong></strong> 会å˜ä¸ºå°å†™å称。</p> <p>例如，在 <code>private/android_filesystem_config.h</code> ä¸ï¼š</p> @@ -56,7 +56,7 @@ <p> è¦å¯ç”¨æ–°çš„ AID 机制，请在 <code>BoardConfig.mk</code> 文件ä¸è®¾ç½® <code>TARGET_FS_CONFIG_GEN</code>。æ¤å˜é‡å«æœ‰é…置文件列表，使您å¯ä»¥æ ¹æ®éœ€è¦é™„åŠ æ–‡ä»¶ã€‚</p> -<aside class="caution"><strong>注æ„</strong>：请勿通过旧版 Android ä¸æ—©æœŸçš„ <code>TARGET_ANDROID_FILESYSTEM_CONFIG_H</code> 方法使用 <code>TARGET_FS_CONFIG_GEN</code>ï¼å¦åˆ™ï¼Œæ‚¨ä¼šæ”¶åˆ°é”™è¯¯æ示。</aside> +<aside class="caution"><strong>注æ„</strong>：请勿通过旧版 Android ä¸æ—©æœŸçš„ <code>TARGET_FS_CONFIG_GEN</code> 方法使用 <code>TARGET_ANDROID_FILESYSTEM_CONFIG_H</code>ï¼å¦åˆ™ï¼Œæ‚¨ä¼šæ”¶åˆ°é”™è¯¯æ示。</aside> <p>按照惯例，é…置文件使用å称 <code>config.fs</code>，但在实践ä¸ï¼Œæ‚¨å¯ä»¥ä½¿ç”¨ä»»ä½•å称。<code>config.fs</code> 文件采用 <a href="https://docs.python.org/2/library/configparser.html" class="external">Python ConfigParser ini æ ¼å¼</a>ï¼Œå¹¶åŒ…å« caps 部分（用于é…置文件系统æƒèƒ½ï¼‰å’Œ AID 部分（用于é…ç½® OEM 专属 AID）。 </p> @@ -129,7 +129,7 @@ <td><code>value</code></td> <td><number></td> <td>有效的 C æ ·å¼çš„æ•°å—å—符串（åå…进制ã€å…«è¿›åˆ¶ã€äºŒè¿›åˆ¶å’Œå进制）。 - <br /><br />使用åŒä¸€å€¼é€‰é¡¹æŒ‡å®šå¤šä¸ªéƒ¨åˆ†<strong>或</strong>指定超出收录的 OEM 范围（在 <code>system/core/include/private/android_filesystem_config.h</code> ä¸æŒ‡å®šï¼‰çš„值，属于错误的åšæ³•ï¼š + <br /><br />使用åŒä¸€å€¼é€‰é¡¹æŒ‡å®šå¤šä¸ªéƒ¨åˆ†<strong>或</strong>指定超出收录的 OEM 范围（在 <code>system/core/include/private/android_filesystem_config.h</code> ä¸æŒ‡å®šï¼‰çš„值，都属于错误的åšæ³•ï¼š <ul> <li>AID_OEM_RESERVED_START(2900) - AID_OEM_RESERVED_END(2999)</li> <li>AID_OEM_RESERVED_2_START(5000) - AID_OEM_RESERVED_2_END(5999)</li> diff --git a/zh-cn/devices/tech/dalvik/improvements.html b/zh-cn/devices/tech/dalvik/improvements.html index 87907a72..6d4ad734 100644 --- a/zh-cn/devices/tech/dalvik/improvements.html +++ b/zh-cn/devices/tech/dalvik/improvements.html @@ -200,7 +200,7 @@ <h2 id="faster-native-methods">更快速的原生方法</h2> <p> - å¯ä»¥ä½¿ç”¨ <a class="external" href="https://android.googlesource.com/platform/libcore/+/master/dalvik/src/main/java/dalvik/annotation/optimization/FastNative.java"><code>@FastNative</code></a> å’Œ <a class="external" href="https://android.googlesource.com/platform/libcore/+/master/dalvik/src/main/java/dalvik/annotation/optimization/CriticalNative.java"><code>@CriticalNative</code></a> 注解实现对 Java åŽŸç”ŸæŽ¥å£ (JNI) 更快速的原生调用。这ç§å†…置的 ART è¿è¡Œæ—¶ä¼˜åŒ–åŠ å¿«äº† JNI 转æ¢å¹¶å–代了现在已弃用的 !<em>bang JNI æ ‡è®°ã€‚</em>注解对éžåŽŸç”Ÿæ–¹æ³•æ²¡æœ‰ä»»ä½•å½±å“，并且仅适用于 <code>bootclasspath</code> ä¸Šçš„å¹³å° Java è¯è¨€ä»£ç ï¼ˆæ— Play 商店更新）。 + 使用 <a class="external" href="https://android.googlesource.com/platform/libcore/+/master/dalvik/src/main/java/dalvik/annotation/optimization/FastNative.java"><code>@FastNative</code></a> å’Œ <a class="external" href="https://android.googlesource.com/platform/libcore/+/master/dalvik/src/main/java/dalvik/annotation/optimization/CriticalNative.java"><code>@CriticalNative</code></a> 注解å¯å®žçŽ°å¯¹ Java åŽŸç”ŸæŽ¥å£ (JNI) 更快速的原生调用。这ç§å†…置的 ART è¿è¡Œæ—¶ä¼˜åŒ–åŠ å¿«äº† JNI 转æ¢ï¼Œå¹¶å–代了现在已弃用的 !<em>bang JNI æ ‡è®°ã€‚</em>注解对éžåŽŸç”Ÿæ–¹æ³•æ²¡æœ‰ä»»ä½•å½±å“，并且仅适用于 <code>bootclasspath</code> ä¸Šçš„å¹³å° Java è¯è¨€ä»£ç ï¼ˆæ— Play 商店更新）。 </p> <p> diff --git a/zh-cn/devices/tech/datausage/tags-explained.html b/zh-cn/devices/tech/datausage/tags-explained.html index e97b4a43..814136e8 100644 --- a/zh-cn/devices/tech/datausage/tags-explained.html +++ b/zh-cn/devices/tech/datausage/tags-explained.html @@ -1,5 +1,5 @@ <html devsite><head> - <title>æµé‡æ¶ˆè€—æ ‡ç¾è¯´æ˜Ž</title> + <title>æµé‡ä½¿ç”¨æƒ…å†µæ ‡ç¾è¯´æ˜Ž</title> <meta name="project_path" value="/_project.yaml"/> <meta name="book_path" value="/_book.yaml"/> </head> diff --git a/zh-cn/devices/tech/debug/ftrace.html b/zh-cn/devices/tech/debug/ftrace.html index 1dee6a9b..dc2e42a8 100644 --- a/zh-cn/devices/tech/debug/ftrace.html +++ b/zh-cn/devices/tech/debug/ftrace.html @@ -48,7 +48,7 @@ echo 1 > /d/tracing/events/irq/enable echo 1 > /d/tracing/events/sched/sched_wakeup/enable </pre> -<p>如果通过写入 sysfs 节点å¯ç”¨äº†é¢å¤–的事件，这些事件将<strong>ä¸ä¼š</strong>被 atrace é‡ç½®ã€‚Qualcomm 设备å¯åŠ¨çš„常用模å¼æ˜¯å¯ç”¨ <code>kgsl</code> (GPU) å’Œ <code>mdss</code>（显示管é“）跟踪点，然åŽä½¿ç”¨ atrace 或 <a href="/devices/tech/debug/systrace.html">systrace</a>：</p> +<p>如果通过写入 sysfs 节点å¯ç”¨äº†é¢å¤–的事件，这些事件将<strong>ä¸ä¼š</strong>被 atrace é‡ç½®ã€‚Qualcomm 设备å¯åŠ¨çš„常è§æ¨¡å¼æ˜¯å¯ç”¨ <code>kgsl</code> (GPU) å’Œ <code>mdss</code>（显示管é“）跟踪点，然åŽä½¿ç”¨ atrace 或 <a href="/devices/tech/debug/systrace.html">systrace</a>：</p> <pre class="devsite-click-to-copy"> <code class="devsite-terminal">adb shell "echo 1 > /d/tracing/events/mdss/enable"</code> @@ -206,7 +206,7 @@ cat /d/tracing/trace > /data/local/tmp/trace <h2 id="lock_stat">使用 lockstat</h2> <p>有时，åªæœ‰ ftrace 是ä¸å¤Ÿçš„ï¼Œæ‚¨å¿…é¡»è°ƒè¯•å†…æ ¸é”争用。还有一ç§å†…æ ¸é€‰é¡¹å€¼å¾—å°è¯•ï¼š<code>CONFIG_LOCK_STAT</code>。这是最åŽä¸€ç§æ–¹æ³•ï¼Œå› 为è¦åœ¨ Android 设备上应用这一方法éžå¸¸å›°éš¾ï¼ŒåŽŸå› æ˜¯å®ƒä¼šä½¿å†…æ ¸çš„å¤§å°è¶…出大多数设备å¯ä»¥å¤„ç†çš„范围。</p> -<p>ä¸è¿‡ï¼Œlockstat 使用调试é”基础设施，这对很多其他应用都有帮助。负责设备å¯åŠ¨çš„所有人都应想出方法æ¥ä½¿è¯¥é€‰é¡¹é€‚用于æ¯å°è®¾å¤‡ï¼Œå› 为您<strong>也许</strong>会想“如果我å¯ä»¥å¼€å¯ <code>LOCK_STAT</code>，就å¯ä»¥åœ¨ 5 分钟（而ä¸æ˜¯ 5 天）内确认或å驳这一问题â€ã€‚</p> +<p>ä¸è¿‡ï¼Œlockstat 使用调试é”基础设施，这对很多其他应用都有帮助。负责设备å¯åŠ¨çš„æ¯ä¸ªäººéƒ½åº”该想法让该选项适用于æ¯å°è®¾å¤‡ï¼Œå› 为，如果<strong>以åŽ</strong>碰到这方é¢çš„事情，您å¯èƒ½ä¼šæƒ³â€œè¦æ˜¯èƒ½å¼€å¯ <code>LOCK_STAT</code>，我就å¯ä»¥åœ¨ 5 分钟（而ä¸æ˜¯ 5 天）内判æ–是ä¸æ˜¯è¿™æ–¹é¢çš„问题â€ã€‚</p> <section class="expandable"> <h4 class="showalways">æ˜¾ç¤ºé—®é¢˜ï¼šå½“å†…æ ¸ä»¥æœ€å¤§è´Ÿè½½è¿è¡Œ non-SCHED_FIFO 时，SCHED_FIFO 终æ¢</h4> @@ -239,6 +239,6 @@ cat /proc/lock_stat > /data/local/tmp/lock_stat </li> </ol> -<p>有关解释所生æˆçš„输出结果的帮助内容，请å‚阅 lockstat 文档：<a href="https://www.kernel.org/doc/Documentation/locking/lockstat.txt"><code><kernel>/Documentation/locking/lockstat.txt</code></a>。</p> +<p>è¦èŽ·å–关于解读所生æˆçš„输出结果的帮助信æ¯ï¼Œè¯·å‚阅 lockstat 文档：<a href="https://www.kernel.org/doc/Documentation/locking/lockstat.txt"><code><kernel>/Documentation/locking/lockstat.txt</code></a>。</p> </body></html>
\ No newline at end of file diff --git a/zh-cn/devices/tech/debug/gdb.html b/zh-cn/devices/tech/debug/gdb.html index e6757058..7f17247a 100644 --- a/zh-cn/devices/tech/debug/gdb.html +++ b/zh-cn/devices/tech/debug/gdb.html @@ -20,7 +20,7 @@ limitations under the License. --> -<p>GNU é¡¹ç›®è°ƒè¯•ç¨‹åº (GDB) 是常用的 Unix 调试程åºã€‚本页详细介ç»äº†å¦‚何使用 <code>gdb</code> 调试 Android 应用和进程。</p> +<p>GNU é¡¹ç›®è°ƒè¯•ç¨‹åº (GDB) 是常用的 Unix 调试程åºã€‚本页详细介ç»äº†å¦‚何使用 <code>gdb</code> 调试 Android 应用和进程（é¢å‘å¹³å°å¼€å‘者）。对于第三方应用开å‘，请å‚阅<a href="https://developer.android.com/studio/debug/index.html">调试您的应用</a>。</p> <h2 id="running">调试è¿è¡Œä¸çš„应用或进程</h2> diff --git a/zh-cn/devices/tech/ota/ab/index.html b/zh-cn/devices/tech/ota/ab/index.html index d7bb1755..54f698d9 100644 --- a/zh-cn/devices/tech/ota/ab/index.html +++ b/zh-cn/devices/tech/ota/ab/index.html @@ -23,7 +23,9 @@ <p>A/B ç³»ç»Ÿæ›´æ–°ï¼ˆä¹Ÿç§°ä¸ºæ— ç¼æ›´æ–°ï¼‰çš„ç›®æ ‡æ˜¯ç¡®ä¿åœ¨<a href="/devices/tech/ota/index.html">æ— çº¿ä¸‹è½½ (OTA) æ›´æ–°</a>期间在ç£ç›˜ä¸Šä¿ç•™ä¸€ä¸ªå¯æ£å¸¸å¯åŠ¨å’Œä½¿ç”¨çš„系统。采用这ç§æ–¹å¼å¯ä»¥é™ä½Žæ›´æ–°ä¹‹åŽè®¾å¤‡æ— 法å¯åŠ¨çš„å¯èƒ½æ€§ï¼Œè¿™æ„味ç€ç”¨æˆ·éœ€è¦å°†è®¾å¤‡é€åˆ°ç»´ä¿®å’Œä¿ä¿®ä¸å¿ƒè¿›è¡Œæ›´æ¢å’Œåˆ·æœºçš„情况将会å‡å°‘。其他æŸäº›å•†ä¸šçº§æ“作系统（例如 <a href="https://www.chromium.org/chromium-os">ChromeOS</a>）也æˆåŠŸè¿ç”¨äº† A/B 更新机制。 </p> - <p>A/B 系统更新å¯å¸¦æ¥ä»¥ä¸‹å¥½å¤„：</p> + <p>è¦è¯¦ç»†äº†è§£ A/B 系统更新，请å‚è§<a href="#slots">分区选择（槽ä½ï¼‰</a>一节。 + + </p><p>A/B 系统更新å¯å¸¦æ¥ä»¥ä¸‹å¥½å¤„：</p> <ul> <li> @@ -137,7 +139,7 @@ A/B 系统更新过程会使用å为 <code>update_engine</code> çš„åŽå°å®ˆæŠ¤ </ul> <p> -由于 <code>update_engine</code> 守护进程本身ä¸ä¼šå‚与到å¯åŠ¨æµç¨‹ä¸ï¼Œå› æ¤è¯¥å®ˆæŠ¤è¿›ç¨‹åœ¨æ›´æ–°æœŸé—´å¯ä»¥æ‰§è¡Œçš„æ“作å—当å‰æ§½ä½ä¸çš„ <a href="/security/selinux/">SELinux</a> 政ç–和功能é™åˆ¶ï¼ˆåœ¨ç³»ç»Ÿå¯åŠ¨åˆ°æ–°ç‰ˆæœ¬ä¹‹å‰ï¼Œæ¤ç±»æ”¿ç–å’ŒåŠŸèƒ½æ— æ³•æ›´æ–°ï¼‰ã€‚<em></em>为了维æŒä¸€ä¸ªç¨³å®šå¯é 的系统，更新æµç¨‹<strong>ä¸åº”</strong>修改分区表ã€å½“å‰æ§½ä½ä¸å„个分区的内容，以åŠæ— 法通过æ¢å¤å‡ºåŽ‚è®¾ç½®æ“¦é™¤çš„éž A/B 分区的内容。 +由于 <code>update_engine</code> 守护进程本身ä¸ä¼šå‚与到å¯åŠ¨æµç¨‹ä¸ï¼Œå› æ¤è¯¥å®ˆæŠ¤è¿›ç¨‹åœ¨æ›´æ–°æœŸé—´å¯æ‰§è¡Œçš„æ“作å—é™äºŽå½“å‰æ§½ä½ä¸çš„ <a href="/security/selinux/">SELinux</a> 政ç–和功能（在系统å¯åŠ¨åˆ°æ–°ç‰ˆæœ¬ä¹‹å‰ï¼Œæ¤ç±»æ”¿ç–å’ŒåŠŸèƒ½æ— æ³•æ›´æ–°ï¼‰ã€‚<em></em>为了维æŒä¸€ä¸ªç¨³å®šå¯é 的系统，更新æµç¨‹<strong>ä¸åº”</strong>修改分区表ã€å½“å‰æ§½ä½ä¸å„个分区的内容，以åŠæ— 法通过æ¢å¤å‡ºåŽ‚è®¾ç½®æ“¦é™¤çš„éž A/B 分区的内容。 </p> <h4 id="update_engine_source">更新引擎æºä»£ç </h4> @@ -156,7 +158,7 @@ A/B 系统更新过程会使用å为 <code>update_engine</code> çš„åŽå°å®ˆæŠ¤ </ul> <p> -如需å¯ä½¿ç”¨çš„示例，请å‚阅 <code><a href="https://android.googlesource.com/device/google/marlin/+/nougat-dr1-release/device-common.mk" class="external-link">/device/google/marlin/device-common.mk</a></code>。 +如需实际示例，请å‚阅 <code><a href="https://android.googlesource.com/device/google/marlin/+/nougat-dr1-release/device-common.mk" class="external-link">/device/google/marlin/device-common.mk</a></code>。 </p> <h4 id="update_engine_logs">更新引擎日志</h4> @@ -178,7 +180,7 @@ A/B 系统更新过程会使用å为 <code>update_engine</code> çš„åŽå°å®ˆæŠ¤ 更改 594637</a></li> </ul> - <p>这些更改会将最新的 <code>update_engine</code> 日志的副本ä¿å˜åˆ° <code>/data/misc/update_engine_log/update_engine.<var>YEAR</var>-<var>TIME</var></code>。除当å‰æ—¥å¿—以外，最近的五个日志也ä¿å˜åœ¨ <code>/data/misc/update_engine_log/</code> 下方。拥有<strong>日志</strong>组 ID 的用户将能够访问相应的文件系统日志。</p> + <p>这些更改会将最新的 <code>update_engine</code> 日志的副本ä¿å˜åˆ° <code>/data/misc/update_engine_log/update_engine.<var>YEAR</var>-<var>TIME</var></code>。除当å‰æ—¥å¿—以外，最近的五个日志也会ä¿å˜åœ¨ <code>/data/misc/update_engine_log/</code> 下方。拥有<strong>日志</strong>组 ID 的用户将能够访问相应的文件系统日志。</p> <h3 id="bootloader-interactions">å¼•å¯¼åŠ è½½ç¨‹åºäº¤äº’</h3> diff --git a/zh-cn/devices/tech/ota/index.html b/zh-cn/devices/tech/ota/index.html index fa5bb3da..0ed9dc39 100644 --- a/zh-cn/devices/tech/ota/index.html +++ b/zh-cn/devices/tech/ota/index.html @@ -21,19 +21,19 @@ --> <p> - æ£å¸¸ä½¿ç”¨çš„ Android 设备å¯ä»¥æŽ¥æ”¶å’Œå®‰è£…ç³»ç»Ÿå’Œåº”ç”¨è½¯ä»¶çš„æ— çº¿ (OTA) 更新。本部分介ç»äº†æ›´æ–°åŒ…的结构以åŠæž„建更新包时所用的工具。它适用于希望将 OTA 更新系统用于新的 Android 设备以åŠæ£åœ¨ç¼–译更新软件包以用于已å‘布设备的开å‘者。OTA 更新旨在å‡çº§åŸºç¡€æ“作系统和系统分区上安装的åªè¯»åº”用；这些更新<em>ä¸ä¼š</em>å½±å“用户从 Google Play 安装的应用。 + æ£å¸¸ä½¿ç”¨çš„ Android 设备å¯ä»¥æŽ¥æ”¶å’Œå®‰è£…ç³»ç»Ÿå’Œåº”ç”¨è½¯ä»¶çš„æ— çº¿ (OTA) 更新。本部分介ç»äº†æ›´æ–°åŒ…的结构以åŠæž„建更新包时所用的工具。它适用于希望将 OTA 更新系统用于新的 Android 设备以åŠæ£åœ¨ç¼–译更新软件包以用于已å‘布设备的开å‘者。<em></em>OTA 更新旨在å‡çº§åŸºç¡€æ“作系统和系统分区上安装的åªè¯»åº”用；这些更新ä¸ä¼šå½±å“用户从 Google Play 安装的应用。 </p> - <h2 id="ab_updates">A/B æ›´æ–°</h2> + <h2 id="ab_updates">A/Bï¼ˆæ— ç¼ï¼‰ç³»ç»Ÿæ›´æ–°</h2> <p> - 现代 A/B 设备ä¸çš„æ¯ä¸ªåˆ†åŒºéƒ½æœ‰ä¸¤ä¸ªå‰¯æœ¬ï¼ˆA å’Œ B）。当系统è¿è¡Œä½†å¤„于空闲状æ€æ—¶ï¼Œè®¾å¤‡ä¼šå°†æ›´æ–°åº”用到当å‰æœªä½¿ç”¨çš„分区。A/B 设备ä¸éœ€è¦ç©ºé—´æ¥ä¸‹è½½æ›´æ–°è½¯ä»¶åŒ…ï¼Œå› ä¸ºå®ƒä»¬å¯ä»¥åœ¨ä»Žç½‘络ä¸è¯»å–更新时应用该更新。这被称为“æµå¼ä¼ 输 A/Bâ€ã€‚A/B æ›´æ–°ä¹Ÿè¢«ç§°ä¸ºâ€œæ— ç¼æ›´æ–°â€ã€‚<em></em><em></em>è¦è¯¦ç»†äº†è§£æœ‰å…³ A/B 设备的 OTA 更新，请å‚阅 <a href="/devices/tech/ota/ab/index.html">A/Bï¼ˆæ— ç¼ï¼‰ç³»ç»Ÿæ›´æ–°</a>。 + 现代 A/B 设备ä¸çš„æ¯ä¸ªåˆ†åŒºéƒ½æœ‰ä¸¤ä¸ªå‰¯æœ¬ï¼ˆA å’Œ B）。当系统è¿è¡Œä½†å¤„于空闲状æ€æ—¶ï¼Œè®¾å¤‡ä¼šå°†æ›´æ–°åº”用到当å‰æœªä½¿ç”¨çš„分区。A/B 设备ä¸éœ€è¦ç©ºé—´æ¥ä¸‹è½½æ›´æ–°è½¯ä»¶åŒ…ï¼Œå› ä¸ºå®ƒä»¬å¯ä»¥åœ¨ä»Žç½‘络ä¸è¯»å–更新时应用该更新。这被称为“æµå¼ä¼ 输 A/Bâ€ã€‚A/B æ›´æ–°ä¹Ÿè¢«ç§°ä¸ºâ€œæ— ç¼æ›´æ–°â€ã€‚<em></em><em></em>è¦è¯¦ç»†äº†è§£æœ‰å…³ A/B 设备的 OTA 更新，请å‚阅 <a href="/devices/tech/ota/ab/index.html">A/Bï¼ˆæ— ç¼ï¼‰ç³»ç»Ÿæ›´æ–°</a>一文。 </p> - <h2 id="nonab_updates">éž A/B æ›´æ–°</h2> + <h2 id="nonab_updates">éž A/B 系统更新</h2> <p> - è€æ¬¾è®¾å¤‡å¯åœ¨ç‰¹æ®Šçš„æ¢å¤åˆ†åŒºä¸ä½¿ç”¨è½¯ä»¶è§£åŽ‹ç¼©ä¸‹è½½çš„更新包并将其应用于其他分区。有关详细信æ¯ï¼Œè¯·æŸ¥çœ‹<a href="/devices/tech/ota/nonab/index.html">éž A/B 系统更新</a>。 + è€æ¬¾è®¾å¤‡å¯åœ¨ç‰¹æ®Šçš„æ¢å¤åˆ†åŒºä¸ä½¿ç”¨è½¯ä»¶è§£åŽ‹ç¼©ä¸‹è½½çš„更新包并将其应用于其他分区。有关详细信æ¯ï¼Œè¯·å‚阅<a href="/devices/tech/ota/nonab/index.html">éž A/B 系统更新</a>一文。 </p> </body></html>
\ No newline at end of file diff --git a/zh-cn/devices/tech/ota/reduce_size.html b/zh-cn/devices/tech/ota/reduce_size.html index 5268b6ec..cdeb517f 100644 --- a/zh-cn/devices/tech/ota/reduce_size.html +++ b/zh-cn/devices/tech/ota/reduce_size.html @@ -73,7 +73,7 @@ <li>è¦äº†è§£æ“ä½œç³»ç»Ÿçš„ç¼–è¯‘æ—¶é—´ï¼Œè¯·è¯»å– <code>ro.build.date</code>（应该会对除增é‡ç¼–译之外的所有内容都适用；增é‡ç¼–译å¯èƒ½ä¸ä¼šæ›´æ–°æ¤æ—¥æœŸï¼‰ã€‚è¦æŸ¥çœ‹ç¤ºä¾‹ï¼Œè¯·å‚阅：<a href="https://android.googlesource.com/platform/external/libchrome/+/8b7977eccc94f6b3a3896cd13b4aeacbfa1e0f84" class="external">https://android.googlesource.com/platform/external/libchrome/+/8b7977eccc94f6b3a3896cd13b4aeacbfa1e0f84</a>。</li> </ul> -<aside class="note"><strong>注æ„</strong>：Android 7.0 å¼€å¯äº† <code>-Werror=date-time</code>ï¼Œå› æ¤ä½¿ç”¨æ—¶é—´æˆ³æ˜¯ä¸€ç§ç¼–译错误。</aside> +<aside class="note"><strong>注æ„</strong>：Android 7.0 å¼€å¯äº† <code>-Werror=date-time</code>ï¼Œå› æ¤ä½¿ç”¨æ—¶é—´æˆ³ä¼šå¯¼è‡´ç¼–译错误。</aside> <h3 id="embedded_timestamps_in_zip-based_archives_zip_jar">归档文件（zipã€jar）ä¸çš„嵌入时间戳</h3> diff --git a/zh-cn/devices/tech/perf/boot-times.html b/zh-cn/devices/tech/perf/boot-times.html index 74b39a90..468ead6f 100644 --- a/zh-cn/devices/tech/perf/boot-times.html +++ b/zh-cn/devices/tech/perf/boot-times.html @@ -212,14 +212,22 @@ CONFIG_MOBICORE_DRIVER=y <h3 id="deferring-initialization">延迟åˆå§‹åŒ–</h3> <p> -很多进程都在设备å¯åŠ¨æœŸé—´å¯åŠ¨ï¼Œä½†åªæœ‰å…³é”®è·¯å¾„ (bootloader > kernel > init > file system mount > zygote > system server) ä¸çš„组件æ‰ä¼šç›´æŽ¥å½±å“å¯åŠ¨æ—¶é—´ã€‚åœ¨å†…æ ¸å¯åŠ¨æœŸé—´æ‰§è¡Œ <strong>initcall</strong> æ¥è¯†åˆ«å¯¹å¯åŠ¨ init 进程ä¸é‡è¦çš„外设/组件，然åŽå°†è¿™äº›å¤–设/组件延迟到å¯åŠ¨è¿‡ç¨‹çš„åŽæœŸæ¥å¯åŠ¨ã€‚ +很多进程都在设备å¯åŠ¨æœŸé—´å¯åŠ¨ï¼Œä½†åªæœ‰å…³é”®è·¯å¾„ (bootloader > kernel > init > file system mount > zygote > system server) ä¸çš„组件æ‰ä¼šç›´æŽ¥å½±å“å¯åŠ¨æ—¶é—´ã€‚åœ¨å†…æ ¸å¯åŠ¨æœŸé—´åˆ†æž <strong>initcall</strong> 的执行情况æ¥è¯†åˆ«æ‰§è¡Œç¼“慢并且对å¯åŠ¨ init 进程ä¸é‡è¦çš„外设/组件，将这些外设/ç»„ä»¶ç¼–è¯‘ä¸ºå†…æ ¸æ¨¡å—并延迟到å¯åŠ¨è¿‡ç¨‹çš„åŽæœŸæ¥å¯åŠ¨ã€‚将外设/组件的åˆå§‹åŒ–过程改为异æ¥å¹¶è¡Œä¹Ÿæœ‰åŠ©äºŽè§£å†³ä»Žå†…æ ¸åˆ°init的关键路径。 </p> -<pre class="prettyprint"> +<pre +class="prettyprint"> BoardConfig-common.mk: BOARD_KERNEL_CMDLINE += initcall_debug ignore_loglevel + +驱动程åº: + .probe_type = PROBE_PREFER_ASYNCHRONOUS, </pre> +<p class="note"> +<strong>注æ„</strong> ：谨慎处ç†é©±åŠ¨ç¨‹åºçš„ä¾èµ–性，如有其他驱动程åºä¾èµ–于被异æ¥çš„驱动程åºï¼Œè¦ç¡®ä¿ <code>EPROBEDEFER</code> 的支æŒæƒ…况。 +</p> + <h2 id="optimizing-i-o-efficiency">优化 I/O 效率</h2> <p> @@ -346,6 +354,10 @@ Init æ˜¯ä»Žå†…æ ¸åˆ°æ¡†æž¶å»ºç«‹ä¹‹å‰çš„衔接过程，设备通常会在ä¸åŒ </li><li>å¯åŠ¨æœåŠ¡å¹¶åŠæ—©å¯ç”¨å…³é”®è·¯å¾„ä¸çš„外围设备。例如，有些 SOC 需è¦å…ˆå¯åŠ¨å®‰å…¨ç›¸å…³æœåŠ¡ï¼Œç„¶åŽå†å¯åŠ¨ SurfaceFlinger。在 ServiceManager 返回“wait for serviceâ€ï¼ˆç‰å¾…æœåŠ¡ï¼‰æ—¶æŸ¥çœ‹ç³»ç»Ÿæ—¥å¿— - 这通常表明必须先å¯åŠ¨ä¾èµ–æœåŠ¡ã€‚ </li><li>移除 init.*.rc ä¸æ‰€æœ‰æœªä½¿ç”¨çš„æœåŠ¡å’Œå‘½ä»¤ã€‚åªè¦æ˜¯æ—©æœŸé˜¶æ®µçš„ init ä¸æ²¡æœ‰ä½¿ç”¨çš„æœåŠ¡å’Œå‘½ä»¤ï¼Œéƒ½åº”推迟到å¯åŠ¨å®ŒæˆåŽå†ä½¿ç”¨ã€‚</li></ul> +<p class="note"> +<strong>注æ„</strong> ：属性æœåŠ¡æ˜¯ init 进程的一部分，如果在init执行内部脚本命令期间，在代ç ä¸è°ƒç”¨è®¾ç½®å±žæ€§çš„函数有å¯èƒ½è¢«å»¶è¿Ÿ +</p> + <h3 id="using-scheduler-tuning">使用调度程åºè°ƒæ•´</h3> <p> @@ -555,4 +567,4 @@ systrace çš„å¯è§†åŒ–å¯ä»¥å¸®åŠ©åˆ†æžå¯åŠ¨è¿‡ç¨‹ä¸çš„具体问题。（ä¸è¿ <strong>注æ„</strong>：Chrome æ— æ³•å¤„ç†è¿‡å¤§çš„文件。请考虑使用 <code>tail</code>ã€<code>head</code> 或 <code>grep</code> 分割 <code>boot_trace</code> 文件，以获得必è¦çš„部分。由于事件过多，I/O 分æžé€šå¸¸éœ€è¦ç›´æŽ¥åˆ†æžèŽ·å–çš„ <code>boot_trace</code>。 </p> -</body></html>
\ No newline at end of file +</body></html> diff --git a/zh-cn/legal.html b/zh-cn/legal.html index 6e97ba7c..a7534dff 100644 --- a/zh-cn/legal.html +++ b/zh-cn/legal.html @@ -30,7 +30,7 @@ <h2 id="Brands">Android å“牌</h2> -<p>“Androidâ€å称ã€<img src="/setup/assets/images/sac_logo.png" alt="Android" style="margin:0;padding:0 2px;vertical-align:baseline"/> å¾½æ ‡å’Œ<a href="http://www.google.com/permissions/">å…¶ä»–å•†æ ‡</a>å‡ä¸º Google LLC 的财产。</p> +<p>“Androidâ€å称ã€<img src="/setup/assets/images/sac_logo.png" alt="Android" style="margin:0;padding:0 2px;vertical-align:baseline"/> å¾½æ ‡åŠ<a href="http://www.google.com/permissions/">å…¶ä»–å•†æ ‡</a>å‡ä¸º Google LLC 的财产。</p> <p>è¦äº†è§£æ›´å¤šè¯¦æƒ…，请å‚阅<a href="/setup/brands.html">å“牌推广指å—</a>。</p> @@ -45,4 +45,4 @@ <div> -</div></div></body></html> +</div></div></body></html>
\ No newline at end of file diff --git a/zh-cn/license.html b/zh-cn/license.html index 4603793b..b9eb8f96 100644 --- a/zh-cn/license.html +++ b/zh-cn/license.html @@ -38,7 +38,7 @@ <h2 id="terms">使用æ¡æ¬¾</h2> -<p>我们éžå¸¸ä¹æ„æ ¹æ®ç›¸åº”æ¡æ¬¾æŽˆæƒæ‚¨ä½¿ç”¨ Android 文档和示例代ç ，这些æ¡æ¬¾é¼“åŠ±æ‚¨æ ¹æ®éœ€è¦é‡‡ç”¨ã€ä¿®æ”¹ã€é‡å¤ä½¿ç”¨ã€æ”¹ç¼–或混编æ¤ç±»å†…容。您å¯ä»¥åœ¨è‡ªå·±çš„作å“ä¸éšæ„使用文档内容，除éžä¸‹æ–‡çš„<a href="#restrictions">é™åˆ¶</a>部分å¦æœ‰è¯´æ˜Žã€‚例如，您å¯ä»¥åœ¨ä¸€æœ¬ä¹¦ä¸å¼•ç”¨ç›¸åº”çš„æ–‡å—，将æŸäº›éƒ¨åˆ†çš„内容剪切并粘贴到您的åšå®¢ä¸ï¼Œå°†ç›¸åº”内容录制æˆæœ‰å£°è¯»ç‰©ä¾›è§†éšœäººå£«æ”¶å¬ï¼Œç”šè‡³è¿˜å¯ä»¥å°†ç›¸åº”内容翻译æˆå…¶ä»–è¯è¨€ã€‚</p> +<p>我们éžå¸¸ä¹æ„æ ¹æ®ç›¸åº”æ¡æ¬¾æŽˆæƒæ‚¨ä½¿ç”¨ Android 文档和示例代ç ，这些æ¡æ¬¾é¼“åŠ±æ‚¨æ ¹æ®éœ€è¦é‡‡ç”¨ã€ä¿®æ”¹ã€é‡å¤ä½¿ç”¨ã€æ”¹ç¼–或混编æ¤ç±»å†…容。您å¯ä»¥åœ¨è‡ªå·±çš„作å“ä¸éšæ„使用文档内容，除éžä¸‹æ–‡çš„<a href="#restrictions">é™åˆ¶</a>部分å¦æœ‰è¯´æ˜Žã€‚例如，您å¯ä»¥åœ¨ä¸€æœ¬ä¹¦ä¸å¼•ç”¨ç›¸åº”çš„æ–‡å—，将部分内容剪切并粘贴到您的åšå®¢ä¸ï¼Œå½•åˆ¶æˆæœ‰å£°è¯»ç‰©ä¾›è§†éšœäººå£«æ”¶å¬ï¼Œç”šè‡³è¿˜å¯ä»¥ç¿»è¯‘æˆå…¶ä»–è¯è¨€ã€‚</p> <h2 id="restrictions">é™åˆ¶</h2> @@ -63,7 +63,7 @@ 如果您的在线作å“åŽŸæ ·å¤åˆ¶æœ¬ç½‘ç«™ä¸çš„全部或部分文å—或图片，请在网页底部附上以下这段内容：<em></em> </p> <p style="margin-left:20px;font-style:italic"> - 本网页的部分内容是从 <a href="https://code.google.com/p/android/">Android å¼€æºé¡¹ç›®</a>原创åŠå…±äº«ä½œå“ä¸å¤åˆ¶çš„，须éµç…§ <a href="https://creativecommons.org/licenses/by/3.0/">Creative Commons Attribution 3.0 许å¯</a>所述æ¡æ¬¾è¿›è¡Œä½¿ç”¨ã€‚ +本网页的部分内容是从 <a href="https://code.google.com/p/android/">Android å¼€æºé¡¹ç›®</a>原创åŠå…±äº«ä½œå“ä¸å¤åˆ¶çš„，须éµç…§ <a href="https://creativecommons.org/licenses/by/3.0/">Creative Commons Attribution 3.0 许å¯</a>所述æ¡æ¬¾è¿›è¡Œä½¿ç”¨ã€‚ </p> <p>æ¤å¤–，请æ供指å‘原始æ¥æºç½‘页的链接，以便读者å‚阅相应网页，了解更多信æ¯ã€‚ @@ -71,8 +71,7 @@ <h3>ç»è¿‡ä¿®æ”¹çš„版本</h3> <p> 如果您的在线作å“会显示在本网站内容的基础上<em>修改的</em>æ–‡å—或图片，请在您的网页底部附上以下这段内容：</p> -<p style="margin-left:20px;font-style:italic"> - 本网页的部分内容是在 <a href="https://code.google.com/p/android/">Android å¼€æºé¡¹ç›®</a>原创åŠå…±äº«ä½œå“的基础上修改而æˆçš„，须éµç…§ <a href="https://creativecommons.org/licenses/by/3.0/">Creative Commons Attribution 3.0 许å¯</a>所述æ¡æ¬¾è¿›è¡Œä½¿ç”¨ã€‚ +<p style="margin-left:20px;font-style:italic">本网页的部分内容是在 <a href="https://code.google.com/p/android/">Android å¼€æºé¡¹ç›®</a>原创åŠå…±äº«ä½œå“的基础上修改而æˆçš„，须éµç…§ <a href="https://creativecommons.org/licenses/by/3.0/">Creative Commons Attribution 3.0 许å¯</a>所述æ¡æ¬¾è¿›è¡Œä½¿ç”¨ã€‚ </p> <p>åŒæ ·ï¼Œè¯·æ供指å‘原始æ¥æºç½‘页的链接，以便读者å‚阅相应网页，了解更多信æ¯ã€‚在对相应内容åšè¿‡ä¿®æ”¹åŽï¼Œå°¤å…¶è¦è°¨è®°è¿™ä¸€ç‚¹ã€‚ </p> diff --git a/zh-cn/security/advisory/index.html b/zh-cn/security/advisory/index.html index 2e0028be..1c617e69 100644 --- a/zh-cn/security/advisory/index.html +++ b/zh-cn/security/advisory/index.html @@ -35,7 +35,12 @@ <tr> <td><a href="2016-03-18.html">2016-03-18</a></td> <td> - <a href="/security/advisory/2016-03-18.html">English</a> / <a href="/security/advisory/2016-03-18.html?hl=ja">日本語</a> / <a href="/security/advisory/2016-03-18.html?hl=ko">í•œêµì–´</a> / <a href="/security/advisory/2016-03-18.html?hl=ru">руÌÑÑкий</a> / <a href="/security/advisory/2016-03-18.html?hl=zh-cn">ä¸æ–‡Â (ä¸å›½)</a> / <a href="/security/advisory/2016-03-18.html?hl=zh-tw">ä¸æ–‡Â (å°ç£)</a> + <a href="/security/advisory/2016-03-18.html">English</a> / + <a href="/security/advisory/2016-03-18.html?hl=ja">日本語</a> / + <a href="/security/advisory/2016-03-18.html?hl=ko">í•œêµì–´</a> / + <a href="/security/advisory/2016-03-18.html?hl=ru">руÌÑÑкий</a> / + <a href="/security/advisory/2016-03-18.html?hl=zh-cn">ä¸æ–‡ï¼ˆä¸å›½ï¼‰</a>/ + <a href="/security/advisory/2016-03-18.html?hl=zh-tw">ä¸æ–‡ï¼ˆå°ç£ï¼‰</a> </td> <td>2016 å¹´ 3 月 18 æ—¥</td> </tr> diff --git a/zh-cn/security/apksigning/v2.html b/zh-cn/security/apksigning/v2.html index 3870b140..b32f6fff 100644 --- a/zh-cn/security/apksigning/v2.html +++ b/zh-cn/security/apksigning/v2.html @@ -1,5 +1,5 @@ <html devsite><head> - <title>APK ç¾å架构 v2</title> + <title>APK ç¾å方案 v2</title> <meta name="project_path" value="/_project.yaml"/> <meta name="book_path" value="/_book.yaml"/> </head> diff --git a/zh-cn/security/bulletin/2016-07-01.html b/zh-cn/security/bulletin/2016-07-01.html index c100c5ae..74ef6b98 100644 --- a/zh-cn/security/bulletin/2016-07-01.html +++ b/zh-cn/security/bulletin/2016-07-01.html @@ -41,7 +41,7 @@ <p>本部分总结了 <a href="/security/enhancements/index.html">Android 安全平å°</a>å’ŒæœåŠ¡é˜²æŠ¤åŠŸèƒ½ï¼ˆå¦‚ SafetyNet）æ供的缓解措施。这些功能å¯é™ä½Ž Android 上的安全æ¼æ´žè¢«æˆåŠŸåˆ©ç”¨çš„å¯èƒ½æ€§ã€‚</p> <ul> <li>新版 Android å¹³å°ä¸çš„å¢žå¼ºåŠŸèƒ½è®©æ”»å‡»è€…æ›´åŠ éš¾ä»¥åˆ©ç”¨ Android 上å˜åœ¨çš„许多问题。我们建议所有用户都尽å¯èƒ½æ›´æ–°åˆ°æœ€æ–°ç‰ˆ Android。</li> - <li>Android 安全团队会积æžåˆ©ç”¨<a href="/security/reports/Google_Android_Security_2015_Report_Final.pdf">“验è¯åº”用â€å’Œ SafetyNet</a> æ¥ç›‘控滥用行为，这些功能å¯åœ¨å‘现<a href="/security/reports/Google_Android_Security_PHA_classifications.pdf">å¯èƒ½æœ‰å®³çš„应用</a>æ—¶å‘用户å‘出è¦å‘Šã€‚在预装有 <a href="http://www.android.com/gms">Google 移动æœåŠ¡</a>的设备上，“验è¯åº”用â€åœ¨é»˜è®¤æƒ…况下处于å¯ç”¨çŠ¶æ€ã€‚对于安装æ¥è‡ª Google Play 以外的应用的用户æ¥è¯´ï¼Œè¿™é¡¹åŠŸèƒ½å°¤ä¸ºé‡è¦ã€‚虽然 Google Play ä¸ç¦æ¢æ供设备 Root 应用，但用户å¯èƒ½ä¼šå°è¯•å®‰è£… Root 应用，而“验è¯åº”用â€ä¼šåœ¨æ£€æµ‹åˆ°è¿™ç±»åº”ç”¨ï¼ˆæ— è®ºåº”ç”¨æ¥è‡ªä½•å¤„）时å‘用户å‘出è¦å‘Šã€‚å¦å¤–，“验è¯åº”用â€ä¼šå°è¯•è¯†åˆ«å¹¶é˜»æ¢ç”¨æˆ·å®‰è£…会利用ææƒæ¼æ´žçš„已知æ¶æ„应用。如果用户已安装æ¤ç±»åº”用，那么“验è¯åº”用â€å°†ä¼šé€šçŸ¥ç”¨æˆ·å¹¶å°è¯•ç§»é™¤æ‰€æ£€æµ‹åˆ°çš„应用。</li> + <li>Android 安全团队会积æžåˆ©ç”¨<a href="/security/reports/Google_Android_Security_2015_Report_Final.pdf">“验è¯åº”用â€å’Œ SafetyNet</a> æ¥ç›‘控滥用行为，这些功能会在å‘现<a href="/security/reports/Google_Android_Security_PHA_classifications.pdf">å¯èƒ½æœ‰å®³çš„应用</a>æ—¶å‘用户å‘出è¦å‘Šã€‚在预装有 <a href="http://www.android.com/gms">Google 移动æœåŠ¡</a>的设备上，“验è¯åº”用â€åœ¨é»˜è®¤æƒ…况下处于å¯ç”¨çŠ¶æ€ã€‚对于安装æ¥è‡ª Google Play 以外的应用的用户æ¥è¯´ï¼Œè¿™é¡¹åŠŸèƒ½å°¤ä¸ºé‡è¦ã€‚虽然 Google Play ä¸ç¦æ¢æ供设备 Root 应用，但用户å¯èƒ½ä¼šå°è¯•å®‰è£… Root 应用，而“验è¯åº”用â€ä¼šåœ¨æ£€æµ‹åˆ°è¿™ç±»åº”ç”¨ï¼ˆæ— è®ºåº”ç”¨æ¥è‡ªä½•å¤„）时å‘用户å‘出è¦å‘Šã€‚å¦å¤–，“验è¯åº”用â€ä¼šå°è¯•è¯†åˆ«å¹¶é˜»æ¢ç”¨æˆ·å®‰è£…会利用ææƒæ¼æ´žçš„已知æ¶æ„应用。如果用户已安装æ¤ç±»åº”用，那么“验è¯åº”用â€å°†ä¼šé€šçŸ¥ç”¨æˆ·å¹¶å°è¯•ç§»é™¤æ‰€æ£€æµ‹åˆ°çš„应用。</li> <li>由于已åšäº†é€‚å½“æ›´æ–°ï¼Œå› æ¤ Google 环èŠå’Œ Messenger 应用ä¸ä¼šè‡ªåŠ¨å°†åª’ä½“å†…å®¹ä¼ é€’ç»™ Mediaserver 这类进程。</li> </ul> @@ -99,7 +99,9 @@ </tr> <tr> <td>CVE-2016-2508</td> - <td><a href="https://android.googlesource.com/platform/frameworks/av/+/f81038006b4c59a5a148dcad887371206033c28f">A-28799341</a> [<a href="https://android.googlesource.com/platform/frameworks/av/+/d112f7d0c1dbaf0368365885becb11ca8d3f13a4">2</a>]</td> + <td><a href="https://android.googlesource.com/platform/frameworks/av/+/f81038006b4c59a5a148dcad887371206033c28f">A-28799341</a> + [<a href="https://android.googlesource.com/platform/frameworks/av/+/d112f7d0c1dbaf0368365885becb11ca8d3f13a4">2</a>] + </td> <td>严é‡</td> <td><a href="#all_nexus">所有 Nexus 设备</a></td> <td>4.4.4ã€5.0.2ã€5.1.1ã€6.0ã€6.0.1</td> @@ -107,7 +109,9 @@ </tr> <tr> <td>CVE-2016-3741</td> - <td><a href="https://android.googlesource.com/platform/external/libavc/+/e629194c62a9a129ce378e08cb1059a8a53f1795">A-28165661</a> [<a href="https://android.googlesource.com/platform/external/libavc/+/cc676ebd95247646e67907ccab150fb77a847335">2</a>]</td> + <td><a href="https://android.googlesource.com/platform/external/libavc/+/e629194c62a9a129ce378e08cb1059a8a53f1795">A-28165661</a> + [<a href="https://android.googlesource.com/platform/external/libavc/+/cc676ebd95247646e67907ccab150fb77a847335">2</a>] + </td> <td>严é‡</td> <td><a href="#all_nexus">所有 Nexus 设备</a></td> <td>6.0ã€6.0.1</td> @@ -460,7 +464,9 @@ </tr> <tr> <td>CVE-2016-3754</td> - <td><a href="https://android.googlesource.com/platform/frameworks/av/+/6fdee2a83432b3b150d6a34f231c4e2f7353c01e">A-28615448</a> [<a href="https://android.googlesource.com/platform/frameworks/av/+/e7142a0703bc93f75e213e96ebc19000022afed9">2</a>]</td> + <td><a href="https://android.googlesource.com/platform/frameworks/av/+/6fdee2a83432b3b150d6a34f231c4e2f7353c01e">A-28615448</a> + [<a href="https://android.googlesource.com/platform/frameworks/av/+/e7142a0703bc93f75e213e96ebc19000022afed9">2</a>] + </td> <td>高</td> <td><a href="#all_nexus">所有 Nexus 设备</a></td> <td>4.4.4ã€5.0.2ã€5.1.1ã€6.0ã€6.0.1</td> @@ -622,7 +628,10 @@ </tr> <tr> <td>CVE-2016-3760</td> - <td><a href="https://android.googlesource.com/platform/hardware/libhardware/+/8b3d5a64c3c8d010ad4517f652731f09107ae9c5">A-27410683</a> [<a href="https://android.googlesource.com/platform/system/bt/+/37c88107679d36c419572732b4af6e18bb2f7dce">2</a>] [<a href="https://android.googlesource.com/platform/packages/apps/Bluetooth/+/122feb9a0b04290f55183ff2f0384c6c53756bd8">3</a>]</td> + <td><a href="https://android.googlesource.com/platform/hardware/libhardware/+/8b3d5a64c3c8d010ad4517f652731f09107ae9c5">A-27410683</a> +[<a href="https://android.googlesource.com/platform/system/bt/+/37c88107679d36c419572732b4af6e18bb2f7dce">2</a>] +[<a href="https://android.googlesource.com/platform/packages/apps/Bluetooth/+/122feb9a0b04290f55183ff2f0384c6c53756bd8">3</a>] + </td> <td>ä¸</td> <td><a href="#all_nexus">所有 Nexus 设备</a></td> <td>5.0.2ã€5.1.1ã€6.0ã€6.0.1</td> @@ -777,7 +786,9 @@ Mediaserver ä¸çš„æ‹’ç»æœåŠ¡æ¼æ´ž</h3> </tr> <tr> <td>CVE-2016-3766</td> - <td><a href="https://android.googlesource.com/platform/frameworks/av/+/6fdee2a83432b3b150d6a34f231c4e2f7353c01e">A-28471206</a> [<a href="https://android.googlesource.com/platform/frameworks/av/+/e7142a0703bc93f75e213e96ebc19000022afed9">2</a>]</td> + <td><a href="https://android.googlesource.com/platform/frameworks/av/+/6fdee2a83432b3b150d6a34f231c4e2f7353c01e">A-28471206</a> + [<a href="https://android.googlesource.com/platform/frameworks/av/+/e7142a0703bc93f75e213e96ebc19000022afed9">2</a>] + </td> <td>ä¸</td> <td><a href="#all_nexus">所有 Nexus 设备</a></td> <td>4.4.4ã€5.0.2ã€5.1.1ã€6.0ã€6.0.1</td> @@ -821,7 +832,7 @@ QC-CR988993</a></td> <td>2016 å¹´ 4 月 20 æ—¥</td> </tr> </tbody></table> -<p>*针对该问题的补ä¸ç¨‹åºæœªå…¬å¼€å‘布。<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上æ供的 Nexus 设备的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。</p> +<p>*尚未公开å‘布针对该问题的补ä¸ç¨‹åºã€‚<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上针对 Nexus 设备æ供的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。</p> <h3 id="elevation-of-privilege-vulnerability-in-mediatek-wi-fi-driver"> MediaTek WLAN 驱动程åºä¸çš„ææƒæ¼æ´ž</h3> @@ -848,7 +859,7 @@ MediaTek WLAN 驱动程åºä¸çš„ææƒæ¼æ´ž</h3> <td>2016 å¹´ 4 月 6 æ—¥</td> </tr> </tbody></table> -<p>* 针对该问题的补ä¸ç¨‹åºæœªå…¬å¼€å‘布。<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上æ供的 Nexus 设备的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。</p> +<p>*尚未公开å‘布针对该问题的补ä¸ç¨‹åºã€‚<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上针对 Nexus 设备æ供的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。</p> <h3 id="elevation-of-privilege-vulnerability-in-qualcomm-performance-component">Qualcomm 效能组件ä¸çš„ææƒæ¼æ´ž</h3> <p>Qualcomm 效能组件ä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡å†…æ ¸æ‰§è¡Œä»»æ„代ç 。由于该æ¼æ´žæœ‰å¯èƒ½ä¼šé€ æˆæœ¬åœ°è®¾å¤‡æ°¸ä¹…æŸå，而用户å¯èƒ½éœ€è¦é€šè¿‡é‡å†™æ“作系统æ¥ä¿®å¤è®¾å¤‡ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“严é‡â€ã€‚</p> @@ -874,7 +885,7 @@ MediaTek WLAN 驱动程åºä¸çš„ææƒæ¼æ´ž</h3> <td>2016 å¹´ 4 月 9 æ—¥</td> </tr> </tbody></table> -<p>*针对该问题的补ä¸ç¨‹åºæœªå…¬å¼€å‘布。<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上æ供的 Nexus 设备的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。</p> +<p>*尚未公开å‘布针对该问题的补ä¸ç¨‹åºã€‚<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上针对 Nexus 设备æ供的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。</p> <h3 id="elevation-of-privilege-vulnerability-in-nvidia-video-driver"> NVIDIA 视频驱动程åºä¸çš„ææƒæ¼æ´ž</h3> @@ -901,7 +912,7 @@ NVIDIA 视频驱动程åºä¸çš„ææƒæ¼æ´ž</h3> <td>2016 å¹´ 4 月 18 æ—¥</td> </tr> </tbody></table> -<p>*针对该问题的补ä¸ç¨‹åºæœªå…¬å¼€å‘布。<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上æ供的 Nexus 设备的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。</p> +<p>*尚未公开å‘布针对该问题的补ä¸ç¨‹åºã€‚<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上针对 Nexus 设备æ供的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。</p> <h3 id="elevation-of-privilege-vulnerability-in-mediatek-drivers-device-specific"> MediaTek 驱动程åºä¸çš„ææƒæ¼æ´žï¼ˆä¸Žç‰¹å®šè®¾å¤‡æœ‰å…³ï¼‰</h3> @@ -956,7 +967,7 @@ MediaTek 驱动程åºä¸çš„ææƒæ¼æ´žï¼ˆä¸Žç‰¹å®šè®¾å¤‡æœ‰å…³ï¼‰</h3> <td>2016 å¹´ 4 月 22 æ—¥</td> </tr> </tbody></table> -<p>*针对该问题的补ä¸ç¨‹åºæœªå…¬å¼€å‘布。<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上æ供的 Nexus 设备的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。</p> +<p>*尚未公开å‘布针对该问题的补ä¸ç¨‹åºã€‚<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上针对 Nexus 设备æ供的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。</p> <h3 id="elevation-of-privilege-vulnerability-in-kernel-file-system"> å†…æ ¸æ–‡ä»¶ç³»ç»Ÿä¸çš„ææƒæ¼æ´ž</h3> @@ -983,7 +994,7 @@ MediaTek 驱动程åºä¸çš„ææƒæ¼æ´žï¼ˆä¸Žç‰¹å®šè®¾å¤‡æœ‰å…³ï¼‰</h3> <td>2016 å¹´ 5 月 4 æ—¥</td> </tr> </tbody></table> -<p>* 针对该问题的补ä¸ç¨‹åºæœªå…¬å¼€å‘布。<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上æ供的 Nexus 设备的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。</p> +<p>*尚未公开å‘布针对该问题的补ä¸ç¨‹åºã€‚<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上针对 Nexus 设备æ供的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。</p> <h3 id="elevation-of-privilege-vulnerability-in-usb-driver"> USB 驱动程åºä¸çš„ææƒæ¼æ´ž</h3> @@ -1010,11 +1021,11 @@ USB 驱动程åºä¸çš„ææƒæ¼æ´ž</h3> <td>2016 å¹´ 5 月 4 æ—¥</td> </tr> </tbody></table> -<p>* 针对该问题的补ä¸ç¨‹åºæœªå…¬å¼€å‘布。<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上æ供的 Nexus 设备的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。</p> +<p>*尚未公开å‘布针对该问题的补ä¸ç¨‹åºã€‚<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上针对 Nexus 设备æ供的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。</p> <h3 id="elevation-of-privilege-vulnerability-in-qualcomm-components"> Qualcomm 组件ä¸çš„ææƒæ¼æ´ž</h3> -<p>ä¸‹è¡¨åˆ—å‡ºäº†å½±å“ Qualcomm ç»„ä»¶ï¼ˆåŒ…æ‹¬å¼•å¯¼åŠ è½½ç¨‹åºã€ç›¸æœºé©±åŠ¨ç¨‹åºã€å—符驱动程åºã€ç½‘络ã€å£°éŸ³é©±åŠ¨ç¨‹åºå’Œè§†é¢‘驱动程åºï¼‰çš„安全æ¼æ´žã€‚</p> +<p>下表ä¸åˆ—å‡ºäº†å½±å“ Qualcomm ç»„ä»¶ï¼ˆåŒ…æ‹¬å¼•å¯¼åŠ è½½ç¨‹åºã€æ‘„åƒå¤´é©±åŠ¨ç¨‹åºã€å—符驱动程åºã€ç½‘络组件ã€å£°éŸ³é©±åŠ¨ç¨‹åºå’Œè§†é¢‘驱动程åºï¼‰çš„安全æ¼æ´žã€‚</p> <p>由于这些问题ä¸å±é™©æ€§æœ€é«˜çš„问题å¯èƒ½ä¼šè®©æœ‰å¿ƒäººå£«æ‰§è¡Œä»»æ„代ç ，进而导致本地设备永久æŸå，且用户å¯èƒ½éœ€è¦é€šè¿‡é‡å†™æ“作系统æ¥ä¿®å¤è®¾å¤‡ï¼Œå› æ¤æˆ‘们将æ¤ç±»é—®é¢˜çš„严é‡ç¨‹åº¦è¯„为“严é‡â€ã€‚</p> <table> @@ -1033,7 +1044,9 @@ Qualcomm 组件ä¸çš„ææƒæ¼æ´ž</h3> <tr> <td>CVE-2014-9795</td> <td>A-28820720<br /> - <a href="https://us.codeaurora.org/cgit/quic/la//kernel/lk/commit/?id=ce2a0ea1f14298abc83729f3a095adab43342342">QC-CR681957</a> [<a href="https://us.codeaurora.org/cgit/quic/la//kernel/lk/commit/?id=fc3b31f81a1c128c2bcc745564a075022cd72a2e">2</a>]</td> + <a href="https://us.codeaurora.org/cgit/quic/la//kernel/lk/commit/?id=ce2a0ea1f14298abc83729f3a095adab43342342">QC-CR681957</a> + [<a href="https://us.codeaurora.org/cgit/quic/la//kernel/lk/commit/?id=fc3b31f81a1c128c2bcc745564a075022cd72a2e">2</a>] + </td> <td>严é‡</td> <td>Nexus 5</td> <td>2014 å¹´ 8 月 8 æ—¥</td> @@ -1124,7 +1137,8 @@ Qualcomm 组件ä¸çš„ææƒæ¼æ´ž</h3> <tr> <td>CVE-2014-9783</td> <td>A-28441831<br /> - <a href="https://us.codeaurora.org/cgit/quic/la/kernel/msm/commit/?id=2b1050b49a9a5f7bb57006648d145e001a3eaa8b">QC-CR511382</a> [<a href="https://us.codeaurora.org/cgit/quic/la/kernel/msm-3.10/commit/?id=a7502f4f801bb95bff73617309835bb7a016cde5">2</a>]</td> + <a href="https://us.codeaurora.org/cgit/quic/la/kernel/msm/commit/?id=2b1050b49a9a5f7bb57006648d145e001a3eaa8b">QC-CR511382</a> + [<a href="https://us.codeaurora.org/cgit/quic/la/kernel/msm-3.10/commit/?id=a7502f4f801bb95bff73617309835bb7a016cde5">2</a>]</td> <td>高</td> <td>Nexus 7 (2013)</td> <td>2014 å¹´ 3 月 31 æ—¥</td> @@ -1172,7 +1186,8 @@ Qualcomm 组件ä¸çš„ææƒæ¼æ´ž</h3> <tr> <td>CVE-2014-9790</td> <td>A-28769136<br /> - <a href="https://us.codeaurora.org/cgit/quic/la/kernel/msm/commit/?h=LA.BF.1.1.3_rb1.12&id=6ed921bda8cbb505e8654dfc1095185b0bccc38e">QC-CR545716</a> [<a href="https://us.codeaurora.org/cgit/quic/la/kernel/msm/commit?h=LA.BF.1.1.3_rb1.12&id=9bc30c0d1832f7dd5b6fa10d5e48a29025176569">2</a>]</td> + <a href="https://us.codeaurora.org/cgit/quic/la/kernel/msm/commit/?h=LA.BF.1.1.3_rb1.12&id=6ed921bda8cbb505e8654dfc1095185b0bccc38e">QC-CR545716</a> + [<a href="https://us.codeaurora.org/cgit/quic/la/kernel/msm/commit?h=LA.BF.1.1.3_rb1.12&id=9bc30c0d1832f7dd5b6fa10d5e48a29025176569">2</a>]</td> <td>高</td> <td>Nexus 5ã€Nexus 7 (2013)</td> <td>2014 å¹´ 4 月 30 æ—¥</td> @@ -1278,7 +1293,7 @@ Qualcomm 组件ä¸çš„ææƒæ¼æ´ž</h3> <h3 id="elevation-of-privilege-vulnerability-in-qualcomm-usb-driver"> Qualcomm USB 驱动程åºä¸çš„ææƒæ¼æ´ž</h3> -<p>Qualcomm USB 驱动程åºä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡å†…æ ¸æ‰§è¡Œä»»æ„代ç 。由于该æ¼æ´žéœ€è¦å…ˆç ´åç‰¹è®¸è¿›ç¨‹ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“高â€ã€‚</p> +<p>Qualcomm USB 驱动程åºä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡å†…æ ¸æ‰§è¡Œä»»æ„代ç 。由于æ¶æ„应用在利用该æ¼æ´žæ—¶éœ€è¦å…ˆç ´å特æƒè¿›ç¨‹ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“高â€ã€‚</p> <table> <colgroup><col width="19%" /> @@ -1305,7 +1320,7 @@ Qualcomm USB 驱动程åºä¸çš„ææƒæ¼æ´ž</h3> <h3 id="elevation-of-privilege-vulnerability-in-qualcomm-wi-fi-driver"> Qualcomm WLAN 驱动程åºä¸çš„ææƒæ¼æ´ž</h3> -<p>Qualcomm WLAN 驱动程åºä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡å†…æ ¸æ‰§è¡Œä»»æ„代ç 。由于该æ¼æ´žéœ€è¦å…ˆç ´åç‰¹è®¸è¿›ç¨‹ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“高â€ã€‚</p> +<p>Qualcomm WLAN 驱动程åºä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡å†…æ ¸æ‰§è¡Œä»»æ„代ç 。由于æ¶æ„应用在利用该æ¼æ´žæ—¶éœ€è¦å…ˆç ´å特æƒè¿›ç¨‹ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“高â€ã€‚</p> <table> <colgroup><col width="19%" /> @@ -1331,8 +1346,8 @@ Qualcomm WLAN 驱动程åºä¸çš„ææƒæ¼æ´ž</h3> </tbody></table> <h3 id="elevation-of-privilege-vulnerability-in-qualcomm-camera-driver"> -Qualcomm 相机驱动程åºä¸çš„ææƒæ¼æ´ž</h3> -<p>Qualcomm 相机驱动程åºä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡å†…æ ¸æ‰§è¡Œä»»æ„代ç 。由于该æ¼æ´žéœ€è¦å…ˆç ´åç‰¹è®¸è¿›ç¨‹ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“高â€ã€‚</p> +Qualcomm æ‘„åƒå¤´é©±åŠ¨ç¨‹åºä¸çš„ææƒæ¼æ´ž</h3> +<p>Qualcomm æ‘„åƒå¤´é©±åŠ¨ç¨‹åºä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡å†…æ ¸æ‰§è¡Œä»»æ„代ç 。由于æ¶æ„应用在利用该æ¼æ´žæ—¶éœ€è¦å…ˆç ´å特æƒè¿›ç¨‹ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“高â€ã€‚</p> <table> <colgroup><col width="19%" /> @@ -1356,11 +1371,11 @@ QC-CR1001092</td> <td>2016 å¹´ 3 月 27 æ—¥</td> </tr> </tbody></table> -<p>* 针对该问题的补ä¸ç¨‹åºæœªå…¬å¼€å‘布。<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上æ供的 Nexus 设备的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。</p> +<p>*尚未公开å‘布针对该问题的补ä¸ç¨‹åºã€‚<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上针对 Nexus 设备æ供的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。</p> <h3 id="elevation-of-privilege-vulnerability-in-nvidia-camera-driver"> -NVIDIA 相机驱动程åºä¸çš„ææƒæ¼æ´ž</h3> -<p>NVIDIA 相机驱动程åºä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡å†…æ ¸æ‰§è¡Œä»»æ„代ç 。由于该æ¼æ´žéœ€è¦å…ˆç ´åç‰¹è®¸è¿›ç¨‹ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“高â€ã€‚</p> +NVIDIA æ‘„åƒå¤´é©±åŠ¨ç¨‹åºä¸çš„ææƒæ¼æ´ž</h3> +<p>NVIDIA æ‘„åƒå¤´é©±åŠ¨ç¨‹åºä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡å†…æ ¸æ‰§è¡Œä»»æ„代ç 。由于æ¶æ„应用在利用该æ¼æ´žæ—¶éœ€è¦å…ˆç ´å特æƒè¿›ç¨‹ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“高â€ã€‚</p> <table> <colgroup><col width="19%" /> @@ -1383,11 +1398,11 @@ NVIDIA 相机驱动程åºä¸çš„ææƒæ¼æ´ž</h3> <td>2016 å¹´ 4 月 5 æ—¥</td> </tr> </tbody></table> -<p>* 针对该问题的补ä¸ç¨‹åºæœªå…¬å¼€å‘布。<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上æ供的 Nexus 设备的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。</p> +<p>*尚未公开å‘布针对该问题的补ä¸ç¨‹åºã€‚<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上针对 Nexus 设备æ供的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。</p> <h3 id="elevation-of-privilege-vulnerability-in-mediatek-power-driver"> MediaTek 电æºé©±åŠ¨ç¨‹åºä¸çš„ææƒæ¼æ´ž</h3> -<p>MediaTek 电æºé©±åŠ¨ç¨‹åºä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡å†…æ ¸æ‰§è¡Œä»»æ„代ç 。由于该æ¼æ´žéœ€è¦å…ˆç ´åç‰¹è®¸è¿›ç¨‹ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“高â€ã€‚</p> +<p>MediaTek 电æºé©±åŠ¨ç¨‹åºä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡å†…æ ¸æ‰§è¡Œä»»æ„代ç 。由于æ¶æ„应用在利用该æ¼æ´žæ—¶éœ€è¦å…ˆç ´å特æƒè¿›ç¨‹ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“高â€ã€‚</p> <table> <colgroup><col width="19%" /> @@ -1417,11 +1432,11 @@ MediaTek 电æºé©±åŠ¨ç¨‹åºä¸çš„ææƒæ¼æ´ž</h3> <td>2016 å¹´ 4 月 7 æ—¥</td> </tr> </tbody></table> -<p>* 针对该问题的补ä¸ç¨‹åºæœªå…¬å¼€å‘布。<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上æ供的 Nexus 设备的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。</p> +<p>*尚未公开å‘布针对该问题的补ä¸ç¨‹åºã€‚<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上针对 Nexus 设备æ供的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。</p> <h3 id="elevation-of-privilege-vulnerability-in-qualcomm-wi-fi-driver-2"> Qualcomm WLAN 驱动程åºä¸çš„ææƒæ¼æ´ž</h3> -<p>Qualcomm WLAN 驱动程åºä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡å†…æ ¸æ‰§è¡Œä»»æ„代ç 。由于该æ¼æ´žéœ€è¦å…ˆç ´åç‰¹è®¸è¿›ç¨‹ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“高â€ã€‚</p> +<p>Qualcomm WLAN 驱动程åºä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡å†…æ ¸æ‰§è¡Œä»»æ„代ç 。由于æ¶æ„应用在利用该æ¼æ´žæ—¶éœ€è¦å…ˆç ´å特æƒè¿›ç¨‹ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“高â€ã€‚</p> <table> <colgroup><col width="19%" /> @@ -1439,17 +1454,17 @@ Qualcomm WLAN 驱动程åºä¸çš„ææƒæ¼æ´ž</h3> <tr> <td>CVE-2016-3797</td> <td>A-28085680* - QC-CR1001450</td> +QC-CR1001450</td> <td>高</td> <td>Nexus 5X</td> <td>2016 å¹´ 4 月 7 æ—¥</td> </tr> </tbody></table> -<p>* 针对该问题的补ä¸ç¨‹åºæœªå…¬å¼€å‘布。<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上æ供的 Nexus 设备的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。</p> +<p>*尚未公开å‘布针对该问题的补ä¸ç¨‹åºã€‚<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上针对 Nexus 设备æ供的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。</p> <h3 id="elevation-of-privilege-vulnerability-in-mediatek-hardware-sensor-driver"> MediaTek ç¡¬ä»¶ä¼ æ„Ÿå™¨é©±åŠ¨ç¨‹åºä¸çš„ææƒæ¼æ´ž</h3> -<p>MediaTek ç¡¬ä»¶ä¼ æ„Ÿå™¨é©±åŠ¨ç¨‹åºä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡å†…æ ¸æ‰§è¡Œä»»æ„代ç 。由于该æ¼æ´žéœ€è¦å…ˆç ´åç‰¹è®¸è¿›ç¨‹ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“高â€ã€‚</p> +<p>MediaTek ç¡¬ä»¶ä¼ æ„Ÿå™¨é©±åŠ¨ç¨‹åºä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡å†…æ ¸æ‰§è¡Œä»»æ„代ç 。由于æ¶æ„应用在利用该æ¼æ´žæ—¶éœ€è¦å…ˆç ´å特æƒè¿›ç¨‹ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“高â€ã€‚</p> <table> <colgroup><col width="19%" /> @@ -1472,11 +1487,11 @@ MediaTek ç¡¬ä»¶ä¼ æ„Ÿå™¨é©±åŠ¨ç¨‹åºä¸çš„ææƒæ¼æ´ž</h3> <td>2016 å¹´ 4 月 11 æ—¥</td> </tr> </tbody></table> -<p>* 针对该问题的补ä¸ç¨‹åºæœªå…¬å¼€å‘布。<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上æ供的 Nexus 设备的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。</p> +<p>*尚未公开å‘布针对该问题的补ä¸ç¨‹åºã€‚<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上针对 Nexus 设备æ供的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。</p> <h3 id="elevation-of-privilege-vulnerability-in-mediatek-video-driver"> MediaTek 视频驱动程åºä¸çš„ææƒæ¼æ´ž</h3> -<p>MediaTek 视频驱动程åºä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡å†…æ ¸æ‰§è¡Œä»»æ„代ç 。由于该æ¼æ´žéœ€è¦å…ˆç ´åç‰¹è®¸è¿›ç¨‹ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“高â€ã€‚</p> +<p>MediaTek 视频驱动程åºä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡å†…æ ¸æ‰§è¡Œä»»æ„代ç 。由于æ¶æ„应用在利用该æ¼æ´žæ—¶éœ€è¦å…ˆç ´å特æƒè¿›ç¨‹ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“高â€ã€‚</p> <table> <colgroup><col width="19%" /> @@ -1506,11 +1521,11 @@ MediaTek 视频驱动程åºä¸çš„ææƒæ¼æ´ž</h3> <td>2016 å¹´ 4 月 11 æ—¥</td> </tr> </tbody></table> -<p>* 针对该问题的补ä¸ç¨‹åºæœªå…¬å¼€å‘布。<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上æ供的 Nexus 设备的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。</p> +<p>*尚未公开å‘布针对该问题的补ä¸ç¨‹åºã€‚<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上针对 Nexus 设备æ供的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。</p> <h3 id="elevation-of-privilege-vulnerability-in-mediatek-gps-driver"> MediaTek GPS 驱动程åºä¸çš„ææƒæ¼æ´ž</h3> -<p>MediaTek GPS 驱动程åºä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡å†…æ ¸æ‰§è¡Œä»»æ„代ç 。由于该æ¼æ´žéœ€è¦å…ˆç ´åç‰¹è®¸è¿›ç¨‹ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“高â€ã€‚</p> +<p>MediaTek GPS 驱动程åºä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡å†…æ ¸æ‰§è¡Œä»»æ„代ç 。由于æ¶æ„应用在利用该æ¼æ´žæ—¶éœ€è¦å…ˆç ´å特æƒè¿›ç¨‹ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“高â€ã€‚</p> <table> <colgroup><col width="19%" /> @@ -1533,11 +1548,11 @@ MediaTek GPS 驱动程åºä¸çš„ææƒæ¼æ´ž</h3> <td>2016 å¹´ 4 月 11 æ—¥</td> </tr> </tbody></table> -<p>* 针对该问题的补ä¸ç¨‹åºæœªå…¬å¼€å‘布。<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上æ供的 Nexus 设备的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。</p> +<p>*尚未公开å‘布针对该问题的补ä¸ç¨‹åºã€‚<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上针对 Nexus 设备æ供的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。</p> <h3 id="elevation-of-privilege-vulnerability-in-kernel-file-system-2"> å†…æ ¸æ–‡ä»¶ç³»ç»Ÿä¸çš„ææƒæ¼æ´ž</h3> -<p>å†…æ ¸æ–‡ä»¶ç³»ç»Ÿä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡å†…æ ¸æ‰§è¡Œä»»æ„代ç 。由于该æ¼æ´žéœ€è¦å…ˆç ´åç‰¹è®¸è¿›ç¨‹ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“高â€ã€‚</p> +<p>å†…æ ¸æ–‡ä»¶ç³»ç»Ÿä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡å†…æ ¸æ‰§è¡Œä»»æ„代ç 。由于æ¶æ„应用在利用该æ¼æ´žæ—¶éœ€è¦å…ˆç ´å特æƒè¿›ç¨‹ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“高â€ã€‚</p> <table> <colgroup><col width="19%" /> @@ -1567,11 +1582,11 @@ MediaTek GPS 驱动程åºä¸çš„ææƒæ¼æ´ž</h3> <td>2016 å¹´ 5 月 4 æ—¥</td> </tr> </tbody></table> -<p>* 针对该问题的补ä¸ç¨‹åºæœªå…¬å¼€å‘布。<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上æ供的 Nexus 设备的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。</p> +<p>*尚未公开å‘布针对该问题的补ä¸ç¨‹åºã€‚<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上针对 Nexus 设备æ供的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。</p> <h3 id="elevation-of-privilege-vulnerability-in-mediatek-power-management-driver"> MediaTek 电æºç®¡ç†é©±åŠ¨ç¨‹åºä¸çš„ææƒæ¼æ´ž</h3> -<p>MediaTek 电æºç®¡ç†é©±åŠ¨ç¨‹åºä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡å†…æ ¸æ‰§è¡Œä»»æ„代ç 。由于该æ¼æ´žéœ€è¦å…ˆç ´åç‰¹è®¸è¿›ç¨‹ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“高â€ã€‚</p> +<p>MediaTek 电æºç®¡ç†é©±åŠ¨ç¨‹åºä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡å†…æ ¸æ‰§è¡Œä»»æ„代ç 。由于æ¶æ„应用在利用该æ¼æ´žæ—¶éœ€è¦å…ˆç ´å特æƒè¿›ç¨‹ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“高â€ã€‚</p> <table> <colgroup><col width="19%" /> @@ -1601,11 +1616,11 @@ MediaTek 电æºç®¡ç†é©±åŠ¨ç¨‹åºä¸çš„ææƒæ¼æ´ž</h3> <td>2016 å¹´ 4 月 21 æ—¥</td> </tr> </tbody></table> -<p>* 针对该问题的补ä¸ç¨‹åºæœªå…¬å¼€å‘布。<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上æ供的 Nexus 设备的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。</p> +<p>*尚未公开å‘布针对该问题的补ä¸ç¨‹åºã€‚<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上针对 Nexus 设备æ供的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。</p> <h3 id="elevation-of-privilege-vulnerability-in-mediatek-display-driver"> MediaTek 显å¡é©±åŠ¨ç¨‹åºä¸çš„ææƒæ¼æ´ž</h3> -<p>MediaTek 显å¡é©±åŠ¨ç¨‹åºä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡å†…æ ¸æ‰§è¡Œä»»æ„代ç 。由于该æ¼æ´žéœ€è¦å…ˆç ´åç‰¹è®¸è¿›ç¨‹ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“高â€ã€‚</p> +<p>MediaTek 显å¡é©±åŠ¨ç¨‹åºä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡å†…æ ¸æ‰§è¡Œä»»æ„代ç 。由于æ¶æ„应用在利用该æ¼æ´žæ—¶éœ€è¦å…ˆç ´å特æƒè¿›ç¨‹ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“高â€ã€‚</p> <table> <colgroup><col width="19%" /> @@ -1628,11 +1643,11 @@ MediaTek 显å¡é©±åŠ¨ç¨‹åºä¸çš„ææƒæ¼æ´ž</h3> <td>2016 å¹´ 4 月 26 æ—¥</td> </tr> </tbody></table> -<p>* 针对该问题的补ä¸ç¨‹åºæœªå…¬å¼€å‘布。<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上æ供的 Nexus 设备的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。</p> +<p>*尚未公开å‘布针对该问题的补ä¸ç¨‹åºã€‚<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上针对 Nexus 设备æ供的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。</p> <h3 id="elevation-of-privilege-vulnerability-in-serial-peripheral-interface-driver"> 串行外设接å£é©±åŠ¨ç¨‹åºä¸çš„ææƒæ¼æ´ž</h3> -<p>串行外设接å£é©±åŠ¨ç¨‹åºä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡å†…æ ¸æ‰§è¡Œä»»æ„代ç 。由于该æ¼æ´žéœ€è¦å…ˆç ´åç‰¹è®¸è¿›ç¨‹ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“高â€ã€‚</p> +<p>串行外设接å£é©±åŠ¨ç¨‹åºä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡å†…æ ¸æ‰§è¡Œä»»æ„代ç 。由于æ¶æ„应用在利用该æ¼æ´žæ—¶éœ€è¦å…ˆç ´å特æƒè¿›ç¨‹ï¼Œå› æ¤æˆ‘们其严é‡ç¨‹åº¦è¯„为“高â€ã€‚</p> <table> <colgroup><col width="19%" /> @@ -1662,11 +1677,11 @@ MediaTek 显å¡é©±åŠ¨ç¨‹åºä¸çš„ææƒæ¼æ´ž</h3> <td>2016 å¹´ 4 月 26 æ—¥</td> </tr> </tbody></table> -<p>* 针对该问题的补ä¸ç¨‹åºæœªå…¬å¼€å‘布。<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上æ供的 Nexus 设备的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。</p> +<p>*尚未公开å‘布针对该问题的补ä¸ç¨‹åºã€‚<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上针对 Nexus 设备æ供的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。</p> <h3 id="elevation-of-privilege-vulnerability-in-qualcomm-sound-driver"> Qualcomm 声音驱动程åºä¸çš„ææƒæ¼æ´ž</h3> -<p>Qualcomm 声音驱动程åºä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡å†…æ ¸æ‰§è¡Œä»»æ„代ç 。由于该æ¼æ´žéœ€è¦å…ˆç ´åç‰¹è®¸è¿›ç¨‹ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“高â€ã€‚</p> +<p>Qualcomm 声音驱动程åºä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡å†…æ ¸æ‰§è¡Œä»»æ„代ç 。由于æ¶æ„应用在利用该æ¼æ´žæ—¶éœ€è¦å…ˆç ´å特æƒè¿›ç¨‹ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“高â€ã€‚</p> <table> <colgroup><col width="19%" /> @@ -1693,7 +1708,7 @@ Qualcomm 声音驱动程åºä¸çš„ææƒæ¼æ´ž</h3> <h3 id="elevation-of-privilege-vulnerability-in-kernel"> å†…æ ¸ä¸çš„ææƒæ¼æ´ž</h3> -<p>å†…æ ¸ä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡å†…æ ¸æ‰§è¡Œä»»æ„代ç 。由于该æ¼æ´žéœ€è¦å…ˆç ´åç‰¹è®¸è¿›ç¨‹ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“高â€ã€‚</p> +<p>å†…æ ¸ä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡å†…æ ¸æ‰§è¡Œä»»æ„代ç 。由于æ¶æ„应用在利用该æ¼æ´žæ—¶éœ€è¦å…ˆç ´å特æƒè¿›ç¨‹ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“高â€ã€‚</p> <table> <colgroup><col width="19%" /> @@ -1743,7 +1758,7 @@ Qualcomm 声音驱动程åºä¸çš„ææƒæ¼æ´ž</h3> <td>2016 å¹´ 3 月 5 æ—¥</td> </tr> </tbody></table> -<p>* 针对该问题的补ä¸ç¨‹åºæœªå…¬å¼€å‘布。<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上æ供的 Nexus 设备的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。</p> +<p>*尚未公开å‘布针对该问题的补ä¸ç¨‹åºã€‚<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上针对 Nexus 设备æ供的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。</p> <h3 id="information-disclosure-vulnerability-in-mediatek-wi-fi-driver"> MediaTek WLAN 驱动程åºä¸çš„ä¿¡æ¯æŠ«éœ²æ¼æ´ž</h3> @@ -1770,11 +1785,11 @@ MediaTek WLAN 驱动程åºä¸çš„ä¿¡æ¯æŠ«éœ²æ¼æ´ž</h3> <td>2016 å¹´ 4 月 12 æ—¥</td> </tr> </tbody></table> -<p>* 针对该问题的补ä¸ç¨‹åºæœªå…¬å¼€å‘布。<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上æ供的 Nexus 设备的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。</p> +<p>*尚未公开å‘布针对该问题的补ä¸ç¨‹åºã€‚<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上针对 Nexus 设备æ供的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。</p> <h3 id="elevation-of-privilege-vulnerability-in-kernel-video-driver"> å†…æ ¸è§†é¢‘é©±åŠ¨ç¨‹åºä¸çš„ææƒæ¼æ´ž</h3> -<p>å†…æ ¸è§†é¢‘é©±åŠ¨ç¨‹åºä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡å†…æ ¸æ‰§è¡Œä»»æ„代ç 。由于该æ¼æ´žéœ€è¦å…ˆç ´åç‰¹è®¸è¿›ç¨‹ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“ä¸â€ã€‚</p> +<p>å†…æ ¸è§†é¢‘é©±åŠ¨ç¨‹åºä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡å†…æ ¸æ‰§è¡Œä»»æ„代ç 。由于æ¶æ„应用在利用该æ¼æ´žæ—¶éœ€è¦å…ˆç ´å特æƒè¿›ç¨‹ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“ä¸â€ã€‚</p> <table> <colgroup><col width="19%" /> @@ -1797,11 +1812,11 @@ MediaTek WLAN 驱动程åºä¸çš„ä¿¡æ¯æŠ«éœ²æ¼æ´ž</h3> <td>Google 内部</td> </tr> </tbody></table> -<p>* 针对该问题的补ä¸ç¨‹åºæœªå…¬å¼€å‘布。<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上æ供的 Nexus 设备的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。</p> +<p>*尚未公开å‘布针对该问题的补ä¸ç¨‹åºã€‚<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上针对 Nexus 设备æ供的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。</p> <h3 id="information-disclosure-vulnerability-in-mediatek-video-codec-driver"> MediaTek 视频编解ç 器驱动程åºä¸çš„ä¿¡æ¯æŠ«éœ²æ¼æ´ž</h3> -<p>MediaTek 视频编解ç 器驱动程åºä¸çš„ä¿¡æ¯æŠ«éœ²æ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用获å–超出其æƒé™èŒƒå›´çš„æ•°æ®ã€‚由于该æ¼æ´žéœ€è¦å…ˆç ´åç‰¹è®¸è¿›ç¨‹ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“ä¸â€ã€‚</p> +<p>MediaTek 视频编解ç 器驱动程åºä¸çš„ä¿¡æ¯æŠ«éœ²æ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用获å–超出其æƒé™èŒƒå›´çš„æ•°æ®ã€‚由于æ¶æ„应用在利用该æ¼æ´žæ—¶éœ€è¦å…ˆç ´å特æƒè¿›ç¨‹ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“ä¸â€ã€‚</p> <table> <colgroup><col width="19%" /> @@ -1824,11 +1839,11 @@ MediaTek 视频编解ç 器驱动程åºä¸çš„ä¿¡æ¯æŠ«éœ²æ¼æ´ž</h3> <td>2016 å¹´ 4 月 11 æ—¥</td> </tr> </tbody></table> -<p>* 针对该问题的补ä¸ç¨‹åºæœªå…¬å¼€å‘布。<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上æ供的 Nexus 设备的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。</p> +<p>*尚未公开å‘布针对该问题的补ä¸ç¨‹åºã€‚<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上针对 Nexus 设备æ供的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。</p> <h3 id="information-disclosure-vulnerability-in-qualcomm-usb-driver"> Qualcomm USB 驱动程åºä¸çš„ä¿¡æ¯æŠ«éœ²æ¼æ´ž</h3> -<p>Qualcomm USB 驱动程åºä¸çš„ä¿¡æ¯æŠ«éœ²æ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用获å–超出其æƒé™èŒƒå›´çš„æ•°æ®ã€‚由于该æ¼æ´žéœ€è¦å…ˆç ´åç‰¹è®¸è¿›ç¨‹ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“ä¸â€ã€‚</p> +<p>Qualcomm USB 驱动程åºä¸çš„ä¿¡æ¯æŠ«éœ²æ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用获å–超出其æƒé™èŒƒå›´çš„æ•°æ®ã€‚由于æ¶æ„应用在利用该æ¼æ´žæ—¶éœ€è¦å…ˆç ´å特æƒè¿›ç¨‹ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“ä¸â€ã€‚</p> <table> <colgroup><col width="19%" /> @@ -1852,11 +1867,11 @@ QC-CR1010222</td> <td>2016 å¹´ 4 月 11 æ—¥</td> </tr> </tbody></table> -<p>* 针对该问题的补ä¸ç¨‹åºæœªå…¬å¼€å‘布。<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上æ供的 Nexus 设备的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。</p> +<p>*尚未公开å‘布针对该问题的补ä¸ç¨‹åºã€‚<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上针对 Nexus 设备æ供的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。</p> <h3 id="information-disclosure-vulnerability-in-nvidia-camera-driver"> -NVIDIA 相机驱动程åºä¸çš„ä¿¡æ¯æŠ«éœ²æ¼æ´ž</h3> -<p>NVIDIA 相机驱动程åºä¸çš„ä¿¡æ¯æŠ«éœ²æ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用获å–超出其æƒé™èŒƒå›´çš„æ•°æ®ã€‚由于该æ¼æ´žéœ€è¦å…ˆç ´åç‰¹è®¸è¿›ç¨‹ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“ä¸â€ã€‚</p> +NVIDIA æ‘„åƒå¤´é©±åŠ¨ç¨‹åºä¸çš„ä¿¡æ¯æŠ«éœ²æ¼æ´ž</h3> +<p>NVIDIA æ‘„åƒå¤´é©±åŠ¨ç¨‹åºä¸çš„ä¿¡æ¯æŠ«éœ²æ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用获å–超出其æƒé™èŒƒå›´çš„æ•°æ®ã€‚由于æ¶æ„应用在利用该æ¼æ´žæ—¶éœ€è¦å…ˆç ´å特æƒè¿›ç¨‹ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“ä¸â€ã€‚</p> <table> <colgroup><col width="19%" /> @@ -1886,11 +1901,11 @@ NVIDIA 相机驱动程åºä¸çš„ä¿¡æ¯æŠ«éœ²æ¼æ´ž</h3> <td>2016 å¹´ 5 月 1 æ—¥</td> </tr> </tbody></table> -<p>* 针对该问题的补ä¸ç¨‹åºæœªå…¬å¼€å‘布。<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上æ供的 Nexus 设备的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。</p> +<p>*尚未公开å‘布针对该问题的补ä¸ç¨‹åºã€‚<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上针对 Nexus 设备æ供的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。</p> <h3 id="information-disclosure-vulnerability-in-mediatek-display-driver"> MediaTek 显å¡é©±åŠ¨ç¨‹åºä¸çš„ä¿¡æ¯æŠ«éœ²æ¼æ´ž</h3> -<p>MediaTek 显å¡é©±åŠ¨ç¨‹åºä¸çš„ä¿¡æ¯æŠ«éœ²æ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用获å–超出其æƒé™èŒƒå›´çš„æ•°æ®ã€‚由于该æ¼æ´žéœ€è¦å…ˆç ´åç‰¹è®¸è¿›ç¨‹ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“ä¸â€ã€‚</p> +<p>MediaTek 显å¡é©±åŠ¨ç¨‹åºä¸çš„ä¿¡æ¯æŠ«éœ²æ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用获å–超出其æƒé™èŒƒå›´çš„æ•°æ®ã€‚由于æ¶æ„应用在利用该æ¼æ´žæ—¶éœ€è¦å…ˆç ´å特æƒè¿›ç¨‹ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“ä¸â€ã€‚</p> <table> <colgroup><col width="19%" /> @@ -1913,11 +1928,11 @@ MediaTek 显å¡é©±åŠ¨ç¨‹åºä¸çš„ä¿¡æ¯æŠ«éœ²æ¼æ´ž</h3> <td>2016 å¹´ 4 月 26 æ—¥</td> </tr> </tbody></table> -<p>* 针对该问题的补ä¸ç¨‹åºæœªå…¬å¼€å‘布。<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上æ供的 Nexus 设备的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。</p> +<p>*尚未公开å‘布针对该问题的补ä¸ç¨‹åºã€‚<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上针对 Nexus 设备æ供的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。</p> <h3 id="information-disclosure-vulnerability-in-kernel-teletype-driver"> å†…æ ¸ç”µä¼ é©±åŠ¨ç¨‹åºä¸çš„ä¿¡æ¯æŠ«éœ²æ¼æ´ž</h3> -<p>ç”µä¼ é©±åŠ¨ç¨‹åºä¸çš„ä¿¡æ¯æŠ«éœ²æ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用获å–超出其æƒé™èŒƒå›´çš„æ•°æ®ã€‚由于该æ¼æ´žéœ€è¦å…ˆç ´åç‰¹è®¸è¿›ç¨‹ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“ä¸â€ã€‚</p> +<p>ç”µä¼ é©±åŠ¨ç¨‹åºä¸çš„ä¿¡æ¯æŠ«éœ²æ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用获å–超出其æƒé™èŒƒå›´çš„æ•°æ®ã€‚由于æ¶æ„应用在利用该æ¼æ´žæ—¶éœ€è¦å…ˆç ´å特æƒè¿›ç¨‹ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“ä¸â€ã€‚</p> <table> <colgroup><col width="19%" /> @@ -1944,7 +1959,7 @@ MediaTek 显å¡é©±åŠ¨ç¨‹åºä¸çš„ä¿¡æ¯æŠ«éœ²æ¼æ´ž</h3> <h3 id="denial-of-service-vulnerability-in-qualcomm-bootloader"> Qualcomm å¼•å¯¼åŠ è½½ç¨‹åºä¸çš„æ‹’ç»æœåŠ¡æ¼æ´ž</h3> -<p>Qualcomm å¼•å¯¼åŠ è½½ç¨‹åºä¸çš„æ‹’ç»æœåŠ¡æ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€ æˆæœ¬åœ°è®¾å¤‡æ°¸ä¹…æŸå，而用户å¯èƒ½éœ€è¦é€šè¿‡é‡å†™æ“作系统æ¥ä¿®å¤è®¾å¤‡ã€‚由于该æ¼æ´žéœ€è¦å…ˆç ´åç‰¹è®¸è¿›ç¨‹ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“ä¸â€ã€‚</p> +<p>Qualcomm å¼•å¯¼åŠ è½½ç¨‹åºä¸çš„æ‹’ç»æœåŠ¡æ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€ æˆæœ¬åœ°è®¾å¤‡æ°¸ä¹…æŸå，而用户å¯èƒ½éœ€è¦é€šè¿‡é‡å†™æ“作系统æ¥ä¿®å¤è®¾å¤‡ã€‚由于æ¶æ„应用在利用该æ¼æ´žæ—¶éœ€è¦å…ˆç ´å特æƒè¿›ç¨‹ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“ä¸â€ã€‚</p> <table> <colgroup><col width="19%" /> @@ -1990,9 +2005,9 @@ Qualcomm å¼•å¯¼åŠ è½½ç¨‹åºä¸çš„æ‹’ç»æœåŠ¡æ¼æ´ž</h3> <p id="all_nexus"><strong>3. 如何确定å„个问题都会影å“哪些 Nexus 设备？</strong></p> <p>在 <a href="#2016-07-01-details">2016-07-01</a> å’Œ <a href="#2016-07-05-details">2016-07-05</a> 安全æ¼æ´žè¯¦æƒ…部分，æ¯ä¸ªè¡¨ä¸å‡åŒ…å«â€œå·²æ›´æ–°çš„ Nexus 设备â€åˆ—，其ä¸åˆ—出了已针对æ¯ä¸ªé—®é¢˜è¿›è¡Œæ›´æ–°çš„å—å½±å“ Nexus 设备。æ¤åˆ—æœ‰ä»¥ä¸‹å‡ ç§æƒ…形：</p> <ul> - <li><strong>所有 Nexus 设备</strong>：如果æŸä¸ªé—®é¢˜ä¼šå½±å“所有 Nexus 设备，则相应表的“已更新的 Nexus 设备â€åˆ—ä¸ä¼šæ˜¾ç¤ºâ€œæ‰€æœ‰ Nexus 设备â€ã€‚<em></em>“所有 Nexus 设备â€åŒ…å«ä¸‹åˆ—<a href="https://support.google.com/nexus/answer/4457705#nexus_devices">å—支æŒçš„设备</a>：Nexus 5ã€Nexus 5Xã€Nexus 6ã€Nexus 6Pã€Nexus 7 (2013)ã€Nexus 9ã€Android Oneã€Nexus Player å’Œ Pixel C。</li> - <li><strong>部分 Nexus 设备</strong>：如果æŸä¸ªé—®é¢˜ä»…会影å“部分 Nexus 设备，则“已更新的 Nexus 设备â€åˆ—ä¸ä¼šåˆ—出å—å½±å“çš„ Nexus 设备。<em></em></li> - <li><strong>æ— Nexus 设备</strong>：如果æŸä¸ªé—®é¢˜ä¸ä¼šå½±å“任何 Nexus 设备，则相应表的“已更新的 Nexus 设备â€åˆ—ä¸ä¼šæ˜¾ç¤ºâ€œæ— â€ã€‚<em></em></li> + <li><strong>所有 Nexus 设备</strong>：如果问题会影å“所有 Nexus 设备，则相应表的“已更新的 Nexus 设备â€åˆ—ä¸ä¼šæ˜¾ç¤ºâ€œæ‰€æœ‰ Nexus 设备â€ã€‚<em></em>“所有 Nexus 设备â€åŒ…å«ä¸‹åˆ—<a href="https://support.google.com/nexus/answer/4457705#nexus_devices">å—支æŒçš„设备</a>：Nexus 5ã€Nexus 5Xã€Nexus 6ã€Nexus 6Pã€Nexus 7 (2013)ã€Nexus 9ã€Android Oneã€Nexus Player å’Œ Pixel C。</li> + <li><strong>部分 Nexus 设备</strong>：如果问题仅会影å“部分 Nexus 设备，则“已更新的 Nexus 设备â€åˆ—ä¸ä¼šåˆ—出å—å½±å“çš„ Nexus 设备。<em></em></li> + <li><strong>æ— Nexus 设备</strong>：如果问题ä¸ä¼šå½±å“任何 Nexus 设备，则相应表的“已更新的 Nexus 设备â€åˆ—ä¸ä¼šæ˜¾ç¤ºâ€œæ— â€ã€‚<em></em></li> </ul> <p><strong>4.“å‚考信æ¯â€åˆ—ä¸çš„æ¡ç›®å¯¹åº”的是什么内容？</strong></p> diff --git a/zh-cn/security/bulletin/2016-12-01.html b/zh-cn/security/bulletin/2016-12-01.html index 0b165b35..3ca21240 100644 --- a/zh-cn/security/bulletin/2016-12-01.html +++ b/zh-cn/security/bulletin/2016-12-01.html @@ -93,7 +93,7 @@ Android 安全公告详细介ç»äº†ä¼šå½±å“ Android 设备的安全æ¼æ´žã€‚除 <li>奇虎 360 科技有é™å…¬å¸æˆéƒ½å®‰å…¨å“应ä¸å¿ƒçš„ <a href="http://weibo.com/ele7enxxh">Zinuo Han</a>：CVE-2016-6762</li> </ul> <p> -æ¤å¤–，还è¦è¡·å¿ƒæ„Ÿè°¢ç“¶å科技的 MengLuo Gou (<a href="https://twitter.com/idhyt3r">@idhyt3r</a>)ã€Google 的王勇 (<a href="https://twitter.com/ThomasKing2014">@ThomasKing2014</a>) å’Œ Zubin Mithra 为本安全公告åšå‡ºçš„贡献。 +æ¤å¤–，还è¦è¡·å¿ƒæ„Ÿè°¢ç“¶å科技的 MengLuo Gou (<a href="https://twitter.com/idhyt3r">@idhyt3r</a>) ä»¥åŠ Google 的王勇 (<a href="https://twitter.com/ThomasKing2014">@ThomasKing2014</a>) å’Œ Zubin Mithra 为本安全公告åšå‡ºçš„贡献。 </p> <h2 id="2016-12-01-details">2016-12-01 安全补ä¸ç¨‹åºçº§åˆ« - æ¼æ´žè¯¦æƒ…</h2> @@ -101,7 +101,7 @@ Android 安全公告详细介ç»äº†ä¼šå½±å“ Android 设备的安全æ¼æ´žã€‚除 <h3 id="rce-in-curl-libcurl">CURL/LIBCURL ä¸çš„远程代ç 执行æ¼æ´ž</h3> <p> -ä¸‹è¡¨åˆ—å‡ºäº†å½±å“ CURL å’Œ LIBCURL 库的安全æ¼æ´žã€‚å…¶ä¸æœ€ä¸¥é‡çš„问题å¯è®©ä¸é—´äººæ”»å‡»è€…ä½¿ç”¨ä¼ªé€ çš„è¯ä¹¦é€šè¿‡ç‰¹è®¸è¿›ç¨‹æ‰§è¡Œä»»æ„代ç 。由于攻击者需è¦ä¼ªé€ çš„è¯ä¹¦ï¼Œå› æ¤æˆ‘们将该æ¼æ´žçš„严é‡ç¨‹åº¦è¯„为“高â€ã€‚ +下表ä¸åˆ—å‡ºäº†å½±å“ CURL å’Œ LIBCURL 库的安全æ¼æ´žã€‚å…¶ä¸æœ€ä¸¥é‡çš„问题å¯è®©ä¸é—´äººæ”»å‡»è€…ä½¿ç”¨ä¼ªé€ çš„è¯ä¹¦é€šè¿‡ç‰¹è®¸è¿›ç¨‹æ‰§è¡Œä»»æ„代ç 。由于攻击者需è¦ä¼ªé€ çš„è¯ä¹¦ï¼Œå› æ¤æˆ‘们将该æ¼æ´žçš„严é‡ç¨‹åº¦è¯„为“高â€ã€‚ </p> <table> @@ -147,7 +147,7 @@ Android 安全公告详细介ç»äº†ä¼šå½±å“ Android 设备的安全æ¼æ´žã€‚除 <h3 id="eop-in-libziparchive">libziparchive ä¸çš„ææƒæ¼æ´ž</h3> <p> -libziparchive 库ä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用通过特许进程执行任æ„代ç 。由于攻击者å¯ä»¥åˆ©ç”¨è¯¥æ¼æ´žä½¿ç¬¬ä¸‰æ–¹åº”用在本地获å–超出规定的æƒèƒ½ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“高â€ã€‚ +libziparchive 库ä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用通过特许进程执行任æ„代ç 。由于攻击者å¯ä»¥åˆ©ç”¨è¯¥æ¼æ´žä½¿ç¬¬ä¸‰æ–¹åº”用在本地获å–超出规定的æƒèƒ½ï¼Œå› æ¤æˆ‘们将该æ¼æ´žçš„严é‡ç¨‹åº¦è¯„为“高â€ã€‚ </p> <table> @@ -167,7 +167,9 @@ libziparchive 库ä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用通过特许进程执 </tr> <tr> <td>CVE-2016-6762</td> - <td><a href="https://android.googlesource.com/platform/system/core/+/1ee4892e66ba314131b7ecf17e98bb1762c4b84c">A-31251826</a> [<a href="https://android.googlesource.com/platform/bionic/+/3656958a16590d07d1e25587734e000beb437740">2</a>]</td> + <td><a href="https://android.googlesource.com/platform/system/core/+/1ee4892e66ba314131b7ecf17e98bb1762c4b84c">A-31251826</a> + [<a href="https://android.googlesource.com/platform/bionic/+/3656958a16590d07d1e25587734e000beb437740">2</a>] + </td> <td>高</td> <td>所有</td> <td>5.0.2ã€5.1.1ã€6.0ã€6.0.1ã€7.0</td> @@ -177,7 +179,7 @@ libziparchive 库ä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用通过特许进程执 <h3 id="dos-in-telephony">Telephony ä¸çš„æ‹’ç»æœåŠ¡æ¼æ´ž</h3> <p> -Telephony ä¸çš„æ‹’ç»æœåŠ¡æ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用使用特制文件挂起或é‡å¯è®¾å¤‡ã€‚由于攻击者å¯ä»¥åˆ©ç”¨è¯¥æ¼æ´žåœ¨æœ¬åœ°å‘起永久拒ç»æœåŠ¡æ”»å‡»ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“高â€ã€‚ +Telephony ä¸çš„æ‹’ç»æœåŠ¡æ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用使用特制文件挂起或é‡å¯è®¾å¤‡ã€‚由于攻击者å¯ä»¥åˆ©ç”¨è¯¥æ¼æ´žåœ¨æœ¬åœ°å‘起永久拒ç»æœåŠ¡æ”»å‡»ï¼Œå› æ¤æˆ‘们将该æ¼æ´žçš„严é‡ç¨‹åº¦è¯„为“高â€ã€‚ </p> <table> @@ -207,7 +209,7 @@ Telephony ä¸çš„æ‹’ç»æœåŠ¡æ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用使用特制文件挂è <h3 id="dos-in-mediaserver">Mediaserver ä¸çš„æ‹’ç»æœåŠ¡æ¼æ´ž</h3> <p> -Mediaserver ä¸çš„æ‹’ç»æœåŠ¡æ¼æ´žå¯è®©æ”»å‡»è€…使用特制文件挂起或é‡å¯è®¾å¤‡ã€‚由于攻击者å¯ä»¥åˆ©ç”¨è¯¥æ¼æ´žè¿œç¨‹å‘èµ·æ‹’ç»æœåŠ¡æ”»å‡»ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“高â€ã€‚ +Mediaserver ä¸çš„æ‹’ç»æœåŠ¡æ¼æ´žå¯è®©æ”»å‡»è€…使用特制文件挂起或é‡å¯è®¾å¤‡ã€‚由于攻击者å¯ä»¥åˆ©ç”¨è¯¥æ¼æ´žè¿œç¨‹å‘èµ·æ‹’ç»æœåŠ¡æ”»å‡»ï¼Œå› æ¤æˆ‘们将该æ¼æ´žçš„严é‡ç¨‹åº¦è¯„为“高â€ã€‚ </p> <table> @@ -260,12 +262,12 @@ Mediaserver ä¸çš„æ‹’ç»æœåŠ¡æ¼æ´žå¯è®©æ”»å‡»è€…ä½¿ç”¨ç‰¹åˆ¶æ–‡ä»¶æŒ‚èµ·æˆ–é‡ </tbody></table> <p> -* æè½½ Android 7.0（或更高版本）且已安装所有å¯ç”¨æ›´æ–°çš„å—支æŒçš„ Google 设备ä¸å—æ¤æ¼æ´žçš„å½±å“。 +*æè½½ Android 7.0（或更高版本）且已安装所有å¯ç”¨æ›´æ–°çš„å—æ”¯æŒ Google 设备ä¸å—æ¤æ¼æ´žçš„å½±å“。 </p> <h3 id="rce-in-framesequence-library">Framesequence 库ä¸çš„远程代ç 执行æ¼æ´ž</h3> <p> -Framesequence 库ä¸çš„远程代ç 执行æ¼æ´žå¯è®©æ”»å‡»è€…使用特制文件通过éžç‰¹è®¸è¿›ç¨‹æ‰§è¡Œä»»æ„代ç 。由于攻击者å¯ä»¥åˆ©ç”¨è¯¥æ¼æ´žåœ¨ä½¿ç”¨ Framesequence 库的应用ä¸è¿œç¨‹æ‰§è¡Œä»£ç ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“高â€ã€‚ +Framesequence 库ä¸çš„远程代ç 执行æ¼æ´žå¯è®©æ”»å‡»è€…使用特制文件通过éžç‰¹è®¸è¿›ç¨‹æ‰§è¡Œä»»æ„代ç 。由于攻击者å¯ä»¥åˆ©ç”¨è¯¥æ¼æ´žåœ¨ä½¿ç”¨ Framesequence 库的应用ä¸è¿œç¨‹æ‰§è¡Œä»£ç ï¼Œå› æ¤æˆ‘们将该æ¼æ´žçš„严é‡ç¨‹åº¦è¯„为“高â€ã€‚ </p> <table> @@ -295,7 +297,7 @@ Framesequence 库ä¸çš„远程代ç 执行æ¼æ´žå¯è®©æ”»å‡»è€…使用特制文件 <h3 id="eop-in-smart-lock">Smart Lock ä¸çš„ææƒæ¼æ´ž</h3> <p> -Smart Lock ä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„ç”¨æˆ·åœ¨æ— éœ€è¾“å…¥ PIN ç 的情况下访问 Smart Lock 设置。由于该æ¼æ´žéœ€è¦æ”»å‡»è€…先拿到已解é”的实物设备，且è¦æ±‚设备用户最åŽä¸€æ¬¡è®¿é—®çš„è®¾ç½®çª—æ ¼å¿…é¡»æ˜¯ Smart Lockï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“ä¸â€ã€‚ +Smart Lock ä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„ç”¨æˆ·åœ¨æ— éœ€è¾“å…¥ PIN ç 的情况下访问 Smart Lock 设置。由于该æ¼æ´žéœ€è¦æ”»å‡»è€…先拿到已解é”的实物设备，且è¦æ±‚设备用户最åŽä¸€æ¬¡è®¿é—®çš„è®¾ç½®çª—æ ¼å¿…é¡»æ˜¯ Smart Lockï¼Œå› æ¤æˆ‘们将该æ¼æ´žçš„严é‡ç¨‹åº¦è¯„为“ä¸â€ã€‚ </p> <table> @@ -323,12 +325,12 @@ Smart Lock ä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„ç”¨æˆ·åœ¨æ— éœ€è¾“å…¥ PIN ç çš„æ </tr> </tbody></table> <p> -* æè½½ Android 7.0（或更高版本）且已安装所有å¯ç”¨æ›´æ–°çš„å—支æŒçš„ Google 设备ä¸å—æ¤æ¼æ´žçš„å½±å“。 +*æè½½ Android 7.0（或更高版本）且已安装所有å¯ç”¨æ›´æ–°çš„å—æ”¯æŒ Google 设备ä¸å—æ¤æ¼æ´žçš„å½±å“。 </p> <h3 id="eop-in-framework-apis">Framework API ä¸çš„ææƒæ¼æ´ž</h3> <p> -Framework API ä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用访问超出其访问æƒé™çº§åˆ«çš„系统功能。由于该æ¼æ´žå…许在本地绕过对å—é™è¿›ç¨‹çš„é™åˆ¶ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“ä¸â€ã€‚ +Framework API ä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用访问超出其访问æƒé™çº§åˆ«çš„系统功能。由于该æ¼æ´žå…许在本地绕过对å—é™è¿›ç¨‹çš„é™åˆ¶ï¼Œå› æ¤æˆ‘们将该æ¼æ´žçš„严é‡ç¨‹åº¦è¯„为“ä¸â€ã€‚ </p> <table> @@ -358,7 +360,7 @@ Framework API ä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨è®¿é—®è¶…å‡ºå…¶è®¿é—®æƒ <h3 id="eop-in-telephony">Telephony ä¸çš„ææƒæ¼æ´ž</h3> <p> -Telephony ä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用访问超出其访问æƒé™çº§åˆ«çš„系统功能。由于该æ¼æ´žå…许在本地绕过对å—é™è¿›ç¨‹çš„é™åˆ¶ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“ä¸â€ã€‚ +Telephony ä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用访问超出其访问æƒé™çº§åˆ«çš„系统功能。由于该æ¼æ´žå…许在本地绕过对å—é™è¿›ç¨‹çš„é™åˆ¶ï¼Œå› æ¤æˆ‘们将该æ¼æ´žçš„严é‡ç¨‹åº¦è¯„为“ä¸â€ã€‚ </p> <table> @@ -388,7 +390,7 @@ Telephony ä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用访问超出其访问æƒé™ç <h3 id="eop-in-wi-fi">WLAN ä¸çš„ææƒæ¼æ´ž</h3> <p> -WLAN ä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用通过特许进程执行任æ„代ç 。由于该æ¼æ´žéœ€è¦å…ˆç ´åç‰¹è®¸è¿›ç¨‹ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“ä¸â€ã€‚ +WLAN ä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用通过特许进程执行任æ„代ç 。由于æ¶æ„应用在利用该æ¼æ´žæ—¶éœ€è¦å…ˆç ´å特æƒè¿›ç¨‹ï¼Œå› æ¤æˆ‘们将该æ¼æ´žçš„严é‡ç¨‹åº¦è¯„为“ä¸â€ã€‚ </p> <table> @@ -408,7 +410,8 @@ WLAN ä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用通过特许进程执行任æ„代 </tr> <tr> <td>CVE-2016-6772</td> - <td><a href="https://android.googlesource.com/platform/frameworks/opt/net/wifi/+/a5a18239096f6faee80f15f3fff39c3311898484">A-31856351</a> [<a href="https://android.googlesource.com/platform/frameworks/opt/net/wifi/+/29a2baf3195256bab6a0a4a2d07b7f2efa46b614">2</a>]</td> + <td><a href="https://android.googlesource.com/platform/frameworks/opt/net/wifi/+/a5a18239096f6faee80f15f3fff39c3311898484">A-31856351</a> + [<a href="https://android.googlesource.com/platform/frameworks/opt/net/wifi/+/29a2baf3195256bab6a0a4a2d07b7f2efa46b614">2</a>]</td> <td>ä¸</td> <td>所有</td> <td>5.0.2ã€5.1.1ã€6.0ã€6.0.1ã€7.0</td> @@ -418,7 +421,7 @@ WLAN ä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用通过特许进程执行任æ„代 <h3 id="id-in-mediaserver">Mediaserver ä¸çš„ä¿¡æ¯æŠ«éœ²æ¼æ´ž</h3> <p> -Mediaserver ä¸çš„ä¿¡æ¯æŠ«éœ²æ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用获å–超出其æƒé™èŒƒå›´çš„æ•°æ®ã€‚由于攻击者å¯ä»¥åˆ©ç”¨è¯¥æ¼æ´žåœ¨æœªç»è®¸å¯çš„情况下获å–æ•æ„Ÿæ•°æ®ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“ä¸â€ã€‚ +Mediaserver ä¸çš„ä¿¡æ¯æŠ«éœ²æ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用获å–超出其æƒé™èŒƒå›´çš„æ•°æ®ã€‚由于攻击者å¯ä»¥åˆ©ç”¨è¯¥æ¼æ´žåœ¨æœªç»è®¸å¯çš„情况下获å–æ•æ„Ÿæ•°æ®ï¼Œå› æ¤æˆ‘们将该æ¼æ´žçš„严é‡ç¨‹åº¦è¯„为“ä¸â€ã€‚ </p> <table> @@ -438,7 +441,8 @@ Mediaserver ä¸çš„ä¿¡æ¯æŠ«éœ²æ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用获å–超出其æƒé™ </tr> <tr> <td>CVE-2016-6773</td> - <td><a href="https://android.googlesource.com/platform/external/libavc/+/026745ef046e646b8d04f4f57d8320042f6b29b0">A-30481714</a> [<a href="https://android.googlesource.com/platform/external/libavc/+/6676aeb4195e7c7379915c0972f3d209410f0641">2</a>]</td> + <td><a href="https://android.googlesource.com/platform/external/libavc/+/026745ef046e646b8d04f4f57d8320042f6b29b0">A-30481714</a> + [<a href="https://android.googlesource.com/platform/external/libavc/+/6676aeb4195e7c7379915c0972f3d209410f0641">2</a>]</td> <td>ä¸</td> <td>所有</td> <td>6.0ã€6.0.1ã€7.0</td> @@ -448,7 +452,7 @@ Mediaserver ä¸çš„ä¿¡æ¯æŠ«éœ²æ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用获å–超出其æƒé™ <h3 id="id-in-package-manager">软件包管ç†å™¨ä¸çš„ä¿¡æ¯æŠ«éœ²æ¼æ´ž</h3> <p> -软件包管ç†å™¨ä¸çš„ä¿¡æ¯æŠ«éœ²æ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用绕过将应用数æ®ä¸Žå…¶ä»–应用隔离开的æ“作系统防护功能。由于该æ¼æ´žéœ€è¦å…ˆç ´åç‰¹è®¸è¿›ç¨‹ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“ä¸â€ã€‚ +软件包管ç†å™¨ä¸çš„ä¿¡æ¯æŠ«éœ²æ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用绕过将应用数æ®ä¸Žå…¶ä»–应用隔离开的æ“作系统防护功能。由于æ¶æ„应用在利用该æ¼æ´žæ—¶éœ€è¦å…ˆç ´å特æƒè¿›ç¨‹ï¼Œå› æ¤æˆ‘们将该æ¼æ´žçš„严é‡ç¨‹åº¦è¯„为“ä¸â€ã€‚ </p> <table> @@ -477,11 +481,11 @@ Mediaserver ä¸çš„ä¿¡æ¯æŠ«éœ²æ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用获å–超出其æƒé™ </tbody></table> <h2 id="2016-12-05-details">2016-12-05 安全补ä¸ç¨‹åºçº§åˆ« - æ¼æ´žè¯¦æƒ…</h2> -<p>我们在下é¢æ供了 2016-12-05 è¡¥ä¸ç¨‹åºçº§åˆ«æ¶µç›–çš„æ¯ä¸ªå®‰å…¨æ¼æ´žçš„详细信æ¯ï¼Œå…¶ä¸åŒ…括问题æè¿°ã€ä¸¥é‡ç¨‹åº¦é˜é‡Šå’Œä¸€ä¸ªè¡¨ï¼Œè¯¥è¡¨ä¸åŒ…å« CVEã€ç›¸å…³å‚考信æ¯ã€ä¸¥é‡ç¨‹åº¦ã€å·²æ›´æ–°çš„ Google 设备ã€å·²æ›´æ–°çš„ AOSP 版本（如果适用）åŠæŠ¥å‘Šæ—¥æœŸã€‚在适用的情况下，我们会将 Bug ID 链接到解决相应问题的公开更改记录（如 AOSP 代ç 更改列表）。如果æŸä¸ª Bug 有多æ¡ç›¸å…³çš„更改记录，我们还通过 Bug ID åŽé¢çš„æ•°å—链接到了更多å‚考信æ¯ã€‚</p> +<p>我们在下é¢æ供了 2016-12-05 è¡¥ä¸ç¨‹åºçº§åˆ«æ¶µç›–çš„æ¯ä¸ªå®‰å…¨æ¼æ´žçš„详细信æ¯ï¼Œå…¶ä¸åŒ…括问题æè¿°ã€ä¸¥é‡ç¨‹åº¦é˜é‡Šå’Œä¸€ä¸ªè¡¨ï¼Œè¯¥è¡¨ä¸åŒ…å« CVEã€ç›¸å…³å‚考信æ¯ã€ä¸¥é‡ç¨‹åº¦ã€å·²æ›´æ–°çš„ Google 设备ã€å·²æ›´æ–°çš„ AOSP 版本（如果适用）åŠæŠ¥å‘Šæ—¥æœŸã€‚在适用的情况下，我们会将 Bug ID 链接到解决相应问题的公开更改记录（如 AOSP 代ç 更改列表）。如果æŸä¸ª Bug 有多æ¡ç›¸å…³çš„更改记录，我们还将通过 Bug ID åŽé¢çš„æ•°å—链接到更多å‚考信æ¯ã€‚</p> <h3 id="eop-in-kernel-memory-subsystem">å†…æ ¸å†…å˜å系统ä¸çš„ææƒæ¼æ´ž</h3> <p> -å†…æ ¸å†…å˜å系统ä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡å†…æ ¸æ‰§è¡Œä»»æ„代ç 。由于该æ¼æ´žæœ‰å¯èƒ½ä¼šé€ æˆæœ¬åœ°è®¾å¤‡æ°¸ä¹…æŸå，而用户å¯èƒ½éœ€è¦é€šè¿‡é‡å†™æ“作系统æ¥ä¿®å¤è®¾å¤‡ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“严é‡â€ã€‚ +å†…æ ¸å†…å˜å系统ä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡å†…æ ¸æ‰§è¡Œä»»æ„代ç 。由于该æ¼æ´žæœ‰å¯èƒ½ä¼šé€ æˆæœ¬åœ°è®¾å¤‡æ°¸ä¹…æŸå，而用户å¯èƒ½éœ€è¦é€šè¿‡é‡å†™æ“作系统æ¥ä¿®å¤è®¾å¤‡ï¼Œå› æ¤æˆ‘们将该æ¼æ´žçš„严é‡ç¨‹åº¦è¯„为“严é‡â€ã€‚ </p> <table> @@ -500,7 +504,8 @@ Mediaserver ä¸çš„ä¿¡æ¯æŠ«éœ²æ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用获å–超出其æƒé™ <tr> <td>CVE-2016-4794</td> <td>A-31596597<br /> - <a href="http://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=6710e594f71ccaad8101bc64321152af7cd9ea28">ä¸Šæ¸¸å†…æ ¸</a> [<a href="http://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=4f996e234dad488e5d9ba0858bc1bae12eff82c3">2</a>]</td> + <a href="http://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=6710e594f71ccaad8101bc64321152af7cd9ea28">ä¸Šæ¸¸å†…æ ¸</a> + [<a href="http://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=4f996e234dad488e5d9ba0858bc1bae12eff82c3">2</a>]</td> <td>严é‡</td> <td>Pixel Cã€Pixelã€Pixel XL</td> <td>2016 å¹´ 4 月 17 æ—¥</td> @@ -508,7 +513,8 @@ Mediaserver ä¸çš„ä¿¡æ¯æŠ«éœ²æ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用获å–超出其æƒé™ <tr> <td>CVE-2016-5195</td> <td>A-32141528<br /> - <a href="https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=9691eac5593ff1e2f82391ad327f21d90322aec1">ä¸Šæ¸¸å†…æ ¸</a> [<a href="https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=e45a502bdeae5a075257c4f061d1ff4ff0821354">2</a>]</td> + <a href="https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=9691eac5593ff1e2f82391ad327f21d90322aec1">ä¸Šæ¸¸å†…æ ¸</a> + [<a href="https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=e45a502bdeae5a075257c4f061d1ff4ff0821354">2</a>]</td> <td>严é‡</td> <td>Nexus 5Xã€Nexus 6ã€Nexus 6Pã€Nexus 9ã€Android Oneã€Pixel Cã€Nexus Playerã€Pixelã€Pixel XL</td> <td>2016 å¹´ 10 月 12 æ—¥</td> @@ -517,7 +523,7 @@ Mediaserver ä¸çš„ä¿¡æ¯æŠ«éœ²æ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用获å–超出其æƒé™ <h3 id="eop-in-nvidia-gpu-driver">NVIDIA GPU 驱动程åºä¸çš„ææƒæ¼æ´ž</h3> <p> -NVIDIA GPU 驱动程åºä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡å†…æ ¸æ‰§è¡Œä»»æ„代ç 。由于该æ¼æ´žæœ‰å¯èƒ½ä¼šé€ æˆæœ¬åœ°è®¾å¤‡æ°¸ä¹…æŸå，而用户å¯èƒ½éœ€è¦é€šè¿‡é‡å†™æ“作系统æ¥ä¿®å¤è®¾å¤‡ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“严é‡â€ã€‚ +NVIDIA GPU 驱动程åºä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡å†…æ ¸æ‰§è¡Œä»»æ„代ç 。由于该æ¼æ´žæœ‰å¯èƒ½ä¼šé€ æˆæœ¬åœ°è®¾å¤‡æ°¸ä¹…æŸå，而用户å¯èƒ½éœ€è¦é€šè¿‡é‡å†™æ“作系统æ¥ä¿®å¤è®¾å¤‡ï¼Œå› æ¤æˆ‘们将该æ¼æ´žçš„严é‡ç¨‹åº¦è¯„为“严é‡â€ã€‚ </p> <table> @@ -556,12 +562,12 @@ NVIDIA GPU 驱动程åºä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡å†…æ ¸æ‰§ </tr> </tbody></table> <p> -* 针对该问题的补ä¸ç¨‹åºæœªå…¬å¼€å‘布。<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上æ供的 Google 设备的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。 +*尚未公开å‘布针对该问题的补ä¸ç¨‹åºã€‚<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上针对 Google 设备æ供的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。 </p> <h3 id="eop-in-kernel">å†…æ ¸ä¸çš„ææƒæ¼æ´ž</h3> <p> -å†…æ ¸ä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡å†…æ ¸æ‰§è¡Œä»»æ„代ç 。由于该æ¼æ´žæœ‰å¯èƒ½ä¼šé€ æˆæœ¬åœ°è®¾å¤‡æ°¸ä¹…æŸå，而用户å¯èƒ½éœ€è¦é€šè¿‡é‡å†™æ“作系统æ¥ä¿®å¤è®¾å¤‡ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“严é‡â€ã€‚ +å†…æ ¸ä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡å†…æ ¸æ‰§è¡Œä»»æ„代ç 。由于该æ¼æ´žæœ‰å¯èƒ½ä¼šé€ æˆæœ¬åœ°è®¾å¤‡æ°¸ä¹…æŸå，而用户å¯èƒ½éœ€è¦é€šè¿‡é‡å†™æ“作系统æ¥ä¿®å¤è®¾å¤‡ï¼Œå› æ¤æˆ‘们将该æ¼æ´žçš„严é‡ç¨‹åº¦è¯„为“严é‡â€ã€‚ </p> <table> @@ -587,11 +593,11 @@ NVIDIA GPU 驱动程åºä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡å†…æ ¸æ‰§ </tr> </tbody></table> <p> -* æè½½ Android 7.0（或更高版本）且已安装所有å¯ç”¨æ›´æ–°çš„å—支æŒçš„ Google 设备ä¸å—æ¤æ¼æ´žçš„å½±å“。 +*æè½½ Android 7.0（或更高版本）且已安装所有å¯ç”¨æ›´æ–°çš„å—æ”¯æŒ Google 设备ä¸å—æ¤æ¼æ´žçš„å½±å“。 </p> <h3 id="eop-in-nvidia-video-driver">NVIDIA 视频驱动程åºä¸çš„ææƒæ¼æ´ž</h3> -<p>NVIDIA 视频驱动程åºä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡å†…æ ¸æ‰§è¡Œä»»æ„代ç 。由于该æ¼æ´žæœ‰å¯èƒ½ä¼šé€ æˆæœ¬åœ°è®¾å¤‡æ°¸ä¹…æŸå，而用户å¯èƒ½éœ€è¦é€šè¿‡é‡å†™æ“作系统æ¥ä¿®å¤è®¾å¤‡ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“严é‡â€ã€‚ +<p>NVIDIA 视频驱动程åºä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡å†…æ ¸æ‰§è¡Œä»»æ„代ç 。由于该æ¼æ´žæœ‰å¯èƒ½ä¼šé€ æˆæœ¬åœ°è®¾å¤‡æ°¸ä¹…æŸå，而用户å¯èƒ½éœ€è¦é€šè¿‡é‡å†™æ“作系统æ¥ä¿®å¤è®¾å¤‡ï¼Œå› æ¤æˆ‘们将该æ¼æ´žçš„严é‡ç¨‹åº¦è¯„为“严é‡â€ã€‚ </p> <table> @@ -616,26 +622,28 @@ NVIDIA GPU 驱动程åºä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡å†…æ ¸æ‰§ </tr> <tr> <td>CVE-2016-6916</td> - <td>A-32072350*<br />N-CVE-2016-6916</td> + <td>A-32072350* + <br />N-CVE-2016-6916</td> <td>严é‡</td> <td>Nexus 9ã€Pixel C</td> <td>2016 å¹´ 9 月 13 æ—¥</td> </tr> <tr> <td>CVE-2016-6917</td> - <td>A-32072253*<br />N-CVE-2016-6917</td> + <td>A-32072253* + <br />N-CVE-2016-6917</td> <td>严é‡</td> <td>Nexus 9</td> <td>2016 å¹´ 9 月 13 æ—¥</td> </tr> </tbody></table> <p> -* 针对该问题的补ä¸ç¨‹åºæœªå…¬å¼€å‘布。<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上æ供的 Google 设备的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。 +*尚未公开å‘布针对该问题的补ä¸ç¨‹åºã€‚<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上针对 Google 设备æ供的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。 </p> <h3 id="eop-in-kernel-ion-driver">å†…æ ¸ ION 驱动程åºä¸çš„ææƒæ¼æ´ž</h3> <p> -å†…æ ¸ ION 驱动程åºä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡å†…æ ¸æ‰§è¡Œä»»æ„代ç 。由于该æ¼æ´žæœ‰å¯èƒ½ä¼šé€ æˆæœ¬åœ°è®¾å¤‡æ°¸ä¹…æŸå，而用户å¯èƒ½éœ€è¦é€šè¿‡é‡å†™æ“作系统æ¥ä¿®å¤è®¾å¤‡ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“严é‡â€ã€‚ +å†…æ ¸ ION 驱动程åºä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡å†…æ ¸æ‰§è¡Œä»»æ„代ç 。由于该æ¼æ´žæœ‰å¯èƒ½ä¼šé€ æˆæœ¬åœ°è®¾å¤‡æ°¸ä¹…æŸå，而用户å¯èƒ½éœ€è¦é€šè¿‡é‡å†™æ“作系统æ¥ä¿®å¤è®¾å¤‡ï¼Œå› æ¤æˆ‘们将该æ¼æ´žçš„严é‡ç¨‹åº¦è¯„为“严é‡â€ã€‚ </p> <table> @@ -686,13 +694,13 @@ NVIDIA GPU 驱动程åºä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡å†…æ ¸æ‰§ <td>Qualcomm 内部</td> </tr> </tbody></table> -<p>* 这些æ¼æ´žçš„严é‡ç¨‹åº¦è¯„级由供应商决定。</p> -<p>** 针对该问题的补ä¸ç¨‹åºæœªå…¬å¼€å‘布。<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上æ供的 Google 设备的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。 +<p>*这些æ¼æ´žçš„严é‡ç¨‹åº¦è¯„级是由供应商决定的。</p> +<p>**尚未公开å‘布针对该问题的补ä¸ç¨‹åºã€‚<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上针对 Google 设备æ供的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。 </p> <h3 id="eop-in-kernel-file-system">å†…æ ¸æ–‡ä»¶ç³»ç»Ÿä¸çš„ææƒæ¼æ´ž</h3> <p> -å†…æ ¸æ–‡ä»¶ç³»ç»Ÿä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用绕过将应用数æ®ä¸Žå…¶ä»–应用隔离开的æ“作系统防护功能。由于攻击者å¯ä»¥åˆ©ç”¨è¯¥æ¼æ´žä½¿ç¬¬ä¸‰æ–¹åº”用在本地获å–超出规定的æƒèƒ½ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“高â€ã€‚ +å†…æ ¸æ–‡ä»¶ç³»ç»Ÿä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用绕过将应用数æ®ä¸Žå…¶ä»–应用隔离开的æ“作系统防护功能。由于攻击者å¯ä»¥åˆ©ç”¨è¯¥æ¼æ´žä½¿ç¬¬ä¸‰æ–¹åº”用在本地获å–超出规定的æƒèƒ½ï¼Œå› æ¤æˆ‘们将该æ¼æ´žçš„严é‡ç¨‹åº¦è¯„为“高â€ã€‚ </p> <table> @@ -720,7 +728,7 @@ NVIDIA GPU 驱动程åºä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡å†…æ ¸æ‰§ <h3 id="eop-in-kernel-2">å†…æ ¸ä¸çš„ææƒæ¼æ´ž</h3> <p> -å†…æ ¸ä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡å†…æ ¸æ‰§è¡Œä»»æ„代ç 。由于该æ¼æ´žçš„攻击行为必须å‘生在å¦ä¸€ä¸ªæ¼æ´žæ”»å‡»è¡Œä¸ºä¹‹åŽï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“高â€ã€‚ +å†…æ ¸ä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡å†…æ ¸æ‰§è¡Œä»»æ„代ç 。由于该æ¼æ´žçš„攻击行为必须å‘生在å¦ä¸€ä¸ªæ¼æ´žæ”»å‡»è¡Œä¸ºä¹‹åŽï¼Œå› æ¤æˆ‘们将该æ¼æ´žçš„严é‡ç¨‹åº¦è¯„为“高â€ã€‚ </p> <table> @@ -748,7 +756,7 @@ NVIDIA GPU 驱动程åºä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡å†…æ ¸æ‰§ <h3 id="eop-in-htc-sound-codec-driver">HTC 声音编解ç 器驱动程åºä¸çš„ææƒæ¼æ´ž</h3> <p> -HTC 声音编解ç 器驱动程åºä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡å†…æ ¸æ‰§è¡Œä»»æ„代ç 。由于该æ¼æ´žéœ€è¦å…ˆç ´åç‰¹è®¸è¿›ç¨‹ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“高â€ã€‚ +HTC 声音编解ç 器驱动程åºä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡å†…æ ¸æ‰§è¡Œä»»æ„代ç 。由于æ¶æ„应用在利用该æ¼æ´žæ—¶éœ€è¦å…ˆç ´å特æƒè¿›ç¨‹ï¼Œå› æ¤æˆ‘们将该æ¼æ´žçš„严é‡ç¨‹åº¦è¯„为“高â€ã€‚ </p> <table> @@ -787,12 +795,12 @@ HTC 声音编解ç 器驱动程åºä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用通è </tr> </tbody></table> <p> -* 针对该问题的补ä¸ç¨‹åºæœªå…¬å¼€å‘布。<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上æ供的 Google 设备的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。 +*尚未公开å‘布针对该问题的补ä¸ç¨‹åºã€‚<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上针对 Google 设备æ供的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。 </p> <h3 id="eop-in-mediatek-driver">MediaTek 驱动程åºä¸çš„ææƒæ¼æ´ž</h3> <p> -MediaTek 驱动程åºä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡å†…æ ¸æ‰§è¡Œä»»æ„代ç 。由于该æ¼æ´žéœ€è¦å…ˆç ´åç‰¹è®¸è¿›ç¨‹ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“高â€ã€‚ +MediaTek 驱动程åºä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡å†…æ ¸æ‰§è¡Œä»»æ„代ç 。由于æ¶æ„应用在利用该æ¼æ´žæ—¶éœ€è¦å…ˆç ´å特æƒè¿›ç¨‹ï¼Œå› æ¤æˆ‘们将该æ¼æ´žçš„严é‡ç¨‹åº¦è¯„为“高â€ã€‚ </p> <table> @@ -852,12 +860,12 @@ MediaTek 驱动程åºä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡å†…æ ¸æ‰§è¡ </tr> </tbody></table> <p> -* æè½½ Android 7.0（或更高版本）且已安装所有å¯ç”¨æ›´æ–°çš„å—支æŒçš„ Google 设备ä¸å—æ¤æ¼æ´žçš„å½±å“。 +*æè½½ Android 7.0（或更高版本）且已安装所有å¯ç”¨æ›´æ–°çš„å—æ”¯æŒ Google 设备ä¸å—æ¤æ¼æ´žçš„å½±å“。 </p> <h3 id="eop-in-qualcomm-media-codecs">Qualcomm 媒体编解ç 器ä¸çš„ææƒæ¼æ´ž</h3> <p> -Qualcomm 媒体编解ç 器ä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用通过特许进程执行任æ„代ç 。由于攻击者å¯ä»¥åˆ©ç”¨è¯¥æ¼æ´žä½¿ç¬¬ä¸‰æ–¹åº”用在本地获å–超出规定的æƒèƒ½ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“高â€ã€‚ +Qualcomm 媒体编解ç 器ä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用通过特许进程执行任æ„代ç 。由于攻击者å¯ä»¥åˆ©ç”¨è¯¥æ¼æ´žä½¿ç¬¬ä¸‰æ–¹åº”用在本地获å–超出规定的æƒèƒ½ï¼Œå› æ¤æˆ‘们将该æ¼æ´žçš„严é‡ç¨‹åº¦è¯„为“高â€ã€‚ </p> <table> @@ -875,40 +883,44 @@ Qualcomm 媒体编解ç 器ä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡ç‰¹è® </tr> <tr> <td>CVE-2016-6761</td> - <td>A-29421682*<br />QC-CR#1055792</td> + <td>A-29421682* + <br />QC-CR#1055792</td> <td>高</td> <td>Nexus 5Xã€Nexus 6ã€Nexus 6Pã€Nexus 9ã€Android Oneã€Nexus Playerã€Pixelã€Pixel XL</td> <td>2016 å¹´ 6 月 16 æ—¥</td> </tr> <tr> <td>CVE-2016-6760</td> - <td>A-29617572*<br />QC-CR#1055783</td> + <td>A-29617572* + <br />QC-CR#1055783</td> <td>高</td> <td>Nexus 5Xã€Nexus 6ã€Nexus 6Pã€Nexus 9ã€Android Oneã€Nexus Playerã€Pixelã€Pixel XL</td> <td>2016 å¹´ 6 月 23 æ—¥</td> </tr> <tr> <td>CVE-2016-6759</td> - <td>A-29982686*<br />QC-CR#1055766</td> + <td>A-29982686* + <br />QC-CR#1055766</td> <td>高</td> <td>Nexus 5Xã€Nexus 6ã€Nexus 6Pã€Nexus 9ã€Android Oneã€Nexus Playerã€Pixelã€Pixel XL</td> <td>2016 å¹´ 7 月 4 æ—¥</td> </tr> <tr> <td>CVE-2016-6758</td> - <td>A-30148882*<br />QC-CR#1071731</td> + <td>A-30148882* + <br />QC-CR#1071731</td> <td>高</td> <td>Nexus 5Xã€Nexus 6ã€Nexus 6Pã€Nexus 9ã€Android Oneã€Nexus Playerã€Pixelã€Pixel XL</td> <td>2016 å¹´ 7 月 13 æ—¥</td> </tr> </tbody></table> <p> -* 针对该问题的补ä¸ç¨‹åºæœªå…¬å¼€å‘布。<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上æ供的 Google 设备的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。 +*尚未公开å‘布针对该问题的补ä¸ç¨‹åºã€‚<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上针对 Google 设备æ供的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。 </p> -<h3 id="eop-in-qualcomm-camera-driver">Qualcomm 相机驱动程åºä¸çš„ææƒæ¼æ´ž</h3> +<h3 id="eop-in-qualcomm-camera-driver">Qualcomm æ‘„åƒå¤´é©±åŠ¨ç¨‹åºä¸çš„ææƒæ¼æ´ž</h3> <p> -Qualcomm 相机驱动程åºä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡å†…æ ¸æ‰§è¡Œä»»æ„代ç 。由于该æ¼æ´žéœ€è¦å…ˆç ´åç‰¹è®¸è¿›ç¨‹ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“高â€ã€‚ +Qualcomm æ‘„åƒå¤´é©±åŠ¨ç¨‹åºä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡å†…æ ¸æ‰§è¡Œä»»æ„代ç 。由于æ¶æ„应用在利用该æ¼æ´žæ—¶éœ€è¦å…ˆç ´å特æƒè¿›ç¨‹ï¼Œå› æ¤æˆ‘们将该æ¼æ´žçš„严é‡ç¨‹åº¦è¯„为“高â€ã€‚ </p> <table> @@ -936,7 +948,7 @@ Qualcomm 相机驱动程åºä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用通过内æ <h3 id="eop-in-kernel-performance-subsystem">å†…æ ¸æ•ˆèƒ½å系统ä¸çš„ææƒæ¼æ´ž</h3> <p> -å†…æ ¸æ•ˆèƒ½å系统ä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡å†…æ ¸æ‰§è¡Œä»»æ„代ç 。由于该æ¼æ´žéœ€è¦å…ˆç ´åç‰¹è®¸è¿›ç¨‹ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“高â€ã€‚ +å†…æ ¸æ•ˆèƒ½å系统ä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡å†…æ ¸æ‰§è¡Œä»»æ„代ç 。由于æ¶æ„应用在利用该æ¼æ´žæ—¶éœ€è¦å…ˆç ´å特æƒè¿›ç¨‹ï¼Œå› æ¤æˆ‘们将该æ¼æ´žçš„严é‡ç¨‹åº¦è¯„为“高â€ã€‚ </p> <table> @@ -972,7 +984,7 @@ Qualcomm 相机驱动程åºä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用通过内æ <h3 id="eop-in-mediatek-i2c-driver">MediaTek I2C 驱动程åºä¸çš„ææƒæ¼æ´ž</h3> <p> -MediaTek I2C 驱动程åºä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡å†…æ ¸æ‰§è¡Œä»»æ„代ç 。由于该æ¼æ´žéœ€è¦å…ˆç ´åç‰¹è®¸è¿›ç¨‹ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“高â€ã€‚ +MediaTek I2C 驱动程åºä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡å†…æ ¸æ‰§è¡Œä»»æ„代ç 。由于æ¶æ„应用在利用该æ¼æ´žæ—¶éœ€è¦å…ˆç ´å特æƒè¿›ç¨‹ï¼Œå› æ¤æˆ‘们将该æ¼æ´žçš„严é‡ç¨‹åº¦è¯„为“高â€ã€‚ </p> <table> @@ -997,12 +1009,12 @@ MediaTek I2C 驱动程åºä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡å†…æ ¸æ </tr> </tbody></table> <p> -* æè½½ Android 7.0（或更高版本）且已安装所有å¯ç”¨æ›´æ–°çš„å—支æŒçš„ Google 设备ä¸å—æ¤æ¼æ´žçš„å½±å“。 +*æè½½ Android 7.0（或更高版本）且已安装所有å¯ç”¨æ›´æ–°çš„å—æ”¯æŒ Google 设备ä¸å—æ¤æ¼æ´žçš„å½±å“。 </p> <h3 id="eop-in-nvidia-libomx-library">NVIDIA libomx 库ä¸çš„ææƒæ¼æ´ž</h3> <p> -NVIDIA libomx 库 (libnvomx) ä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用通过特许进程执行任æ„代ç 。由于攻击者å¯ä»¥åˆ©ç”¨è¯¥æ¼æ´žä½¿ç¬¬ä¸‰æ–¹åº”用在本地获å–超出规定的æƒèƒ½ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“高â€ã€‚ +NVIDIA libomx 库 (libnvomx) ä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用通过特许进程执行任æ„代ç 。由于攻击者å¯ä»¥åˆ©ç”¨è¯¥æ¼æ´žä½¿ç¬¬ä¸‰æ–¹åº”用在本地获å–超出规定的æƒèƒ½ï¼Œå› æ¤æˆ‘们将该æ¼æ´žçš„严é‡ç¨‹åº¦è¯„为“高â€ã€‚ </p> <table> @@ -1020,26 +1032,28 @@ NVIDIA libomx 库 (libnvomx) ä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用通过特 </tr> <tr> <td>CVE-2016-6789</td> - <td>A-31251973*<br />N-CVE-2016-6789</td> + <td>A-31251973* + <br />N-CVE-2016-6789</td> <td>高</td> <td>Pixel C</td> <td>2016 å¹´ 8 月 29 æ—¥</td> </tr> <tr> <td>CVE-2016-6790</td> - <td>A-31251628*<br />N-CVE-2016-6790</td> + <td>A-31251628* + <br />N-CVE-2016-6790</td> <td>高</td> <td>Pixel C</td> <td>2016 å¹´ 8 月 28 æ—¥</td> </tr> </tbody></table> <p> -* 针对该问题的补ä¸ç¨‹åºæœªå…¬å¼€å‘布。<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上æ供的 Google 设备的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。 +*尚未公开å‘布针对该问题的补ä¸ç¨‹åºã€‚<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上针对 Google 设备æ供的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。 </p> <h3 id="eop-in-qualcomm-sound-driver">Qualcomm 声音驱动程åºä¸çš„ææƒæ¼æ´ž</h3> <p> -Qualcomm 声音驱动程åºä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡å†…æ ¸æ‰§è¡Œä»»æ„代ç 。由于该æ¼æ´žéœ€è¦å…ˆç ´åç‰¹è®¸è¿›ç¨‹ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“高â€ã€‚ +Qualcomm 声音驱动程åºä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡å†…æ ¸æ‰§è¡Œä»»æ„代ç 。由于æ¶æ„应用在利用该æ¼æ´žæ—¶éœ€è¦å…ˆç ´å特æƒè¿›ç¨‹ï¼Œå› æ¤æˆ‘们将该æ¼æ´žçš„严é‡ç¨‹åº¦è¯„为“高â€ã€‚ </p> <table> @@ -1058,7 +1072,8 @@ Qualcomm 声音驱动程åºä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用通过内æ <tr> <td>CVE-2016-6791</td> <td>A-31252384<br /> - <a href="https://source.codeaurora.org/quic/la/kernel/msm-3.10/commit/?id=62580295210b6c0bd809cde7088b45ebb65ace79">QC-CR#1071809</a></td> + <a href="https://source.codeaurora.org/quic/la/kernel/msm-3.10/commit/?id=62580295210b6c0bd809cde7088b45ebb65ace79"> +QC-CR#1071809</a></td> <td>高</td> <td>Nexus 5Xã€Nexus 6ã€Nexus 6Pã€Android Oneã€Pixelã€Pixel XL</td> <td>2016 å¹´ 8 月 31 æ—¥</td> @@ -1066,7 +1081,8 @@ Qualcomm 声音驱动程åºä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用通过内æ <tr> <td>CVE-2016-8391</td> <td>A-31253255<br /> - <a href="https://source.codeaurora.org/quic/la/kernel/msm-3.10/commit/?id=62580295210b6c0bd809cde7088b45ebb65ace79">QC-CR#1072166</a></td> + <a href="https://source.codeaurora.org/quic/la/kernel/msm-3.10/commit/?id=62580295210b6c0bd809cde7088b45ebb65ace79"> +QC-CR#1072166</a></td> <td>高</td> <td>Nexus 5Xã€Nexus 6ã€Nexus 6Pã€Android Oneã€Pixelã€Pixel XL</td> <td>2016 å¹´ 8 月 31 æ—¥</td> @@ -1074,7 +1090,8 @@ Qualcomm 声音驱动程åºä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用通过内æ <tr> <td>CVE-2016-8392</td> <td>A-31385862<br /> - <a href="https://source.codeaurora.org/quic/la/kernel/msm-3.10/commit/?id=62580295210b6c0bd809cde7088b45ebb65ace79">QC-CR#1073136</a></td> + <a href="https://source.codeaurora.org/quic/la/kernel/msm-3.10/commit/?id=62580295210b6c0bd809cde7088b45ebb65ace79"> +QC-CR#1073136</a></td> <td>高</td> <td>Nexus 5Xã€Nexus 6ã€Nexus 6Pã€Android Oneã€Pixelã€Pixel XL</td> <td>2016 å¹´ 9 月 8 æ—¥</td> @@ -1083,7 +1100,7 @@ Qualcomm 声音驱动程åºä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用通过内æ <h3 id="eop-in-kernel-security-subsystem">å†…æ ¸å®‰å…¨å系统ä¸çš„ææƒæ¼æ´ž</h3> <p> -å†…æ ¸å®‰å…¨å系统ä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡å†…æ ¸æ‰§è¡Œä»»æ„代ç 。由于该æ¼æ´žéœ€è¦å…ˆç ´åç‰¹è®¸è¿›ç¨‹ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“高â€ã€‚ +å†…æ ¸å®‰å…¨å系统ä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡å†…æ ¸æ‰§è¡Œä»»æ„代ç 。由于æ¶æ„应用在利用该æ¼æ´žæ—¶éœ€è¦å…ˆç ´å特æƒè¿›ç¨‹ï¼Œå› æ¤æˆ‘们将该æ¼æ´žçš„严é‡ç¨‹åº¦è¯„为“高â€ã€‚ </p> <table> @@ -1112,7 +1129,7 @@ Qualcomm 声音驱动程åºä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用通过内æ <h3 id="eop-in-synaptics-touchscreen-driver">Synaptics 触摸å±é©±åŠ¨ç¨‹åºä¸çš„ææƒæ¼æ´ž</h3> <p> -Synaptics 触摸å±é©±åŠ¨ç¨‹åºä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡å†…æ ¸æ‰§è¡Œä»»æ„代ç 。由于该æ¼æ´žéœ€è¦å…ˆç ´åç‰¹è®¸è¿›ç¨‹ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“高â€ã€‚ +Synaptics 触摸å±é©±åŠ¨ç¨‹åºä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡å†…æ ¸æ‰§è¡Œä»»æ„代ç 。由于æ¶æ„应用在利用该æ¼æ´žæ—¶éœ€è¦å…ˆç ´å特æƒè¿›ç¨‹ï¼Œå› æ¤æˆ‘们将该æ¼æ´žçš„严é‡ç¨‹åº¦è¯„为“高â€ã€‚ </p> <table> @@ -1144,12 +1161,12 @@ Synaptics 触摸å±é©±åŠ¨ç¨‹åºä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用通过å </tr> </tbody></table> <p> -* 针对该问题的补ä¸ç¨‹åºæœªå…¬å¼€å‘布。<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上æ供的 Google 设备的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。 +*尚未公开å‘布针对该问题的补ä¸ç¨‹åºã€‚<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上针对 Google 设备æ供的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。 </p> <h3 id="eop-in-broadcom-wi-fi-driver">Broadcom WLAN 驱动程åºä¸çš„ææƒæ¼æ´ž</h3> <p> -Broadcom WLAN 驱动程åºä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡å†…æ ¸æ‰§è¡Œä»»æ„代ç 。由于该æ¼æ´žéœ€è¦å…ˆç ´åç‰¹è®¸è¿›ç¨‹ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“高â€ã€‚ +Broadcom WLAN 驱动程åºä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡å†…æ ¸æ‰§è¡Œä»»æ„代ç 。由于æ¶æ„应用在利用该æ¼æ´žæ—¶éœ€è¦å…ˆç ´å特æƒè¿›ç¨‹ï¼Œå› æ¤æˆ‘们将该æ¼æ´žçš„严é‡ç¨‹åº¦è¯„为“高â€ã€‚ </p> <table> @@ -1181,12 +1198,12 @@ Broadcom WLAN 驱动程åºä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡å†…æ ¸ </tr> </tbody></table> <p> -* æè½½ Android 7.0（或更高版本）且已安装所有å¯ç”¨æ›´æ–°çš„å—支æŒçš„ Google 设备ä¸å—æ¤æ¼æ´žçš„å½±å“。 +*æè½½ Android 7.0（或更高版本）且已安装所有å¯ç”¨æ›´æ–°çš„å—æ”¯æŒ Google 设备ä¸å—æ¤æ¼æ´žçš„å½±å“。 </p> <h3 id="id-in-mediatek-video-driver">MediaTek 视频驱动程åºä¸çš„ä¿¡æ¯æŠ«éœ²æ¼æ´ž</h3> <p> -MediaTek 视频驱动程åºä¸çš„ä¿¡æ¯æŠ«éœ²æ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用获å–超出其æƒé™èŒƒå›´çš„æ•°æ®ã€‚由于攻击者å¯ä»¥åˆ©ç”¨è¯¥æ¼æ´žåœ¨æœªç»ç”¨æˆ·æ˜Žç¡®è®¸å¯çš„情况下获å–æ•æ„Ÿæ•°æ®ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“高â€ã€‚ +MediaTek 视频驱动程åºä¸çš„ä¿¡æ¯æŠ«éœ²æ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用获å–超出其æƒé™èŒƒå›´çš„æ•°æ®ã€‚由于攻击者å¯ä»¥åˆ©ç”¨è¯¥æ¼æ´žåœ¨æœªç»ç”¨æˆ·æ˜Žç¡®è®¸å¯çš„情况下获å–æ•æ„Ÿæ•°æ®ï¼Œå› æ¤æˆ‘们将该æ¼æ´žçš„严é‡ç¨‹åº¦è¯„为“高â€ã€‚ </p> <table> @@ -1211,12 +1228,12 @@ MediaTek 视频驱动程åºä¸çš„ä¿¡æ¯æŠ«éœ²æ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用获å </tr> </tbody></table> <p> -* æè½½ Android 7.0（或更高版本）且已安装所有å¯ç”¨æ›´æ–°çš„å—支æŒçš„ Google 设备ä¸å—æ¤æ¼æ´žçš„å½±å“。 +*æè½½ Android 7.0（或更高版本）且已安装所有å¯ç”¨æ›´æ–°çš„å—æ”¯æŒ Google 设备ä¸å—æ¤æ¼æ´žçš„å½±å“。 </p> <h3 id="id-in-nvidia-video-driver">NVIDIA 视频驱动程åºä¸çš„ä¿¡æ¯æŠ«éœ²æ¼æ´ž</h3> <p> -NVIDIA 视频驱动程åºä¸çš„ä¿¡æ¯æŠ«éœ²æ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用获å–超出其æƒé™èŒƒå›´çš„æ•°æ®ã€‚由于攻击者å¯ä»¥åˆ©ç”¨è¯¥æ¼æ´žåœ¨æœªç»ç”¨æˆ·æ˜Žç¡®è®¸å¯çš„情况下获å–æ•æ„Ÿæ•°æ®ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“高â€ã€‚ +NVIDIA 视频驱动程åºä¸çš„ä¿¡æ¯æŠ«éœ²æ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用获å–超出其æƒé™èŒƒå›´çš„æ•°æ®ã€‚由于攻击者å¯ä»¥åˆ©ç”¨è¯¥æ¼æ´žåœ¨æœªç»ç”¨æˆ·æ˜Žç¡®è®¸å¯çš„情况下获å–æ•æ„Ÿæ•°æ®ï¼Œå› æ¤æˆ‘们将该æ¼æ´žçš„严é‡ç¨‹åº¦è¯„为“高â€ã€‚ </p> <table> @@ -1234,19 +1251,20 @@ NVIDIA 视频驱动程åºä¸çš„ä¿¡æ¯æŠ«éœ²æ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用获å–è </tr> <tr> <td>CVE-2016-8397</td> - <td>A-31385953*<br />N-CVE-2016-8397</td> + <td>A-31385953*<br /> +N-CVE-2016-8397</td> <td>高</td> <td>Nexus 9</td> <td>2016 å¹´ 9 月 8 æ—¥</td> </tr> </tbody></table> <p> -* 针对该问题的补ä¸ç¨‹åºæœªå…¬å¼€å‘布。<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上æ供的 Google 设备的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。 +*尚未公开å‘布针对该问题的补ä¸ç¨‹åºã€‚<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上针对 Google 设备æ供的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。 </p> <h3 id="dos-in-gps">GPS ä¸çš„æ‹’ç»æœåŠ¡æ¼æ´ž</h3> <p> -Qualcomm GPS 组件ä¸çš„æ‹’ç»æœåŠ¡æ¼æ´žå¯è®©è¿œç¨‹æ”»å‡»è€…挂起或é‡å¯è®¾å¤‡ã€‚由于攻击者å¯ä»¥åˆ©ç”¨è¯¥æ¼æ´žè¿œç¨‹å‘起暂时拒ç»æœåŠ¡æ”»å‡»ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“高â€ã€‚ +Qualcomm GPS 组件ä¸çš„æ‹’ç»æœåŠ¡æ¼æ´žå¯è®©è¿œç¨‹æ”»å‡»è€…挂起或é‡æ–°å¯åŠ¨è®¾å¤‡ã€‚由于攻击者å¯ä»¥åˆ©ç”¨è¯¥æ¼æ´žè¿œç¨‹å‘起暂时拒ç»æœåŠ¡æ”»å‡»ï¼Œå› æ¤æˆ‘们将该æ¼æ´žçš„严é‡ç¨‹åº¦è¯„为“高â€ã€‚ </p> <table> @@ -1271,12 +1289,12 @@ Qualcomm GPS 组件ä¸çš„æ‹’ç»æœåŠ¡æ¼æ´žå¯è®©è¿œç¨‹æ”»å‡»è€…挂起或é‡å¯è </tr> </tbody></table> <p> -* 针对该问题的补ä¸ç¨‹åºæœªå…¬å¼€å‘布。<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上æ供的 Google 设备的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。 +*尚未公开å‘布针对该问题的补ä¸ç¨‹åºã€‚<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上针对 Google 设备æ供的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。 </p> -<h3 id="dos-in-nvidia-camera-driver">NVIDIA 相机驱动程åºä¸çš„æ‹’ç»æœåŠ¡æ¼æ´ž</h3> +<h3 id="dos-in-nvidia-camera-driver">NVIDIA æ‘„åƒå¤´é©±åŠ¨ç¨‹åºä¸çš„æ‹’ç»æœåŠ¡æ¼æ´ž</h3> <p> -NVIDIA 相机驱动程åºä¸çš„æ‹’ç»æœåŠ¡æ¼æ´žå¯è®©æ”»å‡»è€…在本地å‘起永久拒ç»æœåŠ¡æ”»å‡»ï¼Œè€Œç”¨æˆ·å¯èƒ½éœ€è¦é€šè¿‡é‡å†™æ“作系统æ¥ä¿®å¤è®¾å¤‡ã€‚由于攻击者å¯ä»¥åˆ©ç”¨è¯¥æ¼æ´žåœ¨æœ¬åœ°å‘起永久拒ç»æœåŠ¡æ”»å‡»ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“高â€ã€‚ +NVIDIA æ‘„åƒå¤´é©±åŠ¨ç¨‹åºä¸çš„æ‹’ç»æœåŠ¡æ¼æ´žå¯è®©æ”»å‡»è€…在本地å‘起永久拒ç»æœåŠ¡æ”»å‡»ï¼Œè€Œç”¨æˆ·å¯èƒ½éœ€è¦é€šè¿‡é‡å†™æ“作系统æ¥ä¿®å¤è®¾å¤‡ã€‚由于攻击者å¯ä»¥åˆ©ç”¨è¯¥æ¼æ´žåœ¨æœ¬åœ°å‘起永久拒ç»æœåŠ¡æ”»å‡»ï¼Œå› æ¤æˆ‘们将该æ¼æ´žçš„严é‡ç¨‹åº¦è¯„为“高â€ã€‚ </p> <table> @@ -1294,19 +1312,20 @@ NVIDIA 相机驱动程åºä¸çš„æ‹’ç»æœåŠ¡æ¼æ´žå¯è®©æ”»å‡»è€…在本地å‘èµ·æ </tr> <tr> <td>CVE-2016-8395</td> - <td>A-31403040*<br />N-CVE-2016-8395</td> + <td>A-31403040* + <br />N-CVE-2016-8395</td> <td>高</td> <td>Pixel C</td> <td>2016 å¹´ 9 月 9 æ—¥</td> </tr> </tbody></table> <p> -* 针对该问题的补ä¸ç¨‹åºæœªå…¬å¼€å‘布。<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上æ供的 Google 设备的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。 +*尚未公开å‘布针对该问题的补ä¸ç¨‹åºã€‚<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上针对 Google 设备æ供的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。 </p> <h3 id="eop-in-kernel-networking-subsystem">å†…æ ¸ç½‘ç»œå系统ä¸çš„ææƒæ¼æ´ž</h3> <p> -å†…æ ¸ç½‘ç»œå系统ä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡å†…æ ¸æ‰§è¡Œä»»æ„代ç 。由于该æ¼æ´žéœ€è¦å…ˆç ´å特许进程，而且当å‰ç¼–译器优化功能é™åˆ¶è®¿é—®æœ‰æ¼æ´žçš„代ç ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“ä¸â€ã€‚ +å†…æ ¸ç½‘ç»œå系统ä¸çš„ææƒæ¼æ´žå¯è®©æœ¬åœ°æ¶æ„åº”ç”¨é€šè¿‡å†…æ ¸æ‰§è¡Œä»»æ„代ç 。由于æ¶æ„应用在利用该æ¼æ´žæ—¶éœ€è¦å…ˆç ´å特æƒè¿›ç¨‹ï¼Œè€Œå½“å‰ç¼–译器优化功能é™åˆ¶è®¿é—®æ˜“å—攻击的代ç ï¼Œå› æ¤æˆ‘们将该æ¼æ´žçš„严é‡ç¨‹åº¦è¯„为“ä¸â€ã€‚ </p> <table> @@ -1331,12 +1350,12 @@ NVIDIA 相机驱动程åºä¸çš„æ‹’ç»æœåŠ¡æ¼æ´žå¯è®©æ”»å‡»è€…在本地å‘èµ·æ </tr> </tbody></table> <p> -* 针对该问题的补ä¸ç¨‹åºæœªå…¬å¼€å‘布。<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上æ供的 Google 设备的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。 +*尚未公开å‘布针对该问题的补ä¸ç¨‹åºã€‚<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上针对 Google 设备æ供的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。 </p> <h3 id="id-in-qualcomm-components">Qualcomm 组件ä¸çš„ä¿¡æ¯æŠ«éœ²æ¼æ´ž</h3> <p> -Qualcomm 组件（包括相机驱动程åºå’Œè§†é¢‘驱动程åºï¼‰ä¸çš„ä¿¡æ¯æŠ«éœ²æ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用获å–超出其æƒé™èŒƒå›´çš„æ•°æ®ã€‚由于该æ¼æ´žéœ€è¦å…ˆç ´åç‰¹è®¸è¿›ç¨‹ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“ä¸â€ã€‚ +Qualcomm 组件（包括摄åƒå¤´é©±åŠ¨ç¨‹åºå’Œè§†é¢‘驱动程åºï¼‰ä¸çš„ä¿¡æ¯æŠ«éœ²æ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用获å–超出其æƒé™èŒƒå›´çš„æ•°æ®ã€‚由于æ¶æ„应用在利用该æ¼æ´žæ—¶éœ€è¦å…ˆç ´å特æƒè¿›ç¨‹ï¼Œå› æ¤æˆ‘们将该æ¼æ´žçš„严é‡ç¨‹åº¦è¯„为“ä¸â€ã€‚ </p> <table> @@ -1355,7 +1374,8 @@ Qualcomm 组件（包括相机驱动程åºå’Œè§†é¢‘驱动程åºï¼‰ä¸çš„ä¿¡æ¯æŠ <tr> <td>CVE-2016-6756</td> <td>A-29464815<br /> - <a href="https://source.codeaurora.org/quic/la//kernel/msm-3.10/commit/?id=f91d28dcba304c9f3af35b5bebaa26233c8c13a5">QC-CR#1042068</a> [<a href="https://source.codeaurora.org/quic/la/kernel/msm-3.18/commit/?id=3a214ef870dc97437c7de79a1507dfe5079dce88">2</a>]</td> + <a href="https://source.codeaurora.org/quic/la//kernel/msm-3.10/commit/?id=f91d28dcba304c9f3af35b5bebaa26233c8c13a5">QC-CR#1042068</a> + [<a href="https://source.codeaurora.org/quic/la/kernel/msm-3.18/commit/?id=3a214ef870dc97437c7de79a1507dfe5079dce88">2</a>]</td> <td>ä¸</td> <td>Nexus 5Xã€Nexus 6ã€Nexus 6Pã€Android Oneã€Pixelã€Pixel XL</td> <td>2016 å¹´ 6 月 17 æ—¥</td> @@ -1363,7 +1383,8 @@ Qualcomm 组件（包括相机驱动程åºå’Œè§†é¢‘驱动程åºï¼‰ä¸çš„ä¿¡æ¯æŠ <tr> <td>CVE-2016-6757</td> <td>A-30148242<br /> - <a href="https://source.codeaurora.org/quic/la/kernel/msm-3.10/commit/?id=cd99d3bbdb16899a425716e672485e0cdc283245">QC-CR#1052821</a></td> + <a href="https://source.codeaurora.org/quic/la/kernel/msm-3.10/commit/?id=cd99d3bbdb16899a425716e672485e0cdc283245"> +QC-CR#1052821</a></td> <td>ä¸</td> <td>Nexus 5Xã€Nexus 6ã€Nexus 6Pã€Pixelã€Pixel XL</td> <td>2016 å¹´ 7 月 13 æ—¥</td> @@ -1372,7 +1393,7 @@ Qualcomm 组件（包括相机驱动程åºå’Œè§†é¢‘驱动程åºï¼‰ä¸çš„ä¿¡æ¯æŠ <h3 id="id-in-nvidia-librm-library">NVIDIA librm 库ä¸çš„ä¿¡æ¯æŠ«éœ²æ¼æ´ž</h3> <p> -NVIDIA librm 库 (libnvrm) ä¸çš„ä¿¡æ¯æŠ«éœ²æ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用获å–超出其æƒé™èŒƒå›´çš„æ•°æ®ã€‚由于攻击者å¯ä»¥åˆ©ç”¨è¯¥æ¼æ´žåœ¨æœªç»è®¸å¯çš„情况下获å–æ•æ„Ÿæ•°æ®ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“ä¸â€ã€‚ +NVIDIA librm 库 (libnvrm) ä¸çš„ä¿¡æ¯æŠ«éœ²æ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用获å–超出其æƒé™èŒƒå›´çš„æ•°æ®ã€‚由于攻击者å¯ä»¥åˆ©ç”¨è¯¥æ¼æ´žåœ¨æœªç»è®¸å¯çš„情况下获å–æ•æ„Ÿæ•°æ®ï¼Œå› æ¤æˆ‘们将该æ¼æ´žçš„严é‡ç¨‹åº¦è¯„为“ä¸â€ã€‚ </p> <table> @@ -1390,19 +1411,20 @@ NVIDIA librm 库 (libnvrm) ä¸çš„ä¿¡æ¯æŠ«éœ²æ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用获å </tr> <tr> <td>CVE-2016-8400</td> - <td>A-31251599*<br />N-CVE-2016-8400</td> + <td>A-31251599* + <br />N-CVE-2016-8400</td> <td>ä¸</td> <td>Pixel C</td> <td>2016 å¹´ 8 月 29 æ—¥</td> </tr> </tbody></table> <p> -* 针对该问题的补ä¸ç¨‹åºæœªå…¬å¼€å‘布。<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上æ供的 Google 设备的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。 +*尚未公开å‘布针对该问题的补ä¸ç¨‹åºã€‚<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上针对 Google 设备æ供的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。 </p> <h3 id="id-in-kernel-components">å†…æ ¸ç»„ä»¶ä¸çš„ä¿¡æ¯æŠ«éœ²æ¼æ´ž</h3> <p> -å†…æ ¸ç»„ä»¶ï¼ˆåŒ…æ‹¬ ION å系统ã€Binderã€USB 驱动程åºå’Œç½‘络å系统）ä¸çš„ä¿¡æ¯æŠ«éœ²æ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用获å–超出其æƒé™èŒƒå›´çš„æ•°æ®ã€‚由于该æ¼æ´žéœ€è¦å…ˆç ´åç‰¹è®¸è¿›ç¨‹ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“ä¸â€ã€‚ +å†…æ ¸ç»„ä»¶ï¼ˆåŒ…æ‹¬ ION å系统ã€Binderã€USB 驱动程åºå’Œç½‘络å系统）ä¸çš„ä¿¡æ¯æŠ«éœ²æ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用获å–超出其æƒé™èŒƒå›´çš„æ•°æ®ã€‚由于æ¶æ„应用在利用该æ¼æ´žæ—¶éœ€è¦å…ˆç ´å特æƒè¿›ç¨‹ï¼Œå› æ¤æˆ‘们将该æ¼æ´žçš„严é‡ç¨‹åº¦è¯„为“ä¸â€ã€‚ </p> <table> @@ -1469,12 +1491,12 @@ NVIDIA librm 库 (libnvrm) ä¸çš„ä¿¡æ¯æŠ«éœ²æ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用获å </tr> </tbody></table> <p> -* 针对该问题的补ä¸ç¨‹åºæœªå…¬å¼€å‘布。<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上æ供的 Google 设备的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。 +*尚未公开å‘布针对该问题的补ä¸ç¨‹åºã€‚<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上针对 Google 设备æ供的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。 </p> <h3 id="id-in-nvidia-video-driver-2">NVIDIA 视频驱动程åºä¸çš„ä¿¡æ¯æŠ«éœ²æ¼æ´ž</h3> <p> -NVIDIA 视频驱动程åºä¸çš„ä¿¡æ¯æŠ«éœ²æ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用获å–超出其æƒé™èŒƒå›´çš„æ•°æ®ã€‚由于该æ¼æ´žéœ€è¦å…ˆç ´åç‰¹è®¸è¿›ç¨‹ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“ä¸â€ã€‚ +NVIDIA 视频驱动程åºä¸çš„ä¿¡æ¯æŠ«éœ²æ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用获å–超出其æƒé™èŒƒå›´çš„æ•°æ®ã€‚由于æ¶æ„应用在利用该æ¼æ´žæ—¶éœ€è¦å…ˆç ´å特æƒè¿›ç¨‹ï¼Œå› æ¤æˆ‘们将该æ¼æ´žçš„严é‡ç¨‹åº¦è¯„为“ä¸â€ã€‚ </p> <table> @@ -1492,26 +1514,28 @@ NVIDIA 视频驱动程åºä¸çš„ä¿¡æ¯æŠ«éœ²æ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用获å–è </tr> <tr> <td>CVE-2016-8408</td> - <td>A-31496571*<br />N-CVE-2016-8408</td> + <td>A-31496571* + <br />N-CVE-2016-8408</td> <td>ä¸</td> <td>Nexus 9</td> <td>2016 å¹´ 9 月 13 æ—¥</td> </tr> <tr> <td>CVE-2016-8409</td> - <td>A-31495687*<br />N-CVE-2016-8409</td> + <td>A-31495687* + <br />N-CVE-2016-8409</td> <td>ä¸</td> <td>Nexus 9</td> <td>2016 å¹´ 9 月 13 æ—¥</td> </tr> </tbody></table> <p> -* 针对该问题的补ä¸ç¨‹åºæœªå…¬å¼€å‘布。<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上æ供的 Google 设备的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。 +*尚未公开å‘布针对该问题的补ä¸ç¨‹åºã€‚<a href="https://developers.google.com/android/nexus/drivers">Google Developers 网站</a>上针对 Google 设备æ供的最新二进制驱动程åºä¸åŒ…å«ç›¸åº”更新。 </p> <h3 id="id-in-qualcomm-sound-driver">Qualcomm 声音驱动程åºä¸çš„ä¿¡æ¯æŠ«éœ²æ¼æ´ž</h3> <p> -Qualcomm 声音驱动程åºä¸çš„ä¿¡æ¯æŠ«éœ²æ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用获å–超出其æƒé™èŒƒå›´çš„æ•°æ®ã€‚由于该æ¼æ´žéœ€è¦å…ˆç ´åç‰¹è®¸è¿›ç¨‹ï¼Œå› æ¤æˆ‘们将其严é‡ç¨‹åº¦è¯„为“ä¸â€ã€‚ +Qualcomm 声音驱动程åºä¸çš„ä¿¡æ¯æŠ«éœ²æ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用获å–超出其æƒé™èŒƒå›´çš„æ•°æ®ã€‚由于æ¶æ„应用在利用该æ¼æ´žæ—¶éœ€è¦å…ˆç ´å特æƒè¿›ç¨‹ï¼Œå› æ¤æˆ‘们将该æ¼æ´žçš„严é‡ç¨‹åº¦è¯„为“ä¸â€ã€‚ </p> <table> @@ -1530,7 +1554,8 @@ Qualcomm 声音驱动程åºä¸çš„ä¿¡æ¯æŠ«éœ²æ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用获å <tr> <td>CVE-2016-8410</td> <td>A-31498403<br /> - <a href="https://source.codeaurora.org/quic/la//kernel/msm-3.10/commit/?h=e2bbf665187a1f0a1248e4a088823cb182153ba9">QC-CR#987010</a></td> + <a href="https://source.codeaurora.org/quic/la//kernel/msm-3.10/commit/?h=e2bbf665187a1f0a1248e4a088823cb182153ba9"> +QC-CR#987010</a></td> <td>ä¸</td> <td>Nexus 5Xã€Nexus 6ã€Nexus 6Pã€Android One</td> <td>Google 内部</td> @@ -1539,14 +1564,14 @@ Qualcomm 声音驱动程åºä¸çš„ä¿¡æ¯æŠ«éœ²æ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用获å <h2 id="common-questions-and-answers">常è§é—®é¢˜å’Œè§£ç”</h2> <p> -这一部分针对阅读本公告åŽå¯èƒ½äº§ç”Ÿçš„常è§é—®é¢˜æ供了相应的解ç”。 +这一部分解ç”了用户阅读本公告åŽå¯èƒ½ä¼šæ出的常è§é—®é¢˜ã€‚ </p> <p> <strong>1. 如何确定我的设备是å¦å·²æ›´æ–°åˆ°è§£å†³äº†è¿™äº›é—®é¢˜çš„版本？ </strong> </p> <p> -è¦äº†è§£å¦‚何检查设备的安全补ä¸ç¨‹åºçº§åˆ«ï¼Œè¯·é˜…读 <a href="https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices">Pixel å’Œ Nexus 更新时间表</a>ä¸çš„说明。 +è¦äº†è§£å¦‚何查看设备的安全补ä¸ç¨‹åºçº§åˆ«ï¼Œè¯·é˜…读 <a href="https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices">Pixel å’Œ Nexus 更新时间表</a>ä¸çš„说明。 </p> <ul> <li>2016-12-01（或之åŽï¼‰çš„安全补ä¸ç¨‹åºçº§åˆ«è§£å†³äº†ä¸Ž 2016-12-01 安全补ä¸ç¨‹åºçº§åˆ«ç›¸å…³çš„所有问题。</li> @@ -1559,7 +1584,7 @@ Qualcomm 声音驱动程åºä¸çš„ä¿¡æ¯æŠ«éœ²æ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用获å <li>[ro.build.version.security_patch]:[2016-12-05]</li> </ul> <p> -<strong>2. 为何本公告会有 2 个安全补ä¸ç¨‹åºçº§åˆ«ï¼Ÿ</strong> +<strong>2. 为何本公告有 2 个安全补ä¸ç¨‹åºçº§åˆ«ï¼Ÿ</strong> </p> <p> 本公告有 2 个安全补ä¸ç¨‹åºçº§åˆ«ï¼Œç›®çš„是让 Android åˆä½œä¼™ä¼´èƒ½å¤Ÿçµæ´»åœ°ã€æ›´å¿«é€Ÿåœ°ä¿®å¤æ‰€æœ‰ Android 设备上类似的一系列æ¼æ´žã€‚我们建议 Android åˆä½œä¼™ä¼´ä¿®å¤æœ¬å…¬å‘Šä¸çš„所有问题并使用最新的安全补ä¸ç¨‹åºçº§åˆ«ã€‚ @@ -1578,9 +1603,9 @@ Qualcomm 声音驱动程åºä¸çš„ä¿¡æ¯æŠ«éœ²æ¼æ´žå¯è®©æœ¬åœ°æ¶æ„应用获å 在 <a href="#2016-12-01-details">2016-12-01</a> å’Œ <a href="#2016-12-05-details">2016-12-05</a> 安全æ¼æ´žè¯¦æƒ…部分，æ¯ä¸ªè¡¨ä¸å‡åŒ…å«â€œå·²æ›´æ–°çš„ Google 设备â€åˆ—，其ä¸åˆ—出了已针对æ¯ä¸ªé—®é¢˜è¿›è¡Œæ›´æ–°çš„å—å½±å“ Google 设备。<em></em>æ¤åˆ—æœ‰ä»¥ä¸‹å‡ ç§æƒ…形： </p> <ul> - <li><strong>所有 Google 设备</strong>：如果æŸä¸ªé—®é¢˜ä¼šå½±å“所有 Nexus å’Œ Pixel 设备，则相应表的“已更新的 Google 设备â€åˆ—ä¸ä¼šæ˜¾ç¤ºâ€œæ‰€æœ‰â€ã€‚<em></em>“所有â€åŒ…å«ä¸‹åˆ—<a href="https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices">å—支æŒçš„设备</a>：Nexus 5ã€Nexus 5Xã€Nexus 6ã€Nexus 6Pã€Nexus 9ã€Android Oneã€Nexus Playerã€Pixel Cã€Pixel å’Œ Pixel XL。</li> - <li><strong>部分 Google 设备</strong>：如果æŸä¸ªé—®é¢˜ä»…会影å“部分 Google 设备，则“已更新的 Google 设备â€åˆ—ä¸ä¼šåˆ—出å—å½±å“çš„ Google 设备。<em></em></li> - <li><strong>æ— Google 设备</strong>：如果æŸä¸ªé—®é¢˜ä¸ä¼šå½±å“任何è¿è¡Œ Android 7.0 çš„ Google 设备，则相应表的“已更新的 Google 设备â€åˆ—ä¸ä¼šæ˜¾ç¤ºâ€œæ— â€ã€‚<em></em></li> + <li><strong>所有 Google 设备</strong>：如果问题会影å“所有 Nexus å’Œ Pixel 设备，则相应表的“已更新的 Google 设备â€åˆ—ä¸ä¼šæ˜¾ç¤ºâ€œæ‰€æœ‰â€ã€‚<em></em>“所有â€åŒ…å«ä¸‹åˆ—<a href="https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices">å—支æŒçš„设备</a>：Nexus 5ã€Nexus 5Xã€Nexus 6ã€Nexus 6Pã€Nexus 9ã€Android Oneã€Nexus Playerã€Pixel Cã€Pixel å’Œ Pixel XL。</li> + <li><strong>部分 Google 设备</strong>：如果问题仅会影å“部分 Google 设备，则“已更新的 Google 设备â€åˆ—ä¸ä¼šåˆ—出å—å½±å“çš„ Google 设备。<em></em></li> + <li><strong>æ— Google 设备</strong>：如果问题ä¸ä¼šå½±å“任何è¿è¡Œ Android 7.0 çš„ Google 设备，则相应表的“已更新的 Google 设备â€åˆ—ä¸ä¼šæ˜¾ç¤ºâ€œæ— â€ã€‚<em></em></li> </ul> <p> <strong>4.“å‚考信æ¯â€åˆ—ä¸çš„æ¡ç›®å¯¹åº”的是什么内容？</strong> diff --git a/zh-cn/security/encryption/file-based.html b/zh-cn/security/encryption/file-based.html index db0b51a2..13e06839 100644 --- a/zh-cn/security/encryption/file-based.html +++ b/zh-cn/security/encryption/file-based.html @@ -90,15 +90,18 @@ Android æä¾›äº†æ–‡ä»¶çº§åŠ å¯†çš„å‚è€ƒå®žçŽ°ï¼Œå…¶ä¸ vold (<a href="https:// </tr> <tr> <td>Android Common</td> - <td><strong>kernel/common</strong> android-3.10.y (<a href="https://android.googlesource.com/kernel/common/+/android-3.10.y">git</a>)</td> + <td><strong>kernel/common</strong> android-3.10.y (<a href="https://android.googlesource.com/kernel/common/+/android-3.10.y">git</a>) + </td> </tr> <tr> <td>Nexus 5X (bullhead)</td> - <td><strong>kernel/msm</strong> android-msm-bullhead-3.10-n-preview-2 (<a href="https://android.googlesource.com/kernel/msm/+/android-msm-bullhead-3.10-n-preview-2">git</a>)</td> + <td><strong>kernel/msm</strong> android-msm-bullhead-3.10-n-preview-2 (<a href="https://android.googlesource.com/kernel/msm/+/android-msm-bullhead-3.10-n-preview-2">git</a>) + </td> </tr> <tr> <td>Nexus 6P (angler)</td> - <td><strong>kernel/msm</strong> android-msm-angler-3.10-n-preview-2 (<a href="https://android.googlesource.com/kernel/msm/+/android-msm-angler-3.10-n-preview-2">git</a>)</td> + <td><strong>kernel/msm</strong> android-msm-angler-3.10-n-preview-2 (<a href="https://android.googlesource.com/kernel/msm/+/android-msm-angler-3.10-n-preview-2">git</a>) + </td> </tr> </tbody></table> <p>请注æ„，以上æ¯ä¸ªå†…æ ¸éƒ½ä½¿ç”¨äº†åˆ° 3.10 çš„åå‘移æ¤ã€‚Linux 3.18 ä¸çš„ EXT4 å’Œ JBD2 驱动程åºå·²ç§»æ¤åˆ°åŸºäºŽ 3.10 çš„çŽ°æœ‰å†…æ ¸ä¸ã€‚ç”±äºŽå†…æ ¸å„个部分之间å˜åœ¨ä¾èµ–å…³ç³»ï¼Œå› æ¤è¿™ç§åå‘移æ¤ä¼šå¯¼è‡´ç³»ç»Ÿåœæ¢æ”¯æŒ Nexus 设备ä¸ä½¿ç”¨çš„一些功能。其ä¸åŒ…括：</p> @@ -117,7 +120,7 @@ Android æä¾›äº†æ–‡ä»¶çº§åŠ å¯†çš„å‚è€ƒå®žçŽ°ï¼Œå…¶ä¸ vold (<a href="https:// </p><p> 测试设备上的 FBE 实现情况时，å¯ä»¥æŒ‡å®šä»¥ä¸‹æ ‡è®°ï¼š<code>forcefdeorfbe="<path/to/metadata/partition>"</code> </p> -<p>æ¤æ ‡è®°ä¼šå°†è®¾å¤‡è®¾ä¸ºä½¿ç”¨ FDE，但å…许针对开å‘者转æ¢ä¸º FBE。默认情况下，æ¤æ ‡è®°çš„行为类似于 <code>forceencrypt</code>，会使设备进入 FDE 模å¼ã€‚ä¸è¿‡ï¼Œå®ƒå°†æ供一个调试选项，以便在开å‘者预览ä¸å…许将设备切æ¢åˆ° FBE 模å¼ã€‚å¦å¤–，还å¯ä»¥ä½¿ç”¨ä»¥ä¸‹å‘½ä»¤åœ¨ fastboot ä¸å¯ç”¨ FBE：</p> +<p>æ¤æ ‡è®°ä¼šå°†è®¾å¤‡è®¾ä¸ºä½¿ç”¨ FDE，但å…许针对开å‘者转æ¢ä¸º FBE。默认情况下，æ¤æ ‡è®°çš„行为类似于 <code>forceencrypt</code>，会使设备进入 FDE 模å¼ã€‚ä¸è¿‡ï¼Œå®ƒå°†æ供一个调试选项，以便在开å‘者预览ä¸å…许将设备切æ¢åˆ° FBE 模å¼ã€‚å¦å¤–，还å¯ä»¥ä½¿ç”¨ä»¥ä¸‹å‘½ä»¤åœ¨ fastboot ä¸å¯ç”¨ FBE：</p> <p> </p><pre class="devsite-terminal devsite-click-to-copy"> fastboot --wipe-and-use-fbe diff --git a/zh-cn/security/overview/acknowledgements.html b/zh-cn/security/overview/acknowledgements.html index 3094e789..c6a10575 100644 --- a/zh-cn/security/overview/acknowledgements.html +++ b/zh-cn/security/overview/acknowledgements.html @@ -25,6 +25,89 @@ <h2 id="2018">2018</h2> <p>2018 年的安全致谢信æ¯å°†æŒ‰æœˆåˆ—å‡ºã€‚è¿‡åŽ»å‡ å¹´çš„è‡´è°¢ä¿¡æ¯æ˜¯åˆ—在一起的。</p> +<h4 id="mar-2018">3 月</h4> + + <table> + <colgroup><col width="70%" /> + <col width="30%" /> + </colgroup><tbody><tr> + <th>ç ”ç©¶äººå‘˜</th> + <th>CVE</th> + </tr> + <tr> + <td>Google çš„ Billy Lau</td> + <td>CVE-2017-14879</td> + </tr> + <tr> + <td>Copperhead Security çš„ Daniel Micay</td> + <td>CVE-2017-13265</td> + </tr> + <tr> + <td><a href="mailto:shaodacheng2016@gmail.com">Dacheng Shao</a> 和周明建</td> + <td>CVE-2017-6288</td> + </tr> + <tr> + <td>奇虎 360 科技有é™å…¬å¸ Alpha 团队的 Elphet 和龚广</td> + <td>CVE-2017-13254</td> + </tr> + <tr> + <td>Shellphish Grill 团队的 Jake Corina</td> + <td>CVE-2018-3560</td> + </tr> + <tr> + <td>奇虎 360 科技有é™å…¬å¸ Alpha 团队的 Jianjun Dai (<a href="https://twitter.com/jioun_dai">@Jioun_dai</a>) 和龚广</td> + <td>CVE-2017-13266ã€CVE-2017-13256ã€CVE-2017-13255</td> + </tr> + <tr> + <td>Julian Rauchberger</td> + <td>CVE-2017-13258</td> + </tr> + <tr> + <td><a href="http://c0reteam.org">C0RE 团队</a>çš„ Hongli Han (<a href="https://twitter.com/hexb1n">@HexB1n</a>)ã€<a href="mailto:shaodacheng2016@gmail.com">Dacheng Shao</a> 和周明建 (<a href="https://twitter.com/Mingjian_Zhou">@Mingjian_Zhou</a>)</td> + <td>CVE-2017-6287</td> + </tr> + <tr> + <td><a href="http://c0reteam.org">C0RE 团队</a>çš„ Hongli Han (<a href="https://twitter.com/HexB1n">@HexB1n</a>) 和周明建 (<a href="https://twitter.com/Mingjian_Zhou">@Mingjian_Zhou</a>)</td> + <td>CVE-2017-6286ã€CVE-2017-6285ã€CVE-2017-6281</td> + </tr> + <tr> + <td>百度安全实验室的ä¸é¹é£žã€åŒ…沉浮和韦韬</td> + <td>CVE-2017-13262ã€CVE-2017-13261ã€CVE-2017-13260ã€CVE-2017-11029ã€CVE-2017-15814</td> + </tr> + <tr> + <td>腾讯安全平å°éƒ¨é—¨çš„ Peter Pi</td> + <td>CVE-2017-13269</td> + </tr> + <tr> + <td>Zimperium zLabs 团队的 Tamir Zahavi-Brunner (<a href="https://twitter.com/tamir_zb">@tamir_zb</a>)</td> + <td>CVE-2017-13253</td> + </tr> + <tr> + <td>Vasily Vasiliev</td> + <td>CVE-2017-13249ã€CVE-2017-13248ã€CVE-2017-13264</td> + </tr> + <tr> + <td>èš‚èšé‡‘æœå·´æ–¯å…‰å¹´å®‰å…¨å®žéªŒå®¤çš„<a href="http://www.weibo.com/wishlinux">å´æ½æµ </a> (<a href=" https://twitter.com/wish_wu">@wish_wu</a>)</td> + <td>CVE-2017-13259ã€CVE-2017-13272</td> + </tr> + <tr> + <td>èš‚èšé‡‘æœå·´æ–¯å…‰å¹´å®‰å…¨å®žéªŒå®¤çš„ Yaoguang Chen</td> + <td>CVE-2017-13257ã€CVE-2017-13268</td> + </tr> + <tr> + <td>奇虎 360 科技有é™å…¬å¸ IceSword 实验室的 Yonggang Guo (<a href="https://twitter.com/guoygang">@guoygang</a>)</td> + <td>CVE-2017-13271</td> + </tr> + <tr> + <td>腾讯安全平å°éƒ¨é—¨çš„ ZhangBo</td> + <td>CVE-2017-18069</td> + </tr> + <tr> + <td>奇虎 360 科技有é™å…¬å¸æˆéƒ½å®‰å…¨å“应ä¸å¿ƒçš„ <a href="http://weibo.com/ele7enxxh">Zinuo Han</a></td> + <td>CVE-2017-13252ã€CVE-2017-13251ã€CVE-2018-3561</td> + </tr> +</tbody></table> + <h4 id="feb-2018">2 月</h4> <table> @@ -71,13 +154,13 @@ </td> </tr> <tr> - <td><a href="http://c0reteam.org">C0RE 团队</a>çš„ Hongli Han (<a href="https://twitter.com/HexB1n">@HexB1n</a>)ã€<a href="mailto:shaodacheng2016@gmail.com">Dacheng Shao</a> å’Œ Mingjian Zhou (<a href="https://twitter.com/Mingjian_Zhou">@Mingjian_Zhou</a>) + <td><a href="http://c0reteam.org">C0RE 团队</a>çš„ Hongli Han (<a href="https://twitter.com/HexB1n">@HexB1n</a>)ã€<a href="mailto:shaodacheng2016@gmail.com">Dacheng Shao</a> 和周明建 (<a href="https://twitter.com/Mingjian_Zhou">@Mingjian_Zhou</a>) </td> <td>CVE-2017-6258 </td> </tr> <tr> - <td><a href="http://c0reteam.org">CORE 团队</a>çš„ Hongli Han (<a href="https://twitter.com/HexB1n">@HexB1n</a>)ã€Mingjian Zhou (<a href="https://twitter.com/Mingjian_Zhou">@Mingjian_Zhou</a>) + <td><a href="http://c0reteam.org">CORE 团队</a>çš„ Hongli Han (<a href="https://twitter.com/HexB1n">@HexB1n</a>)ã€å‘¨æ˜Žå»º (<a href="https://twitter.com/Mingjian_Zhou">@Mingjian_Zhou</a>) </td> <td>CVE-2017-17767ã€CVE-2017-6279 </td> @@ -172,7 +255,7 @@ <td>CVE-2017-13214</td> </tr> <tr> - <td><a href="http://c0reteam.org">C0RE 团队</a>çš„ <a href="mailto:zc1991@mail.ustc.edu.cn">Chi Zhang</a> å’Œ Mingjian Zhou (<a href="https://twitter.com/Mingjian_Zhou">@Mingjian_Zhou</a>)</td> + <td><a href="http://c0reteam.org">C0RE 团队</a>çš„ <a href="mailto:zc1991@mail.ustc.edu.cn">Chi Zhang</a> 和周明建 (<a href="https://twitter.com/Mingjian_Zhou">@Mingjian_Zhou</a>)</td> <td>CVE-2017-13178ã€CVE-2017-13179</td> </tr> <tr> @@ -184,11 +267,11 @@ <td>CVE-2017-13198</td> </tr> <tr> - <td><a href="http://c0reteam.org">C0RE 团队</a>çš„ Hongli Han (<a href="https://twitter.com/HexB1n">@HexB1n</a>) å’Œ Mingjian Zhou (<a href="https://twitter.com/Mingjian_Zhou">@Mingjian_Zhou</a>)</td> + <td><a href="http://c0reteam.org">C0RE 团队</a>çš„ Hongli Han (<a href="https://twitter.com/HexB1n">@HexB1n</a>) 和周明建 (<a href="https://twitter.com/Mingjian_Zhou">@Mingjian_Zhou</a>)</td> <td>CVE-2017-13183ã€CVE-2017-13180</td> </tr> <tr> - <td><a href="http://c0reteam.org">C0RE 团队</a>çš„ Hongli Han (<a href="https://twitter.com/HexB1n">@HexB1n</a>)ã€<a href="mailto:shaodacheng2016@gmail.com">Dacheng Shao</a> å’Œ Mingjian Zhou (<a href="https://twitter.com/Mingjian_Zhou">@Mingjian_Zhou</a>)</td> + <td><a href="http://c0reteam.org">C0RE 团队</a>çš„ Hongli Han (<a href="https://twitter.com/HexB1n">@HexB1n</a>)ã€<a href="mailto:shaodacheng2016@gmail.com">Dacheng Shao</a> 和周明建 (<a href="https://twitter.com/Mingjian_Zhou">@Mingjian_Zhou</a>)</td> <td>CVE-2017-13194</td> </tr> <tr> @@ -1494,8 +1577,7 @@ William Roberts</a> (<a href="mailto:bill.c.roberts@gmail.com">bill.c.roberts@gm <p>å°ç¬¬å®‰çº³å¤§å¦å¸ƒå¢æ˜Žé¡¿åˆ†æ ¡çš„ <a href="http://homes.soic.indiana.edu/luyixing">Luyi Xing</a> (<a href="mailto:xingluyi@gmail.com">xingluyi@gmail.com</a>)</p> <p><a href="https://isecpartners.com/">iSEC Partners</a> çš„ <a href="https://lacklustre.net/">Mike Ryan</a> -<br />（<a href="https://twitter.com/mpeg4codec">@mpeg4codec</a>ã€<a href="mailto:mikeryan@isecpartners.com">mikeryan@isecpartners.com -</a>）</p> +<br />（<a href="https://twitter.com/mpeg4codec">@mpeg4codec</a>ã€<a href="mailto:mikeryan@isecpartners.com">mikeryan@isecpartners.com</a>）</p> <p><a href="http://illinois.edu/">伊利诺伊大å¦åŽ„巴纳-尚佩æ©åˆ†æ ¡</a>çš„ <a href="http://cryptoonline.com/">Muhammad Naveed</a> <br />(<a href="mailto:naveed2@illinois.edu">naveed2@illinois.edu</a>)</p> diff --git a/zh-cn/security/overview/updates-resources.html b/zh-cn/security/overview/updates-resources.html index 32653fbc..7ef59eb0 100644 --- a/zh-cn/security/overview/updates-resources.html +++ b/zh-cn/security/overview/updates-resources.html @@ -223,6 +223,7 @@ <h3 id="reports">报告</h3> <p>Android 安全团队有时会å‘布报告或白皮书。以下是一些最新å‘布的内容。</p> <ul> + <li><a href="/security/reports/Google_Android_Security_2017_Report_Final.pdf">Android 安全性 2017 年年度回顾报告</a></li> <li><a href="/security/reports/Google_Android_Security_2016_Report_Final.pdf">Android 安全性 2016 年年度回顾报告</a></li> <li><a href="/security/reports/Google_Android_Security_2015_Report_Final.pdf">Android 安全性 2015 年年度回顾报告</a></li> <li><a href="/security/reports/Google_Android_Security_2014_Report_Final.pdf">Android 安全性 2014 年年度回顾报告</a></li> diff --git a/zh-tw/security/bulletin/2015-08-01.html b/zh-tw/security/bulletin/2015-08-01.html index 734905d8..f95c10d3 100644 --- a/zh-tw/security/bulletin/2015-08-01.html +++ b/zh-tw/security/bulletin/2015-08-01.html @@ -130,18 +130,13 @@ <p>å—å½±éŸ¿çš„åŠŸèƒ½æ˜¯ä»¥æ‡‰ç”¨ç¨‹å¼ API å½¢å¼æ供使用，而多個應用程å¼éƒ½å…許é ç«¯å…§å®¹é€£åˆ°é€™é …åŠŸèƒ½ï¼Œå…¶ä¸æœ€å¸¸è¦‹çš„內容是多媒體訊æ¯å’Œç€è¦½å™¨ä¸æ’放的媒體。</p> -<p>由於這個å•é¡Œå¯èƒ½æœƒè®“é 端程å¼ç¢¼ç•¶åšç²å¾—授權的æœå‹™ä¾†åŸ·è¡Œï¼Œå› æ¤åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œæœ€é«˜ã€ã€‚儘管媒體伺æœå™¨ -會å—到 SELinux ä¿è·ï¼Œä½†å®ƒç¢ºå¯¦èƒ½å¤ å˜å–音訊和視訊串æµï¼Œ -以åŠåœ¨è¨±å¤šè£ç½®ä¸Šç²å¾—æŽˆæ¬Šçš„æ ¸å¿ƒé©…å‹•ç¨‹å¼è£ç½®ç¯€é»ž (這是 -第三方應用程å¼ä¸€èˆ¬ç„¡æ³•å˜å–的權é™)。</p> +<p>由於這個å•é¡Œå¯èƒ½æœƒè®“é 端程å¼ç¢¼ç•¶åšç²å¾—授權的æœå‹™ä¾†åŸ·è¡Œï¼Œå› æ¤åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œæœ€é«˜ã€ã€‚儘管媒體伺æœå™¨æœƒå—到 SELinux ä¿è·ï¼Œä½†å®ƒç¢ºå¯¦èƒ½å¤ å˜å–音訊和視訊串æµï¼Œä»¥åŠåœ¨è¨±å¤šè£ç½®ä¸Šç²å¾—æŽˆæ¬Šçš„æ ¸å¿ƒé©…å‹•ç¨‹å¼è£ç½®ç¯€é»ž (這是第三方應用程å¼ä¸€èˆ¬ç„¡æ³•å˜å–的權é™)。</p> -<p>請注æ„，ä¾æ“šèˆŠç‰ˆçš„åš´é‡ç¨‹åº¦è©•å®šè¦ç¯„ï¼Œé€™é …æ¼æ´žè¢«è©•å®šç‚º -「高ã€çš„影響程度，並已據æ¤å›žå ±çµ¦åˆä½œå¤¥ä¼´ã€‚但ä¾æ“š -我們 2015 å¹´ 6 月發佈的新版è¦ç¯„ï¼Œé€™é …æ¼æ´žå»å±¬æ–¼ã€Œæœ€é«˜ã€ç‰ç´šçš„å•é¡Œã€‚</p> +<p>請注æ„，ä¾æ“šèˆŠç‰ˆçš„åš´é‡ç¨‹åº¦è©•å®šè¦ç¯„ï¼Œé€™é …æ¼æ´žçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ï¼Œä¸¦å·²æ“šæ¤å›žå ±çµ¦åˆä½œå¤¥ä¼´ï¼Œä½†ä¾æ“šæˆ‘們 2015 å¹´ 6 月發佈的新版è¦ç¯„ï¼Œé€™é …æ¼æ´žå±¬æ–¼ã€Œæœ€é«˜ã€ç‰ç´šçš„å•é¡Œã€‚</p> <table> <tbody><tr> <th>CVE</th> - <th>錯誤 (附有 AOSP 連çµ)</th> + <th>錯誤 (附有 Android 開放原始碼計劃連çµ)</th> <th>åš´é‡ç¨‹åº¦</th> <th>å—影響的版本</th> </tr> @@ -164,15 +159,11 @@ 都å…許é ç«¯å…§å®¹é€£åˆ°é€™é …åŠŸèƒ½ï¼Œå…¶ä¸æœ€å¸¸è¦‹çš„內容是多媒體 訊æ¯å’Œç€è¦½å™¨ä¸æ’放的媒體。</p> -<p>由於這個å•é¡Œå¯èƒ½æœƒè®“é 端程å¼ç¢¼ç•¶åšç²å¾—授權的æœå‹™ä¾† -åŸ·è¡Œï¼Œå› æ¤è¢«è©•å®šç‚ºã€Œæœ€é«˜ã€çš„影響程度。儘管媒體伺æœå™¨ -會å—到 SELinux ä¿è·ï¼Œä½†å®ƒç¢ºå¯¦èƒ½å¤ å˜å–音訊和視訊串æµï¼Œ -以åŠåœ¨è¨±å¤šè£ç½®ä¸Šç²å¾—æŽˆæ¬Šçš„æ ¸å¿ƒé©…å‹•ç¨‹å¼è£ç½®ç¯€é»ž (這是 -第三方應用程å¼ä¸€èˆ¬ç„¡æ³•å˜å–的權é™)。請注æ„，ä¾æ“šèˆŠç‰ˆçš„åš´é‡ç¨‹åº¦è©•å®šè¦ç¯„ï¼Œé€™é …æ¼æ´žçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ï¼Œä¸¦å·²æ“šæ¤å›žå ±çµ¦åˆä½œå¤¥ä¼´ï¼Œä½†ä¾æ“šæˆ‘們 2015 å¹´ 6 月發佈的新版è¦ç¯„ï¼Œé€™é …æ¼æ´žå»å±¬æ–¼ã€Œæœ€é«˜ã€ç‰ç´šçš„å•é¡Œã€‚</p> +<p>由於這個å•é¡Œå¯èƒ½æœƒè®“é 端程å¼ç¢¼ç•¶åšç²å¾—授權的æœå‹™ä¾†åŸ·è¡Œï¼Œå› æ¤åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œæœ€é«˜ã€ã€‚儘管媒體伺æœå™¨æœƒå—到 SELinux ä¿è·ï¼Œä½†å®ƒç¢ºå¯¦èƒ½å¤ å˜å–音訊和視訊串æµï¼Œä»¥åŠåœ¨è¨±å¤šè£ç½®ä¸Šç²å¾—æŽˆæ¬Šçš„æ ¸å¿ƒé©…å‹•ç¨‹å¼è£ç½®ç¯€é»ž (這是第三方應用程å¼ä¸€èˆ¬ç„¡æ³•å˜å–的權é™)。請注æ„，ä¾æ“šèˆŠç‰ˆçš„åš´é‡ç¨‹åº¦è©•å®šè¦ç¯„ï¼Œé€™é …æ¼æ´žçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ï¼Œä¸¦å·²æ“šæ¤å›žå ±çµ¦åˆä½œå¤¥ä¼´ï¼Œä½†ä¾æ“šæˆ‘們 2015 å¹´ 6 月發佈的新版è¦ç¯„ï¼Œé€™é …æ¼æ´žå±¬æ–¼ã€Œæœ€é«˜ã€ç‰ç´šçš„å•é¡Œã€‚</p> <table> <tbody><tr> <th>CVE</th> - <th>錯誤 (附有 AOSP 連çµ)</th> + <th>錯誤 (附有 Android 開放原始碼計劃連çµ)</th> <th>åš´é‡ç¨‹åº¦</th> <th>å—影響的版本</th> </tr> @@ -195,15 +186,11 @@ 都å…許é ç«¯å…§å®¹é€£åˆ°é€™é …åŠŸèƒ½ï¼Œå…¶ä¸æœ€å¸¸è¦‹çš„內容是多媒體 訊æ¯å’Œç€è¦½å™¨ä¸æ’放的媒體。</p> -<p>由於這個å•é¡Œå¯èƒ½æœƒè®“é 端程å¼ç¢¼ç•¶åšç²å¾—授權的æœå‹™ä¾† -åŸ·è¡Œï¼Œå› æ¤è¢«è©•å®šç‚ºã€Œæœ€é«˜ã€çš„影響程度。儘管媒體伺æœå™¨ -會å—到 SELinux ä¿è·ï¼Œä½†å®ƒç¢ºå¯¦èƒ½å¤ å˜å–音訊和視訊串æµï¼Œ -以åŠåœ¨è¨±å¤šè£ç½®ä¸Šç²å¾—æŽˆæ¬Šçš„æ ¸å¿ƒé©…å‹•ç¨‹å¼è£ç½®ç¯€é»ž (這是 -第三方應用程å¼ä¸€èˆ¬ç„¡æ³•å˜å–的權é™)。請注æ„，ä¾æ“šèˆŠç‰ˆçš„åš´é‡ç¨‹åº¦è©•å®šè¦ç¯„ï¼Œé€™é …æ¼æ´žçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ï¼Œä¸¦å·²æ“šæ¤å›žå ±çµ¦åˆä½œå¤¥ä¼´ï¼Œä½†ä¾æ“šæˆ‘們 2015 å¹´ 6 月發佈的新版è¦ç¯„ï¼Œé€™é …æ¼æ´žå»å±¬æ–¼ã€Œæœ€é«˜ã€ç‰ç´šçš„å•é¡Œã€‚</p> +<p>由於這個å•é¡Œå¯èƒ½æœƒè®“é 端程å¼ç¢¼ç•¶åšç²å¾—授權的æœå‹™ä¾†åŸ·è¡Œï¼Œå› æ¤åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œæœ€é«˜ã€ã€‚儘管媒體伺æœå™¨æœƒå—到 SELinux ä¿è·ï¼Œä½†å®ƒç¢ºå¯¦èƒ½å¤ å˜å–音訊和視訊串æµï¼Œä»¥åŠåœ¨è¨±å¤šè£ç½®ä¸Šç²å¾—æŽˆæ¬Šçš„æ ¸å¿ƒé©…å‹•ç¨‹å¼è£ç½®ç¯€é»ž (這是第三方應用程å¼ä¸€èˆ¬ç„¡æ³•å˜å–的權é™)。請注æ„，ä¾æ“šèˆŠç‰ˆçš„åš´é‡ç¨‹åº¦è©•å®šè¦ç¯„ï¼Œé€™é …æ¼æ´žçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ï¼Œä¸¦å·²æ“šæ¤å›žå ±çµ¦åˆä½œå¤¥ä¼´ï¼Œä½†ä¾æ“šæˆ‘們 2015 å¹´ 6 月發佈的新版è¦ç¯„ï¼Œé€™é …æ¼æ´žå±¬æ–¼ã€Œæœ€é«˜ã€ç‰ç´šçš„å•é¡Œã€‚</p> <table> <tbody><tr> <th>CVE</th> - <th>錯誤 (附有 AOSP 連çµ)</th> + <th>錯誤 (附有 Android 開放原始碼計劃連çµ)</th> <th>åš´é‡ç¨‹åº¦</th> <th>å—影響的版本</th> </tr> @@ -225,15 +212,11 @@ 都å…許é ç«¯å…§å®¹é€£åˆ°é€™é …åŠŸèƒ½ï¼Œå…¶ä¸æœ€å¸¸è¦‹çš„內容是多媒體 訊æ¯å’Œç€è¦½å™¨ä¸æ’放的媒體。</p> -<p>由於這個å•é¡Œå¯èƒ½æœƒè®“é 端程å¼ç¢¼ç•¶åšç²å¾—授權的æœå‹™ä¾† -åŸ·è¡Œï¼Œå› æ¤è¢«è©•å®šç‚ºã€Œæœ€é«˜ã€çš„影響程度。儘管媒體伺æœå™¨ -會å—到 SELinux ä¿è·ï¼Œä½†å®ƒç¢ºå¯¦èƒ½å¤ å˜å–音訊和視訊串æµï¼Œ -以åŠåœ¨è¨±å¤šè£ç½®ä¸Šç²å¾—æŽˆæ¬Šçš„æ ¸å¿ƒé©…å‹•ç¨‹å¼è£ç½®ç¯€é»ž (這是 -第三方應用程å¼ä¸€èˆ¬ç„¡æ³•å˜å–的權é™)。請注æ„，ä¾æ“šèˆŠç‰ˆçš„åš´é‡ç¨‹åº¦è©•å®šè¦ç¯„ï¼Œé€™é …æ¼æ´žçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ï¼Œä¸¦å·²æ“šæ¤å›žå ±çµ¦åˆä½œå¤¥ä¼´ï¼Œä½†ä¾æ“šæˆ‘們 2015 å¹´ 6 月發佈的新版è¦ç¯„ï¼Œé€™é …æ¼æ´žå»å±¬æ–¼ã€Œæœ€é«˜ã€ç‰ç´šçš„å•é¡Œã€‚</p> +<p>由於這個å•é¡Œå¯èƒ½æœƒè®“é 端程å¼ç¢¼ç•¶åšç²å¾—授權的æœå‹™ä¾†åŸ·è¡Œï¼Œå› æ¤åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œæœ€é«˜ã€ã€‚儘管媒體伺æœå™¨æœƒå—到 SELinux ä¿è·ï¼Œä½†å®ƒç¢ºå¯¦èƒ½å¤ å˜å–音訊和視訊串æµï¼Œä»¥åŠåœ¨è¨±å¤šè£ç½®ä¸Šç²å¾—æŽˆæ¬Šçš„æ ¸å¿ƒé©…å‹•ç¨‹å¼è£ç½®ç¯€é»ž (這是第三方應用程å¼ä¸€èˆ¬ç„¡æ³•å˜å–的權é™)。請注æ„，ä¾æ“šèˆŠç‰ˆçš„åš´é‡ç¨‹åº¦è©•å®šè¦ç¯„ï¼Œé€™é …æ¼æ´žçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ï¼Œä¸¦å·²æ“šæ¤å›žå ±çµ¦åˆä½œå¤¥ä¼´ï¼Œä½†ä¾æ“šæˆ‘們 2015 å¹´ 6 月發佈的新版è¦ç¯„ï¼Œé€™é …æ¼æ´žå±¬æ–¼ã€Œæœ€é«˜ã€ç‰ç´šçš„å•é¡Œã€‚</p> <table> <tbody><tr> <th>CVE</th> - <th>錯誤 (附有 AOSP 連çµ)</th> + <th>錯誤 (附有 Android 開放原始碼計劃連çµ)</th> <th>åš´é‡ç¨‹åº¦</th> <th>å—影響的版本</th> </tr> @@ -255,8 +238,7 @@ 都å…許é ç«¯å…§å®¹é€£åˆ°é€™é …åŠŸèƒ½ï¼Œå…¶ä¸æœ€å¸¸è¦‹çš„內容是多媒體 訊æ¯å’Œç€è¦½å™¨ä¸æ’放的媒體。</p> -<p>由於這個å•é¡Œå¯èƒ½æœƒè®“é 端程å¼ç¢¼ç•¶åšç²å¾—授權的æœå‹™ä¾† -åŸ·è¡Œï¼Œå› æ¤è¢«è©•å®šç‚ºã€Œæœ€é«˜ã€çš„影響程度。儘管媒體伺æœå™¨ +<p>由於這個å•é¡Œå¯èƒ½æœƒè®“é 端程å¼ç¢¼ç•¶åšç²å¾—授權的æœå‹™ä¾†åŸ·è¡Œï¼Œå› æ¤åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œæœ€é«˜ã€ã€‚儘管媒體伺æœå™¨ 會å—到 SELinux ä¿è·ï¼Œä½†å®ƒç¢ºå¯¦èƒ½å¤ å˜å–音訊和視訊串æµï¼Œ 以åŠåœ¨è¨±å¤šè£ç½®ä¸Šç²å¾—æŽˆæ¬Šçš„æ ¸å¿ƒé©…å‹•ç¨‹å¼è£ç½®ç¯€é»ž (這是 第三方應用程å¼ä¸€èˆ¬ç„¡æ³•å˜å–的權é™)。</p> @@ -268,7 +250,7 @@ <table> <tbody><tr> <th>CVE</th> - <th>錯誤 (附有 AOSP 連çµ)</th> + <th>錯誤 (附有 Android 開放原始碼計劃連çµ)</th> <th>åš´é‡ç¨‹åº¦</th> <th>å—影響的版本</th> </tr> @@ -295,7 +277,7 @@ <table> <tbody><tr> <th>CVE</th> - <th>錯誤 (附有 AOSP 連çµ)</th> + <th>錯誤 (附有 Android 開放原始碼計劃連çµ)</th> <th>åš´é‡ç¨‹åº¦</th> <th>å—影響的版本</th> </tr> @@ -323,7 +305,7 @@ <table> <tbody><tr> <th>CVE</th> - <th>錯誤 (附有 AOSP 連çµ)</th> + <th>錯誤 (附有 Android 開放原始碼計劃連çµ)</th> <th>åš´é‡ç¨‹åº¦</th> <th>å—影響的版本</th> </tr> @@ -362,7 +344,7 @@ <table> <tbody><tr> <th>CVE</th> - <th>錯誤 (附有 AOSP 連çµ)</th> + <th>錯誤 (附有 Android 開放原始碼計劃連çµ)</th> <th>åš´é‡ç¨‹åº¦</th> <th>å—影響的版本</th> </tr> @@ -385,7 +367,7 @@ <table> <tbody><tr> <th>CVE</th> - <th>錯誤 (附有 AOSP 連çµ)</th> + <th>錯誤 (附有 Android 開放原始碼計劃連çµ)</th> <th>åš´é‡ç¨‹åº¦</th> <th>å—影響的版本</th> </tr> @@ -413,7 +395,7 @@ <table> <tbody><tr> <th>CVE</th> - <th>錯誤 (附有 AOSP 連çµ)</th> + <th>錯誤 (附有 Android 開放原始碼計劃連çµ)</th> <th>åš´é‡ç¨‹åº¦</th> <th>å—影響的版本</th> </tr> @@ -441,7 +423,7 @@ <table> <tbody><tr> <th>CVE</th> - <th>錯誤 (附有 AOSP 連çµ)</th> + <th>錯誤 (附有 Android 開放原始碼計劃連çµ)</th> <th>åš´é‡ç¨‹åº¦</th> <th>å—影響的版本</th> </tr> @@ -469,7 +451,7 @@ <table> <tbody><tr> <th>CVE</th> - <th>錯誤 (附有 AOSP 連çµ)</th> + <th>錯誤 (附有 Android 開放原始碼計劃連çµ)</th> <th>åš´é‡ç¨‹åº¦</th> <th>å—影響的版本</th> </tr> @@ -493,7 +475,7 @@ <table> <tbody><tr> <th>CVE</th> - <th>錯誤 (附有 AOSP 連çµ)</th> + <th>錯誤 (附有 Android 開放原始碼計劃連çµ)</th> <th>åš´é‡ç¨‹åº¦</th> <th>å—影響的版本</th> </tr> @@ -520,7 +502,7 @@ <table> <tbody><tr> <th>CVE</th> - <th>錯誤 (附有 AOSP 連çµ)</th> + <th>錯誤 (附有 Android 開放原始碼計劃連çµ)</th> <th>åš´é‡ç¨‹åº¦</th> <th>å—影響的版本</th> </tr> @@ -545,7 +527,7 @@ <table> <tbody><tr> <th>CVE</th> - <th>錯誤 (附有 AOSP 連çµ)</th> + <th>錯誤 (附有 Android 開放原始碼計劃連çµ)</th> <th>åš´é‡ç¨‹åº¦</th> <th>å—影響的版本</th> </tr> @@ -568,7 +550,7 @@ <table> <tbody><tr> <th>CVE</th> - <th>錯誤 (附有 AOSP 連çµ)</th> + <th>錯誤 (附有 Android 開放原始碼計劃連çµ)</th> <th>åš´é‡ç¨‹åº¦</th> <th>å—影響的版本</th> </tr> @@ -598,7 +580,7 @@ <table> <tbody><tr> <th>CVE</th> - <th>錯誤 (附有 AOSP 連çµ)</th> + <th>錯誤 (附有 Android 開放原始碼計劃連çµ)</th> <th>åš´é‡ç¨‹åº¦</th> <th>å—影響的版本</th> </tr> @@ -621,7 +603,7 @@ <table> <tbody><tr> <th>CVE</th> - <th>錯誤 (附有 AOSP 連çµ)</th> + <th>錯誤 (附有 Android 開放原始碼計劃連çµ)</th> <th>åš´é‡ç¨‹åº¦</th> <th>å—影響的版本</th> </tr> diff --git a/zh-tw/security/bulletin/2015-12-01.html b/zh-tw/security/bulletin/2015-12-01.html index 5b9f335c..76987cbc 100644 --- a/zh-tw/security/bulletin/2015-12-01.html +++ b/zh-tw/security/bulletin/2015-12-01.html @@ -36,8 +36,7 @@ <ul> <li>Android å¹³å°æŒçºŒæŽ¨å‡ºæ–°çš„ç‰ˆæœ¬ä¾†å¼·åŒ–å®‰å…¨æ€§ï¼Œå› æ¤æœ‰å¿ƒäººå£«è¶Šä¾†è¶Šé›£åœ¨ Android 系統上找出æ¼æ´žåŠ 以利用。我們建è°æ‰€æœ‰ä½¿ç”¨è€…盡å¯èƒ½æ›´æ–°è‡³æœ€æ–°ç‰ˆçš„ Android。</li> - <li>Android 安全性å°çµ„採用「驗è‰æ‡‰ç”¨ç¨‹å¼ã€å’Œ SafetyNet 主動監控濫用情形，這些功能果發ç¾æ‡‰ç”¨ç¨‹å¼å¯èƒ½æœ‰å®³ï¼Œå°‡åœ¨å®‰è£ä½œæ¥å‰ç™¼å‡ºè¦å‘Šã€‚Google Play å…§ç¦æ¢ç™¼ä½ˆä»»ä½•å¯ç”¨æ–¼ç²å–è£ç½® Root 權é™çš„å·¥å…·ã€‚ç‚ºäº†åœ¨ä½¿ç”¨è€…å®‰è£ Google Play 外的應用程å¼æ™‚æä¾›ä¿è·ï¼Œç³»çµ±é è¨æœƒå•Ÿç”¨é©—è‰æ‡‰ç”¨ç¨‹å¼ï¼Œä¸¦å‘使用者發出è¦å‘Šï¼Œæ醒他們留æ„ç›®å‰å·²çŸ¥æœƒç²å– Root 權é™çš„應用程å¼ã€‚「驗è‰æ‡‰ç”¨ç¨‹å¼ã€æœƒç›¡å¯èƒ½æ‰¾å‡ºå·²çŸ¥æœƒåˆ©ç”¨æ¬Šé™å‡ç´šæ¼æ´žçš„惡æ„應用程å¼ï¼Œ -並å°éŽ–這類應用程å¼çš„安è£ç¨‹åºã€‚如果使用者已安è£é€™é¡žæ‡‰ç”¨ç¨‹å¼ï¼Œã€Œé©—è‰æ‡‰ç”¨ç¨‹å¼ã€æœƒé€šçŸ¥ä½¿ç”¨è€…，並嘗試移除該應用程å¼ã€‚</li> + <li>Android 安全性å°çµ„採用「驗è‰æ‡‰ç”¨ç¨‹å¼ã€å’Œ SafetyNet 主動監控濫用情形，這些功能果發ç¾æ‡‰ç”¨ç¨‹å¼å¯èƒ½æœ‰å®³ï¼Œå°‡åœ¨å®‰è£ä½œæ¥å‰ç™¼å‡ºè¦å‘Šã€‚Google Play å…§ç¦æ¢ç™¼ä½ˆä»»ä½•å¯ç”¨æ–¼ç²å–è£ç½® Root 權é™çš„工具。為了ä¿è·ä¸æ˜¯åœ¨ Google Play 安è£æ‡‰ç”¨ç¨‹å¼çš„使用者，「驗è‰æ‡‰ç”¨ç¨‹å¼ã€åœ¨é è¨ç‹€æ…‹ä¸‹æœƒè‡ªå‹•å•Ÿç”¨ä¸¦å‘使用者發出è¦å‘Šï¼Œæ醒他們留æ„ç›®å‰å·²çŸ¥çš„ç ´è§£ç¨‹å¼ (用於å–å¾— Root 權é™çš„應用程å¼)。「驗è‰æ‡‰ç”¨ç¨‹å¼ã€æœƒç›¡å¯èƒ½æ‰¾å‡ºå·²çŸ¥æœƒåˆ©ç”¨æ¬Šé™å‡ç´šæ¼æ´žçš„惡æ„應用程å¼ï¼Œä¸¦å°éŽ–這類應用程å¼çš„安è£ç¨‹åºã€‚如果使用者已安è£é€™é¡žæ‡‰ç”¨ç¨‹å¼ï¼Œã€Œé©—è‰æ‡‰ç”¨ç¨‹å¼ã€æœƒé€šçŸ¥ä½¿ç”¨è€…，並嘗試移除該應用程å¼ã€‚</li> <li>在é©ç”¨æƒ…æ³ä¸‹ï¼ŒGoogle Hangouts å’Œ Messenger 應用程å¼ä¸æœƒè‡ªå‹•å°‡åª’體內容傳é€çµ¦åª’體伺æœå™¨é€™é¡žçš„處ç†ç¨‹åºã€‚</li> </ul> @@ -139,9 +138,9 @@ CVE-2015-6619ã€CVE-2015-6633ã€CVE-2015-6634 <table> <tbody><tr> <th>CVE</th> - <th>錯誤 (附有 AOSP 連çµ)</th> + <th>錯誤 (附有 Android 開放原始碼計劃連çµ)</th> <th>åš´é‡ç¨‹åº¦</th> - <th>最新版本</th> + <th>需è¦æ›´æ–°çš„版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -208,13 +207,13 @@ CVE-2015-6619ã€CVE-2015-6633ã€CVE-2015-6634 <h3 id="elevation_of_privilege_vulnerabilities_in_libstagefright"> libstagefright ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> -<p>libstagefright ä¸æœ‰å¤šé …æ¼æ´žï¼Œæœ¬æ©Ÿæƒ¡æ„應用程å¼å¯åŠ 以利用，在媒體伺æœå™¨æœå‹™ç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚由於這個å•é¡Œå¯ç”¨æ–¼å–å¾—æŸäº›é€²éšŽæ¬Šé™ (例如 <a href="http://developer.android.com/guide/topics/manifest/permission-element.html#plevel">Signature</a> 或 <a href="http://developer.android.com/guide/topics/manifest/permission-element.html#plevel">SignatureOrSystem</a> ç‰ç¬¬ä¸‰æ–¹æ‡‰ç”¨ç¨‹å¼ç„¡æ³•å˜å–的權é™)ï¼Œå› æ¤åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚</p> +<p>libstagefright ä¸æœ‰å¤šé …æ¼æ´žï¼Œæœ¬æ©Ÿæƒ¡æ„應用程å¼å¯åŠ 以利用，在媒體伺æœå™¨æœå‹™ç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚由於這個å•é¡Œå¯ç”¨æ–¼å–得進階功能 (例如 <a href="http://developer.android.com/guide/topics/manifest/permission-element.html#plevel">Signature</a> 或 <a href="http://developer.android.com/guide/topics/manifest/permission-element.html#plevel">SignatureOrSystem</a> ç‰ç¬¬ä¸‰æ–¹æ‡‰ç”¨ç¨‹å¼ç„¡æ³•å˜å–的權é™)ï¼Œå› æ¤åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚</p> <table> <tbody><tr> <th>CVE</th> - <th>錯誤 (附有 AOSP 連çµ)</th> + <th>錯誤 (附有 Android 開放原始碼計劃連çµ)</th> <th>åš´é‡ç¨‹åº¦</th> - <th>最新版本</th> + <th>需è¦æ›´æ–°çš„版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -235,7 +234,7 @@ libstagefright ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> <h3 id="elevation_of_privilege_vulnerability_in_systemui"> SystemUI ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> -<p>使用鬧é˜æ‡‰ç”¨ç¨‹å¼è¨å®šé¬§é˜æ™‚，應用程å¼å¯èƒ½æœƒåˆ©ç”¨ SystemUI 元件ä¸çš„æ¼æ´žåŸ·è¡Œæ›´é«˜æ¬Šé™ç‰ç´šçš„工作。由於這個å•é¡Œå¯ç”¨æ–¼å–å¾—æŸäº›é€²éšŽæ¬Šé™ (例如 <a href="http://developer.android.com/guide/topics/manifest/permission-element.html#plevel">Signature</a> 或 <a href="http://developer.android.com/guide/topics/manifest/permission-element.html#plevel">SignatureOrSystem</a> ç‰ç¬¬ä¸‰æ–¹æ‡‰ç”¨ç¨‹å¼ç„¡æ³•å˜å–的權é™)ï¼Œå› æ¤åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚</p> +<p>使用鬧é˜æ‡‰ç”¨ç¨‹å¼è¨å®šé¬§é˜æ™‚，應用程å¼å¯èƒ½æœƒåˆ©ç”¨ SystemUI 元件ä¸çš„æ¼æ´žåŸ·è¡Œæ›´é«˜æ¬Šé™ç‰ç´šçš„工作。由於這個å•é¡Œå¯ç”¨æ–¼å–得進階功能 (例如 <a href="http://developer.android.com/guide/topics/manifest/permission-element.html#plevel">Signature</a> 或 <a href="http://developer.android.com/guide/topics/manifest/permission-element.html#plevel">SignatureOrSystem</a> ç‰ç¬¬ä¸‰æ–¹æ‡‰ç”¨ç¨‹å¼ç„¡æ³•å˜å–的權é™)ï¼Œå› æ¤åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚</p> <table> <tbody><tr> <th>CVE</th> @@ -255,13 +254,13 @@ SystemUI ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> <h3 id="information_disclosure_vulnerability_in_native_frameworks_library">原生架構程å¼åº«ä¸çš„資訊外洩æ¼æ´ž</h3> -<p>Android 原生架構程å¼åº«ä¸çš„資訊外洩æ¼æ´žå¯è®“有心人士用來è¦é¿ç³»çµ±ä¸ç”¨æ–¼é˜²ç¯„攻擊者惡æ„é‹ç”¨å¹³å°çš„安全措施。由於這些å•é¡Œä¹Ÿèƒ½ç”¨ä¾†å–å¾—æŸäº›é€²éšŽæ¬Šé™ (例如 <a href="http://developer.android.com/guide/topics/manifest/permission-element.html#plevel">Signature</a> 或 <a href="http://developer.android.com/guide/topics/manifest/permission-element.html#plevel">SignatureOrSystem</a> ç‰ç¬¬ä¸‰æ–¹æ‡‰ç”¨ç¨‹å¼ç„¡æ³•å˜å–的權é™)ï¼Œå› æ¤åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚</p> +<p>Android 原生架構程å¼åº«ä¸çš„資訊外洩æ¼æ´žå¯è®“有心人士用來è¦é¿ç³»çµ±ä¸ç”¨æ–¼é˜²ç¯„攻擊者惡æ„é‹ç”¨å¹³å°çš„安全措施。由於這些å•é¡Œä¹Ÿèƒ½ç”¨ä¾†å–得更高權é™çš„功能 (例如 <a href="http://developer.android.com/guide/topics/manifest/permission-element.html#plevel">Signature</a> 或 <a href="http://developer.android.com/guide/topics/manifest/permission-element.html#plevel">SignatureOrSystem</a> ç‰ç¬¬ä¸‰æ–¹æ‡‰ç”¨ç¨‹å¼ç„¡æ³•å˜å–的權é™)ï¼Œå› æ¤åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚</p> <table> <tbody><tr> <th>CVE</th> - <th>錯誤 (附有 AOSP 連çµ)</th> + <th>錯誤 (附有 Android 開放原始碼計劃連çµ)</th> <th>åš´é‡ç¨‹åº¦</th> - <th>最新版本</th> + <th>需è¦æ›´æ–°çš„版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -275,7 +274,7 @@ SystemUI ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> <h3 id="elevation_of_privilege_vulnerability_in_wi-fi">Wi-Fi 連線ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> -<p>Wi-Fi 連線ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨é€²éšŽç³»çµ±æœå‹™ç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚由於這個å•é¡Œå¯ç”¨æ–¼å–å¾—æŸäº›é€²éšŽæ¬Šé™ (例如 <a href="http://developer.android.com/guide/topics/manifest/permission-element.html#plevel">Signature</a> 或 <a href="http://developer.android.com/guide/topics/manifest/permission-element.html#plevel">SignatureOrSystem</a> ç‰ç¬¬ä¸‰æ–¹æ‡‰ç”¨ç¨‹å¼ç„¡æ³•å˜å–的權é™)ï¼Œå› æ¤åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚</p> +<p>Wi-Fi 連線ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨é€²éšŽç³»çµ±æœå‹™ç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚由於這個å•é¡Œå¯ç”¨æ–¼å–得進階功能 (例如 <a href="http://developer.android.com/guide/topics/manifest/permission-element.html#plevel">Signature</a> 或 <a href="http://developer.android.com/guide/topics/manifest/permission-element.html#plevel">SignatureOrSystem</a> ç‰ç¬¬ä¸‰æ–¹æ‡‰ç”¨ç¨‹å¼ç„¡æ³•å˜å–的權é™)ï¼Œå› æ¤åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚</p> <table> <tbody><tr> <th>CVE</th> @@ -295,7 +294,7 @@ SystemUI ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> <h3 id="elevation_of_privilege_vulnerability_in_system_server">系統伺æœå™¨ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> -<p>系統伺æœå™¨å…ƒä»¶ä¸çš„權é™å‡ç´šæ¼æ´žå¯è®“本機惡æ„應用程å¼å–å¾—æœå‹™ç›¸é—œè³‡è¨Šçš„å˜å–權。由於這個å•é¡Œå¯ç”¨æ–¼å–å¾—æŸäº›é€²éšŽæ¬Šé™ (例如 <a href="http://developer.android.com/guide/topics/manifest/permission-element.html#plevel">Signature</a> 或 <a href="http://developer.android.com/guide/topics/manifest/permission-element.html#plevel">SignatureOrSystem</a> ç‰ç¬¬ä¸‰æ–¹æ‡‰ç”¨ç¨‹å¼ç„¡æ³•å˜å–的權é™)ï¼Œå› æ¤åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚</p> +<p>系統伺æœå™¨å…ƒä»¶ä¸çš„權é™å‡ç´šæ¼æ´žå¯è®“本機惡æ„應用程å¼å–å¾—æœå‹™ç›¸é—œè³‡è¨Šçš„å˜å–權。由於這個å•é¡Œå¯ç”¨æ–¼å–得進階功能 (例如 <a href="http://developer.android.com/guide/topics/manifest/permission-element.html#plevel">Signature</a> 或 <a href="http://developer.android.com/guide/topics/manifest/permission-element.html#plevel">SignatureOrSystem</a> ç‰ç¬¬ä¸‰æ–¹æ‡‰ç”¨ç¨‹å¼ç„¡æ³•å˜å–的權é™)ï¼Œå› æ¤åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚</p> <table> <tbody><tr> <th>CVE</th> @@ -316,7 +315,7 @@ SystemUI ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> <h3 id="information_disclosure_vulnerabilities_in_libstagefright"> libstagefright ä¸çš„資訊外洩æ¼æ´ž</h3> -<p>在系統與媒體伺æœå™¨é€²è¡Œé€šè¨Šæ™‚，libstagefright ä¸çš„一些資訊外洩æ¼æ´žå¯è®“有心人士用來è¦é¿ç³»çµ±ä¸ç”¨æ–¼é˜²ç¯„攻擊者惡æ„é‹ç”¨å¹³å°çš„安全措施。由於這些å•é¡Œä¹Ÿèƒ½ç”¨ä¾†å–å¾—æŸäº›é€²éšŽæ¬Šé™ (例如 <a href="http://developer.android.com/guide/topics/manifest/permission-element.html#plevel">Signature</a> 或 <a href="http://developer.android.com/guide/topics/manifest/permission-element.html#plevel">SignatureOrSystem</a> ç‰ç¬¬ä¸‰æ–¹æ‡‰ç”¨ç¨‹å¼ç„¡æ³•å˜å–的權é™)ï¼Œå› æ¤åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚</p> +<p>在系統與媒體伺æœå™¨é€²è¡Œé€šè¨Šæ™‚，libstagefright ä¸çš„一些資訊外洩æ¼æ´žå¯è®“有心人士用來è¦é¿ç³»çµ±ä¸ç”¨æ–¼é˜²ç¯„攻擊者惡æ„é‹ç”¨å¹³å°çš„安全措施。由於這些å•é¡Œä¹Ÿèƒ½ç”¨ä¾†å–得更高權é™çš„功能 (例如 <a href="http://developer.android.com/guide/topics/manifest/permission-element.html#plevel">Signature</a> 或 <a href="http://developer.android.com/guide/topics/manifest/permission-element.html#plevel">SignatureOrSystem</a> ç‰ç¬¬ä¸‰æ–¹æ‡‰ç”¨ç¨‹å¼ç„¡æ³•å˜å–的權é™)ï¼Œå› æ¤åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚</p> <table> <tbody><tr> <th>CVE</th> @@ -350,7 +349,7 @@ libstagefright ä¸çš„資訊外洩æ¼æ´ž</h3> <h3 id="information_disclosure_vulnerability_in_audio">音訊ä¸çš„資訊外洩æ¼æ´ž</h3> -<p>音訊元件ä¸çš„æ¼æ´žå¯èƒ½æœƒåœ¨ç³»çµ±è™•ç†éŸ³è¨Šæª”案時é到惡æ„é‹ç”¨ã€‚在處ç†æŸäº›ç‰¹æ®Šçš„檔案時，本機惡æ„應用程å¼å¯èƒ½æœƒåˆ©ç”¨é€™é …æ¼æ´žé€ æˆè³‡è¨Šå¤–洩。由於這個å•é¡Œå¯ç”¨æ–¼å–å¾—æŸäº›é€²éšŽæ¬Šé™ (例如 <a href="http://developer.android.com/guide/topics/manifest/permission-element.html#plevel">Signature</a> 或 <a href="http://developer.android.com/guide/topics/manifest/permission-element.html#plevel">SignatureOrSystem</a> ç‰ç¬¬ä¸‰æ–¹æ‡‰ç”¨ç¨‹å¼ç„¡æ³•å˜å–的權é™)ï¼Œå› æ¤åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚</p> +<p>音訊元件ä¸çš„æ¼æ´žå¯èƒ½æœƒåœ¨ç³»çµ±è™•ç†éŸ³è¨Šæª”案時é到惡æ„é‹ç”¨ã€‚在處ç†æŸäº›ç‰¹æ®Šçš„檔案時，本機惡æ„應用程å¼å¯èƒ½æœƒåˆ©ç”¨é€™é …æ¼æ´žé€ æˆè³‡è¨Šå¤–洩。由於這個å•é¡Œå¯ç”¨æ–¼å–得進階功能 (例如 <a href="http://developer.android.com/guide/topics/manifest/permission-element.html#plevel">Signature</a> 或 <a href="http://developer.android.com/guide/topics/manifest/permission-element.html#plevel">SignatureOrSystem</a> ç‰ç¬¬ä¸‰æ–¹æ‡‰ç”¨ç¨‹å¼ç„¡æ³•å˜å–的權é™)ï¼Œå› æ¤åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚</p> <table> <tbody><tr> <th>CVE</th> @@ -390,7 +389,7 @@ libstagefright ä¸çš„資訊外洩æ¼æ´ž</h3> <h3 id="information_disclosure_vulnerability_in_wi-fi">Wi-Fi 連線ä¸çš„資訊外洩æ¼æ´ž</h3> -<p>Wi-Fi 元件ä¸çš„æ¼æ´žå¯è®“æ”»æ“Šè€…é€ æˆ Wi-Fi æœå‹™æ´©æ¼è³‡è¨Šã€‚由於這個å•é¡Œå¯ç”¨æ–¼å–å¾—æŸäº›é€²éšŽæ¬Šé™ (例如 <a href="http://developer.android.com/guide/topics/manifest/permission-element.html#plevel">Signature</a> 或 <a href="http://developer.android.com/guide/topics/manifest/permission-element.html#plevel">SignatureOrSystem</a> ç‰ç¬¬ä¸‰æ–¹æ‡‰ç”¨ç¨‹å¼ç„¡æ³•å˜å–的權é™)ï¼Œå› æ¤åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚</p> +<p>Wi-Fi 元件ä¸çš„æ¼æ´žå¯è®“æ”»æ“Šè€…é€ æˆ Wi-Fi æœå‹™æ´©æ¼è³‡è¨Šã€‚由於這個å•é¡Œå¯ç”¨æ–¼å–得進階功能 (例如 <a href="http://developer.android.com/guide/topics/manifest/permission-element.html#plevel">Signature</a> 或 <a href="http://developer.android.com/guide/topics/manifest/permission-element.html#plevel">SignatureOrSystem</a> ç‰ç¬¬ä¸‰æ–¹æ‡‰ç”¨ç¨‹å¼ç„¡æ³•å˜å–的權é™)ï¼Œå› æ¤åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚</p> <table> <tbody><tr> <th>CVE</th> @@ -414,7 +413,7 @@ libstagefright ä¸çš„資訊外洩æ¼æ´ž</h3> <table> <tbody><tr> <th>CVE</th> - <th>錯誤 (附有 AOSP 連çµ)</th> + <th>錯誤 (附有 Android 開放原始碼計劃連çµ)</th> <th>åš´é‡ç¨‹åº¦</th> <th>需è¦æ›´æ–°çš„版本</th> <th>å›žå ±æ—¥æœŸ</th> diff --git a/zh-tw/security/bulletin/2016-06-01.html b/zh-tw/security/bulletin/2016-06-01.html index 772813f7..a53b2e17 100644 --- a/zh-tw/security/bulletin/2016-06-01.html +++ b/zh-tw/security/bulletin/2016-06-01.html @@ -87,7 +87,7 @@ <th>Android 錯誤</th> <th>åš´é‡ç¨‹åº¦</th> <th>æ›´æ–°çš„ Nexus è£ç½®</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -449,7 +449,7 @@ Qualcomm 音效驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> <td><a href="https://android.googlesource.com/platform/frameworks/av/+/ad40e57890f81a3cf436c5f06da66396010bd9e5">27793371</a> </td> <td>高</td> - <td><a href="#nexus_devices">All Nexus</a></td> + <td><a href="#nexus_devices">所有 Nexus è£ç½®</a></td> <td>4.4.4ã€5.0.2ã€5.1.1ã€6.0ã€6.0.1</td> <td>2016 å¹´ 3 月 22 æ—¥</td> </tr> @@ -460,7 +460,7 @@ Qualcomm 音效驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> [<a href="https://android.googlesource.com/platform/frameworks/av/+/4e32001e4196f39ddd0b86686ae0231c8f5ed944">3</a>] </td> <td>高</td> - <td><a href="#nexus_devices">All Nexus</a></td> + <td><a href="#nexus_devices">所有 Nexus è£ç½®</a></td> <td>4.4.4ã€5.0.2ã€5.1.1ã€6.0ã€6.0.1</td> <td>Google 內部資訊</td> </tr> @@ -660,7 +660,7 @@ SD å¡æ¨¡æ“¬å±¤ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> <th>Android 錯誤</th> <th>åš´é‡ç¨‹åº¦</th> <th>æ›´æ–°çš„ Nexus è£ç½®</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -668,7 +668,7 @@ SD å¡æ¨¡æ“¬å±¤ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> <td><a href="https://android.googlesource.com/platform/system/core/+/864e2e22fcd0cba3f5e67680ccabd0302dfda45d">28085658</a> </td> <td>高</td> - <td><a href="#nexus_devices">All Nexus</a></td> + <td><a href="#nexus_devices">所有 Nexus è£ç½®</a></td> <td>4.4.4ã€5.0.2ã€5.1.1ã€6.0ã€6.0.1</td> <td>2016 å¹´ 4 月 7 æ—¥</td> </tr> @@ -718,7 +718,7 @@ Broadcom Wi-Fi 驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> <th>Android 錯誤</th> <th>åš´é‡ç¨‹åº¦</th> <th>æ›´æ–°çš„ Nexus è£ç½®</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -727,7 +727,7 @@ Broadcom Wi-Fi 驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> [<a href="https://android.googlesource.com/platform/frameworks/av/+/b57b3967b1a42dd505dbe4fcf1e1d810e3ae3777">2</a>] </td> <td>高</td> - <td><a href="#nexus_devices">All Nexus</a></td> + <td><a href="#nexus_devices">所有 Nexus è£ç½®</a></td> <td>4.4.4ã€5.0.2ã€5.1.1ã€6.0ã€6.0.1</td> <td>2016 å¹´ 4 月 6 æ—¥</td> </tr> @@ -749,7 +749,7 @@ Broadcom Wi-Fi 驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> <th>Android 錯誤</th> <th>åš´é‡ç¨‹åº¦</th> <th>æ›´æ–°çš„ Nexus è£ç½®</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -809,7 +809,7 @@ Qualcomm Wi-Fi 驅動程å¼ä¸çš„資訊外洩æ¼æ´ž</h3> <th>Android 錯誤</th> <th>åš´é‡ç¨‹åº¦</th> <th>æ›´æ–°çš„ Nexus è£ç½®</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -839,7 +839,7 @@ Qualcomm Wi-Fi 驅動程å¼ä¸çš„資訊外洩æ¼æ´ž</h3> <th>Android 錯誤</th> <th>åš´é‡ç¨‹åº¦</th> <th>æ›´æ–°çš„ Nexus è£ç½®</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> diff --git a/zh-tw/security/bulletin/2016-07-01.html b/zh-tw/security/bulletin/2016-07-01.html index 1e38a37b..371f56f0 100644 --- a/zh-tw/security/bulletin/2016-07-01.html +++ b/zh-tw/security/bulletin/2016-07-01.html @@ -105,7 +105,7 @@ <th>åƒè€ƒè³‡æ–™</th> <th>åš´é‡ç¨‹åº¦</th> <th>æ›´æ–°çš„ Nexus è£ç½®</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -195,7 +195,7 @@ OpenSSL å’Œ BoringSSL ä¸çš„é 端程å¼ç¢¼åŸ·è¡Œæ¼æ´ž</h3> <th>åƒè€ƒè³‡æ–™</th> <th>åš´é‡ç¨‹åº¦</th> <th>æ›´æ–°çš„ Nexus è£ç½®</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -226,7 +226,7 @@ OpenSSL å’Œ BoringSSL ä¸çš„é 端程å¼ç¢¼åŸ·è¡Œæ¼æ´ž</h3> <th>åƒè€ƒè³‡æ–™</th> <th>åš´é‡ç¨‹åº¦</th> <th>æ›´æ–°çš„ Nexus è£ç½®</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -234,7 +234,7 @@ OpenSSL å’Œ BoringSSL ä¸çš„é 端程å¼ç¢¼åŸ·è¡Œæ¼æ´ž</h3> <td><a href="https://android.googlesource.com/platform/system/bt/+/514139f4b40cbb035bb92f3e24d5a389d75db9e6"> A-27930580</a></td> <td>高</td> - <td><a href="#all_nexus">All Nexus</a></td> + <td><a href="#all_nexus">所有 Nexus è£ç½®</a></td> <td>4.4.4ã€5.0.2ã€5.1.1ã€6.0ã€6.0.1</td> <td>2016 å¹´ 3 月 30 æ—¥</td> </tr> @@ -256,7 +256,7 @@ libpng ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> <th>åƒè€ƒè³‡æ–™</th> <th>åš´é‡ç¨‹åº¦</th> <th>æ›´æ–°çš„ Nexus è£ç½®</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -265,7 +265,7 @@ libpng ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> A-23265085</a> </td> <td>高</td> - <td><a href="#all_nexus">All Nexus</a></td> + <td><a href="#all_nexus">所有 Nexus è£ç½®</a></td> <td>4.4.4ã€5.0.2ã€5.1.1ã€6.0ã€6.0.1</td> <td>2015 å¹´ 12 月 3 æ—¥</td> </tr> @@ -287,7 +287,7 @@ libpng ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> <th>åƒè€ƒè³‡æ–™</th> <th>åš´é‡ç¨‹åº¦</th> <th>æ›´æ–°çš„ Nexus è£ç½®</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -296,7 +296,7 @@ libpng ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> A-28173666</a> </td> <td>高</td> - <td><a href="#all_nexus">All Nexus</a></td> + <td><a href="#all_nexus">所有 Nexus è£ç½®</a></td> <td>4.4.4ã€5.0.2ã€5.1.1ã€6.0ã€6.0.1</td> <td>2016 å¹´ 4 月 10 æ—¥</td> </tr> @@ -306,7 +306,7 @@ libpng ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> A-27890802</a> </td> <td>高</td> - <td><a href="#all_nexus">All Nexus</a></td> + <td><a href="#all_nexus">所有 Nexus è£ç½®</a></td> <td>4.4.4ã€5.0.2ã€5.1.1ã€6.0ã€6.0.1</td> <td>2016 å¹´ 3 月 27 æ—¥</td> </tr> @@ -316,7 +316,7 @@ libpng ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> A-27903498</a> </td> <td>高</td> - <td><a href="#all_nexus">All Nexus</a></td> + <td><a href="#all_nexus">所有 Nexus è£ç½®</a></td> <td>4.4.4ã€5.0.2ã€5.1.1ã€6.0ã€6.0.1</td> <td>2016 å¹´ 3 月 28 æ—¥</td> </tr> @@ -338,7 +338,7 @@ libpng ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> <th>åƒè€ƒè³‡æ–™</th> <th>åš´é‡ç¨‹åº¦</th> <th>æ›´æ–°çš„ Nexus è£ç½®</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -369,7 +369,7 @@ libpng ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> <th>åƒè€ƒè³‡æ–™</th> <th>åš´é‡ç¨‹åº¦</th> <th>æ›´æ–°çš„ Nexus è£ç½®</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -400,7 +400,7 @@ Framework API ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> <th>åƒè€ƒè³‡æ–™</th> <th>åš´é‡ç¨‹åº¦</th> <th>æ›´æ–°çš„ Nexus è£ç½®</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -409,7 +409,7 @@ Framework API ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> A-28395952</a> </td> <td>高</td> - <td><a href="#all_nexus">All Nexus</a></td> + <td><a href="#all_nexus">所有 Nexus è£ç½®</a></td> <td>4.4.4ã€5.0.2ã€5.1.1ã€6.0ã€6.0.1</td> <td>2015 å¹´ 12 月 16 æ—¥</td> </tr> @@ -431,7 +431,7 @@ ChooserTarget æœå‹™ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> <th>åƒè€ƒè³‡æ–™</th> <th>åš´é‡ç¨‹åº¦</th> <th>æ›´æ–°çš„ Nexus è£ç½®</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -462,7 +462,7 @@ ChooserTarget æœå‹™ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> <th>åƒè€ƒè³‡æ–™</th> <th>åš´é‡ç¨‹åº¦</th> <th>æ›´æ–°çš„ Nexus è£ç½®</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -492,7 +492,7 @@ OpenSSL ä¸çš„資訊外洩æ¼æ´ž</h3> <th>åƒè€ƒè³‡æ–™</th> <th>åš´é‡ç¨‹åº¦</th> <th>æ›´æ–°çš„ Nexus è£ç½®</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -522,7 +522,7 @@ OpenSSL ä¸çš„資訊外洩æ¼æ´ž</h3> <th>åƒè€ƒè³‡æ–™</th> <th>åš´é‡ç¨‹åº¦</th> <th>æ›´æ–°çš„ Nexus è£ç½®</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -532,7 +532,7 @@ OpenSSL ä¸çš„資訊外洩æ¼æ´ž</h3> [<a href="https://android.googlesource.com/platform/frameworks/av/+/e7142a0703bc93f75e213e96ebc19000022afed9">2</a>] </td> <td>高</td> - <td><a href="#all_nexus">All Nexus</a></td> + <td><a href="#all_nexus">所有 Nexus è£ç½®</a></td> <td>4.4.4ã€5.0.2ã€5.1.1ã€6.0ã€6.0.1</td> <td>2016 å¹´ 5 月 5 æ—¥</td> </tr> @@ -552,7 +552,7 @@ OpenSSL ä¸çš„資訊外洩æ¼æ´ž</h3> A-28556125</a> </td> <td>高</td> - <td><a href="#all_nexus">All Nexus</a></td> + <td><a href="#all_nexus">所有 Nexus è£ç½®</a></td> <td>4.4.4ã€5.0.2ã€5.1.1ã€6.0ã€6.0.1</td> <td>Google 內部資訊</td> </tr> @@ -573,7 +573,7 @@ OpenSSL ä¸çš„資訊外洩æ¼æ´ž</h3> <th>åƒè€ƒè³‡æ–™</th> <th>åš´é‡ç¨‹åº¦</th> <th>æ›´æ–°çš„ Nexus è£ç½®</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -602,7 +602,7 @@ OpenSSL ä¸çš„資訊外洩æ¼æ´ž</h3> <th>åƒè€ƒè³‡æ–™</th> <th>åš´é‡ç¨‹åº¦</th> <th>æ›´æ–°çš„ Nexus è£ç½®</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -632,7 +632,7 @@ OpenSSL ä¸çš„資訊外洩æ¼æ´ž</h3> <th>åƒè€ƒè³‡æ–™</th> <th>åš´é‡ç¨‹åº¦</th> <th>æ›´æ–°çš„ Nexus è£ç½®</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -663,7 +663,7 @@ Framework API ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> <th>åƒè€ƒè³‡æ–™</th> <th>åš´é‡ç¨‹åº¦</th> <th>æ›´æ–°çš„ Nexus è£ç½®</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -694,7 +694,7 @@ Framework API ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> <th>åƒè€ƒè³‡æ–™</th> <th>åš´é‡ç¨‹åº¦</th> <th>æ›´æ–°çš„ Nexus è£ç½®</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -726,7 +726,7 @@ NFC ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> <th>åƒè€ƒè³‡æ–™</th> <th>åš´é‡ç¨‹åº¦</th> <th>æ›´æ–°çš„ Nexus è£ç½®</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -757,7 +757,7 @@ NFC ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> <th>åƒè€ƒè³‡æ–™</th> <th>åš´é‡ç¨‹åº¦</th> <th>æ›´æ–°çš„ Nexus è£ç½®</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -788,7 +788,7 @@ Proxy 自動è¨å®šä¸çš„資訊外洩æ¼æ´ž</h3> <th>åƒè€ƒè³‡æ–™</th> <th>åš´é‡ç¨‹åº¦</th> <th>æ›´æ–°çš„ Nexus è£ç½®</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -819,7 +819,7 @@ Proxy 自動è¨å®šä¸çš„資訊外洩æ¼æ´ž</h3> <th>åƒè€ƒè³‡æ–™</th> <th>åš´é‡ç¨‹åº¦</th> <th>æ›´æ–°çš„ Nexus è£ç½®</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -860,7 +860,7 @@ Proxy 自動è¨å®šä¸çš„資訊外洩æ¼æ´ž</h3> <th>åƒè€ƒè³‡æ–™</th> <th>åš´é‡ç¨‹åº¦</th> <th>æ›´æ–°çš„ Nexus è£ç½®</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -881,7 +881,7 @@ Proxy 自動è¨å®šä¸çš„資訊外洩æ¼æ´ž</h3> <h3 id="elevation-of-privilege-vulnerability-in-qualcomm-gpu-driver"> Qualcomm GPU 驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> -<p>Qualcomm GPU 驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚由於這個å•é¡Œå¯èƒ½å°Žè‡´æœ¬æ©Ÿè£ç½®çš„å®‰å…¨æ€§å¾¹åº•è¢«ç ´å£žï¼Œä½¿è£ç½®å¿…é ˆä»¥é‚„åŽŸ (Re-flash) 作æ¥ç³»çµ±çš„æ–¹å¼æ‰èƒ½ä¿®å¾©ï¼Œå› æ¤åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œæœ€é«˜ã€ã€‚</p> +<p>Qualcomm GPU 驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚由於這個å•é¡Œå¯èƒ½å°Žè‡´æœ¬æ©Ÿè£ç½®çš„å®‰å…¨æ€§å¾¹åº•è¢«ç ´å£žï¼Œé€ æˆä½¿ç”¨è€…å¿…é ˆä»¥é‚„åŽŸ (Reflash) 作æ¥ç³»çµ±çš„æ–¹å¼æ‰èƒ½ä¿®å¾©è£ç½®ï¼Œå› æ¤åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œæœ€é«˜ã€ã€‚</p> <table> <colgroup><col width="19%" /> @@ -1409,7 +1409,7 @@ Qualcomm USB 驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> <h3 id="elevation-of-privilege-vulnerability-in-qualcomm-wi-fi-driver"> Qualcomm Wi-Fi 驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> -<p>Qualcomm Wi-Fi 驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚ç”±æ–¼é€™ç¨®æ”»æ“Šå¿…é ˆå…ˆç ´å£žç‰¹å®šç²æŽˆæ¬Šçš„程åºæ‰èƒ½åŸ·è¡Œï¼Œå› æ¤é€™å€‹å•é¡Œçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚</p> +<p>Qualcomm Wi-Fi 驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚ç”±æ–¼é€™ç¨®æ”»æ“Šå¿…é ˆå…ˆç ´è§£å…·æœ‰ç‰¹å®šæ¬Šé™çš„程åºæ‰èƒ½åŸ·è¡Œï¼Œå› æ¤é€™å€‹å•é¡Œçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚</p> <table> <colgroup><col width="19%" /> @@ -1436,7 +1436,7 @@ Qualcomm Wi-Fi 驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> <h3 id="elevation-of-privilege-vulnerability-in-qualcomm-camera-driver"> Qualcomm 相機驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> -<p>Qualcomm 相機驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚ç”±æ–¼é€™ç¨®æ”»æ“Šå¿…é ˆå…ˆç ´å£žç‰¹å®šç²æŽˆæ¬Šçš„程åºæ‰èƒ½åŸ·è¡Œï¼Œå› æ¤é€™å€‹å•é¡Œçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚</p> +<p>Qualcomm 相機驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚ç”±æ–¼é€™ç¨®æ”»æ“Šå¿…é ˆå…ˆç ´è§£å…·æœ‰ç‰¹å®šæ¬Šé™çš„程åºæ‰èƒ½åŸ·è¡Œï¼Œå› æ¤é€™å€‹å•é¡Œçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚</p> <table> <colgroup><col width="19%" /> @@ -1528,7 +1528,7 @@ MediaTek é›»æºé©…動程å¼ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> <h3 id="elevation-of-privilege-vulnerability-in-qualcomm-wi-fi-driver-2"> Qualcomm Wi-Fi 驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> -<p>Qualcomm Wi-Fi 驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚ç”±æ–¼é€™ç¨®æ”»æ“Šå¿…é ˆå…ˆç ´å£žç‰¹å®šç²æŽˆæ¬Šçš„程åºæ‰èƒ½åŸ·è¡Œï¼Œå› æ¤é€™å€‹å•é¡Œçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚</p> +<p>Qualcomm Wi-Fi 驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚ç”±æ–¼é€™ç¨®æ”»æ“Šå¿…é ˆå…ˆç ´è§£å…·æœ‰ç‰¹å®šæ¬Šé™çš„程åºæ‰èƒ½åŸ·è¡Œï¼Œå› æ¤é€™å€‹å•é¡Œçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚</p> <table> <colgroup><col width="19%" /> @@ -1556,7 +1556,7 @@ Qualcomm Wi-Fi 驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> <h3 id="elevation-of-privilege-vulnerability-in-mediatek-hardware-sensor-driver"> MediaTek 硬體感測器驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> -<p>MediaTek 硬體感測器驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚ç”±æ–¼é€™ç¨®æ”»æ“Šå¿…é ˆå…ˆç ´å£žç‰¹å®šç²æŽˆæ¬Šçš„程åºæ‰èƒ½åŸ·è¡Œï¼Œå› æ¤é€™å€‹å•é¡Œçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚</p> +<p>MediaTek 硬體感測器驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚ç”±æ–¼é€™ç¨®æ”»æ“Šå¿…é ˆå…ˆç ´è§£å…·æœ‰ç‰¹å®šæ¬Šé™çš„程åºæ‰èƒ½åŸ·è¡Œï¼Œå› æ¤é€™å€‹å•é¡Œçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚</p> <table> <colgroup><col width="19%" /> @@ -1584,7 +1584,7 @@ MediaTek 硬體感測器驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> <h3 id="elevation-of-privilege-vulnerability-in-mediatek-video-driver"> MediaTek 視訊驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> -<p>MediaTek 視訊驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚ç”±æ–¼é€™ç¨®æ”»æ“Šå¿…é ˆå…ˆç ´å£žç‰¹å®šç²æŽˆæ¬Šçš„程åºæ‰èƒ½åŸ·è¡Œï¼Œå› æ¤é€™å€‹å•é¡Œçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚</p> +<p>MediaTek 視訊驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚ç”±æ–¼é€™ç¨®æ”»æ“Šå¿…é ˆå…ˆç ´è§£å…·æœ‰ç‰¹å®šæ¬Šé™çš„程åºæ‰èƒ½åŸ·è¡Œï¼Œå› æ¤é€™å€‹å•é¡Œçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚</p> <table> <colgroup><col width="19%" /> diff --git a/zh-tw/security/bulletin/2016-08-01.html b/zh-tw/security/bulletin/2016-08-01.html index 9c904264..2c490115 100644 --- a/zh-tw/security/bulletin/2016-08-01.html +++ b/zh-tw/security/bulletin/2016-08-01.html @@ -158,7 +158,7 @@ CVE-2016-2504</li> <td><a href="https://android.googlesource.com/platform/external/jhead/+/bae671597d47b9e5955c4cb742e468cebfd7ca6b"> A-28868315</a></td> <td>高</td> - <td>All Nexus</td> + <td>所有 Nexus è£ç½®</td> <td>4.4.4ã€5.0.2ã€5.1.1ã€6.0ã€6.0.1</td> <td>Google 內部資訊</td> </tr> @@ -187,7 +187,7 @@ CVE-2016-2504</li> <td><a href="https://android.googlesource.com/platform/hardware/qcom/media/+/7558d03e6498e970b761aa44fff6b2c659202d95"> A-28815329</a></td> <td>高</td> - <td>All Nexus</td> + <td>所有 Nexus è£ç½®</td> <td>4.4.4ã€5.0.2ã€5.1.1ã€6.0ã€6.0.1</td> <td>2016 å¹´ 5 月 17 æ—¥</td> </tr> @@ -196,7 +196,7 @@ CVE-2016-2504</li> <td><a href="https://android.googlesource.com/platform/frameworks/av/+/b351eabb428c7ca85a34513c64601f437923d576"> A-28816827</a></td> <td>高</td> - <td>All Nexus</td> + <td>所有 Nexus è£ç½®</td> <td>4.4.4ã€5.0.2ã€5.1.1ã€6.0ã€6.0.1</td> <td>2016 å¹´ 5 月 17 æ—¥</td> </tr> @@ -214,7 +214,7 @@ CVE-2016-2504</li> <td><a href="https://android.googlesource.com/platform/frameworks/av/+/9cd8c3289c91254b3955bd7347cf605d6fa032c6"> A-29251553</a></td> <td>高</td> - <td>All Nexus</td> + <td>所有 Nexus è£ç½®</td> <td>4.4.4ã€5.0.2ã€5.1.1ã€6.0ã€6.0.1</td> <td>2016 å¹´ 6 月 9 æ—¥</td> </tr> @@ -270,7 +270,7 @@ CVE-2016-2504</li> <td><a href="https://android.googlesource.com/platform/frameworks/av/+/8e438e153f661e9df8db0ac41d587e940352df06"> A-29153599</a></td> <td>高</td> - <td>All Nexus</td> + <td>所有 Nexus è£ç½®</td> <td>4.4.4ã€5.0.2ã€5.1.1ã€6.0ã€6.0.1</td> <td>Google 內部資訊</td> </tr> @@ -299,7 +299,7 @@ CVE-2016-2504</li> <td><a href="https://android.googlesource.com/platform/frameworks/opt/telephony/+/f47bc301ccbc5e6d8110afab5a1e9bac1d4ef058"> A-29083635</a></td> <td>高</td> - <td>All Nexus</td> + <td>所有 Nexus è£ç½®</td> <td>4.4.4ã€5.0.2ã€5.1.1ã€6.0ã€6.0.1</td> <td>2016 å¹´ 5 月 31 æ—¥</td> </tr> @@ -842,7 +842,7 @@ QC-CR#547479</a> </p> </td> <td>高</td> - <td>Google Nexus 5</td> + <td>Nexus 5</td> <td>2014 å¹´ 4 月 30 æ—¥</td> </tr> <tr> @@ -926,7 +926,7 @@ QC-CR#562261</a> </p> </td> <td>高</td> - <td>Google Nexus 5</td> + <td>Nexus 5</td> <td>2014 å¹´ 4 月 30 æ—¥</td> </tr> <tr> @@ -973,7 +973,7 @@ QC-CR#642735</a> QC-CR#674712</a> </p></td> <td>高</td> - <td>Google Nexus 5</td> + <td>Nexus 5</td> <td>2014 å¹´ 10 月 31 æ—¥</td> </tr> <tr> @@ -1185,7 +1185,7 @@ Qualcomm 效能元件ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„æ‡‰ç”¨ç¨‹å¼ </p> <h3 id="elevation-of-privilege-vulnerability-in-kernel">æ ¸å¿ƒä¸çš„權é™å‡ç´šæ¼æ´ž</h3> -<p>æ ¸å¿ƒä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•æŒ‡ä»¤ã€‚由於這個å•é¡Œå¯èƒ½å°Žè‡´æœ¬æ©Ÿè£ç½®çš„å®‰å…¨æ€§å¾¹åº•è¢«ç ´å£žï¼Œä½¿è£ç½®å¿…é ˆä»¥é‚„åŽŸ (Re-flash) 作æ¥ç³»çµ±çš„æ–¹å¼æ‰èƒ½ä¿®å¾©ï¼Œå› æ¤åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œæœ€é«˜ã€ã€‚ +<p>æ ¸å¿ƒä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•æŒ‡ä»¤ã€‚由於這個å•é¡Œå¯èƒ½å°Žè‡´æœ¬æ©Ÿè£ç½®çš„å®‰å…¨æ€§å¾¹åº•è¢«ç ´å£žï¼Œé€ æˆä½¿ç”¨è€…å¿…é ˆä»¥é‚„åŽŸ (Reflash) 作æ¥ç³»çµ±çš„æ–¹å¼æ‰èƒ½ä¿®å¾©è£ç½®ï¼Œå› æ¤åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œæœ€é«˜ã€ã€‚ </p> <table> <colgroup><col width="19%" /> @@ -1623,7 +1623,7 @@ QC-CR#786116</a></p></td> <a href="https://us.codeaurora.org/cgit/quic/la/kernel/msm-3.10/commit/?id=bfc6eee5e30a0c20bc37495233506f4f0cc4991d"> QC-CR#542223</a></p></td> <td>ä¸</td> - <td>Google Nexus 5</td> + <td>Nexus 5</td> <td>2014 å¹´ 3 月 27 æ—¥</td> </tr> <tr> @@ -2015,7 +2015,7 @@ Framework API ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“é 先安è£çš„應用程å¼åœ¨ <ul> <li><strong>所有 Nexus è£ç½®</strong>：如果å•é¡Œæœƒå½±éŸ¿åˆ°æ‰€æœ‰ Nexus è£ç½®ï¼Œè¡¨æ ¼å…§ã€Œæ›´æ–°çš„ Nexus è£ç½®ã€<em></em>欄ä¸å°±æœƒé¡¯ç¤ºã€Œæ‰€æœ‰ Nexus è£ç½®ã€å—樣。「所有 Nexus è£ç½®ã€åŒ…å«ä¸‹åˆ—<a href="https://support.google.com/nexus/answer/4457705#nexus_devices">支æ´çš„è£ç½®</a>：Nexus 5ã€Nexus 5Xã€Nexus 6ã€Nexus 6Pã€Nexus 7 (2013)ã€Nexus 9ã€Android Oneã€Nexus Player å’Œ Pixel C。</li> <li><strong>部分 Nexus è£ç½®</strong>：如果å•é¡Œä¸¦æœªå½±éŸ¿æ‰€æœ‰ Nexus è£ç½®ï¼Œã€Œæ›´æ–°çš„ Nexus è£ç½®ã€<em></em>欄ä¸å°±æœƒåˆ—出å—到影響的 Nexus è£ç½®ã€‚</li> -<li><strong>ä¸å½±éŸ¿ä»»ä½• Nexus è£ç½®</strong>：如果å•é¡Œä¸æœƒå½±éŸ¿åˆ°ä»»ä½• Nexus è£ç½®ï¼Œã€Œæ›´æ–°çš„ Nexus è£ç½®ã€<em></em>欄ä¸å°±æœƒé¡¯ç¤ºã€Œç„¡ã€å—樣。 +<li><strong>ä¸å½±éŸ¿ä»»ä½• Nexus è£ç½®</strong>：如果å•é¡Œä¸æœƒå½±éŸ¿åˆ°ä»»ä½• Nexus è£ç½®ï¼Œè¡¨æ ¼å…§ã€Œæ›´æ–°çš„ Nexus è£ç½®ã€<em></em>欄ä¸å°±æœƒæ¨™ç¤ºã€Œç„¡ã€å—樣。 </li> </ul> <p> diff --git a/zh-tw/security/bulletin/2016-10-01.html b/zh-tw/security/bulletin/2016-10-01.html index 78bb518f..2365f1ba 100644 --- a/zh-tw/security/bulletin/2016-10-01.html +++ b/zh-tw/security/bulletin/2016-10-01.html @@ -53,7 +53,8 @@ <li>在é©ç”¨æƒ…æ³ä¸‹ï¼ŒGoogle Hangouts å’Œ Messenger 應用程å¼ä¸æœƒè‡ªå‹•å°‡åª’體內容傳é€çµ¦åª’體伺æœå™¨é€™é¡žçš„處ç†ç¨‹åºã€‚</li> </ul> <h2 id="acknowledgements">特別銘è¬</h2> -<p>æ„Ÿè¬ä»¥ä¸‹ç ”究人員åšå‡ºçš„è²¢ç»ï¼š +<p> +æ„Ÿè¬ä»¥ä¸‹ç ”究人員åšå‡ºçš„è²¢ç»ï¼š </p> <ul> <li>Andre Teixeira Rizzo：CVE-2016-3882</li> @@ -85,8 +86,9 @@ <li><a href="https://twitter.com/0xr0ot">çµè±¹ç§»å‹•</a>安全實驗室的 Zhanpeng Zhao (行之) (<a href="http://www.cmcm.com">@0xr0ot</a>)：CVE-2016-3908</li> </ul> -<h2 id="2016-10-01-details">2016-10-01 安全性修補程å¼ç‰ç´š — 資安æ¼æ´žè©³æƒ…</h2> -<p>下列å„節é‡å° 2016-10-01 安全性修補程å¼ç‰ç´šé©ç”¨çš„å„é …å®‰å…¨æ€§æ¼æ´žæ供了詳細資訊，包括å•é¡Œèªªæ˜Žã€åš´é‡ç¨‹åº¦è©•å®šåŽŸå› ，以åŠä¸€ä»½æ¼æ´žè³‡è¨Šè¡¨ï¼Œé¡¯ç¤ºæ¼æ´žçš„ CVEã€ç›¸é—œåƒè€ƒè³‡æ–™ã€åš´é‡ç¨‹åº¦ã€æ›´æ–°çš„ Nexus è£ç½®ã€æ›´æ–°çš„ AOSP 版本 (在é©ç”¨æƒ…æ³ä¸‹) å’Œå›žå ±æ—¥æœŸã€‚å¦‚æžœç›¸é—œéŒ¯èª¤æœ‰å…¬é–‹è®Šæ›´ï¼Œè©²éŒ¯èª¤ ID 會連çµåˆ°ç›¸å°æ‡‰çš„變更 (例如 AOSP 變更清單)ã€‚å¦‚æžœå–®ä¸€éŒ¯èª¤æœ‰å¤šé …ç›¸é—œè®Šæ›´ï¼Œå…¶ä»–åƒè€ƒè³‡æ–™å¯é€éŽè©²éŒ¯èª¤ ID 後é¢çš„編號連çµé–‹å•Ÿã€‚</p> +<h2 id="2016-10-01-details">2016-10-01 安全性修補程å¼ç‰ç´š - 資安æ¼æ´žè©³æƒ…</h2> +<p> +下列å„節é‡å° 2016-10-01 安全性修補程å¼ç‰ç´šé©ç”¨çš„å„é …å®‰å…¨æ€§æ¼æ´žæ供了詳細資訊，å¦å¤–也附上了å•é¡Œèªªæ˜Žã€åš´é‡ç¨‹åº¦è©•å®šåŽŸå› 和一份 CVE 資訊表，其ä¸åŒ…括了相關åƒè€ƒè³‡æ–™ã€åš´é‡ç¨‹åº¦ã€æ›´æ–°çš„ Nexus è£ç½®ã€æ›´æ–°çš„ Android 開放原始碼計劃版本 (在é©ç”¨æƒ…æ³ä¸‹) å’Œå›žå ±æ—¥æœŸã€‚å‡å¦‚相關錯誤有公開變更，該錯誤 ID 會連çµåˆ°ç›¸å°æ‡‰çš„變更 (例如 Android 開放原始碼計劃變更清單)ã€‚å¦‚æžœå–®ä¸€éŒ¯èª¤æœ‰å¤šé …ç›¸é—œè®Šæ›´ï¼Œæ‚¨å¯ä»¥é€éŽè©²éŒ¯èª¤ ID 後é¢çš„編號連çµé–‹å•Ÿé¡å¤–çš„åƒè€ƒè³‡æ–™ã€‚</p> <h3 id="eopv-in-servicemanager">ServiceManager ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> <p> ServiceManager ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼è¨»å†Šé€šå¸¸æ˜¯ç”±ç²å¾—æŽˆæ¬Šçš„ç¨‹åº (例如 system_server) 所æ供的任何æœå‹™ã€‚由於這個å•é¡Œå¯èƒ½æœƒå…許冒用他人身分的æœå‹™ï¼Œå› æ¤åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚ @@ -103,7 +105,7 @@ ServiceManager ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼è¨»å† <th>åƒè€ƒè³‡æ–™</th> <th>åš´é‡ç¨‹åº¦</th> <th>æ›´æ–°çš„ Nexus è£ç½®</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -133,7 +135,7 @@ ServiceManager ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼è¨»å† <th>åƒè€ƒè³‡æ–™</th> <th>åš´é‡ç¨‹åº¦</th> <th>æ›´æ–°çš„ Nexus è£ç½®</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -147,7 +149,7 @@ ServiceManager ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼è¨»å† </tr> </tbody></table> <h3 id="eopv-in-mediaserver">媒體伺æœå™¨ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> -<p>媒體伺æœå™¨ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨ç²å¾—授權的程åºç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚由於這個å•é¡Œå¯ç”¨æ–¼å–å¾—æŸäº›é€²éšŽåŠŸèƒ½çš„本機å˜å–權，第三方應用程å¼é€šå¸¸ç„¡æ³•å˜å–é€™é¡žåŠŸèƒ½ï¼Œå› æ¤åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚ +<p>媒體伺æœå™¨ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨ç²å¾—授權的程åºç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚由於有心人士å¯åˆ©ç”¨é€™å€‹æ¼æ´žä¾†å–å¾—æŸäº›é€²éšŽåŠŸèƒ½çš„本機å˜å–權，第三方應用程å¼é€šå¸¸ç„¡æ³•å˜å–é€™é¡žåŠŸèƒ½ï¼Œå› æ¤åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚ </p> <table> <colgroup><col width="18%" /> @@ -161,7 +163,7 @@ ServiceManager ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼è¨»å† <th>åƒè€ƒè³‡æ–™</th> <th>åš´é‡ç¨‹åº¦</th> <th>æ›´æ–°çš„ Nexus è£ç½®</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -195,7 +197,7 @@ ServiceManager ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼è¨»å† </tbody></table> <h3 id="eopv-in-zygote-process">Zygote 程åºä¸çš„權é™å‡ç´šæ¼æ´ž</h3> <p> -Zygote 程åºä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨ç²å¾—授權的程åºç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚由於這個å•é¡Œå¯ç”¨æ–¼å–å¾—æŸäº›é€²éšŽåŠŸèƒ½çš„本機å˜å–權，第三方應用程å¼é€šå¸¸ç„¡æ³•å˜å–é€™é¡žåŠŸèƒ½ï¼Œå› æ¤åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚ +Zygote 程åºä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨ç²å¾—授權的程åºç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚由於有心人士å¯åˆ©ç”¨é€™å€‹æ¼æ´žä¾†å–å¾—æŸäº›é€²éšŽåŠŸèƒ½çš„本機å˜å–權，第三方應用程å¼é€šå¸¸ç„¡æ³•å˜å–é€™é¡žåŠŸèƒ½ï¼Œå› æ¤åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚ </p> <table> <colgroup><col width="18%" /> @@ -209,7 +211,7 @@ Zygote 程åºä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨ç²å <th>åƒè€ƒè³‡æ–™</th> <th>åš´é‡ç¨‹åº¦</th> <th>æ›´æ–°çš„ Nexus è£ç½®</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -219,12 +221,12 @@ Zygote 程åºä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨ç²å <td>高</td> <td>所有 Nexus è£ç½®</td> <td>4.4.4ã€5.0.2ã€5.1.1ã€6.0ã€6.0.1ã€7.0</td> - <td>2016 å¹´ 7 月 16 æ—¥</td> + <td>2016 å¹´ 7 月 12 æ—¥</td> </tr> </tbody></table> <h3 id="eopv-in-framework-apis">Framework API ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> <p> -Framework API ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨ç²å¾—授權的程åºç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚由於這個å•é¡Œå¯ç”¨æ–¼å–å¾—æŸäº›é€²éšŽåŠŸèƒ½çš„本機å˜å–權，第三方應用程å¼é€šå¸¸ç„¡æ³•å˜å–é€™é¡žåŠŸèƒ½ï¼Œå› æ¤åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚ +Framework API ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨ç²å¾—授權的程åºç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚由於有心人士å¯åˆ©ç”¨é€™å€‹æ¼æ´žä¾†å–å¾—æŸäº›é€²éšŽåŠŸèƒ½çš„本機å˜å–權，第三方應用程å¼é€šå¸¸ç„¡æ³•å˜å–é€™é¡žåŠŸèƒ½ï¼Œå› æ¤åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚ </p> <table> <colgroup><col width="18%" /> @@ -238,7 +240,7 @@ Framework API ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨ç² <th>åƒè€ƒè³‡æ–™</th> <th>åš´é‡ç¨‹åº¦</th> <th>æ›´æ–°çš„ Nexus è£ç½®</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -253,7 +255,7 @@ Framework API ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨ç² </tbody></table> <h3 id="eopv-in-telephony">電話通訊系統ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> <p> -電話通訊系統元件ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨ç²å¾—授權的程åºç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚由於這個å•é¡Œå¯ç”¨æ–¼å–å¾—æŸäº›é€²éšŽåŠŸèƒ½çš„本機å˜å–權，第三方應用程å¼é€šå¸¸ç„¡æ³•å˜å–é€™é¡žåŠŸèƒ½ï¼Œå› æ¤åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚ +電話通訊系統元件ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨ç²å¾—授權的程åºç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚由於有心人士å¯åˆ©ç”¨é€™å€‹æ¼æ´žä¾†å–å¾—æŸäº›é€²éšŽåŠŸèƒ½çš„本機å˜å–權，第三方應用程å¼é€šå¸¸ç„¡æ³•å˜å–é€™é¡žåŠŸèƒ½ï¼Œå› æ¤åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚ </p> <table> <colgroup><col width="18%" /> @@ -267,7 +269,7 @@ Framework API ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨ç² <th>åƒè€ƒè³‡æ–™</th> <th>åš´é‡ç¨‹åº¦</th> <th>æ›´æ–°çš„ Nexus è£ç½®</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -282,7 +284,7 @@ Framework API ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨ç² </tbody></table> <h3 id="eopv-in-camera-service">相機æœå‹™ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> <p> -相機æœå‹™ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨ç²å¾—授權的程åºç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚由於這個å•é¡Œå¯ç”¨æ–¼å–å¾—æŸäº›é€²éšŽåŠŸèƒ½çš„本機å˜å–權，第三方應用程å¼é€šå¸¸ç„¡æ³•å˜å–é€™é¡žåŠŸèƒ½ï¼Œå› æ¤åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚ +相機æœå‹™ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨ç²å¾—授權的程åºç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚由於有心人士å¯åˆ©ç”¨é€™å€‹æ¼æ´žä¾†å–å¾—æŸäº›é€²éšŽåŠŸèƒ½çš„本機å˜å–權，第三方應用程å¼é€šå¸¸ç„¡æ³•å˜å–é€™é¡žåŠŸèƒ½ï¼Œå› æ¤åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚ </p> <table> <colgroup><col width="18%" /> @@ -296,7 +298,7 @@ Framework API ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨ç² <th>åƒè€ƒè³‡æ–™</th> <th>åš´é‡ç¨‹åº¦</th> <th>æ›´æ–°çš„ Nexus è£ç½®</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -334,7 +336,7 @@ Framework API ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨ç² <th>åƒè€ƒè³‡æ–™</th> <th>åš´é‡ç¨‹åº¦</th> <th>æ›´æ–°çš„ Nexus è£ç½®</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -347,9 +349,9 @@ Framework API ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨ç² <td>2016 å¹´ 8 月 5 æ—¥</td> </tr> </tbody></table> -<h3 id="information-disclosure-vulnerability-in-aosp-mail">AOSP Mail ä¸çš„資訊外洩æ¼æ´ž</h3> +<h3 id="information-disclosure-vulnerability-in-aosp-mail">Android 開放原始碼計劃 Mail ä¸çš„資訊外洩æ¼æ´ž</h3> <p> -AOSP Mail ä¸çš„資訊外洩æ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼è¦é¿ä½œæ¥ç³»çµ±ç‚ºäº†å°‡æ‡‰ç”¨ç¨‹å¼è³‡æ–™èˆ‡å…¶ä»–應用程å¼éš”離而採å–的防è·æŽªæ–½ã€‚由於這個å•é¡Œå¯ç”¨æ–¼åœ¨æœªç²æŽˆæ¬Šçš„情æ³ä¸‹å˜å–è³‡æ–™ï¼Œå› æ¤åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚ +Android 開放原始碼計劃 Mail ä¸çš„資訊外洩æ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼è¦é¿ä½œæ¥ç³»çµ±ç‚ºäº†å°‡æ‡‰ç”¨ç¨‹å¼è³‡æ–™èˆ‡å…¶ä»–應用程å¼éš”離而採å–的防è·æŽªæ–½ã€‚由於這個å•é¡Œå¯èƒ½å°Žè‡´æœ‰å¿ƒäººå£«åœ¨æœªç²æŽˆæ¬Šçš„情æ³ä¸‹å˜å–è³‡æ–™ï¼Œå› æ¤åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚ </p> <table> <colgroup><col width="18%" /> @@ -363,7 +365,7 @@ AOSP Mail ä¸çš„資訊外洩æ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼è¦é¿ä½œæ <th>åƒè€ƒè³‡æ–™</th> <th>åš´é‡ç¨‹åº¦</th> <th>æ›´æ–°çš„ Nexus è£ç½®</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -392,7 +394,7 @@ Wi-Fi ä¸çš„拒絕æœå‹™æ¼æ´žå¯èƒ½æœƒè®“é„°è¿‘æœ¬æ©Ÿçš„æ”»æ“Šè€…å»ºç«‹ç„¡ç·šåŸ <th>åƒè€ƒè³‡æ–™</th> <th>åš´é‡ç¨‹åº¦</th> <th>æ›´æ–°çš„ Nexus è£ç½®</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -421,7 +423,7 @@ GPS 元件ä¸çš„拒絕æœå‹™æ¼æ´žå¯èƒ½æœƒè®“é ç«¯æ”»æ“Šè€…é€ æˆè£ç½®åœæ¢é <th>åƒè€ƒè³‡æ–™</th> <th>åš´é‡ç¨‹åº¦</th> <th>æ›´æ–°çš„ Nexus è£ç½®</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -450,7 +452,7 @@ GPS 元件ä¸çš„拒絕æœå‹™æ¼æ´žå¯èƒ½æœƒè®“é ç«¯æ”»æ“Šè€…é€ æˆè£ç½®åœæ¢é <th>åƒè€ƒè³‡æ–™</th> <th>åš´é‡ç¨‹åº¦</th> <th>æ›´æ–°çš„ Nexus è£ç½®</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -465,7 +467,7 @@ GPS 元件ä¸çš„拒絕æœå‹™æ¼æ´žå¯èƒ½æœƒè®“é ç«¯æ”»æ“Šè€…é€ æˆè£ç½®åœæ¢é </tbody></table> <h3 id="eopv-in-framework-listener">Framework 接è½ç¨‹å¼ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> <p> -Framework 接è½ç¨‹å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨ç²å¾—授權的程åºç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚ç”±æ–¼é€™ç¨®æ”»æ“Šå¿…é ˆå…ˆç ´å£žç‰¹å®šç²æŽˆæ¬Šçš„程åºæ‰èƒ½åŸ·è¡Œï¼Œå› æ¤é€™å€‹å•é¡Œçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œä¸ã€ã€‚ +Framework 接è½ç¨‹å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨ç²å¾—授權的程åºç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚ç”±æ–¼é€™ç¨®æ”»æ“Šå¿…é ˆå…ˆç ´è§£å…·æœ‰ç‰¹å®šæ¬Šé™çš„程åºæ‰èƒ½åŸ·è¡Œï¼Œå› æ¤é€™å€‹å•é¡Œçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œä¸ã€ã€‚ </p> <table> <colgroup><col width="18%" /> @@ -479,7 +481,7 @@ Framework 接è½ç¨‹å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å <th>åƒè€ƒè³‡æ–™</th> <th>åš´é‡ç¨‹åº¦</th> <th>æ›´æ–°çš„ Nexus è£ç½®</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -494,7 +496,7 @@ Framework 接è½ç¨‹å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å </tbody></table> <h3 id="eopv-in-telephony-2">電話通訊系統ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> <p> -電話通訊系統ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨ç²å¾—授權的程åºç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚ç”±æ–¼é€™ç¨®æ”»æ“Šå¿…é ˆå…ˆç ´å£žç‰¹å®šç²æŽˆæ¬Šçš„程åºæ‰èƒ½åŸ·è¡Œï¼Œå› æ¤é€™å€‹å•é¡Œçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œä¸ã€ã€‚ +電話通訊系統ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨ç²å¾—授權的程åºç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚ç”±æ–¼é€™ç¨®æ”»æ“Šå¿…é ˆå…ˆç ´è§£å…·æœ‰ç‰¹å®šæ¬Šé™çš„程åºæ‰èƒ½åŸ·è¡Œï¼Œå› æ¤é€™å€‹å•é¡Œçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œä¸ã€ã€‚ </p> <table> <colgroup><col width="18%" /> @@ -508,7 +510,7 @@ Framework 接è½ç¨‹å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å <th>åƒè€ƒè³‡æ–™</th> <th>åš´é‡ç¨‹åº¦</th> <th>æ›´æ–°çš„ Nexus è£ç½®</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -537,7 +539,7 @@ Framework 接è½ç¨‹å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å <th>åƒè€ƒè³‡æ–™</th> <th>åš´é‡ç¨‹åº¦</th> <th>æ›´æ–°çš„ Nexus è£ç½®</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -552,7 +554,7 @@ Framework 接è½ç¨‹å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å </tbody></table> <h3 id="information-disclosure-vulnerability-in-mediaserver">媒體伺æœå™¨ä¸çš„資訊外洩æ¼æ´ž</h3> <p> -媒體伺æœå™¨ä¸çš„資訊外洩æ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼å˜å–其權é™ç‰ç´šä»¥å¤–的資料。由於這個å•é¡Œå¯èƒ½å°Žè‡´æœ‰å¿ƒäººå£«åœ¨æœªç²æŽˆæ¬Šçš„情æ³ä¸‹å˜å–æ©Ÿå¯†è³‡æ–™ï¼Œå› æ¤åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œä¸ã€ã€‚ +媒體伺æœå™¨ä¸çš„資訊外洩æ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼å˜å–其權é™ç¯„åœä»¥å¤–的資料。由於這個å•é¡Œå¯èƒ½æœƒè®“有心人士在未ç²æŽˆæ¬Šçš„情æ³ä¸‹å˜å–æ©Ÿå¯†è³‡æ–™ï¼Œå› æ¤åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œä¸ã€ã€‚ </p> <table> <colgroup><col width="18%" /> @@ -566,7 +568,7 @@ Framework 接è½ç¨‹å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å <th>åƒè€ƒè³‡æ–™</th> <th>åš´é‡ç¨‹åº¦</th> <th>æ›´æ–°çš„ Nexus è£ç½®</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -595,7 +597,7 @@ Wi-Fi æœå‹™ä¸çš„拒絕æœå‹™æ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼ç¦æ¢ç™ <th>åƒè€ƒè³‡æ–™</th> <th>åš´é‡ç¨‹åº¦</th> <th>æ›´æ–°çš„ Nexus è£ç½®</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -608,11 +610,12 @@ Wi-Fi æœå‹™ä¸çš„拒絕æœå‹™æ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼ç¦æ¢ç™ <td>Google 內部資訊</td> </tr> </tbody></table> -<h2 id="2016-10-05-details">2016-10-05 安全性修補程å¼ç‰ç´š — 資安æ¼æ´žè©³æƒ…</h2> -<p>下列å„節é‡å° 2016-10-05 安全性修補程å¼ç‰ç´šé©ç”¨çš„å„é …å®‰å…¨æ€§æ¼æ´žæ供了詳細資訊。包括å•é¡Œèªªæ˜Žã€åš´é‡ç¨‹åº¦è©•å®šåŽŸå› ，以åŠä¸€ä»½æ¼æ´žè³‡è¨Šè¡¨ï¼Œé¡¯ç¤ºæ¼æ´žçš„ CVEã€ç›¸é—œåƒè€ƒè³‡æ–™ã€åš´é‡ç¨‹åº¦ã€æ›´æ–°çš„ Nexus è£ç½®ã€æ›´æ–°çš„ AOSP 版本 (在é©ç”¨æƒ…æ³ä¸‹) å’Œå›žå ±æ—¥æœŸã€‚å¦‚æžœç›¸é—œéŒ¯èª¤æœ‰å…¬é–‹è®Šæ›´ï¼Œè©²éŒ¯èª¤ ID 會連çµåˆ°ç›¸å°æ‡‰çš„變更 (例如 AOSP 變更清單)ã€‚å¦‚æžœå–®ä¸€éŒ¯èª¤æœ‰å¤šé …ç›¸é—œè®Šæ›´ï¼Œå…¶ä»–åƒè€ƒè³‡æ–™å¯é€éŽè©²éŒ¯èª¤ ID 後é¢çš„編號連çµé–‹å•Ÿã€‚</p> +<h2 id="2016-10-05-details">2016-10-05 安全性修補程å¼ç‰ç´š - 資安æ¼æ´žè©³æƒ…</h2> +<p> +下列å„節é‡å° 2016-10-05 安全性修補程å¼ç‰ç´šé©ç”¨çš„å„é …å®‰å…¨æ€§æ¼æ´žæ供了詳細資訊，å¦å¤–也附上了å•é¡Œèªªæ˜Žã€åš´é‡ç¨‹åº¦è©•å®šåŽŸå› 和一份 CVE 資訊表，其ä¸åŒ…括了相關åƒè€ƒè³‡æ–™ã€åš´é‡ç¨‹åº¦ã€æ›´æ–°çš„ Nexus è£ç½®ã€æ›´æ–°çš„ Android 開放原始碼計劃版本 (在é©ç”¨æƒ…æ³ä¸‹) å’Œå›žå ±æ—¥æœŸã€‚å‡å¦‚相關錯誤有公開變更，該錯誤 ID 會連çµåˆ°ç›¸å°æ‡‰çš„變更 (例如 Android 開放原始碼計劃變更清單)ã€‚å¦‚æžœå–®ä¸€éŒ¯èª¤æœ‰å¤šé …ç›¸é—œè®Šæ›´ï¼Œæ‚¨å¯ä»¥é€éŽè©²éŒ¯èª¤ ID 後é¢çš„編號連çµé–‹å•Ÿé¡å¤–çš„åƒè€ƒè³‡æ–™ã€‚</p> <h3 id="remote-code-execution-vulnerability-in-kernel-asn-1-decoder">æ ¸å¿ƒ ASN.1 解碼器ä¸çš„é 端程å¼ç¢¼åŸ·è¡Œæ¼æ´ž</h3> <p> -æ ¸å¿ƒ ASN.1 解碼器ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚由於這個å•é¡Œå¯èƒ½å°Žè‡´æœ¬æ©Ÿè£ç½®çš„å®‰å…¨æ€§å¾¹åº•è¢«ç ´å£žï¼Œä½¿è£ç½®å¿…é ˆä»¥é‚„åŽŸ (Re-flash) 作æ¥ç³»çµ±çš„æ–¹å¼æ‰èƒ½ä¿®å¾©ï¼Œå› æ¤åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œæœ€é«˜ã€ã€‚ +æ ¸å¿ƒ ASN.1 解碼器ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚由於這個å•é¡Œå¯èƒ½å°Žè‡´æœ¬æ©Ÿè£ç½®çš„å®‰å…¨æ€§å¾¹åº•è¢«ç ´å£žï¼Œé€ æˆä½¿ç”¨è€…å¿…é ˆä»¥é‚„åŽŸ (Reflash) 作æ¥ç³»çµ±çš„æ–¹å¼æ‰èƒ½ä¿®å¾©è£ç½®ï¼Œå› æ¤åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œæœ€é«˜ã€ã€‚ </p> <table> <colgroup><col width="19%" /> @@ -639,7 +642,7 @@ Wi-Fi æœå‹™ä¸çš„拒絕æœå‹™æ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼ç¦æ¢ç™ </tbody></table> <h3 id="remote-code-execution-vulnerability-in-kernel-networking-subsystem">æ ¸å¿ƒç¶²è·¯å系統ä¸çš„é 端程å¼ç¢¼åŸ·è¡Œæ¼æ´ž</h3> <p> -æ ¸å¿ƒç¶²è·¯å系統ä¸çš„é 端程å¼ç¢¼åŸ·è¡Œæ¼æ´žå¯èƒ½æœƒè®“é ç«¯æ”»æ“Šè€…åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚由於這個å•é¡Œå¯èƒ½å°Žè‡´æœ¬æ©Ÿè£ç½®çš„å®‰å…¨æ€§å¾¹åº•è¢«ç ´å£žï¼Œä½¿è£ç½®å¿…é ˆä»¥é‚„åŽŸ (Re-flash) 作æ¥ç³»çµ±çš„æ–¹å¼æ‰èƒ½ä¿®å¾©ï¼Œå› æ¤åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œæœ€é«˜ã€ã€‚ +æ ¸å¿ƒç¶²è·¯å系統ä¸çš„é 端程å¼ç¢¼åŸ·è¡Œæ¼æ´žå¯èƒ½æœƒè®“é ç«¯æ”»æ“Šè€…åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚由於這個å•é¡Œå¯èƒ½å°Žè‡´æœ¬æ©Ÿè£ç½®çš„å®‰å…¨æ€§å¾¹åº•è¢«ç ´å£žï¼Œé€ æˆä½¿ç”¨è€…å¿…é ˆä»¥é‚„åŽŸ (Reflash) 作æ¥ç³»çµ±çš„æ–¹å¼æ‰èƒ½ä¿®å¾©è£ç½®ï¼Œå› æ¤åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œæœ€é«˜ã€ã€‚ </p> <table> <colgroup><col width="19%" /> @@ -665,7 +668,7 @@ Wi-Fi æœå‹™ä¸çš„拒絕æœå‹™æ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼ç¦æ¢ç™ </tbody></table> <h3 id="eopv-in-mediatek-video-driver">MediaTek 視訊驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> <p> -MediaTek 視訊驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚由於這個å•é¡Œå¯èƒ½å°Žè‡´æœ¬æ©Ÿè£ç½®çš„å®‰å…¨æ€§å¾¹åº•è¢«ç ´å£žï¼Œä½¿è£ç½®å¿…é ˆä»¥é‚„åŽŸ (Re-flash) 作æ¥ç³»çµ±çš„æ–¹å¼æ‰èƒ½ä¿®å¾©ï¼Œå› æ¤åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œæœ€é«˜ã€ã€‚ +MediaTek 視訊驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚由於這個å•é¡Œå¯èƒ½å°Žè‡´æœ¬æ©Ÿè£ç½®çš„å®‰å…¨æ€§å¾¹åº•è¢«ç ´å£žï¼Œé€ æˆä½¿ç”¨è€…å¿…é ˆä»¥é‚„åŽŸ (Reflash) 作æ¥ç³»çµ±çš„æ–¹å¼æ‰èƒ½ä¿®å¾©è£ç½®ï¼Œå› æ¤åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œæœ€é«˜ã€ã€‚ </p> <table> <colgroup><col width="19%" /> @@ -689,11 +692,12 @@ MediaTek 視訊驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„æ‡‰ç” <td>2016 å¹´ 7 月 6 æ—¥</td> </tr> </tbody></table> -<p>* 這個å•é¡Œçš„修補程å¼ä¸¦æœªå…¬é–‹æ供，而是直接整åˆåœ¨æœ€æ–°çš„ Nexus è£ç½®å°ˆç”¨é©…動程å¼çš„安è£æª”ä¸ã€‚您å¯ä»¥å‰å¾€ <a href="https://developers.google.com/android/nexus/drivers">Google Developers 網站</a>下載這些驅動程å¼ã€‚ +<p> +* 這個å•é¡Œçš„修補程å¼ä¸¦æœªé–‹æ”¾çµ¦ä¸€èˆ¬ä½¿ç”¨è€…下載，相關的更新已直接整åˆåœ¨æœ€æ–°çš„ Nexus è£ç½®å°ˆç”¨é©…動程å¼çš„安è£æª”ä¸ã€‚您å¯ä»¥å‰å¾€ <a href="https://developers.google.com/android/nexus/drivers">Google Developers 網站</a>下載這些驅動程å¼ã€‚ </p> <h3 id="eopv-in-kernel-shared-memory-driver">æ ¸å¿ƒå…±ç”¨è¨˜æ†¶é«”é©…å‹•ç¨‹å¼ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> <p> -æ ¸å¿ƒå…±ç”¨è¨˜æ†¶é«”é©…å‹•ç¨‹å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚由於這個å•é¡Œå¯èƒ½å°Žè‡´æœ¬æ©Ÿè£ç½®çš„å®‰å…¨æ€§å¾¹åº•è¢«ç ´å£žï¼Œä½¿è£ç½®å¿…é ˆä»¥é‚„åŽŸ (Re-flash) 作æ¥ç³»çµ±çš„æ–¹å¼æ‰èƒ½ä¿®å¾©ï¼Œå› æ¤åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œæœ€é«˜ã€ã€‚ +æ ¸å¿ƒå…±ç”¨è¨˜æ†¶é«”é©…å‹•ç¨‹å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚由於這個å•é¡Œå¯èƒ½å°Žè‡´æœ¬æ©Ÿè£ç½®çš„å®‰å…¨æ€§å¾¹åº•è¢«ç ´å£žï¼Œé€ æˆä½¿ç”¨è€…å¿…é ˆä»¥é‚„åŽŸ (Reflash) 作æ¥ç³»çµ±çš„æ–¹å¼æ‰èƒ½ä¿®å¾©è£ç½®ï¼Œå› æ¤åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œæœ€é«˜ã€ã€‚ </p> <table> <colgroup><col width="19%" /> @@ -757,11 +761,12 @@ MediaTek 視訊驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„æ‡‰ç” <td>Qualcomm 內部資訊</td> </tr> </tbody></table> -<p>* 這個å•é¡Œçš„修補程å¼ä¸¦æœªå…¬é–‹æ供，而是直接整åˆåœ¨æœ€æ–°çš„ Nexus è£ç½®å°ˆç”¨é©…動程å¼çš„安è£æª”ä¸ã€‚您å¯ä»¥å‰å¾€ <a href="https://developers.google.com/android/nexus/drivers">Google Developers 網站</a>下載這些驅動程å¼ã€‚ +<p> +* 這個å•é¡Œçš„修補程å¼ä¸¦æœªé–‹æ”¾çµ¦ä¸€èˆ¬ä½¿ç”¨è€…下載，相關的更新已直接整åˆåœ¨æœ€æ–°çš„ Nexus è£ç½®å°ˆç”¨é©…動程å¼çš„安è£æª”ä¸ã€‚您å¯ä»¥å‰å¾€ <a href="https://developers.google.com/android/nexus/drivers">Google Developers 網站</a>下載這些驅動程å¼ã€‚ </p> <h3 id="eopv-in-qualcomm-networking-component">Qualcomm 網路元件ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> <p> -Qualcomm 網路元件ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚ç”±æ–¼é€™ç¨®æ”»æ“Šå¿…é ˆå…ˆç ´å£žç‰¹å®šç²æŽˆæ¬Šçš„程åºæ‰èƒ½åŸ·è¡Œï¼Œå› æ¤é€™å€‹å•é¡Œçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚ +Qualcomm 網路元件ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚ç”±æ–¼é€™ç¨®æ”»æ“Šå¿…é ˆå…ˆç ´è§£å…·æœ‰ç‰¹å®šæ¬Šé™çš„程åºæ‰èƒ½åŸ·è¡Œï¼Œå› æ¤é€™å€‹å•é¡Œçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚ </p> <table> <colgroup><col width="19%" /> @@ -787,7 +792,7 @@ Qualcomm 網路元件ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„æ‡‰ç”¨ç¨‹å¼ </tbody></table> <h3 id="eopv-in-nvidia-mmc-test-driver">NVIDIA MMC 測試驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> <p> -NVIDIA MMC 測試驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚ç”±æ–¼é€™ç¨®æ”»æ“Šå¿…é ˆå…ˆç ´å£žç‰¹å®šç²æŽˆæ¬Šçš„程åºæ‰èƒ½åŸ·è¡Œï¼Œå› æ¤é€™å€‹å•é¡Œçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚ +NVIDIA MMC 測試驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚ç”±æ–¼é€™ç¨®æ”»æ“Šå¿…é ˆå…ˆç ´è§£å…·æœ‰ç‰¹å®šæ¬Šé™çš„程åºæ‰èƒ½åŸ·è¡Œï¼Œå› æ¤é€™å€‹å•é¡Œçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚ </p> <table> <colgroup><col width="19%" /> @@ -811,10 +816,11 @@ NVIDIA MMC 測試驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應 <td>2016 å¹´ 5 月 12 æ—¥</td> </tr> </tbody></table> -<p>* 這個å•é¡Œçš„修補程å¼ä¸¦æœªå…¬é–‹æ供，而是直接整åˆåœ¨æœ€æ–°çš„ Nexus è£ç½®å°ˆç”¨é©…動程å¼çš„安è£æª”ä¸ã€‚您å¯ä»¥å‰å¾€ <a href="https://developers.google.com/android/nexus/drivers">Google Developers 網站</a>下載這些驅動程å¼ã€‚ +<p> +* 這個å•é¡Œçš„修補程å¼ä¸¦æœªé–‹æ”¾çµ¦ä¸€èˆ¬ä½¿ç”¨è€…下載，相關的更新已直接整åˆåœ¨æœ€æ–°çš„ Nexus è£ç½®å°ˆç”¨é©…動程å¼çš„安è£æª”ä¸ã€‚您å¯ä»¥å‰å¾€ <a href="https://developers.google.com/android/nexus/drivers">Google Developers 網站</a>下載這些驅動程å¼ã€‚ </p> <h3 id="eopv-in-qsee-communicator-driver">Qualcomm QSEE 通訊工具驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> -<p>Qualcomm QSEE 通訊工具驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚ç”±æ–¼é€™ç¨®æ”»æ“Šå¿…é ˆå…ˆç ´å£žç‰¹å®šç²æŽˆæ¬Šçš„程åºæ‰èƒ½åŸ·è¡Œï¼Œå› æ¤é€™å€‹å•é¡Œçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚ +<p>Qualcomm QSEE 通訊工具驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚ç”±æ–¼é€™ç¨®æ”»æ“Šå¿…é ˆå…ˆç ´è§£å…·æœ‰ç‰¹å®šæ¬Šé™çš„程åºæ‰èƒ½åŸ·è¡Œï¼Œå› æ¤é€™å€‹å•é¡Œçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚ </p> <table> <colgroup><col width="19%" /> @@ -839,7 +845,7 @@ NVIDIA MMC 測試驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應 </tr> </tbody></table> <h3 id="eopv-in-mediaserver-2">媒體伺æœå™¨ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> -<p>媒體伺æœå™¨ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨ç²å¾—授權的程åºç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚由於這個å•é¡Œå¯ç”¨æ–¼å–å¾—æŸäº›é€²éšŽåŠŸèƒ½çš„本機å˜å–權，第三方應用程å¼é€šå¸¸ç„¡æ³•å˜å–é€™é¡žåŠŸèƒ½ï¼Œå› æ¤åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚ +<p>媒體伺æœå™¨ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨ç²å¾—授權的程åºç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚由於有心人士å¯åˆ©ç”¨é€™å€‹æ¼æ´žä¾†å–å¾—æŸäº›é€²éšŽåŠŸèƒ½çš„本機å˜å–權，第三方應用程å¼é€šå¸¸ç„¡æ³•å˜å–é€™é¡žåŠŸèƒ½ï¼Œå› æ¤åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚ </p> <table> <colgroup><col width="19%" /> @@ -871,11 +877,12 @@ NVIDIA MMC 測試驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應 <td>2016 å¹´ 6 月 14 æ—¥</td> </tr> </tbody></table> -<p>* 這個å•é¡Œçš„修補程å¼ä¸¦æœªå…¬é–‹æ供，而是直接整åˆåœ¨æœ€æ–°çš„ Nexus è£ç½®å°ˆç”¨é©…動程å¼çš„安è£æª”ä¸ã€‚您å¯ä»¥å‰å¾€ <a href="https://developers.google.com/android/nexus/drivers">Google Developers 網站</a>下載這些驅動程å¼ã€‚ +<p> +* 這個å•é¡Œçš„修補程å¼ä¸¦æœªé–‹æ”¾çµ¦ä¸€èˆ¬ä½¿ç”¨è€…下載，相關的更新已直接整åˆåœ¨æœ€æ–°çš„ Nexus è£ç½®å°ˆç”¨é©…動程å¼çš„安è£æª”ä¸ã€‚您å¯ä»¥å‰å¾€ <a href="https://developers.google.com/android/nexus/drivers">Google Developers 網站</a>下載這些驅動程å¼ã€‚ </p> <h3 id="eopv-in-qualcomm-camera-driver">Qualcomm 相機驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> <p> -Qualcomm 相機驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚ç”±æ–¼é€™ç¨®æ”»æ“Šå¿…é ˆå…ˆç ´å£žç‰¹å®šç²æŽˆæ¬Šçš„程åºæ‰èƒ½åŸ·è¡Œï¼Œå› æ¤é€™å€‹å•é¡Œçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚ +Qualcomm 相機驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚ç”±æ–¼é€™ç¨®æ”»æ“Šå¿…é ˆå…ˆç ´è§£å…·æœ‰ç‰¹å®šæ¬Šé™çš„程åºæ‰èƒ½åŸ·è¡Œï¼Œå› æ¤é€™å€‹å•é¡Œçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚ </p> <table> <colgroup><col width="19%" /> @@ -904,12 +911,12 @@ Qualcomm 相機驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„æ‡‰ç” <a href="https://source.codeaurora.org/quic/la/kernel/msm-3.10/commit/?id=27fbeb6b025d5d46ccb0497cbed4c6e78ed1c5cc">QC-CR#789704</a></td> <td>高</td> <td>Nexus 5ã€Nexus 5Xã€Nexus 6ã€Nexus 6Pã€Android One</td> - <td>2016 å¹´ 7 月 16 æ—¥</td> + <td>2016 å¹´ 7 月 12 æ—¥</td> </tr> </tbody></table> <h3 id="eopv-in-qualcomm-sound-driver">Qualcomm 音效驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> <p> -Qualcomm 音效驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚ç”±æ–¼é€™ç¨®æ”»æ“Šå¿…é ˆå…ˆç ´å£žç‰¹å®šç²æŽˆæ¬Šçš„程åºæ‰èƒ½åŸ·è¡Œï¼Œå› æ¤é€™å€‹å•é¡Œçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚ +Qualcomm 音效驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚ç”±æ–¼é€™ç¨®æ”»æ“Šå¿…é ˆå…ˆç ´è§£å…·æœ‰ç‰¹å®šæ¬Šé™çš„程åºæ‰èƒ½åŸ·è¡Œï¼Œå› æ¤é€™å€‹å•é¡Œçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚ </p> <table> <colgroup><col width="19%" /> @@ -935,7 +942,7 @@ Qualcomm 音效驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„æ‡‰ç” </tr> </tbody></table> <h3 id="eopv-in-qualcomm-crypto-engine-driver">Qualcomm åŠ å¯†å¼•æ“Žé©…å‹•ç¨‹å¼ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> -<p>Qualcomm åŠ å¯†å¼•æ“Žé©…å‹•ç¨‹å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚ç”±æ–¼é€™ç¨®æ”»æ“Šå¿…é ˆå…ˆç ´å£žç‰¹å®šç²æŽˆæ¬Šçš„程åºæ‰èƒ½åŸ·è¡Œï¼Œå› æ¤é€™å€‹å•é¡Œçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚ +<p>Qualcomm åŠ å¯†å¼•æ“Žé©…å‹•ç¨‹å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚ç”±æ–¼é€™ç¨®æ”»æ“Šå¿…é ˆå…ˆç ´è§£å…·æœ‰ç‰¹å®šæ¬Šé™çš„程åºæ‰èƒ½åŸ·è¡Œï¼Œå› æ¤é€™å€‹å•é¡Œçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚ </p> <table> <colgroup><col width="19%" /> @@ -969,7 +976,7 @@ Qualcomm 音效驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„æ‡‰ç” </tbody></table> <h3 id="eopv-in-mediatek-video-driver-2">MediaTek 視訊驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> <p> -MediaTek 視訊驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚ç”±æ–¼é€™ç¨®æ”»æ“Šå¿…é ˆå…ˆç ´å£žç‰¹å®šç²æŽˆæ¬Šçš„程åºæ‰èƒ½åŸ·è¡Œï¼Œå› æ¤é€™å€‹å•é¡Œçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚ +MediaTek 視訊驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚ç”±æ–¼é€™ç¨®æ”»æ“Šå¿…é ˆå…ˆç ´è§£å…·æœ‰ç‰¹å®šæ¬Šé™çš„程åºæ‰èƒ½åŸ·è¡Œï¼Œå› æ¤é€™å€‹å•é¡Œçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚ </p> <table> <colgroup><col width="19%" /> @@ -1001,11 +1008,12 @@ MediaTek 視訊驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„æ‡‰ç” <td>2016 å¹´ 7 月 7 æ—¥</td> </tr> </tbody></table> -<p>* 這個å•é¡Œçš„修補程å¼ä¸¦æœªå…¬é–‹æ供，而是直接整åˆåœ¨æœ€æ–°çš„ Nexus è£ç½®å°ˆç”¨é©…動程å¼çš„安è£æª”ä¸ã€‚您å¯ä»¥å‰å¾€ <a href="https://developers.google.com/android/nexus/drivers">Google Developers 網站</a>下載這些驅動程å¼ã€‚ +<p> +* 這個å•é¡Œçš„修補程å¼ä¸¦æœªé–‹æ”¾çµ¦ä¸€èˆ¬ä½¿ç”¨è€…下載，相關的更新已直接整åˆåœ¨æœ€æ–°çš„ Nexus è£ç½®å°ˆç”¨é©…動程å¼çš„安è£æª”ä¸ã€‚您å¯ä»¥å‰å¾€ <a href="https://developers.google.com/android/nexus/drivers">Google Developers 網站</a>下載這些驅動程å¼ã€‚ </p> <h3 id="eopv-in-qualcomm-video-driver">Qualcomm 視訊驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> <p> -Qualcomm 視訊驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚ç”±æ–¼é€™ç¨®æ”»æ“Šå¿…é ˆå…ˆç ´å£žç‰¹å®šç²æŽˆæ¬Šçš„程åºæ‰èƒ½åŸ·è¡Œï¼Œå› æ¤é€™å€‹å•é¡Œçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚ +Qualcomm 視訊驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚ç”±æ–¼é€™ç¨®æ”»æ“Šå¿…é ˆå…ˆç ´è§£å…·æœ‰ç‰¹å®šæ¬Šé™çš„程åºæ‰èƒ½åŸ·è¡Œï¼Œå› æ¤é€™å€‹å•é¡Œçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚ </p> <table> <colgroup><col width="19%" /> @@ -1038,7 +1046,7 @@ Qualcomm 視訊驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„æ‡‰ç” </tr> </tbody></table> <h3 id="eopv-in-synaptics-touchscreen-driver">Synaptics 觸控螢幕驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> -<p>Synaptics 觸控螢幕驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚ç”±æ–¼é€™ç¨®æ”»æ“Šå¿…é ˆå…ˆç ´å£žç‰¹å®šç²æŽˆæ¬Šçš„程åºæ‰èƒ½åŸ·è¡Œï¼Œå› æ¤é€™å€‹å•é¡Œçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚ +<p>Synaptics 觸控螢幕驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚ç”±æ–¼é€™ç¨®æ”»æ“Šå¿…é ˆå…ˆç ´è§£å…·æœ‰ç‰¹å®šæ¬Šé™çš„程åºæ‰èƒ½åŸ·è¡Œï¼Œå› æ¤é€™å€‹å•é¡Œçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚ </p> <table> <colgroup><col width="19%" /> @@ -1058,7 +1066,7 @@ Qualcomm 視訊驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„æ‡‰ç” <td>A-30141991*</td> <td>高</td> <td>Nexus 6Pã€Android One</td> - <td>2016 å¹´ 7 月 16 æ—¥</td> + <td>2016 å¹´ 7 月 12 æ—¥</td> </tr> <tr> <td>CVE-2016-6672</td> @@ -1068,11 +1076,12 @@ Qualcomm 視訊驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„æ‡‰ç” <td>2016 å¹´ 7 月 31 æ—¥</td> </tr> </tbody></table> -<p>* 這個å•é¡Œçš„修補程å¼ä¸¦æœªå…¬é–‹æ供，而是直接整åˆåœ¨æœ€æ–°çš„ Nexus è£ç½®å°ˆç”¨é©…動程å¼çš„安è£æª”ä¸ã€‚您å¯ä»¥å‰å¾€ <a href="https://developers.google.com/android/nexus/drivers">Google Developers 網站</a>下載這些驅動程å¼ã€‚ +<p> +* 這個å•é¡Œçš„修補程å¼ä¸¦æœªé–‹æ”¾çµ¦ä¸€èˆ¬ä½¿ç”¨è€…下載，相關的更新已直接整åˆåœ¨æœ€æ–°çš„ Nexus è£ç½®å°ˆç”¨é©…動程å¼çš„安è£æª”ä¸ã€‚您å¯ä»¥å‰å¾€ <a href="https://developers.google.com/android/nexus/drivers">Google Developers 網站</a>下載這些驅動程å¼ã€‚ </p> <h3 id="eopv-in-nvidia-camera-driver">NVIDIA 相機驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> <p> -NVIDIA 相機驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚ç”±æ–¼é€™ç¨®æ”»æ“Šå¿…é ˆå…ˆç ´å£žç‰¹å®šç²æŽˆæ¬Šçš„程åºæ‰èƒ½åŸ·è¡Œï¼Œå› æ¤é€™å€‹å•é¡Œçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚ +NVIDIA 相機驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚ç”±æ–¼é€™ç¨®æ”»æ“Šå¿…é ˆå…ˆç ´è§£å…·æœ‰ç‰¹å®šæ¬Šé™çš„程åºæ‰èƒ½åŸ·è¡Œï¼Œå› æ¤é€™å€‹å•é¡Œçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚ </p> <table> <colgroup><col width="19%" /> @@ -1096,10 +1105,11 @@ NVIDIA 相機驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用ç <td>2016 å¹´ 7 月 17 æ—¥</td> </tr> </tbody></table> -<p>* 這個å•é¡Œçš„修補程å¼ä¸¦æœªå…¬é–‹æ供，而是直接整åˆåœ¨æœ€æ–°çš„ Nexus è£ç½®å°ˆç”¨é©…動程å¼çš„安è£æª”ä¸ã€‚您å¯ä»¥å‰å¾€ <a href="https://developers.google.com/android/nexus/drivers">Google Developers 網站</a>下載這些驅動程å¼ã€‚ +<p> +* 這個å•é¡Œçš„修補程å¼ä¸¦æœªé–‹æ”¾çµ¦ä¸€èˆ¬ä½¿ç”¨è€…下載，相關的更新已直接整åˆåœ¨æœ€æ–°çš„ Nexus è£ç½®å°ˆç”¨é©…動程å¼çš„安è£æª”ä¸ã€‚您å¯ä»¥å‰å¾€ <a href="https://developers.google.com/android/nexus/drivers">Google Developers 網站</a>下載這些驅動程å¼ã€‚ </p> <h3 id="eopv-in-system_server">System_server ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> -<p>System_server ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨ç²å¾—授權的程åºç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚由於這個å•é¡Œå¯ç”¨æ–¼å–å¾—æŸäº›é€²éšŽåŠŸèƒ½çš„本機å˜å–權，第三方應用程å¼é€šå¸¸ç„¡æ³•å˜å–é€™é¡žåŠŸèƒ½ï¼Œå› æ¤åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚ +<p>System_server ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨ç²å¾—授權的程åºç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚由於有心人士å¯åˆ©ç”¨é€™å€‹æ¼æ´žä¾†å–å¾—æŸäº›é€²éšŽåŠŸèƒ½çš„本機å˜å–權，第三方應用程å¼é€šå¸¸ç„¡æ³•å˜å–é€™é¡žåŠŸèƒ½ï¼Œå› æ¤åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚ </p> <table> <colgroup><col width="19%" /> @@ -1122,11 +1132,12 @@ NVIDIA 相機驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用ç <td>2016 å¹´ 7 月 26 æ—¥</td> </tr> </tbody></table> -<p>* 這個å•é¡Œçš„修補程å¼ä¸¦æœªå…¬é–‹æ供，而是直接整åˆåœ¨æœ€æ–°çš„ Nexus è£ç½®å°ˆç”¨é©…動程å¼çš„安è£æª”ä¸ã€‚您å¯ä»¥å‰å¾€ <a href="https://developers.google.com/android/nexus/drivers">Google Developers 網站</a>下載這些驅動程å¼ã€‚ +<p> +* 這個å•é¡Œçš„修補程å¼ä¸¦æœªé–‹æ”¾çµ¦ä¸€èˆ¬ä½¿ç”¨è€…下載，相關的更新已直接整åˆåœ¨æœ€æ–°çš„ Nexus è£ç½®å°ˆç”¨é©…動程å¼çš„安è£æª”ä¸ã€‚您å¯ä»¥å‰å¾€ <a href="https://developers.google.com/android/nexus/drivers">Google Developers 網站</a>下載這些驅動程å¼ã€‚ </p> <h3 id="eopv-in-qualcomm-wi-fi-driver">Qualcomm Wi-Fi 驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> <p> -Qualcomm Wi-Fi 驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚ç”±æ–¼é€™ç¨®æ”»æ“Šå¿…é ˆå…ˆç ´å£žç‰¹å®šç²æŽˆæ¬Šçš„程åºæ‰èƒ½åŸ·è¡Œï¼Œå› æ¤é€™å€‹å•é¡Œçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚ +Qualcomm Wi-Fi 驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚ç”±æ–¼é€™ç¨®æ”»æ“Šå¿…é ˆå…ˆç ´è§£å…·æœ‰ç‰¹å®šæ¬Šé™çš„程åºæ‰èƒ½åŸ·è¡Œï¼Œå› æ¤é€™å€‹å•é¡Œçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚ </p> <table> <colgroup><col width="19%" /> @@ -1176,7 +1187,7 @@ Qualcomm Wi-Fi 驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„æ‡‰ç” </tbody></table> <h3 id="eopv-in-kernel-performance-subsystem">æ ¸å¿ƒæ•ˆèƒ½å系統ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> <p> -æ ¸å¿ƒæ•ˆèƒ½å系統ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚ç”±æ–¼é€™ç¨®æ”»æ“Šå¿…é ˆå…ˆç ´å£žç‰¹å®šç²æŽˆæ¬Šçš„程åºæ‰èƒ½åŸ·è¡Œï¼Œå› æ¤é€™å€‹å•é¡Œçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚ +æ ¸å¿ƒæ•ˆèƒ½å系統ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚ç”±æ–¼é€™ç¨®æ”»æ“Šå¿…é ˆå…ˆç ´è§£å…·æœ‰ç‰¹å®šæ¬Šé™çš„程åºæ‰èƒ½åŸ·è¡Œï¼Œå› æ¤é€™å€‹å•é¡Œçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚ </p> <table> <colgroup><col width="19%" /> @@ -1202,7 +1213,7 @@ Qualcomm Wi-Fi 驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„æ‡‰ç” </tbody></table> <h3 id="information-disclosure-vulnerability-in-kernel-ion-subsystem">æ ¸å¿ƒ ION å系統ä¸çš„資訊外洩æ¼æ´ž</h3> <p> -æ ¸å¿ƒ ION å系統ä¸çš„資訊外洩æ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼å˜å–其權é™ç‰ç´šä»¥å¤–的資料。由於這個å•é¡Œå¯ç”¨æ–¼åœ¨æœªç²ä½¿ç”¨è€…明確授權的情æ³ä¸‹å˜å–æ©Ÿå¯†è³‡æ–™ï¼Œå› æ¤åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚ +æ ¸å¿ƒ ION å系統ä¸çš„資訊外洩æ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼å˜å–其權é™ç¯„åœä»¥å¤–的資料。由於這個å•é¡Œå¯èƒ½è®“有心人士在未ç²ä½¿ç”¨è€…明確授權的情æ³ä¸‹å˜å–æ©Ÿå¯†è³‡æ–™ï¼Œå› æ¤åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚ </p> <table> <colgroup><col width="19%" /> @@ -1227,7 +1238,7 @@ Qualcomm Wi-Fi 驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„æ‡‰ç” </tr> </tbody></table> <h3 id="information-disclosure-vulnerability-in-nvidia-gpu-driver">NVIDIA GPU 驅動程å¼ä¸çš„資訊外洩æ¼æ´ž</h3> -<p>NVIDIA GPU 驅動程å¼ä¸çš„資訊外洩æ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼å˜å–其權é™ç‰ç´šä»¥å¤–çš„è³‡æ–™ã€‚ç”±æ–¼é€™ç¨®æ”»æ“Šå¿…é ˆå…ˆç ´å£žç‰¹å®šç²æŽˆæ¬Šçš„程åºæ‰èƒ½åŸ·è¡Œï¼Œå› æ¤é€™å€‹å•é¡Œçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚ +<p>NVIDIA GPU 驅動程å¼ä¸çš„資訊外洩æ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼å˜å–其權é™ç¯„åœä»¥å¤–çš„è³‡æ–™ã€‚ç”±æ–¼é€™ç¨®æ”»æ“Šå¿…é ˆå…ˆç ´è§£å…·æœ‰ç‰¹å®šæ¬Šé™çš„程åºæ‰èƒ½åŸ·è¡Œï¼Œå› æ¤é€™å€‹å•é¡Œçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚ </p> <table> <colgroup><col width="19%" /> @@ -1251,11 +1262,12 @@ Qualcomm Wi-Fi 驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„æ‡‰ç” <td>2016 å¹´ 7 月 19 æ—¥</td> </tr> </tbody></table> -<p>* 這個å•é¡Œçš„修補程å¼ä¸¦æœªå…¬é–‹æ供，而是直接整åˆåœ¨æœ€æ–°çš„ Nexus è£ç½®å°ˆç”¨é©…動程å¼çš„安è£æª”ä¸ã€‚您å¯ä»¥å‰å¾€ <a href="https://developers.google.com/android/nexus/drivers">Google Developers 網站</a>下載這些驅動程å¼ã€‚ +<p> +* 這個å•é¡Œçš„修補程å¼ä¸¦æœªé–‹æ”¾çµ¦ä¸€èˆ¬ä½¿ç”¨è€…下載，相關的更新已直接整åˆåœ¨æœ€æ–°çš„ Nexus è£ç½®å°ˆç”¨é©…動程å¼çš„安è£æª”ä¸ã€‚您å¯ä»¥å‰å¾€ <a href="https://developers.google.com/android/nexus/drivers">Google Developers 網站</a>下載這些驅動程å¼ã€‚ </p> <h3 id="eopv-in-qualcomm-character-driver">Qualcomm å—元驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> <p> -Qualcomm å—元驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚ç”±æ–¼é€™ç¨®æ”»æ“Šå¿…é ˆå…ˆç ´å£žç‰¹å®šç²æŽˆæ¬Šçš„程åºæ‰èƒ½åŸ·è¡Œï¼Œè€Œä¸”ç›®å‰ä¹Ÿç„¡æ³•å˜å–å—到影響的程å¼ç¢¼ï¼Œå› æ¤é€™å€‹å•é¡Œçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œä¸ã€ã€‚ +Qualcomm å—元驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚ç”±æ–¼é€™ç¨®æ”»æ“Šå¿…é ˆå…ˆç ´è§£å…·æœ‰ç‰¹å®šæ¬Šé™çš„程åºæ‰èƒ½åŸ·è¡Œï¼Œè€Œä¸”ç›®å‰ä¹Ÿç„¡æ³•å˜å–å—到影響的程å¼ç¢¼ï¼Œå› æ¤é€™å€‹å•é¡Œçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œä¸ã€ã€‚ </p> <table> <colgroup><col width="19%" /> @@ -1281,7 +1293,7 @@ Qualcomm å—元驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„æ‡‰ç” </tbody></table> <h3 id="information-disclosure-vulnerability-in-qualcomm-sound-driver">Qualcomm 音效驅動程å¼ä¸çš„資訊外洩æ¼æ´ž</h3> <p> -Qualcomm 音效驅動程å¼ä¸çš„資訊外洩æ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼å˜å–其權é™ç‰ç´šä»¥å¤–çš„è³‡æ–™ã€‚ç”±æ–¼é€™ç¨®æ”»æ“Šå¿…é ˆå…ˆç ´å£žç‰¹å®šç²æŽˆæ¬Šçš„程åºæ‰èƒ½åŸ·è¡Œï¼Œå› æ¤é€™å€‹å•é¡Œçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œä¸ã€ã€‚ +Qualcomm 音效驅動程å¼ä¸çš„資訊外洩æ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼å˜å–其權é™ç¯„åœä»¥å¤–çš„è³‡æ–™ã€‚ç”±æ–¼é€™ç¨®æ”»æ“Šå¿…é ˆå…ˆç ´è§£å…·æœ‰ç‰¹å®šæ¬Šé™çš„程åºæ‰èƒ½åŸ·è¡Œï¼Œå› æ¤é€™å€‹å•é¡Œçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œä¸ã€ã€‚ </p> <table> <colgroup><col width="19%" /> @@ -1302,12 +1314,12 @@ Qualcomm 音效驅動程å¼ä¸çš„資訊外洩æ¼æ´žå¯èƒ½æœƒè®“本機惡æ„æ‡‰ç” <a href="https://source.codeaurora.org/quic/la/kernel/msm-3.18/diff/sound/soc/msm/qdsp6v2/audio_calibration.c?id=528976f54be246ec93a71ac53aa4faf3e3791c48">QC-CR#1038127</a></td> <td>ä¸</td> <td>Nexus 5Xã€Nexus 6Pã€Android One</td> - <td>20164 å¹´ 6 月 13 æ—¥</td> + <td>2016 å¹´ 6 月 13 æ—¥</td> </tr> </tbody></table> <h3 id="information-disclosure-vulnerability-in-motorola-usbnet-driver">Motorola USBNet 驅動程å¼ä¸çš„資訊外洩æ¼æ´ž</h3> <p> -Motorola USBNet 驅動程å¼ä¸çš„資訊外洩æ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼å˜å–其權é™ç‰ç´šä»¥å¤–çš„è³‡æ–™ã€‚ç”±æ–¼é€™ç¨®æ”»æ“Šå¿…é ˆå…ˆç ´å£žç‰¹å®šç²æŽˆæ¬Šçš„程åºæ‰èƒ½åŸ·è¡Œï¼Œå› æ¤é€™å€‹å•é¡Œçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œä¸ã€ã€‚ +Motorola USBNet 驅動程å¼ä¸çš„資訊外洩æ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼å˜å–其權é™ç¯„åœä»¥å¤–çš„è³‡æ–™ã€‚ç”±æ–¼é€™ç¨®æ”»æ“Šå¿…é ˆå…ˆç ´è§£å…·æœ‰ç‰¹å®šæ¬Šé™çš„程åºæ‰èƒ½åŸ·è¡Œï¼Œå› æ¤é€™å€‹å•é¡Œçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œä¸ã€ã€‚ </p> <table> <colgroup><col width="19%" /> @@ -1330,11 +1342,12 @@ Motorola USBNet 驅動程å¼ä¸çš„資訊外洩æ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應ç <td>2016 å¹´ 6 月 30 æ—¥</td> </tr> </tbody></table> -<p>* 這個å•é¡Œçš„修補程å¼ä¸¦æœªå…¬é–‹æ供，而是直接整åˆåœ¨æœ€æ–°çš„ Nexus è£ç½®å°ˆç”¨é©…動程å¼çš„安è£æª”ä¸ã€‚您å¯ä»¥å‰å¾€ <a href="https://developers.google.com/android/nexus/drivers">Google Developers 網站</a>下載這些驅動程å¼ã€‚ +<p> +* 這個å•é¡Œçš„修補程å¼ä¸¦æœªé–‹æ”¾çµ¦ä¸€èˆ¬ä½¿ç”¨è€…下載，相關的更新已直接整åˆåœ¨æœ€æ–°çš„ Nexus è£ç½®å°ˆç”¨é©…動程å¼çš„安è£æª”ä¸ã€‚您å¯ä»¥å‰å¾€ <a href="https://developers.google.com/android/nexus/drivers">Google Developers 網站</a>下載這些驅動程å¼ã€‚ </p> <h3 id="information-disclosure-vulnerability-in-qualcomm-components">Qualcomm 元件ä¸çš„資訊外洩æ¼æ´ž</h3> <p> -Qualcomm 元件 (包括音效驅動程å¼ã€IPA 驅動程å¼å’Œ Wi-Fi 驅動程å¼) ä¸çš„資訊外洩æ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼å˜å–其權é™ç‰ç´šä»¥å¤–çš„è³‡æ–™ã€‚ç”±æ–¼é€™ç¨®æ”»æ“Šå¿…é ˆå…ˆç ´å£žç‰¹å®šç²æŽˆæ¬Šçš„程åºæ‰èƒ½åŸ·è¡Œï¼Œå› æ¤é€™å€‹å•é¡Œçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œä¸ã€ã€‚ +Qualcomm 元件 (包括音效驅動程å¼ã€IPA 驅動程å¼å’Œ Wi-Fi 驅動程å¼) ä¸çš„資訊外洩æ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼å˜å–其權é™ç¯„åœä»¥å¤–çš„è³‡æ–™ã€‚ç”±æ–¼é€™ç¨®æ”»æ“Šå¿…é ˆå…ˆç ´è§£å…·æœ‰ç‰¹å®šæ¬Šé™çš„程åºæ‰èƒ½åŸ·è¡Œï¼Œå› æ¤é€™å€‹å•é¡Œçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œä¸ã€ã€‚ </p> <table> <colgroup><col width="19%" /> @@ -1563,7 +1576,8 @@ NVIDIA 分æžå™¨ä¸çš„資訊外洩æ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼å˜å <td>2016 å¹´ 5 月 18 æ—¥</td> </tr> </tbody></table> -<p>* 這個å•é¡Œçš„修補程å¼ä¸¦æœªå…¬é–‹æ供，而是直接整åˆåœ¨æœ€æ–°çš„ Nexus è£ç½®å°ˆç”¨é©…動程å¼çš„安è£æª”ä¸ã€‚您å¯ä»¥å‰å¾€ <a href="https://developers.google.com/android/nexus/drivers">Google Developers 網站</a>下載這些驅動程å¼ã€‚ +<p> +* 這個å•é¡Œçš„修補程å¼ä¸¦æœªé–‹æ”¾çµ¦ä¸€èˆ¬ä½¿ç”¨è€…下載，而是直接整åˆåœ¨æœ€æ–°çš„ Nexus è£ç½®å°ˆç”¨é©…動程å¼çš„安è£æª”ä¸ã€‚您å¯ä»¥å‰å¾€ <a href="https://developers.google.com/android/nexus/drivers">Google Developers 網站</a>下載這些驅動程å¼ã€‚ </p> <h3 id="vulnerabilities-in-qualcomm-components">Qualcomm 元件ä¸çš„æ¼æ´ž</h3> <p> @@ -1668,7 +1682,7 @@ NVIDIA 分æžå™¨ä¸çš„資訊外洩æ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼å˜å <ul> <li><strong>所有 Nexus è£ç½®</strong>：如果å•é¡Œæœƒå½±éŸ¿åˆ°æ‰€æœ‰ Nexus è£ç½®ï¼Œè¡¨æ ¼å…§ã€Œæ›´æ–°çš„ Nexus è£ç½®ã€<em></em>欄ä¸å°±æœƒé¡¯ç¤ºã€Œæ‰€æœ‰ Nexus è£ç½®ã€å—樣。「所有 Nexus è£ç½®ã€åŒ…å«ä¸‹åˆ—<a href="https://support.google.com/nexus/answer/4457705#nexus_devices">支æ´çš„è£ç½®</a>：Nexus 5ã€Nexus 5Xã€Nexus 6ã€Nexus 6Pã€Nexus 9ã€Android Oneã€Nexus Player å’Œ Pixel C。</li> <li><strong>部分 Nexus è£ç½®</strong>：如果å•é¡Œä¸¦æœªå½±éŸ¿æ‰€æœ‰ Nexus è£ç½®ï¼Œã€Œæ›´æ–°çš„ Nexus è£ç½®ã€<em></em>欄ä¸å°±æœƒåˆ—出å—到影響的 Nexus è£ç½®ã€‚</li> - <li><strong>ä¸å½±éŸ¿ä»»ä½• Nexus è£ç½®</strong>：如果å•é¡Œä¸æœƒå½±éŸ¿åˆ°ä»»ä½•æ載 Android 7.0 çš„ Nexus è£ç½®ï¼Œè¡¨å€‹å…§ã€Œæ›´æ–°çš„ Nexus è£ç½®ã€<em></em>欄ä¸å°±æœƒæ¨™ç¤ºã€Œç„¡ã€å—樣。</li> + <li><strong>ä¸å½±éŸ¿ä»»ä½• Nexus è£ç½®</strong>：如果å•é¡Œä¸æœƒå½±éŸ¿åˆ°ä»»ä½•æ載 Android 7.0 çš„ Nexus è£ç½®ï¼Œè¡¨æ ¼å…§ã€Œæ›´æ–°çš„ Nexus è£ç½®ã€<em></em>欄ä¸å°±æœƒé¡¯ç¤ºã€Œç„¡ã€å—樣。</li> </ul> <p> <strong>4. åƒè€ƒè³‡æ–™æ¬„底下列出的è˜åˆ¥ç¢¼ä»£è¡¨ä»€éº¼æ„義？</strong> @@ -1677,7 +1691,7 @@ NVIDIA 分æžå™¨ä¸çš„資訊外洩æ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼å˜å </p> <table> <tbody><tr> - <th>å‰ç½®å—å…ƒ</th> + <th>å‰ç½®å—串</th> <th>åƒè€ƒè³‡æ–™</th> </tr> <tr> diff --git a/zh-tw/security/bulletin/2017-01-01.html b/zh-tw/security/bulletin/2017-01-01.html index 8d1093f4..18e95d91 100644 --- a/zh-tw/security/bulletin/2017-01-01.html +++ b/zh-tw/security/bulletin/2017-01-01.html @@ -97,7 +97,7 @@ </ul> <h2 id="2017-01-01-details">2017-01-01 安全性修補程å¼ç‰ç´š — 資安æ¼æ´žè©³æƒ…</h2> -<p>下列å„節é‡å° 2017-01-01 安全性修補程å¼ç‰ç´šé©ç”¨çš„å„é …å®‰å…¨æ€§æ¼æ´žæ供了詳細資訊，包括å•é¡Œèªªæ˜Žã€åš´é‡ç¨‹åº¦è©•å®šåŽŸå› ，以åŠä¸€ä»½æ¼æ´žè³‡è¨Šè¡¨ï¼Œé¡¯ç¤ºæ¼æ´žçš„ CVEã€ç›¸é—œåƒè€ƒè³‡æ–™ã€åš´é‡ç¨‹åº¦ã€æ›´æ–°çš„ Google è£ç½®ã€æ›´æ–°çš„ AOSP 版本 (在é©ç”¨æƒ…æ³ä¸‹) å’Œå›žå ±æ—¥æœŸã€‚å‡å¦‚相關錯誤有公開變更，該錯誤 ID 會連çµåˆ°ç›¸å°æ‡‰çš„變更 (例如 AOSP 變更清單)ã€‚å¦‚æžœå–®ä¸€éŒ¯èª¤æœ‰å¤šé …ç›¸é—œè®Šæ›´ï¼Œå…¶ä»–åƒè€ƒè³‡æ–™å¯é€éŽè©²éŒ¯èª¤ ID 後é¢çš„編號連çµé–‹å•Ÿã€‚</p> +<p>下列å„節é‡å° 2017-01-01 安全性修補程å¼ç‰ç´šé©ç”¨çš„å„é …å®‰å…¨æ€§æ¼æ´žæ供了詳細資訊，包括å•é¡Œèªªæ˜Žã€åš´é‡ç¨‹åº¦è©•å®šåŽŸå› ，以åŠä¸€ä»½æ¼æ´žè³‡è¨Šè¡¨ï¼Œé¡¯ç¤ºæ¼æ´žçš„ CVEã€ç›¸é—œåƒè€ƒè³‡æ–™ã€åš´é‡ç¨‹åº¦ã€æ›´æ–°çš„ Google è£ç½®ã€æ›´æ–°çš„ AOSP 版本 (在é©ç”¨æƒ…æ³ä¸‹) å’Œå›žå ±æ—¥æœŸã€‚å‡å¦‚相關錯誤有公開變更，該錯誤 ID 會連çµåˆ°ç›¸å°æ‡‰çš„變更 (例如 Android 開放原始碼計劃變更清單)ã€‚å¦‚æžœå–®ä¸€éŒ¯èª¤æœ‰å¤šé …ç›¸é—œè®Šæ›´ï¼Œå…¶ä»–åƒè€ƒè³‡æ–™å¯é€éŽè©²éŒ¯èª¤ ID 後é¢çš„編號連çµé–‹å•Ÿã€‚</p> <h3 id="rce-in-c-ares">c-ares ä¸çš„é 端程å¼ç¢¼åŸ·è¡Œæ¼æ´ž</h3> <p> @@ -116,7 +116,7 @@ c-ares ä¸çš„é 端程å¼ç¢¼åŸ·è¡Œæ¼æ´žå¯èƒ½æœƒè®“攻擊者能利用特製è¦æ <th>åƒè€ƒè³‡æ–™</th> <th>åš´é‡ç¨‹åº¦</th> <th>æ›´æ–°çš„ Google è£ç½®</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -146,7 +146,7 @@ Framesequence 程å¼åº«ä¸çš„é 端程å¼ç¢¼åŸ·è¡Œæ¼æ´žå¯èƒ½æœƒè®“攻擊者能 <th>åƒè€ƒè³‡æ–™</th> <th>åš´é‡ç¨‹åº¦</th> <th>æ›´æ–°çš„ Google è£ç½®</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -175,7 +175,7 @@ Framework API ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨ç² <th>åƒè€ƒè³‡æ–™</th> <th>åš´é‡ç¨‹åº¦</th> <th>æ›´æ–°çš„ Google è£ç½®</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -203,7 +203,7 @@ Framework API ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨ç² <th>åƒè€ƒè³‡æ–™</th> <th>åš´é‡ç¨‹åº¦</th> <th>æ›´æ–°çš„ Google è£ç½®</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -241,7 +241,7 @@ libnl 程å¼åº«ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨ç <th>åƒè€ƒè³‡æ–™</th> <th>åš´é‡ç¨‹åº¦</th> <th>æ›´æ–°çš„ Google è£ç½®</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -270,7 +270,7 @@ libnl 程å¼åº«ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨ç <th>åƒè€ƒè³‡æ–™</th> <th>åš´é‡ç¨‹åº¦</th> <th>æ›´æ–°çš„ Google è£ç½®</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -299,7 +299,7 @@ libnl 程å¼åº«ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨ç <th>åƒè€ƒè³‡æ–™</th> <th>åš´é‡ç¨‹åº¦</th> <th>æ›´æ–°çš„ Google è£ç½®</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -328,7 +328,7 @@ libnl 程å¼åº«ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨ç <th>åƒè€ƒè³‡æ–™</th> <th>åš´é‡ç¨‹åº¦</th> <th>æ›´æ–°çš„ Google è£ç½®</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -359,7 +359,7 @@ libnl 程å¼åº«ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨ç <th>åƒè€ƒè³‡æ–™</th> <th>åš´é‡ç¨‹åº¦</th> <th>æ›´æ–°çš„ Google è£ç½®</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -415,7 +415,7 @@ libnl 程å¼åº«ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨ç <th>åƒè€ƒè³‡æ–™</th> <th>åš´é‡ç¨‹åº¦</th> <th>æ›´æ–°çš„ Google è£ç½®</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -444,7 +444,7 @@ libnl 程å¼åº«ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨ç <th>åƒè€ƒè³‡æ–™</th> <th>åš´é‡ç¨‹åº¦</th> <th>æ›´æ–°çš„ Google è£ç½®</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -473,7 +473,7 @@ libnl 程å¼åº«ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨ç <th>åƒè€ƒè³‡æ–™</th> <th>åš´é‡ç¨‹åº¦</th> <th>æ›´æ–°çš„ Google è£ç½®</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -520,7 +520,7 @@ libnl 程å¼åº«ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨ç <th>åƒè€ƒè³‡æ–™</th> <th>åš´é‡ç¨‹åº¦</th> <th>æ›´æ–°çš„ Google è£ç½®</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -592,11 +592,11 @@ libnl 程å¼åº«ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨ç </tbody></table> <h2 id="2017-01-05-details">2017-01-05 安全性修補程å¼ç‰ç´š — 資安æ¼æ´žè©³æƒ…</h2> -<p>下列å„節é‡å° 2017-01-05 安全性修補程å¼ç‰ç´šé©ç”¨çš„å„é …å®‰å…¨æ€§æ¼æ´žæ供了詳細資訊，包括å•é¡Œèªªæ˜Žã€åš´é‡ç¨‹åº¦è©•å®šåŽŸå› ，以åŠä¸€ä»½æ¼æ´žè³‡è¨Šè¡¨ï¼Œé¡¯ç¤ºæ¼æ´žçš„ CVEã€ç›¸é—œåƒè€ƒè³‡æ–™ã€åš´é‡ç¨‹åº¦ã€æ›´æ–°çš„ Google è£ç½®ã€æ›´æ–°çš„ AOSP 版本 (在é©ç”¨æƒ…æ³ä¸‹) å’Œå›žå ±æ—¥æœŸã€‚å‡å¦‚相關錯誤有公開變更，該錯誤 ID 會連çµåˆ°ç›¸å°æ‡‰çš„變更 (例如 AOSP 變更清單)ã€‚å¦‚æžœå–®ä¸€éŒ¯èª¤æœ‰å¤šé …ç›¸é—œè®Šæ›´ï¼Œå…¶ä»–åƒè€ƒè³‡æ–™å¯é€éŽè©²éŒ¯èª¤ ID 後é¢çš„編號連çµé–‹å•Ÿã€‚</p> +<p>下列å„節é‡å° 2017-01-05 安全性修補程å¼ç‰ç´šé©ç”¨çš„å„é …å®‰å…¨æ€§æ¼æ´žæ供了詳細資訊，包括å•é¡Œèªªæ˜Žã€åš´é‡ç¨‹åº¦è©•å®šåŽŸå› ，以åŠä¸€ä»½æ¼æ´žè³‡è¨Šè¡¨ï¼Œé¡¯ç¤ºæ¼æ´žçš„ CVEã€ç›¸é—œåƒè€ƒè³‡æ–™ã€åš´é‡ç¨‹åº¦ã€æ›´æ–°çš„ Google è£ç½®ã€æ›´æ–°çš„ AOSP 版本 (在é©ç”¨æƒ…æ³ä¸‹) å’Œå›žå ±æ—¥æœŸã€‚å‡å¦‚相關錯誤有公開變更，該錯誤 ID 會連çµåˆ°ç›¸å°æ‡‰çš„變更 (例如 AOSP 變更清單)ã€‚å¦‚æžœå–®ä¸€éŒ¯èª¤æœ‰å¤šé …ç›¸é—œè®Šæ›´ï¼Œæ‚¨å¯ä»¥é€éŽè©²éŒ¯èª¤ ID 後é¢çš„編號連çµé–‹å•Ÿé¡å¤–çš„åƒè€ƒè³‡æ–™ã€‚</p> <h3 id="eop-in-kernel-memory-subsystem">æ ¸å¿ƒè¨˜æ†¶é«”å系統ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> <p> -æ ¸å¿ƒè¨˜æ†¶é«”å系統ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•æŒ‡ä»¤ã€‚由於這個å•é¡Œå¯èƒ½å°Žè‡´æœ¬æ©Ÿè£ç½®çš„å®‰å…¨æ€§å¾¹åº•è¢«ç ´å£žï¼Œé€ æˆä½¿ç”¨è€…å¿…é ˆä»¥é‚„åŽŸ (Re-flash) 作æ¥ç³»çµ±çš„æ–¹å¼æ‰èƒ½ä¿®å¾©è£ç½®ï¼Œå› æ¤åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œæœ€é«˜ã€ã€‚ +æ ¸å¿ƒè¨˜æ†¶é«”å系統ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚由於這個å•é¡Œå¯èƒ½å°Žè‡´æœ¬æ©Ÿè£ç½®çš„å®‰å…¨æ€§å¾¹åº•è¢«ç ´å£žï¼Œé€ æˆä½¿ç”¨è€…å¿…é ˆä»¥é‚„åŽŸ (Reflash) 作æ¥ç³»çµ±çš„æ–¹å¼æ‰èƒ½ä¿®å¾©è£ç½®ï¼Œå› æ¤åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œæœ€é«˜ã€ã€‚ </p> <table> @@ -828,7 +828,7 @@ MediaTek 驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„æ‡‰ç”¨ç¨‹å¼ </p> <h3 id="eop-in-qualcomm-gpu-driver">Qualcomm GPU 驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> -<p>Qualcomm GPU 驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•æŒ‡ä»¤ã€‚由於這個å•é¡Œå¯èƒ½å°Žè‡´æœ¬æ©Ÿè£ç½®çš„å®‰å…¨æ€§å¾¹åº•è¢«ç ´å£žï¼Œé€ æˆä½¿ç”¨è€…å¿…é ˆä»¥é‚„åŽŸ (Re-flash) 作æ¥ç³»çµ±çš„æ–¹å¼æ‰èƒ½ä¿®å¾©è£ç½®ï¼Œå› æ¤åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œæœ€é«˜ã€ã€‚ +<p>Qualcomm GPU 驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•æŒ‡ä»¤ã€‚由於這個å•é¡Œå¯èƒ½å°Žè‡´æœ¬æ©Ÿè£ç½®çš„å®‰å…¨æ€§å¾¹åº•è¢«ç ´å£žï¼Œé€ æˆä½¿ç”¨è€…å¿…é ˆä»¥é‚„åŽŸ (Reflash) 作æ¥ç³»çµ±çš„æ–¹å¼æ‰èƒ½ä¿®å¾©è£ç½®ï¼Œå› æ¤åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œæœ€é«˜ã€ã€‚ </p> <table> @@ -1172,7 +1172,7 @@ NVIDIA GPU 驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程 <h3 id="eop-in-qualcomm-sound-driver">Qualcomm 音效驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> <p> -Qualcomm 音效驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•æŒ‡ä»¤ã€‚ç”±æ–¼é€™ç¨®æ”»æ“Šå¿…é ˆå…ˆç ´å£žç‰¹å®šç²æŽˆæ¬Šçš„程åºæ‰èƒ½åŸ·è¡Œï¼Œå› æ¤é€™å€‹å•é¡Œçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚ +Qualcomm 音效驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•æŒ‡ä»¤ã€‚ç”±æ–¼é€™ç¨®æ”»æ“Šå¿…é ˆå…ˆç ´è§£å…·æœ‰ç‰¹å®šæ¬Šé™çš„程åºæ‰èƒ½åŸ·è¡Œï¼Œå› æ¤é€™å€‹å•é¡Œçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚ </p> <table> @@ -1200,7 +1200,7 @@ QC-CR#880388</a></td> </tbody></table> <h3 id="eop-in-synaptics-touchscreen-driver">Synaptics 觸控螢幕驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> -<p>Synaptics 觸控螢幕驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•æŒ‡ä»¤ã€‚ç”±æ–¼é€™ç¨®æ”»æ“Šå¿…é ˆå…ˆç ´å£žç‰¹å®šç²æŽˆæ¬Šçš„程åºæ‰èƒ½åŸ·è¡Œï¼Œå› æ¤é€™å€‹å•é¡Œçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚ +<p>Synaptics 觸控螢幕驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚ç”±æ–¼é€™ç¨®æ”»æ“Šå¿…é ˆå…ˆç ´è§£å…·æœ‰ç‰¹å®šæ¬Šé™çš„程åºæ‰èƒ½åŸ·è¡Œï¼Œå› æ¤é€™å€‹å•é¡Œçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚ </p> <table> @@ -1290,7 +1290,7 @@ QC-CR#880388</a></td> <h3 id="eop-in-kernel-sound-subsystem">æ ¸å¿ƒéŸ³æ•ˆå系統ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> <p> -æ ¸å¿ƒéŸ³æ•ˆå系統ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•æŒ‡ä»¤ã€‚ç”±æ–¼é€™ç¨®æ”»æ“Šå¿…é ˆå…ˆç ´å£žç‰¹å®šç²æŽˆæ¬Šçš„程åºæ‰èƒ½åŸ·è¡Œï¼Œå› æ¤é€™å€‹å•é¡Œçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚ +æ ¸å¿ƒéŸ³æ•ˆå系統ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•æŒ‡ä»¤ã€‚ç”±æ–¼é€™ç¨®æ”»æ“Šå¿…é ˆå…ˆç ´è§£å…·æœ‰ç‰¹å®šæ¬Šé™çš„程åºæ‰èƒ½åŸ·è¡Œï¼Œå› æ¤é€™å€‹å•é¡Œçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚ </p> <table> @@ -1406,7 +1406,7 @@ QC-CR#1079713</a></td> <h3 id="eop-in-broadcom-wi-fi-driver">Broadcom Wi-Fi 驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> <p> -Broadcom Wi-Fi 驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•æŒ‡ä»¤ã€‚ç”±æ–¼é€™ç¨®æ”»æ“Šå¿…é ˆå…ˆç ´å£žç‰¹å®šç²æŽˆæ¬Šçš„程åºæ‰èƒ½åŸ·è¡Œï¼Œå› æ¤é€™å€‹å•é¡Œçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚ +Broadcom Wi-Fi 驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•æŒ‡ä»¤ã€‚ç”±æ–¼é€™ç¨®æ”»æ“Šå¿…é ˆå…ˆç ´è§£å…·æœ‰ç‰¹å®šæ¬Šé™çš„程åºæ‰èƒ½åŸ·è¡Œï¼Œå› æ¤é€™å€‹å•é¡Œçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚ </p> <table> @@ -1468,7 +1468,7 @@ Broadcom Wi-Fi 驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„æ‡‰ç” </p> <h3 id="eop-in-synaptics-touchscreen-driver-2">Synaptics 觸控螢幕驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> -<p>Synaptics 觸控螢幕驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•æŒ‡ä»¤ã€‚ç”±æ–¼é€™ç¨®æ”»æ“Šå¿…é ˆå…ˆç ´å£žç‰¹å®šç²æŽˆæ¬Šçš„程åºæ‰èƒ½åŸ·è¡Œï¼Œå› æ¤é€™å€‹å•é¡Œçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚ +<p>Synaptics 觸控螢幕驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚ç”±æ–¼é€™ç¨®æ”»æ“Šå¿…é ˆå…ˆç ´è§£å…·æœ‰ç‰¹å®šæ¬Šé™çš„程åºæ‰èƒ½åŸ·è¡Œï¼Œå› æ¤é€™å€‹å•é¡Œçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚ </p> <table> @@ -1827,7 +1827,7 @@ Qualcomm 音訊後置處ç†å™¨ä¸çš„資訊外洩æ¼æ´žå¯èƒ½æœƒè®“本機惡æ„æ‡ <th>åƒè€ƒè³‡æ–™</th> <th>åš´é‡ç¨‹åº¦</th> <th>æ›´æ–°çš„ Google è£ç½®</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -1963,16 +1963,16 @@ HTC 輸入驅動程å¼ä¸çš„資訊外洩æ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å <p>在 <a href="#2017-01-01-details">2017-01-01</a> å’Œ <a href="#2017-01-05-details">2017-01-05</a> 安全性æ¼æ´žè©³æƒ…çš„ç« ç¯€ä¸ï¼Œæ¯å€‹è¡¨æ ¼éƒ½åŒ…å«ã€Œæ›´æ–°çš„ Google è£ç½®ã€<em></em>欄，當ä¸åˆ—出已é‡å°å„個å•é¡Œé€²è¡Œæ›´æ–°çš„å—影響 Google è£ç½®ç¯„åœã€‚æ¤æ¬„ä¸çš„é¸é …包括：</p> <ul> <li><strong>所有 Google è£ç½®</strong>：如果å•é¡Œæœƒå½±éŸ¿åˆ° Pixel è£ç½®å’Œæ‰€æœ‰çš„ Google è£ç½®ï¼Œè¡¨æ ¼å…§ã€Œæ›´æ–°çš„ Google è£ç½®ã€<em></em>欄ä¸å°±æœƒæ¨™ç¤ºã€Œå…¨éƒ¨ã€å—樣。「全部ã€åŒ…å«ä¸‹åˆ—<a href="https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices">支æ´çš„è£ç½®</a>：Nexus 5Xã€Nexus 6ã€Nexus 6Pã€Nexus 9ã€Android Oneã€Nexus Playerã€Pixel Cã€Pixel å’Œ Pixel XL。</li> - <li><strong>部分 Google è£ç½®</strong>：如果å•é¡Œä¸¦æœªå½±éŸ¿åˆ°æ‰€æœ‰ Google è£ç½®ï¼Œå‰‡ã€Œæ›´æ–°çš„ Google è£ç½®ã€<em></em>欄ä¸æœƒåˆ—出å—影響的 Google è£ç½®ã€‚</li> + <li><strong>部分 Google è£ç½®</strong>：如果å•é¡Œä¸¦æœªå½±éŸ¿åˆ°æ‰€æœ‰ Google è£ç½®ï¼Œã€Œæ›´æ–°çš„ Google è£ç½®ã€<em></em>欄ä¸æœƒåˆ—出å—影響的 Google è£ç½®ã€‚</li> <li><strong>ä¸å½±éŸ¿ä»»ä½• Google è£ç½®</strong>：如果å•é¡Œä¸æœƒå½±éŸ¿åˆ°ä»»ä½•æ載目å‰æ供最新版 Android çš„ Google è£ç½®ï¼Œè¡¨æ ¼å…§ã€Œæ›´æ–°çš„ Google è£ç½®ã€<em></em>欄ä¸å°±æœƒæ¨™ç¤ºã€Œç„¡ã€å—樣。</li> </ul> <p><strong>4. åƒè€ƒè³‡æ–™æ¬„底下列出的è˜åˆ¥ç¢¼ä»£è¡¨ä»€éº¼æ„義？</strong></p> -<p>資安æ¼æ´žè©³æƒ…è¡¨æ ¼ä¸ã€Œåƒè€ƒè³‡æ–™ã€<em></em>æ¬„åº•ä¸‹çš„é …ç›®å¯èƒ½æœƒåŒ…å«ä¸€å€‹å‰ç½®å—串，用以表示該åƒè€ƒè³‡æ–™å€¼æ‰€å±¬çš„機構或公å¸ã€‚這些å‰ç½®å—元代表的æ„義如下：</p> +<p>資安æ¼æ´žè©³æƒ…è¡¨æ ¼ä¸ã€Œåƒè€ƒè³‡æ–™ã€<em></em>æ¬„åº•ä¸‹çš„é …ç›®å¯èƒ½æœƒåŒ…å«ä¸€å€‹å‰ç½®å—串，用以表示該åƒè€ƒè³‡æ–™å€¼æ‰€å±¬çš„機構或公å¸ã€‚這些å‰ç½®å—串代表的æ„義如下：</p> <table> <tbody><tr> - <th>å‰ç½®å—å…ƒ</th> + <th>å‰ç½®å—串</th> <th>åƒè€ƒè³‡æ–™</th> </tr> <tr> diff --git a/zh-tw/security/bulletin/2017-03-01.html b/zh-tw/security/bulletin/2017-03-01.html index 36644735..15ebedba 100644 --- a/zh-tw/security/bulletin/2017-03-01.html +++ b/zh-tw/security/bulletin/2017-03-01.html @@ -22,7 +22,7 @@ <p><em>發佈日期：2017 å¹´ 3 月 6 æ—¥ | 更新日期：2017 å¹´ 3 月 7 æ—¥</em></p> <p>Android å®‰å…¨æ€§å…¬å‘Šç¾…åˆ—äº†æœƒå° Android è£ç½®é€ æˆå½±éŸ¿çš„安全性æ¼æ´žï¼Œä¸¦èªªæ˜Žå„é …ç›¸é—œç´°ç¯€ã€‚åœ¨é€™ç¯‡å…¬å‘Šç™¼ä½ˆçš„åŒæ™‚，Google å·²é€éŽ OTA 更新機制發佈了 Google è£ç½®çš„安全性更新。æ¤å¤–，Google éŸŒé«”æ˜ åƒæª”也已經發佈到 <a href="https://developers.google.com/android/nexus/images">Google Developers 網站</a>上。2017 å¹´ 3 月 5 日之後的安全性修補程å¼ç‰ç´šå·²è§£æ±ºäº†é€™äº›å·²æåŠçš„所有å•é¡Œã€‚è«‹åƒé–± <a href="https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices">Pixel 與 Nexus 更新時間表</a>，çžè§£å¦‚何查看è£ç½®çš„安全性修補程å¼ç‰ç´šã€‚</p> -<p>我們的åˆä½œå¤¥ä¼´åœ¨ 2017 å¹´ 2 月 6 日當天或更早之å‰å·²æ”¶åˆ°å…¬å‘Šä¸æ‰€è¿°å•é¡Œçš„相關通知。這些å•é¡Œçš„原始碼修補程å¼å·²ç™¼ä½ˆåˆ° Android 開放原始碼計劃 (AOSP) å˜æ”¾å€ä¸ï¼Œä¸”公告ä¸äº¦æ供相關連çµã€‚æ¤å¤–，本公告也æä¾› AOSP 以外的修補程å¼é€£çµã€‚</p> +<p>我們的åˆä½œå¤¥ä¼´åœ¨ 2017 å¹´ 2 月 6 日當天或更早之å‰å·²æ”¶åˆ°å…¬å‘Šä¸æ‰€è¿°å•é¡Œçš„相關通知。這些å•é¡Œçš„原始碼修補程å¼å·²ç™¼ä½ˆåˆ° Android 開放原始碼計劃 (AOSP) å˜æ”¾å€ä¸ï¼Œä¸”公告ä¸äº¦æ供相關連çµã€‚æ¤å¤–，本公告也æä¾› Android 開放原始碼計劃以外的修補程å¼é€£çµã€‚</p> <p>在這些å•é¡Œä¸ï¼Œæœ€åš´é‡çš„就是「最高ã€ç‰ç´šçš„安全性æ¼æ´žã€‚當系統執行媒體檔案時，é 端程å¼ç¢¼å¯åˆ©ç”¨é€™é¡žæ¼æ´žï¼Œé€éŽé›»å郵件ã€ç¶²é ç€è¦½æ´»å‹•å’Œå¤šåª’體訊æ¯ç‰æ–¹æ³•ï¼Œè‡ªå‹•åœ¨å—影響的è£ç½®ä¸ŠåŸ·è¡Œã€‚<a href="/security/overview/updates-resources.html#severity">åš´é‡ç¨‹åº¦è©•å®šæ¨™æº–</a>是å‡è¨å¹³å°èˆ‡æœå‹™çš„å› æ‡‰é˜²è·æŽªæ–½åŸºæ–¼é–‹ç™¼ä½œæ¥çš„需求而被åœç”¨ï¼Œæˆ–是éåˆ°æœ‰å¿ƒäººå£«ç ´è§£ï¼Œç„¶å¾ŒæŽ¨ç®—ç•¶æœ‰äººæƒ¡æ„é‹ç”¨æ¼æ´žæ™‚，è£ç½®æœƒå—到多大的影響，據æ¤è©•å®šæ¼æ´žçš„åš´é‡ç¨‹åº¦ã€‚</p> <p>é‡å°é€™äº›æ–°ç™¼ç¾çš„æ¼æ´žï¼Œæˆ‘們目å‰å°šæœªæ”¶åˆ°ä»»ä½•å®¢æˆ¶å›žå ±ç›¸é—œçš„æ¼æ´žæ¿«ç”¨æ¡ˆä¾‹ã€‚如果您想進一æ¥çžè§£ <a href="#mitigations">Android 安全性平å°é˜²è·æŽªæ–½</a>å’Œæœå‹™é˜²è·æŽªæ–½ (例如 <a href="/security/enhancements/index.html">SafetyNet</a>) å¦‚ä½•åŠ å¼· Android å¹³å°çš„安全性，請åƒé–± <a href="https://developer.android.com/training/safetynet/index.html">Android å’Œ Google æœå‹™å•é¡Œå› 應措施</a>一節。</p> <p>我們建è°æ‰€æœ‰å®¢æˆ¶æŽ¥å—這些è£ç½®æ›´æ–°ã€‚</p> @@ -39,18 +39,18 @@ <p>本節概述 <a href="/security/enhancements/index.html">Android 安全性平å°</a>å’Œ SafetyNet ç‰æœå‹™é˜²è·æ–¹æ¡ˆé‡å°è³‡å®‰æ¼æ´žæ‰€æä¾›çš„å› æ‡‰æŽªæ–½ã€‚é€™äº›æŽªæ–½å¯æœ‰æ•ˆé˜²ç¯„有心人士在 Android 系統上惡æ„é‹ç”¨å®‰å…¨æ€§æ¼æ´žä¾†é”到特定目的。</p> <ul> <li>Android å¹³å°æŒçºŒæŽ¨å‡ºæ–°çš„ç‰ˆæœ¬ä¾†å¼·åŒ–å®‰å…¨æ€§ï¼Œå› æ¤æœ‰å¿ƒäººå£«è¶Šä¾†è¶Šé›£åœ¨ Android 系統上找出æ¼æ´žåŠ 以利用。我們建è°æ‰€æœ‰ä½¿ç”¨è€…盡å¯èƒ½æ›´æ–°è‡³æœ€æ–°ç‰ˆçš„ Android。</li> -<li>Android 安全性å°çµ„採用<a href="http://static.googleusercontent.com/media/source.android.com/en//security/reports/Google_Android_Security_2015_Report_Final.pdf">「驗è‰æ‡‰ç”¨ç¨‹å¼ã€å’Œ SafetyNet</a> 主動監控濫用情形；使用這些功能的目的是在發ç¾<a href="http://static.googleusercontent.com/media/source.android.com/en//security/reports/Google_Android_Security_PHA_classifications.pdf">å¯èƒ½æœ‰å®³çš„應用程å¼</a>時è¦å‘Šä½¿ç”¨è€…。「驗è‰æ‡‰ç”¨ç¨‹å¼ã€åœ¨æ載 <a href="http://www.android.com/gms">Google 行動æœå‹™</a>çš„è£ç½®ä¸Šéƒ½æœƒé è¨å•Ÿç”¨ï¼Œä¸”å°æ–¼è¦å¾ž Google Play 以外來æºå®‰è£æ‡‰ç”¨ç¨‹å¼çš„ä½¿ç”¨è€…ä¾†èªªæ ¼å¤–é‡è¦ã€‚Google Play ç¦æ¢ç™¼ä½ˆä»»ä½•å¯ç”¨æ–¼ç²å–è£ç½® Root 權é™çš„工具，但「驗è‰æ‡‰ç”¨ç¨‹å¼ã€æœƒåœ¨ä½¿ç”¨è€…嘗試安è£å·²åµæ¸¬åˆ°çš„ Root 權é™ç²å–æ‡‰ç”¨ç¨‹å¼ (無論其來æºç‚ºä½•) 時發出è¦å‘Šã€‚æ¤å¤–，「驗è‰æ‡‰ç”¨ç¨‹å¼ã€æœƒè¨æ³•æ‰¾å‡ºå·²çŸ¥æœƒåˆ©ç”¨æ¬Šé™å‡ç´šæ¼æ´žçš„惡æ„應用程å¼ï¼Œä¸¦å°éŽ–這類應用程å¼çš„安è£ä½œæ¥ã€‚如果使用者已安è£é€™é¡žæ‡‰ç”¨ç¨‹å¼ï¼Œã€Œé©—è‰æ‡‰ç”¨ç¨‹å¼ã€æœƒé€šçŸ¥ä½¿ç”¨è€…並嘗試移除åµæ¸¬åˆ°çš„應用程å¼ã€‚</li> +<li>Android 安全性å°çµ„採用<a href="http://static.googleusercontent.com/media/source.android.com/en//security/reports/Google_Android_Security_2015_Report_Final.pdf">「驗è‰æ‡‰ç”¨ç¨‹å¼ã€å’Œ SafetyNet</a> 主動監控濫用情形；使用這些功能的目的是在發ç¾<a href="http://static.googleusercontent.com/media/source.android.com/en//security/reports/Google_Android_Security_PHA_classifications.pdf">å¯èƒ½æœ‰å®³çš„應用程å¼</a>時è¦å‘Šä½¿ç”¨è€…。在é è¨æƒ…æ³ä¸‹ï¼Œæ載 <a href="http://www.android.com/gms">Google 行動æœå‹™</a>çš„è£ç½®æœƒè‡ªå‹•å•Ÿç”¨ã€Œé©—è‰æ‡‰ç”¨ç¨‹å¼ã€ã€‚å°æ–¼éœ€è¦å¾ž Google Play 以外的來æºå®‰è£æ‡‰ç”¨ç¨‹å¼çš„ä½¿ç”¨è€…ä¾†èªªï¼Œé€™é …é˜²è·æŽªæ–½æ ¼å¤–é‡è¦ã€‚雖然 Google Play ç¦æ¢ç™¼ä½ˆä»»ä½•å¯ç”¨æ–¼ç²å–è£ç½® Root 權é™çš„工具，但是當「驗è‰æ‡‰ç”¨ç¨‹å¼ã€åµæ¸¬åˆ°ä½¿ç”¨è€…嘗試安è£å…·æœ‰é€™é¡žç”¨é€”的應用程å¼æ™‚，無論其來æºç‚ºä½•ï¼Œéƒ½æœƒç™¼å‡ºè¦å‘Šã€‚æ¤å¤–，「驗è‰æ‡‰ç”¨ç¨‹å¼ã€æœƒè¨æ³•æ‰¾å‡ºå·²çŸ¥æœƒåˆ©ç”¨æ¬Šé™å‡ç´šæ¼æ´žçš„惡æ„應用程å¼ï¼Œä¸¦å°éŽ–這類應用程å¼çš„安è£ä½œæ¥ã€‚如果使用者已安è£é€™é¡žæ‡‰ç”¨ç¨‹å¼ï¼Œã€Œé©—è‰æ‡‰ç”¨ç¨‹å¼ã€æœƒé€šçŸ¥ä½¿ç”¨è€…並嘗試移除åµæ¸¬åˆ°çš„應用程å¼ã€‚</li> <li>在é©ç”¨æƒ…æ³ä¸‹ï¼ŒGoogle Hangouts å’Œ Messenger 應用程å¼ä¸æœƒè‡ªå‹•å°‡åª’體內容傳é€çµ¦åª’體伺æœå™¨é€™é¡žçš„處ç†ç¨‹åºã€‚</li> </ul> <h2 id="acknowledgements">特別銘è¬</h2> <p>æ„Ÿè¬ä»¥ä¸‹ç ”究人員åšå‡ºçš„è²¢ç»ï¼š</p> <ul> -<li>Google 動態工具å°çµ„æˆå“¡ Alexander Potapenko：CVE-2017-0537</li><li>阿里巴巴行動安全å°çµ„æˆå“¡ Baozeng Dingã€Chengming Yangã€Peng Xiao å’Œ Yang Song：CVE-2017-0506</li><li>阿里巴巴行動安全å°çµ„æˆå“¡ Baozeng Dingã€Ning Youã€Chengming Yangã€Peng Xiao å’Œ Yang Song：CVE-2017-0463</li><li>Android 安全性å°çµ„æˆå“¡ Billy Lau：CVE-2017-0335ã€CVE-2017-0336ã€CVE-2017-0338ã€CVE-2017-0460</li><li><a href="mailto:derrek.haxx@gmail.com">derrek</a> (<a href="https://twitter.com/derrekr6">@derrekr6</a>)：CVE-2016-8413ã€CVE-2016-8477ã€CVE-2017-0531</li><li><a href="mailto:derrek.haxx@gmail.com">derrek</a> (<a href="https://twitter.com/derrekr6">@derrekr6</a>) å’Œ <a href="mailto:sbauer@plzdonthack.me">Scott Bauer</a> (<a href="https://twitter.com/ScottyBauer1">@ScottyBauer1</a>)：CVE-2017-0521</li><li>騰訊科æ©å¯¦é©—室 (<a href="https://twitter.com/returnsme">@keen_lab</a>) çš„ Di Shen (<a href="https://twitter.com/keen_lab">@returnsme</a>)：CVE-2017-0334ã€CVE-2017-0456ã€CVE-2017-0457ã€CVE-2017-0525</li><li><a href="https://twitter.com/heeeeen4x">MS509Team</a> çš„ En He (<a href="http://www.ms509.com">@heeeeen4x</a>) å’Œ Bo Liu：CVE-2017-0490</li><li>奇虎 360 科技有é™å…¬å¸ IceSword 實驗室的 Gengjia Chen (<a href="https://twitter.com/chengjia4574">@chengjia4574</a>) å’Œ <a href="http://weibo.com/jfpan">pjf</a>：CVE-2017-0500ã€CVE-2017-0501ã€CVE-2017-0502ã€CVE-2017-0503ã€CVE-2017-0509ã€CVE-2017-0524ã€CVE-2017-0529ã€CVE-2017-0536</li><li>奇虎 360 科技有é™å…¬å¸ Alpha å°çµ„æˆå“¡ Hao Chen å’Œ Guang Gong：CVE-2017-0453ã€CVE-2017-0461ã€CVE-2017-0464</li><li>Sony Mobile Communications Inc. çš„ Hiroki Yamamoto å’Œ Fang Chen：CVE-2017-0481</li><li>IBM 安全性 X-Force ç ”ç©¶å“¡ Sagi Kedmi å’Œ Roee Hay：CVE-2017-0510</li><li><a href="https://twitter.com/Jioun_dai">奇虎 360 Skyeye 實驗室</a>çš„ Jianjun Dai (<a href="https://skyeye.360safe.com">@Jioun_dai</a>)：CVE-2017-0478</li><li>奇虎 360 IceSword 實驗室的 Jianqiang Zhao (<a href="https://twitter.com/jianqiangzhao">@jianqiangzhao</a>) å’Œ <a href="http://weibo.com/jfpan">pjf</a>：CVE-2016-8416ã€CVE-2016-8478ã€CVE-2017-0458ã€CVE-2017-0459ã€CVE-2017-0518ã€CVE-2017-0519ã€CVE-2017-0533ã€CVE-2017-0534</li><li><a href="mailto:zlbzlb815@163.com">C0RE å°çµ„</a>æˆå“¡ <a href="mailto:segfault5514@gmail.com">Lubo Zhang</a>ã€<a href="mailto:computernik@gmail.com">Tong Lin</a>ã€<a href="http://c0reteam.org">Yuan-Tsung Lo</a> å’Œ Xuxian Jiang：CVE-2016-8479</li><li>Google çš„ Makoto Onuki：CVE-2017-0491</li><li><a href="https://twitter.com/Mingjian_Zhou">C0RE å°çµ„</a>æˆå“¡ Mingjian Zhou (<a href="mailto:arnow117@gmail.com">@Mingjian_Zhou</a>)ã€<a href="http://c0reteam.org">Hanxiang Wen</a> å’Œ Xuxian Jiang：CVE-2017-0479ã€CVE-2017-0480</li><li>Nathan Crandall (<a href="https://twitter.com/natecray">@natecray</a>)：CVE-2017-0535</li><li>特斯拉產å“安全å°çµ„æˆå“¡ Nathan Crandall (<a href="https://twitter.com/natecray">@natecray</a>)：CVE-2017-0306</li><li>百度安全實驗室的 Pengfei Ding (ä¸é¹é£ž)ã€Chenfu Bao (包沉浮) å’Œ Lenx Wei (韦韬)：CVE-2016-8417</li><li>騰訊科æ©å¯¦é©—室的 Qidan He (何淇丹) (<a href="https://twitter.com/flanker_hqd">@flanker_hqd</a>)：CVE-2017-0337ã€CVE-2017-0476</li><li>奇虎 360 çš„ Qing Zhang å’Œæ–°åŠ å¡ç†å·¥å¤§å¸ (SIT) çš„ Guangdong Bai：CVE-2017-0496</li><li>螞蟻金æœå·´æ–¯å…‰å¹´å®‰å…¨å¯¦é©—室的 Quhe å’Œ wanchouchou：CVE-2017-0522</li><li>DarkMatter 安全通訊å°çµ„çš„ <a href="mailto:keun-o.park@darkmatter.ae">Sahara</a>：CVE-2017-0528</li><li>åŠ å·žå¤§å¸è–å¡”èŠèŠæ‹‰åˆ†æ ¡ Shellphish Grill å°çµ„çš„ salls (<a href="https://twitter.com/chris_salls">@chris_salls</a>)：CVE-2017-0505</li><li><a href="mailto:sbauer@plzdonthack.me">Scott Bauer</a> (<a href="https://twitter.com/ScottyBauer1">@ScottyBauer1</a>)：CVE-2017-0504ã€CVE-2017-0516</li><li>Sean Beaupre (beaups)：CVE-2017-0455</li><li>趨勢科技的 Seven Shen (<a href="https://twitter.com/lingtongshen">@lingtongshen</a>)：CVE-2017-0452</li><li>富士通的 Shinichi Matsumoto：CVE-2017-0498</li><li><a href="mailto:smarques84@gmail.com">ByteRev</a> çš„ <a href="http://www.byterev.com">Stéphane Marques</a>：CVE-2017-0489 -</li><li>Google çš„ Svetoslav Ganov：CVE-2017-0492</li><li><a href="mailto:segfault5514@gmail.com">C0RE å°çµ„</a>æˆå“¡ <a href="mailto:computernik@gmail.com">Tong Lin</a>ã€<a href="http://c0reteam.org">Yuan-Tsung Lo</a> å’Œ Xuxian Jiang：CVE-2017-0333</li><li><a href="https://twitter.com/vysea">趨勢科技</a><a href="http://blog.trendmicro.com/trendlabs-security-intelligence/category/mobile">行動å¨è„…ç ”ç©¶å°çµ„</a>æˆå“¡ V.E.O (<a href="http://www.trendmicro.com">@VYSEa</a>)：CVE-2017-0466ã€CVE-2017-0467ã€CVE-2017-0468ã€CVE-2017-0469ã€CVE-2017-0470ã€CVE-2017-0471ã€CVE-2017-0472ã€CVE-2017-0473ã€CVE-2017-0482ã€CVE-2017-0484ã€CVE-2017-0485ã€CVE-2017-0486ã€CVE-2017-0487ã€CVE-2017-0494ã€CVE-2017-0495</li><li>螞蟻金æœå·´æ–¯å…‰å¹´å®‰å…¨å¯¦é©—室的 Wish Wu (å´æ½æµ æ¤å½¼) (<a href="https://twitter.com/wish_wu">@wish_wu</a>)：CVE-2017-0477</li><li>奇虎 360 科技有é™å…¬å¸ Vulpecker å°çµ„æˆå“¡ Yu Pan：CVE-2017-0517ã€CVE-2017-0532</li><li><a href="http://c0reteam.org">C0RE å°çµ„</a>æˆå“¡ <a href="mailto:computernik@gmail.com">Yuan-Tsung Lo</a> å’Œ Xuxian Jiang：CVE-2017-0526ã€CVE-2017-0527</li><li><a href="https://twitter.com/nikos233__">C0RE å°çµ„</a>æˆå“¡ Yuqi Lu (<a href="mailto:vancouverdou@gmail.com">@nikos233</a>)ã€<a href="mailto:shaodacheng2016@gmail.com">Wenke Dou</a>ã€<a href="https://twitter.com/Mingjian_Zhou">Dacheng Shao</a>ã€Mingjian Zhou (<a href="http://c0reteam.org">@Mingjian_Zhou</a>) å’Œ Xuxian Jiang：CVE-2017-0483</li> +<li>Google 動態工具å°çµ„æˆå“¡ Alexander Potapenko：CVE-2017-0537</li><li>阿里巴巴行動安全å°çµ„æˆå“¡ Baozeng Dingã€Chengming Yangã€Peng Xiao å’Œ Yang Song：CVE-2017-0506</li><li>阿里巴巴行動安全å°çµ„æˆå“¡ Baozeng Dingã€Ning Youã€Chengming Yangã€Peng Xiao å’Œ Yang Song：CVE-2017-0463</li><li>Android 安全性å°çµ„æˆå“¡ Billy Lau：CVE-2017-0335ã€CVE-2017-0336ã€CVE-2017-0338ã€CVE-2017-0460</li><li><a href="mailto:derrek.haxx@gmail.com">derrek</a> (<a href="https://twitter.com/derrekr6">@derrekr6</a>)：CVE-2016-8413ã€CVE-2016-8477ã€CVE-2017-0531</li><li><a href="mailto:derrek.haxx@gmail.com">derrek</a> (<a href="https://twitter.com/derrekr6">@derrekr6</a>) å’Œ <a href="mailto:sbauer@plzdonthack.me">Scott Bauer</a> (<a href="https://twitter.com/ScottyBauer1">@ScottyBauer1</a>)：CVE-2017-0521</li><li>騰訊科æ©å¯¦é©—室 (<a href="https://twitter.com/returnsme">@keen_lab</a>) çš„ Di Shen (<a href="https://twitter.com/keen_lab">@returnsme</a>)：CVE-2017-0334ã€CVE-2017-0456ã€CVE-2017-0457ã€CVE-2017-0525</li><li><a href="https://twitter.com/heeeeen4x">MS509Team</a> çš„ En He (<a href="http://www.ms509.com">@heeeeen4x</a>) å’Œ Bo Liu：CVE-2017-0490</li><li>奇虎 360 科技有é™å…¬å¸ IceSword 實驗室的 Gengjia Chen (<a href="https://twitter.com/chengjia4574">@chengjia4574</a>) å’Œ <a href="http://weibo.com/jfpan">pjf</a>：CVE-2017-0500ã€CVE-2017-0501ã€CVE-2017-0502ã€CVE-2017-0503ã€CVE-2017-0509ã€CVE-2017-0524ã€CVE-2017-0529ã€CVE-2017-0536</li><li>奇虎 360 科技有é™å…¬å¸ Alpha å°çµ„æˆå“¡ Hao Chen å’Œ Guang Gong：CVE-2017-0453ã€CVE-2017-0461ã€CVE-2017-0464</li><li>Sony Mobile Communications Inc. çš„ Hiroki Yamamoto å’Œ Fang Chen：CVE-2017-0481</li><li>IBM 安全性 X-Force ç ”ç©¶å“¡ Sagi Kedmi å’Œ Roee Hay：CVE-2017-0510</li><li><a href="https://twitter.com/Jioun_dai">奇虎 360 Skyeye 實驗室</a>çš„ Jianjun Dai (<a href="https://skyeye.360safe.com">@Jioun_dai</a>)：CVE-2017-0478</li><li>奇虎 360 IceSword 實驗室的 Jianqiang Zhao (<a href="https://twitter.com/jianqiangzhao">@jianqiangzhao</a>) å’Œ <a href="http://weibo.com/jfpan">pjf</a>：CVE-2016-8416ã€CVE-2016-8478ã€CVE-2017-0458ã€CVE-2017-0459ã€CVE-2017-0518ã€CVE-2017-0519ã€CVE-2017-0533ã€CVE-2017-0534</li><li><a href="mailto:zlbzlb815@163.com">C0RE å°çµ„</a>æˆå“¡ <a href="mailto:segfault5514@gmail.com">Lubo Zhang</a>ã€<a href="mailto:computernik@gmail.com">Tong Lin</a>ã€<a href="http://c0reteam.org">Yuan-Tsung Lo</a> å’Œ Xuxian Jiang：CVE-2016-8479</li><li>Google çš„ Makoto Onuki：CVE-2017-0491</li><li><a href="https://twitter.com/Mingjian_Zhou">C0RE å°çµ„</a>æˆå“¡ Mingjian Zhou (<a href="mailto:arnow117@gmail.com">@Mingjian_Zhou</a>)ã€<a href="http://c0reteam.org">Hanxiang Wen</a> å’Œ Xuxian Jiang：CVE-2017-0479ã€CVE-2017-0480</li><li>Nathan Crandall (<a href="https://twitter.com/natecray">@natecray</a>)：CVE-2017-0535</li><li>特斯拉產å“安全å°çµ„æˆå“¡ Nathan Crandall (<a href="https://twitter.com/natecray">@natecray</a>)：CVE-2017-0306</li><li>百度安全實驗室的 Pengfei Ding (ä¸éµ¬é£›)ã€Chenfu Bao (包沉浮) å’Œ Lenx Wei (韋韜)：CVE-2016-8417</li><li>騰訊科æ©å¯¦é©—室的 Qidan He (何淇丹) (<a href="https://twitter.com/flanker_hqd">@flanker_hqd</a>)：CVE-2017-0337ã€CVE-2017-0476</li><li>奇虎 360 çš„ Qing Zhang å’Œæ–°åŠ å¡ç†å·¥å¤§å¸ (SIT) çš„ Guangdong Bai：CVE-2017-0496</li><li>螞蟻金æœå·´æ–¯å…‰å¹´å®‰å…¨å¯¦é©—室的 Quhe å’Œ wanchouchou：CVE-2017-0522</li><li>DarkMatter 安全通訊å°çµ„çš„ <a href="mailto:keun-o.park@darkmatter.ae">Sahara</a>：CVE-2017-0528</li><li>åŠ å·žå¤§å¸è–å¡”èŠèŠæ‹‰åˆ†æ ¡ Shellphish Grill å°çµ„çš„ salls (<a href="https://twitter.com/chris_salls">@chris_salls</a>)：CVE-2017-0505</li><li><a href="mailto:sbauer@plzdonthack.me">Scott Bauer</a> (<a href="https://twitter.com/ScottyBauer1">@ScottyBauer1</a>)：CVE-2017-0504ã€CVE-2017-0516</li><li>Sean Beaupre (beaups)：CVE-2017-0455</li><li>趨勢科技的 Seven Shen (<a href="https://twitter.com/lingtongshen">@lingtongshen</a>)：CVE-2017-0452</li><li>富士通的 Shinichi Matsumoto：CVE-2017-0498</li><li><a href="mailto:smarques84@gmail.com">ByteRev</a> çš„ <a href="http://www.byterev.com">Stéphane Marques</a>：CVE-2017-0489 +</li><li>Google çš„ Svetoslav Ganov：CVE-2017-0492</li><li><a href="mailto:segfault5514@gmail.com">C0RE å°çµ„</a>æˆå“¡ <a href="mailto:computernik@gmail.com">Tong Lin</a>ã€<a href="http://c0reteam.org">Yuan-Tsung Lo</a> å’Œ Xuxian Jiang：CVE-2017-0333</li><li><a href="https://twitter.com/vysea">趨勢科技</a><a href="http://blog.trendmicro.com/trendlabs-security-intelligence/category/mobile">行動å¨è„…ç ”ç©¶å°çµ„</a>æˆå“¡ V.E.O (<a href="http://www.trendmicro.com">@VYSEa</a>)：CVE-2017-0466ã€CVE-2017-0467ã€CVE-2017-0468ã€CVE-2017-0469ã€CVE-2017-0470ã€CVE-2017-0471ã€CVE-2017-0472ã€CVE-2017-0473ã€CVE-2017-0482ã€CVE-2017-0484ã€CVE-2017-0485ã€CVE-2017-0486ã€CVE-2017-0487ã€CVE-2017-0494ã€CVE-2017-0495</li><li>螞蟻金æœå·´æ–¯å…‰å¹´å®‰å…¨å¯¦é©—室的 Wish Wu (å´æ½æµ æ¤å½¼) (<a href="https://twitter.com/wish_wu">@wish_wu</a>)：CVE-2017-0477</li><li>奇虎 360 科技有é™å…¬å¸ Vulpecker å°çµ„æˆå“¡ Yu Pan：CVE-2017-0517ã€CVE-2017-0532</li><li><a href="mailto:computernik@gmail.com">C0RE å°çµ„</a>æˆå“¡ <a href="http://c0reteam.org">Yuan-Tsung Lo</a> å’Œ Xuxian Jiang：CVE-2017-0526ã€CVE-2017-0527</li><li><a href="https://twitter.com/nikos233__">C0RE å°çµ„</a>æˆå“¡ Yuqi Lu (<a href="mailto:vancouverdou@gmail.com">@nikos233</a>)ã€<a href="mailto:shaodacheng2016@gmail.com">Wenke Dou</a>ã€<a href="https://twitter.com/Mingjian_Zhou">Dacheng Shao</a>ã€Mingjian Zhou (<a href="http://c0reteam.org">@Mingjian_Zhou</a>) å’Œ Xuxian Jiang：CVE-2017-0483</li> <li>奇虎 360 科技有é™å…¬å¸æˆéƒ½å®‰å…¨æ€§æ‡‰è®Šä¸å¿ƒæˆå“¡ Zinuo Han (<a href="https://weibo.com/ele7enxxh">weibo.com/ele7enxxh</a>)：CVE-2017-0475ã€CVE-2017-0497</li></ul> <h2 id="2017-03-01-details">2017-03-01 安全性修補程å¼ç‰ç´š — 資安æ¼æ´žè©³æƒ…</h2> -<p>下列å„節é‡å° 2017-03-01 安全性修補程å¼ç‰ç´šé©ç”¨çš„å„é …å®‰å…¨æ€§æ¼æ´žæ供了詳細資訊，包括å•é¡Œèªªæ˜Žã€åš´é‡ç¨‹åº¦è©•å®šåŽŸå› ，以åŠä¸€ä»½æ¼æ´žè³‡è¨Šè¡¨ï¼Œé¡¯ç¤ºæ¼æ´žçš„ CVEã€ç›¸é—œåƒè€ƒè³‡æ–™ã€åš´é‡ç¨‹åº¦ã€æ›´æ–°çš„ Google è£ç½®ã€æ›´æ–°çš„ AOSP 版本 (在é©ç”¨æƒ…æ³ä¸‹) å’Œå›žå ±æ—¥æœŸã€‚å‡å¦‚相關錯誤有公開變更，該錯誤 ID 會連çµåˆ°ç›¸å°æ‡‰çš„變更 (例如 AOSP 變更清單)ã€‚å¦‚æžœå–®ä¸€éŒ¯èª¤æœ‰å¤šé …ç›¸é—œè®Šæ›´ï¼Œå…¶ä»–åƒè€ƒè³‡æ–™å¯é€éŽè©²éŒ¯èª¤ ID 後é¢çš„編號連çµé–‹å•Ÿã€‚</p> +<p>下列å„節é‡å° 2017-03-01 安全性修補程å¼ç‰ç´šé©ç”¨çš„å„é …å®‰å…¨æ€§æ¼æ´žæ供了詳細資訊，包括å•é¡Œèªªæ˜Žã€åš´é‡ç¨‹åº¦è©•å®šåŽŸå› ，以åŠä¸€ä»½æ¼æ´žè³‡è¨Šè¡¨ï¼Œé¡¯ç¤ºæ¼æ´žçš„ CVEã€ç›¸é—œåƒè€ƒè³‡æ–™ã€åš´é‡ç¨‹åº¦ã€æ›´æ–°çš„ Google è£ç½®ã€æ›´æ–°çš„ AOSP 版本 (在é©ç”¨æƒ…æ³ä¸‹) å’Œå›žå ±æ—¥æœŸã€‚å‡å¦‚相關錯誤有公開變更，該錯誤 ID 會連çµåˆ°ç›¸å°æ‡‰çš„變更 (例如 Android 開放原始碼計劃變更清單)ã€‚å¦‚æžœå–®ä¸€éŒ¯èª¤æœ‰å¤šé …ç›¸é—œè®Šæ›´ï¼Œå…¶ä»–åƒè€ƒè³‡æ–™å¯é€éŽè©²éŒ¯èª¤ ID 後é¢çš„編號連çµé–‹å•Ÿã€‚</p> <h3 id="rce-in-openssl-&-boringssl">OpenSSL å’Œ BoringSSL ä¸çš„é 端程å¼ç¢¼åŸ·è¡Œæ¼æ´ž</h3> <p>在檔案和資料的處ç†æœŸé–“，OpenSSL å’Œ BoringSSL ä¸çš„é 端程å¼ç¢¼åŸ·è¡Œæ¼æ´žå¯èƒ½æœƒè®“æ”»æ“Šè€…èƒ½åˆ©ç”¨ç‰¹è£½æª”æ¡ˆé€ æˆè¨˜æ†¶é«”出錯。由於這個å•é¡Œå¯èƒ½æœƒè®“é 端程å¼ç¢¼åœ¨ç²å¾—授權的程åºç’°å¢ƒå…§åŸ·è¡Œï¼Œå› æ¤åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œæœ€é«˜ã€ã€‚</p> @@ -67,7 +67,7 @@ <th>åƒè€ƒè³‡æ–™</th> <th>åš´é‡ç¨‹åº¦</th> <th>æ›´æ–°çš„ Google è£ç½®</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -96,7 +96,7 @@ <th>åƒè€ƒè³‡æ–™</th> <th>åš´é‡ç¨‹åº¦</th> <th>æ›´æ–°çš„ Google è£ç½®</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -200,7 +200,7 @@ <th>åƒè€ƒè³‡æ–™</th> <th>åš´é‡ç¨‹åº¦</th> <th>æ›´æ–°çš„ Google è£ç½®</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -214,8 +214,8 @@ </tr> </tbody></table> -<h3 id="rce-in-aosp-messaging">AOSP Messaging ä¸çš„é 端程å¼ç¢¼åŸ·è¡Œæ¼æ´ž</h3> -<p>在媒體檔案和資料的處ç†æœŸé–“，AOSP Messaging ä¸çš„é 端程å¼ç¢¼åŸ·è¡Œæ¼æ´žå¯èƒ½æœƒè®“æ”»æ“Šè€…èƒ½åˆ©ç”¨ç‰¹è£½æª”æ¡ˆé€ æˆè¨˜æ†¶é«”出錯。由於這個å•é¡Œå¯èƒ½æœƒè®“é 端程å¼ç¢¼åœ¨æœªç²æŽˆæ¬Šçš„程åºç’°å¢ƒå…§åŸ·è¡Œï¼Œå› æ¤åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚</p> +<h3 id="rce-in-aosp-messaging">Android 開放原始碼計劃 Messaging ä¸çš„é 端程å¼ç¢¼åŸ·è¡Œæ¼æ´ž</h3> +<p>在媒體檔案和資料的處ç†æœŸé–“，Android 開放原始碼計劃 Messaging ä¸çš„é 端程å¼ç¢¼åŸ·è¡Œæ¼æ´žå¯èƒ½æœƒè®“æ”»æ“Šè€…èƒ½åˆ©ç”¨ç‰¹è£½æª”æ¡ˆé€ æˆè¨˜æ†¶é«”出錯。由於這個å•é¡Œå¯èƒ½æœƒè®“é 端程å¼ç¢¼åœ¨æœªç²æŽˆæ¬Šçš„程åºç’°å¢ƒå…§åŸ·è¡Œï¼Œå› æ¤åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚</p> <table> <colgroup><col width="18%" /> @@ -229,7 +229,7 @@ <th>åƒè€ƒè³‡æ–™</th> <th>åš´é‡ç¨‹åº¦</th> <th>æ›´æ–°çš„ Google è£ç½®</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -258,7 +258,7 @@ <th>åƒè€ƒè³‡æ–™</th> <th>åš´é‡ç¨‹åº¦</th> <th>æ›´æ–°çš„ Google è£ç½®</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -287,7 +287,7 @@ <th>åƒè€ƒè³‡æ–™</th> <th>åš´é‡ç¨‹åº¦</th> <th>æ›´æ–°çš„ Google è£ç½®</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -316,7 +316,7 @@ <th>åƒè€ƒè³‡æ–™</th> <th>åš´é‡ç¨‹åº¦</th> <th>æ›´æ–°çš„ Google è£ç½®</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -345,7 +345,7 @@ <th>åƒè€ƒè³‡æ–™</th> <th>åš´é‡ç¨‹åº¦</th> <th>æ›´æ–°çš„ Google è£ç½®</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -506,7 +506,7 @@ <th>åƒè€ƒè³‡æ–™</th> <th>åš´é‡ç¨‹åº¦</th> <th>æ›´æ–°çš„ Google è£ç½®</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -538,7 +538,7 @@ <th>åƒè€ƒè³‡æ–™</th> <th>åš´é‡ç¨‹åº¦</th> <th>æ›´æ–°çš„ Google è£ç½®</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -598,7 +598,7 @@ <th>åƒè€ƒè³‡æ–™</th> <th>åš´é‡ç¨‹åº¦</th> <th>æ›´æ–°çš„ Google è£ç½®</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -627,7 +627,7 @@ <th>åƒè€ƒè³‡æ–™</th> <th>åš´é‡ç¨‹åº¦</th> <th>æ›´æ–°çš„ Google è£ç½®</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -656,7 +656,7 @@ <th>åƒè€ƒè³‡æ–™</th> <th>åš´é‡ç¨‹åº¦</th> <th>æ›´æ–°çš„ Google è£ç½®</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -686,7 +686,7 @@ <th>åƒè€ƒè³‡æ–™</th> <th>åš´é‡ç¨‹åº¦</th> <th>æ›´æ–°çš„ Google è£ç½®</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -715,7 +715,7 @@ <th>åƒè€ƒè³‡æ–™</th> <th>åš´é‡ç¨‹åº¦</th> <th>æ›´æ–°çš„ Google è£ç½®</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> <th>å›žå ±æ—¥æœŸ</th> </tr> <tr> @@ -761,10 +761,10 @@ </tbody></table> <h2 id="2017-03-05-details">2017-03-05 安全性修補程å¼ç‰ç´š — 資安æ¼æ´žè©³æƒ…</h2> -<p>下列å„節é‡å° 2017-03-05 安全性修補程å¼ç‰ç´šé©ç”¨çš„å„é …å®‰å…¨æ€§æ¼æ´žæ供了詳細資訊，包括å•é¡Œèªªæ˜Žã€åš´é‡ç¨‹åº¦è©•å®šåŽŸå› ，以åŠä¸€ä»½æ¼æ´žè³‡è¨Šè¡¨ï¼Œé¡¯ç¤ºæ¼æ´žçš„ CVEã€ç›¸é—œåƒè€ƒè³‡æ–™ã€åš´é‡ç¨‹åº¦ã€æ›´æ–°çš„ Google è£ç½®ã€æ›´æ–°çš„ AOSP 版本 (在é©ç”¨æƒ…æ³ä¸‹) å’Œå›žå ±æ—¥æœŸã€‚å‡å¦‚相關錯誤有公開變更，該錯誤 ID 會連çµåˆ°ç›¸å°æ‡‰çš„變更 (例如 AOSP 變更清單)ã€‚å¦‚æžœå–®ä¸€éŒ¯èª¤æœ‰å¤šé …ç›¸é—œè®Šæ›´ï¼Œå…¶ä»–åƒè€ƒè³‡æ–™å¯é€éŽè©²éŒ¯èª¤ ID 後é¢çš„編號連çµé–‹å•Ÿã€‚</p> +<p>下列å„節é‡å° 2017-03-05 安全性修補程å¼ç‰ç´šé©ç”¨çš„å„é …å®‰å…¨æ€§æ¼æ´žæ供了詳細資訊，包括å•é¡Œèªªæ˜Žã€åš´é‡ç¨‹åº¦è©•å®šåŽŸå› ，以åŠä¸€ä»½æ¼æ´žè³‡è¨Šè¡¨ï¼Œé¡¯ç¤ºæ¼æ´žçš„ CVEã€ç›¸é—œåƒè€ƒè³‡æ–™ã€åš´é‡ç¨‹åº¦ã€æ›´æ–°çš„ Google è£ç½®ã€æ›´æ–°çš„ AOSP 版本 (在é©ç”¨æƒ…æ³ä¸‹) å’Œå›žå ±æ—¥æœŸã€‚å‡å¦‚相關錯誤有公開變更，該錯誤 ID 會連çµåˆ°ç›¸å°æ‡‰çš„變更 (例如 Android 開放原始碼計劃變更清單)ã€‚å¦‚æžœå–®ä¸€éŒ¯èª¤æœ‰å¤šé …ç›¸é—œè®Šæ›´ï¼Œå…¶ä»–åƒè€ƒè³‡æ–™å¯é€éŽè©²éŒ¯èª¤ ID 後é¢çš„編號連çµé–‹å•Ÿã€‚</p> <h3 id="eop-in-mediatek-components">MediaTek 元件ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> -<p>MediaTek 元件 (包括 M4U 驅動程å¼ã€éŸ³æ•ˆé©…動程å¼ã€è§¸æŽ§èž¢å¹•é©…動程å¼ã€GPU 驅動程å¼å’ŒæŒ‡ä»¤ä½‡åˆ—驅動程å¼) ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•æŒ‡ä»¤ã€‚由於這個å•é¡Œå¯èƒ½å°Žè‡´æœ¬æ©Ÿè£ç½®çš„å®‰å…¨æ€§å¾¹åº•è¢«ç ´å£žï¼Œé€ æˆä½¿ç”¨è€…å¿…é ˆä»¥é‚„åŽŸ (Re-flash) 作æ¥ç³»çµ±çš„æ–¹å¼æ‰èƒ½ä¿®å¾©è£ç½®ï¼Œå› æ¤åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œæœ€é«˜ã€ã€‚</p> +<p>MediaTek 元件 (包括 M4U 驅動程å¼ã€éŸ³æ•ˆé©…動程å¼ã€è§¸æŽ§èž¢å¹•é©…動程å¼ã€GPU 驅動程å¼å’ŒæŒ‡ä»¤ä½‡åˆ—驅動程å¼) ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚由於這個å•é¡Œå¯èƒ½å°Žè‡´æœ¬æ©Ÿè£ç½®çš„å®‰å…¨æ€§å¾¹åº•è¢«ç ´å£žï¼Œé€ æˆä½¿ç”¨è€…å¿…é ˆä»¥é‚„åŽŸ (Reflash) 作æ¥ç³»çµ±çš„æ–¹å¼æ‰èƒ½ä¿®å¾©è£ç½®ï¼Œå› æ¤åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œæœ€é«˜ã€ã€‚</p> <table> <colgroup><col width="19%" /> @@ -956,7 +956,7 @@ <td>2016 å¹´ 10 月 12 æ—¥</td> </tr> </tbody></table> -<p>* 這個å•é¡Œçš„修補程å¼ä¸¦æœªé–‹æ”¾çµ¦ä¸€èˆ¬ä½¿ç”¨è€…下載，而是直接整åˆåœ¨æœ€æ–°çš„ Nexus è£ç½®å°ˆç”¨é©…動程å¼çš„安è£æª”ä¸ã€‚您å¯ä»¥å‰å¾€ <a href="https://developers.google.com/android/nexus/drivers">Google Developers 網站</a>下載這些驅動程å¼ã€‚</p> +<p>* 這個å•é¡Œçš„修補程å¼ä¸¦æœªé–‹æ”¾çµ¦ä¸€èˆ¬ä½¿ç”¨è€…下載，相關的更新已直接整åˆåœ¨æœ€æ–°çš„ Nexus è£ç½®å°ˆç”¨é©…動程å¼çš„安è£æª”ä¸ã€‚您å¯ä»¥å‰å¾€ <a href="https://developers.google.com/android/nexus/drivers">Google Developers 網站</a>下載這些驅動程å¼ã€‚</p> <p>** 如果是æ載 Android 7.0 以上版本的 Google è£ç½® (å¿…é ˆæ˜¯å—支æ´çš„機型，且已安è£æ‰€æœ‰å¯ç”¨æ›´æ–°)，就ä¸æœƒå—到這個æ¼æ´žå½±éŸ¿ã€‚</p> <h3 id="eop-in-kernel-fiq-debugger">æ ¸å¿ƒ FIQ åµéŒ¯å·¥å…·ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> @@ -1105,7 +1105,7 @@ <p>*** 如果是æ載 Android 7.0 以上版本的 Google è£ç½® (å¿…é ˆæ˜¯å—支æ´çš„機型，且已安è£æ‰€æœ‰å¯ç”¨æ›´æ–°)，就ä¸æœƒå—到這個æ¼æ´žå½±éŸ¿ã€‚</p> <h3 id="eop-in-kernel-networking-subsystem-2">æ ¸å¿ƒç¶²è·¯å系統ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> -<p>æ ¸å¿ƒç¶²è·¯å系統ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•æŒ‡ä»¤ã€‚ç”±æ–¼é€™ç¨®æ”»æ“Šå¿…é ˆå…ˆç ´å£žç‰¹å®šç²æŽˆæ¬Šçš„程åºæ‰èƒ½åŸ·è¡Œï¼Œå› æ¤é€™å€‹å•é¡Œçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚</p> +<p>æ ¸å¿ƒç¶²è·¯å系統ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚ç”±æ–¼é€™ç¨®æ”»æ“Šå¿…é ˆå…ˆç ´è§£å…·æœ‰ç‰¹å®šæ¬Šé™çš„程åºæ‰èƒ½åŸ·è¡Œï¼Œå› æ¤é€™å€‹å•é¡Œçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚</p> <table> <colgroup><col width="19%" /> @@ -1141,7 +1141,7 @@ </tbody></table> <h3 id="eop-in-qualcomm-input-hardware-driver">Qualcomm 輸入硬體驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> -<p>Qualcomm 輸入硬體驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•æŒ‡ä»¤ã€‚ç”±æ–¼é€™ç¨®æ”»æ“Šå¿…é ˆå…ˆç ´å£žç‰¹å®šç²æŽˆæ¬Šçš„程åºæ‰èƒ½åŸ·è¡Œï¼Œå› æ¤é€™å€‹å•é¡Œçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚</p> +<p>Qualcomm 輸入硬體驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚ç”±æ–¼é€™ç¨®æ”»æ“Šå¿…é ˆå…ˆç ´è§£å…·æœ‰ç‰¹å®šæ¬Šé™çš„程åºæ‰èƒ½åŸ·è¡Œï¼Œå› æ¤é€™å€‹å•é¡Œçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚</p> <table> <colgroup><col width="19%" /> @@ -1196,7 +1196,7 @@ <p>** 如果是æ載 Android 7.0 以上版本的 Google è£ç½® (å¿…é ˆæ˜¯å—支æ´çš„機型，且已安è£æ‰€æœ‰å¯ç”¨æ›´æ–°)，就ä¸æœƒå—到這個æ¼æ´žæ‰€å½±éŸ¿ã€‚</p> <h3 id="eop-in-qualcomm-adsprpc-driver">Qualcomm ADSPRPC 驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> -<p>Qualcomm ADSPRPC 驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•æŒ‡ä»¤ã€‚ç”±æ–¼é€™ç¨®æ”»æ“Šå¿…é ˆå…ˆç ´å£žç‰¹å®šç²æŽˆæ¬Šçš„程åºæ‰èƒ½åŸ·è¡Œï¼Œå› æ¤é€™å€‹å•é¡Œçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚</p> +<p>Qualcomm ADSPRPC 驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•æŒ‡ä»¤ã€‚ç”±æ–¼é€™ç¨®æ”»æ“Šå¿…é ˆå…ˆç ´è§£å…·æœ‰ç‰¹å®šæ¬Šé™çš„程åºæ‰èƒ½åŸ·è¡Œï¼Œå› æ¤é€™å€‹å•é¡Œçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚</p> <table> <colgroup><col width="19%" /> @@ -1286,7 +1286,7 @@ QC-CR#1082636</a></td> </tbody></table> <h3 id="eop-in-qualcomm-camera-driver">Qualcomm 相機驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> -<p>Qualcomm 相機驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•æŒ‡ä»¤ã€‚ç”±æ–¼é€™ç¨®æ”»æ“Šå¿…é ˆå…ˆç ´å£žç‰¹å®šç²æŽˆæ¬Šçš„程åºæ‰èƒ½åŸ·è¡Œï¼Œå› æ¤é€™å€‹å•é¡Œçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚</p> +<p>Qualcomm 相機驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•æŒ‡ä»¤ã€‚ç”±æ–¼é€™ç¨®æ”»æ“Šå¿…é ˆå…ˆç ´è§£å…·æœ‰ç‰¹å®šæ¬Šé™çš„程åºæ‰èƒ½åŸ·è¡Œï¼Œå› æ¤é€™å€‹å•é¡Œçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚</p> <table> <colgroup><col width="19%" /> @@ -1346,11 +1346,11 @@ QC-CR#1097709</a></td> <td>2016 å¹´ 11 月 15 æ—¥</td> </tr> </tbody></table> -<p>* 這個å•é¡Œçš„修補程å¼ä¸¦æœªé–‹æ”¾çµ¦ä¸€èˆ¬ä½¿ç”¨è€…下載，而是直接整åˆåœ¨æœ€æ–°çš„ Nexus è£ç½®å°ˆç”¨é©…動程å¼çš„安è£æª”ä¸ã€‚您å¯ä»¥å‰å¾€ <a href="https://developers.google.com/android/nexus/drivers">Google Developers 網站</a>下載這些驅動程å¼ã€‚</p> +<p>* 這個å•é¡Œçš„修補程å¼ä¸¦æœªé–‹æ”¾çµ¦ä¸€èˆ¬ä½¿ç”¨è€…下載，相關的更新已直接整åˆåœ¨æœ€æ–°çš„ Nexus è£ç½®å°ˆç”¨é©…動程å¼çš„安è£æª”ä¸ã€‚您å¯ä»¥å‰å¾€ <a href="https://developers.google.com/android/nexus/drivers">Google Developers 網站</a>下載這些驅動程å¼ã€‚</p> <p>** 如果是æ載 Android 7.0 以上版本的 Google è£ç½® (å¿…é ˆæ˜¯å—支æ´çš„機型，且已安è£æ‰€æœ‰å¯ç”¨æ›´æ–°)，就ä¸æœƒå—到這個æ¼æ´žæ‰€å½±éŸ¿ã€‚</p> <h3 id="eop-in-qualcomm-wi-fi-driver">Qualcomm Wi-Fi 驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> -<p>Qualcomm Wi-Fi 驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•æŒ‡ä»¤ã€‚ç”±æ–¼é€™ç¨®æ”»æ“Šå¿…é ˆå…ˆç ´å£žç‰¹å®šç²æŽˆæ¬Šçš„程åºæ‰èƒ½åŸ·è¡Œï¼Œå› æ¤é€™å€‹å•é¡Œçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚</p> +<p>Qualcomm Wi-Fi 驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•æŒ‡ä»¤ã€‚ç”±æ–¼é€™ç¨®æ”»æ“Šå¿…é ˆå…ˆç ´è§£å…·æœ‰ç‰¹å®šæ¬Šé™çš„程åºæ‰èƒ½åŸ·è¡Œï¼Œå› æ¤é€™å€‹å•é¡Œçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚</p> <table> <colgroup><col width="19%" /> @@ -1514,7 +1514,7 @@ QC-CR#1096945</a></td> <td>2016 å¹´ 11 月 28 æ—¥</td> </tr> </tbody></table> -<p>* 這個å•é¡Œçš„修補程å¼ä¸¦æœªé–‹æ”¾çµ¦ä¸€èˆ¬ä½¿ç”¨è€…下載，而是直接整åˆåœ¨æœ€æ–°çš„ Nexus è£ç½®å°ˆç”¨é©…動程å¼çš„安è£æª”ä¸ã€‚您å¯ä»¥å‰å¾€ <a href="https://developers.google.com/android/nexus/drivers">Google Developers 網站</a>下載這些驅動程å¼ã€‚</p> +<p>* 這個å•é¡Œçš„修補程å¼ä¸¦æœªé–‹æ”¾çµ¦ä¸€èˆ¬ä½¿ç”¨è€…下載，相關的更新已直接整åˆåœ¨æœ€æ–°çš„ Nexus è£ç½®å°ˆç”¨é©…動程å¼çš„安è£æª”ä¸ã€‚您å¯ä»¥å‰å¾€ <a href="https://developers.google.com/android/nexus/drivers">Google Developers 網站</a>下載這些驅動程å¼ã€‚</p> <p>** 如果是æ載 Android 7.0 以上版本的 Google è£ç½® (å¿…é ˆæ˜¯å—支æ´çš„機型，且已安è£æ‰€æœ‰å¯ç”¨æ›´æ–°)，就ä¸æœƒå—到這個æ¼æ´žæ‰€å½±éŸ¿ã€‚</p> <h3 id="eop-in-qualcomm-networking-driver">Qualcomm 網路驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> @@ -1668,7 +1668,7 @@ QC-CR#1094140</a></td> <td>2016 å¹´ 4 月 27 æ—¥</td> </tr> </tbody></table> -<p>* 這個å•é¡Œçš„修補程å¼ä¸¦æœªé–‹æ”¾çµ¦ä¸€èˆ¬ä½¿ç”¨è€…下載，而是直接整åˆåœ¨æœ€æ–°çš„ Nexus è£ç½®å°ˆç”¨é©…動程å¼çš„安è£æª”ä¸ã€‚您å¯ä»¥å‰å¾€ <a href="https://developers.google.com/android/nexus/drivers">Google Developers 網站</a>下載這些驅動程å¼ã€‚</p> +<p>* 這個å•é¡Œçš„修補程å¼ä¸¦æœªé–‹æ”¾çµ¦ä¸€èˆ¬ä½¿ç”¨è€…下載，相關的更新已直接整åˆåœ¨æœ€æ–°çš„ Nexus è£ç½®å°ˆç”¨é©…動程å¼çš„安è£æª”ä¸ã€‚您å¯ä»¥å‰å¾€ <a href="https://developers.google.com/android/nexus/drivers">Google Developers 網站</a>下載這些驅動程å¼ã€‚</p> <p>** 如果是æ載 Android 7.0 以上版本的 Google è£ç½® (å¿…é ˆæ˜¯å—支æ´çš„機型，且已安è£æ‰€æœ‰å¯ç”¨æ›´æ–°)，就ä¸æœƒå—到這個æ¼æ´žå½±éŸ¿ã€‚</p> <h3 id="id-in-qualcomm-bootloader">Qualcomm 系統啟動載入程å¼ä¸çš„資訊外洩æ¼æ´ž</h3> @@ -1942,7 +1942,7 @@ QC-CR#1088206</a></td> </tbody></table> <h3 id="id-in-qualcomm-camera-driver">Qualcomm 相機驅動程å¼ä¸çš„資訊外洩æ¼æ´ž</h3> -<p>Qualcomm 相機驅動程å¼ä¸çš„資訊外洩æ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼å˜å–其權é™ç¯„åœä»¥å¤–çš„è³‡æ–™ã€‚ç”±æ–¼é€™ç¨®æ”»æ“Šå¿…é ˆå…ˆç ´å£žç‰¹å®šç²æŽˆæ¬Šçš„程åºæ‰èƒ½åŸ·è¡Œï¼Œå› æ¤é€™å€‹å•é¡Œçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œä¸ã€ã€‚</p> +<p>Qualcomm 相機驅動程å¼ä¸çš„資訊外洩æ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼å˜å–其權é™ç¯„åœä»¥å¤–çš„è³‡æ–™ã€‚ç”±æ–¼é€™ç¨®æ”»æ“Šå¿…é ˆå…ˆç ´è§£å…·æœ‰ç‰¹å®šæ¬Šé™çš„程åºæ‰èƒ½åŸ·è¡Œï¼Œå› æ¤é€™å€‹å•é¡Œçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œä¸ã€ã€‚</p> <table> <colgroup><col width="19%" /> @@ -2005,7 +2005,7 @@ QC-CR#1090007</a> <p>* 這個å•é¡Œçš„修補程å¼ä¸¦æœªé–‹æ”¾çµ¦ä¸€èˆ¬ä½¿ç”¨è€…下載，而是直接整åˆåœ¨æœ€æ–°çš„ Nexus è£ç½®å°ˆç”¨é©…動程å¼çš„安è£æª”ä¸ã€‚您å¯ä»¥å‰å¾€ <a href="https://developers.google.com/android/nexus/drivers">Google Developers 網站</a>下載這些驅動程å¼ã€‚</p> <h3 id="id-in-synaptics-touchscreen-driver">Synaptics 觸控螢幕驅動程å¼ä¸çš„資訊外洩æ¼æ´ž</h3> -<p>Synaptics 觸控螢幕驅動程å¼ä¸çš„資訊外洩æ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼å˜å–其權é™ç¯„åœä»¥å¤–çš„è³‡æ–™ã€‚ç”±æ–¼é€™ç¨®æ”»æ“Šå¿…é ˆå…ˆç ´å£žç‰¹å®šç²æŽˆæ¬Šçš„程åºæ‰èƒ½åŸ·è¡Œï¼Œå› æ¤é€™å€‹å•é¡Œçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œä¸ã€ã€‚</p> +<p>Synaptics 觸控螢幕驅動程å¼ä¸çš„資訊外洩æ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼å˜å–其權é™ç¯„åœä»¥å¤–çš„è³‡æ–™ã€‚ç”±æ–¼é€™ç¨®æ”»æ“Šå¿…é ˆå…ˆç ´è§£å…·æœ‰ç‰¹å®šæ¬Šé™çš„程åºæ‰èƒ½åŸ·è¡Œï¼Œå› æ¤é€™å€‹å•é¡Œçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œä¸ã€ã€‚</p> <table> <colgroup><col width="19%" /> diff --git a/zh-tw/security/bulletin/2017-05-01.html b/zh-tw/security/bulletin/2017-05-01.html index 4cbd02a0..0603f671 100644 --- a/zh-tw/security/bulletin/2017-05-01.html +++ b/zh-tw/security/bulletin/2017-05-01.html @@ -561,7 +561,7 @@ </tr> </tbody></table> -<p>* 這個å•é¡Œçš„修補程å¼ä¸¦æœªé–‹æ”¾çµ¦ä¸€èˆ¬ä½¿ç”¨è€…下載，而是直接整åˆåœ¨æœ€æ–°çš„ Nexus è£ç½®å°ˆç”¨é©…動程å¼çš„安è£æª”ä¸ã€‚您å¯ä»¥å‰å¾€ <a href="https://developers.google.com/android/nexus/drivers">Google Developers 網站</a>下載這些驅動程å¼ã€‚</p> +<p>* 這個å•é¡Œçš„修補程å¼ä¸¦æœªé–‹æ”¾çµ¦ä¸€èˆ¬ä½¿ç”¨è€…下載，相關的更新已直接整åˆåœ¨æœ€æ–°çš„ Nexus è£ç½®å°ˆç”¨é©…動程å¼çš„安è£æª”ä¸ã€‚您å¯ä»¥å‰å¾€ <a href="https://developers.google.com/android/nexus/drivers">Google Developers 網站</a>下載這些驅動程å¼ã€‚</p> <p>** 如果是æ載 Android 7.1.1 以上版本的 Google è£ç½® (å¿…é ˆæ˜¯å—支æ´çš„機型，且已安è£æ‰€æœ‰å¯ç”¨æ›´æ–°)，就ä¸æœƒå—到這個æ¼æ´žæ‰€å½±éŸ¿ã€‚</p> @@ -849,7 +849,7 @@ QC-CR#826589</a></td> </tr> </tbody></table> -<p>* 這個å•é¡Œçš„修補程å¼ä¸¦æœªé–‹æ”¾çµ¦ä¸€èˆ¬ä½¿ç”¨è€…下載，而是直接整åˆåœ¨æœ€æ–°çš„ Nexus è£ç½®å°ˆç”¨é©…動程å¼çš„安è£æª”ä¸ã€‚您å¯ä»¥å‰å¾€ <a href="https://developers.google.com/android/nexus/drivers">Google Developers 網站</a>下載這些驅動程å¼ã€‚</p> +<p>* 這個å•é¡Œçš„修補程å¼ä¸¦æœªé–‹æ”¾çµ¦ä¸€èˆ¬ä½¿ç”¨è€…下載，相關的更新已直接整åˆåœ¨æœ€æ–°çš„ Nexus è£ç½®å°ˆç”¨é©…動程å¼çš„安è£æª”ä¸ã€‚您å¯ä»¥å‰å¾€ <a href="https://developers.google.com/android/nexus/drivers">Google Developers 網站</a>下載這些驅動程å¼ã€‚</p> <p>** 如果是æ載 Android 7.1.1 以上版本的 Google è£ç½® (å¿…é ˆæ˜¯å—支æ´çš„機型，且已安è£æ‰€æœ‰å¯ç”¨æ›´æ–°)，就ä¸æœƒå—到這個æ¼æ´žæ‰€å½±éŸ¿ã€‚</p> @@ -1289,7 +1289,7 @@ QC-CR#1080290</a></td> </tr> </tbody></table> -<p>* 這個å•é¡Œçš„修補程å¼ä¸¦æœªé–‹æ”¾çµ¦ä¸€èˆ¬ä½¿ç”¨è€…下載，而是直接整åˆåœ¨æœ€æ–°çš„ Nexus è£ç½®å°ˆç”¨é©…動程å¼çš„安è£æª”ä¸ã€‚您å¯ä»¥å‰å¾€ <a href="https://developers.google.com/android/nexus/drivers">Google Developers 網站</a>下載這些驅動程å¼ã€‚</p> +<p>* 這個å•é¡Œçš„修補程å¼ä¸¦æœªé–‹æ”¾çµ¦ä¸€èˆ¬ä½¿ç”¨è€…下載，相關的更新已直接整åˆåœ¨æœ€æ–°çš„ Nexus è£ç½®å°ˆç”¨é©…動程å¼çš„安è£æª”ä¸ã€‚您å¯ä»¥å‰å¾€ <a href="https://developers.google.com/android/nexus/drivers">Google Developers 網站</a>下載這些驅動程å¼ã€‚</p> <p>** 如果是æ載 Android 7.1.1 以上版本的 Google è£ç½® (å¿…é ˆæ˜¯å—支æ´çš„機型，且已安è£æ‰€æœ‰å¯ç”¨æ›´æ–°)，就ä¸æœƒå—到這個æ¼æ´žæ‰€å½±éŸ¿ã€‚</p> @@ -1351,7 +1351,7 @@ QC-CR#1080290</a></td> </tr> </tbody></table> -<p>* 這個å•é¡Œçš„修補程å¼ä¸¦æœªé–‹æ”¾çµ¦ä¸€èˆ¬ä½¿ç”¨è€…下載，而是直接整åˆåœ¨æœ€æ–°çš„ Nexus è£ç½®å°ˆç”¨é©…動程å¼çš„安è£æª”ä¸ã€‚您å¯ä»¥å‰å¾€ <a href="https://developers.google.com/android/nexus/drivers">Google Developers 網站</a>下載這些驅動程å¼ã€‚</p> +<p>* 這個å•é¡Œçš„修補程å¼ä¸¦æœªé–‹æ”¾çµ¦ä¸€èˆ¬ä½¿ç”¨è€…下載，相關的更新已直接整åˆåœ¨æœ€æ–°çš„ Nexus è£ç½®å°ˆç”¨é©…動程å¼çš„安è£æª”ä¸ã€‚您å¯ä»¥å‰å¾€ <a href="https://developers.google.com/android/nexus/drivers">Google Developers 網站</a>下載這些驅動程å¼ã€‚</p> <p>** 如果是æ載 Android 7.1.1 以上版本的 Google è£ç½® (å¿…é ˆæ˜¯å—支æ´çš„機型，且已安è£æ‰€æœ‰å¯ç”¨æ›´æ–°)，就ä¸æœƒå—到這個æ¼æ´žæ‰€å½±éŸ¿ã€‚</p> @@ -1382,7 +1382,7 @@ QC-CR#1080290</a></td> </tr> </tbody></table> -<p>* 這個å•é¡Œçš„修補程å¼ä¸¦æœªé–‹æ”¾çµ¦ä¸€èˆ¬ä½¿ç”¨è€…下載，而是直接整åˆåœ¨æœ€æ–°çš„ Nexus è£ç½®å°ˆç”¨é©…動程å¼çš„安è£æª”ä¸ã€‚您å¯ä»¥å‰å¾€ <a href="https://developers.google.com/android/nexus/drivers">Google Developers 網站</a>下載這些驅動程å¼ã€‚</p> +<p>* 這個å•é¡Œçš„修補程å¼ä¸¦æœªé–‹æ”¾çµ¦ä¸€èˆ¬ä½¿ç”¨è€…下載，相關的更新已直接整åˆåœ¨æœ€æ–°çš„ Nexus è£ç½®å°ˆç”¨é©…動程å¼çš„安è£æª”ä¸ã€‚您å¯ä»¥å‰å¾€ <a href="https://developers.google.com/android/nexus/drivers">Google Developers 網站</a>下載這些驅動程å¼ã€‚</p> <p>** 如果是æ載 Android 7.1.1 以上版本的 Google è£ç½® (å¿…é ˆæ˜¯å—支æ´çš„機型，且已安è£æ‰€æœ‰å¯ç”¨æ›´æ–°)，就ä¸æœƒå—到這個æ¼æ´žæ‰€å½±éŸ¿ã€‚</p> @@ -1528,7 +1528,7 @@ QC-CR#831322</a></td> <h3 id="eop-in-qualcomm-networking-driver">Qualcomm 網路驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´ž</h3> -<p>Qualcomm 網路驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•æŒ‡ä»¤ã€‚ç”±æ–¼é€™ç¨®æ”»æ“Šå¿…é ˆå…ˆç ´è§£å…·æœ‰ç‰¹å®šæ¬Šé™çš„程åºæ‰èƒ½åŸ·è¡Œï¼Œå› æ¤é€™å€‹å•é¡Œçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚</p> +<p>Qualcomm 網路驅動程å¼ä¸çš„權é™å‡ç´šæ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨æ ¸å¿ƒç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚ç”±æ–¼é€™ç¨®æ”»æ“Šå¿…é ˆå…ˆç ´è§£å…·æœ‰ç‰¹å®šæ¬Šé™çš„程åºæ‰èƒ½åŸ·è¡Œï¼Œå› æ¤é€™å€‹å•é¡Œçš„åš´é‡ç¨‹åº¦è¢«è©•å®šç‚ºã€Œé«˜ã€ã€‚</p> <table> <colgroup><col width="19%" /> @@ -2404,7 +2404,7 @@ QC-CR#832915</a></td> <p>在 <a href="#2017-05-01-details">2017-05-01</a> å’Œ <a href="#2017-05-05-details">2017-05-05</a> 安全性æ¼æ´žè©³æƒ…çš„ç« ç¯€ä¸ï¼Œæ¯å€‹è¡¨æ ¼éƒ½åŒ…å«ã€Œæ›´æ–°çš„ Google è£ç½®ã€<em></em>欄，當ä¸åˆ—出已é‡å°å„個å•é¡Œé€²è¡Œæ›´æ–°çš„å—影響 Google è£ç½®ç¯„åœã€‚æ¤æ¬„ä¸çš„é¸é …包括：</p> <ul> <li><strong>所有 Google è£ç½®</strong>：如果å•é¡Œæœƒå½±éŸ¿åˆ° Pixel è£ç½®å’Œæ‰€æœ‰çš„ Google è£ç½®ï¼Œè¡¨æ ¼å…§ã€Œæ›´æ–°çš„ Google è£ç½®ã€<em></em>欄ä¸å°±æœƒæ¨™ç¤ºã€Œå…¨éƒ¨ã€å—樣。「全部ã€åŒ…å«ä¸‹åˆ—<a href="https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices">支æ´çš„è£ç½®</a>：Nexus 5Xã€Nexus 6ã€Nexus 6Pã€Nexus 9ã€Android Oneã€Nexus Playerã€Pixel Cã€Pixel å’Œ Pixel XL。</li> -<li><strong>部分 Google è£ç½®</strong>：如果å•é¡Œä¸¦æœªå½±éŸ¿åˆ°æ‰€æœ‰ Google è£ç½®ï¼Œå‰‡ã€Œæ›´æ–°çš„ Google è£ç½®ã€<em></em>欄ä¸æœƒåˆ—出å—影響的 Google è£ç½®ã€‚</li> +<li><strong>部分 Google è£ç½®</strong>：如果å•é¡Œä¸¦æœªå½±éŸ¿åˆ°æ‰€æœ‰ Google è£ç½®ï¼Œã€Œæ›´æ–°çš„ Google è£ç½®ã€<em></em>欄ä¸æœƒåˆ—出å—影響的 Google è£ç½®ã€‚</li> <li><strong>ä¸å½±éŸ¿ä»»ä½• Google è£ç½®</strong>：如果å•é¡Œä¸æœƒå½±éŸ¿åˆ°ä»»ä½•æ載 Android 7.0 çš„ Google è£ç½®ï¼Œè¡¨æ ¼å…§ã€Œæ›´æ–°çš„ Google è£ç½®ã€<em></em>欄ä¸å°±æœƒæ¨™ç¤ºã€Œç„¡ã€å—樣。</li> </ul> <p><strong>4. åƒè€ƒè³‡æ–™æ¬„底下列出的è˜åˆ¥ç¢¼ä»£è¡¨ä»€éº¼æ„義？</strong></p> diff --git a/zh-tw/security/bulletin/2017-11-01.html b/zh-tw/security/bulletin/2017-11-01.html index fbd1b550..16c50cc9 100644 --- a/zh-tw/security/bulletin/2017-11-01.html +++ b/zh-tw/security/bulletin/2017-11-01.html @@ -29,7 +29,8 @@ Android åˆä½œå¤¥ä¼´åœ¨ 2017-11-01 å’Œ 2017-11-05 修補程å¼å…¬å‘Šçš„至少一 <p> 在這些å•é¡Œä¸ï¼Œæœ€åš´é‡çš„就是媒體架構ä¸ã€Œæœ€é«˜ã€ç‰ç´šçš„安全性æ¼æ´žã€‚é 端攻擊者å¯åˆ©ç”¨é€™é¡žæ¼æ´žï¼Œåœ¨ç²å¾—授權的程åºç’°å¢ƒå…§é€éŽç‰¹è£½æª”案執行任何指令。<a href="/security/overview/updates-resources.html#severity">åš´é‡ç¨‹åº¦è©•å®šæ¨™æº–</a>是å‡è¨å¹³å°èˆ‡æœå‹™çš„å› æ‡‰é˜²è·æŽªæ–½åŸºæ–¼é–‹ç™¼ä½œæ¥çš„需求而被關閉，或是éåˆ°æœ‰å¿ƒäººå£«ç ´è§£ï¼Œç„¶å¾ŒæŽ¨ç®—ç•¶æœ‰äººæƒ¡æ„é‹ç”¨æ¼æ´žæ™‚，使用者的è£ç½®æœƒå—到多大的影響，據æ¤è©•å®šæ¼æ´žçš„åš´é‡ç¨‹åº¦ã€‚ </p> -<p>é‡å°é€™äº›æ–°ç™¼ç¾çš„æ¼æ´žï¼Œæˆ‘們目å‰å°šæœªæ”¶åˆ°ä»»ä½•å®¢æˆ¶å›žå ±ç›¸é—œçš„æ¼æ´žæ¿«ç”¨æ¡ˆä¾‹ã€‚如果想進一æ¥çžè§£ <a href="#mitigations">Android 安全性平å°é˜²è·æŽªæ–½</a>å’Œ Google Play 安全防è·æ©Ÿåˆ¶å¦‚ä½•åŠ å¼· Android å¹³å°çš„安全性，請åƒé–± <a href="/security/enhancements/index.html">Android å’Œ Google Play 安全防è·æ©Ÿåˆ¶æ‰€æä¾›çš„å› æ‡‰æŽªæ–½</a>。 +<p> +é‡å°é€™äº›æ–°ç™¼ç¾çš„æ¼æ´žï¼Œæˆ‘們目å‰å°šæœªæ”¶åˆ°ä»»ä½•å®¢æˆ¶å›žå ±ç›¸é—œçš„æ¼æ´žæ¿«ç”¨æ¡ˆä¾‹ã€‚如果想進一æ¥çžè§£ <a href="#mitigations">Android 安全性平å°é˜²è·æŽªæ–½</a>å’Œ Google Play 安全防è·æ©Ÿåˆ¶å¦‚ä½•åŠ å¼· Android å¹³å°çš„安全性，請åƒé–± <a href="/security/enhancements/index.html">Android å’Œ Google Play 安全防è·æ©Ÿåˆ¶æ‰€æä¾›çš„å› æ‡‰æŽªæ–½</a>。 </p> <p class="note"> <strong>注æ„：</strong><a href="/security/bulletin/pixel/2017-11-01">2017 å¹´ 11 月 Pixel / Nexus 安全性公告</a>æ供了和 Google è£ç½®çš„最新無線下載更新 (OTA) èˆ‡éŸŒé«”æ˜ åƒæª”有關的資訊。 @@ -49,7 +50,7 @@ Android åˆä½œå¤¥ä¼´åœ¨ 2017-11-01 å’Œ 2017-11-05 修補程å¼å…¬å‘Šçš„至少一 </ul> <h2 id="2017-11-01-details">2017-11-01 安全性修補程å¼ç‰ç´š - 資安æ¼æ´žè©³æƒ…</h2> <p> -下列å„節é‡å° 2017-11-01 安全性修補程å¼ç‰ç´šé©ç”¨çš„å„é …å®‰å…¨æ€§æ¼æ´žæ供了詳細資訊，並ä¾ç…§è³‡å®‰å•é¡Œæœ¬èº«æ‰€å½±éŸ¿çš„元件將å„é …æ¼æ´žåˆ†é–€åˆ¥é¡žï¼ŒåŒ…括å•é¡Œèªªæ˜Žä»¥åŠä¸€ä»½æ¼æ´žè³‡è¨Šè¡¨ï¼Œé¡¯ç¤ºæ¼æ´žçš„ CVEã€ç›¸é—œåƒè€ƒè³‡æ–™ã€<a href="#type">æ¼æ´žé¡žåž‹</a>ã€<a href="/security/overview/updates-resources.html#severity">åš´é‡ç¨‹åº¦</a>，以åŠæ›´æ–°çš„ Android 開放原始碼計劃版本 (在é©ç”¨æƒ…æ³ä¸‹)。å‡å¦‚相關錯誤有公開變更，該錯誤 ID 會連çµåˆ°ç›¸å°æ‡‰çš„變更 (例如 Android 開放原始碼計劃變更清單)ã€‚å¦‚æžœå–®ä¸€éŒ¯èª¤æœ‰å¤šé …ç›¸é—œè®Šæ›´ï¼Œæ‚¨å¯ä»¥é€éŽè©²éŒ¯èª¤ ID 後é¢çš„編號連çµé–‹å•Ÿé¡å¤–çš„åƒè€ƒè³‡æ–™ã€‚</p> +下列å„節é‡å° 2017-11-01 安全性修補程å¼ç‰ç´šé©ç”¨çš„å„é …å®‰å…¨æ€§æ¼æ´žæ供了詳細資訊，我們ä¾ç…§è³‡å®‰å•é¡Œæœ¬èº«æ‰€å½±éŸ¿çš„元件將å„é …æ¼æ´žåˆ†é–€åˆ¥é¡žï¼Œå¦å¤–也附上了å•é¡Œèªªæ˜Žå’Œä¸€ä»½ CVE 資訊表，其ä¸åŒ…括了相關åƒè€ƒè³‡æ–™ã€<a href="#type">æ¼æ´žé¡žåž‹</a>ã€<a href="/security/overview/updates-resources.html#severity">åš´é‡ç¨‹åº¦</a>，以åŠæ›´æ–°çš„ Android 開放原始碼計劃版本 (在é©ç”¨æƒ…æ³ä¸‹)。å‡å¦‚相關錯誤有公開變更，該錯誤 ID 會連çµåˆ°ç›¸å°æ‡‰çš„變更 (例如 Android 開放原始碼計劃變更清單)ã€‚å¦‚æžœå–®ä¸€éŒ¯èª¤æœ‰å¤šé …ç›¸é—œè®Šæ›´ï¼Œæ‚¨å¯ä»¥é€éŽè©²éŒ¯èª¤ ID 後é¢çš„編號連çµé–‹å•Ÿé¡å¤–çš„åƒè€ƒè³‡æ–™ã€‚</p> <h3 id="framework">架構</h3> <p>本節ä¸æœ€åš´é‡çš„æ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼è¦é¿ä½¿ç”¨è€…互動è¦æ±‚以å–得其他權é™ã€‚</p> @@ -84,7 +85,7 @@ Android åˆä½œå¤¥ä¼´åœ¨ 2017-11-01 å’Œ 2017-11-05 修補程å¼å…¬å‘Šçš„至少一 </tbody></table> <h3 id="media-framework">媒體架構</h3> -<p>本節ä¸æœ€åš´é‡çš„æ¼æ´žå¯èƒ½æœƒè®“é 端攻擊者得以利用特製檔案在ç²å¾—授權的程åºç’°å¢ƒå…§åŸ·è¡Œä»»ä½•æŒ‡ä»¤ã€‚</p> +<p>本節ä¸æœ€åš´é‡çš„æ¼æ´žå¯èƒ½æœƒè®“é 端攻擊者得以利用特製檔案在ç²å¾—授權的程åºç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚</p> <table> <colgroup><col width="17%" /> @@ -187,7 +188,7 @@ Android åˆä½œå¤¥ä¼´åœ¨ 2017-11-01 å’Œ 2017-11-05 修補程å¼å…¬å‘Šçš„至少一 下列å„節é‡å° 2017-11-05 安全性修補程å¼ç‰ç´šé©ç”¨çš„å„é …å®‰å…¨æ€§æ¼æ´žæ供了詳細資訊。我們ä¾ç…§è³‡å®‰å•é¡Œæœ¬èº«æ‰€å½±éŸ¿çš„元件將å„é …æ¼æ´žåˆ†é–€åˆ¥é¡žï¼Œå¦å¤–也附上了一些詳細資料，例如 CVEã€ç›¸é—œåƒè€ƒè³‡æ–™ã€<a href="#type">æ¼æ´žé¡žåž‹</a>ã€<a href="/security/overview/updates-resources.html#severity">åš´é‡ç¨‹åº¦</a>ã€å…ƒä»¶ (在é©ç”¨æƒ…æ³ä¸‹)，和更新的 Android 開放原始碼計劃版本 (在é©ç”¨æƒ…æ³ä¸‹)。å‡å¦‚相關錯誤有公開變更，該錯誤 ID 會連çµåˆ°ç›¸å°æ‡‰çš„變更 (例如 Android 開放原始碼計劃變更清單)ã€‚å¦‚æžœå–®ä¸€éŒ¯èª¤æœ‰å¤šé …ç›¸é—œè®Šæ›´ï¼Œæ‚¨å¯ä»¥é€éŽè©²éŒ¯èª¤ ID 後é¢çš„編號連çµé–‹å•Ÿé¡å¤–çš„åƒè€ƒè³‡æ–™ã€‚</p> <h3 id="kernel-components">æ ¸å¿ƒå…ƒä»¶</h3> -<p>本節ä¸æœ€åš´é‡çš„æ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨ç²å¾—授權的程åºç’°å¢ƒå…§åŸ·è¡Œä»»ä½•æŒ‡ä»¤ã€‚</p> +<p>本節ä¸æœ€åš´é‡çš„æ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨ç²å¾—授權的程åºç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚</p> <table> <colgroup><col width="17%" /> @@ -223,7 +224,7 @@ Android åˆä½œå¤¥ä¼´åœ¨ 2017-11-01 å’Œ 2017-11-05 修補程å¼å…¬å‘Šçš„至少一 </tbody></table> <h3 id="mediatek-components">MediaTek 元件</h3> -<p>本節ä¸æœ€åš´é‡çš„æ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨ç²å¾—授權的程åºç’°å¢ƒå…§åŸ·è¡Œä»»ä½•æŒ‡ä»¤ã€‚</p> +<p>本節ä¸æœ€åš´é‡çš„æ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨ç²å¾—授權的程åºç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚</p> <table> <colgroup><col width="17%" /> @@ -249,7 +250,7 @@ Android åˆä½œå¤¥ä¼´åœ¨ 2017-11-01 å’Œ 2017-11-05 修補程å¼å…¬å‘Šçš„至少一 </tbody></table> <h3 id="nvidia-components">NVIDIA 元件</h3> -<p>本節ä¸æœ€åš´é‡çš„æ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨ç²å¾—授權的程åºç’°å¢ƒå…§åŸ·è¡Œä»»ä½•æŒ‡ä»¤ã€‚</p> +<p>本節ä¸æœ€åš´é‡çš„æ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨ç²å¾—授權的程åºç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚</p> <table> <colgroup><col width="17%" /> @@ -275,7 +276,7 @@ Android åˆä½œå¤¥ä¼´åœ¨ 2017-11-01 å’Œ 2017-11-05 修補程å¼å…¬å‘Šçš„至少一 </tbody></table> <h3 id="qualcomm-components">Qualcomm 元件</h3> -<p>本節ä¸æœ€åš´é‡çš„æ¼æ´žå¯èƒ½æœƒè®“é 端攻擊者得以利用特製檔案在ç²å¾—授權的程åºç’°å¢ƒå…§åŸ·è¡Œä»»ä½•æŒ‡ä»¤ã€‚</p> +<p>本節ä¸æœ€åš´é‡çš„æ¼æ´žå¯èƒ½æœƒè®“é 端攻擊者得以利用特製檔案在ç²å¾—授權的程åºç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚</p> <table> <colgroup><col width="17%" /> @@ -454,7 +455,7 @@ QC-CR#2008683</a> è«‹åƒé–±<a href="//support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices">檢查åŠæ›´æ–° Android 版本</a>一文，çžè§£å¦‚何查看è£ç½®çš„安全性修補程å¼ç‰ç´šã€‚ </p> <ul> - <li>2017 å¹´ 11 月 1 日之後的安全性修補程å¼ç‰ç´šå·²è§£æ±ºäº†æ‰€æœ‰èˆ‡ 2017-11-01 安全性修補程å¼ç‰ç´šç›¸é—œçš„å•é¡Œã€‚</li> + <li>2017-11-01 之後的安全性修補程å¼ç‰ç´šå·²è§£æ±ºäº†æ‰€æœ‰èˆ‡ 2017-11-01 安全性修補程å¼ç‰ç´šç›¸é—œçš„å•é¡Œã€‚</li> <li>2017 å¹´ 11 月 5 日之後的安全性修補程å¼ç‰ç´šå®Œå…¨è§£æ±ºäº†èˆ‡ 2017-11-05 安全性修補程å¼ç‰ç´šåŠæ‰€æœ‰å…ˆå‰ä¿®è£œç¨‹å¼ç‰ç´šç›¸é—œçš„å•é¡Œã€‚</li> <li>2017 å¹´ 11 月 6 日之後的安全性修補程å¼ç‰ç´šå®Œå…¨è§£æ±ºäº†èˆ‡ 2017-11-06 安全性修補程å¼ç‰ç´šåŠæ‰€æœ‰å…ˆå‰ä¿®è£œç¨‹å¼ç‰ç´šç›¸é—œçš„å•é¡Œã€‚ </li> diff --git a/zh-tw/security/bulletin/2018-01-01.html b/zh-tw/security/bulletin/2018-01-01.html index 057ebdae..eae9c8a9 100644 --- a/zh-tw/security/bulletin/2018-01-01.html +++ b/zh-tw/security/bulletin/2018-01-01.html @@ -19,24 +19,30 @@ See the License for the specific language governing permissions and limitations under the License. --> -<p><em>發佈日期：2018 å¹´ 1 月 2 æ—¥</em></p> +<p><em>發佈日期：2018 å¹´ 1 月 2 æ—¥ | 更新日期：2018 å¹´ 1 月 29 æ—¥</em></p> <p> Android å®‰å…¨æ€§å…¬å‘Šç¾…åˆ—äº†æœƒå° Android è£ç½®é€ æˆå½±éŸ¿çš„安全性æ¼æ´žï¼Œä¸¦èªªæ˜Žå„é …ç›¸é—œç´°ç¯€ã€‚2018-01-05 之後的安全性修補程å¼ç‰ç´šå·²è§£æ±ºäº†é€™äº›å•é¡Œã€‚è«‹åƒé–±<a href="https://support.google.com/pixelphone/answer/4457705">檢查åŠæ›´æ–° Android 版本</a>一文，çžè§£å¦‚何查看è£ç½®çš„安全性修補程å¼ç‰ç´šã€‚ </p> <p> -Android çš„åˆä½œå¤¥ä¼´åœ¨è‡³å°‘一個月之å‰å·²æ”¶åˆ°å…¬å‘Šä¸æ‰€æœ‰å•é¡Œçš„相關通知。這些å•é¡Œçš„原始碼修補程å¼å°‡æ–¼æŽ¥ä¸‹ä¾† 48 å°æ™‚內發佈到 Android 開放原始碼計劃 (AOSP) å˜æ”¾å€ï¼Œç‰åˆ°ç›¸é—œ Android 開放原始碼計劃連çµå»ºç«‹å®Œæˆå¾Œï¼Œæˆ‘們就會修訂這則公告。 -</p> +Android çš„åˆä½œå¤¥ä¼´åœ¨è‡³å°‘一個月之å‰å·²æ”¶åˆ°å…¬å‘Šä¸æ‰€æœ‰å•é¡Œçš„相關通知。這些å•é¡Œçš„原始碼修補程å¼å·²ç™¼ä½ˆåˆ° Android 開放原始碼計劃 (AOSP) å˜æ”¾å€ä¸ï¼Œä¸”公告ä¸äº¦æ供相關連çµã€‚æ¤å¤–，本公告也æä¾› Android 開放原始碼計劃以外的修補程å¼é€£çµã€‚</p> <p> -在這些å•é¡Œä¸ï¼Œæœ€åš´é‡çš„就是媒體架構ä¸ã€Œæœ€é«˜ã€ç‰ç´šçš„安全性æ¼æ´žã€‚é 端攻擊者å¯åˆ©ç”¨é€™é¡žæ¼æ´žï¼Œåœ¨ç²å¾—授權的程åºç’°å¢ƒå…§é€éŽç‰¹è£½æª”案執行任何程å¼ç¢¼ã€‚<a href="/security/overview/updates-resources.html#severity">åš´é‡ç¨‹åº¦è©•å®šæ¨™æº–</a>是å‡è¨å¹³å°èˆ‡æœå‹™çš„å› æ‡‰é˜²è·æŽªæ–½åŸºæ–¼é–‹ç™¼ä½œæ¥çš„需求而被關閉，或是éåˆ°æœ‰å¿ƒäººå£«ç ´è§£ï¼Œç„¶å¾ŒæŽ¨ç®—ç•¶æœ‰äººæƒ¡æ„é‹ç”¨æ¼æ´žæ™‚，使用者的è£ç½®æœƒå—到多大的影響，據æ¤è©•å®šæ¼æ´žçš„åš´é‡ç¨‹åº¦ã€‚ +在這些å•é¡Œä¸ï¼Œæœ€åš´é‡çš„就是媒體架構ä¸ã€Œæœ€é«˜ã€ç‰ç´šçš„安全性æ¼æ´žã€‚é 端攻擊者å¯åˆ©ç”¨é€™é¡žæ¼æ´žï¼Œåœ¨ç²å¾—授權的程åºç’°å¢ƒå…§é€éŽç‰¹è£½æª”案執行任何指令。<a href="/security/overview/updates-resources.html#severity">åš´é‡ç¨‹åº¦è©•å®šæ¨™æº–</a>是å‡è¨å¹³å°èˆ‡æœå‹™çš„å› æ‡‰é˜²è·æŽªæ–½åŸºæ–¼é–‹ç™¼ä½œæ¥çš„需求而被關閉，或是éåˆ°æœ‰å¿ƒäººå£«ç ´è§£ï¼Œç„¶å¾ŒæŽ¨ç®—ç•¶æœ‰äººæƒ¡æ„é‹ç”¨æ¼æ´žæ™‚，使用者的è£ç½®æœƒå—到多大的影響，據æ¤è©•å®šæ¼æ´žçš„åš´é‡ç¨‹åº¦ã€‚ </p> -<p> -é‡å°é€™äº›æ–°ç™¼ç¾çš„æ¼æ´žï¼Œæˆ‘們目å‰å°šæœªæ”¶åˆ°ä»»ä½•å®¢æˆ¶å›žå ±ç›¸é—œçš„æ¼æ´žæ¿«ç”¨æ¡ˆä¾‹ã€‚如果想進一æ¥çžè§£ <a href="/security/enhancements/index.html">Android 安全性平å°é˜²è·æŽªæ–½</a>å’Œ Google Play 安全防è·æ©Ÿåˆ¶å¦‚ä½•åŠ å¼· Android å¹³å°çš„安全性，請åƒé–± <a href="#mitigations">Android å’Œ Google Play 安全防è·æ©Ÿåˆ¶æ‰€æä¾›çš„å› æ‡‰æŽªæ–½</a>。 +<p>é‡å°é€™äº›æ–°ç™¼ç¾çš„æ¼æ´žï¼Œæˆ‘們目å‰å°šæœªæ”¶åˆ°ä»»ä½•å®¢æˆ¶å›žå ±ç›¸é—œçš„æ¼æ´žæ¿«ç”¨æ¡ˆä¾‹ã€‚如果想進一æ¥çžè§£ <a href="#mitigations">Android 安全性平å°é˜²è·æŽªæ–½</a>å’Œ Google Play 安全防è·æ©Ÿåˆ¶å¦‚ä½•åŠ å¼· Android å¹³å°çš„安全性，請åƒé–± <a href="/security/enhancements/index.html">Android å’Œ Google Play 安全防è·æ©Ÿåˆ¶æ‰€æä¾›çš„å› æ‡‰æŽªæ–½</a>。 </p> <p> <strong>注æ„：</strong>2018 å¹´ 1 月 Pixel/Nexus 安全性公告æ供了和 Google è£ç½®çš„最新無線下載更新 (OTA) èˆ‡éŸŒé«”æ˜ åƒæª”有關的資訊。 </p> <h2 id="announcements">å…¬å‘Šäº‹é …</h2> +<aside class="note"> +<p><strong>注æ„：</strong>CVE-2017-5715ã€CVE-2017-5753 å’Œ CVE-2017-5754 這一組與處ç†å™¨ä¸æŽ¨æ¸¬æ€§åŸ·è¡Œç›¸é—œçš„安全性æ¼æ´žå·²å…¬é–‹æ露。Android 並ä¸æ¸…楚目å‰æ˜¯å¦æœ‰äººæˆåŠŸåˆ©ç”¨é€™äº›æ¼æ´žï¼Œé€ æˆä»»ä½•æŽ¡ç”¨ ARM 架構的 Android è£ç½®ç™¼ç”Ÿæœªç¶“授權的資訊外洩情æ³ã€‚ +</p> +<p> +為æä¾›é¡å¤–的安全防è·ï¼Œæˆ‘們已經在這個公告ä¸åŠ å…¥ CVE-2017-13218 的更新，以é™åˆ¶å˜å–高精度計時器，藉æ¤é™ä½Žæ‰€æœ‰å·²çŸ¥ ARM 處ç†å™¨ç³»åˆ—å—到æ—路攻擊 (例如 CVE-2017-5715ã€CVE-2017-5753 å’Œ CVE-2017-5754) 的機率。 +</p> +<p>æˆ‘å€‘å»ºè° Android 使用者接å—å¯ç”¨çš„è£ç½®å®‰å…¨æ€§æ›´æ–°ã€‚詳情請åƒé–± <a href="https://security.googleblog.com/2018/01/todays-cpu-vulnerability-what-you-need.html">Google 安全性網誌</a>。</p> +</aside> <p> 我們新推出了 <a href="/security/bulletin/pixel/">Pixel/Nexus 安全性公告</a>，其ä¸ç¾…列了其他已解決的安全性æ¼æ´žèˆ‡ç›¸é—œè©³æƒ…，以åŠå„é …åŠŸèƒ½æ”¹å–„é …ç›® (é©ç”¨æ–¼ Pixel å’Œ Nexus è£ç½®)。Android è£ç½®è£½é€ 商å¯è—‰æ¤è™•ç†è‡ªå®¶è£ç½®çš„相關å•é¡Œã€‚如需查詢其他相關資訊，請åƒé–±<a href="#common-questions-and-answers">常見å•é¡Œèˆ‡è§£ç”</a>。 </p> @@ -48,7 +54,7 @@ Android çš„åˆä½œå¤¥ä¼´åœ¨è‡³å°‘一個月之å‰å·²æ”¶åˆ°å…¬å‘Šä¸æ‰€æœ‰å•é¡Œçš„ </li><li>Android 安全性å°çµ„é€éŽ <a href="https://www.android.com/play-protect">Google Play 安全防è·</a>主動監控濫用情形；使用這些功能的目的是在發ç¾<a href="/security/reports/Google_Android_Security_PHA_classifications.pdf">å¯èƒ½æœ‰å®³çš„應用程å¼</a>時è¦å‘Šä½¿ç”¨è€…。在é è¨æƒ…æ³ä¸‹ï¼Œæ載 <a href="http://www.android.com/gms">Google 行動æœå‹™</a>çš„è£ç½®æœƒè‡ªå‹•å•Ÿç”¨ Google Play 安全防è·æ©Ÿåˆ¶ã€‚å°æ–¼éœ€è¦å¾ž Google Play 以外的來æºå®‰è£æ‡‰ç”¨ç¨‹å¼çš„ä½¿ç”¨è€…ä¾†èªªï¼Œé€™é …é˜²è·æŽªæ–½æ ¼å¤–é‡è¦ã€‚</li></ul> <h2 id="2018-01-01-security-patch-level—vulnerability-details">2018-01-01 安全性修補程å¼ç‰ç´š - 資安æ¼æ´žè©³æƒ…</h2> <p> -下列å„節é‡å° 2018-01-01 安全性修補程å¼ç‰ç´šé©ç”¨çš„å„é …å®‰å…¨æ€§æ¼æ´žæ供了詳細資訊。我們ä¾ç…§è³‡å®‰å•é¡Œæœ¬èº«æ‰€å½±éŸ¿çš„元件將å„é …æ¼æ´žåˆ†é–€åˆ¥é¡žï¼Œå¦å¤–也附上了å•é¡Œèªªæ˜Žå’Œä¸€ä»½ CVE 資訊表，其ä¸åŒ…括了相關åƒè€ƒè³‡æ–™ã€<a href="#type">æ¼æ´žé¡žåž‹</a>ã€<a href="/security/overview/updates-resources.html#severity">åš´é‡ç¨‹åº¦</a>，以åŠæ›´æ–°çš„ Android 開放原始碼計劃版本 (在é©ç”¨æƒ…æ³ä¸‹)。å‡å¦‚相關錯誤有公開變更，該錯誤 ID 會連çµåˆ°ç›¸å°æ‡‰çš„變更 (例如 AOSP 變更清單)ã€‚å¦‚æžœå–®ä¸€éŒ¯èª¤æœ‰å¤šé …ç›¸é—œè®Šæ›´ï¼Œæ‚¨å¯ä»¥é€éŽè©²éŒ¯èª¤ ID 後é¢çš„編號連çµé–‹å•Ÿé¡å¤–çš„åƒè€ƒè³‡æ–™ã€‚</p> +下列å„節é‡å° 2018-01-01 安全性修補程å¼ç‰ç´šé©ç”¨çš„å„é …å®‰å…¨æ€§æ¼æ´žæ供了詳細資訊。我們ä¾ç…§è³‡å®‰å•é¡Œæœ¬èº«æ‰€å½±éŸ¿çš„元件將å„é …æ¼æ´žåˆ†é–€åˆ¥é¡žï¼Œå¦å¤–也附上了å•é¡Œèªªæ˜Žå’Œä¸€ä»½ CVE 資訊表，其ä¸åŒ…括了相關åƒè€ƒè³‡æ–™ã€<a href="#type">æ¼æ´žé¡žåž‹</a>ã€<a href="/security/overview/updates-resources.html#severity">åš´é‡ç¨‹åº¦</a>，以åŠæ›´æ–°çš„ Android 開放原始碼計劃版本 (在é©ç”¨æƒ…æ³ä¸‹)。å‡å¦‚相關錯誤有公開變更，該錯誤 ID 會連çµåˆ°ç›¸å°æ‡‰çš„變更 (例如 Android 開放原始碼計劃變更清單)ã€‚å¦‚æžœå–®ä¸€éŒ¯èª¤æœ‰å¤šé …ç›¸é—œè®Šæ›´ï¼Œæ‚¨å¯ä»¥é€éŽè©²éŒ¯èª¤ ID 後é¢çš„編號連çµé–‹å•Ÿé¡å¤–çš„åƒè€ƒè³‡æ–™ã€‚</p> <h3 id="android-runtime">Android 執行階段</h3> <p>本節ä¸æœ€åš´é‡çš„æ¼æ´žå¯èƒ½æœƒè®“é 端攻擊者è¦é¿ä½¿ç”¨è€…互動è¦æ±‚以å–得其他權é™ã€‚</p> @@ -68,7 +74,8 @@ Android çš„åˆä½œå¤¥ä¼´åœ¨è‡³å°‘一個月之å‰å·²æ”¶åˆ°å…¬å‘Šä¸æ‰€æœ‰å•é¡Œçš„ </tr> <tr> <td>CVE-2017-13176</td> - <td>A-68341964</td> + <td><a href="https://android.googlesource.com/platform/frameworks/base/+/4afa0352d6c1046f9e9b67fbf0011bcd751fcbb5"> + A-68341964</a></td> <td>EoP</td> <td>高</td> <td>5.1.1ã€6.0ã€6.0.1ã€7.0ã€7.1.1ã€7.1.2ã€8.0ã€8.1</td> @@ -92,109 +99,124 @@ Android çš„åˆä½œå¤¥ä¼´åœ¨è‡³å°‘一個月之å‰å·²æ”¶åˆ°å…¬å‘Šä¸æ‰€æœ‰å•é¡Œçš„ <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> </tr> <tr> - <td>CVE-2017-13177</td> - <td>A-68320413</td> - <td>RCE</td> - <td>最高</td> - <td>5.1.1ã€6.0ã€6.0.1ã€7.0ã€7.1.1ã€7.1.2ã€8.0ã€8.1</td> + <td>CVE-2017-13177</td> + <td><a href="https://android.googlesource.com/platform/external/libhevc/+/b686bb2df155fd1f55220d56f38cc0033afe278c"> + A-68320413</a></td> + <td>RCE</td> + <td>最高</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-13178</td> - <td>A-66969281</td> - <td>RCE</td> - <td>最高</td> - <td>6.0.1ã€7.0ã€7.1.1ã€7.1.2ã€8.0ã€8.1</td> + <td>CVE-2017-13178</td> + <td><a href="https://android.googlesource.com/platform/frameworks/av/+/646a18fef28d19ba5beb6a2e1c00ac4c2663a10b"> + A-66969281</a></td> + <td>RCE</td> + <td>最高</td> + <td>6.0.1ã€7.0ã€7.1.1ã€7.1.2ã€8.0ã€8.1</td> </tr> <tr> - <td>CVE-2017-13179</td> - <td>A-66969193</td> - <td>RCE</td> - <td>最高</td> - <td>6.0.1ã€7.0ã€7.1.1ã€7.1.2ã€8.0ã€8.1</td> + <td>CVE-2017-13179</td> + <td><a href="https://android.googlesource.com/platform/frameworks/av/+/47d4b33b504e14e98420943f771a9aecd6d09516"> + A-66969193</a></td> + <td>RCE</td> + <td>最高</td> + <td>6.0.1ã€7.0ã€7.1.1ã€7.1.2ã€8.0ã€8.1</td> </tr> <tr> - <td>CVE-2017-13180</td> - <td>A-66969349</td> - <td>EoP</td> - <td>高</td> - <td>6.0ã€6.0.1ã€7.0ã€7.1.1ã€7.1.2ã€8.0ã€8.1</td> + <td>CVE-2017-13180</td> + <td><a href="https://android.googlesource.com/platform/frameworks/av/+/cf1e36f93fc8776e3a8109149424babeee7f8382"> + A-66969349</a></td> + <td>EoP</td> + <td>高</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-13181</td> - <td>A-67864232</td> - <td>EoP</td> - <td>高</td> - <td>7.0ã€7.1.1ã€7.1.2ã€8.0ã€8.1</td> + <td>CVE-2017-13181</td> + <td><a href="https://android.googlesource.com/platform/frameworks/base/+/d64e9594d3d73c613010ca9fafc7af9782e9225d"> + A-67864232</a></td> + <td>EoP</td> + <td>高</td> + <td>7.0ã€7.1.1ã€7.1.2ã€8.0ã€8.1</td> </tr> <tr> - <td>CVE-2017-13182</td> - <td>A-67737022</td> - <td>EoP</td> - <td>高</td> - <td>8.0ã€8.1</td> + <td>CVE-2017-13182</td> + <td><a href="https://android.googlesource.com/platform/frameworks/av/+/f1652e1b9f1d2840c79b6bf784d1befe40f4799e"> + A-67737022</a></td> + <td>EoP</td> + <td>高</td> + <td>8.0ã€8.1</td> </tr> <tr> - <td>CVE-2017-13184</td> - <td>A-65483324</td> - <td>EoP</td> - <td>高</td> - <td>8.0ã€8.1</td> + <td>CVE-2017-13184</td> + <td><a href="https://android.googlesource.com/platform/frameworks/native/+/16392a119661fd1da750d4d4e8e03442578bc543"> + A-65483324</a></td> + <td>EoP</td> + <td>高</td> + <td>8.0ã€8.1</td> </tr> <tr> - <td>CVE-2017-0855</td> - <td>A-64452857</td> - <td>DoS</td> - <td>高</td> - <td>5.1.1ã€6.0ã€6.0.1ã€7.0ã€7.1.1ã€7.1.2ã€8.0</td> + <td>CVE-2017-0855</td> + <td><a href="https://android.googlesource.com/platform/frameworks/av/+/d7d6df849cec9d0a9c1fd0d9957a1b8edef361b7"> + A-64452857</a></td> + <td>DoS</td> + <td>高</td> + <td>5.1.1ã€6.0ã€6.0.1ã€7.0ã€7.1.1ã€7.1.2ã€8.0</td> </tr> <tr> - <td>CVE-2017-13191</td> - <td>A-64380403</td> - <td>DoS</td> - <td>高</td> - <td>5.1.1ã€6.0ã€6.0.1ã€7.0ã€7.1.1ã€7.1.2ã€8.0ã€8.1</td> + <td>CVE-2017-13191</td> + <td><a href="https://android.googlesource.com/platform/external/libhevc/+/f5b2fa243b4c45a4cd885e85f49ae548ab88c264"> + A-64380403</a></td> + <td>DoS</td> + <td>高</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-13192</td> - <td>A-64380202</td> - <td>DoS</td> - <td>高</td> - <td>5.1.1ã€6.0ã€6.0.1ã€7.0ã€7.1.1ã€7.1.2ã€8.0ã€8.1</td> + <td>CVE-2017-13192</td> + <td><a href="https://android.googlesource.com/platform/external/libhevc/+/52ca619511acbd542d843df1f92f858ce13048a5"> + A-64380202</a></td> + <td>DoS</td> + <td>高</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-13193</td> - <td>A-65718319</td> - <td>DoS</td> - <td>高</td> - <td>5.1.1ã€6.0ã€6.0.1ã€7.0ã€7.1.1ã€7.1.2ã€8.0ã€8.1</td> + <td>CVE-2017-13193</td> + <td><a href="https://android.googlesource.com/platform/external/libhevc/+/b3f31e493ef6fa886989198da9787807635eaae2"> + A-65718319</a></td> + <td>DoS</td> + <td>高</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-13195</td> - <td>A-65398821</td> - <td>DoS</td> - <td>高</td> - <td>5.1.1ã€6.0ã€6.0.1ã€7.0ã€7.1.1ã€7.1.2ã€8.0ã€8.1</td> + <td>CVE-2017-13195</td> + <td><a href="https://android.googlesource.com/platform/external/libhevc/+/066e3b1f9c954d95045bc9d33d2cdc9df419784f"> + A-65398821</a></td> + <td>DoS</td> + <td>高</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-13196</td> - <td>A-63522067</td> - <td>DoS</td> - <td>高</td> - <td>5.1.1ã€6.0ã€6.0.1ã€7.0ã€7.1.1ã€7.1.2ã€8.0ã€8.1</td> + <td>CVE-2017-13196</td> + <td><a href="https://android.googlesource.com/platform/external/libhevc/+/f5b2fa243b4c45a4cd885e85f49ae548ab88c264"> + A-63522067</a></td> + <td>DoS</td> + <td>高</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-13197</td> - <td>A-64784973</td> - <td>DoS</td> - <td>高</td> - <td>6.0ã€6.0.1ã€7.0ã€7.1.1ã€7.1.2ã€8.0ã€8.1</td> + <td>CVE-2017-13197</td> + <td><a href="https://android.googlesource.com/platform/external/libhevc/+/0a714d3a14d256c6a5675d6fbd975ca26e9bc471"> + A-64784973</a></td> + <td>DoS</td> + <td>高</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-13199</td> - <td>A-33846679</td> - <td>DoS</td> - <td>高</td> - <td>8.0ã€8.1</td> + <td>CVE-2017-13199</td> + <td><a href="https://android.googlesource.com/platform/frameworks/base/+/42b2e419b48a26d2ba599d87e3a2a02c4aa625f4"> + A-33846679</a></td> + <td>DoS</td> + <td>高</td> + <td>8.0ã€8.1</td> </tr> </tbody></table> @@ -215,37 +237,43 @@ Android çš„åˆä½œå¤¥ä¼´åœ¨è‡³å°‘一個月之å‰å·²æ”¶åˆ°å…¬å‘Šä¸æ‰€æœ‰å•é¡Œçš„ <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> </tr> <tr> - <td>CVE-2017-13208</td> - <td>A-67474440</td> - <td>RCE</td> - <td>最高</td> - <td>5.1.1ã€6.0ã€6.0.1ã€7.0ã€7.1.1ã€7.1.2ã€8.0ã€8.1</td> + <td>CVE-2017-13208</td> + <td><a href="https://android.googlesource.com/platform/system/core/+/b71335264a7c3629f80b7bf1f87375c75c42d868"> + A-67474440</a></td> + <td>RCE</td> + <td>最高</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-13209</td> - <td>A-68217907</td> - <td>EoP</td> - <td>高</td> - <td>8.0ã€8.1</td> + <td>CVE-2017-13209</td> + <td><a href="https://android.googlesource.com/platform/system/libhidl/+/a4d0252ab5b6f6cc52a221538e1536c5b55c1fa7"> + A-68217907</a> +[<a href="https://android.googlesource.com/platform/system/tools/hidl/+/8539fc8ac94d5c92ef9df33675844ab294f68d61">2</a>] +[<a href="https://android.googlesource.com/platform/system/hwservicemanager/+/e1b4a889e8b84f5c13b76333d4de90dbe102a0de">3</a>]</td> + <td>EoP</td> + <td>高</td> + <td>8.0ã€8.1</td> </tr> <tr> - <td>CVE-2017-13210</td> - <td>A-67782345</td> - <td>EoP</td> - <td>高</td> - <td>5.1.1ã€6.0ã€6.0.1ã€7.0ã€7.1.1ã€7.1.2ã€8.0ã€8.1</td> + <td>CVE-2017-13210</td> + <td><a href="https://android.googlesource.com/platform/system/media/+/e770e378dc8e2320679272234285456ca2244a62"> + A-67782345</a></td> + <td>EoP</td> + <td>高</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-13211</td> - <td>A-65174158</td> - <td>DoS</td> - <td>高</td> - <td>8.0</td> + <td>CVE-2017-13211</td> + <td><a href="https://android.googlesource.com/platform/system/bt/+/181144a50114c824cfe3cdfd695c11a074673a5e"> + A-65174158</a></td> + <td>DoS</td> + <td>高</td> + <td>8.0</td> </tr> </tbody></table> <h2 id="2018-01-05-security-patch-level—vulnerability-details">2018-01-05 安全性修補程å¼ç‰ç´š - 資安æ¼æ´žè©³æƒ…</h2> -<p>下列å„節é‡å° 2018-01-05 安全性修補程å¼ç‰ç´šé©ç”¨çš„å„é …å®‰å…¨æ€§æ¼æ´žæ供了詳細資訊。我們ä¾ç…§è³‡å®‰å•é¡Œæœ¬èº«æ‰€å½±éŸ¿çš„元件將å„é …æ¼æ´žåˆ†é–€åˆ¥é¡žï¼Œå¦å¤–也附上了一些詳細資料，例如 CVEã€ç›¸é—œåƒè€ƒè³‡æ–™ã€<a href="#type">æ¼æ´žé¡žåž‹</a>ã€<a href="/security/overview/updates-resources.html#severity">åš´é‡ç¨‹åº¦</a>ã€å…ƒä»¶ (在é©ç”¨æƒ…æ³ä¸‹)，和更新的 Android 開放原始碼計劃版本 (在é©ç”¨æƒ…æ³ä¸‹)。å‡å¦‚相關錯誤有公開變更，該錯誤 ID 會連çµåˆ°ç›¸å°æ‡‰çš„變更 (例如 AOSP 變更清單)ã€‚å¦‚æžœå–®ä¸€éŒ¯èª¤æœ‰å¤šé …ç›¸é—œè®Šæ›´ï¼Œæ‚¨å¯ä»¥é€éŽè©²éŒ¯èª¤ ID 後é¢çš„編號連çµé–‹å•Ÿé¡å¤–çš„åƒè€ƒè³‡æ–™ã€‚</p> +<p>下列å„節é‡å° 2018-01-05 安全性修補程å¼ç‰ç´šé©ç”¨çš„å„é …å®‰å…¨æ€§æ¼æ´žæ供了詳細資訊。我們ä¾ç…§è³‡å®‰å•é¡Œæœ¬èº«æ‰€å½±éŸ¿çš„元件將å„é …æ¼æ´žåˆ†é–€åˆ¥é¡žï¼Œå¦å¤–也附上了一些詳細資料，例如 CVEã€ç›¸é—œåƒè€ƒè³‡æ–™ã€<a href="#type">æ¼æ´žé¡žåž‹</a>ã€<a href="/security/overview/updates-resources.html#severity">åš´é‡ç¨‹åº¦</a>ã€å…ƒä»¶ (在é©ç”¨æƒ…æ³ä¸‹)，和更新的 Android 開放原始碼計劃版本 (在é©ç”¨æƒ…æ³ä¸‹)。å‡å¦‚相關錯誤有公開變更，該錯誤 ID 會連çµåˆ°ç›¸å°æ‡‰çš„變更 (例如 Android 開放原始碼計劃變更清單)ã€‚å¦‚æžœå–®ä¸€éŒ¯èª¤æœ‰å¤šé …ç›¸é—œè®Šæ›´ï¼Œæ‚¨å¯ä»¥é€éŽè©²éŒ¯èª¤ ID 後é¢çš„編號連çµé–‹å•Ÿé¡å¤–çš„åƒè€ƒè³‡æ–™ã€‚</p> <h3 id="htc-components">HTC 元件</h3> <p>本節ä¸æœ€åš´é‡çš„æ¼æ´žå¯èƒ½æœƒè®“é‡è¦çš„系統程åºåœ¨é到é 端攻擊時拒絕æœå‹™ã€‚</p> @@ -273,7 +301,7 @@ Android çš„åˆä½œå¤¥ä¼´åœ¨è‡³å°‘一個月之å‰å·²æ”¶åˆ°å…¬å‘Šä¸æ‰€æœ‰å•é¡Œçš„ </tbody></table> <h3 id="kernel-components">æ ¸å¿ƒå…ƒä»¶</h3> -<p>本節ä¸æœ€åš´é‡çš„æ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨ç²å¾—授權的程åºç’°å¢ƒå…§åŸ·è¡Œä»»ä½•æŒ‡ä»¤ã€‚</p> +<p>本節ä¸æœ€åš´é‡çš„æ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨ç²å¾—授權的程åºç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚</p> <table> <colgroup><col width="17%" /> @@ -318,7 +346,7 @@ Android çš„åˆä½œå¤¥ä¼´åœ¨è‡³å°‘一個月之å‰å·²æ”¶åˆ°å…¬å‘Šä¸æ‰€æœ‰å•é¡Œçš„ <td>A-68266545<a href="#asterisk">*</a></td> <td>ID</td> <td>高</td> - <td>計時器</td> + <td>高精度計時器</td> </tr> </tbody></table> @@ -372,34 +400,8 @@ Android çš„åˆä½œå¤¥ä¼´åœ¨è‡³å°‘一個月之å‰å·²æ”¶åˆ°å…¬å‘Šä¸æ‰€æœ‰å•é¡Œçš„ </tr> </tbody></table> -<h3 id="mediatek-components">MediaTek 元件</h3> -<p>本節ä¸æœ€åš´é‡çš„æ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨ç²å¾—授權的程åºç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚</p> - -<table> - <colgroup><col width="17%" /> - <col width="19%" /> - <col width="9%" /> - <col width="14%" /> - <col width="39%" /> - </colgroup><tbody><tr> - <th>CVE</th> - <th>åƒè€ƒè³‡æ–™</th> - <th>é¡žåž‹</th> - <th>åš´é‡ç¨‹åº¦</th> - <th>元件</th> - </tr> - <tr> - <td>CVE-2017-13225</td> - <td>A-38308024<a href="#asterisk">*</a><br /> - M-ALPS03495789</td> - <td>EoP</td> - <td>高</td> - <td>MTK 媒體</td> - </tr> -</tbody></table> - <h3 id="nvidia-components">NVIDIA 元件</h3> -<p>本節ä¸æœ€åš´é‡çš„æ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨ç²å¾—授權的程åºç’°å¢ƒå…§åŸ·è¡Œä»»ä½•æŒ‡ä»¤ã€‚</p> +<p>本節ä¸æœ€åš´é‡çš„æ¼æ´žå¯èƒ½æœƒè®“本機惡æ„應用程å¼åœ¨ç²å¾—授權的程åºç’°å¢ƒå…§åŸ·è¡Œä»»ä½•ç¨‹å¼ç¢¼ã€‚</p> <table> <colgroup><col width="17%" /> @@ -563,7 +565,7 @@ QC-CR#2060780</a></td> 我們建è°åˆä½œå¤¥ä¼´å°‡æ‰€æœ‰å•é¡Œé©ç”¨çš„修補程å¼éƒ½å½™æ•´åœ¨å–®ä¸€æ›´æ–°ä¸ã€‚ </p> <p id="type"> -<strong>3. 「類型ã€<em></em>欄ä¸çš„é …ç›®ä»£è¡¨ä»€éº¼æ„義？</strong> +<strong>3.「類型ã€<em></em>欄ä¸çš„é …ç›®ä»£è¡¨ä»€éº¼æ„義？</strong> </p> <p> 資安æ¼æ´žè©³æƒ…è¡¨æ ¼ä¸ã€Œé¡žåž‹ã€<em></em>欄ä¸çš„é …ç›®ä»£è¡¨çš„æ˜¯å®‰å…¨æ€§æ¼æ´žçš„類別。 @@ -597,7 +599,7 @@ QC-CR#2060780</a></td> </tr> </tbody></table> <p> -<strong>4. 「åƒè€ƒè³‡æ–™ã€<em></em>欄底下列出的è˜åˆ¥ç¢¼ä»£è¡¨ä»€éº¼æ„義？</strong> +<strong>4.「åƒè€ƒè³‡æ–™ã€<em></em>欄底下列出的è˜åˆ¥ç¢¼ä»£è¡¨ä»€éº¼æ„義？</strong> </p> <p> 資安æ¼æ´žè©³æƒ…è¡¨æ ¼ä¸ã€Œåƒè€ƒè³‡æ–™ã€<em></em>æ¬„åº•ä¸‹çš„é …ç›®å¯èƒ½æœƒåŒ…å«ä¸€å€‹å‰ç½®å—串，用以表示該åƒè€ƒè³‡æ–™å€¼æ‰€å±¬çš„機構或公å¸ã€‚ @@ -639,14 +641,13 @@ QC-CR#2060780</a></td> <p> <strong>6. 為什麼安全性æ¼æ´žæœƒåˆ†åˆ¥åˆŠè¼‰åœ¨é€™ä»½å®‰å…¨æ€§å…¬å‘Šå’Œè£ç½®/åˆä½œå¤¥ä¼´å®‰å…¨æ€§å…¬å‘Š (例如 Pixel/Nexus 公告)？</strong> </p> -<p> -為了宣告 Android è£ç½®æœ€æ–°çš„安全性修補程å¼ç‰ç´šï¼Œæˆ‘å€‘å¿…é ˆå…ˆåœ¨é€™ä»½å®‰å…¨æ€§å…¬å‘Šä¸åˆŠè¼‰ç›¸é—œçš„安全性æ¼æ´žã€‚è£ç½®/åˆä½œå¤¥ä¼´å®‰å…¨æ€§å…¬å‘Šæ‰€åˆŠè¼‰çš„其他安全性æ¼æ´žä¸¦æœªå¼·åˆ¶è¦å®šå®£å‘Šå®‰å…¨æ€§ä¿®è£œç¨‹å¼ç‰ç´šã€‚我們鼓勵 Android è£ç½®å’Œæ™¶ç‰‡è£½é€ 商é€éŽè‡ªå·±çš„網站刊載修æ£æ–¹æ³•ï¼Œä¾‹å¦‚ <a href="https://security.samsungmobile.com/securityUpdate.smsb">Samsung</a>ã€<a href="https://lgsecurity.lge.com/security_updates.html">LGE</a> 或是 <a href="/security/bulletin/pixel/">Pixel/Nexus</a> 安全性公告。 +<p>為了宣告 Android è£ç½®æœ€æ–°çš„安全性修補程å¼ç‰ç´šï¼Œæˆ‘å€‘å¿…é ˆå…ˆåœ¨é€™ä»½å®‰å…¨æ€§å…¬å‘Šä¸åˆŠè¼‰ç›¸é—œçš„安全性æ¼æ´žã€‚è£ç½®/åˆä½œå¤¥ä¼´å®‰å…¨æ€§å…¬å‘Šæ‰€åˆŠè¼‰çš„其他安全性æ¼æ´žä¸¦æœªå¼·åˆ¶è¦å®šå®£å‘Šå®‰å…¨æ€§ä¿®è£œç¨‹å¼ç‰ç´šã€‚我們鼓勵 Android è£ç½®å’Œæ™¶ç‰‡è£½é€ 商é€éŽè‡ªå·±çš„網站刊載修æ£æ–¹æ³•ï¼Œä¾‹å¦‚ <a href="https://security.samsungmobile.com/securityUpdate.smsb">Samsung</a>ã€<a href="https://lgsecurity.lge.com/security_updates.html">LGE</a> 或是 <a href="/security/bulletin/pixel/">Pixel/Nexus</a> 安全性公告。 </p> <h2 id="versions">版本</h2> <table> - <colgroup><col width="25%" /> + <colgroup><col width="15%" /> <col width="25%" /> - <col width="50%" /> + <col width="60%" /> </colgroup><tbody><tr> <th>版本</th> <th>日期</th> @@ -657,6 +658,20 @@ QC-CR#2060780</a></td> <td>2018 å¹´ 1 月 2 æ—¥</td> <td>發佈公告。</td> </tr> -</tbody></table> + <tr> + <td>1.1</td> + <td>2018 å¹´ 1 月 3 æ—¥</td> + <td>更新公告內容 (åŠ å…¥ CVE-2017-13218 çš„å…¬å‘Šäº‹é …)。</td> + </tr> + <tr> + <td>1.2</td> + <td>2018 å¹´ 1 月 5 æ—¥</td> + <td>修訂公告內容 (åŠ å…¥ Android 開放原始碼計劃連çµ)。</td> + </tr> + <tr> + <td>1.3</td> + <td>2018 å¹´ 1 月 29 æ—¥</td> + <td>å°‡ CVE-2017-13225 移至 <a href="/security/bulletin/pixel/">Pixel / Nexus 安全性公告</a>。</td> +</tr></tbody></table> </body></html>
\ No newline at end of file diff --git a/zh-tw/security/bulletin/pixel/2017-10-01.html b/zh-tw/security/bulletin/pixel/2017-10-01.html index 8db531ae..76dc6f78 100644 --- a/zh-tw/security/bulletin/pixel/2017-10-01.html +++ b/zh-tw/security/bulletin/pixel/2017-10-01.html @@ -21,7 +21,7 @@ --> <p><em>發佈日期：2017 å¹´ 10 月 2 æ—¥ | 更新日期：2017 å¹´ 10 月 3 æ—¥</em></p> -<p>Pixel/Nexus 安全性公告羅列了會å°<a href="https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices">支æ´çš„ Google Pixel å’Œ Nexus è£ç½®</a> (Google è£ç½®) é€ æˆå½±éŸ¿çš„安全性æ¼æ´žå’ŒåŠŸèƒ½æ”¹å–„é …ç›®ï¼Œä¸¦èªªæ˜Žå„é …ç›¸é—œç´°ç¯€ã€‚é‡å° Google è£ç½®ï¼Œ2017 å¹´ 10 月 5 日之後的安全性修補程å¼ç‰ç´šå·²è§£æ±ºäº†æœ¬å®‰å…¨æ€§å…¬å‘Šå’Œ <a href="/security/bulletin/2017-10-01">2017 å¹´ 10 月 Android 安全性公告</a>ä¸çš„所有å•é¡Œã€‚想çžè§£å¦‚何查看è£ç½®çš„安全性修補程å¼ç‰ç´šï¼Œè«‹åƒé–±<a href="https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices">檢查和更新 Android 版本</a>。</p> +<p>Pixel/Nexus 安全性公告羅列了會å°<a href="https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices">支æ´çš„ Google Pixel å’Œ Nexus è£ç½®</a> (Google è£ç½®) é€ æˆå½±éŸ¿çš„安全性æ¼æ´žå’ŒåŠŸèƒ½æ”¹å–„é …ç›®ï¼Œä¸¦èªªæ˜Žå„é …ç›¸é—œç´°ç¯€ã€‚é‡å° Google è£ç½®ï¼Œ2017 å¹´ 10 月 5 日之後的安全性修補程å¼ç‰ç´šå·²è§£æ±ºäº†æœ¬å®‰å…¨æ€§å…¬å‘Šå’Œ <a href="/security/bulletin/2017-10-01">2017 å¹´ 10 月 Android 安全性公告</a>ä¸çš„所有å•é¡Œã€‚è«‹åƒé–±<a href="https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices">檢查åŠæ›´æ–° Android 版本</a>一文，çžè§£å¦‚何查看è£ç½®çš„安全性修補程å¼ç‰ç´šã€‚</p> <p>所有支æ´çš„ Google è£ç½®éƒ½æœƒæ”¶åˆ° 2017-10-05 修補ç‰ç´šæ›´æ–°ã€‚我們建è°æ‰€æœ‰å®¢æˆ¶æŽ¥å—這些è£ç½®æ›´æ–°ã€‚</p> @@ -82,7 +82,7 @@ <th>åƒè€ƒè³‡æ–™</th> <th>é¡žåž‹</th> <th>åš´é‡ç¨‹åº¦</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> </tr> <tr> <td>CVE-2017-0813</td> @@ -161,14 +161,14 @@ <th>åƒè€ƒè³‡æ–™</th> <th>é¡žåž‹</th> <th>åš´é‡ç¨‹åº¦</th> - <th>æ›´æ–°çš„ AOSP 版本</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> </tr> <tr> <td>CVE-2017-0822</td> <td><a href="https://android.googlesource.com/platform/frameworks/base/+/c574568aaede7f652432deb7707f20ae54bbdf9a">A-63787722</a></td> <td>EoP</td> <td>ä¸</td> - <td>6.0.1, 7.0, 7.1.1, 7.1.2, 8.0</td> + <td>6.0.1ã€7.0ã€7.1.1ã€7.1.2ã€8.0</td> </tr> <tr> <td>CVE-2017-0823</td> @@ -232,7 +232,7 @@ <td>A-34949781<a href="#asterisk">*</a></td> <td>EoP</td> <td>ä¸</td> - <td>系統啟動載入程å¼</td> + <td>開機載入器</td> </tr> </tbody></table> @@ -306,7 +306,7 @@ <td>A-62345044<a href="#asterisk">*</a></td> <td>EoP</td> <td>ä¸</td> - <td>系統啟動載入程å¼</td> + <td>開機載入器</td> </tr> </tbody></table> @@ -523,10 +523,10 @@ QC-CR#2016076</a></td> <p><strong>1. 如何判斷我目å‰çš„è£ç½®è»Ÿé«”版本是å¦å·²ä¿®æ£é€™äº›å•é¡Œï¼Ÿ </strong></p> -<p>2017 å¹´ 10 月 5 日之後的安全修補ç‰ç´šå®Œå…¨è§£æ±ºäº†èˆ‡ 2017-10-05 安全修補ç‰ç´šåŠæ‰€æœ‰å…ˆå‰ä¿®è£œç‰ç´šç›¸é—œçš„å•é¡Œã€‚想çžè§£å¦‚何查看è£ç½®çš„安全性修補程å¼ç‰ç´šï¼Œè«‹è©³è®€ <a href="https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices">Pixel å’Œ Nexus 更新時間表</a>ä¸çš„æ“作說明。</p> +<p>2017-10-05 之後的安全修補ç‰ç´šå®Œå…¨è§£æ±ºäº†èˆ‡ 2017-10-05 安全性修補程å¼ç‰ç´šåŠæ‰€æœ‰å…ˆå‰ä¿®è£œç‰ç´šç›¸é—œçš„å•é¡Œã€‚è«‹åƒé–± <a href="https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices">Pixel 與 Nexus 更新時間表</a>ä¸çš„æ“作說明，çžè§£å¦‚何查看è£ç½®çš„安全性修補程å¼ç‰ç´šã€‚</p> <p id="type"> -<strong>2.「類型ã€<em></em>欄底下列出的è˜åˆ¥ç¢¼ä»£è¡¨ä»€éº¼æ„義？</strong></p> +<strong>2.「類型ã€<em></em>欄ä¸çš„é …ç›®ä»£è¡¨ä»€éº¼æ„義？</strong></p> <p>資安æ¼æ´žè©³æƒ…è¡¨æ ¼ä¸ã€Œé¡žåž‹ã€<em></em>欄ä¸çš„é …ç›®ä»£è¡¨çš„æ˜¯å®‰å…¨æ€§æ¼æ´žçš„類別。</p> @@ -558,7 +558,7 @@ QC-CR#2016076</a></td> <td>未分類</td> </tr> </tbody></table> -<p><strong>3.「åƒè€ƒè³‡æ–™ã€<em></em>欄ä¸çš„é …ç›®ä»£è¡¨ä»€éº¼æ„義？</strong></p> +<p><strong>3.「åƒè€ƒè³‡æ–™ã€<em></em>欄底下列出的è˜åˆ¥ç¢¼ä»£è¡¨ä»€éº¼æ„義？</strong></p> <p>資安æ¼æ´žè©³æƒ…è¡¨æ ¼ä¸ã€Œåƒè€ƒè³‡æ–™ã€<em></em>æ¬„åº•ä¸‹çš„é …ç›®å¯èƒ½æœƒåŒ…å«ä¸€å€‹å‰ç½®å—串，用以表示該åƒè€ƒè³‡æ–™å€¼æ‰€å±¬çš„機構或公å¸ã€‚</p> @@ -598,7 +598,8 @@ QC-CR#2016076</a></td> <p id="split"> <strong>5. 為什麼安全性æ¼æ´žæœƒå€åˆ†ç‚ºæœ¬å®‰å…¨æ€§å…¬å‘Šå’Œ Android 安全性公告？</strong> </p> -<p>刊載在 Android 安全性公告的安全性æ¼æ´žæœ‰å…¶è¦å®šä½œæ¥ï¼Œä»¥ä¾¿é‡å° Android è£ç½®å®£å‘Šæœ€æ–°çš„安全性修補程å¼ç‰ç´šã€‚其他安全性æ¼æ´ž (例如本安全性公告所刊載的安全性æ¼æ´ž) 並未強制è¦å®šå®£å‘Šå®‰å…¨æ€§ä¿®è£œç¨‹å¼ç‰ç´šã€‚ +<p> +為了宣告 Android è£ç½®æœ€æ–°çš„安全性修補程å¼ç‰ç´šï¼Œæˆ‘å€‘å¿…é ˆå…ˆåœ¨ Android 安全性公告ä¸åˆŠè¼‰ç›¸é—œçš„安全性æ¼æ´žã€‚其他安全性æ¼æ´ž (例如本安全性公告所刊載的安全性æ¼æ´ž) 並未強制è¦å®šå®£å‘Šå®‰å…¨æ€§ä¿®è£œç¨‹å¼ç‰ç´šã€‚ </p> <h2 id="versions">版本</h2> diff --git a/zh-tw/security/bulletin/pixel/2018-03-01.html b/zh-tw/security/bulletin/pixel/2018-03-01.html new file mode 100644 index 00000000..c50efcf1 --- /dev/null +++ b/zh-tw/security/bulletin/pixel/2018-03-01.html @@ -0,0 +1,651 @@ +<html devsite><head> + <title>Pixel / Nexus 安全性公告 - 2018 å¹´ 3 月</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>發佈日期：2018 å¹´ 3 月 5 æ—¥</em></p> + +<p> +Pixel/Nexus 安全性公告羅列了會å°<a href="https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices">支æ´çš„ Google Pixel å’Œ Nexus è£ç½®</a> (Google è£ç½®) é€ æˆå½±éŸ¿çš„安全性æ¼æ´žå’ŒåŠŸèƒ½æ”¹å–„é …ç›®ï¼Œä¸¦èªªæ˜Žå„é …ç›¸é—œç´°ç¯€ã€‚2018-03-05 之後的安全性修補程å¼ç‰ç´šä¹Ÿå·²é‡å° Google è£ç½®è§£æ±ºäº†é€™å€‹å…¬å‘Šå’Œ <a href="/security/bulletin/2018-03-01">2018 å¹´ 3 月 Android 安全性公告</a>列出的所有å•é¡Œã€‚è«‹åƒé–±<a href="https://support.google.com/pixelphone/answer/4457705">檢查åŠæ›´æ–° Android 版本</a>一文，çžè§£å¦‚何查看è£ç½®çš„安全性修補程å¼ç‰ç´šã€‚</p> +<p> +所有支æ´çš„ Google è£ç½®éƒ½æœƒæ”¶åˆ° 2018-03-05 修補程å¼ç‰ç´šæ›´æ–°ã€‚我們建è°æ‰€æœ‰å®¢æˆ¶æŽ¥å—這些è£ç½®æ›´æ–°ã€‚ +</p> +<p class="note"> +<strong>注æ„：</strong>您å¯ä»¥å‰å¾€ <a href="https://developers.google.com/android/nexus/images">Google Developers 網站</a>å–å¾— Google è£ç½®éŸŒé«”æ˜ åƒæª”。 +</p> + +<h2 id="announcements">å…¬å‘Šäº‹é …</h2> +<p>我們除了修補 <a href="/security/bulletin/2018-03-01">2018 å¹´ 3 月 Android 安全性公告</a>ä¸æ‰€åˆ—出的安全性æ¼æ´žï¼Œä¹Ÿé‡å°ä¸‹æ–‡åˆ—出的 Google è£ç½®çš„安全性æ¼æ´žæ供修補程å¼ã€‚我們的åˆä½œå¤¥ä¼´åœ¨è‡³å°‘一個月之å‰å·²æ”¶åˆ°æ‰€è¿°å•é¡Œçš„相關通知，方便他們將相關內容ç´å…¥å…¶è£ç½®æ›´æ–°ä¸ã€‚</p> + +<h2 id="security-patches">安全性修補程å¼</h2> +<p> +我們ä¾ç…§è³‡å®‰å•é¡Œæœ¬èº«æ‰€å½±éŸ¿çš„元件將å„é …æ¼æ´žåˆ†é–€åˆ¥é¡žï¼Œå¦å¤–也附上了å•é¡Œèªªæ˜Žå’Œä¸€ä»½ CVE 資訊表，其ä¸åŒ…括了相關åƒè€ƒè³‡æ–™ã€<a href="#type">æ¼æ´žé¡žåž‹</a>ã€<a href="https://source.android.com/security/overview/updates-resources.html#severity">åš´é‡ç¨‹åº¦</a>，以åŠæ›´æ–°çš„ Android 開放原始碼計劃 (AOSP) 版本 (在é©ç”¨æƒ…æ³ä¸‹)。å‡å¦‚相關錯誤有公開變更，該錯誤 ID 會連çµåˆ°ç›¸å°æ‡‰çš„變更 (例如 Android 開放原始碼計劃變更清單)ã€‚å¦‚æžœå–®ä¸€éŒ¯èª¤æœ‰å¤šé …ç›¸é—œè®Šæ›´ï¼Œæ‚¨å¯ä»¥é€éŽè©²éŒ¯èª¤ ID 後é¢çš„編號連çµé–‹å•Ÿé¡å¤–çš„åƒè€ƒè³‡æ–™ã€‚</p> + +<h3 id="framework">架構</h3> + +<table> + <colgroup><col width="17%" /> + <col width="19%" /> + <col width="9%" /> + <col width="14%" /> + <col width="39%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>åƒè€ƒè³‡æ–™</th> + <th>é¡žåž‹</th> + <th>åš´é‡ç¨‹åº¦</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> + </tr> + <tr> + <td>CVE-2017-13263</td> + <td>A-69383160</td> + <td>EoP</td> + <td>ä¸</td> + <td>8.0ã€8.1</td> + </tr> +</tbody></table> + +<h3 id="media-framework">媒體架構</h3> + +<table> + <colgroup><col width="17%" /> + <col width="19%" /> + <col width="9%" /> + <col width="14%" /> + <col width="39%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>åƒè€ƒè³‡æ–™</th> + <th>é¡žåž‹</th> + <th>åš´é‡ç¨‹åº¦</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> + </tr> + <tr> + <td rowspan="2">CVE-2017-13264</td> + <td rowspan="2">A-70294343</td> + <td>NSI</td> + <td>NSI</td> + <td>7.0ã€7.1.1ã€7.1.2ã€8.0ã€8.1</td> + </tr> + <tr> + <td>DoS</td> + <td>高</td> + <td>6.0ã€6.0.1</td> + </tr> + <tr> + <td rowspan="2">CVE-2017-13254</td> + <td rowspan="2">A-70239507</td> + <td>NSI</td> + <td>NSI</td> + <td>7.0ã€7.1.1ã€7.1.2ã€8.0ã€8.1</td> + </tr> + <tr> + <td>DoS</td> + <td>高</td> + <td>5.1.1ã€6.0ã€6.0.1</td> + </tr> +</tbody></table> + +<h3 id="system">系統</h3> + +<table> + <colgroup><col width="17%" /> + <col width="19%" /> + <col width="9%" /> + <col width="14%" /> + <col width="39%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>åƒè€ƒè³‡æ–™</th> + <th>é¡žåž‹</th> + <th>åš´é‡ç¨‹åº¦</th> + <th>æ›´æ–°çš„ Android 開放原始碼計劃版本</th> + </tr> + <tr> + <td>CVE-2017-13265</td> + <td>A-36232423</td> + <td>EoP</td> + <td>ä¸</td> + <td>7.0ã€7.1.1ã€7.1.2ã€8.0ã€8.1</td> + </tr> + <tr> + <td>CVE-2017-13266</td> + <td>A-69478941</td> + <td>EoP</td> + <td>ä¸</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-13268</td> + <td>A-67058064</td> + <td>ID</td> + <td>ä¸</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-13269</td> + <td>A-68818034</td> + <td>ID</td> + <td>ä¸</td> + <td>5.1.1ã€6.0ã€6.0.1ã€7.0ã€7.1.1ã€7.1.2ã€8.0ã€8.1</td> + </tr> +</tbody></table> + +<h3 id="kernel-components">æ ¸å¿ƒå…ƒä»¶</h3> + +<table> + <colgroup><col width="17%" /> + <col width="19%" /> + <col width="9%" /> + <col width="14%" /> + <col width="39%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>åƒè€ƒè³‡æ–™</th> + <th>é¡žåž‹</th> + <th>åš´é‡ç¨‹åº¦</th> + <th>元件</th> + </tr> + <tr> + <td>CVE-2017-5754</td> + <td>A-69856074<a href="#asterisk">*</a></td> + <td>ID</td> + <td>高</td> + <td>記憶體å°æ‡‰æª”案</td> + </tr> + <tr> + <td>CVE-2017-13270</td> + <td>A-69474744<a href="#asterisk">*</a></td> + <td>EoP</td> + <td>ä¸</td> + <td>Mnh_sm 驅動程å¼</td> + </tr> + <tr> + <td>CVE-2017-13271</td> + <td>A-69006799<a href="#asterisk">*</a></td> + <td>EoP</td> + <td>ä¸</td> + <td>Mnh_sm 驅動程å¼</td> + </tr> + <tr> + <td>CVE-2017-16527</td> + <td>A-69051382<br /> +<a href="https://github.com/torvalds/linux/commit/124751d5e63c823092060074bd0abaae61aaa9c4"> +上游程å¼åº«æ ¸å¿ƒ</a></td> + <td>EoP</td> + <td>ä¸</td> + <td>USB 音效驅動程å¼</td> + </tr> + <tr> + <td>CVE-2017-15649</td> + <td>A-69160446<br /> +<a href="http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=008ba2a13f2d04c947adc536d19debb8fe66f110"> +上游程å¼åº«æ ¸å¿ƒ</a> +[<a href="http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4971613c1639d8e5f102c4e797c3bf8f83a5a69e">2</a>]</td> + <td>EoP</td> + <td>ä¸</td> + <td>網路驅動程å¼</td> + </tr> + <tr> + <td>CVE-2017-1000111</td> + <td>A-68806121<br /> +<a href="http://patchwork.ozlabs.org/patch/800274/">上游程å¼åº«æ ¸å¿ƒ</a></td> + <td>EoP</td> + <td>ä¸</td> + <td>網路驅動程å¼</td> + </tr> +</tbody></table> + +<h3 id="nvidia-components">NVIDIA 元件</h3> + +<table> + <colgroup><col width="17%" /> + <col width="19%" /> + <col width="9%" /> + <col width="14%" /> + <col width="39%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>åƒè€ƒè³‡æ–™</th> + <th>é¡žåž‹</th> + <th>åš´é‡ç¨‹åº¦</th> + <th>元件</th> + </tr> + <tr> + <td>CVE-2017-6287</td> + <td>A-64893264<a href="#asterisk">*</a><br /> + N-CVE-2017-6287</td> + <td>ID</td> + <td>ä¸</td> + <td>媒體架構</td> + </tr> + <tr> + <td>CVE-2017-6285</td> + <td>A-64893156<a href="#asterisk">*</a><br /> + N-CVE-2017-6285</td> + <td>ID</td> + <td>ä¸</td> + <td>媒體架構</td> + </tr> + <tr> + <td>CVE-2017-6288</td> + <td>A-65482562<a href="#asterisk">*</a><br /> + N-CVE-2017-6288</td> + <td>ID</td> + <td>ä¸</td> + <td>媒體架構</td> + </tr> +</tbody></table> + +<h3 id="qualcomm-components">Qualcomm 元件</h3> + +<table> + <colgroup><col width="17%" /> + <col width="19%" /> + <col width="9%" /> + <col width="14%" /> + <col width="39%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>åƒè€ƒè³‡æ–™</th> + <th>é¡žåž‹</th> + <th>åš´é‡ç¨‹åº¦</th> + <th>元件</th> + </tr> + <tr> + <td>CVE-2017-18061</td> + <td>A-70237701<br /> +<a href="https://source.codeaurora.org/quic/la/kernel/msm-3.18/commit/?id=b65cf2a007e88fe86dbd6d3269682fc585a4130f"> +QC-CR#2117246</a></td> + <td>EoP</td> + <td>ä¸</td> + <td>Wil6210</td> + </tr> + <tr> + <td>CVE-2017-18050</td> + <td>A-70237697<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=63b57442d65dfdb4b4634ff32059b1bca8c72fb7"> +QC-CR#2119443</a></td> + <td>EoP</td> + <td>ä¸</td> + <td>Wma 管ç†</td> + </tr> + <tr> + <td>CVE-2017-18054</td> + <td>A-70237694<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=6eefc756612e39fab49ff719b3dc9b94def53396"> +QC-CR#2119432</a></td> + <td>EoP</td> + <td>ä¸</td> + <td>Wma</td> + </tr> + <tr> + <td>CVE-2017-18055</td> + <td>A-70237693<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=50a0554d12cff58b3ffbd51d3194304244b87023"> +QC-CR#2119430</a></td> + <td>EoP</td> + <td>ä¸</td> + <td>Wma</td> + </tr> + <tr> + <td>CVE-2017-18065</td> + <td>A-70237685<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=a8bc0f90ef49ea0aee90047a17772e4eebff259a"> +QC-CR#2113423</a></td> + <td>EoP</td> + <td>ä¸</td> + <td>Wma</td> + </tr> + <tr> + <td>CVE-2017-18066</td> + <td>A-70235107<br /> +<a href="https://source.codeaurora.org/quic/la/kernel/msm-3.18/commit/?id=ff11f44c0c10c94170f03a8698f73f7e08b74625"> +QC-CR#2107976</a></td> + <td>EoP</td> + <td>ä¸</td> + <td>é›»æºé©…動程å¼</td> + </tr> + <tr> + <td>CVE-2017-18062</td> + <td>A-68992451<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=d7927eb7c9c2d79a3e24cddd1e9447ab98bf6700"> +QC-CR#2115375</a></td> + <td>EoP</td> + <td>ä¸</td> + <td>Wma</td> + </tr> + <tr> + <td>CVE-2018-3561</td> + <td>A-68870904<a href="#asterisk">*</a><br /> + QC-CR#2068569</td> + <td>EoP</td> + <td>ä¸</td> + <td>Diagchar</td> + </tr> + <tr> + <td>CVE-2018-3560</td> + <td>A-68664502<a href="#asterisk">*</a><br /> + QC-CR#2142216</td> + <td>EoP</td> + <td>ä¸</td> + <td>Qdsp6v2 音效驅動程å¼</td> + </tr> + <tr> + <td>CVE-2017-15834</td> + <td>A-70237704<br /> +<a href="https://source.codeaurora.org/quic/la/kernel/msm-3.18/commit/?id=2e1b54e38f1516e70d9f6581c4f1ee935effb903"> +QC-CR#2111858</a></td> + <td>EoP</td> + <td>ä¸</td> + <td>Diagchar</td> + </tr> + <tr> + <td>CVE-2017-15833</td> + <td>A-70237702<br /> +<a href="https://source.codeaurora.org/quic/la/kernel/msm-3.10/commit/?id=51ce6aec73d80e1f1fcc9c7fa71e9c2fcbdbc0fd"> +QC-CR#2059835</a></td> + <td>EoP</td> + <td>ä¸</td> + <td>é›»æºé©…動程å¼</td> + </tr> + <tr> + <td>CVE-2017-15831</td> + <td>A-70237687<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=31e6a657320e4299c659e3d57d38a89afe8c1ce1"> +QC-CR#2114255</a></td> + <td>EoP</td> + <td>ä¸</td> + <td>Wma</td> + </tr> + <tr> + <td>CVE-2017-15830</td> + <td>A-70237719<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=8a7a2a9c5d203e3395811963061c79d3bc257ebe"> +QC-CR#2120725</a></td> + <td>EoP</td> + <td>ä¸</td> + <td>sme 驅動程å¼</td> + </tr> + <tr> + <td>CVE-2017-14889</td> + <td>A-70237700<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=e11e9dc8298dc0632050cacce96e9652d017f755"> +QC-CR#2119803</a></td> + <td>EoP</td> + <td>ä¸</td> + <td>Wma</td> + </tr> + <tr> + <td>CVE-2017-14887</td> + <td>A-70237715<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=4ce28e7c85f89e2c3555ec840b6adda47bd5dab0"> +QC-CR#2119673</a></td> + <td>EoP</td> + <td>ä¸</td> + <td>WLAN</td> + </tr> + <tr> + <td>CVE-2017-14879</td> + <td>A-63851638<a href="#asterisk">*</a><br /> + QC-CR#2056307</td> + <td>EoP</td> + <td>ä¸</td> + <td>IPA</td> + </tr> + <tr> + <td>CVE-2017-11082</td> + <td>A-66937387<br /> +<a href="https://www.codeaurora.org/gitweb/quic/la/?p=kernel/msm-3.10.git;a=commit;h=2d4f8cd8d11f8fb1491a20d7e316cc0fd03eeb59"> +QC-CR#2071560</a></td> + <td>EoP</td> + <td>ä¸</td> + <td>WLAN</td> + </tr> + <tr> + <td>CVE-2017-11074</td> + <td>A-68940798<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/prima/commit/?id=f5ae7b35c90f14b7e66b3a91d4fb247563a8a22b"> +QC-CR#2049138</a></td> + <td>EoP</td> + <td>ä¸</td> + <td>WLAN</td> + </tr> + <tr> + <td>CVE-2017-18052</td> + <td>A-70237712<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=c04c4870bd86a5f878553d7acf207388f3d6c3bd"> +QC-CR#2119439</a></td> + <td>ID</td> + <td>ä¸</td> + <td>WLAN</td> + </tr> + <tr> + <td>CVE-2017-18057</td> + <td>A-70237709<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=24d41d2bd3d98325b3800345f4ba27a334b3894b"> +QC-CR#2119403</a></td> + <td>ID</td> + <td>ä¸</td> + <td>WLAN</td> + </tr> + <tr> + <td>CVE-2017-18059</td> + <td>A-70237708<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=217705da7726002ffe61dad51a6c9cc97c52f649"> +QC-CR#2119399</a></td> + <td>ID</td> + <td>ä¸</td> + <td>WLAN</td> + </tr> + <tr> + <td>CVE-2017-18060</td> + <td>A-70237707<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=f3d81bd0b3cb992c214d94196b33168b02589c6b"> +QC-CR#2119394</a></td> + <td>ID</td> + <td>ä¸</td> + <td>WLAN</td> + </tr> + <tr> + <td>CVE-2017-18051</td> + <td>A-70237696<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=38fba6a9f6ca3c7bf0c4c1bd84fa2b89fbcaeb93"> +QC-CR#2119442</a></td> + <td>ID</td> + <td>ä¸</td> + <td>WLAN</td> + </tr> + <tr> + <td>CVE-2017-18053</td> + <td>A-70237695<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=da1c6e996ac7635c202296e31118f088f9427947"> +QC-CR#2119434</a></td> + <td>ID</td> + <td>ä¸</td> + <td>WLAN</td> + </tr> + <tr> + <td>CVE-2017-18058</td> + <td>A-70237690<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=d6d42a10d4abf09299cdfacdd8aed5c26731b5ff"> +QC-CR#2119401</a></td> + <td>ID</td> + <td>ä¸</td> + <td>WLAN</td> + </tr> + <tr> + <td>CVE-2017-15855</td> + <td>A-38232131<a href="#asterisk">*</a><br /> + QC-CR#2139514</td> + <td>ID</td> + <td>ä¸</td> + <td>Camera_v2 驅動程å¼</td> + </tr> + <tr> + <td>CVE-2017-15814</td> + <td>A-64836865<a href="#asterisk">*</a><br /> + QC-CR#2092793</td> + <td>ID</td> + <td>ä¸</td> + <td>Camera_v2 驅動程å¼</td> + </tr> +</tbody></table> + +<h2 id="functional-updates">功能更新</h2> +<p> +這些更新的目的在於解決å—影響 Pixel è£ç½®çš„功能å•é¡Œï¼Œèˆ‡ Pixel è£ç½®çš„安全性無關。下表列出相關åƒè€ƒè³‡æ–™ã€å—影響的類別 (例如è—牙或行動數據)，以åŠå•é¡Œæ‘˜è¦ã€‚ +</p> + +<table> + <tbody><tr> + <th>åƒè€ƒè³‡æ–™</th> + <th>類別</th> + <th>æ”¹å–„é …ç›®</th> + <th>è£ç½®</th> + </tr> + <tr> + <td>A-70491468</td> + <td>效能</td> + <td>改善指紋解鎖的螢幕喚醒效能</td> + <td>Pixel 2ã€Pixel 2 XL</td> + </tr> + <tr> + <td>A-69307875</td> + <td>音訊</td> + <td>改善錄製影片時的音訊效能</td> + <td>Pixel 2 XL</td> + </tr> + <tr> + <td>A-70641186</td> + <td>å›žå ±</td> + <td>æ”¹å–„ç•¶æ©Ÿå›žå ±åŠŸèƒ½</td> + <td>Pixel 2ã€Pixel 2 XL</td> + </tr> +</tbody></table> + +<h2 id="common-questions-and-answers">常見å•é¡Œèˆ‡è§£ç”</h2> +<p> +如果您在閱讀這篇公告後有任何疑å•ï¼Œå¯åƒè€ƒæœ¬ç¯€çš„常見å•ç”。 +</p> +<p> +<strong>1. 如何判斷我目å‰çš„è£ç½®è»Ÿé«”版本是å¦å·²ä¿®æ£é€™äº›å•é¡Œï¼Ÿ +</strong> +</p> +<p>2018-03-05 之後的安全性修補程å¼ç‰ç´šå®Œå…¨è§£æ±ºäº†èˆ‡ 2018-03-05 安全性修補程å¼ç‰ç´šåŠæ‰€æœ‰å…ˆå‰ä¿®è£œç¨‹å¼ç‰ç´šç›¸é—œçš„å•é¡Œã€‚è«‹åƒé–± <a href="https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices">Pixel 與 Nexus 更新時間表</a>ä¸çš„æ“作說明，çžè§£å¦‚何查看è£ç½®çš„安全性修補程å¼ç‰ç´šã€‚ +</p> +<p id="type"> +<strong>2.「類型ã€<em></em>欄ä¸çš„é …ç›®ä»£è¡¨ä»€éº¼æ„義？</strong> +</p> +<p> +資安æ¼æ´žè©³æƒ…è¡¨æ ¼ä¸ã€Œé¡žåž‹ã€<em></em>欄ä¸çš„é …ç›®ä»£è¡¨çš„æ˜¯å®‰å…¨æ€§æ¼æ´žçš„類別。 +</p> +<table> + <colgroup><col width="25%" /> + <col width="75%" /> + </colgroup><tbody><tr> + <th>縮寫詞</th> + <th>定義</th> + </tr> + <tr> + <td>RCE</td> + <td>é 端程å¼ç¢¼åŸ·è¡Œ</td> + </tr> + <tr> + <td>EoP</td> + <td>權é™å‡ç´š</td> + </tr> + <tr> + <td>ID</td> + <td>資訊外洩</td> + </tr> + <tr> + <td>DoS</td> + <td>拒絕æœå‹™</td> + </tr> + <tr> + <td>ç„¡</td> + <td>未分類</td> + </tr> +</tbody></table> +<p> +<strong>3.「åƒè€ƒè³‡æ–™ã€<em></em>欄底下列出的è˜åˆ¥ç¢¼ä»£è¡¨ä»€éº¼æ„義？</strong> +</p> +<p> +資安æ¼æ´žè©³æƒ…è¡¨æ ¼ä¸ã€Œåƒè€ƒè³‡æ–™ã€<em></em>æ¬„åº•ä¸‹çš„é …ç›®å¯èƒ½æœƒåŒ…å«ä¸€å€‹å‰ç½®å—串，用以表示該åƒè€ƒè³‡æ–™å€¼æ‰€å±¬çš„機構或公å¸ã€‚ +</p> +<table> + <colgroup><col width="25%" /> + <col width="75%" /> + </colgroup><tbody><tr> + <th>å‰ç½®å—串</th> + <th>åƒè€ƒè³‡æ–™</th> + </tr> + <tr> + <td>A-</td> + <td>Android 錯誤 ID</td> + </tr> + <tr> + <td>QC-</td> + <td>Qualcomm åƒè€ƒç·¨è™Ÿ</td> + </tr> + <tr> + <td>M-</td> + <td>MediaTek åƒè€ƒç·¨è™Ÿ</td> + </tr> + <tr> + <td>N-</td> + <td>NVIDIA åƒè€ƒç·¨è™Ÿ</td> + </tr> + <tr> + <td>B-</td> + <td>Broadcom åƒè€ƒç·¨è™Ÿ</td> + </tr> +</tbody></table> +<p id="asterisk"> +<strong>4.「åƒè€ƒè³‡æ–™ã€<em></em>æ¬„ä¸ Android 錯誤 ID æ—邊的星號 (*) 代表什麼æ„義？</strong> +</p> +<p> +在「åƒè€ƒè³‡æ–™ã€<em></em>æ¬„ä¸ Android 錯誤 ID æ—邊標上星號 (*) 代表該å•é¡Œä¸¦æœªå…¬é–‹ï¼Œç›¸é—œçš„更新通常是直接整åˆåœ¨æœ€æ–°çš„ Nexus è£ç½®å°ˆç”¨é©…動程å¼çš„安è£æª”ä¸ã€‚您å¯ä»¥å‰å¾€ <a href="https://developers.google.com/android/nexus/drivers">Google Developers 網站</a>下載這些驅動程å¼ã€‚ +</p> +<p> +<strong>5. 為什麼安全性æ¼æ´žæœƒåˆ†åˆ¥åˆŠè¼‰åœ¨é€™ä»½å®‰å…¨æ€§å…¬å‘Šå’Œ Android 安全性公告？</strong> +</p> +<p> +為了宣告 Android è£ç½®æœ€æ–°çš„安全性修補程å¼ç‰ç´šï¼Œæˆ‘å€‘å¿…é ˆå…ˆåœ¨ Android 安全性公告ä¸åˆŠè¼‰ç›¸é—œçš„安全性æ¼æ´žã€‚其他安全性æ¼æ´ž (例如本安全性公告所刊載的安全性æ¼æ´ž) 並未強制è¦å®šå®£å‘Šå®‰å…¨æ€§ä¿®è£œç¨‹å¼ç‰ç´šã€‚ +</p> +<h2 id="versions">版本</h2> +<table> + <colgroup><col width="25%" /> + <col width="25%" /> + <col width="50%" /> + </colgroup><tbody><tr> + <th>版本</th> + <th>日期</th> + <th>附註</th> + </tr> + <tr> + <td>1.0</td> + <td>2018 å¹´ 3 月 5 æ—¥</td> + <td>發佈公告。</td> + </tr> +</tbody></table> + +</body></html>
\ No newline at end of file diff --git a/zh-tw/security/bulletin/pixel/2018.html b/zh-tw/security/bulletin/pixel/2018.html index e3e462d8..bb8968d0 100644 --- a/zh-tw/security/bulletin/pixel/2018.html +++ b/zh-tw/security/bulletin/pixel/2018.html @@ -34,17 +34,43 @@ <th>安全性修補程å¼ç‰ç´š</th> </tr> <tr> - <td><a href="/security/bulletin/pixel/2018-01-01.html">2018 å¹´ 1 月</a></td> + <td><a href="/security/bulletin/pixel/2018-03-01.html">2018 å¹´ 3 月</a></td> <td>å³å°‡æŽ¨å‡º <!-- - <a href="/security/bulletin/pixel/2018-01-01.html">English</a> / - <a href="/security/bulletin/pixel/2018-01-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/pixel/2018-01-01.html?hl=ko">í•œêµì–´</a> / - <a href="/security/bulletin/pixel/2018-01-01.html?hl=ru">руÌÑÑкий</a> / - <a href="/security/bulletin/pixel/2018-01-01.html?hl=zh-cn">ä¸æ–‡ (ä¸å›½)</a> / - <a href="/security/bulletin/pixel/2018-01-01.html?hl=zh-tw">ä¸æ–‡ (å°ç£)</a> + <a href="/security/bulletin/pixel/2018-03-01.html">English</a> / + <a href="/security/bulletin/pixel/2018-03-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/pixel/2018-03-01.html?hl=ko">í•œêµì–´</a> / + <a href="/security/bulletin/pixel/2018-03-01.html?hl=ru">руÌÑÑкий</a> / + <a href="/security/bulletin/pixel/2018-03-01.html?hl=zh-cn">ä¸æ–‡ (ä¸å›½)</a> / + <a href="/security/bulletin/pixel/2018-03-01.html?hl=zh-tw">ä¸æ–‡ (å°ç£)</a> --> </td> + <td>2018 å¹´ 3 月</td> + <td>2018-03-05</td> + </tr> + <tr> + <td><a href="/security/bulletin/pixel/2018-02-01.html">2018 å¹´ 2 月</a></td> + <td> + <a href="/security/bulletin/pixel/2018-02-01.html">English</a> / + <a href="/security/bulletin/pixel/2018-02-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/pixel/2018-02-01.html?hl=ko">í•œêµì–´</a> / + <a href="/security/bulletin/pixel/2018-02-01.html?hl=ru">руÌÑÑкий</a> / + <a href="/security/bulletin/pixel/2018-02-01.html?hl=zh-cn">ä¸æ–‡Â (ä¸å›½)</a> / + <a href="/security/bulletin/pixel/2018-02-01.html?hl=zh-tw">ä¸æ–‡Â (å°ç£)</a> + </td> + <td>2018 å¹´ 2 月</td> + <td>2018-02-05</td> + </tr> + <tr> + <td><a href="/security/bulletin/pixel/2018-01-01.html">2018 å¹´ 1 月</a></td> + <td> + <a href="/security/bulletin/pixel/2018-01-01.html">English</a> / + <a href="/security/bulletin/pixel/2018-01-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/pixel/2018-01-01.html?hl=ko">í•œêµì–´</a> / + <a href="/security/bulletin/pixel/2018-01-01.html?hl=ru">руÌÑÑкий</a> / + <a href="/security/bulletin/pixel/2018-01-01.html?hl=zh-cn">ä¸æ–‡Â (ä¸å›½)</a> / + <a href="/security/bulletin/pixel/2018-01-01.html?hl=zh-tw">ä¸æ–‡Â (å°ç£)</a> + </td> <td>2018 å¹´ 1 月</td> <td>2018-01-05</td> </tr> |
