ID VU:584653 Type cert Reporter CERT Modified 2018-07-03T21:27:00
Description
Overview
CPU hardware implementations are vulnerable to cache side-channel attacks. These vulnerabilities are referred to as Meltdown and Spectre.
Description
CPU hardware implementations are vulnerable to side-channel attacks referred to as Meltdown and Spectre. Both Spectre and Meltdown take advantage of the ability to extract information from instructions that have executed on a CPU using the CPU cache as a side-channel. These attacks are described in detail by Google Project Zero, the Institute of Applied Information Processing and Communications (IAIK) at Graz University of Technology (TU Graz) and Anders Fogh. The issues are organized into three variants:
* Variant 1 (CVE-2017-5753, [Spectre](<https://spectreattack.com/spectre.pdf>)): Bounds check bypass
* Variant 2 (CVE-2017-5715, also [Spectre](<https://spectreattack.com/spectre.pdf>)): Branch target injection[](<https://spectreattack.com/spectre.pdf>)
* Variant 3 (CVE-2017-5754, [Meltdown](<https://meltdownattack.com/meltdown.pdf>)): Rogue data cache load, memory access permission check performed after kernel memory read
Spectre
Spectre attacks take advantage of a CPU's branch prediction capabilities. Modern CPUs include a feature called branch prediction, which speculatively executes instructions at a location that the CPU believes it will branch to. Such speculative execution helps to more fully utilize the parts of the CPU, minimizing the time waiting, and therefore improving performance. When a branch is successfully predicted, instructions will retire, which means the outcomes of the instructions such as register and memory writes will be committed. If a branch is mispredicted, the speculatively-executed instructions will be discarded, and the direct side-effects of the instructions are undone. What is not undone are the indirect side-effects, such as CPU cache changes. By measuring latency of memory access operations, the cache can be used to extract values from speculatively-executed instructions.
With Spectre variant 1 (CVE-2017-5753), the instructions after a conditional branch are speculatively executed as the result of a misprediction. With Spectre variant 2 (CVE-2017-5715), the CPU executes instructions at a location determined by a mispredicted branch target.
With both variants of the Spectre attack, the impact is that a process may leak sensitive data to other processes on a system. Spectre may also allow one part of an application to access other parts of the same process memory space that would otherwise not be permitted.
While the Spectre attack itself does not cross a user/kernel memory privilege boundary, depending on the configuration of the target platform, the Spectre attack may indirectly allow a user-space application to access kernel memory. For example, the Project Zero blog post describes a scenario that uses eBPF to exfiltrate kernel memory contents into user-space code. This is made possible because eBPF JIT allows for userspace applications to inject code that is executed in kernel space. While this code is verified by the kernel, eBPF-compliant code will be allowed to execute with kernel permissions. The exploit described by Project Zero leverages eBPF to execute the Spectre attack in kernel space, while exfiltrating the data to user space. It is possible that other technologies that allow in-kernel code execution may also possibly be leveraged to leak kernel memory using Spectre.
Meltdown
Meltdown is related to the Spectre attack in that it also uses a cache side channel to access data that otherwise wouldn't be available. The main difference is that it leverages out-of-order execution capabilities in modern CPUs. Like speculative execution due to branch prediction, as used by Spectre, out-of-order execution on a CPU is a technique for ensuring fullest utilization of the CPU's parts. Although instructions may appear sequentially in the machine language, a CPU that supports out-of-order execution may execute instructions in a non-sequential manner, which can minimize the time that a CPU spends idle.
Meltdown leverages insecure behavior that has been demonstrated in Intel CPUs and may affect CPUs from other vendors. Vulnerable CPUs allow memory reads in out-of-order instruction execution, and also contain a race condition between the raising of exceptions and the out-of-order instruction execution. The Meltdown attack reads a kernel memory value, which raises an exception because code running with user-space privileges are not permitted to directly read kernel memory. However, due to the race condition, out-of-order instructions following the faulting instruction may also execute. Even though instructions appear after the faulting instruction, out-of-order execution allows them to execute, using data retrieved from the instruction that raises the exception. By the time the exception is raised, some number of out-of-order instructions have executed. Although the raised exception causes the CPU to roll back the out-of-order instructions, the cache state is not reverted. This allows data from out-of-order instructions to persist beyond the point when the exception has been raised.
The impact of Meltdown is that a process running in user space is able to view the contents of kernel memory. Meltdown may also allow Spectre-like memory content leaking that does not cross the user/kernel privilege boundary.
The Linux kernel mitigations for Meltdown are referred to as KAISER, and subsequently KPTI, which aim to improve separation of kernel and user memory pages. Because the Spectre attacks do not cross user/kernel boundaries, the protections introduced with KAISER/KPTI do not add any protection against them.
The following table compares Spectre and Meltdown.
| | Spectre| Meltdown
---|---|--- CPU mechanism for triggering| Speculative execution from branch prediction| Out-of-order execution Affected platforms| CPUs that perform speculative execution from branch prediction| CPUs that allow memory reads in out-of-order instructions Difficulty of successful attack| High - Requires tailoring to the software environment of the victim process| Low - Kernel memory access exploit code is mostly universal Impact| Cross- and intra-process (including kernel) memory disclosure| Kernel memory disclosure to userspace Software mitigations| Variant 1: Compiler changes. Web browser updates to help prevent exploitation from JavaScript
Variant 2: Indirect Branch Restricted Speculation (IBRS). Note: The software mitigation for Spectre variant 2 requires CPU microcode updates| Kernel page-table isolation (KPTI)
Impact
An attacker able to execute code with user privileges can achieve various impacts. The Meltdown attack allows reading of kernel memory from userspace. This can result in privilege escalation, disclosure of sensitive information, or it can weaken kernel-level protections, such as KASLR. The Spectre attack can allow inter-process or intra-process data leaks.
To execute code locally, an attacker would require a valid account or independent compromise of the target. Attacks using JavaScript in web browsers are possible. Multi-user and multi-tenant systems (including virtualized and cloud environments) likely face the greatest risk. Systems used to browse arbitrary web sites are also at risk. Single-user systems that do not readily provide a way for attackers to execute code locally face significantly lower risk.
Solution
Apply updates
Operating system, CPU microcode updates, and some application updates mitigate these attacks. Note that in many cases, the software fixes for these vulnerabilities will have a negative affect on system performance. Also note that Microsoft Windows systems will no longer receive security updates via Windows Update if they are not running compliant anti-virus software. As with deploying any software updates, be sure to prioritize and test updates as necessary.
Consider CPU Options
Initial reports from the field indicate that overall system performance is impacted by many of the available patches for these vulnerabilities. Depending on the software workflow and the CPU capabilities present, the performance impact of software mitigations may be non-trivial and therefore may become an ongoing operational concern for some organizations. While we recognize that replacing existing CPUs in already deployed systems is not practical, organizations acquiring new systems should evaluate their CPU selection in light of the expected longevity of this vulnerability in available hardware as well as the performance impacts resulting from the various platform-specific software patches. Deployment contexts and performance requirements vary widely, and must be balanced by informed evaluation of the associated security risks. Contact your system vendor to determine if the CPU and operating system combination will experience a performance penalty due to software mitigations for these vulnerabilities.
Vendor Information
584653
Filter by status: All Affected Not Affected Unknown
Filter by content: __ Vendor has issued information
__ Sort by: Status Alphabetical
Expand all
Affected Unknown __ Unaffected
Javascript is disabled. Click here to view vendors.
__ AMD
Updated: January 03, 2018
Status
__ Affected
Vendor Statement
No statement is currently available from the vendor regarding this vulnerability.
Vendor Information
We are not aware of further vendor information regarding this vulnerability.
Note that Windows systems without antivirus do not appear to receive the ADV180002 update automatically. In order to receive the update through Windows Update, run the following command:
reg add "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat" /v cadca5fe-87d3-4b96-b7fb-a231484277cc /t REG_DWORD /d 0 /f
If a third-party antivirus product does not explicitly indicate compatibility with to the protections provided by ADV180002 using the above registry value, the system will not automatically receive the ADV180002 update as well.
Once a system has the ADV180002 update installed, it must be manually activated using the following commands to make the appropriate registry changes:
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management" /v FeatureSettingsOverride /t REG_DWORD /d 0 /f reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management" /v FeatureSettingsOverrideMask /t REG_DWORD /d 3 /f reg add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Virtualization" /v MinVmVersionForCpuBasedMitigations /t REG_SZ /d "1.0" /f
Also note that in addition to the above changes, ADV180002 requires CPU microcode updates to achieve full protection. In some cases, Windows Update may not automatically install the ADV180002 update. An unofficial spreadsheet of antivirus vendor compatibility with this update is maintained here:
On systems that have not received the ADV180002 update automatically, you may have to install the update manually. Please see for more details.
To verify that your Windows system has protections against Meltdown and Spectre variant 2, in a PowerShell session running with Administrator privileges, run:
Get-SpeculationControlSettings
If this fails, you may need to change your PowerShell ExecutionPolicy setting: Set-ExecutionPolicy RemoteSignedOnce you are satisfied with the PowerShell output, you can revert the ExecutionPolicy setting back to the default Restricted setting by running: Set-ExecutionPolicy Restricted
The output of this PowerShell command will indicate the status of whether the CPU has the required microcode update, whether Windows has the required software update installed, and whether the mitigations are enabled. Any setting that indicates "False" is an indicator of incomplete protection from Meltdown and/or Spectre.
For example, a system that has the ADV180002 update properly installed and enabled, but is missing the CPU microcode update to fully enable the protections will show output like this:
Once the CPU microcode is updated on such a system (e.g. by way of a BIOS update) , the output will look like this, which indicates that the protections that Microsoft have released are fully enabled:
If the above PowerShell command indicates "Windows OS support for PCID optimization is enabled: False", this is a symptom of using a processor that doesn't support process context identifiers (PCID). Such processors cannot take advantage of the performance optimization that avoids a TLB flush.
If the above PowerShell command indicates "Hardware requires kernel VA shadowing: False", this is a symptom of using a processor that doesn't require mitigations for CVE-2017-5754 (Meltdown).
Also note that Microsoft has not yet provided protection for CVE-2017-5754 (Meltdown) on affected 32-bit platforms.
If you have feedback, comments, or additional information about this vulnerability, please send us email.
__ Mozilla
Updated: January 03, 2018
Status
__ Affected
Vendor Statement
No statement is currently available from the vendor regarding this vulnerability.
Vendor Information
We are not aware of further vendor information regarding this vulnerability.
Both Spectre and Meltdown attacks presupposed “open platforms”, where
additional code can be added by a non-privileged user. The Technicolor products
are not open platforms. Even where 3rd party application can run in containers
and can be managed via Life Cycle Management, these applications are validated
and signed before they can be installed on the platform. Technicolor is
currently working with its vendors to identify if additional layers of
protection are needed. Yet, as the current platforms are closed and have secure
bootloading mechanism in place, there is no risk and no privilege acquired by
an attacker in exploiting such an attack on Technicolor's devices.
Vendor Information
We are not aware of further vendor information regarding this vulnerability.
__ ASUSTeK Computer Inc.
Updated: January 05, 2018
Status
__ Unknown
Vendor Statement
No statement is currently available from the vendor regarding this vulnerability.
Vendor Information
We are not aware of further vendor information regarding this vulnerability.
__ Acer
Updated: January 05, 2018
Status
__ Unknown
Vendor Statement
No statement is currently available from the vendor regarding this vulnerability.
Vendor Information
We are not aware of further vendor information regarding this vulnerability.
__ F5 Networks, Inc.
Updated: January 05, 2018
Status
__ Unknown
Vendor Statement
No statement is currently available from the vendor regarding this vulnerability.
Vendor Information
We are not aware of further vendor information regarding this vulnerability.
Vendor References
<https://support.f5.com/csp/article/K91229003>
__ GIGABYTE
Updated: January 05, 2018
Status
__ Unknown
Vendor Statement
No statement is currently available from the vendor regarding this vulnerability.
Vendor Information
We are not aware of further vendor information regarding this vulnerability.
__ HP Inc.
Updated: January 05, 2018
Status
__ Unknown
Vendor Statement
No statement is currently available from the vendor regarding this vulnerability.
Vendor Information
We are not aware of further vendor information regarding this vulnerability.
__ Samsung Semiconductor Inc.
Updated: January 05, 2018
Status
__ Unknown
Vendor Statement
No statement is currently available from the vendor regarding this vulnerability.
Vendor Information
We are not aware of further vendor information regarding this vulnerability.
__ Toshiba Corporation
Updated: January 05, 2018
Status
__ Unknown
Vendor Statement
No statement is currently available from the vendor regarding this vulnerability.
Vendor Information
We are not aware of further vendor information regarding this vulnerability.
These issues were researched and reported by researchers at Google Project Zero (Jann Horn) the Institute of Applied Information Processing and Communications (IAIK) at Graz University of Technology (Gruss et. al.), Paul Kocher, and Anders Fogh.
This document was written by Art Manion and Will Dormann.
Other Information
CVE IDs: | CVE-2017-5753, CVE-2017-5715, CVE-2017-5754
---|--- Date Public: | 2018-01-03 Date First Published: | 2018-01-04 Date Last Updated: | 2018-07-03 21:27 UTC Document Revision: | 230
{"id": "VU:584653", "hash": "d0094ef411327cd6b58a1ac31940f92e", "type": "cert", "bulletinFamily": "info", "title": "CPU hardware vulnerable to side-channel attacks", "description": "### Overview \n\nCPU hardware implementations are vulnerable to cache side-channel attacks. These vulnerabilities are referred to as [Meltdown](<https://meltdownattack.com/>) and [Spectre](<https://spectreattack.com/>).\n\n### Description \n\nCPU hardware implementations are vulnerable to side-channel attacks referred to as [Meltdown](<https://meltdownattack.com/>) and [Spectre](<https://spectreattack.com/>). Both Spectre and Meltdown take advantage of the ability to extract information from instructions that have executed on a CPU using the CPU cache as a side-channel. These attacks are described in detail by [Google Project Zero](<https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html>), the Institute of Applied Information Processing and Communications (IAIK) at Graz University of Technology (TU Graz) and Anders Fogh. The issues are organized into three variants:\n\n * Variant 1 (CVE-2017-5753, [Spectre](<https://spectreattack.com/spectre.pdf>)): Bounds check bypass\n * Variant 2 (CVE-2017-5715, also [Spectre](<https://spectreattack.com/spectre.pdf>)): Branch target injection[](<https://spectreattack.com/spectre.pdf>)\n * Variant 3 (CVE-2017-5754, [Meltdown](<https://meltdownattack.com/meltdown.pdf>)): Rogue data cache load, memory access permission check performed after kernel memory read\n \n**Spectre** \n \nSpectre attacks take advantage of a CPU's branch prediction capabilities. Modern CPUs include a feature called branch prediction, which speculatively executes instructions at a location that the CPU believes it will branch to. Such speculative execution helps to more fully utilize the parts of the CPU, minimizing the time waiting, and therefore improving performance. When a branch is successfully predicted, instructions will retire, which means the outcomes of the instructions such as register and memory writes will be committed. If a branch is mispredicted, the speculatively-executed instructions will be discarded, and the direct side-effects of the instructions are undone. What is not undone are the indirect side-effects, such as CPU cache changes. By measuring latency of memory access operations, the cache can be used to extract values from speculatively-executed instructions. \n \nWith Spectre variant 1 (CVE-2017-5753), the instructions after a conditional branch are speculatively executed as the result of a misprediction. With Spectre variant 2 (CVE-2017-5715), the CPU executes instructions at a location determined by a mispredicted branch target. \n \nWith both variants of the Spectre attack, the impact is that a process may leak sensitive data to other processes on a system. Spectre may also allow one part of an application to access other parts of the same process memory space that would otherwise not be permitted. \n \nWhile the Spectre attack itself does not cross a user/kernel memory privilege boundary, depending on the configuration of the target platform, the Spectre attack may indirectly allow a user-space application to access kernel memory. For example, the[ Project Zero blog post](<https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html>) describes a scenario that uses eBPF to exfiltrate kernel memory contents into user-space code. This is made possible because eBPF JIT allows for userspace applications to inject code that is executed in kernel space. While this code is verified by the kernel, eBPF-compliant code will be allowed to execute with kernel permissions. The exploit described by Project Zero leverages eBPF to execute the Spectre attack in kernel space, while exfiltrating the data to user space. It is possible that other technologies that allow in-kernel code execution may also possibly be leveraged to leak kernel memory using Spectre. \n \n**Meltdown** \n \nMeltdown is related to the Spectre attack in that it also uses a cache side channel to access data that otherwise wouldn't be available. The main difference is that it leverages out-of-order execution capabilities in modern CPUs. Like speculative execution due to branch prediction, as used by Spectre, out-of-order execution on a CPU is a technique for ensuring fullest utilization of the CPU's parts. Although instructions may appear sequentially in the machine language, a CPU that supports out-of-order execution may execute instructions in a non-sequential manner, which can minimize the time that a CPU spends idle. \n \nMeltdown leverages insecure behavior that has been demonstrated in Intel CPUs and may affect CPUs from other vendors. Vulnerable CPUs allow memory reads in out-of-order instruction execution, and also contain a race condition between the raising of exceptions and the out-of-order instruction execution. The Meltdown attack reads a kernel memory value, which raises an exception because code running with user-space privileges are not permitted to directly read kernel memory. However, due to the race condition, out-of-order instructions following the faulting instruction may also execute. Even though instructions appear after the faulting instruction, out-of-order execution allows them to execute, using data retrieved from the instruction that raises the exception. By the time the exception is raised, some number of out-of-order instructions have executed. Although the raised exception causes the CPU to roll back the out-of-order instructions, the cache state is not reverted. This allows data from out-of-order instructions to persist beyond the point when the exception has been raised. \n \nThe impact of Meltdown is that a process running in user space is able to view the contents of kernel memory. Meltdown may also allow Spectre-like memory content leaking that does not cross the user/kernel privilege boundary. \n \nThe Linux kernel mitigations for Meltdown are referred to as KAISER, and subsequently KPTI, which aim to improve separation of kernel and user memory pages. Because the Spectre attacks do not cross user/kernel boundaries, the protections introduced with KAISER/KPTI do not add any protection against them. \n \nThe following table compares Spectre and Meltdown. \n \n| | **Spectre**| **Meltdown** \n---|---|--- \n**CPU mechanism for triggering**| Speculative execution from branch prediction| Out-of-order execution \n**Affected platforms**| CPUs that perform speculative execution from branch prediction| CPUs that allow memory reads in out-of-order instructions \n**Difficulty of successful attack**| High - Requires tailoring to the software environment of the victim process| Low - Kernel memory access exploit code is mostly universal \n**Impact**| Cross- and intra-process (including kernel) memory disclosure| Kernel memory disclosure to userspace \n**Software mitigations**| Variant 1: Compiler changes. Web browser updates to help prevent exploitation from JavaScript \nVariant 2: Indirect Branch Restricted Speculation ([IBRS](<https://lkml.org/lkml/2018/1/4/615>)). \n**Note: **The software mitigation for Spectre variant 2 requires CPU microcode updates| Kernel page-table isolation ([KPTI](<https://en.wikipedia.org/wiki/Kernel_page-table_isolation>)) \n \n### Impact \n\nAn attacker able to execute code with user privileges can achieve various impacts. The Meltdown attack allows reading of kernel memory from userspace. This can result in privilege escalation, disclosure of sensitive information, or it can weaken kernel-level protections, such as KASLR. The Spectre attack can allow inter-process or intra-process data leaks. \n \nTo execute code locally, an attacker would require a valid account or independent compromise of the target. Attacks using JavaScript in web browsers are possible. Multi-user and multi-tenant systems (including virtualized and cloud environments) likely face the greatest risk. Systems used to browse arbitrary web sites are also at risk. Single-user systems that do not readily provide a way for attackers to execute code locally face significantly lower risk. \n \n--- \n \n### Solution \n\n**Apply updates** \n \nOperating system, CPU microcode updates, and some application updates mitigate these attacks. Note that in many cases, the software fixes for these vulnerabilities will have a negative affect on system performance. Also note that Microsoft Windows systems [will no longer receive security updates](<https://doublepulsar.com/important-information-about-microsoft-meltdown-cpu-security-fixes-antivirus-vendors-and-you-a852ba0292ec>) via Windows Update if they are not running compliant anti-virus software. As with deploying any software updates, be sure to prioritize and test updates as necessary. \n \n**Consider CPU Options** \n \nInitial reports from the field indicate that overall system performance is impacted by many of the available patches for these vulnerabilities. Depending on the software workflow and the CPU capabilities present, the performance impact of software mitigations may be non-trivial and therefore may become an ongoing operational concern for some organizations. While we recognize that replacing existing CPUs in already deployed systems is not practical, organizations acquiring new systems should evaluate their CPU selection in light of the expected longevity of this vulnerability in available hardware as well as the performance impacts resulting from the various platform-specific software patches. Deployment contexts and performance requirements vary widely, and must be balanced by informed evaluation of the associated security risks. Contact your system vendor to determine if the CPU and operating system combination will experience a performance penalty due to software mitigations for these vulnerabilities. \n \n--- \n \n### Vendor Information\n\n584653\n\nFilter by status: All Affected Not Affected Unknown\n\nFilter by content: __ Vendor has issued information\n\n__ Sort by: Status Alphabetical\n\nExpand all\n\n__ Affected __ Unknown __ Unaffected \n\n**Javascript is disabled. Click here to view vendors.**\n\n### __ AMD\n\nUpdated: January 03, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://www.amd.com/en/corporate/speculative-execution>\n\n### __ Amazon\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://aws.amazon.com/security/security-bulletins/AWS-2018-013/>\n\n### __ Android Open Source Project\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://source.android.com/security/bulletin/2018-01-01>\n\n### __ Apple\n\nUpdated: February 02, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://support.apple.com/en-us/HT208394>\n * <https://support.apple.com/en-us/HT208397>\n * <https://support.apple.com/en-us/HT208403>\n * <https://support.apple.com/en-us/HT208401>\n * <https://support.apple.com/en-ca/HT208465>\n\n### Addendum\n\n<https://twitter.com/aionescu/status/948609809540046849> \n<https://twitter.com/ErrataRob/status/949088097475743744>\n\nIf you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:cert@cert.org?Subject=VU%23584653 Feedback>).\n\n### __ Arm\n\nUpdated: January 03, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://developer.arm.com/support/security-update>\n * <https://developer.arm.com/-/media/Files/pdf/Cache_Speculation_Side-channels.pdf>\n\n### Addendum\n\n<https://lwn.net/Articles/740393/>\n\nIf you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:cert@cert.org?Subject=VU%23584653 Feedback>).\n\n### __ CentOS\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://lists.centos.org/pipermail/centos-announce/2018-January/date.html>\n\n### __ Cisco\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20180104-cpusidechannel>\n\n### __ Citrix\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://support.citrix.com/article/CTX231399>\n\n### __ Debian GNU/Linux\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://security-tracker.debian.org/tracker/CVE-2017-5754>\n\n### __ Dell\n\nUpdated: January 08, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <http://www.dell.com/support/contents/us/en/19/article/product-support/self-support-knowledgebase/software-and-downloads/support-for-meltdown-and-spectre>\n\n### __ DragonFly BSD Project\n\nUpdated: January 08, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <http://lists.dragonflybsd.org/pipermail/users/2018-January/313758.html>\n\n### __ Fedora Project\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://fedoramagazine.org/protect-fedora-system-meltdown/>\n\n### __ Fortinet, Inc.\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://fortiguard.com/psirt/FG-IR-18-002>\n\n### __ FreeBSD Project\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://www.freebsd.org/news/newsflash.html#event20180104:01>\n\n### __ Fujitsu\n\nUpdated: January 11, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <http://support.ts.fujitsu.com/content/SideChannelAnalysisMethod.asp?lng=EN>\n\n### __ Google\n\nUpdated: January 03, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://security.googleblog.com/2018/01/todays-cpu-vulnerability-what-you-need.html>\n * <https://support.google.com/faqs/answer/7622138>\n\n### __ Hewlett Packard Enterprise\n\nUpdated: January 08, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://www.hpe.com/us/en/services/security-vulnerability.html>\n\n### __ IBM Corporation\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://www.ibm.com/blogs/psirt/potential-cpu-security-issue/>\n\n### __ Intel\n\nUpdated: January 22, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://newsroom.intel.com/news/intel-responds-to-security-research-findings/>\n * <https://newsroom.intel.com/news-releases/intel-issues-updates-protect-systems-security-exploits>\n * <https://www.intel.com/content/www/us/en/architecture-and-technology/facts-about-side-channel-analysis-and-intel-products.html>\n * <https://newsroom.intel.com/news/root-cause-of-reboot-issue-identified-updated-guidance-for-customers-and-partners/>\n * <https://newsroom.intel.com/wp-content/uploads/sites/11/2018/01/microcode-update-guidance.pdf>\n\n### __ Lenovo\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://support.lenovo.com/us/en/solutions/len-18282>\n\n### __ Linux Kernel\n\nUpdated: January 04, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://lkml.org/lkml/2017/11/22/956>\n * <https://lkml.org/lkml/2018/1/4/174>\n * <https://lkml.org/lkml/2018/1/4/615>\n\n### __ Microsoft\n\nUpdated: January 11, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://support.microsoft.com/en-us/help/4073119/protect-against-speculative-execution-side-channel-vulnerabilities-in>\n * <https://support.microsoft.com/en-us/help/4072699/january-3-2018-windows-security-updates-and-antivirus-software>\n * <https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/CVE-2017-5715-and-hyper-v-vms>\n * <https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/ADV180002>\n * <https://blogs.windows.com/msedgedev/2018/01/03/speculative-execution-mitigations-microsoft-edge-internet-explorer/>\n * <https://azure.microsoft.com/en-us/blog/securing-azure-customers-from-cpu-vulnerability/>\n * <https://cloudblogs.microsoft.com/microsoftsecure/2018/01/09/understanding-the-performance-impact-of-spectre-and-meltdown-mitigations-on-windows-systems/>\n * <https://support.microsoft.com/en-us/help/4073707/windows-os-security-update-block-for-some-amd-based-devices>\n\n### Addendum\n\nNote that Windows systems without antivirus do not appear to receive the ADV180002 update automatically. In order to receive the update through Windows Update, run the following command:\n\n \n`reg add \"HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\QualityCompat\" /v cadca5fe-87d3-4b96-b7fb-a231484277cc /t REG_DWORD /d 0 /f` \nIf a third-party antivirus product does not explicitly indicate compatibility with to the protections provided by ADV180002 using the above registry value, the system will not automatically receive the ADV180002 update as well. \n \nOnce a system has the ADV180002 update installed, it must be manually activated using the following commands to make the appropriate registry changes: \n\n\n`reg add \"HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Control\\Session Manager\\Memory Management\" /v FeatureSettingsOverride /t REG_DWORD /d 0 /f` \n`reg add \"HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Control\\Session Manager\\Memory Management\" /v FeatureSettingsOverrideMask /t REG_DWORD /d 3 /f` \n`reg add \"HKLM\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Virtualization\" /v MinVmVersionForCpuBasedMitigations /t REG_SZ /d \"1.0\" /f ` \nAlso note that in addition to the above changes, ADV180002 requires CPU microcode updates to achieve full protection. In some cases, Windows Update may not automatically install the ADV180002 update. An unofficial spreadsheet of antivirus vendor compatibility with this update is maintained here: \n \nOn systems that have not received the ADV180002 update automatically, you may have to install the update manually. Please see for more details. \n \nTo verify that your Windows system has protections against Meltdown and Spectre variant 2, in a PowerShell session running with Administrator privileges, run:\n\n 1. `Install-Module SpeculationControl` \nIf this fails, you may need to install [PackageManagement PowerShell Modules](<https://www.microsoft.com/en-us/download/details.aspx?id=51451>)\n 2. `Get-SpeculationControlSettings` \nIf this fails, you may need to change your PowerShell ExecutionPolicy setting: ` \nSet-ExecutionPolicy RemoteSigned \n`Once you are satisfied with the PowerShell output, you can revert the ExecutionPolicy setting back to the default Restricted setting by running: \n`Set-ExecutionPolicy Restricted`\n` ` \nThe output of this PowerShell command will indicate the status of whether the CPU has the required microcode update, whether Windows has the required software update installed, and whether the mitigations are enabled. Any setting that indicates \"False\" is an indicator of incomplete protection from Meltdown and/or Spectre. \n \nFor example, a system that has the ADV180002 update properly installed and enabled, but is missing the CPU microcode update to fully enable the protections will show output like this: \n \n \nOnce the CPU microcode is updated on such a system (e.g. by way of a BIOS update) , the output will look like this, which indicates that the protections that Microsoft have released are fully enabled: \n \n \nIf the above PowerShell command indicates \"Windows OS support for PCID optimization is enabled: False\", this is a symptom of using a processor that doesn't support process context identifiers (PCID). Such processors cannot take advantage of the performance optimization that avoids a TLB flush. \n \nIf the above PowerShell command indicates \"Hardware requires kernel VA shadowing: False\", this is a symptom of using a processor that doesn't require mitigations for CVE-2017-5754 (Meltdown). \n \nAlso note that Microsoft has not yet provided protection for CVE-2017-5754 (Meltdown) on affected 32-bit platforms. \n\nIf you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:cert@cert.org?Subject=VU%23584653 Feedback>).\n\n### __ Mozilla\n\nUpdated: January 03, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://blog.mozilla.org/security/2018/01/03/mitigations-landing-new-class-timing-attack/>\n\n### __ NVIDIA\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <http://nvidia.custhelp.com/app/answers/detail/a_id/4609>\n * <http://nvidia.custhelp.com/app/answers/detail/a_id/4611>\n * <http://nvidia.custhelp.com/app/answers/detail/a_id/4613>\n * <http://nvidia.custhelp.com/app/answers/detail/a_id/4614>\n * <https://www.nvidia.com/en-us/product-security/>\n\n### __ NetBSD\n\nUpdated: January 08, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### __ OpenBSD\n\nUpdated: January 08, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * [https://marc.info/?l=openbsd-tech&m=151521435721902&w=2](<https://marc.info/?l=openbsd-tech&m=151521435721902&w=2>)\n\n### __ Oracle Corporation\n\nUpdated: February 23, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://www.theregister.co.uk/2018/01/16/oracle_quarterly_patches_jan_2018/>\n\n### __ QUALCOMM Incorporated\n\nUpdated: January 11, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Addendum\n\nThe Register has published the following: <https://www.theregister.co.uk/2018/01/06/qualcomm_processor_security_vulnerabilities/>\n\nIf you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:cert@cert.org?Subject=VU%23584653 Feedback>).\n\n### __ Red Hat, Inc.\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * [https://access.redhat.com/security/security-updates/#/security-advisories?q=&p=1&sort=portal_publication_date%20desc&rows=10&documentKind=PortalProduct](<https://access.redhat.com/security/security-updates/#/security-advisories?q=&p=1&sort=portal_publication_date%20desc&rows=10&documentKind=PortalProduct>)\n\n### __ SUSE Linux\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://www.suse.com/c/suse-addresses-meltdown-spectre-vulnerabilities/>\n * <http://lists.suse.com/pipermail/sle-security-updates/2018-January/date.html>\n\n### __ Synology\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://www.synology.com/en-global/support/security/Synology_SA_18_01>\n\n### __ Trend Micro\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://success.trendmicro.com/solution/1119183-important-information-for-trend-micro-solutions-and-microsoft-january-2018-security-updates>\n\n### __ Ubuntu\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/SpectreAndMeltdown>\n\n### __ VMware\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://www.vmware.com/security/advisories/VMSA-2018-0002.html>\n\n### __ Xen\n\nUpdated: January 24, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <http://xenbits.xen.org/xsa/advisory-254.html>\n * <https://blog.xenproject.org/2018/01/22/xen-project-spectre-meltdown-faq-jan-22-update/>\n\n### __ openSUSE project\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://lists.opensuse.org/opensuse-security-announce/2018-01/msg00001.html>\n\n### __ NetApp\n\nUpdated: January 08, 2018 \n\n### Status\n\n__ Not Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * [httpsecurity.netapp.com/advisory/ntap-20180104-0001/](<httpsecurity.netapp.com/advisory/ntap-20180104-0001/>)\n\n### __ Raspberry Pi\n\nUpdated: January 08, 2018 \n\n### Status\n\n__ Not Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://www.raspberrypi.org/blog/why-raspberry-pi-isnt-vulnerable-to-spectre-or-meltdown/>\n\n### __ __ Technicolor\n\nUpdated: January 08, 2018 \n\n### Status\n\n__ Not Affected\n\n### Vendor Statement\n\nBoth Spectre and Meltdown attacks presupposed \u201copen platforms\u201d, where \nadditional code can be added by a non-privileged user. The Technicolor products \nare not open platforms. Even where 3rd party application can run in containers \nand can be managed via Life Cycle Management, these applications are validated \nand signed before they can be installed on the platform. Technicolor is \ncurrently working with its vendors to identify if additional layers of \nprotection are needed. Yet, as the current platforms are closed and have secure \nbootloading mechanism in place, there is no risk and no privilege acquired by \nan attacker in exploiting such an attack on Technicolor's devices.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### __ ASUSTeK Computer Inc.\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Unknown\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### __ Acer\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Unknown\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### __ F5 Networks, Inc.\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Unknown\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://support.f5.com/csp/article/K91229003>\n\n### __ GIGABYTE\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Unknown\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### __ HP Inc.\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Unknown\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### __ Samsung Semiconductor Inc.\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Unknown\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### __ Toshiba Corporation\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Unknown\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\nView all 46 vendors __View less vendors __\n\n \n\n\n### CVSS Metrics \n\nGroup | Score | Vector \n---|---|--- \nBase | 4.4 | AV:L/AC:M/Au:S/C:C/I:N/A:N \nTemporal | 3.4 | E:POC/RL:OF/RC:C \nEnvironmental | 5.1 | CDP:ND/TD:H/CR:H/IR:ND/AR:ND \n \n \n\n\n### References \n\n * <https://vuls.cert.org/confluence/display/Wiki/Vulnerabilities+Associated+with+CPU+Speculative+Execution>\n * <https://meltdownattack.com/>\n * <https://meltdownattack.com/meltdown.pdf>\n * <https://spectreattack.com/>\n * <https://spectreattack.com/spectre.pdf>\n * <https://security.googleblog.com/2018/01/todays-cpu-vulnerability-what-you-need.html>\n * <https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html>\n * <https://cyber.wtf/2017/07/28/negative-result-reading-kernel-memory-from-user-mode/>\n * <https://github.com/IAIK/KAISER>\n * <https://gruss.cc/files/kaiser.pdf>\n * <https://gruss.cc/files/prefetch.pdf>\n * <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5aa90a84589282b87666f92b6c3c917c8080a9bf>\n * <https://lkml.org/lkml/2017/12/27/2>\n * <https://lkml.org/lkml/2018/1/4/615>\n * <https://lwn.net/Articles/741878/>\n * <https://lwn.net/Articles/737940/>\n * <https://lwn.net/Articles/742702/>\n * <http://pythonsweetness.tumblr.com/post/169166980422/the-mysterious-case-of-the-linux-page-table>\n * <https://nakedsecurity.sophos.com/2018/01/03/fckwit-aka-kaiser-aka-kpti-intel-cpu-flaw-needs-low-level-os-patches/>\n * <https://en.wikipedia.org/wiki/Kernel_page-table_isolation>\n * <https://chrisam.net/2018/01/04/speculative-execution-side-channel-vulnerabilities-vendor-published-info/>\n * <https://www.raspberrypi.org/blog/why-raspberry-pi-isnt-vulnerable-to-spectre-or-meltdown/>\n * <https://doublepulsar.com/important-information-about-microsoft-meltdown-cpu-security-fixes-antivirus-vendors-and-you-a852ba0292ec>\n * [https://docs.google.com/spreadsheets/d/184wcDt9I9TUNFFbsAVLpzAtckQxYiuirADzf3cL42FQ/htmlview?usp=sharing&sle=true](<https://docs.google.com/spreadsheets/d/184wcDt9I9TUNFFbsAVLpzAtckQxYiuirADzf3cL42FQ/htmlview?usp=sharing&sle=true>)\n * <https://github.com/iadgov/Spectre-and-Meltdown-Guidance>\n * <https://arxiv.org/abs/1802.03802>\n\n### Acknowledgements\n\nThese issues were researched and reported by researchers at Google Project Zero (Jann Horn) the Institute of Applied Information Processing and Communications (IAIK) at Graz University of Technology (Gruss et. al.), Paul Kocher, and Anders Fogh. \n\nThis document was written by Art Manion and Will Dormann. \n\n### Other Information\n\n**CVE IDs:** | [CVE-2017-5753, ](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5753>) [CVE-2017-5715, ](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5715>) [CVE-2017-5754](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5754>) \n---|--- \n**Date Public:** | 2018-01-03 \n**Date First Published:** | 2018-01-04 \n**Date Last Updated: ** | 2018-07-03 21:27 UTC \n**Document Revision: ** | 230 \n", "published": "2018-01-04T00:00:00", "modified": "2018-07-03T21:27:00", "cvss": {"score": 4.7, "vector": "AV:L/AC:M/Au:N/C:C/I:N/A:N"}, "href": "https://www.kb.cert.org/vuls/id/584653", "reporter": "CERT", "references": ["https://vuls.cert.org/confluence/display/Wiki/Vulnerabilities+Associated+with+CPU+Speculative+Execution", "https://meltdownattack.com/", "https://meltdownattack.com/meltdown.pdf", "https://spectreattack.com/", "https://spectreattack.com/spectre.pdf", "https://security.googleblog.com/2018/01/todays-cpu-vulnerability-what-you-need.html", "https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html", "https://cyber.wtf/2017/07/28/negative-result-reading-kernel-memory-from-user-mode/", "https://github.com/IAIK/KAISER", "https://gruss.cc/files/kaiser.pdf", "https://gruss.cc/files/prefetch.pdf", "https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5aa90a84589282b87666f92b6c3c917c8080a9bf", "https://lkml.org/lkml/2017/12/27/2", "https://lkml.org/lkml/2018/1/4/615", "https://lwn.net/Articles/741878/", "https://lwn.net/Articles/737940/", "https://lwn.net/Articles/742702/", "http://pythonsweetness.tumblr.com/post/169166980422/the-mysterious-case-of-the-linux-page-table", "https://nakedsecurity.sophos.com/2018/01/03/fckwit-aka-kaiser-aka-kpti-intel-cpu-flaw-needs-low-level-os-patches/", "https://en.wikipedia.org/wiki/Kernel_page-table_isolation", "https://chrisam.net/2018/01/04/speculative-execution-side-channel-vulnerabilities-vendor-published-info/", "https://www.raspberrypi.org/blog/why-raspberry-pi-isnt-vulnerable-to-spectre-or-meltdown/", "https://doublepulsar.com/important-information-about-microsoft-meltdown-cpu-security-fixes-antivirus-vendors-and-you-a852ba0292ec", "https://docs.google.com/spreadsheets/d/184wcDt9I9TUNFFbsAVLpzAtckQxYiuirADzf3cL42FQ/htmlview?usp=sharing&sle=true", "https://github.com/iadgov/Spectre-and-Meltdown-Guidance", "https://arxiv.org/abs/1802.03802"], "cvelist": ["CVE-2017-5715", "CVE-2017-5753", "CVE-2017-5754"], "lastseen": "2019-05-29T20:42:04", "history": [{"bulletin": {"id": "VU:584653", "hash": "a6f3a70a76219bbf674c162a629a9859a04a1c6fbe21c1853b36594496fcad41", "type": "cert", "bulletinFamily": "info", "title": "CPU hardware vulnerable to side-channel attacks", "description": "### Overview\n\nCPU hardware implementations are vulnerable to side-channel attacks. These vulnerabilities are referred to as [Meltdown](<https://meltdownattack.com/>) and [Spectre](<https://spectreattack.com/>).\n\n### Description\n\nCPU hardware implementations are vulnerable to side-channel attacks referred to as [Meltdown](<https://meltdownattack.com/>) and [Spectre](<https://spectreattack.com/>) (also KAISER and KPTI). These attacks are described in detail by [Google Project Zero](<https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html>) and the Institute of Applied Information Processing and Communications (IAIK) at Graz University of Technology (TU Graz). \n \n--- \n \n### Impact\n\nAn attacker able to execute code with user privileges can achieve various impacts, such as reading otherwise protected kernel memory and bypassing KASLR. \n \n--- \n \n### Solution\n\n**Replace CPU hardware**\n\nThe underlying vulnerability is primarily caused by CPU architecture design choices. Fully removing the vulnerability requires replacing vulnerable CPU hardware. \n \n--- \n \n**Apply updates** \n \nOperating system updates mitigate the underlying hardware vulnerability. \n \n--- \n \n### Vendor Information \n\nMany CPU architectures are affected. The list below consists of CPU vendors and operating system vendors. \n \n--- \nVendor| Status| Date Notified| Date Updated \n---|---|---|--- \nAMD| | -| 03 Jan 2018 \nApple| | -| 03 Jan 2018 \nArm| | -| 03 Jan 2018 \nGoogle| | -| 03 Jan 2018 \nIntel| | -| 03 Jan 2018 \nMicrosoft| | -| 03 Jan 2018 \nIf you are a vendor and your product is affected, [let us know](<mailto:cert@cert.org?Subject=VU%23584653 Vendor Status Inquiry>).\n\n### CVSS Metrics \n\nGroup | Score | Vector \n---|---|--- \nBase | 1.5 | AV:L/AC:M/Au:S/C:P/I:N/A:N \nTemporal | 1.2 | E:POC/RL:OF/RC:C \nEnvironmental | 2.0 | CDP:ND/TD:H/CR:H/IR:ND/AR:ND \n \n### References\n\n * <https://meltdownattack.com/>\n * <https://spectreattack.com/>\n * <https://security.googleblog.com/2018/01/todays-cpu-vulnerability-what-you-need.html>\n * <https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html>\n * <https://github.com/IAIK/KAISER>\n * <https://gruss.cc/files/kaiser.pdf>\n * <https://gruss.cc/files/prefetch.pdf>\n * <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5aa90a84589282b87666f92b6c3c917c8080a9bf>\n * <https://lwn.net/Articles/741878/>\n * <https://lwn.net/Articles/737940/>\n * <http://pythonsweetness.tumblr.com/post/169166980422/the-mysterious-case-of-the-linux-page-table>\n * <https://nakedsecurity.sophos.com/2018/01/03/fckwit-aka-kaiser-aka-kpti-intel-cpu-flaw-needs-low-level-os-patches/>\n\n### Credit\n\nThese issues were researched and reported by researchers at Google Project Zero and the Institute of Applied Information Processing and Communications (IAIK) at Graz University of Technology (TU Graz).\n\nThis document was written by Art Manion.\n\n### Other Information\n\n * CVE IDs: [CVE-2017-5753](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5753>) [CVE-2017-5715](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5715>) [CVE-2017-5754](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5754>)\n * Date Public: 03 Jan 2018\n * Date First Published: 03 Jan 2018\n * Date Last Updated: 03 Jan 2018\n * Document Revision: 15\n\n", "published": "2018-01-03T00:00:00", "modified": "2018-01-03T00:00:00", "cvss": {"score": 0.0, "vector": "NONE"}, "href": "https://www.kb.cert.org/vuls/id/584653", "reporter": "CERT", "references": ["https://nakedsecurity.sophos.com/2018/01/03/fckwit-aka-kaiser-aka-kpti-intel-cpu-flaw-needs-low-level-os-patches/", "https://security.googleblog.com/2018/01/todays-cpu-vulnerability-what-you-need.html", "https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html", "https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html", "http://pythonsweetness.tumblr.com/post/169166980422/the-mysterious-case-of-the-linux-page-table", "https://gruss.cc/files/kaiser.pdf", "https://meltdownattack.com/", "https://meltdownattack.com/", "https://meltdownattack.com/", "http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5753", "https://spectreattack.com/", "https://spectreattack.com/", "https://spectreattack.com/", "https://lwn.net/Articles/737940/", "http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5715", "https://github.com/IAIK/KAISER", "https://lwn.net/Articles/741878/", "https://gruss.cc/files/prefetch.pdf", "https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5aa90a84589282b87666f92b6c3c917c8080a9bf", "http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5754"], "cvelist": ["CVE-2017-5753", "CVE-2017-5753", "CVE-2017-5754", "CVE-2017-5754", "CVE-2017-5715", "CVE-2017-5715"], "lastseen": "2018-01-04T06:55:30", "history": [], "viewCount": 0, "enchantments": {"score": {"modified": "2018-01-04T06:55:30", "value": 1.5}}, "objectVersion": "1.4"}, "lastseen": "2018-01-04T06:55:30", "differentElements": ["description", "references"], "edition": 1}, {"bulletin": {"id": "VU:584653", "hash": "bf6c60822c300aad7964b0e676b7514611b75797dd001485de802d44a44752bf", "type": "cert", "bulletinFamily": "info", "title": "CPU hardware vulnerable to side-channel attacks", "description": "### Overview\n\nCPU hardware implementations are vulnerable to side-channel attacks. These vulnerabilities are referred to as [Meltdown](<https://meltdownattack.com/>) and [Spectre](<https://spectreattack.com/>).\n\n### Description\n\nCPU hardware implementations are vulnerable to side-channel attacks referred to as [Meltdown](<https://meltdownattack.com/>) and [Spectre](<https://spectreattack.com/>) (also KAISER and KPTI). These attacks are described in detail by [Google Project Zero](<https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html>) and the Institute of Applied Information Processing and Communications (IAIK) at Graz University of Technology (TU Graz). \n \n--- \n \n### Impact\n\nAn attacker able to execute code with user privileges can achieve various impacts, such as reading otherwise protected kernel memory and bypassing KASLR. \n \n--- \n \n### Solution\n\n**Replace CPU hardware**\n\nThe underlying vulnerability is primarily caused by CPU architecture design choices. Fully removing the vulnerability requires replacing vulnerable CPU hardware. \n \n--- \n \n**Apply updates** \n \nOperating system updates mitigate the underlying hardware vulnerability. \n \n--- \n \n### Vendor Information \n\nMultiple CPU architectures are affected. Operating systems and \n \n--- \nVendor| Status| Date Notified| Date Updated \n---|---|---|--- \nAMD| | -| 03 Jan 2018 \nApple| | -| 03 Jan 2018 \nArm| | -| 03 Jan 2018 \nGoogle| | -| 03 Jan 2018 \nIntel| | -| 03 Jan 2018 \nLinux Kernel| | -| 03 Jan 2018 \nMicrosoft| | -| 03 Jan 2018 \nMozilla| | -| 03 Jan 2018 \nIf you are a vendor and your product is affected, [let us know](<mailto:cert@cert.org?Subject=VU%23584653 Vendor Status Inquiry>).\n\n### CVSS Metrics \n\nGroup | Score | Vector \n---|---|--- \nBase | 1.5 | AV:L/AC:M/Au:S/C:P/I:N/A:N \nTemporal | 1.2 | E:POC/RL:OF/RC:C \nEnvironmental | 2.0 | CDP:ND/TD:H/CR:H/IR:ND/AR:ND \n \n### References\n\n * <https://meltdownattack.com/>\n * <https://spectreattack.com/>\n * <https://security.googleblog.com/2018/01/todays-cpu-vulnerability-what-you-need.html>\n * <https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html>\n * <https://www.us-cert.gov/ncas/current-activity/2018/01/03/Meltdown-and-Spectre-Side-Channel-Vulnerabilities>\n * <https://github.com/IAIK/KAISER>\n * <https://gruss.cc/files/kaiser.pdf>\n * <https://gruss.cc/files/prefetch.pdf>\n * <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5aa90a84589282b87666f92b6c3c917c8080a9bf>\n * <https://lwn.net/Articles/741878/>\n * <https://lwn.net/Articles/737940/>\n * <http://pythonsweetness.tumblr.com/post/169166980422/the-mysterious-case-of-the-linux-page-table>\n * <https://nakedsecurity.sophos.com/2018/01/03/fckwit-aka-kaiser-aka-kpti-intel-cpu-flaw-needs-low-level-os-patches/>\n\n### Credit\n\nThese issues were researched and reported by researchers at Google Project Zero and the Institute of Applied Information Processing and Communications (IAIK) at Graz University of Technology (TU Graz).\n\nThis document was written by Art Manion.\n\n### Other Information\n\n * CVE IDs: [CVE-2017-5753](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5753>) [CVE-2017-5715](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5715>) [CVE-2017-5754](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5754>)\n * Date Public: 03 Jan 2018\n * Date First Published: 03 Jan 2018\n * Date Last Updated: 03 Jan 2018\n * Document Revision: 20\n\n", "published": "2018-01-03T00:00:00", "modified": "2018-01-03T00:00:00", "cvss": {"score": 0.0, "vector": "NONE"}, "href": "https://www.kb.cert.org/vuls/id/584653", "reporter": "CERT", "references": ["https://nakedsecurity.sophos.com/2018/01/03/fckwit-aka-kaiser-aka-kpti-intel-cpu-flaw-needs-low-level-os-patches/", "https://security.googleblog.com/2018/01/todays-cpu-vulnerability-what-you-need.html", "https://www.us-cert.gov/ncas/current-activity/2018/01/03/Meltdown-and-Spectre-Side-Channel-Vulnerabilities", "https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html", "https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html", "http://pythonsweetness.tumblr.com/post/169166980422/the-mysterious-case-of-the-linux-page-table", "https://gruss.cc/files/kaiser.pdf", "https://meltdownattack.com/", "https://meltdownattack.com/", "https://meltdownattack.com/", "http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5753", "https://spectreattack.com/", "https://spectreattack.com/", "https://spectreattack.com/", "https://lwn.net/Articles/737940/", "http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5715", "https://github.com/IAIK/KAISER", "https://lwn.net/Articles/741878/", "https://gruss.cc/files/prefetch.pdf", "https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5aa90a84589282b87666f92b6c3c917c8080a9bf", "http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5754"], "cvelist": ["CVE-2017-5753", "CVE-2017-5753", "CVE-2017-5754", "CVE-2017-5754", "CVE-2017-5715", "CVE-2017-5715"], "lastseen": "2018-01-04T08:55:50", "history": [], "viewCount": 37, "enchantments": {"score": {"modified": "2018-01-04T08:55:50", "value": 5.2}}, "objectVersion": "1.4"}, "lastseen": "2018-01-04T08:55:50", "differentElements": ["description", "modified"], "edition": 2}, {"bulletin": {"id": "VU:584653", "hash": "6cedf41f4833d71abed16ffd406b19d0a3eb050fa9d3a57dcdad42580095e045", "type": "cert", "bulletinFamily": "info", "title": "CPU hardware vulnerable to side-channel attacks", "description": "### Overview\n\nCPU hardware implementations are vulnerable to side-channel attacks. These vulnerabilities are referred to as [Meltdown](<https://meltdownattack.com/>) and [Spectre](<https://spectreattack.com/>).\n\n### Description\n\nCPU hardware implementations are vulnerable to side-channel attacks referred to as [Meltdown](<https://meltdownattack.com/>) and [Spectre](<https://spectreattack.com/>). These attacks are described in detail by [Google Project Zero](<https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html>) and the Institute of Applied Information Processing and Communications (IAIK) at Graz University of Technology (TU Graz). The Linux kernel mitigations for this vulnerability are referred to as KAISER, and subsequently KPTI, which aim to improve separation of kernel and user memory pages. \n \n--- \n \n### Impact\n\nAn attacker able to execute code with user privileges can achieve various impacts, such as reading otherwise protected kernel memory and bypassing KASLR. \n \n--- \n \n### Solution\n\n**Replace CPU hardware**\n\nThe underlying vulnerability is primarily caused by CPU implementation optimization choices. Fully removing the vulnerability requires replacing vulnerable CPU hardware. \n \n--- \n \n**Apply updates** \n \nOperating system updates mitigate the underlying hardware vulnerability. \n \n--- \n \n### Vendor Information \n\nVendor| Status| Date Notified| Date Updated \n---|---|---|--- \nAMD| | -| 03 Jan 2018 \nApple| | -| 03 Jan 2018 \nArm| | -| 03 Jan 2018 \nGoogle| | -| 03 Jan 2018 \nIntel| | -| 03 Jan 2018 \nLinux Kernel| | -| 03 Jan 2018 \nMicrosoft| | -| 03 Jan 2018 \nMozilla| | -| 03 Jan 2018 \nIf you are a vendor and your product is affected, [let us know](<mailto:cert@cert.org?Subject=VU%23584653 Vendor Status Inquiry>).\n\n### CVSS Metrics \n\nGroup | Score | Vector \n---|---|--- \nBase | 1.5 | AV:L/AC:M/Au:S/C:P/I:N/A:N \nTemporal | 1.2 | E:POC/RL:OF/RC:C \nEnvironmental | 2.0 | CDP:ND/TD:H/CR:H/IR:ND/AR:ND \n \n### References\n\n * <https://meltdownattack.com/>\n * <https://spectreattack.com/>\n * <https://security.googleblog.com/2018/01/todays-cpu-vulnerability-what-you-need.html>\n * <https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html>\n * <https://www.us-cert.gov/ncas/current-activity/2018/01/03/Meltdown-and-Spectre-Side-Channel-Vulnerabilities>\n * <https://github.com/IAIK/KAISER>\n * <https://gruss.cc/files/kaiser.pdf>\n * <https://gruss.cc/files/prefetch.pdf>\n * <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5aa90a84589282b87666f92b6c3c917c8080a9bf>\n * <https://lwn.net/Articles/741878/>\n * <https://lwn.net/Articles/737940/>\n * <http://pythonsweetness.tumblr.com/post/169166980422/the-mysterious-case-of-the-linux-page-table>\n * <https://nakedsecurity.sophos.com/2018/01/03/fckwit-aka-kaiser-aka-kpti-intel-cpu-flaw-needs-low-level-os-patches/>\n\n### Credit\n\nThese issues were researched and reported by researchers at Google Project Zero and the Institute of Applied Information Processing and Communications (IAIK) at Graz University of Technology (TU Graz).\n\nThis document was written by Art Manion.\n\n### Other Information\n\n * CVE IDs: [CVE-2017-5753](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5753>) [CVE-2017-5715](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5715>) [CVE-2017-5754](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5754>)\n * Date Public: 03 Jan 2018\n * Date First Published: 03 Jan 2018\n * Date Last Updated: 04 Jan 2018\n * Document Revision: 28\n\n", "published": "2018-01-03T00:00:00", "modified": "2018-01-04T00:00:00", "cvss": {"score": 0.0, "vector": "NONE"}, "href": "https://www.kb.cert.org/vuls/id/584653", "reporter": "CERT", "references": ["https://nakedsecurity.sophos.com/2018/01/03/fckwit-aka-kaiser-aka-kpti-intel-cpu-flaw-needs-low-level-os-patches/", "https://security.googleblog.com/2018/01/todays-cpu-vulnerability-what-you-need.html", "https://www.us-cert.gov/ncas/current-activity/2018/01/03/Meltdown-and-Spectre-Side-Channel-Vulnerabilities", "https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html", "https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html", "http://pythonsweetness.tumblr.com/post/169166980422/the-mysterious-case-of-the-linux-page-table", "https://gruss.cc/files/kaiser.pdf", "https://meltdownattack.com/", "https://meltdownattack.com/", "https://meltdownattack.com/", "http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5753", "https://spectreattack.com/", "https://spectreattack.com/", "https://spectreattack.com/", "https://lwn.net/Articles/737940/", "http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5715", "https://github.com/IAIK/KAISER", "https://lwn.net/Articles/741878/", "https://gruss.cc/files/prefetch.pdf", "https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5aa90a84589282b87666f92b6c3c917c8080a9bf", "http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5754"], "cvelist": ["CVE-2017-5753", "CVE-2017-5753", "CVE-2017-5754", "CVE-2017-5754", "CVE-2017-5715", "CVE-2017-5715"], "lastseen": "2018-01-04T18:54:16", "history": [], "viewCount": 61, "enchantments": {"score": {"modified": "2018-01-04T18:54:16", "value": 5.2}}, "objectVersion": "1.4"}, "lastseen": "2018-01-04T18:54:16", "differentElements": ["cvelist", "description", "references"], "edition": 3}, {"bulletin": {"id": "VU:584653", "hash": "33769fd3ccbde7b823d38c23fef814184eb2d89a909bd55f4bcb1072cb34591d", "type": "cert", "bulletinFamily": "info", "title": "CPU hardware vulnerable to side-channel attacks", "description": "### Overview\n\nCPU hardware implementations are vulnerable to side-channel attacks. These vulnerabilities are referred to as [Meltdown](<https://meltdownattack.com/>) and [Spectre](<https://spectreattack.com/>).\n\n### Description\n\nCPU hardware implementations are vulnerable to side-channel attacks referred to as [Meltdown](<https://meltdownattack.com/>) and [Spectre](<https://spectreattack.com/>). These attacks are described in detail by [Google Project Zero](<https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html>) and the Institute of Applied Information Processing and Communications (IAIK) at Graz University of Technology (TU Graz). The issues are organized into three variants: \n\n * Variant 1 (CVE-2017-5753, [Spectre](<https://spectreattack.com/spectre.pdf>)): Bounds check bypass\n * Variant 2 (CVE-2017-5715, also [Spectre](<https://spectreattack.com/spectre.pdf>)): Branch target injection[](<https://spectreattack.com/spectre.pdf>)\n * Variant 3 (CVE-2017-5754, [Meltdown](<https://meltdownattack.com/meltdown.pdf>)): Rogue data cache load, memory access permission check performed after kernel memory read\n \nThese attacks are possible due to the interaction between operating system memory management and CPU implementation optimization choices. Different CPUs are impacted differently, for example, the speculative execution and cache implementation of many Intel CPUs allows an attacker to read kernel memory using variant 3 on un-protected operating systems. \n \nAttacks require the ability to execute code locally on a target system. Typically this requires a valid account or independent compromise of the target. Attacks using JavaScript in web browsers are possible. Multi-user and multi-tenant systems (including virtualized and cloud environments) likely face the greatest risk. Systems use to browse arbitrary web sites are also at risk. Single-user systems that do not readily provide a way for attackers to execute code locally face significantly lower risk. \n \nThe Linux kernel mitigations for Meltdown are referred to as KAISER, and subsequently KPTI, which aim to improve separation of kernel and user memory pages. \n \n--- \n \n### Impact\n\nAn attacker able to execute code with user privileges can achieve various impacts, such as reading otherwise protected kernel memory and bypassing KASLR. \n \n--- \n \n### Solution\n\n**Apply updates** \n \nOperating system and some application updates mitigate these attacks. \n \n--- \n \n### Vendor Information \n\nVendor| Status| Date Notified| Date Updated \n---|---|---|--- \nAMD| | -| 03 Jan 2018 \nApple| | -| 03 Jan 2018 \nArm| | -| 03 Jan 2018 \nGoogle| | -| 03 Jan 2018 \nIntel| | -| 03 Jan 2018 \nLinux Kernel| | -| 03 Jan 2018 \nMicrosoft| | -| 03 Jan 2018 \nMozilla| | -| 03 Jan 2018 \nIf you are a vendor and your product is affected, [let us know](<mailto:cert@cert.org?Subject=VU%23584653 Vendor Status Inquiry>).\n\n### CVSS Metrics \n\nGroup | Score | Vector \n---|---|--- \nBase | 1.5 | AV:L/AC:M/Au:S/C:P/I:N/A:N \nTemporal | 1.2 | E:POC/RL:OF/RC:C \nEnvironmental | 2.0 | CDP:ND/TD:H/CR:H/IR:ND/AR:ND \n \n### References\n\n * <https://meltdownattack.com/>\n * <https://meltdownattack.com/meltdown.pdf>\n * <https://spectreattack.com/>\n * <https://spectreattack.com/spectre.pdf>\n * <https://security.googleblog.com/2018/01/todays-cpu-vulnerability-what-you-need.html>\n * <https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html>\n * <https://cyber.wtf/2017/07/28/negative-result-reading-kernel-memory-from-user-mode/>\n * <https://www.us-cert.gov/ncas/current-activity/2018/01/03/Meltdown-and-Spectre-Side-Channel-Vulnerabilities>\n * <https://github.com/IAIK/KAISER>\n * <https://gruss.cc/files/kaiser.pdf>\n * <https://gruss.cc/files/prefetch.pdf>\n * <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5aa90a84589282b87666f92b6c3c917c8080a9bf>\n * <https://lkml.org/lkml/2017/12/27/2>\n * <https://lwn.net/Articles/741878/>\n * <https://lwn.net/Articles/737940/>\n * <https://lwn.net/Articles/742702/>\n * <http://pythonsweetness.tumblr.com/post/169166980422/the-mysterious-case-of-the-linux-page-table>\n * <https://nakedsecurity.sophos.com/2018/01/03/fckwit-aka-kaiser-aka-kpti-intel-cpu-flaw-needs-low-level-os-patches/>\n\n### Credit\n\nThese issues were researched and reported by researchers at Google Project Zero (Jann Horn) and the Institute of Applied Information Processing and Communications (IAIK) at Graz University of Technology (TU Graz) (Gruss et. al.). Anders Fogh is credited with [research](<https://cyber.wtf/2017/07/28/negative-result-reading-kernel-memory-from-user-mode/>) on variant 3.\n\nThis document was written by Art Manion.\n\n### Other Information\n\n * CVE IDs: [CVE-2017-5753](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5753>) [CVE-2017-5715](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5715>) [CVE-2017-5754](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5754>)\n * Date Public: 03 Jan 2018\n * Date First Published: 03 Jan 2018\n * Date Last Updated: 04 Jan 2018\n * Document Revision: 47\n\n", "published": "2018-01-03T00:00:00", "modified": "2018-01-04T00:00:00", "cvss": {"score": 0.0, "vector": "NONE"}, "href": "https://www.kb.cert.org/vuls/id/584653", "reporter": "CERT", "references": ["https://meltdownattack.com/meltdown.pdf", "https://meltdownattack.com/meltdown.pdf", "https://lwn.net/Articles/742702/", "https://nakedsecurity.sophos.com/2018/01/03/fckwit-aka-kaiser-aka-kpti-intel-cpu-flaw-needs-low-level-os-patches/", "https://lkml.org/lkml/2017/12/27/2", "https://security.googleblog.com/2018/01/todays-cpu-vulnerability-what-you-need.html", "https://www.us-cert.gov/ncas/current-activity/2018/01/03/Meltdown-and-Spectre-Side-Channel-Vulnerabilities", "https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html", "https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html", "http://pythonsweetness.tumblr.com/post/169166980422/the-mysterious-case-of-the-linux-page-table", "https://gruss.cc/files/kaiser.pdf", "https://meltdownattack.com/", "https://meltdownattack.com/", "https://meltdownattack.com/", "http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5753", "https://spectreattack.com/", "https://spectreattack.com/", "https://spectreattack.com/", "https://lwn.net/Articles/737940/", "http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5715", "https://github.com/IAIK/KAISER", "https://cyber.wtf/2017/07/28/negative-result-reading-kernel-memory-from-user-mode/", "https://cyber.wtf/2017/07/28/negative-result-reading-kernel-memory-from-user-mode/", "https://lwn.net/Articles/741878/", "https://gruss.cc/files/prefetch.pdf", "https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5aa90a84589282b87666f92b6c3c917c8080a9bf", "http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5754", "https://spectreattack.com/spectre.pdf", "https://spectreattack.com/spectre.pdf", "https://spectreattack.com/spectre.pdf", "https://spectreattack.com/spectre.pdf"], "cvelist": ["CVE-2017-5753", "CVE-2017-5753", "CVE-2017-5753", "CVE-2017-5754", "CVE-2017-5754", "CVE-2017-5754", "CVE-2017-5715", "CVE-2017-5715", "CVE-2017-5715"], "lastseen": "2018-01-04T22:54:15", "history": [], "viewCount": 68, "enchantments": {"score": {"modified": "2018-01-04T22:54:15", "value": 5.2}}, "objectVersion": "1.4"}, "lastseen": "2018-01-04T22:54:15", "differentElements": ["cvelist", "description", "references"], "edition": 4}, {"bulletin": {"id": "VU:584653", "hash": "87c740e1191106a5316a6b51454d418fe5d1b73c8f97a6fd82161877862ac8b1", "type": "cert", "bulletinFamily": "info", "title": "CPU hardware vulnerable to side-channel attacks", "description": "### Overview\n\nCPU hardware implementations are vulnerable to cache side-channel attacks. These vulnerabilities are referred to as [Meltdown](<https://meltdownattack.com/>) and [Spectre](<https://spectreattack.com/>).\n\n### Description\n\nCPU hardware implementations are vulnerable to side-channel attacks referred to as [Meltdown](<https://meltdownattack.com/>) and [Spectre](<https://spectreattack.com/>). Both Spectre and Meltdown take advantage of the ability to extract information from instructions that have executed on a CPU using the CPU cache as a side-channel. These attacks are described in detail by [Google Project Zero](<https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html>) and the Institute of Applied Information Processing and Communications (IAIK) at Graz University of Technology (TU Graz). The issues are organized into three variants: \n\n * Variant 1 (CVE-2017-5753, [Spectre](<https://spectreattack.com/spectre.pdf>)): Bounds check bypass\n * Variant 2 (CVE-2017-5715, also [Spectre](<https://spectreattack.com/spectre.pdf>)): Branch target injection[](<https://spectreattack.com/spectre.pdf>)\n * Variant 3 (CVE-2017-5754, [Meltdown](<https://meltdownattack.com/meltdown.pdf>)): Rogue data cache load, memory access permission check performed after kernel memory read\n \n**Spectre** \n \nSpectre attacks take advantage of a CPU's branch prediction capabilities. Modern CPUs include a feature called branch prediction, which speculatively executes instructions at a location that the CPU believes it will branch to. Such speculative execution helps to more fully utilize the parts of the CPU, minimizing the time waiting, and therefore improving performance. When a branch is successfully predicted, instructions will retire, which means the outcomes of the instructions such as register and memory writes will be committed. If a branch is mispredicted, the speculatively-executed instructions will be discarded, and the direct side-effects of the instructions are undone. What is not undone are the indirect side-effects, such as CPU cache changes. By measuring latency of memory access operations, the cache can be used to extract values from speculatively-executed instructions. \n \nWith Spectre variant 1 (CVE-2017-5753), the instructions after a conditional branch are speculatively executed as the result of a misprediction. With Spectre variant 2 (CVE-2017-5715), the instructions at a location determined by a branch target that is mispredicted. \n \nWith both variants of the Spectre attack, the impact is that a process may leak sensitive data to other processes on a system. Spectre may also allow one part of an application to access other parts of the same process memory space that would otherwise not be permitted. \n \n \n**Meltdown** \n \nMeltdown is related to the Spectre attack in that it also uses a cache side channel to access data that otherwise wouldn't be available. The main difference is that it leverages out-of-order execution capabilities in modern CPUs. Like speculative execution due to branch prediction, as used by Spectre, out-of-order execution on a CPU is a technique for ensuring fullest utilization of the CPU's parts. Although instructions may appear sequentially in the machine language, a CPU that supports out-of-order execution may execute instructions in a non-sequential manner, which can minimize the time that a CPU spends waiting. \n \nMeltdown leverages a flaw that has been demonstrated in Intel CPUs. Vulnerable CPUs allow memory reads in out-of-order instruction execution, and also contain a race condition between the raising of exceptions and the out-of-order instruction execution. The Meltdown attack reads a kernel memory value, which raises an exception because code running with user-space privileges are not permitted to directly read kernel memory. However, due to the race condition, out-of-order instructions following the faulting instruction may also execute. Even though instructions appear after the faulting instruction, out-of-order execution allows them to execute, using data retrieved from the instruction that raises the exception. By the time the exception is raised, some number of out-of-order instructions have executed. Although the raised exception causes the CPU to roll back the out-of-order instructions, the cache state is not reverted. This allows data from out-of-order instructions to persist beyond the point when the exception has been raised. \n \nThe impact of Meltdown is that a process running in user space is able to view the contents of kernel memory. Meltdown may also allow Spectre-like memory content leaking that does not cross the user/kernel privilege boundary. \n \n \nAttacks require the ability to execute code locally on a target system. Typically this requires a valid account or independent compromise of the target. Attacks using JavaScript in web browsers are possible. Multi-user and multi-tenant systems (including virtualized and cloud environments) likely face the greatest risk. Systems use to browse arbitrary web sites are also at risk. Single-user systems that do not readily provide a way for attackers to execute code locally face significantly lower risk. \n \nThe Linux kernel mitigations for Meltdown are referred to as KAISER, and subsequently KPTI, which aim to improve separation of kernel and user memory pages. Because the Spectre attacks do not cross user/kernel boundaries, the protections introduced with KAISER/KPTI do not add any protection against them. \n \n \nFor your convenience, here is a table that compares Spectre and Meltdown: \n \n| | **Spectre**| **Meltdown** \n---|---|--- \n**CPU mechanism for triggering**| Speculative execution from branch prediction| Out-of-order execution \n**Affected platforms**| CPUs that perform speculative execution from branch prediction| Intel x86 CPUs that allow memory reads in out-of-order instructions \n**Difficulty of successful attack**| High - Requires tailoring to the software environment of the victim process| Low - Kernel memory access exploit code is mostly universal \n**Impact**| Cross- and intra-process memory disclosure| Kernel memory disclosure to userspace \n**Software mitigations**| Unknown| Kernel page-table isolation ([KPTI](<https://en.wikipedia.org/wiki/Kernel_page-table_isolation>)) \n \n### Impact\n\nAn attacker able to execute code with user privileges can achieve various impacts. The Meltdown attack allows reading of kernel memory from userspace. This can result in privilege escalation, disclosure of sensitive information, or it can weaken kernel-level protections, such as KASLR. The Spectre attack can allow inter-process or intra-process data leaks. \n \n--- \n \n### Solution\n\n**Apply updates** \n \nOperating system and some application updates mitigate these attacks. \n \n--- \n \n### Vendor Information \n\nVendor| Status| Date Notified| Date Updated \n---|---|---|--- \nAMD| | -| 03 Jan 2018 \nApple| | -| 03 Jan 2018 \nArm| | -| 03 Jan 2018 \nGoogle| | -| 03 Jan 2018 \nIntel| | -| 03 Jan 2018 \nLinux Kernel| | -| 03 Jan 2018 \nMicrosoft| | -| 03 Jan 2018 \nMozilla| | -| 03 Jan 2018 \nIf you are a vendor and your product is affected, [let us know](<mailto:cert@cert.org?Subject=VU%23584653 Vendor Status Inquiry>).\n\n### CVSS Metrics \n\nGroup | Score | Vector \n---|---|--- \nBase | 4.4 | AV:L/AC:M/Au:S/C:C/I:N/A:N \nTemporal | 3.4 | E:POC/RL:OF/RC:C \nEnvironmental | 5.1 | CDP:ND/TD:H/CR:H/IR:ND/AR:ND \n \n### References\n\n * <https://meltdownattack.com/>\n * <https://meltdownattack.com/meltdown.pdf>\n * <https://spectreattack.com/>\n * <https://spectreattack.com/spectre.pdf>\n * <https://security.googleblog.com/2018/01/todays-cpu-vulnerability-what-you-need.html>\n * <https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html>\n * <https://cyber.wtf/2017/07/28/negative-result-reading-kernel-memory-from-user-mode/>\n * <https://www.us-cert.gov/ncas/current-activity/2018/01/03/Meltdown-and-Spectre-Side-Channel-Vulnerabilities>\n * <https://github.com/IAIK/KAISER>\n * <https://gruss.cc/files/kaiser.pdf>\n * <https://gruss.cc/files/prefetch.pdf>\n * <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5aa90a84589282b87666f92b6c3c917c8080a9bf>\n * <https://lkml.org/lkml/2017/12/27/2>\n * <https://lwn.net/Articles/741878/>\n * <https://lwn.net/Articles/737940/>\n * <https://lwn.net/Articles/742702/>\n * <http://pythonsweetness.tumblr.com/post/169166980422/the-mysterious-case-of-the-linux-page-table>\n * <https://nakedsecurity.sophos.com/2018/01/03/fckwit-aka-kaiser-aka-kpti-intel-cpu-flaw-needs-low-level-os-patches/>\n * <https://en.wikipedia.org/wiki/Kernel_page-table_isolation>\n\n### Credit\n\nThese issues were researched and reported by researchers at Google Project Zero (Jann Horn) and the Institute of Applied Information Processing and Communications (IAIK) at Graz University of Technology (TU Graz) (Gruss et. al.). Anders Fogh is credited with [research](<https://cyber.wtf/2017/07/28/negative-result-reading-kernel-memory-from-user-mode/>) on variant 3.\n\nThis document was written by Art Manion and Will Dormann.\n\n### Other Information\n\n * CVE IDs: [CVE-2017-5753](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5753>) [CVE-2017-5715](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5715>) [CVE-2017-5754](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5754>)\n * Date Public: 03 Jan 2018\n * Date First Published: 03 Jan 2018\n * Date Last Updated: 04 Jan 2018\n * Document Revision: 66\n\n", "published": "2018-01-03T00:00:00", "modified": "2018-01-04T00:00:00", "cvss": {"score": 0.0, "vector": "NONE"}, "href": "https://www.kb.cert.org/vuls/id/584653", "reporter": "CERT", "references": ["https://meltdownattack.com/meltdown.pdf", "https://meltdownattack.com/meltdown.pdf", "https://lwn.net/Articles/742702/", "https://nakedsecurity.sophos.com/2018/01/03/fckwit-aka-kaiser-aka-kpti-intel-cpu-flaw-needs-low-level-os-patches/", "https://lkml.org/lkml/2017/12/27/2", "https://security.googleblog.com/2018/01/todays-cpu-vulnerability-what-you-need.html", "https://www.us-cert.gov/ncas/current-activity/2018/01/03/Meltdown-and-Spectre-Side-Channel-Vulnerabilities", "https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html", "https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html", "http://pythonsweetness.tumblr.com/post/169166980422/the-mysterious-case-of-the-linux-page-table", "https://gruss.cc/files/kaiser.pdf", "https://meltdownattack.com/", "https://meltdownattack.com/", "https://meltdownattack.com/", "https://en.wikipedia.org/wiki/Kernel_page-table_isolation", "https://en.wikipedia.org/wiki/Kernel_page-table_isolation", "http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5753", "https://spectreattack.com/", "https://spectreattack.com/", "https://spectreattack.com/", "https://lwn.net/Articles/737940/", "http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5715", "https://github.com/IAIK/KAISER", "https://cyber.wtf/2017/07/28/negative-result-reading-kernel-memory-from-user-mode/", "https://cyber.wtf/2017/07/28/negative-result-reading-kernel-memory-from-user-mode/", "https://lwn.net/Articles/741878/", "https://gruss.cc/files/prefetch.pdf", "https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5aa90a84589282b87666f92b6c3c917c8080a9bf", "http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5754", "https://spectreattack.com/spectre.pdf", "https://spectreattack.com/spectre.pdf", "https://spectreattack.com/spectre.pdf", "https://spectreattack.com/spectre.pdf"], "cvelist": ["CVE-2017-5753", "CVE-2017-5753", "CVE-2017-5753", "CVE-2017-5753", "CVE-2017-5754", "CVE-2017-5754", "CVE-2017-5754", "CVE-2017-5715", "CVE-2017-5715", "CVE-2017-5715", "CVE-2017-5715"], "lastseen": "2018-01-05T04:54:20", "history": [], "viewCount": 70, "enchantments": {"score": {"modified": "2018-01-05T04:54:20", "value": 6.6}}, "objectVersion": "1.4"}, "lastseen": "2018-01-05T04:54:20", "differentElements": ["description", "references"], "edition": 5}, {"bulletin": {"id": "VU:584653", "hash": "c0f21a092dd2320d1a1c2635222521bc4b2fc95d137073696ced50f2741b3b5e", "type": "cert", "bulletinFamily": "info", "title": "CPU hardware vulnerable to side-channel attacks", "description": "### Overview\n\nCPU hardware implementations are vulnerable to cache side-channel attacks. These vulnerabilities are referred to as [Meltdown](<https://meltdownattack.com/>) and [Spectre](<https://spectreattack.com/>).\n\n### Description\n\nCPU hardware implementations are vulnerable to side-channel attacks referred to as [Meltdown](<https://meltdownattack.com/>) and [Spectre](<https://spectreattack.com/>). Both Spectre and Meltdown take advantage of the ability to extract information from instructions that have executed on a CPU using the CPU cache as a side-channel. These attacks are described in detail by [Google Project Zero](<https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html>), the Institute of Applied Information Processing and Communications (IAIK) at Graz University of Technology (TU Graz) and Anders Fogh. The issues are organized into three variants: \n\n * Variant 1 (CVE-2017-5753, [Spectre](<https://spectreattack.com/spectre.pdf>)): Bounds check bypass\n * Variant 2 (CVE-2017-5715, also [Spectre](<https://spectreattack.com/spectre.pdf>)): Branch target injection[](<https://spectreattack.com/spectre.pdf>)\n * Variant 3 (CVE-2017-5754, [Meltdown](<https://meltdownattack.com/meltdown.pdf>)): Rogue data cache load, memory access permission check performed after kernel memory read\n \n**Spectre** \n \nSpectre attacks take advantage of a CPU's branch prediction capabilities. Modern CPUs include a feature called branch prediction, which speculatively executes instructions at a location that the CPU believes it will branch to. Such speculative execution helps to more fully utilize the parts of the CPU, minimizing the time waiting, and therefore improving performance. When a branch is successfully predicted, instructions will retire, which means the outcomes of the instructions such as register and memory writes will be committed. If a branch is mispredicted, the speculatively-executed instructions will be discarded, and the direct side-effects of the instructions are undone. What is not undone are the indirect side-effects, such as CPU cache changes. By measuring latency of memory access operations, the cache can be used to extract values from speculatively-executed instructions. \n \nWith Spectre variant 1 (CVE-2017-5753), the instructions after a conditional branch are speculatively executed as the result of a misprediction. With Spectre variant 2 (CVE-2017-5715), the instructions at a location determined by a branch target that is mispredicted. \n \nWith both variants of the Spectre attack, the impact is that a process may leak sensitive data to other processes on a system. Spectre may also allow one part of an application to access other parts of the same process memory space that would otherwise not be permitted. \n \n**Meltdown** \n \nMeltdown is related to the Spectre attack in that it also uses a cache side channel to access data that otherwise wouldn't be available. The main difference is that it leverages out-of-order execution capabilities in modern CPUs. Like speculative execution due to branch prediction, as used by Spectre, out-of-order execution on a CPU is a technique for ensuring fullest utilization of the CPU's parts. Although instructions may appear sequentially in the machine language, a CPU that supports out-of-order execution may execute instructions in a non-sequential manner, which can minimize the time that a CPU spends waiting. \n \nMeltdown leverages a flaw that has been demonstrated in Intel CPUs. Vulnerable CPUs allow memory reads in out-of-order instruction execution, and also contain a race condition between the raising of exceptions and the out-of-order instruction execution. The Meltdown attack reads a kernel memory value, which raises an exception because code running with user-space privileges are not permitted to directly read kernel memory. However, due to the race condition, out-of-order instructions following the faulting instruction may also execute. Even though instructions appear after the faulting instruction, out-of-order execution allows them to execute, using data retrieved from the instruction that raises the exception. By the time the exception is raised, some number of out-of-order instructions have executed. Although the raised exception causes the CPU to roll back the out-of-order instructions, the cache state is not reverted. This allows data from out-of-order instructions to persist beyond the point when the exception has been raised. \n \nThe impact of Meltdown is that a process running in user space is able to view the contents of kernel memory. Meltdown may also allow Spectre-like memory content leaking that does not cross the user/kernel privilege boundary. \n \nThe Linux kernel mitigations for Meltdown are referred to as KAISER, and subsequently KPTI, which aim to improve separation of kernel and user memory pages. Because the Spectre attacks do not cross user/kernel boundaries, the protections introduced with KAISER/KPTI do not add any protection against them. \n \nThe following table compares Spectre and Meltdown. \n \n| | **Spectre**| **Meltdown** \n---|---|--- \n**CPU mechanism for triggering**| Speculative execution from branch prediction| Out-of-order execution \n**Affected platforms**| CPUs that perform speculative execution from branch prediction| Intel x86 CPUs that allow memory reads in out-of-order instructions \n**Difficulty of successful attack**| High - Requires tailoring to the software environment of the victim process| Low - Kernel memory access exploit code is mostly universal \n**Impact**| Cross- and intra-process memory disclosure| Kernel memory disclosure to userspace \n**Software mitigations**| Unknown| Kernel page-table isolation ([KPTI](<https://en.wikipedia.org/wiki/Kernel_page-table_isolation>)) \n \n### Impact\n\nAn attacker able to execute code with user privileges can achieve various impacts. The Meltdown attack allows reading of kernel memory from userspace. This can result in privilege escalation, disclosure of sensitive information, or it can weaken kernel-level protections, such as KASLR. The Spectre attack can allow inter-process or intra-process data leaks. \n \nTo execute code locally, an attacker would require a valid account or independent compromise of the target. Attacks using JavaScript in web browsers are possible. Multi-user and multi-tenant systems (including virtualized and cloud environments) likely face the greatest risk. Systems use to browse arbitrary web sites are also at risk. Single-user systems that do not readily provide a way for attackers to execute code locally face significantly lower risk. \n \n--- \n \n### Solution\n\n**Apply updates** \n \nOperating system and some application updates mitigate these attacks. \n \n--- \n \n### Vendor Information \n\nVendor| Status| Date Notified| Date Updated \n---|---|---|--- \nAMD| | -| 03 Jan 2018 \nApple| | -| 03 Jan 2018 \nArm| | -| 03 Jan 2018 \nGoogle| | -| 03 Jan 2018 \nIntel| | -| 03 Jan 2018 \nLinux Kernel| | -| 03 Jan 2018 \nMicrosoft| | -| 03 Jan 2018 \nMozilla| | -| 03 Jan 2018 \nIf you are a vendor and your product is affected, [let us know](<mailto:cert@cert.org?Subject=VU%23584653 Vendor Status Inquiry>).\n\n### CVSS Metrics \n\nGroup | Score | Vector \n---|---|--- \nBase | 4.4 | AV:L/AC:M/Au:S/C:C/I:N/A:N \nTemporal | 3.4 | E:POC/RL:OF/RC:C \nEnvironmental | 5.1 | CDP:ND/TD:H/CR:H/IR:ND/AR:ND \n \n### References\n\n * <https://meltdownattack.com/>\n * <https://meltdownattack.com/meltdown.pdf>\n * <https://spectreattack.com/>\n * <https://spectreattack.com/spectre.pdf>\n * <https://security.googleblog.com/2018/01/todays-cpu-vulnerability-what-you-need.html>\n * <https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html>\n * <https://cyber.wtf/2017/07/28/negative-result-reading-kernel-memory-from-user-mode/>\n * <https://github.com/IAIK/KAISER>\n * <https://gruss.cc/files/kaiser.pdf>\n * <https://gruss.cc/files/prefetch.pdf>\n * <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5aa90a84589282b87666f92b6c3c917c8080a9bf>\n * <https://lkml.org/lkml/2017/12/27/2>\n * <https://lwn.net/Articles/741878/>\n * <https://lwn.net/Articles/737940/>\n * <https://lwn.net/Articles/742702/>\n * <http://pythonsweetness.tumblr.com/post/169166980422/the-mysterious-case-of-the-linux-page-table>\n * <https://nakedsecurity.sophos.com/2018/01/03/fckwit-aka-kaiser-aka-kpti-intel-cpu-flaw-needs-low-level-os-patches/>\n * <https://en.wikipedia.org/wiki/Kernel_page-table_isolation>\n\n### Credit\n\nThese issues were researched and reported by researchers at Google Project Zero (Jann Horn) the Institute of Applied Information Processing and Communications (IAIK) at Graz University of Technology (Gruss et. al.), and Anders Fogh.\n\nThis document was written by Art Manion and Will Dormann.\n\n### Other Information\n\n * CVE IDs: [CVE-2017-5753](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5753>) [CVE-2017-5715](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5715>) [CVE-2017-5754](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5754>)\n * US-CERT Alert: [TA18-004A](<http://www.us-cert.gov/cas/techalerts/TA18-004A.html>)\n * Date Public: 03 Jan 2018\n * Date First Published: 03 Jan 2018\n * Date Last Updated: 04 Jan 2018\n * Document Revision: 82\n\n", "published": "2018-01-03T00:00:00", "modified": "2018-01-04T00:00:00", "cvss": {"score": 0.0, "vector": "NONE"}, "href": "https://www.kb.cert.org/vuls/id/584653", "reporter": "CERT", "references": ["https://meltdownattack.com/meltdown.pdf", "https://meltdownattack.com/meltdown.pdf", "https://lwn.net/Articles/742702/", "https://nakedsecurity.sophos.com/2018/01/03/fckwit-aka-kaiser-aka-kpti-intel-cpu-flaw-needs-low-level-os-patches/", "https://lkml.org/lkml/2017/12/27/2", "https://security.googleblog.com/2018/01/todays-cpu-vulnerability-what-you-need.html", "https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html", "https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html", "http://pythonsweetness.tumblr.com/post/169166980422/the-mysterious-case-of-the-linux-page-table", "https://gruss.cc/files/kaiser.pdf", "http://www.us-cert.gov/cas/techalerts/TA18-004A.html", "https://meltdownattack.com/", "https://meltdownattack.com/", "https://meltdownattack.com/", "https://en.wikipedia.org/wiki/Kernel_page-table_isolation", "https://en.wikipedia.org/wiki/Kernel_page-table_isolation", "http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5753", "https://spectreattack.com/", "https://spectreattack.com/", "https://spectreattack.com/", "https://lwn.net/Articles/737940/", "http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5715", "https://github.com/IAIK/KAISER", "https://cyber.wtf/2017/07/28/negative-result-reading-kernel-memory-from-user-mode/", "https://lwn.net/Articles/741878/", "https://gruss.cc/files/prefetch.pdf", "https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5aa90a84589282b87666f92b6c3c917c8080a9bf", "http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5754", "https://spectreattack.com/spectre.pdf", "https://spectreattack.com/spectre.pdf", "https://spectreattack.com/spectre.pdf", "https://spectreattack.com/spectre.pdf"], "cvelist": ["CVE-2017-5753", "CVE-2017-5753", "CVE-2017-5753", "CVE-2017-5753", "CVE-2017-5754", "CVE-2017-5754", "CVE-2017-5754", "CVE-2017-5715", "CVE-2017-5715", "CVE-2017-5715", "CVE-2017-5715"], "lastseen": "2018-01-05T06:56:03", "history": [], "viewCount": 71, "enchantments": {"score": {"modified": "2018-01-05T06:56:03", "value": 6.6}}, "objectVersion": "1.4"}, "lastseen": "2018-01-05T06:56:03", "differentElements": ["description", "modified"], "edition": 6}, {"bulletin": {"id": "VU:584653", "hash": "ee9803a3ac37051b266e636478114d68e0dda42580fcfa017c22cddbbf98950b", "type": "cert", "bulletinFamily": "info", "title": "CPU hardware vulnerable to side-channel attacks", "description": "### Overview\n\nCPU hardware implementations are vulnerable to cache side-channel attacks. These vulnerabilities are referred to as [Meltdown](<https://meltdownattack.com/>) and [Spectre](<https://spectreattack.com/>).\n\n### Description\n\n**Note: This Vulnerability Note is the product of ongoing analysis and represents our best knowledge as of the most recent revision. As a result, the content may change as our understanding of the issues develops.**\n\nCPU hardware implementations are vulnerable to side-channel attacks referred to as [Meltdown](<https://meltdownattack.com/>) and [Spectre](<https://spectreattack.com/>). Both Spectre and Meltdown take advantage of the ability to extract information from instructions that have executed on a CPU using the CPU cache as a side-channel. These attacks are described in detail by [Google Project Zero](<https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html>), the Institute of Applied Information Processing and Communications (IAIK) at Graz University of Technology (TU Graz) and Anders Fogh. The issues are organized into three variants: \n\n\n * Variant 1 (CVE-2017-5753, [Spectre](<https://spectreattack.com/spectre.pdf>)): Bounds check bypass\n * Variant 2 (CVE-2017-5715, also [Spectre](<https://spectreattack.com/spectre.pdf>)): Branch target injection[](<https://spectreattack.com/spectre.pdf>)\n * Variant 3 (CVE-2017-5754, [Meltdown](<https://meltdownattack.com/meltdown.pdf>)): Rogue data cache load, memory access permission check performed after kernel memory read\n \n**Spectre** \n \nSpectre attacks take advantage of a CPU's branch prediction capabilities. Modern CPUs include a feature called branch prediction, which speculatively executes instructions at a location that the CPU believes it will branch to. Such speculative execution helps to more fully utilize the parts of the CPU, minimizing the time waiting, and therefore improving performance. When a branch is successfully predicted, instructions will retire, which means the outcomes of the instructions such as register and memory writes will be committed. If a branch is mispredicted, the speculatively-executed instructions will be discarded, and the direct side-effects of the instructions are undone. What is not undone are the indirect side-effects, such as CPU cache changes. By measuring latency of memory access operations, the cache can be used to extract values from speculatively-executed instructions. \n \nWith Spectre variant 1 (CVE-2017-5753), the instructions after a conditional branch are speculatively executed as the result of a misprediction. With Spectre variant 2 (CVE-2017-5715), the instructions at a location determined by a branch target that is mispredicted. \n \nWith both variants of the Spectre attack, the impact is that a process may leak sensitive data to other processes on a system. Spectre may also allow one part of an application to access other parts of the same process memory space that would otherwise not be permitted. \n \n**Meltdown** \n \nMeltdown is related to the Spectre attack in that it also uses a cache side channel to access data that otherwise wouldn't be available. The main difference is that it leverages out-of-order execution capabilities in modern CPUs. Like speculative execution due to branch prediction, as used by Spectre, out-of-order execution on a CPU is a technique for ensuring fullest utilization of the CPU's parts. Although instructions may appear sequentially in the machine language, a CPU that supports out-of-order execution may execute instructions in a non-sequential manner, which can minimize the time that a CPU spends idle. \n \nMeltdown leverages insecure behavior that has been demonstrated in Intel CPUs and may affect CPUs from other vendors. Vulnerable CPUs allow memory reads in out-of-order instruction execution, and also contain a race condition between the raising of exceptions and the out-of-order instruction execution. The Meltdown attack reads a kernel memory value, which raises an exception because code running with user-space privileges are not permitted to directly read kernel memory. However, due to the race condition, out-of-order instructions following the faulting instruction may also execute. Even though instructions appear after the faulting instruction, out-of-order execution allows them to execute, using data retrieved from the instruction that raises the exception. By the time the exception is raised, some number of out-of-order instructions have executed. Although the raised exception causes the CPU to roll back the out-of-order instructions, the cache state is not reverted. This allows data from out-of-order instructions to persist beyond the point when the exception has been raised. \n \nThe impact of Meltdown is that a process running in user space is able to view the contents of kernel memory. Meltdown may also allow Spectre-like memory content leaking that does not cross the user/kernel privilege boundary. \n \nThe Linux kernel mitigations for Meltdown are referred to as KAISER, and subsequently KPTI, which aim to improve separation of kernel and user memory pages. Because the Spectre attacks do not cross user/kernel boundaries, the protections introduced with KAISER/KPTI do not add any protection against them. \n \nThe following table compares Spectre and Meltdown. \n \n| | **Spectre**| **Meltdown** \n---|---|--- \n**CPU mechanism for triggering**| Speculative execution from branch prediction| Out-of-order execution \n**Affected platforms**| CPUs that perform speculative execution from branch prediction| CPUs that allow memory reads in out-of-order instructions \n**Difficulty of successful attack**| High - Requires tailoring to the software environment of the victim process| Low - Kernel memory access exploit code is mostly universal \n**Impact**| Cross- and intra-process memory disclosure| Kernel memory disclosure to userspace \n**Software mitigations**| Unknown| Kernel page-table isolation ([KPTI](<https://en.wikipedia.org/wiki/Kernel_page-table_isolation>)) \n \n### Impact\n\nAn attacker able to execute code with user privileges can achieve various impacts. The Meltdown attack allows reading of kernel memory from userspace. This can result in privilege escalation, disclosure of sensitive information, or it can weaken kernel-level protections, such as KASLR. The Spectre attack can allow inter-process or intra-process data leaks. \n \nTo execute code locally, an attacker would require a valid account or independent compromise of the target. Attacks using JavaScript in web browsers are possible. Multi-user and multi-tenant systems (including virtualized and cloud environments) likely face the greatest risk. Systems use to browse arbitrary web sites are also at risk. Single-user systems that do not readily provide a way for attackers to execute code locally face significantly lower risk. \n \n--- \n \n### Solution\n\n**Apply updates** \n \nOperating system and some application updates mitigate these attacks. \n \n--- \n \n### Vendor Information \n\nVendor| Status| Date Notified| Date Updated \n---|---|---|--- \nAMD| | -| 03 Jan 2018 \nApple| | -| 04 Jan 2018 \nArm| | -| 03 Jan 2018 \nGoogle| | -| 03 Jan 2018 \nIntel| | -| 05 Jan 2018 \nLinux Kernel| | -| 04 Jan 2018 \nMicrosoft| | -| 05 Jan 2018 \nMozilla| | -| 03 Jan 2018 \nIf you are a vendor and your product is affected, [let us know](<mailto:cert@cert.org?Subject=VU%23584653 Vendor Status Inquiry>).\n\n### CVSS Metrics \n\nGroup | Score | Vector \n---|---|--- \nBase | 4.4 | AV:L/AC:M/Au:S/C:C/I:N/A:N \nTemporal | 3.4 | E:POC/RL:OF/RC:C \nEnvironmental | 5.1 | CDP:ND/TD:H/CR:H/IR:ND/AR:ND \n \n### References\n\n * <https://meltdownattack.com/>\n * <https://meltdownattack.com/meltdown.pdf>\n * <https://spectreattack.com/>\n * <https://spectreattack.com/spectre.pdf>\n * <https://security.googleblog.com/2018/01/todays-cpu-vulnerability-what-you-need.html>\n * <https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html>\n * <https://cyber.wtf/2017/07/28/negative-result-reading-kernel-memory-from-user-mode/>\n * <https://github.com/IAIK/KAISER>\n * <https://gruss.cc/files/kaiser.pdf>\n * <https://gruss.cc/files/prefetch.pdf>\n * <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5aa90a84589282b87666f92b6c3c917c8080a9bf>\n * <https://lkml.org/lkml/2017/12/27/2>\n * <https://lwn.net/Articles/741878/>\n * <https://lwn.net/Articles/737940/>\n * <https://lwn.net/Articles/742702/>\n * <http://pythonsweetness.tumblr.com/post/169166980422/the-mysterious-case-of-the-linux-page-table>\n * <https://nakedsecurity.sophos.com/2018/01/03/fckwit-aka-kaiser-aka-kpti-intel-cpu-flaw-needs-low-level-os-patches/>\n * <https://en.wikipedia.org/wiki/Kernel_page-table_isolation>\n\n### Credit\n\nThese issues were researched and reported by researchers at Google Project Zero (Jann Horn) the Institute of Applied Information Processing and Communications (IAIK) at Graz University of Technology (Gruss et. al.), and Anders Fogh.\n\nThis document was written by Art Manion and Will Dormann.\n\n### Other Information\n\n * CVE IDs: [CVE-2017-5753](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5753>) [CVE-2017-5715](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5715>) [CVE-2017-5754](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5754>)\n * US-CERT Alert: [TA18-004A](<http://www.us-cert.gov/cas/techalerts/TA18-004A.html>)\n * Date Public: 03 Jan 2018\n * Date First Published: 03 Jan 2018\n * Date Last Updated: 05 Jan 2018\n * Document Revision: 92\n\n", "published": "2018-01-03T00:00:00", "modified": "2018-01-05T00:00:00", "cvss": {"score": 0.0, "vector": "NONE"}, "href": "https://www.kb.cert.org/vuls/id/584653", "reporter": "CERT", "references": ["https://meltdownattack.com/meltdown.pdf", "https://meltdownattack.com/meltdown.pdf", "https://lwn.net/Articles/742702/", "https://nakedsecurity.sophos.com/2018/01/03/fckwit-aka-kaiser-aka-kpti-intel-cpu-flaw-needs-low-level-os-patches/", "https://lkml.org/lkml/2017/12/27/2", "https://security.googleblog.com/2018/01/todays-cpu-vulnerability-what-you-need.html", "https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html", "https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html", "http://pythonsweetness.tumblr.com/post/169166980422/the-mysterious-case-of-the-linux-page-table", "https://gruss.cc/files/kaiser.pdf", "http://www.us-cert.gov/cas/techalerts/TA18-004A.html", "https://meltdownattack.com/", "https://meltdownattack.com/", "https://meltdownattack.com/", "https://en.wikipedia.org/wiki/Kernel_page-table_isolation", "https://en.wikipedia.org/wiki/Kernel_page-table_isolation", "http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5753", "https://spectreattack.com/", "https://spectreattack.com/", "https://spectreattack.com/", "https://lwn.net/Articles/737940/", "http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5715", "https://github.com/IAIK/KAISER", "https://cyber.wtf/2017/07/28/negative-result-reading-kernel-memory-from-user-mode/", "https://lwn.net/Articles/741878/", "https://gruss.cc/files/prefetch.pdf", "https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5aa90a84589282b87666f92b6c3c917c8080a9bf", "http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5754", "https://spectreattack.com/spectre.pdf", "https://spectreattack.com/spectre.pdf", "https://spectreattack.com/spectre.pdf", "https://spectreattack.com/spectre.pdf"], "cvelist": ["CVE-2017-5753", "CVE-2017-5753", "CVE-2017-5753", "CVE-2017-5753", "CVE-2017-5754", "CVE-2017-5754", "CVE-2017-5754", "CVE-2017-5715", "CVE-2017-5715", "CVE-2017-5715", "CVE-2017-5715"], "lastseen": "2018-01-05T17:09:08", "history": [], "viewCount": 95, "enchantments": {"score": {"modified": "2018-01-05T17:09:08", "value": 6.6}}, "objectVersion": "1.4"}, "lastseen": "2018-01-05T17:09:08", "differentElements": ["description", "references"], "edition": 7}, {"bulletin": {"id": "VU:584653", "hash": "6b58bab9f508c64a32378e87c892f0a521fc87f3333dcce6ce409f5b383c198d", "type": "cert", "bulletinFamily": "info", "title": "CPU hardware vulnerable to side-channel attacks", "description": "### Overview\n\nCPU hardware implementations are vulnerable to cache side-channel attacks. These vulnerabilities are referred to as [Meltdown](<https://meltdownattack.com/>) and [Spectre](<https://spectreattack.com/>).\n\n### Description\n\n**Note: This Vulnerability Note is the product of ongoing analysis and represents our best knowledge as of the most recent revision. As a result, the content may change as our understanding of the issues develops.**\n\nCPU hardware implementations are vulnerable to side-channel attacks referred to as [Meltdown](<https://meltdownattack.com/>) and [Spectre](<https://spectreattack.com/>). Both Spectre and Meltdown take advantage of the ability to extract information from instructions that have executed on a CPU using the CPU cache as a side-channel. These attacks are described in detail by [Google Project Zero](<https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html>), the Institute of Applied Information Processing and Communications (IAIK) at Graz University of Technology (TU Graz) and Anders Fogh. The issues are organized into three variants: \n\n\n * Variant 1 (CVE-2017-5753, [Spectre](<https://spectreattack.com/spectre.pdf>)): Bounds check bypass\n * Variant 2 (CVE-2017-5715, also [Spectre](<https://spectreattack.com/spectre.pdf>)): Branch target injection[](<https://spectreattack.com/spectre.pdf>)\n * Variant 3 (CVE-2017-5754, [Meltdown](<https://meltdownattack.com/meltdown.pdf>)): Rogue data cache load, memory access permission check performed after kernel memory read\n \n**Spectre** \n \nSpectre attacks take advantage of a CPU's branch prediction capabilities. Modern CPUs include a feature called branch prediction, which speculatively executes instructions at a location that the CPU believes it will branch to. Such speculative execution helps to more fully utilize the parts of the CPU, minimizing the time waiting, and therefore improving performance. When a branch is successfully predicted, instructions will retire, which means the outcomes of the instructions such as register and memory writes will be committed. If a branch is mispredicted, the speculatively-executed instructions will be discarded, and the direct side-effects of the instructions are undone. What is not undone are the indirect side-effects, such as CPU cache changes. By measuring latency of memory access operations, the cache can be used to extract values from speculatively-executed instructions. \n \nWith Spectre variant 1 (CVE-2017-5753), the instructions after a conditional branch are speculatively executed as the result of a misprediction. With Spectre variant 2 (CVE-2017-5715), the instructions at a location determined by a branch target that is mispredicted. \n \nWith both variants of the Spectre attack, the impact is that a process may leak sensitive data to other processes on a system. Spectre may also allow one part of an application to access other parts of the same process memory space that would otherwise not be permitted. \n \n**Meltdown** \n \nMeltdown is related to the Spectre attack in that it also uses a cache side channel to access data that otherwise wouldn't be available. The main difference is that it leverages out-of-order execution capabilities in modern CPUs. Like speculative execution due to branch prediction, as used by Spectre, out-of-order execution on a CPU is a technique for ensuring fullest utilization of the CPU's parts. Although instructions may appear sequentially in the machine language, a CPU that supports out-of-order execution may execute instructions in a non-sequential manner, which can minimize the time that a CPU spends idle. \n \nMeltdown leverages insecure behavior that has been demonstrated in Intel CPUs and may affect CPUs from other vendors. Vulnerable CPUs allow memory reads in out-of-order instruction execution, and also contain a race condition between the raising of exceptions and the out-of-order instruction execution. The Meltdown attack reads a kernel memory value, which raises an exception because code running with user-space privileges are not permitted to directly read kernel memory. However, due to the race condition, out-of-order instructions following the faulting instruction may also execute. Even though instructions appear after the faulting instruction, out-of-order execution allows them to execute, using data retrieved from the instruction that raises the exception. By the time the exception is raised, some number of out-of-order instructions have executed. Although the raised exception causes the CPU to roll back the out-of-order instructions, the cache state is not reverted. This allows data from out-of-order instructions to persist beyond the point when the exception has been raised. \n \nThe impact of Meltdown is that a process running in user space is able to view the contents of kernel memory. Meltdown may also allow Spectre-like memory content leaking that does not cross the user/kernel privilege boundary. \n \nThe Linux kernel mitigations for Meltdown are referred to as KAISER, and subsequently KPTI, which aim to improve separation of kernel and user memory pages. Because the Spectre attacks do not cross user/kernel boundaries, the protections introduced with KAISER/KPTI do not add any protection against them. \n \nThe following table compares Spectre and Meltdown. \n \n| | **Spectre**| **Meltdown** \n---|---|--- \n**CPU mechanism for triggering**| Speculative execution from branch prediction| Out-of-order execution \n**Affected platforms**| CPUs that perform speculative execution from branch prediction| CPUs that allow memory reads in out-of-order instructions \n**Difficulty of successful attack**| High - Requires tailoring to the software environment of the victim process| Low - Kernel memory access exploit code is mostly universal \n**Impact**| Cross- and intra-process memory disclosure| Kernel memory disclosure to userspace \n**Software mitigations**| Indirect Branch Restricted Speculation ([IBRS](<https://lkml.org/lkml/2018/1/4/615>)) \n**Note: **This software mitigation also requires CPU microcode updates and it only mitigates Spectre variant 2| Kernel page-table isolation ([KPTI](<https://en.wikipedia.org/wiki/Kernel_page-table_isolation>)) \n \n### Impact\n\nAn attacker able to execute code with user privileges can achieve various impacts. The Meltdown attack allows reading of kernel memory from userspace. This can result in privilege escalation, disclosure of sensitive information, or it can weaken kernel-level protections, such as KASLR. The Spectre attack can allow inter-process or intra-process data leaks. \n \nTo execute code locally, an attacker would require a valid account or independent compromise of the target. Attacks using JavaScript in web browsers are possible. Multi-user and multi-tenant systems (including virtualized and cloud environments) likely face the greatest risk. Systems use to browse arbitrary web sites are also at risk. Single-user systems that do not readily provide a way for attackers to execute code locally face significantly lower risk. \n \n--- \n \n### Solution\n\n**Apply updates** \n \nOperating system, CPU microcode updates, and some application updates mitigate these attacks. \n \n--- \n \n### Vendor Information \n\nVendor| Status| Date Notified| Date Updated \n---|---|---|--- \nAmazon| | -| 05 Jan 2018 \nAMD| | -| 03 Jan 2018 \nApple| | -| 04 Jan 2018 \nArm| | -| 03 Jan 2018 \nCentOS| | -| 05 Jan 2018 \nCitrix| | -| 05 Jan 2018 \nDebian GNU/Linux| | -| 05 Jan 2018 \nFedora Project| | -| 05 Jan 2018 \nFortinet, Inc.| | -| 05 Jan 2018 \nGoogle| | -| 03 Jan 2018 \nIBM Corporation| | -| 05 Jan 2018 \nIntel| | -| 05 Jan 2018 \nLinux Kernel| | -| 04 Jan 2018 \nMicrosoft| | -| 05 Jan 2018 \nMozilla| | -| 03 Jan 2018 \nIf you are a vendor and your product is affected, [let us know](<mailto:cert@cert.org?Subject=VU%23584653 Vendor Status Inquiry>). \n \n\n\n### CVSS Metrics \n\nGroup | Score | Vector \n---|---|--- \nBase | 4.4 | AV:L/AC:M/Au:S/C:C/I:N/A:N \nTemporal | 3.4 | E:POC/RL:OF/RC:C \nEnvironmental | 5.1 | CDP:ND/TD:H/CR:H/IR:ND/AR:ND \n \n### References\n\n * <https://meltdownattack.com/>\n * <https://meltdownattack.com/meltdown.pdf>\n * <https://spectreattack.com/>\n * <https://spectreattack.com/spectre.pdf>\n * <https://security.googleblog.com/2018/01/todays-cpu-vulnerability-what-you-need.html>\n * <https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html>\n * <https://cyber.wtf/2017/07/28/negative-result-reading-kernel-memory-from-user-mode/>\n * <https://github.com/IAIK/KAISER>\n * <https://gruss.cc/files/kaiser.pdf>\n * <https://gruss.cc/files/prefetch.pdf>\n * <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5aa90a84589282b87666f92b6c3c917c8080a9bf>\n * <https://lkml.org/lkml/2017/12/27/2>\n * <https://lkml.org/lkml/2018/1/4/615>\n * <https://lwn.net/Articles/741878/>\n * <https://lwn.net/Articles/737940/>\n * <https://lwn.net/Articles/742702/>\n * <http://pythonsweetness.tumblr.com/post/169166980422/the-mysterious-case-of-the-linux-page-table>\n * <https://nakedsecurity.sophos.com/2018/01/03/fckwit-aka-kaiser-aka-kpti-intel-cpu-flaw-needs-low-level-os-patches/>\n * <https://en.wikipedia.org/wiki/Kernel_page-table_isolation>\n\n### Credit\n\nThese issues were researched and reported by researchers at Google Project Zero (Jann Horn) the Institute of Applied Information Processing and Communications (IAIK) at Graz University of Technology (Gruss et. al.), and Anders Fogh.\n\nThis document was written by Art Manion and Will Dormann.\n\n### Other Information\n\n * CVE IDs: [CVE-2017-5753](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5753>) [CVE-2017-5715](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5715>) [CVE-2017-5754](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5754>)\n * US-CERT Alert: [TA18-004A](<http://www.us-cert.gov/cas/techalerts/TA18-004A.html>)\n * Date Public: 03 Jan 2018\n * Date First Published: 03 Jan 2018\n * Date Last Updated: 05 Jan 2018\n * Document Revision: 122\n\n", "published": "2018-01-03T00:00:00", "modified": "2018-01-05T00:00:00", "cvss": {"score": 0.0, "vector": "NONE"}, "href": "https://www.kb.cert.org/vuls/id/584653", "reporter": "CERT", "references": ["https://meltdownattack.com/meltdown.pdf", "https://meltdownattack.com/meltdown.pdf", "https://lwn.net/Articles/742702/", "https://nakedsecurity.sophos.com/2018/01/03/fckwit-aka-kaiser-aka-kpti-intel-cpu-flaw-needs-low-level-os-patches/", "https://lkml.org/lkml/2017/12/27/2", "https://security.googleblog.com/2018/01/todays-cpu-vulnerability-what-you-need.html", "https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html", "https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html", "http://pythonsweetness.tumblr.com/post/169166980422/the-mysterious-case-of-the-linux-page-table", "https://gruss.cc/files/kaiser.pdf", "http://www.us-cert.gov/cas/techalerts/TA18-004A.html", "https://meltdownattack.com/", "https://meltdownattack.com/", "https://meltdownattack.com/", "https://en.wikipedia.org/wiki/Kernel_page-table_isolation", "https://en.wikipedia.org/wiki/Kernel_page-table_isolation", "http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5753", "https://spectreattack.com/", "https://spectreattack.com/", "https://spectreattack.com/", "https://lwn.net/Articles/737940/", "http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5715", "https://lkml.org/lkml/2018/1/4/615", "https://lkml.org/lkml/2018/1/4/615", "https://github.com/IAIK/KAISER", "https://cyber.wtf/2017/07/28/negative-result-reading-kernel-memory-from-user-mode/", "https://lwn.net/Articles/741878/", "https://gruss.cc/files/prefetch.pdf", "https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5aa90a84589282b87666f92b6c3c917c8080a9bf", "http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5754", "https://spectreattack.com/spectre.pdf", "https://spectreattack.com/spectre.pdf", "https://spectreattack.com/spectre.pdf", "https://spectreattack.com/spectre.pdf"], "cvelist": ["CVE-2017-5753", "CVE-2017-5753", "CVE-2017-5753", "CVE-2017-5753", "CVE-2017-5754", "CVE-2017-5754", "CVE-2017-5754", "CVE-2017-5715", "CVE-2017-5715", "CVE-2017-5715", "CVE-2017-5715"], "lastseen": "2018-01-05T22:55:36", "history": [], "viewCount": 109, "enchantments": {"score": {"modified": "2018-01-05T22:55:36", "value": 6.6}}, "objectVersion": "1.4"}, "lastseen": "2018-01-05T22:55:36", "differentElements": ["description", "references"], "edition": 8}, {"bulletin": {"id": "VU:584653", "hash": "fa4dab0097f407ca784d6956ae2fd75c3114f9b2272069e67c3e509a437b6d44", "type": "cert", "bulletinFamily": "info", "title": "CPU hardware vulnerable to side-channel attacks", "description": "### Overview\n\nCPU hardware implementations are vulnerable to cache side-channel attacks. These vulnerabilities are referred to as [Meltdown](<https://meltdownattack.com/>) and [Spectre](<https://spectreattack.com/>).\n\n### Description\n\n**Note: This Vulnerability Note is the product of ongoing analysis and represents our best knowledge as of the most recent revision. As a result, the content may change as our understanding of the issues develops.**\n\nCPU hardware implementations are vulnerable to side-channel attacks referred to as [Meltdown](<https://meltdownattack.com/>) and [Spectre](<https://spectreattack.com/>). Both Spectre and Meltdown take advantage of the ability to extract information from instructions that have executed on a CPU using the CPU cache as a side-channel. These attacks are described in detail by [Google Project Zero](<https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html>), the Institute of Applied Information Processing and Communications (IAIK) at Graz University of Technology (TU Graz) and Anders Fogh. The issues are organized into three variants: \n\n\n * Variant 1 (CVE-2017-5753, [Spectre](<https://spectreattack.com/spectre.pdf>)): Bounds check bypass\n * Variant 2 (CVE-2017-5715, also [Spectre](<https://spectreattack.com/spectre.pdf>)): Branch target injection[](<https://spectreattack.com/spectre.pdf>)\n * Variant 3 (CVE-2017-5754, [Meltdown](<https://meltdownattack.com/meltdown.pdf>)): Rogue data cache load, memory access permission check performed after kernel memory read\n \n**Spectre** \n \nSpectre attacks take advantage of a CPU's branch prediction capabilities. Modern CPUs include a feature called branch prediction, which speculatively executes instructions at a location that the CPU believes it will branch to. Such speculative execution helps to more fully utilize the parts of the CPU, minimizing the time waiting, and therefore improving performance. When a branch is successfully predicted, instructions will retire, which means the outcomes of the instructions such as register and memory writes will be committed. If a branch is mispredicted, the speculatively-executed instructions will be discarded, and the direct side-effects of the instructions are undone. What is not undone are the indirect side-effects, such as CPU cache changes. By measuring latency of memory access operations, the cache can be used to extract values from speculatively-executed instructions. \n \nWith Spectre variant 1 (CVE-2017-5753), the instructions after a conditional branch are speculatively executed as the result of a misprediction. With Spectre variant 2 (CVE-2017-5715), the instructions at a location determined by a branch target that is mispredicted. \n \nWith both variants of the Spectre attack, the impact is that a process may leak sensitive data to other processes on a system. Spectre may also allow one part of an application to access other parts of the same process memory space that would otherwise not be permitted. \n \n**Meltdown** \n \nMeltdown is related to the Spectre attack in that it also uses a cache side channel to access data that otherwise wouldn't be available. The main difference is that it leverages out-of-order execution capabilities in modern CPUs. Like speculative execution due to branch prediction, as used by Spectre, out-of-order execution on a CPU is a technique for ensuring fullest utilization of the CPU's parts. Although instructions may appear sequentially in the machine language, a CPU that supports out-of-order execution may execute instructions in a non-sequential manner, which can minimize the time that a CPU spends idle. \n \nMeltdown leverages insecure behavior that has been demonstrated in Intel CPUs and may affect CPUs from other vendors. Vulnerable CPUs allow memory reads in out-of-order instruction execution, and also contain a race condition between the raising of exceptions and the out-of-order instruction execution. The Meltdown attack reads a kernel memory value, which raises an exception because code running with user-space privileges are not permitted to directly read kernel memory. However, due to the race condition, out-of-order instructions following the faulting instruction may also execute. Even though instructions appear after the faulting instruction, out-of-order execution allows them to execute, using data retrieved from the instruction that raises the exception. By the time the exception is raised, some number of out-of-order instructions have executed. Although the raised exception causes the CPU to roll back the out-of-order instructions, the cache state is not reverted. This allows data from out-of-order instructions to persist beyond the point when the exception has been raised. \n \nThe impact of Meltdown is that a process running in user space is able to view the contents of kernel memory. Meltdown may also allow Spectre-like memory content leaking that does not cross the user/kernel privilege boundary. \n \nThe Linux kernel mitigations for Meltdown are referred to as KAISER, and subsequently KPTI, which aim to improve separation of kernel and user memory pages. Because the Spectre attacks do not cross user/kernel boundaries, the protections introduced with KAISER/KPTI do not add any protection against them. \n \nThe following table compares Spectre and Meltdown. \n \n| | **Spectre**| **Meltdown** \n---|---|--- \n**CPU mechanism for triggering**| Speculative execution from branch prediction| Out-of-order execution \n**Affected platforms**| CPUs that perform speculative execution from branch prediction| CPUs that allow memory reads in out-of-order instructions \n**Difficulty of successful attack**| High - Requires tailoring to the software environment of the victim process| Low - Kernel memory access exploit code is mostly universal \n**Impact**| Cross- and intra-process memory disclosure| Kernel memory disclosure to userspace \n**Software mitigations**| Indirect Branch Restricted Speculation ([IBRS](<https://lkml.org/lkml/2018/1/4/615>)) \n**Note: **This software mitigation also requires CPU microcode updates and it only mitigates Spectre variant 2| Kernel page-table isolation ([KPTI](<https://en.wikipedia.org/wiki/Kernel_page-table_isolation>)) \n \n### Impact\n\nAn attacker able to execute code with user privileges can achieve various impacts. The Meltdown attack allows reading of kernel memory from userspace. This can result in privilege escalation, disclosure of sensitive information, or it can weaken kernel-level protections, such as KASLR. The Spectre attack can allow inter-process or intra-process data leaks. \n \nTo execute code locally, an attacker would require a valid account or independent compromise of the target. Attacks using JavaScript in web browsers are possible. Multi-user and multi-tenant systems (including virtualized and cloud environments) likely face the greatest risk. Systems used to browse arbitrary web sites are also at risk. Single-user systems that do not readily provide a way for attackers to execute code locally face significantly lower risk. \n \n--- \n \n### Solution\n\n**Apply updates** \n \nOperating system, CPU microcode updates, and some application updates mitigate these attacks. \n \n--- \n \n### Vendor Information \n\nVendor| Status| Date Notified| Date Updated \n---|---|---|--- \nAmazon| | -| 05 Jan 2018 \nAMD| | -| 03 Jan 2018 \nAndroid Open Source Project| | -| 05 Jan 2018 \nApple| | -| 04 Jan 2018 \nArm| | -| 03 Jan 2018 \nCentOS| | -| 05 Jan 2018 \nCisco| | -| 05 Jan 2018 \nCitrix| | -| 05 Jan 2018 \nDebian GNU/Linux| | -| 05 Jan 2018 \nFedora Project| | -| 05 Jan 2018 \nFortinet, Inc.| | -| 05 Jan 2018 \nFreeBSD Project| | -| 05 Jan 2018 \nGoogle| | -| 03 Jan 2018 \nIBM Corporation| | -| 05 Jan 2018 \nIntel| | -| 05 Jan 2018 \nIf you are a vendor and your product is affected, [let us know](<mailto:cert@cert.org?Subject=VU%23584653 Vendor Status Inquiry>). \n \n\n\n### CVSS Metrics \n\nGroup | Score | Vector \n---|---|--- \nBase | 4.4 | AV:L/AC:M/Au:S/C:C/I:N/A:N \nTemporal | 3.4 | E:POC/RL:OF/RC:C \nEnvironmental | 5.1 | CDP:ND/TD:H/CR:H/IR:ND/AR:ND \n \n### References\n\n * <https://meltdownattack.com/>\n * <https://meltdownattack.com/meltdown.pdf>\n * <https://spectreattack.com/>\n * <https://spectreattack.com/spectre.pdf>\n * <https://security.googleblog.com/2018/01/todays-cpu-vulnerability-what-you-need.html>\n * <https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html>\n * <https://cyber.wtf/2017/07/28/negative-result-reading-kernel-memory-from-user-mode/>\n * <https://github.com/IAIK/KAISER>\n * <https://gruss.cc/files/kaiser.pdf>\n * <https://gruss.cc/files/prefetch.pdf>\n * <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5aa90a84589282b87666f92b6c3c917c8080a9bf>\n * <https://lkml.org/lkml/2017/12/27/2>\n * <https://lkml.org/lkml/2018/1/4/615>\n * <https://lwn.net/Articles/741878/>\n * <https://lwn.net/Articles/737940/>\n * <https://lwn.net/Articles/742702/>\n * <http://pythonsweetness.tumblr.com/post/169166980422/the-mysterious-case-of-the-linux-page-table>\n * <https://nakedsecurity.sophos.com/2018/01/03/fckwit-aka-kaiser-aka-kpti-intel-cpu-flaw-needs-low-level-os-patches/>\n * <https://en.wikipedia.org/wiki/Kernel_page-table_isolation>\n * <https://chrisam.net/2018/01/04/speculative-execution-side-channel-vulnerabilities-vendor-published-info/>\n\n### Credit\n\nThese issues were researched and reported by researchers at Google Project Zero (Jann Horn) the Institute of Applied Information Processing and Communications (IAIK) at Graz University of Technology (Gruss et. al.), and Anders Fogh.\n\nThis document was written by Art Manion and Will Dormann.\n\n### Other Information\n\n * CVE IDs: [CVE-2017-5753](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5753>) [CVE-2017-5715](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5715>) [CVE-2017-5754](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5754>)\n * US-CERT Alert: [TA18-004A](<http://www.us-cert.gov/cas/techalerts/TA18-004A.html>)\n * Date Public: 03 Jan 2018\n * Date First Published: 03 Jan 2018\n * Date Last Updated: 05 Jan 2018\n * Document Revision: 145\n\n", "published": "2018-01-03T00:00:00", "modified": "2018-01-05T00:00:00", "cvss": {"score": 0.0, "vector": "NONE"}, "href": "https://www.kb.cert.org/vuls/id/584653", "reporter": "CERT", "references": ["https://meltdownattack.com/meltdown.pdf", "https://meltdownattack.com/meltdown.pdf", "https://lwn.net/Articles/742702/", "https://nakedsecurity.sophos.com/2018/01/03/fckwit-aka-kaiser-aka-kpti-intel-cpu-flaw-needs-low-level-os-patches/", "https://lkml.org/lkml/2017/12/27/2", "https://security.googleblog.com/2018/01/todays-cpu-vulnerability-what-you-need.html", "https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html", "https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html", "http://pythonsweetness.tumblr.com/post/169166980422/the-mysterious-case-of-the-linux-page-table", "https://gruss.cc/files/kaiser.pdf", "http://www.us-cert.gov/cas/techalerts/TA18-004A.html", "https://chrisam.net/2018/01/04/speculative-execution-side-channel-vulnerabilities-vendor-published-info/", "https://meltdownattack.com/", "https://meltdownattack.com/", "https://meltdownattack.com/", "https://en.wikipedia.org/wiki/Kernel_page-table_isolation", "https://en.wikipedia.org/wiki/Kernel_page-table_isolation", "http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5753", "https://spectreattack.com/", "https://spectreattack.com/", "https://spectreattack.com/", "https://lwn.net/Articles/737940/", "http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5715", "https://lkml.org/lkml/2018/1/4/615", "https://lkml.org/lkml/2018/1/4/615", "https://github.com/IAIK/KAISER", "https://cyber.wtf/2017/07/28/negative-result-reading-kernel-memory-from-user-mode/", "https://lwn.net/Articles/741878/", "https://gruss.cc/files/prefetch.pdf", "https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5aa90a84589282b87666f92b6c3c917c8080a9bf", "http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5754", "https://spectreattack.com/spectre.pdf", "https://spectreattack.com/spectre.pdf", "https://spectreattack.com/spectre.pdf", "https://spectreattack.com/spectre.pdf"], "cvelist": ["CVE-2017-5753", "CVE-2017-5753", "CVE-2017-5753", "CVE-2017-5753", "CVE-2017-5754", "CVE-2017-5754", "CVE-2017-5754", "CVE-2017-5715", "CVE-2017-5715", "CVE-2017-5715", "CVE-2017-5715"], "lastseen": "2018-01-06T00:53:37", "history": [], "viewCount": 112, "enchantments": {"score": {"modified": "2018-01-06T00:53:37", "value": 6.6}}, "objectVersion": "1.4"}, "lastseen": "2018-01-06T00:53:37", "differentElements": ["cvss"], "edition": 9}, {"bulletin": {"id": "VU:584653", "hash": "29a106d6ade88a871c1221f704e9580eb9bdb0c333aad4ecedae55521f37d7cc", "type": "cert", "bulletinFamily": "info", "title": "CPU hardware vulnerable to side-channel attacks", "description": "### Overview\n\nCPU hardware implementations are vulnerable to cache side-channel attacks. These vulnerabilities are referred to as [Meltdown](<https://meltdownattack.com/>) and [Spectre](<https://spectreattack.com/>).\n\n### Description\n\n**Note: This Vulnerability Note is the product of ongoing analysis and represents our best knowledge as of the most recent revision. As a result, the content may change as our understanding of the issues develops.**\n\nCPU hardware implementations are vulnerable to side-channel attacks referred to as [Meltdown](<https://meltdownattack.com/>) and [Spectre](<https://spectreattack.com/>). Both Spectre and Meltdown take advantage of the ability to extract information from instructions that have executed on a CPU using the CPU cache as a side-channel. These attacks are described in detail by [Google Project Zero](<https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html>), the Institute of Applied Information Processing and Communications (IAIK) at Graz University of Technology (TU Graz) and Anders Fogh. The issues are organized into three variants: \n\n\n * Variant 1 (CVE-2017-5753, [Spectre](<https://spectreattack.com/spectre.pdf>)): Bounds check bypass\n * Variant 2 (CVE-2017-5715, also [Spectre](<https://spectreattack.com/spectre.pdf>)): Branch target injection[](<https://spectreattack.com/spectre.pdf>)\n * Variant 3 (CVE-2017-5754, [Meltdown](<https://meltdownattack.com/meltdown.pdf>)): Rogue data cache load, memory access permission check performed after kernel memory read\n \n**Spectre** \n \nSpectre attacks take advantage of a CPU's branch prediction capabilities. Modern CPUs include a feature called branch prediction, which speculatively executes instructions at a location that the CPU believes it will branch to. Such speculative execution helps to more fully utilize the parts of the CPU, minimizing the time waiting, and therefore improving performance. When a branch is successfully predicted, instructions will retire, which means the outcomes of the instructions such as register and memory writes will be committed. If a branch is mispredicted, the speculatively-executed instructions will be discarded, and the direct side-effects of the instructions are undone. What is not undone are the indirect side-effects, such as CPU cache changes. By measuring latency of memory access operations, the cache can be used to extract values from speculatively-executed instructions. \n \nWith Spectre variant 1 (CVE-2017-5753), the instructions after a conditional branch are speculatively executed as the result of a misprediction. With Spectre variant 2 (CVE-2017-5715), the instructions at a location determined by a branch target that is mispredicted. \n \nWith both variants of the Spectre attack, the impact is that a process may leak sensitive data to other processes on a system. Spectre may also allow one part of an application to access other parts of the same process memory space that would otherwise not be permitted. \n \n**Meltdown** \n \nMeltdown is related to the Spectre attack in that it also uses a cache side channel to access data that otherwise wouldn't be available. The main difference is that it leverages out-of-order execution capabilities in modern CPUs. Like speculative execution due to branch prediction, as used by Spectre, out-of-order execution on a CPU is a technique for ensuring fullest utilization of the CPU's parts. Although instructions may appear sequentially in the machine language, a CPU that supports out-of-order execution may execute instructions in a non-sequential manner, which can minimize the time that a CPU spends idle. \n \nMeltdown leverages insecure behavior that has been demonstrated in Intel CPUs and may affect CPUs from other vendors. Vulnerable CPUs allow memory reads in out-of-order instruction execution, and also contain a race condition between the raising of exceptions and the out-of-order instruction execution. The Meltdown attack reads a kernel memory value, which raises an exception because code running with user-space privileges are not permitted to directly read kernel memory. However, due to the race condition, out-of-order instructions following the faulting instruction may also execute. Even though instructions appear after the faulting instruction, out-of-order execution allows them to execute, using data retrieved from the instruction that raises the exception. By the time the exception is raised, some number of out-of-order instructions have executed. Although the raised exception causes the CPU to roll back the out-of-order instructions, the cache state is not reverted. This allows data from out-of-order instructions to persist beyond the point when the exception has been raised. \n \nThe impact of Meltdown is that a process running in user space is able to view the contents of kernel memory. Meltdown may also allow Spectre-like memory content leaking that does not cross the user/kernel privilege boundary. \n \nThe Linux kernel mitigations for Meltdown are referred to as KAISER, and subsequently KPTI, which aim to improve separation of kernel and user memory pages. Because the Spectre attacks do not cross user/kernel boundaries, the protections introduced with KAISER/KPTI do not add any protection against them. \n \nThe following table compares Spectre and Meltdown. \n \n| | **Spectre**| **Meltdown** \n---|---|--- \n**CPU mechanism for triggering**| Speculative execution from branch prediction| Out-of-order execution \n**Affected platforms**| CPUs that perform speculative execution from branch prediction| CPUs that allow memory reads in out-of-order instructions \n**Difficulty of successful attack**| High - Requires tailoring to the software environment of the victim process| Low - Kernel memory access exploit code is mostly universal \n**Impact**| Cross- and intra-process memory disclosure| Kernel memory disclosure to userspace \n**Software mitigations**| Indirect Branch Restricted Speculation ([IBRS](<https://lkml.org/lkml/2018/1/4/615>)) \n**Note: **This software mitigation also requires CPU microcode updates and it only mitigates Spectre variant 2| Kernel page-table isolation ([KPTI](<https://en.wikipedia.org/wiki/Kernel_page-table_isolation>)) \n \n### Impact\n\nAn attacker able to execute code with user privileges can achieve various impacts. The Meltdown attack allows reading of kernel memory from userspace. This can result in privilege escalation, disclosure of sensitive information, or it can weaken kernel-level protections, such as KASLR. The Spectre attack can allow inter-process or intra-process data leaks. \n \nTo execute code locally, an attacker would require a valid account or independent compromise of the target. Attacks using JavaScript in web browsers are possible. Multi-user and multi-tenant systems (including virtualized and cloud environments) likely face the greatest risk. Systems used to browse arbitrary web sites are also at risk. Single-user systems that do not readily provide a way for attackers to execute code locally face significantly lower risk. \n \n--- \n \n### Solution\n\n**Apply updates** \n \nOperating system, CPU microcode updates, and some application updates mitigate these attacks. \n \n--- \n \n### Vendor Information \n\nVendor| Status| Date Notified| Date Updated \n---|---|---|--- \nAmazon| | -| 05 Jan 2018 \nAMD| | -| 03 Jan 2018 \nAndroid Open Source Project| | -| 05 Jan 2018 \nApple| | -| 04 Jan 2018 \nArm| | -| 03 Jan 2018 \nCentOS| | -| 05 Jan 2018 \nCisco| | -| 05 Jan 2018 \nCitrix| | -| 05 Jan 2018 \nDebian GNU/Linux| | -| 05 Jan 2018 \nFedora Project| | -| 05 Jan 2018 \nFortinet, Inc.| | -| 05 Jan 2018 \nFreeBSD Project| | -| 05 Jan 2018 \nGoogle| | -| 03 Jan 2018 \nIBM Corporation| | -| 05 Jan 2018 \nIntel| | -| 05 Jan 2018 \nIf you are a vendor and your product is affected, [let us know](<mailto:cert@cert.org?Subject=VU%23584653 Vendor Status Inquiry>). \n \n\n\n### CVSS Metrics \n\nGroup | Score | Vector \n---|---|--- \nBase | 4.4 | AV:L/AC:M/Au:S/C:C/I:N/A:N \nTemporal | 3.4 | E:POC/RL:OF/RC:C \nEnvironmental | 5.1 | CDP:ND/TD:H/CR:H/IR:ND/AR:ND \n \n### References\n\n * <https://meltdownattack.com/>\n * <https://meltdownattack.com/meltdown.pdf>\n * <https://spectreattack.com/>\n * <https://spectreattack.com/spectre.pdf>\n * <https://security.googleblog.com/2018/01/todays-cpu-vulnerability-what-you-need.html>\n * <https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html>\n * <https://cyber.wtf/2017/07/28/negative-result-reading-kernel-memory-from-user-mode/>\n * <https://github.com/IAIK/KAISER>\n * <https://gruss.cc/files/kaiser.pdf>\n * <https://gruss.cc/files/prefetch.pdf>\n * <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5aa90a84589282b87666f92b6c3c917c8080a9bf>\n * <https://lkml.org/lkml/2017/12/27/2>\n * <https://lkml.org/lkml/2018/1/4/615>\n * <https://lwn.net/Articles/741878/>\n * <https://lwn.net/Articles/737940/>\n * <https://lwn.net/Articles/742702/>\n * <http://pythonsweetness.tumblr.com/post/169166980422/the-mysterious-case-of-the-linux-page-table>\n * <https://nakedsecurity.sophos.com/2018/01/03/fckwit-aka-kaiser-aka-kpti-intel-cpu-flaw-needs-low-level-os-patches/>\n * <https://en.wikipedia.org/wiki/Kernel_page-table_isolation>\n * <https://chrisam.net/2018/01/04/speculative-execution-side-channel-vulnerabilities-vendor-published-info/>\n\n### Credit\n\nThese issues were researched and reported by researchers at Google Project Zero (Jann Horn) the Institute of Applied Information Processing and Communications (IAIK) at Graz University of Technology (Gruss et. al.), and Anders Fogh.\n\nThis document was written by Art Manion and Will Dormann.\n\n### Other Information\n\n * CVE IDs: [CVE-2017-5753](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5753>) [CVE-2017-5715](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5715>) [CVE-2017-5754](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5754>)\n * US-CERT Alert: [TA18-004A](<http://www.us-cert.gov/cas/techalerts/TA18-004A.html>)\n * Date Public: 03 Jan 2018\n * Date First Published: 03 Jan 2018\n * Date Last Updated: 05 Jan 2018\n * Document Revision: 145\n\n", "published": "2018-01-03T00:00:00", "modified": "2018-01-05T00:00:00", "cvss": {"score": 4.7, "vector": "AV:LOCAL/AC:MEDIUM/Au:NONE/C:COMPLETE/I:NONE/A:NONE/"}, "href": "https://www.kb.cert.org/vuls/id/584653", "reporter": "CERT", "references": ["https://meltdownattack.com/meltdown.pdf", "https://meltdownattack.com/meltdown.pdf", "https://lwn.net/Articles/742702/", "https://nakedsecurity.sophos.com/2018/01/03/fckwit-aka-kaiser-aka-kpti-intel-cpu-flaw-needs-low-level-os-patches/", "https://lkml.org/lkml/2017/12/27/2", "https://security.googleblog.com/2018/01/todays-cpu-vulnerability-what-you-need.html", "https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html", "https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html", "http://pythonsweetness.tumblr.com/post/169166980422/the-mysterious-case-of-the-linux-page-table", "https://gruss.cc/files/kaiser.pdf", "http://www.us-cert.gov/cas/techalerts/TA18-004A.html", "https://chrisam.net/2018/01/04/speculative-execution-side-channel-vulnerabilities-vendor-published-info/", "https://meltdownattack.com/", "https://meltdownattack.com/", "https://meltdownattack.com/", "https://en.wikipedia.org/wiki/Kernel_page-table_isolation", "https://en.wikipedia.org/wiki/Kernel_page-table_isolation", "http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5753", "https://spectreattack.com/", "https://spectreattack.com/", "https://spectreattack.com/", "https://lwn.net/Articles/737940/", "http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5715", "https://lkml.org/lkml/2018/1/4/615", "https://lkml.org/lkml/2018/1/4/615", "https://github.com/IAIK/KAISER", "https://cyber.wtf/2017/07/28/negative-result-reading-kernel-memory-from-user-mode/", "https://lwn.net/Articles/741878/", "https://gruss.cc/files/prefetch.pdf", "https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5aa90a84589282b87666f92b6c3c917c8080a9bf", "http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5754", "https://spectreattack.com/spectre.pdf", "https://spectreattack.com/spectre.pdf", "https://spectreattack.com/spectre.pdf", "https://spectreattack.com/spectre.pdf"], "cvelist": ["CVE-2017-5753", "CVE-2017-5753", "CVE-2017-5753", "CVE-2017-5753", "CVE-2017-5754", "CVE-2017-5754", "CVE-2017-5754", "CVE-2017-5715", "CVE-2017-5715", "CVE-2017-5715", "CVE-2017-5715"], "lastseen": "2018-01-06T12:53:18", "history": [], "viewCount": 142, "enchantments": {"score": {"modified": "2018-01-06T12:53:18", "value": 6.6}}, "objectVersion": "1.4"}, "lastseen": "2018-01-06T12:53:18", "differentElements": ["description", "modified", "references"], "edition": 10}, {"bulletin": {"id": "VU:584653", "hash": "b15f6522f9ac4b29a113908d7760fc9942cf86f49c06bef4f4dcfcca34ed75c4", "type": "cert", "bulletinFamily": "info", "title": "CPU hardware vulnerable to side-channel attacks", "description": "### Overview\n\nCPU hardware implementations are vulnerable to cache side-channel attacks. These vulnerabilities are referred to as [Meltdown](<https://meltdownattack.com/>) and [Spectre](<https://spectreattack.com/>).\n\n### Description\n\n**Note: This Vulnerability Note is the product of ongoing analysis and represents our best knowledge as of the most recent revision. As a result, the content may change as our understanding of the issues develops.**\n\nCPU hardware implementations are vulnerable to side-channel attacks referred to as [Meltdown](<https://meltdownattack.com/>) and [Spectre](<https://spectreattack.com/>). Both Spectre and Meltdown take advantage of the ability to extract information from instructions that have executed on a CPU using the CPU cache as a side-channel. These attacks are described in detail by [Google Project Zero](<https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html>), the Institute of Applied Information Processing and Communications (IAIK) at Graz University of Technology (TU Graz) and Anders Fogh. The issues are organized into three variants: \n\n\n * Variant 1 (CVE-2017-5753, [Spectre](<https://spectreattack.com/spectre.pdf>)): Bounds check bypass\n * Variant 2 (CVE-2017-5715, also [Spectre](<https://spectreattack.com/spectre.pdf>)): Branch target injection[](<https://spectreattack.com/spectre.pdf>)\n * Variant 3 (CVE-2017-5754, [Meltdown](<https://meltdownattack.com/meltdown.pdf>)): Rogue data cache load, memory access permission check performed after kernel memory read\n \n**Spectre** \n \nSpectre attacks take advantage of a CPU's branch prediction capabilities. Modern CPUs include a feature called branch prediction, which speculatively executes instructions at a location that the CPU believes it will branch to. Such speculative execution helps to more fully utilize the parts of the CPU, minimizing the time waiting, and therefore improving performance. When a branch is successfully predicted, instructions will retire, which means the outcomes of the instructions such as register and memory writes will be committed. If a branch is mispredicted, the speculatively-executed instructions will be discarded, and the direct side-effects of the instructions are undone. What is not undone are the indirect side-effects, such as CPU cache changes. By measuring latency of memory access operations, the cache can be used to extract values from speculatively-executed instructions. \n \nWith Spectre variant 1 (CVE-2017-5753), the instructions after a conditional branch are speculatively executed as the result of a misprediction. With Spectre variant 2 (CVE-2017-5715), the instructions at a location determined by a branch target that is mispredicted. \n \nWith both variants of the Spectre attack, the impact is that a process may leak sensitive data to other processes on a system. Spectre may also allow one part of an application to access other parts of the same process memory space that would otherwise not be permitted. \n \nWhile the Spectre attack itself does not cross a user/kernel memory privilege boundary, depending on the configuration of the target platform, the Spectre attack may indirectly allow a user-space application to access kernel memory. For example, the[ Project Zero blog post](<https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html>) describes a scenario that uses eBPF to exfiltrate kernel memory contents into user-space code. This is made possible because eBPF JIT allows for userspace applications to inject code that is executed in kernel space. While this code is verified by the kernel, eBPF-compliant code will be allowed to execute with kernel permissions. The exploit described by Project Zero leverages eBPF to execute the Spectre attack in kernel space, while exfiltrating the data to user space. It is possible that other technologies that allow in-kernel code execution may also possibly be leveraged to leak kernel memory using Spectre. \n \n**Meltdown** \n \nMeltdown is related to the Spectre attack in that it also uses a cache side channel to access data that otherwise wouldn't be available. The main difference is that it leverages out-of-order execution capabilities in modern CPUs. Like speculative execution due to branch prediction, as used by Spectre, out-of-order execution on a CPU is a technique for ensuring fullest utilization of the CPU's parts. Although instructions may appear sequentially in the machine language, a CPU that supports out-of-order execution may execute instructions in a non-sequential manner, which can minimize the time that a CPU spends idle. \n \nMeltdown leverages insecure behavior that has been demonstrated in Intel CPUs and may affect CPUs from other vendors. Vulnerable CPUs allow memory reads in out-of-order instruction execution, and also contain a race condition between the raising of exceptions and the out-of-order instruction execution. The Meltdown attack reads a kernel memory value, which raises an exception because code running with user-space privileges are not permitted to directly read kernel memory. However, due to the race condition, out-of-order instructions following the faulting instruction may also execute. Even though instructions appear after the faulting instruction, out-of-order execution allows them to execute, using data retrieved from the instruction that raises the exception. By the time the exception is raised, some number of out-of-order instructions have executed. Although the raised exception causes the CPU to roll back the out-of-order instructions, the cache state is not reverted. This allows data from out-of-order instructions to persist beyond the point when the exception has been raised. \n \nThe impact of Meltdown is that a process running in user space is able to view the contents of kernel memory. Meltdown may also allow Spectre-like memory content leaking that does not cross the user/kernel privilege boundary. \n \nThe Linux kernel mitigations for Meltdown are referred to as KAISER, and subsequently KPTI, which aim to improve separation of kernel and user memory pages. Because the Spectre attacks do not cross user/kernel boundaries, the protections introduced with KAISER/KPTI do not add any protection against them. \n \nThe following table compares Spectre and Meltdown. \n \n| | **Spectre**| **Meltdown** \n---|---|--- \n**CPU mechanism for triggering**| Speculative execution from branch prediction| Out-of-order execution \n**Affected platforms**| CPUs that perform speculative execution from branch prediction| CPUs that allow memory reads in out-of-order instructions \n**Difficulty of successful attack**| High - Requires tailoring to the software environment of the victim process| Low - Kernel memory access exploit code is mostly universal \n**Impact**| Cross- and intra-process (including kernel) memory disclosure| Kernel memory disclosure to userspace \n**Software mitigations**| Indirect Branch Restricted Speculation ([IBRS](<https://lkml.org/lkml/2018/1/4/615>)) \n**Note: **This software mitigation also requires CPU microcode updates and it only mitigates Spectre variant 2| Kernel page-table isolation ([KPTI](<https://en.wikipedia.org/wiki/Kernel_page-table_isolation>)) \n \n### Impact\n\nAn attacker able to execute code with user privileges can achieve various impacts. The Meltdown attack allows reading of kernel memory from userspace. This can result in privilege escalation, disclosure of sensitive information, or it can weaken kernel-level protections, such as KASLR. The Spectre attack can allow inter-process or intra-process data leaks. \n \nTo execute code locally, an attacker would require a valid account or independent compromise of the target. Attacks using JavaScript in web browsers are possible. Multi-user and multi-tenant systems (including virtualized and cloud environments) likely face the greatest risk. Systems used to browse arbitrary web sites are also at risk. Single-user systems that do not readily provide a way for attackers to execute code locally face significantly lower risk. \n \n--- \n \n### Solution\n\n**Apply updates** \n \nOperating system, CPU microcode updates, and some application updates mitigate these attacks. \n \n--- \n \n### Vendor Information \n\nVendor| Status| Date Notified| Date Updated \n---|---|---|--- \nAmazon| | -| 05 Jan 2018 \nAMD| | -| 03 Jan 2018 \nAndroid Open Source Project| | -| 05 Jan 2018 \nApple| | -| 04 Jan 2018 \nArm| | -| 03 Jan 2018 \nCentOS| | -| 05 Jan 2018 \nCisco| | -| 05 Jan 2018 \nCitrix| | -| 05 Jan 2018 \nDebian GNU/Linux| | -| 05 Jan 2018 \nFedora Project| | -| 05 Jan 2018 \nFortinet, Inc.| | -| 05 Jan 2018 \nFreeBSD Project| | -| 05 Jan 2018 \nGoogle| | -| 03 Jan 2018 \nIBM Corporation| | -| 05 Jan 2018 \nIntel| | -| 05 Jan 2018 \nIf you are a vendor and your product is affected, [let us know](<mailto:cert@cert.org?Subject=VU%23584653 Vendor Status Inquiry>). \n \n\n\n### CVSS Metrics \n\nGroup | Score | Vector \n---|---|--- \nBase | 4.4 | AV:L/AC:M/Au:S/C:C/I:N/A:N \nTemporal | 3.4 | E:POC/RL:OF/RC:C \nEnvironmental | 5.1 | CDP:ND/TD:H/CR:H/IR:ND/AR:ND \n \n### References\n\n * <https://meltdownattack.com/>\n * <https://meltdownattack.com/meltdown.pdf>\n * <https://spectreattack.com/>\n * <https://spectreattack.com/spectre.pdf>\n * <https://security.googleblog.com/2018/01/todays-cpu-vulnerability-what-you-need.html>\n * <https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html>\n * <https://cyber.wtf/2017/07/28/negative-result-reading-kernel-memory-from-user-mode/>\n * <https://github.com/IAIK/KAISER>\n * <https://gruss.cc/files/kaiser.pdf>\n * <https://gruss.cc/files/prefetch.pdf>\n * <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5aa90a84589282b87666f92b6c3c917c8080a9bf>\n * <https://lkml.org/lkml/2017/12/27/2>\n * <https://lkml.org/lkml/2018/1/4/615>\n * <https://lwn.net/Articles/741878/>\n * <https://lwn.net/Articles/737940/>\n * <https://lwn.net/Articles/742702/>\n * <http://pythonsweetness.tumblr.com/post/169166980422/the-mysterious-case-of-the-linux-page-table>\n * <https://nakedsecurity.sophos.com/2018/01/03/fckwit-aka-kaiser-aka-kpti-intel-cpu-flaw-needs-low-level-os-patches/>\n * <https://en.wikipedia.org/wiki/Kernel_page-table_isolation>\n * <https://chrisam.net/2018/01/04/speculative-execution-side-channel-vulnerabilities-vendor-published-info/>\n\n### Credit\n\nThese issues were researched and reported by researchers at Google Project Zero (Jann Horn) the Institute of Applied Information Processing and Communications (IAIK) at Graz University of Technology (Gruss et. al.), and Anders Fogh.\n\nThis document was written by Art Manion and Will Dormann.\n\n### Other Information\n\n * CVE IDs: [CVE-2017-5753](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5753>) [CVE-2017-5715](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5715>) [CVE-2017-5754](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5754>)\n * US-CERT Alert: [TA18-004A](<http://www.us-cert.gov/cas/techalerts/TA18-004A.html>)\n * Date Public: 03 Jan 2018\n * Date First Published: 03 Jan 2018\n * Date Last Updated: 06 Jan 2018\n * Document Revision: 155\n\n", "published": "2018-01-03T00:00:00", "modified": "2018-01-06T00:00:00", "cvss": {"score": 4.7, "vector": "AV:LOCAL/AC:MEDIUM/Au:NONE/C:COMPLETE/I:NONE/A:NONE/"}, "href": "https://www.kb.cert.org/vuls/id/584653", "reporter": "CERT", "references": ["https://meltdownattack.com/meltdown.pdf", "https://meltdownattack.com/meltdown.pdf", "https://lwn.net/Articles/742702/", "https://nakedsecurity.sophos.com/2018/01/03/fckwit-aka-kaiser-aka-kpti-intel-cpu-flaw-needs-low-level-os-patches/", "https://lkml.org/lkml/2017/12/27/2", "https://security.googleblog.com/2018/01/todays-cpu-vulnerability-what-you-need.html", "https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html", "https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html", "https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html", "http://pythonsweetness.tumblr.com/post/169166980422/the-mysterious-case-of-the-linux-page-table", "https://gruss.cc/files/kaiser.pdf", "http://www.us-cert.gov/cas/techalerts/TA18-004A.html", "https://chrisam.net/2018/01/04/speculative-execution-side-channel-vulnerabilities-vendor-published-info/", "https://meltdownattack.com/", "https://meltdownattack.com/", "https://meltdownattack.com/", "https://en.wikipedia.org/wiki/Kernel_page-table_isolation", "https://en.wikipedia.org/wiki/Kernel_page-table_isolation", "http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5753", "https://spectreattack.com/", "https://spectreattack.com/", "https://spectreattack.com/", "https://lwn.net/Articles/737940/", "http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5715", "https://lkml.org/lkml/2018/1/4/615", "https://lkml.org/lkml/2018/1/4/615", "https://github.com/IAIK/KAISER", "https://cyber.wtf/2017/07/28/negative-result-reading-kernel-memory-from-user-mode/", "https://lwn.net/Articles/741878/", "https://gruss.cc/files/prefetch.pdf", "https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5aa90a84589282b87666f92b6c3c917c8080a9bf", "http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5754", "https://spectreattack.com/spectre.pdf", "https://spectreattack.com/spectre.pdf", "https://spectreattack.com/spectre.pdf", "https://spectreattack.com/spectre.pdf"], "cvelist": ["CVE-2017-5753", "CVE-2017-5753", "CVE-2017-5753", "CVE-2017-5753", "CVE-2017-5754", "CVE-2017-5754", "CVE-2017-5754", "CVE-2017-5715", "CVE-2017-5715", "CVE-2017-5715", "CVE-2017-5715"], "lastseen": "2018-01-07T02:55:54", "history": [], "viewCount": 157, "enchantments": {"score": {"modified": "2018-01-07T02:55:54", "value": 6.6}}, "objectVersion": "1.4"}, "lastseen": "2018-01-07T02:55:54", "differentElements": ["description", "modified", "references"], "edition": 11}, {"bulletin": {"id": "VU:584653", "hash": "5b03afa9e41d9bccbab9a18143dc2d9d21c8ae9cab119b1592cebed9f713bdaa", "type": "cert", "bulletinFamily": "info", "title": "CPU hardware vulnerable to side-channel attacks", "description": "### Overview\n\nCPU hardware implementations are vulnerable to cache side-channel attacks. These vulnerabilities are referred to as [Meltdown](<https://meltdownattack.com/>) and [Spectre](<https://spectreattack.com/>).\n\n### Description\n\n**Note: This Vulnerability Note is the product of ongoing analysis and represents our best knowledge as of the most recent revision. As a result, the content may change as our understanding of the issues develops.**\n\nCPU hardware implementations are vulnerable to side-channel attacks referred to as [Meltdown](<https://meltdownattack.com/>) and [Spectre](<https://spectreattack.com/>). Both Spectre and Meltdown take advantage of the ability to extract information from instructions that have executed on a CPU using the CPU cache as a side-channel. These attacks are described in detail by [Google Project Zero](<https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html>), the Institute of Applied Information Processing and Communications (IAIK) at Graz University of Technology (TU Graz) and Anders Fogh. The issues are organized into three variants: \n\n\n * Variant 1 (CVE-2017-5753, [Spectre](<https://spectreattack.com/spectre.pdf>)): Bounds check bypass\n * Variant 2 (CVE-2017-5715, also [Spectre](<https://spectreattack.com/spectre.pdf>)): Branch target injection[](<https://spectreattack.com/spectre.pdf>)\n * Variant 3 (CVE-2017-5754, [Meltdown](<https://meltdownattack.com/meltdown.pdf>)): Rogue data cache load, memory access permission check performed after kernel memory read\n \n**Spectre** \n \nSpectre attacks take advantage of a CPU's branch prediction capabilities. Modern CPUs include a feature called branch prediction, which speculatively executes instructions at a location that the CPU believes it will branch to. Such speculative execution helps to more fully utilize the parts of the CPU, minimizing the time waiting, and therefore improving performance. When a branch is successfully predicted, instructions will retire, which means the outcomes of the instructions such as register and memory writes will be committed. If a branch is mispredicted, the speculatively-executed instructions will be discarded, and the direct side-effects of the instructions are undone. What is not undone are the indirect side-effects, such as CPU cache changes. By measuring latency of memory access operations, the cache can be used to extract values from speculatively-executed instructions. \n \nWith Spectre variant 1 (CVE-2017-5753), the instructions after a conditional branch are speculatively executed as the result of a misprediction. With Spectre variant 2 (CVE-2017-5715), the CPU executes instructions at a location determined by a mispredicted branch target. \n \nWith both variants of the Spectre attack, the impact is that a process may leak sensitive data to other processes on a system. Spectre may also allow one part of an application to access other parts of the same process memory space that would otherwise not be permitted. \n \nWhile the Spectre attack itself does not cross a user/kernel memory privilege boundary, depending on the configuration of the target platform, the Spectre attack may indirectly allow a user-space application to access kernel memory. For example, the[ Project Zero blog post](<https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html>) describes a scenario that uses eBPF to exfiltrate kernel memory contents into user-space code. This is made possible because eBPF JIT allows for userspace applications to inject code that is executed in kernel space. While this code is verified by the kernel, eBPF-compliant code will be allowed to execute with kernel permissions. The exploit described by Project Zero leverages eBPF to execute the Spectre attack in kernel space, while exfiltrating the data to user space. It is possible that other technologies that allow in-kernel code execution may also possibly be leveraged to leak kernel memory using Spectre. \n \n**Meltdown** \n \nMeltdown is related to the Spectre attack in that it also uses a cache side channel to access data that otherwise wouldn't be available. The main difference is that it leverages out-of-order execution capabilities in modern CPUs. Like speculative execution due to branch prediction, as used by Spectre, out-of-order execution on a CPU is a technique for ensuring fullest utilization of the CPU's parts. Although instructions may appear sequentially in the machine language, a CPU that supports out-of-order execution may execute instructions in a non-sequential manner, which can minimize the time that a CPU spends idle. \n \nMeltdown leverages insecure behavior that has been demonstrated in Intel CPUs and may affect CPUs from other vendors. Vulnerable CPUs allow memory reads in out-of-order instruction execution, and also contain a race condition between the raising of exceptions and the out-of-order instruction execution. The Meltdown attack reads a kernel memory value, which raises an exception because code running with user-space privileges are not permitted to directly read kernel memory. However, due to the race condition, out-of-order instructions following the faulting instruction may also execute. Even though instructions appear after the faulting instruction, out-of-order execution allows them to execute, using data retrieved from the instruction that raises the exception. By the time the exception is raised, some number of out-of-order instructions have executed. Although the raised exception causes the CPU to roll back the out-of-order instructions, the cache state is not reverted. This allows data from out-of-order instructions to persist beyond the point when the exception has been raised. \n \nThe impact of Meltdown is that a process running in user space is able to view the contents of kernel memory. Meltdown may also allow Spectre-like memory content leaking that does not cross the user/kernel privilege boundary. \n \nThe Linux kernel mitigations for Meltdown are referred to as KAISER, and subsequently KPTI, which aim to improve separation of kernel and user memory pages. Because the Spectre attacks do not cross user/kernel boundaries, the protections introduced with KAISER/KPTI do not add any protection against them. \n \nThe following table compares Spectre and Meltdown. \n \n| | **Spectre**| **Meltdown** \n---|---|--- \n**CPU mechanism for triggering**| Speculative execution from branch prediction| Out-of-order execution \n**Affected platforms**| CPUs that perform speculative execution from branch prediction| CPUs that allow memory reads in out-of-order instructions \n**Difficulty of successful attack**| High - Requires tailoring to the software environment of the victim process| Low - Kernel memory access exploit code is mostly universal \n**Impact**| Cross- and intra-process (including kernel) memory disclosure| Kernel memory disclosure to userspace \n**Software mitigations**| Indirect Branch Restricted Speculation ([IBRS](<https://lkml.org/lkml/2018/1/4/615>)) \n**Note: **This software mitigation also requires CPU microcode updates and it only mitigates Spectre variant 2| Kernel page-table isolation ([KPTI](<https://en.wikipedia.org/wiki/Kernel_page-table_isolation>)) \n \n### Impact\n\nAn attacker able to execute code with user privileges can achieve various impacts. The Meltdown attack allows reading of kernel memory from userspace. This can result in privilege escalation, disclosure of sensitive information, or it can weaken kernel-level protections, such as KASLR. The Spectre attack can allow inter-process or intra-process data leaks. \n \nTo execute code locally, an attacker would require a valid account or independent compromise of the target. Attacks using JavaScript in web browsers are possible. Multi-user and multi-tenant systems (including virtualized and cloud environments) likely face the greatest risk. Systems used to browse arbitrary web sites are also at risk. Single-user systems that do not readily provide a way for attackers to execute code locally face significantly lower risk. \n \n--- \n \n### Solution\n\n**Apply updates** \n \nOperating system, CPU microcode updates, and some application updates mitigate these attacks. \n \n--- \n \n### Vendor Information \n\nVendor| Status| Date Notified| Date Updated \n---|---|---|--- \nAmazon| | -| 05 Jan 2018 \nAMD| | -| 03 Jan 2018 \nAndroid Open Source Project| | -| 05 Jan 2018 \nApple| | -| 08 Jan 2018 \nArm| | -| 03 Jan 2018 \nCentOS| | -| 05 Jan 2018 \nCisco| | -| 05 Jan 2018 \nCitrix| | -| 05 Jan 2018 \nDebian GNU/Linux| | -| 05 Jan 2018 \nDell| | -| 08 Jan 2018 \nDragonFly BSD Project| | -| 08 Jan 2018 \nFedora Project| | -| 05 Jan 2018 \nFortinet, Inc.| | -| 05 Jan 2018 \nFreeBSD Project| | -| 05 Jan 2018 \nGoogle| | -| 03 Jan 2018 \nIf you are a vendor and your product is affected, [let us know](<mailto:cert@cert.org?Subject=VU%23584653 Vendor Status Inquiry>). \n \n\n\n### CVSS Metrics \n\nGroup | Score | Vector \n---|---|--- \nBase | 4.4 | AV:L/AC:M/Au:S/C:C/I:N/A:N \nTemporal | 3.4 | E:POC/RL:OF/RC:C \nEnvironmental | 5.1 | CDP:ND/TD:H/CR:H/IR:ND/AR:ND \n \n### References\n\n * <https://meltdownattack.com/>\n * <https://meltdownattack.com/meltdown.pdf>\n * <https://spectreattack.com/>\n * <https://spectreattack.com/spectre.pdf>\n * <https://security.googleblog.com/2018/01/todays-cpu-vulnerability-what-you-need.html>\n * <https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html>\n * <https://cyber.wtf/2017/07/28/negative-result-reading-kernel-memory-from-user-mode/>\n * <https://github.com/IAIK/KAISER>\n * <https://gruss.cc/files/kaiser.pdf>\n * <https://gruss.cc/files/prefetch.pdf>\n * <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5aa90a84589282b87666f92b6c3c917c8080a9bf>\n * <https://lkml.org/lkml/2017/12/27/2>\n * <https://lkml.org/lkml/2018/1/4/615>\n * <https://lwn.net/Articles/741878/>\n * <https://lwn.net/Articles/737940/>\n * <https://lwn.net/Articles/742702/>\n * <http://pythonsweetness.tumblr.com/post/169166980422/the-mysterious-case-of-the-linux-page-table>\n * <https://nakedsecurity.sophos.com/2018/01/03/fckwit-aka-kaiser-aka-kpti-intel-cpu-flaw-needs-low-level-os-patches/>\n * <https://en.wikipedia.org/wiki/Kernel_page-table_isolation>\n * <https://chrisam.net/2018/01/04/speculative-execution-side-channel-vulnerabilities-vendor-published-info/>\n * <https://www.raspberrypi.org/blog/why-raspberry-pi-isnt-vulnerable-to-spectre-or-meltdown/>\n\n### Credit\n\nThese issues were researched and reported by researchers at Google Project Zero (Jann Horn) the Institute of Applied Information Processing and Communications (IAIK) at Graz University of Technology (Gruss et. al.), and Anders Fogh.\n\nThis document was written by Art Manion and Will Dormann.\n\n### Other Information\n\n * CVE IDs: [CVE-2017-5753](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5753>) [CVE-2017-5715](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5715>) [CVE-2017-5754](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5754>)\n * US-CERT Alert: [TA18-004A](<http://www.us-cert.gov/cas/techalerts/TA18-004A.html>)\n * Date Public: 03 Jan 2018\n * Date First Published: 03 Jan 2018\n * Date Last Updated: 08 Jan 2018\n * Document Revision: 171\n\n", "published": "2018-01-03T00:00:00", "modified": "2018-01-08T00:00:00", "cvss": {"score": 4.7, "vector": "AV:LOCAL/AC:MEDIUM/Au:NONE/C:COMPLETE/I:NONE/A:NONE/"}, "href": "https://www.kb.cert.org/vuls/id/584653", "reporter": "CERT", "references": ["https://meltdownattack.com/meltdown.pdf", "https://meltdownattack.com/meltdown.pdf", "https://lwn.net/Articles/742702/", "https://nakedsecurity.sophos.com/2018/01/03/fckwit-aka-kaiser-aka-kpti-intel-cpu-flaw-needs-low-level-os-patches/", "https://www.raspberrypi.org/blog/why-raspberry-pi-isnt-vulnerable-to-spectre-or-meltdown/", "https://lkml.org/lkml/2017/12/27/2", "https://security.googleblog.com/2018/01/todays-cpu-vulnerability-what-you-need.html", "https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html", "https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html", "https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html", "http://pythonsweetness.tumblr.com/post/169166980422/the-mysterious-case-of-the-linux-page-table", "https://gruss.cc/files/kaiser.pdf", "http://www.us-cert.gov/cas/techalerts/TA18-004A.html", "https://chrisam.net/2018/01/04/speculative-execution-side-channel-vulnerabilities-vendor-published-info/", "https://meltdownattack.com/", "https://meltdownattack.com/", "https://meltdownattack.com/", "https://en.wikipedia.org/wiki/Kernel_page-table_isolation", "https://en.wikipedia.org/wiki/Kernel_page-table_isolation", "http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5753", "https://spectreattack.com/", "https://spectreattack.com/", "https://spectreattack.com/", "https://lwn.net/Articles/737940/", "http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5715", "https://lkml.org/lkml/2018/1/4/615", "https://lkml.org/lkml/2018/1/4/615", "https://github.com/IAIK/KAISER", "https://cyber.wtf/2017/07/28/negative-result-reading-kernel-memory-from-user-mode/", "https://lwn.net/Articles/741878/", "https://gruss.cc/files/prefetch.pdf", "https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5aa90a84589282b87666f92b6c3c917c8080a9bf", "http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5754", "https://spectreattack.com/spectre.pdf", "https://spectreattack.com/spectre.pdf", "https://spectreattack.com/spectre.pdf", "https://spectreattack.com/spectre.pdf"], "cvelist": ["CVE-2017-5753", "CVE-2017-5753", "CVE-2017-5753", "CVE-2017-5753", "CVE-2017-5754", "CVE-2017-5754", "CVE-2017-5754", "CVE-2017-5715", "CVE-2017-5715", "CVE-2017-5715", "CVE-2017-5715"], "lastseen": "2018-01-09T00:55:29", "history": [], "viewCount": 160, "enchantments": {"score": {"modified": "2018-01-09T00:55:29", "value": 6.6}}, "objectVersion": "1.4"}, "lastseen": "2018-01-09T00:55:29", "differentElements": ["description", "references"], "edition": 12}, {"bulletin": {"id": "VU:584653", "hash": "b747748b0ff1d2ae8f7206f1e03d1858500bef11fa93f25277c64db7b067aa8b", "type": "cert", "bulletinFamily": "info", "title": "CPU hardware vulnerable to side-channel attacks", "description": "### Overview\n\nCPU hardware implementations are vulnerable to cache side-channel attacks. These vulnerabilities are referred to as [Meltdown](<https://meltdownattack.com/>) and [Spectre](<https://spectreattack.com/>).\n\n### Description\n\n**Note: This Vulnerability Note is the product of ongoing analysis and represents our best knowledge as of the most recent revision. As a result, the content may change as our understanding of the issues develops.**\n\nCPU hardware implementations are vulnerable to side-channel attacks referred to as [Meltdown](<https://meltdownattack.com/>) and [Spectre](<https://spectreattack.com/>). Both Spectre and Meltdown take advantage of the ability to extract information from instructions that have executed on a CPU using the CPU cache as a side-channel. These attacks are described in detail by [Google Project Zero](<https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html>), the Institute of Applied Information Processing and Communications (IAIK) at Graz University of Technology (TU Graz) and Anders Fogh. The issues are organized into three variants: \n\n\n * Variant 1 (CVE-2017-5753, [Spectre](<https://spectreattack.com/spectre.pdf>)): Bounds check bypass\n * Variant 2 (CVE-2017-5715, also [Spectre](<https://spectreattack.com/spectre.pdf>)): Branch target injection[](<https://spectreattack.com/spectre.pdf>)\n * Variant 3 (CVE-2017-5754, [Meltdown](<https://meltdownattack.com/meltdown.pdf>)): Rogue data cache load, memory access permission check performed after kernel memory read\n \n**Spectre** \n \nSpectre attacks take advantage of a CPU's branch prediction capabilities. Modern CPUs include a feature called branch prediction, which speculatively executes instructions at a location that the CPU believes it will branch to. Such speculative execution helps to more fully utilize the parts of the CPU, minimizing the time waiting, and therefore improving performance. When a branch is successfully predicted, instructions will retire, which means the outcomes of the instructions such as register and memory writes will be committed. If a branch is mispredicted, the speculatively-executed instructions will be discarded, and the direct side-effects of the instructions are undone. What is not undone are the indirect side-effects, such as CPU cache changes. By measuring latency of memory access operations, the cache can be used to extract values from speculatively-executed instructions. \n \nWith Spectre variant 1 (CVE-2017-5753), the instructions after a conditional branch are speculatively executed as the result of a misprediction. With Spectre variant 2 (CVE-2017-5715), the CPU executes instructions at a location determined by a mispredicted branch target. \n \nWith both variants of the Spectre attack, the impact is that a process may leak sensitive data to other processes on a system. Spectre may also allow one part of an application to access other parts of the same process memory space that would otherwise not be permitted. \n \nWhile the Spectre attack itself does not cross a user/kernel memory privilege boundary, depending on the configuration of the target platform, the Spectre attack may indirectly allow a user-space application to access kernel memory. For example, the[ Project Zero blog post](<https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html>) describes a scenario that uses eBPF to exfiltrate kernel memory contents into user-space code. This is made possible because eBPF JIT allows for userspace applications to inject code that is executed in kernel space. While this code is verified by the kernel, eBPF-compliant code will be allowed to execute with kernel permissions. The exploit described by Project Zero leverages eBPF to execute the Spectre attack in kernel space, while exfiltrating the data to user space. It is possible that other technologies that allow in-kernel code execution may also possibly be leveraged to leak kernel memory using Spectre. \n \n**Meltdown** \n \nMeltdown is related to the Spectre attack in that it also uses a cache side channel to access data that otherwise wouldn't be available. The main difference is that it leverages out-of-order execution capabilities in modern CPUs. Like speculative execution due to branch prediction, as used by Spectre, out-of-order execution on a CPU is a technique for ensuring fullest utilization of the CPU's parts. Although instructions may appear sequentially in the machine language, a CPU that supports out-of-order execution may execute instructions in a non-sequential manner, which can minimize the time that a CPU spends idle. \n \nMeltdown leverages insecure behavior that has been demonstrated in Intel CPUs and may affect CPUs from other vendors. Vulnerable CPUs allow memory reads in out-of-order instruction execution, and also contain a race condition between the raising of exceptions and the out-of-order instruction execution. The Meltdown attack reads a kernel memory value, which raises an exception because code running with user-space privileges are not permitted to directly read kernel memory. However, due to the race condition, out-of-order instructions following the faulting instruction may also execute. Even though instructions appear after the faulting instruction, out-of-order execution allows them to execute, using data retrieved from the instruction that raises the exception. By the time the exception is raised, some number of out-of-order instructions have executed. Although the raised exception causes the CPU to roll back the out-of-order instructions, the cache state is not reverted. This allows data from out-of-order instructions to persist beyond the point when the exception has been raised. \n \nThe impact of Meltdown is that a process running in user space is able to view the contents of kernel memory. Meltdown may also allow Spectre-like memory content leaking that does not cross the user/kernel privilege boundary. \n \nThe Linux kernel mitigations for Meltdown are referred to as KAISER, and subsequently KPTI, which aim to improve separation of kernel and user memory pages. Because the Spectre attacks do not cross user/kernel boundaries, the protections introduced with KAISER/KPTI do not add any protection against them. \n \nThe following table compares Spectre and Meltdown. \n \n| | **Spectre**| **Meltdown** \n---|---|--- \n**CPU mechanism for triggering**| Speculative execution from branch prediction| Out-of-order execution \n**Affected platforms**| CPUs that perform speculative execution from branch prediction| CPUs that allow memory reads in out-of-order instructions \n**Difficulty of successful attack**| High - Requires tailoring to the software environment of the victim process| Low - Kernel memory access exploit code is mostly universal \n**Impact**| Cross- and intra-process (including kernel) memory disclosure| Kernel memory disclosure to userspace \n**Software mitigations**| Indirect Branch Restricted Speculation ([IBRS](<https://lkml.org/lkml/2018/1/4/615>)) \n**Note: **This software mitigation also requires CPU microcode updates and it only mitigates Spectre variant 2| Kernel page-table isolation ([KPTI](<https://en.wikipedia.org/wiki/Kernel_page-table_isolation>)) \n \n### Impact\n\nAn attacker able to execute code with user privileges can achieve various impacts. The Meltdown attack allows reading of kernel memory from userspace. This can result in privilege escalation, disclosure of sensitive information, or it can weaken kernel-level protections, such as KASLR. The Spectre attack can allow inter-process or intra-process data leaks. \n \nTo execute code locally, an attacker would require a valid account or independent compromise of the target. Attacks using JavaScript in web browsers are possible. Multi-user and multi-tenant systems (including virtualized and cloud environments) likely face the greatest risk. Systems used to browse arbitrary web sites are also at risk. Single-user systems that do not readily provide a way for attackers to execute code locally face significantly lower risk. \n \n--- \n \n### Solution\n\n**Apply updates** \n \nOperating system, CPU microcode updates, and some application updates mitigate these attacks. \n \n--- \n \n### Vendor Information \n\nVendor| Status| Date Notified| Date Updated \n---|---|---|--- \nAmazon| | -| 05 Jan 2018 \nAMD| | -| 03 Jan 2018 \nAndroid Open Source Project| | -| 05 Jan 2018 \nApple| | -| 08 Jan 2018 \nArm| | -| 03 Jan 2018 \nCentOS| | -| 05 Jan 2018 \nCisco| | -| 05 Jan 2018 \nCitrix| | -| 05 Jan 2018 \nDebian GNU/Linux| | -| 05 Jan 2018 \nDell| | -| 08 Jan 2018 \nDragonFly BSD Project| | -| 08 Jan 2018 \nFedora Project| | -| 05 Jan 2018 \nFortinet, Inc.| | -| 05 Jan 2018 \nFreeBSD Project| | -| 05 Jan 2018 \nGoogle| | -| 03 Jan 2018 \nIf you are a vendor and your product is affected, [let us know](<mailto:cert@cert.org?Subject=VU%23584653 Vendor Status Inquiry>). \n \n\n\n### CVSS Metrics \n\nGroup | Score | Vector \n---|---|--- \nBase | 4.4 | AV:L/AC:M/Au:S/C:C/I:N/A:N \nTemporal | 3.4 | E:POC/RL:OF/RC:C \nEnvironmental | 5.1 | CDP:ND/TD:H/CR:H/IR:ND/AR:ND \n \n### References\n\n * <https://meltdownattack.com/>\n * <https://meltdownattack.com/meltdown.pdf>\n * <https://spectreattack.com/>\n * <https://spectreattack.com/spectre.pdf>\n * <https://security.googleblog.com/2018/01/todays-cpu-vulnerability-what-you-need.html>\n * <https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html>\n * <https://cyber.wtf/2017/07/28/negative-result-reading-kernel-memory-from-user-mode/>\n * <https://github.com/IAIK/KAISER>\n * <https://gruss.cc/files/kaiser.pdf>\n * <https://gruss.cc/files/prefetch.pdf>\n * <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5aa90a84589282b87666f92b6c3c917c8080a9bf>\n * <https://lkml.org/lkml/2017/12/27/2>\n * <https://lkml.org/lkml/2018/1/4/615>\n * <https://lwn.net/Articles/741878/>\n * <https://lwn.net/Articles/737940/>\n * <https://lwn.net/Articles/742702/>\n * <http://pythonsweetness.tumblr.com/post/169166980422/the-mysterious-case-of-the-linux-page-table>\n * <https://nakedsecurity.sophos.com/2018/01/03/fckwit-aka-kaiser-aka-kpti-intel-cpu-flaw-needs-low-level-os-patches/>\n * <https://en.wikipedia.org/wiki/Kernel_page-table_isolation>\n * <https://chrisam.net/2018/01/04/speculative-execution-side-channel-vulnerabilities-vendor-published-info/>\n * <https://www.raspberrypi.org/blog/why-raspberry-pi-isnt-vulnerable-to-spectre-or-meltdown/>\n * <https://doublepulsar.com/important-information-about-microsoft-meltdown-cpu-security-fixes-antivirus-vendors-and-you-a852ba0292ec>\n\n### Credit\n\nThese issues were researched and reported by researchers at Google Project Zero (Jann Horn) the Institute of Applied Information Processing and Communications (IAIK) at Graz University of Technology (Gruss et. al.), Paul Kocher, and Anders Fogh.\n\nThis document was written by Art Manion and Will Dormann.\n\n### Other Information\n\n * CVE IDs: [CVE-2017-5753](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5753>) [CVE-2017-5715](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5715>) [CVE-2017-5754](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5754>)\n * US-CERT Alert: [TA18-004A](<http://www.us-cert.gov/cas/techalerts/TA18-004A.html>)\n * Date Public: 03 Jan 2018\n * Date First Published: 03 Jan 2018\n * Date Last Updated: 08 Jan 2018\n * Document Revision: 179\n\n", "published": "2018-01-03T00:00:00", "modified": "2018-01-08T00:00:00", "cvss": {"score": 4.7, "vector": "AV:LOCAL/AC:MEDIUM/Au:NONE/C:COMPLETE/I:NONE/A:NONE/"}, "href": "https://www.kb.cert.org/vuls/id/584653", "reporter": "CERT", "references": ["https://meltdownattack.com/meltdown.pdf", "https://meltdownattack.com/meltdown.pdf", "https://lwn.net/Articles/742702/", "https://nakedsecurity.sophos.com/2018/01/03/fckwit-aka-kaiser-aka-kpti-intel-cpu-flaw-needs-low-level-os-patches/", "https://www.raspberrypi.org/blog/why-raspberry-pi-isnt-vulnerable-to-spectre-or-meltdown/", "https://lkml.org/lkml/2017/12/27/2", "https://security.googleblog.com/2018/01/todays-cpu-vulnerability-what-you-need.html", "https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html", "https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html", "https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html", "http://pythonsweetness.tumblr.com/post/169166980422/the-mysterious-case-of-the-linux-page-table", "https://gruss.cc/files/kaiser.pdf", "https://doublepulsar.com/important-information-about-microsoft-meltdown-cpu-security-fixes-antivirus-vendors-and-you-a852ba0292ec", "http://www.us-cert.gov/cas/techalerts/TA18-004A.html", "https://chrisam.net/2018/01/04/speculative-execution-side-channel-vulnerabilities-vendor-published-info/", "https://meltdownattack.com/", "https://meltdownattack.com/", "https://meltdownattack.com/", "https://en.wikipedia.org/wiki/Kernel_page-table_isolation", "https://en.wikipedia.org/wiki/Kernel_page-table_isolation", "http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5753", "https://spectreattack.com/", "https://spectreattack.com/", "https://spectreattack.com/", "https://lwn.net/Articles/737940/", "http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5715", "https://lkml.org/lkml/2018/1/4/615", "https://lkml.org/lkml/2018/1/4/615", "https://github.com/IAIK/KAISER", "https://cyber.wtf/2017/07/28/negative-result-reading-kernel-memory-from-user-mode/", "https://lwn.net/Articles/741878/", "https://gruss.cc/files/prefetch.pdf", "https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5aa90a84589282b87666f92b6c3c917c8080a9bf", "http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5754", "https://spectreattack.com/spectre.pdf", "https://spectreattack.com/spectre.pdf", "https://spectreattack.com/spectre.pdf", "https://spectreattack.com/spectre.pdf"], "cvelist": ["CVE-2017-5753", "CVE-2017-5753", "CVE-2017-5753", "CVE-2017-5753", "CVE-2017-5754", "CVE-2017-5754", "CVE-2017-5754", "CVE-2017-5715", "CVE-2017-5715", "CVE-2017-5715", "CVE-2017-5715"], "lastseen": "2018-01-09T03:02:32", "history": [], "viewCount": 168, "enchantments": {"score": {"modified": "2018-01-09T03:02:32", "value": 6.6}}, "objectVersion": "1.4"}, "lastseen": "2018-01-09T03:02:32", "differentElements": ["description", "modified", "references"], "edition": 13}, {"bulletin": {"id": "VU:584653", "hash": "cc94773315a483f0dd389c93951529b1d77e2f4fb45751ab89af7a85003d8d66", "type": "cert", "bulletinFamily": "info", "title": "CPU hardware vulnerable to side-channel attacks", "description": "### Overview\n\nCPU hardware implementations are vulnerable to cache side-channel attacks. These vulnerabilities are referred to as [Meltdown](<https://meltdownattack.com/>) and [Spectre](<https://spectreattack.com/>).\n\n### Description\n\n**Note: This Vulnerability Note is the product of ongoing analysis and represents our best knowledge as of the most recent revision. As a result, the content may change as our understanding of the issues develops.**\n\nCPU hardware implementations are vulnerable to side-channel attacks referred to as [Meltdown](<https://meltdownattack.com/>) and [Spectre](<https://spectreattack.com/>). Both Spectre and Meltdown take advantage of the ability to extract information from instructions that have executed on a CPU using the CPU cache as a side-channel. These attacks are described in detail by [Google Project Zero](<https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html>), the Institute of Applied Information Processing and Communications (IAIK) at Graz University of Technology (TU Graz) and Anders Fogh. The issues are organized into three variants: \n\n\n * Variant 1 (CVE-2017-5753, [Spectre](<https://spectreattack.com/spectre.pdf>)): Bounds check bypass\n * Variant 2 (CVE-2017-5715, also [Spectre](<https://spectreattack.com/spectre.pdf>)): Branch target injection[](<https://spectreattack.com/spectre.pdf>)\n * Variant 3 (CVE-2017-5754, [Meltdown](<https://meltdownattack.com/meltdown.pdf>)): Rogue data cache load, memory access permission check performed after kernel memory read\n \n**Spectre** \n \nSpectre attacks take advantage of a CPU's branch prediction capabilities. Modern CPUs include a feature called branch prediction, which speculatively executes instructions at a location that the CPU believes it will branch to. Such speculative execution helps to more fully utilize the parts of the CPU, minimizing the time waiting, and therefore improving performance. When a branch is successfully predicted, instructions will retire, which means the outcomes of the instructions such as register and memory writes will be committed. If a branch is mispredicted, the speculatively-executed instructions will be discarded, and the direct side-effects of the instructions are undone. What is not undone are the indirect side-effects, such as CPU cache changes. By measuring latency of memory access operations, the cache can be used to extract values from speculatively-executed instructions. \n \nWith Spectre variant 1 (CVE-2017-5753), the instructions after a conditional branch are speculatively executed as the result of a misprediction. With Spectre variant 2 (CVE-2017-5715), the CPU executes instructions at a location determined by a mispredicted branch target. \n \nWith both variants of the Spectre attack, the impact is that a process may leak sensitive data to other processes on a system. Spectre may also allow one part of an application to access other parts of the same process memory space that would otherwise not be permitted. \n \nWhile the Spectre attack itself does not cross a user/kernel memory privilege boundary, depending on the configuration of the target platform, the Spectre attack may indirectly allow a user-space application to access kernel memory. For example, the[ Project Zero blog post](<https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html>) describes a scenario that uses eBPF to exfiltrate kernel memory contents into user-space code. This is made possible because eBPF JIT allows for userspace applications to inject code that is executed in kernel space. While this code is verified by the kernel, eBPF-compliant code will be allowed to execute with kernel permissions. The exploit described by Project Zero leverages eBPF to execute the Spectre attack in kernel space, while exfiltrating the data to user space. It is possible that other technologies that allow in-kernel code execution may also possibly be leveraged to leak kernel memory using Spectre. \n \n**Meltdown** \n \nMeltdown is related to the Spectre attack in that it also uses a cache side channel to access data that otherwise wouldn't be available. The main difference is that it leverages out-of-order execution capabilities in modern CPUs. Like speculative execution due to branch prediction, as used by Spectre, out-of-order execution on a CPU is a technique for ensuring fullest utilization of the CPU's parts. Although instructions may appear sequentially in the machine language, a CPU that supports out-of-order execution may execute instructions in a non-sequential manner, which can minimize the time that a CPU spends idle. \n \nMeltdown leverages insecure behavior that has been demonstrated in Intel CPUs and may affect CPUs from other vendors. Vulnerable CPUs allow memory reads in out-of-order instruction execution, and also contain a race condition between the raising of exceptions and the out-of-order instruction execution. The Meltdown attack reads a kernel memory value, which raises an exception because code running with user-space privileges are not permitted to directly read kernel memory. However, due to the race condition, out-of-order instructions following the faulting instruction may also execute. Even though instructions appear after the faulting instruction, out-of-order execution allows them to execute, using data retrieved from the instruction that raises the exception. By the time the exception is raised, some number of out-of-order instructions have executed. Although the raised exception causes the CPU to roll back the out-of-order instructions, the cache state is not reverted. This allows data from out-of-order instructions to persist beyond the point when the exception has been raised. \n \nThe impact of Meltdown is that a process running in user space is able to view the contents of kernel memory. Meltdown may also allow Spectre-like memory content leaking that does not cross the user/kernel privilege boundary. \n \nThe Linux kernel mitigations for Meltdown are referred to as KAISER, and subsequently KPTI, which aim to improve separation of kernel and user memory pages. Because the Spectre attacks do not cross user/kernel boundaries, the protections introduced with KAISER/KPTI do not add any protection against them. \n \nThe following table compares Spectre and Meltdown. \n \n| | **Spectre**| **Meltdown** \n---|---|--- \n**CPU mechanism for triggering**| Speculative execution from branch prediction| Out-of-order execution \n**Affected platforms**| CPUs that perform speculative execution from branch prediction| CPUs that allow memory reads in out-of-order instructions \n**Difficulty of successful attack**| High - Requires tailoring to the software environment of the victim process| Low - Kernel memory access exploit code is mostly universal \n**Impact**| Cross- and intra-process (including kernel) memory disclosure| Kernel memory disclosure to userspace \n**Software mitigations**| Indirect Branch Restricted Speculation ([IBRS](<https://lkml.org/lkml/2018/1/4/615>)) \n**Note: **This software mitigation also requires CPU microcode updates and it only mitigates Spectre variant 2| Kernel page-table isolation ([KPTI](<https://en.wikipedia.org/wiki/Kernel_page-table_isolation>)) \n \n### Impact\n\nAn attacker able to execute code with user privileges can achieve various impacts. The Meltdown attack allows reading of kernel memory from userspace. This can result in privilege escalation, disclosure of sensitive information, or it can weaken kernel-level protections, such as KASLR. The Spectre attack can allow inter-process or intra-process data leaks. \n \nTo execute code locally, an attacker would require a valid account or independent compromise of the target. Attacks using JavaScript in web browsers are possible. Multi-user and multi-tenant systems (including virtualized and cloud environments) likely face the greatest risk. Systems used to browse arbitrary web sites are also at risk. Single-user systems that do not readily provide a way for attackers to execute code locally face significantly lower risk. \n \n--- \n \n### Solution\n\n**Apply updates** \n \nOperating system, CPU microcode updates, and some application updates mitigate these attacks. \n \n--- \n \n### Vendor Information \n\nVendor| Status| Date Notified| Date Updated \n---|---|---|--- \nAmazon| | -| 05 Jan 2018 \nAMD| | -| 03 Jan 2018 \nAndroid Open Source Project| | -| 05 Jan 2018 \nApple| | -| 08 Jan 2018 \nArm| | -| 03 Jan 2018 \nCentOS| | -| 05 Jan 2018 \nCisco| | -| 05 Jan 2018 \nCitrix| | -| 05 Jan 2018 \nDebian GNU/Linux| | -| 05 Jan 2018 \nDell| | -| 08 Jan 2018 \nDragonFly BSD Project| | -| 08 Jan 2018 \nFedora Project| | -| 05 Jan 2018 \nFortinet, Inc.| | -| 05 Jan 2018 \nFreeBSD Project| | -| 05 Jan 2018 \nGoogle| | -| 03 Jan 2018 \nIf you are a vendor and your product is affected, [let us know](<mailto:cert@cert.org?Subject=VU%23584653 Vendor Status Inquiry>). \n \n\n\n### CVSS Metrics \n\nGroup | Score | Vector \n---|---|--- \nBase | 4.4 | AV:L/AC:M/Au:S/C:C/I:N/A:N \nTemporal | 3.4 | E:POC/RL:OF/RC:C \nEnvironmental | 5.1 | CDP:ND/TD:H/CR:H/IR:ND/AR:ND \n \n### References\n\n * <https://meltdownattack.com/>\n * <https://meltdownattack.com/meltdown.pdf>\n * <https://spectreattack.com/>\n * <https://spectreattack.com/spectre.pdf>\n * <https://security.googleblog.com/2018/01/todays-cpu-vulnerability-what-you-need.html>\n * <https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html>\n * <https://cyber.wtf/2017/07/28/negative-result-reading-kernel-memory-from-user-mode/>\n * <https://github.com/IAIK/KAISER>\n * <https://gruss.cc/files/kaiser.pdf>\n * <https://gruss.cc/files/prefetch.pdf>\n * <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5aa90a84589282b87666f92b6c3c917c8080a9bf>\n * <https://lkml.org/lkml/2017/12/27/2>\n * <https://lkml.org/lkml/2018/1/4/615>\n * <https://lwn.net/Articles/741878/>\n * <https://lwn.net/Articles/737940/>\n * <https://lwn.net/Articles/742702/>\n * <http://pythonsweetness.tumblr.com/post/169166980422/the-mysterious-case-of-the-linux-page-table>\n * <https://nakedsecurity.sophos.com/2018/01/03/fckwit-aka-kaiser-aka-kpti-intel-cpu-flaw-needs-low-level-os-patches/>\n * <https://en.wikipedia.org/wiki/Kernel_page-table_isolation>\n * <https://chrisam.net/2018/01/04/speculative-execution-side-channel-vulnerabilities-vendor-published-info/>\n * <https://www.raspberrypi.org/blog/why-raspberry-pi-isnt-vulnerable-to-spectre-or-meltdown/>\n * <https://doublepulsar.com/important-information-about-microsoft-meltdown-cpu-security-fixes-antivirus-vendors-and-you-a852ba0292ec>\n * [https://docs.google.com/spreadsheets/d/184wcDt9I9TUNFFbsAVLpzAtckQxYiuirADzf3cL42FQ/htmlview?usp=sharing&sle;=true](<https://docs.google.com/spreadsheets/d/184wcDt9I9TUNFFbsAVLpzAtckQxYiuirADzf3cL42FQ/htmlview?usp=sharing&sle=true>)\n\n### Credit\n\nThese issues were researched and reported by researchers at Google Project Zero (Jann Horn) the Institute of Applied Information Processing and Communications (IAIK) at Graz University of Technology (Gruss et. al.), Paul Kocher, and Anders Fogh.\n\nThis document was written by Art Manion and Will Dormann.\n\n### Other Information\n\n * CVE IDs: [CVE-2017-5753](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5753>) [CVE-2017-5715](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5715>) [CVE-2017-5754](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5754>)\n * US-CERT Alert: [TA18-004A](<http://www.us-cert.gov/cas/techalerts/TA18-004A.html>)\n * Date Public: 03 Jan 2018\n * Date First Published: 03 Jan 2018\n * Date Last Updated: 09 Jan 2018\n * Document Revision: 185\n\n", "published": "2018-01-03T00:00:00", "modified": "2018-01-09T00:00:00", "cvss": {"score": 4.7, "vector": "AV:LOCAL/AC:MEDIUM/Au:NONE/C:COMPLETE/I:NONE/A:NONE/"}, "href": "https://www.kb.cert.org/vuls/id/584653", "reporter": "CERT", "references": ["https://meltdownattack.com/meltdown.pdf", "https://meltdownattack.com/meltdown.pdf", "https://docs.google.com/spreadsheets/d/184wcDt9I9TUNFFbsAVLpzAtckQxYiuirADzf3cL42FQ/htmlview?usp=sharing&sle=true", "https://lwn.net/Articles/742702/", "https://nakedsecurity.sophos.com/2018/01/03/fckwit-aka-kaiser-aka-kpti-intel-cpu-flaw-needs-low-level-os-patches/", "https://www.raspberrypi.org/blog/why-raspberry-pi-isnt-vulnerable-to-spectre-or-meltdown/", "https://lkml.org/lkml/2017/12/27/2", "https://security.googleblog.com/2018/01/todays-cpu-vulnerability-what-you-need.html", "https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html", "https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html", "https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html", "http://pythonsweetness.tumblr.com/post/169166980422/the-mysterious-case-of-the-linux-page-table", "https://gruss.cc/files/kaiser.pdf", "https://doublepulsar.com/important-information-about-microsoft-meltdown-cpu-security-fixes-antivirus-vendors-and-you-a852ba0292ec", "http://www.us-cert.gov/cas/techalerts/TA18-004A.html", "https://chrisam.net/2018/01/04/speculative-execution-side-channel-vulnerabilities-vendor-published-info/", "https://meltdownattack.com/", "https://meltdownattack.com/", "https://meltdownattack.com/", "https://en.wikipedia.org/wiki/Kernel_page-table_isolation", "https://en.wikipedia.org/wiki/Kernel_page-table_isolation", "http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5753", "https://spectreattack.com/", "https://spectreattack.com/", "https://spectreattack.com/", "https://lwn.net/Articles/737940/", "http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5715", "https://lkml.org/lkml/2018/1/4/615", "https://lkml.org/lkml/2018/1/4/615", "https://github.com/IAIK/KAISER", "https://cyber.wtf/2017/07/28/negative-result-reading-kernel-memory-from-user-mode/", "https://lwn.net/Articles/741878/", "https://gruss.cc/files/prefetch.pdf", "https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5aa90a84589282b87666f92b6c3c917c8080a9bf", "http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5754", "https://spectreattack.com/spectre.pdf", "https://spectreattack.com/spectre.pdf", "https://spectreattack.com/spectre.pdf", "https://spectreattack.com/spectre.pdf"], "cvelist": ["CVE-2017-5753", "CVE-2017-5753", "CVE-2017-5753", "CVE-2017-5753", "CVE-2017-5754", "CVE-2017-5754", "CVE-2017-5754", "CVE-2017-5715", "CVE-2017-5715", "CVE-2017-5715", "CVE-2017-5715"], "lastseen": "2018-01-09T20:53:56", "history": [], "viewCount": 169, "enchantments": {"score": {"modified": "2018-01-09T20:53:56", "value": 6.6}}, "objectVersion": "1.4"}, "lastseen": "2018-01-09T20:53:56", "differentElements": ["description", "references"], "edition": 14}, {"bulletin": {"id": "VU:584653", "hash": "c5274678fb7f7ecd4e89cf77723a0e00d8efe8117cb665571080eb5af9b20580", "type": "cert", "bulletinFamily": "info", "title": "CPU hardware vulnerable to side-channel attacks", "description": "### Overview\n\nCPU hardware implementations are vulnerable to cache side-channel attacks. These vulnerabilities are referred to as [Meltdown](<https://meltdownattack.com/>) and [Spectre](<https://spectreattack.com/>).\n\n### Description\n\n**Note: This Vulnerability Note is the product of ongoing analysis and represents our best knowledge as of the most recent revision. As a result, the content may change as our understanding of the issues develops.**\n\nCPU hardware implementations are vulnerable to side-channel attacks referred to as [Meltdown](<https://meltdownattack.com/>) and [Spectre](<https://spectreattack.com/>). Both Spectre and Meltdown take advantage of the ability to extract information from instructions that have executed on a CPU using the CPU cache as a side-channel. These attacks are described in detail by [Google Project Zero](<https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html>), the Institute of Applied Information Processing and Communications (IAIK) at Graz University of Technology (TU Graz) and Anders Fogh. The issues are organized into three variants: \n\n\n * Variant 1 (CVE-2017-5753, [Spectre](<https://spectreattack.com/spectre.pdf>)): Bounds check bypass\n * Variant 2 (CVE-2017-5715, also [Spectre](<https://spectreattack.com/spectre.pdf>)): Branch target injection[](<https://spectreattack.com/spectre.pdf>)\n * Variant 3 (CVE-2017-5754, [Meltdown](<https://meltdownattack.com/meltdown.pdf>)): Rogue data cache load, memory access permission check performed after kernel memory read\n \n**Spectre** \n \nSpectre attacks take advantage of a CPU's branch prediction capabilities. Modern CPUs include a feature called branch prediction, which speculatively executes instructions at a location that the CPU believes it will branch to. Such speculative execution helps to more fully utilize the parts of the CPU, minimizing the time waiting, and therefore improving performance. When a branch is successfully predicted, instructions will retire, which means the outcomes of the instructions such as register and memory writes will be committed. If a branch is mispredicted, the speculatively-executed instructions will be discarded, and the direct side-effects of the instructions are undone. What is not undone are the indirect side-effects, such as CPU cache changes. By measuring latency of memory access operations, the cache can be used to extract values from speculatively-executed instructions. \n \nWith Spectre variant 1 (CVE-2017-5753), the instructions after a conditional branch are speculatively executed as the result of a misprediction. With Spectre variant 2 (CVE-2017-5715), the CPU executes instructions at a location determined by a mispredicted branch target. \n \nWith both variants of the Spectre attack, the impact is that a process may leak sensitive data to other processes on a system. Spectre may also allow one part of an application to access other parts of the same process memory space that would otherwise not be permitted. \n \nWhile the Spectre attack itself does not cross a user/kernel memory privilege boundary, depending on the configuration of the target platform, the Spectre attack may indirectly allow a user-space application to access kernel memory. For example, the[ Project Zero blog post](<https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html>) describes a scenario that uses eBPF to exfiltrate kernel memory contents into user-space code. This is made possible because eBPF JIT allows for userspace applications to inject code that is executed in kernel space. While this code is verified by the kernel, eBPF-compliant code will be allowed to execute with kernel permissions. The exploit described by Project Zero leverages eBPF to execute the Spectre attack in kernel space, while exfiltrating the data to user space. It is possible that other technologies that allow in-kernel code execution may also possibly be leveraged to leak kernel memory using Spectre. \n \n**Meltdown** \n \nMeltdown is related to the Spectre attack in that it also uses a cache side channel to access data that otherwise wouldn't be available. The main difference is that it leverages out-of-order execution capabilities in modern CPUs. Like speculative execution due to branch prediction, as used by Spectre, out-of-order execution on a CPU is a technique for ensuring fullest utilization of the CPU's parts. Although instructions may appear sequentially in the machine language, a CPU that supports out-of-order execution may execute instructions in a non-sequential manner, which can minimize the time that a CPU spends idle. \n \nMeltdown leverages insecure behavior that has been demonstrated in Intel CPUs and may affect CPUs from other vendors. Vulnerable CPUs allow memory reads in out-of-order instruction execution, and also contain a race condition between the raising of exceptions and the out-of-order instruction execution. The Meltdown attack reads a kernel memory value, which raises an exception because code running with user-space privileges are not permitted to directly read kernel memory. However, due to the race condition, out-of-order instructions following the faulting instruction may also execute. Even though instructions appear after the faulting instruction, out-of-order execution allows them to execute, using data retrieved from the instruction that raises the exception. By the time the exception is raised, some number of out-of-order instructions have executed. Although the raised exception causes the CPU to roll back the out-of-order instructions, the cache state is not reverted. This allows data from out-of-order instructions to persist beyond the point when the exception has been raised. \n \nThe impact of Meltdown is that a process running in user space is able to view the contents of kernel memory. Meltdown may also allow Spectre-like memory content leaking that does not cross the user/kernel privilege boundary. \n \nThe Linux kernel mitigations for Meltdown are referred to as KAISER, and subsequently KPTI, which aim to improve separation of kernel and user memory pages. Because the Spectre attacks do not cross user/kernel boundaries, the protections introduced with KAISER/KPTI do not add any protection against them. \n \nThe following table compares Spectre and Meltdown. \n \n| | **Spectre**| **Meltdown** \n---|---|--- \n**CPU mechanism for triggering**| Speculative execution from branch prediction| Out-of-order execution \n**Affected platforms**| CPUs that perform speculative execution from branch prediction| CPUs that allow memory reads in out-of-order instructions \n**Difficulty of successful attack**| High - Requires tailoring to the software environment of the victim process| Low - Kernel memory access exploit code is mostly universal \n**Impact**| Cross- and intra-process (including kernel) memory disclosure| Kernel memory disclosure to userspace \n**Software mitigations**| Variant 1: Compiler changes. Web browser updates to help prevent exploitation from JavaScript \nVariant 2: Indirect Branch Restricted Speculation ([IBRS](<https://lkml.org/lkml/2018/1/4/615>)). \n**Note: **The software mitigation for Spectre variant 2 requires CPU microcode updates| Kernel page-table isolation ([KPTI](<https://en.wikipedia.org/wiki/Kernel_page-table_isolation>)) \n \n### Impact\n\nAn attacker able to execute code with user privileges can achieve various impacts. The Meltdown attack allows reading of kernel memory from userspace. This can result in privilege escalation, disclosure of sensitive information, or it can weaken kernel-level protections, such as KASLR. The Spectre attack can allow inter-process or intra-process data leaks. \n \nTo execute code locally, an attacker would require a valid account or independent compromise of the target. Attacks using JavaScript in web browsers are possible. Multi-user and multi-tenant systems (including virtualized and cloud environments) likely face the greatest risk. Systems used to browse arbitrary web sites are also at risk. Single-user systems that do not readily provide a way for attackers to execute code locally face significantly lower risk. \n \n--- \n \n### Solution\n\n**Apply updates** \n \nOperating system, CPU microcode updates, and some application updates mitigate these attacks. Note that in many cases, the software fixes for these vulnerabilities will have a negative affect on system performance. Also note that Microsoft Windows systems [will no longer receive security updates](<https://doublepulsar.com/important-information-about-microsoft-meltdown-cpu-security-fixes-antivirus-vendors-and-you-a852ba0292ec>) via Windows Update if they are not running compliant anti-virus software. As with deploying any software updates, be sure to prioritize and test updates as necessary. \n \n--- \n \n### Vendor Information \n\nVendor| Status| Date Notified| Date Updated \n---|---|---|--- \nAmazon| | -| 05 Jan 2018 \nAMD| | -| 03 Jan 2018 \nAndroid Open Source Project| | -| 05 Jan 2018 \nApple| | -| 08 Jan 2018 \nArm| | -| 03 Jan 2018 \nCentOS| | -| 05 Jan 2018 \nCisco| | -| 05 Jan 2018 \nCitrix| | -| 05 Jan 2018 \nDebian GNU/Linux| | -| 05 Jan 2018 \nDell| | -| 08 Jan 2018 \nDragonFly BSD Project| | -| 08 Jan 2018 \nFedora Project| | -| 05 Jan 2018 \nFortinet, Inc.| | -| 05 Jan 2018 \nFreeBSD Project| | -| 05 Jan 2018 \nGoogle| | -| 03 Jan 2018 \nIf you are a vendor and your product is affected, [let us know](<mailto:cert@cert.org?Subject=VU%23584653 Vendor Status Inquiry>). \n \n\n\n### CVSS Metrics \n\nGroup | Score | Vector \n---|---|--- \nBase | 4.4 | AV:L/AC:M/Au:S/C:C/I:N/A:N \nTemporal | 3.4 | E:POC/RL:OF/RC:C \nEnvironmental | 5.1 | CDP:ND/TD:H/CR:H/IR:ND/AR:ND \n \n### References\n\n * <https://meltdownattack.com/>\n * <https://meltdownattack.com/meltdown.pdf>\n * <https://spectreattack.com/>\n * <https://spectreattack.com/spectre.pdf>\n * <https://security.googleblog.com/2018/01/todays-cpu-vulnerability-what-you-need.html>\n * <https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html>\n * <https://cyber.wtf/2017/07/28/negative-result-reading-kernel-memory-from-user-mode/>\n * <https://github.com/IAIK/KAISER>\n * <https://gruss.cc/files/kaiser.pdf>\n * <https://gruss.cc/files/prefetch.pdf>\n * <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5aa90a84589282b87666f92b6c3c917c8080a9bf>\n * <https://lkml.org/lkml/2017/12/27/2>\n * <https://lkml.org/lkml/2018/1/4/615>\n * <https://lwn.net/Articles/741878/>\n * <https://lwn.net/Articles/737940/>\n * <https://lwn.net/Articles/742702/>\n * <http://pythonsweetness.tumblr.com/post/169166980422/the-mysterious-case-of-the-linux-page-table>\n * <https://nakedsecurity.sophos.com/2018/01/03/fckwit-aka-kaiser-aka-kpti-intel-cpu-flaw-needs-low-level-os-patches/>\n * <https://en.wikipedia.org/wiki/Kernel_page-table_isolation>\n * <https://chrisam.net/2018/01/04/speculative-execution-side-channel-vulnerabilities-vendor-published-info/>\n * <https://www.raspberrypi.org/blog/why-raspberry-pi-isnt-vulnerable-to-spectre-or-meltdown/>\n * <https://doublepulsar.com/important-information-about-microsoft-meltdown-cpu-security-fixes-antivirus-vendors-and-you-a852ba0292ec>\n * [https://docs.google.com/spreadsheets/d/184wcDt9I9TUNFFbsAVLpzAtckQxYiuirADzf3cL42FQ/htmlview?usp=sharing&sle;=true](<https://docs.google.com/spreadsheets/d/184wcDt9I9TUNFFbsAVLpzAtckQxYiuirADzf3cL42FQ/htmlview?usp=sharing&sle=true>)\n\n### Credit\n\nThese issues were researched and reported by researchers at Google Project Zero (Jann Horn) the Institute of Applied Information Processing and Communications (IAIK) at Graz University of Technology (Gruss et. al.), Paul Kocher, and Anders Fogh.\n\nThis document was written by Art Manion and Will Dormann.\n\n### Other Information\n\n * CVE IDs: [CVE-2017-5753](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5753>) [CVE-2017-5715](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5715>) [CVE-2017-5754](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5754>)\n * US-CERT Alert: [TA18-004A](<http://www.us-cert.gov/cas/techalerts/TA18-004A.html>)\n * Date Public: 03 Jan 2018\n * Date First Published: 03 Jan 2018\n * Date Last Updated: 09 Jan 2018\n * Document Revision: 203\n\n", "published": "2018-01-03T00:00:00", "modified": "2018-01-09T00:00:00", "cvss": {"score": 4.7, "vector": "AV:LOCAL/AC:MEDIUM/Au:NONE/C:COMPLETE/I:NONE/A:NONE/"}, "href": "https://www.kb.cert.org/vuls/id/584653", "reporter": "CERT", "references": ["https://meltdownattack.com/meltdown.pdf", "https://meltdownattack.com/meltdown.pdf", "https://docs.google.com/spreadsheets/d/184wcDt9I9TUNFFbsAVLpzAtckQxYiuirADzf3cL42FQ/htmlview?usp=sharing&sle=true", "https://lwn.net/Articles/742702/", "https://nakedsecurity.sophos.com/2018/01/03/fckwit-aka-kaiser-aka-kpti-intel-cpu-flaw-needs-low-level-os-patches/", "https://www.raspberrypi.org/blog/why-raspberry-pi-isnt-vulnerable-to-spectre-or-meltdown/", "https://lkml.org/lkml/2017/12/27/2", "https://security.googleblog.com/2018/01/todays-cpu-vulnerability-what-you-need.html", "https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html", "https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html", "https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html", "http://pythonsweetness.tumblr.com/post/169166980422/the-mysterious-case-of-the-linux-page-table", "https://gruss.cc/files/kaiser.pdf", "https://doublepulsar.com/important-information-about-microsoft-meltdown-cpu-security-fixes-antivirus-vendors-and-you-a852ba0292ec", "https://doublepulsar.com/important-information-about-microsoft-meltdown-cpu-security-fixes-antivirus-vendors-and-you-a852ba0292ec", "http://www.us-cert.gov/cas/techalerts/TA18-004A.html", "https://chrisam.net/2018/01/04/speculative-execution-side-channel-vulnerabilities-vendor-published-info/", "https://meltdownattack.com/", "https://meltdownattack.com/", "https://meltdownattack.com/", "https://en.wikipedia.org/wiki/Kernel_page-table_isolation", "https://en.wikipedia.org/wiki/Kernel_page-table_isolation", "http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5753", "https://spectreattack.com/", "https://spectreattack.com/", "https://spectreattack.com/", "https://lwn.net/Articles/737940/", "http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5715", "https://lkml.org/lkml/2018/1/4/615", "https://lkml.org/lkml/2018/1/4/615", "https://github.com/IAIK/KAISER", "https://cyber.wtf/2017/07/28/negative-result-reading-kernel-memory-from-user-mode/", "https://lwn.net/Articles/741878/", "https://gruss.cc/files/prefetch.pdf", "https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5aa90a84589282b87666f92b6c3c917c8080a9bf", "http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5754", "https://spectreattack.com/spectre.pdf", "https://spectreattack.com/spectre.pdf", "https://spectreattack.com/spectre.pdf", "https://spectreattack.com/spectre.pdf"], "cvelist": ["CVE-2017-5753", "CVE-2017-5753", "CVE-2017-5753", "CVE-2017-5753", "CVE-2017-5754", "CVE-2017-5754", "CVE-2017-5754", "CVE-2017-5715", "CVE-2017-5715", "CVE-2017-5715", "CVE-2017-5715"], "lastseen": "2018-01-10T02:54:38", "history": [], "viewCount": 179, "enchantments": {"score": {"modified": "2018-01-10T02:54:38", "value": 6.6}}, "objectVersion": "1.4"}, "lastseen": "2018-01-10T02:54:38", "differentElements": ["description", "modified"], "edition": 15}, {"bulletin": {"id": "VU:584653", "hash": "32d7873203cab2ff031146664f7be0a7e38c7e62dfdfa1ac6010166afed412ca", "type": "cert", "bulletinFamily": "info", "title": "CPU hardware vulnerable to side-channel attacks", "description": "### Overview\n\nCPU hardware implementations are vulnerable to cache side-channel attacks. These vulnerabilities are referred to as [Meltdown](<https://meltdownattack.com/>) and [Spectre](<https://spectreattack.com/>).\n\n### Description\n\n**Note: This Vulnerability Note is the product of ongoing analysis and represents our best knowledge as of the most recent revision. As a result, the content may change as our understanding of the issues develops.**\n\nCPU hardware implementations are vulnerable to side-channel attacks referred to as [Meltdown](<https://meltdownattack.com/>) and [Spectre](<https://spectreattack.com/>). Both Spectre and Meltdown take advantage of the ability to extract information from instructions that have executed on a CPU using the CPU cache as a side-channel. These attacks are described in detail by [Google Project Zero](<https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html>), the Institute of Applied Information Processing and Communications (IAIK) at Graz University of Technology (TU Graz) and Anders Fogh. The issues are organized into three variants: \n\n\n * Variant 1 (CVE-2017-5753, [Spectre](<https://spectreattack.com/spectre.pdf>)): Bounds check bypass\n * Variant 2 (CVE-2017-5715, also [Spectre](<https://spectreattack.com/spectre.pdf>)): Branch target injection[](<https://spectreattack.com/spectre.pdf>)\n * Variant 3 (CVE-2017-5754, [Meltdown](<https://meltdownattack.com/meltdown.pdf>)): Rogue data cache load, memory access permission check performed after kernel memory read\n \n**Spectre** \n \nSpectre attacks take advantage of a CPU's branch prediction capabilities. Modern CPUs include a feature called branch prediction, which speculatively executes instructions at a location that the CPU believes it will branch to. Such speculative execution helps to more fully utilize the parts of the CPU, minimizing the time waiting, and therefore improving performance. When a branch is successfully predicted, instructions will retire, which means the outcomes of the instructions such as register and memory writes will be committed. If a branch is mispredicted, the speculatively-executed instructions will be discarded, and the direct side-effects of the instructions are undone. What is not undone are the indirect side-effects, such as CPU cache changes. By measuring latency of memory access operations, the cache can be used to extract values from speculatively-executed instructions. \n \nWith Spectre variant 1 (CVE-2017-5753), the instructions after a conditional branch are speculatively executed as the result of a misprediction. With Spectre variant 2 (CVE-2017-5715), the CPU executes instructions at a location determined by a mispredicted branch target. \n \nWith both variants of the Spectre attack, the impact is that a process may leak sensitive data to other processes on a system. Spectre may also allow one part of an application to access other parts of the same process memory space that would otherwise not be permitted. \n \nWhile the Spectre attack itself does not cross a user/kernel memory privilege boundary, depending on the configuration of the target platform, the Spectre attack may indirectly allow a user-space application to access kernel memory. For example, the[ Project Zero blog post](<https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html>) describes a scenario that uses eBPF to exfiltrate kernel memory contents into user-space code. This is made possible because eBPF JIT allows for userspace applications to inject code that is executed in kernel space. While this code is verified by the kernel, eBPF-compliant code will be allowed to execute with kernel permissions. The exploit described by Project Zero leverages eBPF to execute the Spectre attack in kernel space, while exfiltrating the data to user space. It is possible that other technologies that allow in-kernel code execution may also possibly be leveraged to leak kernel memory using Spectre. \n \n**Meltdown** \n \nMeltdown is related to the Spectre attack in that it also uses a cache side channel to access data that otherwise wouldn't be available. The main difference is that it leverages out-of-order execution capabilities in modern CPUs. Like speculative execution due to branch prediction, as used by Spectre, out-of-order execution on a CPU is a technique for ensuring fullest utilization of the CPU's parts. Although instructions may appear sequentially in the machine language, a CPU that supports out-of-order execution may execute instructions in a non-sequential manner, which can minimize the time that a CPU spends idle. \n \nMeltdown leverages insecure behavior that has been demonstrated in Intel CPUs and may affect CPUs from other vendors. Vulnerable CPUs allow memory reads in out-of-order instruction execution, and also contain a race condition between the raising of exceptions and the out-of-order instruction execution. The Meltdown attack reads a kernel memory value, which raises an exception because code running with user-space privileges are not permitted to directly read kernel memory. However, due to the race condition, out-of-order instructions following the faulting instruction may also execute. Even though instructions appear after the faulting instruction, out-of-order execution allows them to execute, using data retrieved from the instruction that raises the exception. By the time the exception is raised, some number of out-of-order instructions have executed. Although the raised exception causes the CPU to roll back the out-of-order instructions, the cache state is not reverted. This allows data from out-of-order instructions to persist beyond the point when the exception has been raised. \n \nThe impact of Meltdown is that a process running in user space is able to view the contents of kernel memory. Meltdown may also allow Spectre-like memory content leaking that does not cross the user/kernel privilege boundary. \n \nThe Linux kernel mitigations for Meltdown are referred to as KAISER, and subsequently KPTI, which aim to improve separation of kernel and user memory pages. Because the Spectre attacks do not cross user/kernel boundaries, the protections introduced with KAISER/KPTI do not add any protection against them. \n \nThe following table compares Spectre and Meltdown. \n \n| | **Spectre**| **Meltdown** \n---|---|--- \n**CPU mechanism for triggering**| Speculative execution from branch prediction| Out-of-order execution \n**Affected platforms**| CPUs that perform speculative execution from branch prediction| CPUs that allow memory reads in out-of-order instructions \n**Difficulty of successful attack**| High - Requires tailoring to the software environment of the victim process| Low - Kernel memory access exploit code is mostly universal \n**Impact**| Cross- and intra-process (including kernel) memory disclosure| Kernel memory disclosure to userspace \n**Software mitigations**| Variant 1: Compiler changes. Web browser updates to help prevent exploitation from JavaScript \nVariant 2: Indirect Branch Restricted Speculation ([IBRS](<https://lkml.org/lkml/2018/1/4/615>)). \n**Note: **The software mitigation for Spectre variant 2 requires CPU microcode updates| Kernel page-table isolation ([KPTI](<https://en.wikipedia.org/wiki/Kernel_page-table_isolation>)) \n \n### Impact\n\nAn attacker able to execute code with user privileges can achieve various impacts. The Meltdown attack allows reading of kernel memory from userspace. This can result in privilege escalation, disclosure of sensitive information, or it can weaken kernel-level protections, such as KASLR. The Spectre attack can allow inter-process or intra-process data leaks. \n \nTo execute code locally, an attacker would require a valid account or independent compromise of the target. Attacks using JavaScript in web browsers are possible. Multi-user and multi-tenant systems (including virtualized and cloud environments) likely face the greatest risk. Systems used to browse arbitrary web sites are also at risk. Single-user systems that do not readily provide a way for attackers to execute code locally face significantly lower risk. \n \n--- \n \n### Solution\n\n**Apply updates** \n \nOperating system, CPU microcode updates, and some application updates mitigate these attacks. Note that in many cases, the software fixes for these vulnerabilities will have a negative affect on system performance. Also note that Microsoft Windows systems [will no longer receive security updates](<https://doublepulsar.com/important-information-about-microsoft-meltdown-cpu-security-fixes-antivirus-vendors-and-you-a852ba0292ec>) via Windows Update if they are not running compliant anti-virus software. As with deploying any software updates, be sure to prioritize and test updates as necessary. \n \n**Consider CPU Options** \n \nInitial reports from the field indicate that overall system performance is impacted by many of the available patches for these vulnerabilities. Depending on the software workflow and the CPU capabilities present, the performance impact of software mitigations may be non-trivial and therefore may become an ongoing operational concern for some organizations. While we recognize that replacing existing CPUs in already deployed systems is not practical, organizations acquiring new systems should evaluate their CPU selection in light of the expected longevity of this vulnerability in available hardware as well as the performance impacts resulting from the various platform-specific software patches. Deployment contexts and performance requirements vary widely, and must be balanced by informed evaluation of the associated security risks. Contact your system vendor to determine if the CPU and operating system combination will experience a performance penalty due to software mitigations for these vulnerabilities. \n \n--- \n \n### Vendor Information \n\nVendor| Status| Date Notified| Date Updated \n---|---|---|--- \nAmazon| | -| 05 Jan 2018 \nAMD| | -| 03 Jan 2018 \nAndroid Open Source Project| | -| 05 Jan 2018 \nApple| | -| 08 Jan 2018 \nArm| | -| 03 Jan 2018 \nCentOS| | -| 05 Jan 2018 \nCisco| | -| 05 Jan 2018 \nCitrix| | -| 05 Jan 2018 \nDebian GNU/Linux| | -| 05 Jan 2018 \nDell| | -| 08 Jan 2018 \nDragonFly BSD Project| | -| 08 Jan 2018 \nFedora Project| | -| 05 Jan 2018 \nFortinet, Inc.| | -| 05 Jan 2018 \nFreeBSD Project| | -| 05 Jan 2018 \nFujitsu| | -| 11 Jan 2018 \nIf you are a vendor and your product is affected, [let us know](<mailto:cert@cert.org?Subject=VU%23584653 Vendor Status Inquiry>). \n \n\n\n### CVSS Metrics \n\nGroup | Score | Vector \n---|---|--- \nBase | 4.4 | AV:L/AC:M/Au:S/C:C/I:N/A:N \nTemporal | 3.4 | E:POC/RL:OF/RC:C \nEnvironmental | 5.1 | CDP:ND/TD:H/CR:H/IR:ND/AR:ND \n \n### References\n\n * <https://meltdownattack.com/>\n * <https://meltdownattack.com/meltdown.pdf>\n * <https://spectreattack.com/>\n * <https://spectreattack.com/spectre.pdf>\n * <https://security.googleblog.com/2018/01/todays-cpu-vulnerability-what-you-need.html>\n * <https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html>\n * <https://cyber.wtf/2017/07/28/negative-result-reading-kernel-memory-from-user-mode/>\n * <https://github.com/IAIK/KAISER>\n * <https://gruss.cc/files/kaiser.pdf>\n * <https://gruss.cc/files/prefetch.pdf>\n * <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5aa90a84589282b87666f92b6c3c917c8080a9bf>\n * <https://lkml.org/lkml/2017/12/27/2>\n * <https://lkml.org/lkml/2018/1/4/615>\n * <https://lwn.net/Articles/741878/>\n * <https://lwn.net/Articles/737940/>\n * <https://lwn.net/Articles/742702/>\n * <http://pythonsweetness.tumblr.com/post/169166980422/the-mysterious-case-of-the-linux-page-table>\n * <https://nakedsecurity.sophos.com/2018/01/03/fckwit-aka-kaiser-aka-kpti-intel-cpu-flaw-needs-low-level-os-patches/>\n * <https://en.wikipedia.org/wiki/Kernel_page-table_isolation>\n * <https://chrisam.net/2018/01/04/speculative-execution-side-channel-vulnerabilities-vendor-published-info/>\n * <https://www.raspberrypi.org/blog/why-raspberry-pi-isnt-vulnerable-to-spectre-or-meltdown/>\n * <https://doublepulsar.com/important-information-about-microsoft-meltdown-cpu-security-fixes-antivirus-vendors-and-you-a852ba0292ec>\n * [https://docs.google.com/spreadsheets/d/184wcDt9I9TUNFFbsAVLpzAtckQxYiuirADzf3cL42FQ/htmlview?usp=sharing&sle;=true](<https://docs.google.com/spreadsheets/d/184wcDt9I9TUNFFbsAVLpzAtckQxYiuirADzf3cL42FQ/htmlview?usp=sharing&sle=true>)\n\n### Credit\n\nThese issues were researched and reported by researchers at Google Project Zero (Jann Horn) the Institute of Applied Information Processing and Communications (IAIK) at Graz University of Technology (Gruss et. al.), Paul Kocher, and Anders Fogh.\n\nThis document was written by Art Manion and Will Dormann.\n\n### Other Information\n\n * CVE IDs: [CVE-2017-5753](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5753>) [CVE-2017-5715](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5715>) [CVE-2017-5754](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5754>)\n * US-CERT Alert: [TA18-004A](<http://www.us-cert.gov/cas/techalerts/TA18-004A.html>)\n * Date Public: 03 Jan 2018\n * Date First Published: 03 Jan 2018\n * Date Last Updated: 22 Jan 2018\n * Document Revision: 209\n\n", "published": "2018-01-03T00:00:00", "modified": "2018-01-22T00:00:00", "cvss": {"score": 4.7, "vector": "AV:LOCAL/AC:MEDIUM/Au:NONE/C:COMPLETE/I:NONE/A:NONE/"}, "href": "https://www.kb.cert.org/vuls/id/584653", "reporter": "CERT", "references": ["https://meltdownattack.com/meltdown.pdf", "https://meltdownattack.com/meltdown.pdf", "https://docs.google.com/spreadsheets/d/184wcDt9I9TUNFFbsAVLpzAtckQxYiuirADzf3cL42FQ/htmlview?usp=sharing&sle=true", "https://lwn.net/Articles/742702/", "https://nakedsecurity.sophos.com/2018/01/03/fckwit-aka-kaiser-aka-kpti-intel-cpu-flaw-needs-low-level-os-patches/", "https://www.raspberrypi.org/blog/why-raspberry-pi-isnt-vulnerable-to-spectre-or-meltdown/", "https://lkml.org/lkml/2017/12/27/2", "https://security.googleblog.com/2018/01/todays-cpu-vulnerability-what-you-need.html", "https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html", "https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html", "https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html", "http://pythonsweetness.tumblr.com/post/169166980422/the-mysterious-case-of-the-linux-page-table", "https://gruss.cc/files/kaiser.pdf", "https://doublepulsar.com/important-information-about-microsoft-meltdown-cpu-security-fixes-antivirus-vendors-and-you-a852ba0292ec", "https://doublepulsar.com/important-information-about-microsoft-meltdown-cpu-security-fixes-antivirus-vendors-and-you-a852ba0292ec", "http://www.us-cert.gov/cas/techalerts/TA18-004A.html", "https://chrisam.net/2018/01/04/speculative-execution-side-channel-vulnerabilities-vendor-published-info/", "https://meltdownattack.com/", "https://meltdownattack.com/", "https://meltdownattack.com/", "https://en.wikipedia.org/wiki/Kernel_page-table_isolation", "https://en.wikipedia.org/wiki/Kernel_page-table_isolation", "http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5753", "https://spectreattack.com/", "https://spectreattack.com/", "https://spectreattack.com/", "https://lwn.net/Articles/737940/", "http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5715", "https://lkml.org/lkml/2018/1/4/615", "https://lkml.org/lkml/2018/1/4/615", "https://github.com/IAIK/KAISER", "https://cyber.wtf/2017/07/28/negative-result-reading-kernel-memory-from-user-mode/", "https://lwn.net/Articles/741878/", "https://gruss.cc/files/prefetch.pdf", "https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5aa90a84589282b87666f92b6c3c917c8080a9bf", "http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5754", "https://spectreattack.com/spectre.pdf", "https://spectreattack.com/spectre.pdf", "https://spectreattack.com/spectre.pdf", "https://spectreattack.com/spectre.pdf"], "cvelist": ["CVE-2017-5753", "CVE-2017-5753", "CVE-2017-5753", "CVE-2017-5753", "CVE-2017-5754", "CVE-2017-5754", "CVE-2017-5754", "CVE-2017-5715", "CVE-2017-5715", "CVE-2017-5715", "CVE-2017-5715"], "lastseen": "2018-01-22T22:09:17", "history": [], "viewCount": 238, "enchantments": {"score": {"modified": "2018-01-22T22:09:17", "value": null}}, "objectVersion": "1.4"}, "lastseen": "2018-01-22T22:09:17", "differentElements": ["description"], "edition": 16}, {"bulletin": {"id": "VU:584653", "hash": "46f56717faf8899ea8992ca6771fafd44727a970a76121249296663f13e751dc", "type": "cert", "bulletinFamily": "info", "title": "CPU hardware vulnerable to side-channel attacks", "description": "### Overview\n\nCPU hardware implementations are vulnerable to cache side-channel attacks. These vulnerabilities are referred to as [Meltdown](<https://meltdownattack.com/>) and [Spectre](<https://spectreattack.com/>).\n\n### Description\n\n**Note: This Vulnerability Note is the product of ongoing analysis and represents our best knowledge as of the most recent revision. As a result, the content may change as our understanding of the issues develops.**\n\nCPU hardware implementations are vulnerable to side-channel attacks referred to as [Meltdown](<https://meltdownattack.com/>) and [Spectre](<https://spectreattack.com/>). Both Spectre and Meltdown take advantage of the ability to extract information from instructions that have executed on a CPU using the CPU cache as a side-channel. These attacks are described in detail by [Google Project Zero](<https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html>), the Institute of Applied Information Processing and Communications (IAIK) at Graz University of Technology (TU Graz) and Anders Fogh. The issues are organized into three variants: \n\n\n * Variant 1 (CVE-2017-5753, [Spectre](<https://spectreattack.com/spectre.pdf>)): Bounds check bypass\n * Variant 2 (CVE-2017-5715, also [Spectre](<https://spectreattack.com/spectre.pdf>)): Branch target injection[](<https://spectreattack.com/spectre.pdf>)\n * Variant 3 (CVE-2017-5754, [Meltdown](<https://meltdownattack.com/meltdown.pdf>)): Rogue data cache load, memory access permission check performed after kernel memory read\n \n**Spectre** \n \nSpectre attacks take advantage of a CPU's branch prediction capabilities. Modern CPUs include a feature called branch prediction, which speculatively executes instructions at a location that the CPU believes it will branch to. Such speculative execution helps to more fully utilize the parts of the CPU, minimizing the time waiting, and therefore improving performance. When a branch is successfully predicted, instructions will retire, which means the outcomes of the instructions such as register and memory writes will be committed. If a branch is mispredicted, the speculatively-executed instructions will be discarded, and the direct side-effects of the instructions are undone. What is not undone are the indirect side-effects, such as CPU cache changes. By measuring latency of memory access operations, the cache can be used to extract values from speculatively-executed instructions. \n \nWith Spectre variant 1 (CVE-2017-5753), the instructions after a conditional branch are speculatively executed as the result of a misprediction. With Spectre variant 2 (CVE-2017-5715), the CPU executes instructions at a location determined by a mispredicted branch target. \n \nWith both variants of the Spectre attack, the impact is that a process may leak sensitive data to other processes on a system. Spectre may also allow one part of an application to access other parts of the same process memory space that would otherwise not be permitted. \n \nWhile the Spectre attack itself does not cross a user/kernel memory privilege boundary, depending on the configuration of the target platform, the Spectre attack may indirectly allow a user-space application to access kernel memory. For example, the[ Project Zero blog post](<https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html>) describes a scenario that uses eBPF to exfiltrate kernel memory contents into user-space code. This is made possible because eBPF JIT allows for userspace applications to inject code that is executed in kernel space. While this code is verified by the kernel, eBPF-compliant code will be allowed to execute with kernel permissions. The exploit described by Project Zero leverages eBPF to execute the Spectre attack in kernel space, while exfiltrating the data to user space. It is possible that other technologies that allow in-kernel code execution may also possibly be leveraged to leak kernel memory using Spectre. \n \n**Meltdown** \n \nMeltdown is related to the Spectre attack in that it also uses a cache side channel to access data that otherwise wouldn't be available. The main difference is that it leverages out-of-order execution capabilities in modern CPUs. Like speculative execution due to branch prediction, as used by Spectre, out-of-order execution on a CPU is a technique for ensuring fullest utilization of the CPU's parts. Although instructions may appear sequentially in the machine language, a CPU that supports out-of-order execution may execute instructions in a non-sequential manner, which can minimize the time that a CPU spends idle. \n \nMeltdown leverages insecure behavior that has been demonstrated in Intel CPUs and may affect CPUs from other vendors. Vulnerable CPUs allow memory reads in out-of-order instruction execution, and also contain a race condition between the raising of exceptions and the out-of-order instruction execution. The Meltdown attack reads a kernel memory value, which raises an exception because code running with user-space privileges are not permitted to directly read kernel memory. However, due to the race condition, out-of-order instructions following the faulting instruction may also execute. Even though instructions appear after the faulting instruction, out-of-order execution allows them to execute, using data retrieved from the instruction that raises the exception. By the time the exception is raised, some number of out-of-order instructions have executed. Although the raised exception causes the CPU to roll back the out-of-order instructions, the cache state is not reverted. This allows data from out-of-order instructions to persist beyond the point when the exception has been raised. \n \nThe impact of Meltdown is that a process running in user space is able to view the contents of kernel memory. Meltdown may also allow Spectre-like memory content leaking that does not cross the user/kernel privilege boundary. \n \nThe Linux kernel mitigations for Meltdown are referred to as KAISER, and subsequently KPTI, which aim to improve separation of kernel and user memory pages. Because the Spectre attacks do not cross user/kernel boundaries, the protections introduced with KAISER/KPTI do not add any protection against them. \n \nThe following table compares Spectre and Meltdown. \n \n| | **Spectre**| **Meltdown** \n---|---|--- \n**CPU mechanism for triggering**| Speculative execution from branch prediction| Out-of-order execution \n**Affected platforms**| CPUs that perform speculative execution from branch prediction| CPUs that allow memory reads in out-of-order instructions \n**Difficulty of successful attack**| High - Requires tailoring to the software environment of the victim process| Low - Kernel memory access exploit code is mostly universal \n**Impact**| Cross- and intra-process (including kernel) memory disclosure| Kernel memory disclosure to userspace \n**Software mitigations**| Variant 1: Compiler changes. Web browser updates to help prevent exploitation from JavaScript \nVariant 2: Indirect Branch Restricted Speculation ([IBRS](<https://lkml.org/lkml/2018/1/4/615>)). \n**Note: **The software mitigation for Spectre variant 2 requires CPU microcode updates| Kernel page-table isolation ([KPTI](<https://en.wikipedia.org/wiki/Kernel_page-table_isolation>)) \n \n### Impact\n\nAn attacker able to execute code with user privileges can achieve various impacts. The Meltdown attack allows reading of kernel memory from userspace. This can result in privilege escalation, disclosure of sensitive information, or it can weaken kernel-level protections, such as KASLR. The Spectre attack can allow inter-process or intra-process data leaks. \n \nTo execute code locally, an attacker would require a valid account or independent compromise of the target. Attacks using JavaScript in web browsers are possible. Multi-user and multi-tenant systems (including virtualized and cloud environments) likely face the greatest risk. Systems used to browse arbitrary web sites are also at risk. Single-user systems that do not readily provide a way for attackers to execute code locally face significantly lower risk. \n \n--- \n \n### Solution\n\n**Apply updates** \n \nOperating system, CPU microcode updates, and some application updates mitigate these attacks. Note that in many cases, the software fixes for these vulnerabilities will have a negative affect on system performance. Also note that Microsoft Windows systems [will no longer receive security updates](<https://doublepulsar.com/important-information-about-microsoft-meltdown-cpu-security-fixes-antivirus-vendors-and-you-a852ba0292ec>) via Windows Update if they are not running compliant anti-virus software. As with deploying any software updates, be sure to prioritize and test updates as necessary. \n \n**Consider CPU Options** \n \nInitial reports from the field indicate that overall system performance is impacted by many of the available patches for these vulnerabilities. Depending on the software workflow and the CPU capabilities present, the performance impact of software mitigations may be non-trivial and therefore may become an ongoing operational concern for some organizations. While we recognize that replacing existing CPUs in already deployed systems is not practical, organizations acquiring new systems should evaluate their CPU selection in light of the expected longevity of this vulnerability in available hardware as well as the performance impacts resulting from the various platform-specific software patches. Deployment contexts and performance requirements vary widely, and must be balanced by informed evaluation of the associated security risks. Contact your system vendor to determine if the CPU and operating system combination will experience a performance penalty due to software mitigations for these vulnerabilities. \n \n--- \n \n### Vendor Information \n\nVendor| Status| Date Notified| Date Updated \n---|---|---|--- \nAmazon| | -| 05 Jan 2018 \nAMD| | -| 03 Jan 2018 \nAndroid Open Source Project| | -| 05 Jan 2018 \nApple| | -| 08 Jan 2018 \nArm| | -| 03 Jan 2018 \nCentOS| | -| 05 Jan 2018 \nCisco| | -| 05 Jan 2018 \nCitrix| | -| 05 Jan 2018 \nDebian GNU/Linux| | -| 05 Jan 2018 \nDell| | -| 08 Jan 2018 \nDragonFly BSD Project| | -| 08 Jan 2018 \nFedora Project| | -| 05 Jan 2018 \nFortinet, Inc.| | -| 05 Jan 2018 \nFreeBSD Project| | -| 05 Jan 2018 \nFujitsu| | -| 11 Jan 2018 \nIf you are a vendor and your product is affected, [let us know](<mailto:cert@cert.org?Subject=VU%23584653 Vendor Status Inquiry>). \n \n\n\n### CVSS Metrics \n\nGroup | Score | Vector \n---|---|--- \nBase | 4.4 | AV:L/AC:M/Au:S/C:C/I:N/A:N \nTemporal | 3.4 | E:POC/RL:OF/RC:C \nEnvironmental | 5.1 | CDP:ND/TD:H/CR:H/IR:ND/AR:ND \n \n### References\n\n * <https://meltdownattack.com/>\n * <https://meltdownattack.com/meltdown.pdf>\n * <https://spectreattack.com/>\n * <https://spectreattack.com/spectre.pdf>\n * <https://security.googleblog.com/2018/01/todays-cpu-vulnerability-what-you-need.html>\n * <https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html>\n * <https://cyber.wtf/2017/07/28/negative-result-reading-kernel-memory-from-user-mode/>\n * <https://github.com/IAIK/KAISER>\n * <https://gruss.cc/files/kaiser.pdf>\n * <https://gruss.cc/files/prefetch.pdf>\n * <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5aa90a84589282b87666f92b6c3c917c8080a9bf>\n * <https://lkml.org/lkml/2017/12/27/2>\n * <https://lkml.org/lkml/2018/1/4/615>\n * <https://lwn.net/Articles/741878/>\n * <https://lwn.net/Articles/737940/>\n * <https://lwn.net/Articles/742702/>\n * <http://pythonsweetness.tumblr.com/post/169166980422/the-mysterious-case-of-the-linux-page-table>\n * <https://nakedsecurity.sophos.com/2018/01/03/fckwit-aka-kaiser-aka-kpti-intel-cpu-flaw-needs-low-level-os-patches/>\n * <https://en.wikipedia.org/wiki/Kernel_page-table_isolation>\n * <https://chrisam.net/2018/01/04/speculative-execution-side-channel-vulnerabilities-vendor-published-info/>\n * <https://www.raspberrypi.org/blog/why-raspberry-pi-isnt-vulnerable-to-spectre-or-meltdown/>\n * <https://doublepulsar.com/important-information-about-microsoft-meltdown-cpu-security-fixes-antivirus-vendors-and-you-a852ba0292ec>\n * [https://docs.google.com/spreadsheets/d/184wcDt9I9TUNFFbsAVLpzAtckQxYiuirADzf3cL42FQ/htmlview?usp=sharing&sle;=true](<https://docs.google.com/spreadsheets/d/184wcDt9I9TUNFFbsAVLpzAtckQxYiuirADzf3cL42FQ/htmlview?usp=sharing&sle=true>)\n\n### Credit\n\nThese issues were researched and reported by researchers at Google Project Zero (Jann Horn) the Institute of Applied Information Processing and Communications (IAIK) at Graz University of Technology (Gruss et. al.), Paul Kocher, and Anders Fogh.\n\nThis document was written by Art Manion and Will Dormann.\n\n### Other Information\n\n * CVE IDs: [CVE-2017-5753](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5753>) [CVE-2017-5715](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5715>) [CVE-2017-5754](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5754>)\n * US-CERT Alert: [TA18-004A](<http://www.us-cert.gov/cas/techalerts/TA18-004A.html>)\n * Date Public: 03 Jan 2018\n * Date First Published: 03 Jan 2018\n * Date Last Updated: 22 Jan 2018\n * Document Revision: 211\n\n", "published": "2018-01-03T00:00:00", "modified": "2018-01-22T00:00:00", "cvss": {"score": 4.7, "vector": "AV:LOCAL/AC:MEDIUM/Au:NONE/C:COMPLETE/I:NONE/A:NONE/"}, "href": "https://www.kb.cert.org/vuls/id/584653", "reporter": "CERT", "references": ["https://meltdownattack.com/meltdown.pdf", "https://meltdownattack.com/meltdown.pdf", "https://docs.google.com/spreadsheets/d/184wcDt9I9TUNFFbsAVLpzAtckQxYiuirADzf3cL42FQ/htmlview?usp=sharing&sle=true", "https://lwn.net/Articles/742702/", "https://nakedsecurity.sophos.com/2018/01/03/fckwit-aka-kaiser-aka-kpti-intel-cpu-flaw-needs-low-level-os-patches/", "https://www.raspberrypi.org/blog/why-raspberry-pi-isnt-vulnerable-to-spectre-or-meltdown/", "https://lkml.org/lkml/2017/12/27/2", "https://security.googleblog.com/2018/01/todays-cpu-vulnerability-what-you-need.html", "https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html", "https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html", "https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html", "http://pythonsweetness.tumblr.com/post/169166980422/the-mysterious-case-of-the-linux-page-table", "https://gruss.cc/files/kaiser.pdf", "https://doublepulsar.com/important-information-about-microsoft-meltdown-cpu-security-fixes-antivirus-vendors-and-you-a852ba0292ec", "https://doublepulsar.com/important-information-about-microsoft-meltdown-cpu-security-fixes-antivirus-vendors-and-you-a852ba0292ec", "http://www.us-cert.gov/cas/techalerts/TA18-004A.html", "https://chrisam.net/2018/01/04/speculative-execution-side-channel-vulnerabilities-vendor-published-info/", "https://meltdownattack.com/", "https://meltdownattack.com/", "https://meltdownattack.com/", "https://en.wikipedia.org/wiki/Kernel_page-table_isolation", "https://en.wikipedia.org/wiki/Kernel_page-table_isolation", "http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5753", "https://spectreattack.com/", "https://spectreattack.com/", "https://spectreattack.com/", "https://lwn.net/Articles/737940/", "http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5715", "https://lkml.org/lkml/2018/1/4/615", "https://lkml.org/lkml/2018/1/4/615", "https://github.com/IAIK/KAISER", "https://cyber.wtf/2017/07/28/negative-result-reading-kernel-memory-from-user-mode/", "https://lwn.net/Articles/741878/", "https://gruss.cc/files/prefetch.pdf", "https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5aa90a84589282b87666f92b6c3c917c8080a9bf", "http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5754", "https://spectreattack.com/spectre.pdf", "https://spectreattack.com/spectre.pdf", "https://spectreattack.com/spectre.pdf", "https://spectreattack.com/spectre.pdf"], "cvelist": ["CVE-2017-5753", "CVE-2017-5753", "CVE-2017-5753", "CVE-2017-5753", "CVE-2017-5754", "CVE-2017-5754", "CVE-2017-5754", "CVE-2017-5715", "CVE-2017-5715", "CVE-2017-5715", "CVE-2017-5715"], "lastseen": "2018-01-23T02:55:13", "history": [], "viewCount": 261, "enchantments": {"score": {"modified": "2018-01-23T02:55:13", "value": 6.6}}, "objectVersion": "1.4"}, "lastseen": "2018-01-23T02:55:13", "differentElements": ["description", "modified", "references"], "edition": 17}, {"bulletin": {"id": "VU:584653", "hash": "076ef9c10c859148a05da938670bafbff994a10c3a18c3777e5f637c331d0a70", "type": "cert", "bulletinFamily": "info", "title": "CPU hardware vulnerable to side-channel attacks", "description": "### Overview\n\nCPU hardware implementations are vulnerable to cache side-channel attacks. These vulnerabilities are referred to as [Meltdown](<https://meltdownattack.com/>) and [Spectre](<https://spectreattack.com/>).\n\n### Description\n\nCPU hardware implementations are vulnerable to side-channel attacks referred to as [Meltdown](<https://meltdownattack.com/>) and [Spectre](<https://spectreattack.com/>). Both Spectre and Meltdown take advantage of the ability to extract information from instructions that have executed on a CPU using the CPU cache as a side-channel. These attacks are described in detail by [Google Project Zero](<https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html>), the Institute of Applied Information Processing and Communications (IAIK) at Graz University of Technology (TU Graz) and Anders Fogh. The issues are organized into three variants: \n\n * Variant 1 (CVE-2017-5753, [Spectre](<https://spectreattack.com/spectre.pdf>)): Bounds check bypass\n * Variant 2 (CVE-2017-5715, also [Spectre](<https://spectreattack.com/spectre.pdf>)): Branch target injection[](<https://spectreattack.com/spectre.pdf>)\n * Variant 3 (CVE-2017-5754, [Meltdown](<https://meltdownattack.com/meltdown.pdf>)): Rogue data cache load, memory access permission check performed after kernel memory read\n \n**Spectre** \n \nSpectre attacks take advantage of a CPU's branch prediction capabilities. Modern CPUs include a feature called branch prediction, which speculatively executes instructions at a location that the CPU believes it will branch to. Such speculative execution helps to more fully utilize the parts of the CPU, minimizing the time waiting, and therefore improving performance. When a branch is successfully predicted, instructions will retire, which means the outcomes of the instructions such as register and memory writes will be committed. If a branch is mispredicted, the speculatively-executed instructions will be discarded, and the direct side-effects of the instructions are undone. What is not undone are the indirect side-effects, such as CPU cache changes. By measuring latency of memory access operations, the cache can be used to extract values from speculatively-executed instructions. \n \nWith Spectre variant 1 (CVE-2017-5753), the instructions after a conditional branch are speculatively executed as the result of a misprediction. With Spectre variant 2 (CVE-2017-5715), the CPU executes instructions at a location determined by a mispredicted branch target. \n \nWith both variants of the Spectre attack, the impact is that a process may leak sensitive data to other processes on a system. Spectre may also allow one part of an application to access other parts of the same process memory space that would otherwise not be permitted. \n \nWhile the Spectre attack itself does not cross a user/kernel memory privilege boundary, depending on the configuration of the target platform, the Spectre attack may indirectly allow a user-space application to access kernel memory. For example, the[ Project Zero blog post](<https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html>) describes a scenario that uses eBPF to exfiltrate kernel memory contents into user-space code. This is made possible because eBPF JIT allows for userspace applications to inject code that is executed in kernel space. While this code is verified by the kernel, eBPF-compliant code will be allowed to execute with kernel permissions. The exploit described by Project Zero leverages eBPF to execute the Spectre attack in kernel space, while exfiltrating the data to user space. It is possible that other technologies that allow in-kernel code execution may also possibly be leveraged to leak kernel memory using Spectre. \n \n**Meltdown** \n \nMeltdown is related to the Spectre attack in that it also uses a cache side channel to access data that otherwise wouldn't be available. The main difference is that it leverages out-of-order execution capabilities in modern CPUs. Like speculative execution due to branch prediction, as used by Spectre, out-of-order execution on a CPU is a technique for ensuring fullest utilization of the CPU's parts. Although instructions may appear sequentially in the machine language, a CPU that supports out-of-order execution may execute instructions in a non-sequential manner, which can minimize the time that a CPU spends idle. \n \nMeltdown leverages insecure behavior that has been demonstrated in Intel CPUs and may affect CPUs from other vendors. Vulnerable CPUs allow memory reads in out-of-order instruction execution, and also contain a race condition between the raising of exceptions and the out-of-order instruction execution. The Meltdown attack reads a kernel memory value, which raises an exception because code running with user-space privileges are not permitted to directly read kernel memory. However, due to the race condition, out-of-order instructions following the faulting instruction may also execute. Even though instructions appear after the faulting instruction, out-of-order execution allows them to execute, using data retrieved from the instruction that raises the exception. By the time the exception is raised, some number of out-of-order instructions have executed. Although the raised exception causes the CPU to roll back the out-of-order instructions, the cache state is not reverted. This allows data from out-of-order instructions to persist beyond the point when the exception has been raised. \n \nThe impact of Meltdown is that a process running in user space is able to view the contents of kernel memory. Meltdown may also allow Spectre-like memory content leaking that does not cross the user/kernel privilege boundary. \n \nThe Linux kernel mitigations for Meltdown are referred to as KAISER, and subsequently KPTI, which aim to improve separation of kernel and user memory pages. Because the Spectre attacks do not cross user/kernel boundaries, the protections introduced with KAISER/KPTI do not add any protection against them. \n \nThe following table compares Spectre and Meltdown. \n \n| | **Spectre**| **Meltdown** \n---|---|--- \n**CPU mechanism for triggering**| Speculative execution from branch prediction| Out-of-order execution \n**Affected platforms**| CPUs that perform speculative execution from branch prediction| CPUs that allow memory reads in out-of-order instructions \n**Difficulty of successful attack**| High - Requires tailoring to the software environment of the victim process| Low - Kernel memory access exploit code is mostly universal \n**Impact**| Cross- and intra-process (including kernel) memory disclosure| Kernel memory disclosure to userspace \n**Software mitigations**| Variant 1: Compiler changes. Web browser updates to help prevent exploitation from JavaScript \nVariant 2: Indirect Branch Restricted Speculation ([IBRS](<https://lkml.org/lkml/2018/1/4/615>)). \n**Note: **The software mitigation for Spectre variant 2 requires CPU microcode updates| Kernel page-table isolation ([KPTI](<https://en.wikipedia.org/wiki/Kernel_page-table_isolation>)) \n \n### Impact\n\nAn attacker able to execute code with user privileges can achieve various impacts. The Meltdown attack allows reading of kernel memory from userspace. This can result in privilege escalation, disclosure of sensitive information, or it can weaken kernel-level protections, such as KASLR. The Spectre attack can allow inter-process or intra-process data leaks. \n \nTo execute code locally, an attacker would require a valid account or independent compromise of the target. Attacks using JavaScript in web browsers are possible. Multi-user and multi-tenant systems (including virtualized and cloud environments) likely face the greatest risk. Systems used to browse arbitrary web sites are also at risk. Single-user systems that do not readily provide a way for attackers to execute code locally face significantly lower risk. \n \n--- \n \n### Solution\n\n**Apply updates** \n \nOperating system, CPU microcode updates, and some application updates mitigate these attacks. Note that in many cases, the software fixes for these vulnerabilities will have a negative affect on system performance. Also note that Microsoft Windows systems [will no longer receive security updates](<https://doublepulsar.com/important-information-about-microsoft-meltdown-cpu-security-fixes-antivirus-vendors-and-you-a852ba0292ec>) via Windows Update if they are not running compliant anti-virus software. As with deploying any software updates, be sure to prioritize and test updates as necessary. \n \n**Consider CPU Options** \n \nInitial reports from the field indicate that overall system performance is impacted by many of the available patches for these vulnerabilities. Depending on the software workflow and the CPU capabilities present, the performance impact of software mitigations may be non-trivial and therefore may become an ongoing operational concern for some organizations. While we recognize that replacing existing CPUs in already deployed systems is not practical, organizations acquiring new systems should evaluate their CPU selection in light of the expected longevity of this vulnerability in available hardware as well as the performance impacts resulting from the various platform-specific software patches. Deployment contexts and performance requirements vary widely, and must be balanced by informed evaluation of the associated security risks. Contact your system vendor to determine if the CPU and operating system combination will experience a performance penalty due to software mitigations for these vulnerabilities. \n \n--- \n \n### Vendor Information \n\nVendor| Status| Date Notified| Date Updated \n---|---|---|--- \nAmazon| | -| 05 Jan 2018 \nAMD| | -| 03 Jan 2018 \nAndroid Open Source Project| | -| 05 Jan 2018 \nApple| | -| 02 Feb 2018 \nArm| | -| 03 Jan 2018 \nCentOS| | -| 05 Jan 2018 \nCisco| | -| 05 Jan 2018 \nCitrix| | -| 05 Jan 2018 \nDebian GNU/Linux| | -| 05 Jan 2018 \nDell| | -| 08 Jan 2018 \nDragonFly BSD Project| | -| 08 Jan 2018 \nFedora Project| | -| 05 Jan 2018 \nFortinet, Inc.| | -| 05 Jan 2018 \nFreeBSD Project| | -| 05 Jan 2018 \nFujitsu| | -| 11 Jan 2018 \nIf you are a vendor and your product is affected, [let us know](<mailto:cert@cert.org?Subject=VU%23584653 Vendor Status Inquiry>). \n \n\n\n### CVSS Metrics \n\nGroup | Score | Vector \n---|---|--- \nBase | 4.4 | AV:L/AC:M/Au:S/C:C/I:N/A:N \nTemporal | 3.4 | E:POC/RL:OF/RC:C \nEnvironmental | 5.1 | CDP:ND/TD:H/CR:H/IR:ND/AR:ND \n \n### References\n\n * <https://vuls.cert.org/confluence/display/Wiki/Vulnerabilities+Associated+with+CPU+Speculative+Execution>\n * <https://meltdownattack.com/>\n * <https://meltdownattack.com/meltdown.pdf>\n * <https://spectreattack.com/>\n * <https://spectreattack.com/spectre.pdf>\n * <https://security.googleblog.com/2018/01/todays-cpu-vulnerability-what-you-need.html>\n * <https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html>\n * <https://cyber.wtf/2017/07/28/negative-result-reading-kernel-memory-from-user-mode/>\n * <https://github.com/IAIK/KAISER>\n * <https://gruss.cc/files/kaiser.pdf>\n * <https://gruss.cc/files/prefetch.pdf>\n * <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5aa90a84589282b87666f92b6c3c917c8080a9bf>\n * <https://lkml.org/lkml/2017/12/27/2>\n * <https://lkml.org/lkml/2018/1/4/615>\n * <https://lwn.net/Articles/741878/>\n * <https://lwn.net/Articles/737940/>\n * <https://lwn.net/Articles/742702/>\n * <http://pythonsweetness.tumblr.com/post/169166980422/the-mysterious-case-of-the-linux-page-table>\n * <https://nakedsecurity.sophos.com/2018/01/03/fckwit-aka-kaiser-aka-kpti-intel-cpu-flaw-needs-low-level-os-patches/>\n * <https://en.wikipedia.org/wiki/Kernel_page-table_isolation>\n * <https://chrisam.net/2018/01/04/speculative-execution-side-channel-vulnerabilities-vendor-published-info/>\n * <https://www.raspberrypi.org/blog/why-raspberry-pi-isnt-vulnerable-to-spectre-or-meltdown/>\n * <https://doublepulsar.com/important-information-about-microsoft-meltdown-cpu-security-fixes-antivirus-vendors-and-you-a852ba0292ec>\n * [https://docs.google.com/spreadsheets/d/184wcDt9I9TUNFFbsAVLpzAtckQxYiuirADzf3cL42FQ/htmlview?usp=sharing&sle;=true](<https://docs.google.com/spreadsheets/d/184wcDt9I9TUNFFbsAVLpzAtckQxYiuirADzf3cL42FQ/htmlview?usp=sharing&sle=true>)\n * <https://github.com/iadgov/Spectre-and-Meltdown-Guidance>\n * <https://arxiv.org/abs/1802.03802>\n\n### Credit\n\nThese issues were researched and reported by researchers at Google Project Zero (Jann Horn) the Institute of Applied Information Processing and Communications (IAIK) at Graz University of Technology (Gruss et. al.), Paul Kocher, and Anders Fogh.\n\nThis document was written by Art Manion and Will Dormann.\n\n### Other Information\n\n * CVE IDs: [CVE-2017-5753](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5753>) [CVE-2017-5715](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5715>) [CVE-2017-5754](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5754>)\n * US-CERT Alert: [TA18-004A](<http://www.us-cert.gov/cas/techalerts/TA18-004A.html>)\n * Date Public: 03 Jan 2018\n * Date First Published: 03 Jan 2018\n * Date Last Updated: 03 Jul 2018\n * Document Revision: 230\n\n", "published": "2018-01-03T00:00:00", "modified": "2018-07-03T00:00:00", "cvss": {"score": 4.7, "vector": "AV:LOCAL/AC:MEDIUM/Au:NONE/C:COMPLETE/I:NONE/A:NONE/"}, "href": "https://www.kb.cert.org/vuls/id/584653", "reporter": "CERT", "references": ["https://meltdownattack.com/meltdown.pdf", "https://meltdownattack.com/meltdown.pdf", "https://docs.google.com/spreadsheets/d/184wcDt9I9TUNFFbsAVLpzAtckQxYiuirADzf3cL42FQ/htmlview?usp=sharing&sle=true", "https://lwn.net/Articles/742702/", "https://nakedsecurity.sophos.com/2018/01/03/fckwit-aka-kaiser-aka-kpti-intel-cpu-flaw-needs-low-level-os-patches/", "https://www.raspberrypi.org/blog/why-raspberry-pi-isnt-vulnerable-to-spectre-or-meltdown/", "https://lkml.org/lkml/2017/12/27/2", "https://security.googleblog.com/2018/01/todays-cpu-vulnerability-what-you-need.html", "https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html", "https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html", "https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html", "https://vuls.cert.org/confluence/display/Wiki/Vulnerabilities+Associated+with+CPU+Speculative+Execution", "http://pythonsweetness.tumblr.com/post/169166980422/the-mysterious-case-of-the-linux-page-table", "https://arxiv.org/abs/1802.03802", "https://gruss.cc/files/kaiser.pdf", "https://doublepulsar.com/important-information-about-microsoft-meltdown-cpu-security-fixes-antivirus-vendors-and-you-a852ba0292ec", "https://doublepulsar.com/important-information-about-microsoft-meltdown-cpu-security-fixes-antivirus-vendors-and-you-a852ba0292ec", "http://www.us-cert.gov/cas/techalerts/TA18-004A.html", "https://chrisam.net/2018/01/04/speculative-execution-side-channel-vulnerabilities-vendor-published-info/", "https://meltdownattack.com/", "https://meltdownattack.com/", "https://meltdownattack.com/", "https://en.wikipedia.org/wiki/Kernel_page-table_isolation", "https://en.wikipedia.org/wiki/Kernel_page-table_isolation", "http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5753", "https://spectreattack.com/", "https://spectreattack.com/", "https://spectreattack.com/", "https://lwn.net/Articles/737940/", "http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5715", "https://lkml.org/lkml/2018/1/4/615", "https://lkml.org/lkml/2018/1/4/615", "https://github.com/IAIK/KAISER", "https://cyber.wtf/2017/07/28/negative-result-reading-kernel-memory-from-user-mode/", "https://lwn.net/Articles/741878/", "https://gruss.cc/files/prefetch.pdf", "https://github.com/iadgov/Spectre-and-Meltdown-Guidance", "https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5aa90a84589282b87666f92b6c3c917c8080a9bf", "http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5754", "https://spectreattack.com/spectre.pdf", "https://spectreattack.com/spectre.pdf", "https://spectreattack.com/spectre.pdf", "https://spectreattack.com/spectre.pdf"], "cvelist": ["CVE-2017-5753", "CVE-2017-5753", "CVE-2017-5753", "CVE-2017-5753", "CVE-2017-5754", "CVE-2017-5754", "CVE-2017-5754", "CVE-2017-5715", "CVE-2017-5715", "CVE-2017-5715", "CVE-2017-5715"], "lastseen": "2018-07-04T01:26:32", "history": [], "viewCount": 286, "enchantments": {"score": {"value": 7.2, "vector": "NONE"}}, "objectVersion": "1.4"}, "lastseen": "2018-07-04T01:26:32", "differentElements": ["description", "references"], "edition": 18}, {"bulletin": {"id": "VU:584653", "hash": "a73507953d7e20377aeef65cd04757f410fe7e64c4a8014a8fbdb3763f984e74", "type": "cert", "bulletinFamily": "info", "title": "CPU hardware vulnerable to side-channel attacks", "description": "### Overview\n\nCPU hardware implementations are vulnerable to cache side-channel attacks. These vulnerabilities are referred to as [Meltdown](<https://meltdownattack.com/>) and [Spectre](<https://spectreattack.com/>).\n\n### Description\n\nCPU hardware implementations are vulnerable to side-channel attacks referred to as [Meltdown](<https://meltdownattack.com/>) and [Spectre](<https://spectreattack.com/>). Both Spectre and Meltdown take advantage of the ability to extract information from instructions that have executed on a CPU using the CPU cache as a side-channel. These attacks are described in detail by [Google Project Zero](<https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html>), the Institute of Applied Information Processing and Communications (IAIK) at Graz University of Technology (TU Graz) and Anders Fogh. The issues are organized into three variants: \n\n * Variant 1 (CVE-2017-5753, [Spectre](<https://spectreattack.com/spectre.pdf>)): Bounds check bypass\n * Variant 2 (CVE-2017-5715, also [Spectre](<https://spectreattack.com/spectre.pdf>)): Branch target injection[](<https://spectreattack.com/spectre.pdf>)\n * Variant 3 (CVE-2017-5754, [Meltdown](<https://meltdownattack.com/meltdown.pdf>)): Rogue data cache load, memory access permission check performed after kernel memory read\n \n**Spectre** \n \nSpectre attacks take advantage of a CPU's branch prediction capabilities. Modern CPUs include a feature called branch prediction, which speculatively executes instructions at a location that the CPU believes it will branch to. Such speculative execution helps to more fully utilize the parts of the CPU, minimizing the time waiting, and therefore improving performance. When a branch is successfully predicted, instructions will retire, which means the outcomes of the instructions such as register and memory writes will be committed. If a branch is mispredicted, the speculatively-executed instructions will be discarded, and the direct side-effects of the instructions are undone. What is not undone are the indirect side-effects, such as CPU cache changes. By measuring latency of memory access operations, the cache can be used to extract values from speculatively-executed instructions. \n \nWith Spectre variant 1 (CVE-2017-5753), the instructions after a conditional branch are speculatively executed as the result of a misprediction. With Spectre variant 2 (CVE-2017-5715), the CPU executes instructions at a location determined by a mispredicted branch target. \n \nWith both variants of the Spectre attack, the impact is that a process may leak sensitive data to other processes on a system. Spectre may also allow one part of an application to access other parts of the same process memory space that would otherwise not be permitted. \n \nWhile the Spectre attack itself does not cross a user/kernel memory privilege boundary, depending on the configuration of the target platform, the Spectre attack may indirectly allow a user-space application to access kernel memory. For example, the[ Project Zero blog post](<https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html>) describes a scenario that uses eBPF to exfiltrate kernel memory contents into user-space code. This is made possible because eBPF JIT allows for userspace applications to inject code that is executed in kernel space. While this code is verified by the kernel, eBPF-compliant code will be allowed to execute with kernel permissions. The exploit described by Project Zero leverages eBPF to execute the Spectre attack in kernel space, while exfiltrating the data to user space. It is possible that other technologies that allow in-kernel code execution may also possibly be leveraged to leak kernel memory using Spectre. \n \n**Meltdown** \n \nMeltdown is related to the Spectre attack in that it also uses a cache side channel to access data that otherwise wouldn't be available. The main difference is that it leverages out-of-order execution capabilities in modern CPUs. Like speculative execution due to branch prediction, as used by Spectre, out-of-order execution on a CPU is a technique for ensuring fullest utilization of the CPU's parts. Although instructions may appear sequentially in the machine language, a CPU that supports out-of-order execution may execute instructions in a non-sequential manner, which can minimize the time that a CPU spends idle. \n \nMeltdown leverages insecure behavior that has been demonstrated in Intel CPUs and may affect CPUs from other vendors. Vulnerable CPUs allow memory reads in out-of-order instruction execution, and also contain a race condition between the raising of exceptions and the out-of-order instruction execution. The Meltdown attack reads a kernel memory value, which raises an exception because code running with user-space privileges are not permitted to directly read kernel memory. However, due to the race condition, out-of-order instructions following the faulting instruction may also execute. Even though instructions appear after the faulting instruction, out-of-order execution allows them to execute, using data retrieved from the instruction that raises the exception. By the time the exception is raised, some number of out-of-order instructions have executed. Although the raised exception causes the CPU to roll back the out-of-order instructions, the cache state is not reverted. This allows data from out-of-order instructions to persist beyond the point when the exception has been raised. \n \nThe impact of Meltdown is that a process running in user space is able to view the contents of kernel memory. Meltdown may also allow Spectre-like memory content leaking that does not cross the user/kernel privilege boundary. \n \nThe Linux kernel mitigations for Meltdown are referred to as KAISER, and subsequently KPTI, which aim to improve separation of kernel and user memory pages. Because the Spectre attacks do not cross user/kernel boundaries, the protections introduced with KAISER/KPTI do not add any protection against them. \n \nThe following table compares Spectre and Meltdown. \n \n| | **Spectre**| **Meltdown** \n---|---|--- \n**CPU mechanism for triggering**| Speculative execution from branch prediction| Out-of-order execution \n**Affected platforms**| CPUs that perform speculative execution from branch prediction| CPUs that allow memory reads in out-of-order instructions \n**Difficulty of successful attack**| High - Requires tailoring to the software environment of the victim process| Low - Kernel memory access exploit code is mostly universal \n**Impact**| Cross- and intra-process (including kernel) memory disclosure| Kernel memory disclosure to userspace \n**Software mitigations**| Variant 1: Compiler changes. Web browser updates to help prevent exploitation from JavaScript \nVariant 2: Indirect Branch Restricted Speculation ([IBRS](<https://lkml.org/lkml/2018/1/4/615>)). \n**Note: **The software mitigation for Spectre variant 2 requires CPU microcode updates| Kernel page-table isolation ([KPTI](<https://en.wikipedia.org/wiki/Kernel_page-table_isolation>)) \n \n### Impact\n\nAn attacker able to execute code with user privileges can achieve various impacts. The Meltdown attack allows reading of kernel memory from userspace. This can result in privilege escalation, disclosure of sensitive information, or it can weaken kernel-level protections, such as KASLR. The Spectre attack can allow inter-process or intra-process data leaks. \n \nTo execute code locally, an attacker would require a valid account or independent compromise of the target. Attacks using JavaScript in web browsers are possible. Multi-user and multi-tenant systems (including virtualized and cloud environments) likely face the greatest risk. Systems used to browse arbitrary web sites are also at risk. Single-user systems that do not readily provide a way for attackers to execute code locally face significantly lower risk. \n \n--- \n \n### Solution\n\n**Apply updates** \n \nOperating system, CPU microcode updates, and some application updates mitigate these attacks. Note that in many cases, the software fixes for these vulnerabilities will have a negative affect on system performance. Also note that Microsoft Windows systems [will no longer receive security updates](<https://doublepulsar.com/important-information-about-microsoft-meltdown-cpu-security-fixes-antivirus-vendors-and-you-a852ba0292ec>) via Windows Update if they are not running compliant anti-virus software. As with deploying any software updates, be sure to prioritize and test updates as necessary. \n \n**Consider CPU Options** \n \nInitial reports from the field indicate that overall system performance is impacted by many of the available patches for these vulnerabilities. Depending on the software workflow and the CPU capabilities present, the performance impact of software mitigations may be non-trivial and therefore may become an ongoing operational concern for some organizations. While we recognize that replacing existing CPUs in already deployed systems is not practical, organizations acquiring new systems should evaluate their CPU selection in light of the expected longevity of this vulnerability in available hardware as well as the performance impacts resulting from the various platform-specific software patches. Deployment contexts and performance requirements vary widely, and must be balanced by informed evaluation of the associated security risks. Contact your system vendor to determine if the CPU and operating system combination will experience a performance penalty due to software mitigations for these vulnerabilities. \n \n--- \n \n### Vendor Information \n\nVendor| Status| Date Notified| Date Updated \n---|---|---|--- \nAmazon| | -| 05 Jan 2018 \nAMD| | -| 03 Jan 2018 \nAndroid Open Source Project| | -| 05 Jan 2018 \nApple| | -| 02 Feb 2018 \nArm| | -| 03 Jan 2018 \nCentOS| | -| 05 Jan 2018 \nCisco| | -| 05 Jan 2018 \nCitrix| | -| 05 Jan 2018 \nDebian GNU/Linux| | -| 05 Jan 2018 \nDell| | -| 08 Jan 2018 \nDragonFly BSD Project| | -| 08 Jan 2018 \nFedora Project| | -| 05 Jan 2018 \nFortinet, Inc.| | -| 05 Jan 2018 \nFreeBSD Project| | -| 05 Jan 2018 \nFujitsu| | -| 11 Jan 2018 \nIf you are a vendor and your product is affected, [let us know](<mailto:cert@cert.org?Subject=VU%23584653 Vendor Status Inquiry>). \n \n\n\n### CVSS Metrics \n\nGroup | Score | Vector \n---|---|--- \nBase | 4.4 | AV:L/AC:M/Au:S/C:C/I:N/A:N \nTemporal | 3.4 | E:POC/RL:OF/RC:C \nEnvironmental | 5.1 | CDP:ND/TD:H/CR:H/IR:ND/AR:ND \n \n### References\n\n * <https://vuls.cert.org/confluence/display/Wiki/Vulnerabilities+Associated+with+CPU+Speculative+Execution>\n * <https://meltdownattack.com/>\n * <https://meltdownattack.com/meltdown.pdf>\n * <https://spectreattack.com/>\n * <https://spectreattack.com/spectre.pdf>\n * <https://security.googleblog.com/2018/01/todays-cpu-vulnerability-what-you-need.html>\n * <https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html>\n * <https://cyber.wtf/2017/07/28/negative-result-reading-kernel-memory-from-user-mode/>\n * <https://github.com/IAIK/KAISER>\n * <https://gruss.cc/files/kaiser.pdf>\n * <https://gruss.cc/files/prefetch.pdf>\n * <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5aa90a84589282b87666f92b6c3c917c8080a9bf>\n * <https://lkml.org/lkml/2017/12/27/2>\n * <https://lkml.org/lkml/2018/1/4/615>\n * <https://lwn.net/Articles/741878/>\n * <https://lwn.net/Articles/737940/>\n * <https://lwn.net/Articles/742702/>\n * <http://pythonsweetness.tumblr.com/post/169166980422/the-mysterious-case-of-the-linux-page-table>\n * <https://nakedsecurity.sophos.com/2018/01/03/fckwit-aka-kaiser-aka-kpti-intel-cpu-flaw-needs-low-level-os-patches/>\n * <https://en.wikipedia.org/wiki/Kernel_page-table_isolation>\n * <https://chrisam.net/2018/01/04/speculative-execution-side-channel-vulnerabilities-vendor-published-info/>\n * <https://www.raspberrypi.org/blog/why-raspberry-pi-isnt-vulnerable-to-spectre-or-meltdown/>\n * <https://doublepulsar.com/important-information-about-microsoft-meltdown-cpu-security-fixes-antivirus-vendors-and-you-a852ba0292ec>\n * [https://docs.google.com/spreadsheets/d/184wcDt9I9TUNFFbsAVLpzAtckQxYiuirADzf3cL42FQ/htmlview?usp=sharing&sle;=true](<https://docs.google.com/spreadsheets/d/184wcDt9I9TUNFFbsAVLpzAtckQxYiuirADzf3cL42FQ/htmlview?usp=sharing&sle=true>)\n * <https://github.com/iadgov/Spectre-and-Meltdown-Guidance>\n * <https://arxiv.org/abs/1802.03802>\n\n### Credit\n\nThese issues were researched and reported by researchers at Google Project Zero (Jann Horn) the Institute of Applied Information Processing and Communications (IAIK) at Graz University of Technology (Gruss et. al.), Paul Kocher, and Anders Fogh.\n\nThis document was written by Art Manion and Will Dormann.\n\n### Other Information\n\n * CVE IDs: [CVE-2017-5753 CVE-2017-5715 CVE-2017-5754](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5753 CVE-2017-5715 CVE-2017-5754>)\n * US-CERT Alert: [TA18-004A](<http://www.us-cert.gov/cas/techalerts/TA18-004A.html>)\n * Date Public: 03 Jan 2018\n * Date First Published: 03 Jan 2018\n * Date Last Updated: 03 Jul 2018\n * Document Revision: 230\n\n", "published": "2018-01-03T00:00:00", "modified": "2018-07-03T00:00:00", "cvss": {"score": 4.7, "vector": "AV:LOCAL/AC:MEDIUM/Au:NONE/C:COMPLETE/I:NONE/A:NONE/"}, "href": "https://www.kb.cert.org/vuls/id/584653", "reporter": "CERT", "references": ["https://meltdownattack.com/meltdown.pdf", "https://meltdownattack.com/meltdown.pdf", "https://docs.google.com/spreadsheets/d/184wcDt9I9TUNFFbsAVLpzAtckQxYiuirADzf3cL42FQ/htmlview?usp=sharing&sle=true", "https://lwn.net/Articles/742702/", "https://nakedsecurity.sophos.com/2018/01/03/fckwit-aka-kaiser-aka-kpti-intel-cpu-flaw-needs-low-level-os-patches/", "https://www.raspberrypi.org/blog/why-raspberry-pi-isnt-vulnerable-to-spectre-or-meltdown/", "http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5753 CVE-2017-5715 CVE-2017-5754", "https://lkml.org/lkml/2017/12/27/2", "https://security.googleblog.com/2018/01/todays-cpu-vulnerability-what-you-need.html", "https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html", "https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html", "https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html", "https://vuls.cert.org/confluence/display/Wiki/Vulnerabilities+Associated+with+CPU+Speculative+Execution", "http://pythonsweetness.tumblr.com/post/169166980422/the-mysterious-case-of-the-linux-page-table", "https://arxiv.org/abs/1802.03802", "https://gruss.cc/files/kaiser.pdf", "https://doublepulsar.com/important-information-about-microsoft-meltdown-cpu-security-fixes-antivirus-vendors-and-you-a852ba0292ec", "https://doublepulsar.com/important-information-about-microsoft-meltdown-cpu-security-fixes-antivirus-vendors-and-you-a852ba0292ec", "http://www.us-cert.gov/cas/techalerts/TA18-004A.html", "https://chrisam.net/2018/01/04/speculative-execution-side-channel-vulnerabilities-vendor-published-info/", "https://meltdownattack.com/", "https://meltdownattack.com/", "https://meltdownattack.com/", "https://en.wikipedia.org/wiki/Kernel_page-table_isolation", "https://en.wikipedia.org/wiki/Kernel_page-table_isolation", "https://spectreattack.com/", "https://spectreattack.com/", "https://spectreattack.com/", "https://lwn.net/Articles/737940/", "https://lkml.org/lkml/2018/1/4/615", "https://lkml.org/lkml/2018/1/4/615", "https://github.com/IAIK/KAISER", "https://cyber.wtf/2017/07/28/negative-result-reading-kernel-memory-from-user-mode/", "https://lwn.net/Articles/741878/", "https://gruss.cc/files/prefetch.pdf", "https://github.com/iadgov/Spectre-and-Meltdown-Guidance", "https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5aa90a84589282b87666f92b6c3c917c8080a9bf", "https://spectreattack.com/spectre.pdf", "https://spectreattack.com/spectre.pdf", "https://spectreattack.com/spectre.pdf", "https://spectreattack.com/spectre.pdf"], "cvelist": ["CVE-2017-5753", "CVE-2017-5753", "CVE-2017-5753", "CVE-2017-5753", "CVE-2017-5754", "CVE-2017-5754", "CVE-2017-5754", "CVE-2017-5715", "CVE-2017-5715", "CVE-2017-5715", "CVE-2017-5715"], "lastseen": "2018-08-02T23:57:33", "history": [], "viewCount": 289, "enchantments": {"score": {"value": 7.2, "vector": "NONE"}}, "objectVersion": "1.4"}, "lastseen": "2018-08-02T23:57:33", "differentElements": ["description", "references"], "edition": 19}, {"bulletin": {"id": "VU:584653", "hash": "71791706d562f368ed2ef9e70298808c", "type": "cert", "bulletinFamily": "info", "title": "CPU hardware vulnerable to side-channel attacks", "description": "### Overview\n\nCPU hardware implementations are vulnerable to cache side-channel attacks. These vulnerabilities are referred to as [Meltdown](<https://meltdownattack.com/>) and [Spectre](<https://spectreattack.com/>).\n\n### Description\n\nCPU hardware implementations are vulnerable to side-channel attacks referred to as [Meltdown](<https://meltdownattack.com/>) and [Spectre](<https://spectreattack.com/>). Both Spectre and Meltdown take advantage of the ability to extract information from instructions that have executed on a CPU using the CPU cache as a side-channel. These attacks are described in detail by [Google Project Zero](<https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html>), the Institute of Applied Information Processing and Communications (IAIK) at Graz University of Technology (TU Graz) and Anders Fogh. The issues are organized into three variants: \n\n * Variant 1 (CVE-2017-5753, [Spectre](<https://spectreattack.com/spectre.pdf>)): Bounds check bypass\n * Variant 2 (CVE-2017-5715, also [Spectre](<https://spectreattack.com/spectre.pdf>)): Branch target injection[](<https://spectreattack.com/spectre.pdf>)\n * Variant 3 (CVE-2017-5754, [Meltdown](<https://meltdownattack.com/meltdown.pdf>)): Rogue data cache load, memory access permission check performed after kernel memory read\n \n**Spectre** \n \nSpectre attacks take advantage of a CPU's branch prediction capabilities. Modern CPUs include a feature called branch prediction, which speculatively executes instructions at a location that the CPU believes it will branch to. Such speculative execution helps to more fully utilize the parts of the CPU, minimizing the time waiting, and therefore improving performance. When a branch is successfully predicted, instructions will retire, which means the outcomes of the instructions such as register and memory writes will be committed. If a branch is mispredicted, the speculatively-executed instructions will be discarded, and the direct side-effects of the instructions are undone. What is not undone are the indirect side-effects, such as CPU cache changes. By measuring latency of memory access operations, the cache can be used to extract values from speculatively-executed instructions. \n \nWith Spectre variant 1 (CVE-2017-5753), the instructions after a conditional branch are speculatively executed as the result of a misprediction. With Spectre variant 2 (CVE-2017-5715), the CPU executes instructions at a location determined by a mispredicted branch target. \n \nWith both variants of the Spectre attack, the impact is that a process may leak sensitive data to other processes on a system. Spectre may also allow one part of an application to access other parts of the same process memory space that would otherwise not be permitted. \n \nWhile the Spectre attack itself does not cross a user/kernel memory privilege boundary, depending on the configuration of the target platform, the Spectre attack may indirectly allow a user-space application to access kernel memory. For example, the[ Project Zero blog post](<https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html>) describes a scenario that uses eBPF to exfiltrate kernel memory contents into user-space code. This is made possible because eBPF JIT allows for userspace applications to inject code that is executed in kernel space. While this code is verified by the kernel, eBPF-compliant code will be allowed to execute with kernel permissions. The exploit described by Project Zero leverages eBPF to execute the Spectre attack in kernel space, while exfiltrating the data to user space. It is possible that other technologies that allow in-kernel code execution may also possibly be leveraged to leak kernel memory using Spectre. \n \n**Meltdown** \n \nMeltdown is related to the Spectre attack in that it also uses a cache side channel to access data that otherwise wouldn't be available. The main difference is that it leverages out-of-order execution capabilities in modern CPUs. Like speculative execution due to branch prediction, as used by Spectre, out-of-order execution on a CPU is a technique for ensuring fullest utilization of the CPU's parts. Although instructions may appear sequentially in the machine language, a CPU that supports out-of-order execution may execute instructions in a non-sequential manner, which can minimize the time that a CPU spends idle. \n \nMeltdown leverages insecure behavior that has been demonstrated in Intel CPUs and may affect CPUs from other vendors. Vulnerable CPUs allow memory reads in out-of-order instruction execution, and also contain a race condition between the raising of exceptions and the out-of-order instruction execution. The Meltdown attack reads a kernel memory value, which raises an exception because code running with user-space privileges are not permitted to directly read kernel memory. However, due to the race condition, out-of-order instructions following the faulting instruction may also execute. Even though instructions appear after the faulting instruction, out-of-order execution allows them to execute, using data retrieved from the instruction that raises the exception. By the time the exception is raised, some number of out-of-order instructions have executed. Although the raised exception causes the CPU to roll back the out-of-order instructions, the cache state is not reverted. This allows data from out-of-order instructions to persist beyond the point when the exception has been raised. \n \nThe impact of Meltdown is that a process running in user space is able to view the contents of kernel memory. Meltdown may also allow Spectre-like memory content leaking that does not cross the user/kernel privilege boundary. \n \nThe Linux kernel mitigations for Meltdown are referred to as KAISER, and subsequently KPTI, which aim to improve separation of kernel and user memory pages. Because the Spectre attacks do not cross user/kernel boundaries, the protections introduced with KAISER/KPTI do not add any protection against them. \n \nThe following table compares Spectre and Meltdown. \n \n| | **Spectre**| **Meltdown** \n---|---|--- \n**CPU mechanism for triggering**| Speculative execution from branch prediction| Out-of-order execution \n**Affected platforms**| CPUs that perform speculative execution from branch prediction| CPUs that allow memory reads in out-of-order instructions \n**Difficulty of successful attack**| High - Requires tailoring to the software environment of the victim process| Low - Kernel memory access exploit code is mostly universal \n**Impact**| Cross- and intra-process (including kernel) memory disclosure| Kernel memory disclosure to userspace \n**Software mitigations**| Variant 1: Compiler changes. Web browser updates to help prevent exploitation from JavaScript \nVariant 2: Indirect Branch Restricted Speculation ([IBRS](<https://lkml.org/lkml/2018/1/4/615>)). \n**Note: **The software mitigation for Spectre variant 2 requires CPU microcode updates| Kernel page-table isolation ([KPTI](<https://en.wikipedia.org/wiki/Kernel_page-table_isolation>)) \n \n### Impact\n\nAn attacker able to execute code with user privileges can achieve various impacts. The Meltdown attack allows reading of kernel memory from userspace. This can result in privilege escalation, disclosure of sensitive information, or it can weaken kernel-level protections, such as KASLR. The Spectre attack can allow inter-process or intra-process data leaks. \n \nTo execute code locally, an attacker would require a valid account or independent compromise of the target. Attacks using JavaScript in web browsers are possible. Multi-user and multi-tenant systems (including virtualized and cloud environments) likely face the greatest risk. Systems used to browse arbitrary web sites are also at risk. Single-user systems that do not readily provide a way for attackers to execute code locally face significantly lower risk. \n \n--- \n \n### Solution\n\n**Apply updates** \n \nOperating system, CPU microcode updates, and some application updates mitigate these attacks. Note that in many cases, the software fixes for these vulnerabilities will have a negative affect on system performance. Also note that Microsoft Windows systems [will no longer receive security updates](<https://doublepulsar.com/important-information-about-microsoft-meltdown-cpu-security-fixes-antivirus-vendors-and-you-a852ba0292ec>) via Windows Update if they are not running compliant anti-virus software. As with deploying any software updates, be sure to prioritize and test updates as necessary. \n \n**Consider CPU Options** \n \nInitial reports from the field indicate that overall system performance is impacted by many of the available patches for these vulnerabilities. Depending on the software workflow and the CPU capabilities present, the performance impact of software mitigations may be non-trivial and therefore may become an ongoing operational concern for some organizations. While we recognize that replacing existing CPUs in already deployed systems is not practical, organizations acquiring new systems should evaluate their CPU selection in light of the expected longevity of this vulnerability in available hardware as well as the performance impacts resulting from the various platform-specific software patches. Deployment contexts and performance requirements vary widely, and must be balanced by informed evaluation of the associated security risks. Contact your system vendor to determine if the CPU and operating system combination will experience a performance penalty due to software mitigations for these vulnerabilities. \n \n--- \n \n### Vendor Information \n\nVendor| Status| Date Notified| Date Updated \n---|---|---|--- \nAmazon| | -| 05 Jan 2018 \nAMD| | -| 03 Jan 2018 \nAndroid Open Source Project| | -| 05 Jan 2018 \nApple| | -| 02 Feb 2018 \nArm| | -| 03 Jan 2018 \nCentOS| | -| 05 Jan 2018 \nCisco| | -| 05 Jan 2018 \nCitrix| | -| 05 Jan 2018 \nDebian GNU/Linux| | -| 05 Jan 2018 \nDell| | -| 08 Jan 2018 \nDragonFly BSD Project| | -| 08 Jan 2018 \nFedora Project| | -| 05 Jan 2018 \nFortinet, Inc.| | -| 05 Jan 2018 \nFreeBSD Project| | -| 05 Jan 2018 \nFujitsu| | -| 11 Jan 2018 \nIf you are a vendor and your product is affected, [let us know](<mailto:cert@cert.org?Subject=VU%23584653 Vendor Status Inquiry>). \n \n\n\n### CVSS Metrics \n\nGroup | Score | Vector \n---|---|--- \nBase | 4.4 | AV:L/AC:M/Au:S/C:C/I:N/A:N \nTemporal | 3.4 | E:POC/RL:OF/RC:C \nEnvironmental | 5.1 | CDP:ND/TD:H/CR:H/IR:ND/AR:ND \n \n### References\n\n * <https://vuls.cert.org/confluence/display/Wiki/Vulnerabilities+Associated+with+CPU+Speculative+Execution>\n * <https://meltdownattack.com/>\n * <https://meltdownattack.com/meltdown.pdf>\n * <https://spectreattack.com/>\n * <https://spectreattack.com/spectre.pdf>\n * <https://security.googleblog.com/2018/01/todays-cpu-vulnerability-what-you-need.html>\n * <https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html>\n * <https://cyber.wtf/2017/07/28/negative-result-reading-kernel-memory-from-user-mode/>\n * <https://github.com/IAIK/KAISER>\n * <https://gruss.cc/files/kaiser.pdf>\n * <https://gruss.cc/files/prefetch.pdf>\n * <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5aa90a84589282b87666f92b6c3c917c8080a9bf>\n * <https://lkml.org/lkml/2017/12/27/2>\n * <https://lkml.org/lkml/2018/1/4/615>\n * <https://lwn.net/Articles/741878/>\n * <https://lwn.net/Articles/737940/>\n * <https://lwn.net/Articles/742702/>\n * <http://pythonsweetness.tumblr.com/post/169166980422/the-mysterious-case-of-the-linux-page-table>\n * <https://nakedsecurity.sophos.com/2018/01/03/fckwit-aka-kaiser-aka-kpti-intel-cpu-flaw-needs-low-level-os-patches/>\n * <https://en.wikipedia.org/wiki/Kernel_page-table_isolation>\n * <https://chrisam.net/2018/01/04/speculative-execution-side-channel-vulnerabilities-vendor-published-info/>\n * <https://www.raspberrypi.org/blog/why-raspberry-pi-isnt-vulnerable-to-spectre-or-meltdown/>\n * <https://doublepulsar.com/important-information-about-microsoft-meltdown-cpu-security-fixes-antivirus-vendors-and-you-a852ba0292ec>\n * [https://docs.google.com/spreadsheets/d/184wcDt9I9TUNFFbsAVLpzAtckQxYiuirADzf3cL42FQ/htmlview?usp=sharing&sle;=true](<https://docs.google.com/spreadsheets/d/184wcDt9I9TUNFFbsAVLpzAtckQxYiuirADzf3cL42FQ/htmlview?usp=sharing&sle=true>)\n * <https://github.com/iadgov/Spectre-and-Meltdown-Guidance>\n * <https://arxiv.org/abs/1802.03802>\n\n### Credit\n\nThese issues were researched and reported by researchers at Google Project Zero (Jann Horn) the Institute of Applied Information Processing and Communications (IAIK) at Graz University of Technology (Gruss et. al.), Paul Kocher, and Anders Fogh.\n\nThis document was written by Art Manion and Will Dormann.\n\n### Other Information\n\n * CVE IDs: [CVE-2017-5753](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5753>) [CVE-2017-5715](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5715>) [CVE-2017-5754](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5754>)\n * US-CERT Alert: [TA18-004A](<http://www.us-cert.gov/cas/techalerts/TA18-004A.html>)\n * Date Public: 03 Jan 2018\n * Date First Published: 03 Jan 2018\n * Date Last Updated: 03 Jul 2018\n * Document Revision: 230\n\n", "published": "2018-01-03T00:00:00", "modified": "2018-07-03T00:00:00", "cvss": {"score": 4.7, "vector": "AV:LOCAL/AC:MEDIUM/Au:NONE/C:COMPLETE/I:NONE/A:NONE/"}, "href": "https://www.kb.cert.org/vuls/id/584653", "reporter": "CERT", "references": ["https://meltdownattack.com/meltdown.pdf", "https://meltdownattack.com/meltdown.pdf", "https://docs.google.com/spreadsheets/d/184wcDt9I9TUNFFbsAVLpzAtckQxYiuirADzf3cL42FQ/htmlview?usp=sharing&sle=true", "https://lwn.net/Articles/742702/", "https://nakedsecurity.sophos.com/2018/01/03/fckwit-aka-kaiser-aka-kpti-intel-cpu-flaw-needs-low-level-os-patches/", "https://www.raspberrypi.org/blog/why-raspberry-pi-isnt-vulnerable-to-spectre-or-meltdown/", "https://lkml.org/lkml/2017/12/27/2", "https://security.googleblog.com/2018/01/todays-cpu-vulnerability-what-you-need.html", "https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html", "https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html", "https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html", "https://vuls.cert.org/confluence/display/Wiki/Vulnerabilities+Associated+with+CPU+Speculative+Execution", "http://pythonsweetness.tumblr.com/post/169166980422/the-mysterious-case-of-the-linux-page-table", "https://arxiv.org/abs/1802.03802", "https://gruss.cc/files/kaiser.pdf", "https://doublepulsar.com/important-information-about-microsoft-meltdown-cpu-security-fixes-antivirus-vendors-and-you-a852ba0292ec", "https://doublepulsar.com/important-information-about-microsoft-meltdown-cpu-security-fixes-antivirus-vendors-and-you-a852ba0292ec", "http://www.us-cert.gov/cas/techalerts/TA18-004A.html", "https://chrisam.net/2018/01/04/speculative-execution-side-channel-vulnerabilities-vendor-published-info/", "https://meltdownattack.com/", "https://meltdownattack.com/", "https://meltdownattack.com/", "https://en.wikipedia.org/wiki/Kernel_page-table_isolation", "https://en.wikipedia.org/wiki/Kernel_page-table_isolation", "http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5753", "https://spectreattack.com/", "https://spectreattack.com/", "https://spectreattack.com/", "https://lwn.net/Articles/737940/", "http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5715", "https://lkml.org/lkml/2018/1/4/615", "https://lkml.org/lkml/2018/1/4/615", "https://github.com/IAIK/KAISER", "https://cyber.wtf/2017/07/28/negative-result-reading-kernel-memory-from-user-mode/", "https://lwn.net/Articles/741878/", "https://gruss.cc/files/prefetch.pdf", "https://github.com/iadgov/Spectre-and-Meltdown-Guidance", "https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5aa90a84589282b87666f92b6c3c917c8080a9bf", "http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5754", "https://spectreattack.com/spectre.pdf", "https://spectreattack.com/spectre.pdf", "https://spectreattack.com/spectre.pdf", "https://spectreattack.com/spectre.pdf"], "cvelist": ["CVE-2017-5753", "CVE-2017-5753", "CVE-2017-5753", "CVE-2017-5753", "CVE-2017-5754", "CVE-2017-5754", "CVE-2017-5754", "CVE-2017-5715", "CVE-2017-5715", "CVE-2017-5715", "CVE-2017-5715"], "lastseen": "2018-09-05T16:45:49", "history": [], "viewCount": 805, "enchantments": {"score": {"value": 7.2, "vector": "NONE"}}, "objectVersion": "1.4"}, "lastseen": "2018-09-05T16:45:49", "differentElements": ["cvelist", "description", "modified", "published", "references"], "edition": 20}, {"bulletin": {"id": "VU:584653", "hash": "3440b910c3f04ee2d3231c3420c7469f", "type": "cert", "bulletinFamily": "info", "title": "CPU hardware vulnerable to side-channel attacks", "description": "### Overview \n\nCPU hardware implementations are vulnerable to cache side-channel attacks. These vulnerabilities are referred to as [Meltdown](<https://meltdownattack.com/>) and [Spectre](<https://spectreattack.com/>).\n\n### Description \n\nCPU hardware implementations are vulnerable to side-channel attacks referred to as [Meltdown](<https://meltdownattack.com/>) and [Spectre](<https://spectreattack.com/>). Both Spectre and Meltdown take advantage of the ability to extract information from instructions that have executed on a CPU using the CPU cache as a side-channel. These attacks are described in detail by [Google Project Zero](<https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html>), the Institute of Applied Information Processing and Communications (IAIK) at Graz University of Technology (TU Graz) and Anders Fogh. The issues are organized into three variants:\n\n * Variant 1 (CVE-2017-5753, [Spectre](<https://spectreattack.com/spectre.pdf>)): Bounds check bypass\n * Variant 2 (CVE-2017-5715, also [Spectre](<https://spectreattack.com/spectre.pdf>)): Branch target injection[](<https://spectreattack.com/spectre.pdf>)\n * Variant 3 (CVE-2017-5754, [Meltdown](<https://meltdownattack.com/meltdown.pdf>)): Rogue data cache load, memory access permission check performed after kernel memory read\n \n**Spectre** \n \nSpectre attacks take advantage of a CPU's branch prediction capabilities. Modern CPUs include a feature called branch prediction, which speculatively executes instructions at a location that the CPU believes it will branch to. Such speculative execution helps to more fully utilize the parts of the CPU, minimizing the time waiting, and therefore improving performance. When a branch is successfully predicted, instructions will retire, which means the outcomes of the instructions such as register and memory writes will be committed. If a branch is mispredicted, the speculatively-executed instructions will be discarded, and the direct side-effects of the instructions are undone. What is not undone are the indirect side-effects, such as CPU cache changes. By measuring latency of memory access operations, the cache can be used to extract values from speculatively-executed instructions. \n \nWith Spectre variant 1 (CVE-2017-5753), the instructions after a conditional branch are speculatively executed as the result of a misprediction. With Spectre variant 2 (CVE-2017-5715), the CPU executes instructions at a location determined by a mispredicted branch target. \n \nWith both variants of the Spectre attack, the impact is that a process may leak sensitive data to other processes on a system. Spectre may also allow one part of an application to access other parts of the same process memory space that would otherwise not be permitted. \n \nWhile the Spectre attack itself does not cross a user/kernel memory privilege boundary, depending on the configuration of the target platform, the Spectre attack may indirectly allow a user-space application to access kernel memory. For example, the[ Project Zero blog post](<https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html>) describes a scenario that uses eBPF to exfiltrate kernel memory contents into user-space code. This is made possible because eBPF JIT allows for userspace applications to inject code that is executed in kernel space. While this code is verified by the kernel, eBPF-compliant code will be allowed to execute with kernel permissions. The exploit described by Project Zero leverages eBPF to execute the Spectre attack in kernel space, while exfiltrating the data to user space. It is possible that other technologies that allow in-kernel code execution may also possibly be leveraged to leak kernel memory using Spectre. \n \n**Meltdown** \n \nMeltdown is related to the Spectre attack in that it also uses a cache side channel to access data that otherwise wouldn't be available. The main difference is that it leverages out-of-order execution capabilities in modern CPUs. Like speculative execution due to branch prediction, as used by Spectre, out-of-order execution on a CPU is a technique for ensuring fullest utilization of the CPU's parts. Although instructions may appear sequentially in the machine language, a CPU that supports out-of-order execution may execute instructions in a non-sequential manner, which can minimize the time that a CPU spends idle. \n \nMeltdown leverages insecure behavior that has been demonstrated in Intel CPUs and may affect CPUs from other vendors. Vulnerable CPUs allow memory reads in out-of-order instruction execution, and also contain a race condition between the raising of exceptions and the out-of-order instruction execution. The Meltdown attack reads a kernel memory value, which raises an exception because code running with user-space privileges are not permitted to directly read kernel memory. However, due to the race condition, out-of-order instructions following the faulting instruction may also execute. Even though instructions appear after the faulting instruction, out-of-order execution allows them to execute, using data retrieved from the instruction that raises the exception. By the time the exception is raised, some number of out-of-order instructions have executed. Although the raised exception causes the CPU to roll back the out-of-order instructions, the cache state is not reverted. This allows data from out-of-order instructions to persist beyond the point when the exception has been raised. \n \nThe impact of Meltdown is that a process running in user space is able to view the contents of kernel memory. Meltdown may also allow Spectre-like memory content leaking that does not cross the user/kernel privilege boundary. \n \nThe Linux kernel mitigations for Meltdown are referred to as KAISER, and subsequently KPTI, which aim to improve separation of kernel and user memory pages. Because the Spectre attacks do not cross user/kernel boundaries, the protections introduced with KAISER/KPTI do not add any protection against them. \n \nThe following table compares Spectre and Meltdown. \n \n| | **Spectre**| **Meltdown** \n---|---|--- \n**CPU mechanism for triggering**| Speculative execution from branch prediction| Out-of-order execution \n**Affected platforms**| CPUs that perform speculative execution from branch prediction| CPUs that allow memory reads in out-of-order instructions \n**Difficulty of successful attack**| High - Requires tailoring to the software environment of the victim process| Low - Kernel memory access exploit code is mostly universal \n**Impact**| Cross- and intra-process (including kernel) memory disclosure| Kernel memory disclosure to userspace \n**Software mitigations**| Variant 1: Compiler changes. Web browser updates to help prevent exploitation from JavaScript \nVariant 2: Indirect Branch Restricted Speculation ([IBRS](<https://lkml.org/lkml/2018/1/4/615>)). \n**Note: **The software mitigation for Spectre variant 2 requires CPU microcode updates| Kernel page-table isolation ([KPTI](<https://en.wikipedia.org/wiki/Kernel_page-table_isolation>)) \n \n### Impact \n\nAn attacker able to execute code with user privileges can achieve various impacts. The Meltdown attack allows reading of kernel memory from userspace. This can result in privilege escalation, disclosure of sensitive information, or it can weaken kernel-level protections, such as KASLR. The Spectre attack can allow inter-process or intra-process data leaks. \n \nTo execute code locally, an attacker would require a valid account or independent compromise of the target. Attacks using JavaScript in web browsers are possible. Multi-user and multi-tenant systems (including virtualized and cloud environments) likely face the greatest risk. Systems used to browse arbitrary web sites are also at risk. Single-user systems that do not readily provide a way for attackers to execute code locally face significantly lower risk. \n \n--- \n \n### Solution \n\n**Apply updates** \n \nOperating system, CPU microcode updates, and some application updates mitigate these attacks. Note that in many cases, the software fixes for these vulnerabilities will have a negative affect on system performance. Also note that Microsoft Windows systems [will no longer receive security updates](<https://doublepulsar.com/important-information-about-microsoft-meltdown-cpu-security-fixes-antivirus-vendors-and-you-a852ba0292ec>) via Windows Update if they are not running compliant anti-virus software. As with deploying any software updates, be sure to prioritize and test updates as necessary. \n \n**Consider CPU Options** \n \nInitial reports from the field indicate that overall system performance is impacted by many of the available patches for these vulnerabilities. Depending on the software workflow and the CPU capabilities present, the performance impact of software mitigations may be non-trivial and therefore may become an ongoing operational concern for some organizations. While we recognize that replacing existing CPUs in already deployed systems is not practical, organizations acquiring new systems should evaluate their CPU selection in light of the expected longevity of this vulnerability in available hardware as well as the performance impacts resulting from the various platform-specific software patches. Deployment contexts and performance requirements vary widely, and must be balanced by informed evaluation of the associated security risks. Contact your system vendor to determine if the CPU and operating system combination will experience a performance penalty due to software mitigations for these vulnerabilities. \n \n--- \n \n### Vendor Information\n\n584653\n\nFilter by status: All Affected Not Affected Unknown\n\nFilter by content: __ Vendor has issued information\n\n__ Sort by: Status Alphabetical\n\nExpand all\n\n__ Affected __ Unknown __ Unaffected \n\n**Javascript is disabled. Click here to view vendors.**\n\n### __ AMD \n\nUpdated: January 03, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://www.amd.com/en/corporate/speculative-execution>\n\n### __ Amazon \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://aws.amazon.com/security/security-bulletins/AWS-2018-013/>\n\n### __ Android Open Source Project \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://source.android.com/security/bulletin/2018-01-01>\n\n### __ Apple \n\nUpdated: February 02, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://support.apple.com/en-us/HT208394\nhttps://support.apple.com/en-us/HT208397\nhttps://support.apple.com/en-us/HT208403\nhttps://support.apple.com/en-us/HT208401\nhttps://support.apple.com/en-ca/HT208465>\n\n### Addendum\n\n<https://twitter.com/aionescu/status/948609809540046849> \n<https://twitter.com/ErrataRob/status/949088097475743744>\n\nIf you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:cert@cert.org?Subject=VU%23584653 Feedback>).\n\n### __ Arm \n\nUpdated: January 03, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://developer.arm.com/support/security-update\nhttps://developer.arm.com/-/media/Files/pdf/Cache_Speculation_Side-channels.pdf>\n\n### Addendum\n\n<https://lwn.net/Articles/740393/>\n\nIf you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:cert@cert.org?Subject=VU%23584653 Feedback>).\n\n### __ CentOS \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://lists.centos.org/pipermail/centos-announce/2018-January/date.html>\n\n### __ Cisco \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20180104-cpusidechannel>\n\n### __ Citrix \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://support.citrix.com/article/CTX231399>\n\n### __ Debian GNU/Linux \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://security-tracker.debian.org/tracker/CVE-2017-5754>\n\n### __ Dell \n\nUpdated: January 08, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<http://www.dell.com/support/contents/us/en/19/article/product-support/self-support-knowledgebase/software-and-downloads/support-for-meltdown-and-spectre>\n\n### __ DragonFly BSD Project \n\nUpdated: January 08, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<http://lists.dragonflybsd.org/pipermail/users/2018-January/313758.html>\n\n### __ Fedora Project \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://fedoramagazine.org/protect-fedora-system-meltdown/>\n\n### __ Fortinet, Inc. \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://fortiguard.com/psirt/FG-IR-18-002>\n\n### __ FreeBSD Project \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://www.freebsd.org/news/newsflash.html#event20180104:01>\n\n### __ Fujitsu \n\nUpdated: January 11, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<http://support.ts.fujitsu.com/content/SideChannelAnalysisMethod.asp?lng=EN>\n\n### __ Google \n\nUpdated: January 03, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://security.googleblog.com/2018/01/todays-cpu-vulnerability-what-you-need.html\nhttps://support.google.com/faqs/answer/7622138>\n\n### __ Hewlett Packard Enterprise \n\nUpdated: January 08, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://www.hpe.com/us/en/services/security-vulnerability.html>\n\n### __ IBM Corporation \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://www.ibm.com/blogs/psirt/potential-cpu-security-issue/>\n\n### __ Intel \n\nUpdated: January 22, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://newsroom.intel.com/news/intel-responds-to-security-research-findings/\nhttps://newsroom.intel.com/news-releases/intel-issues-updates-protect-systems-security-exploits\nhttps://www.intel.com/content/www/us/en/architecture-and-technology/facts-about-side-channel-analysis-and-intel-products.html\nhttps://newsroom.intel.com/news/root-cause-of-reboot-issue-identified-updated-guidance-for-customers-and-partners/\nhttps://newsroom.intel.com/wp-content/uploads/sites/11/2018/01/microcode-update-guidance.pdf>\n\n### __ Lenovo \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://support.lenovo.com/us/en/solutions/len-18282>\n\n### __ Linux Kernel \n\nUpdated: January 04, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://lkml.org/lkml/2017/11/22/956\nhttps://lkml.org/lkml/2018/1/4/174\nhttps://lkml.org/lkml/2018/1/4/615>\n\n### __ Microsoft \n\nUpdated: January 11, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://support.microsoft.com/en-us/help/4073119/protect-against-speculative-execution-side-channel-vulnerabilities-in\nhttps://support.microsoft.com/en-us/help/4072699/january-3-2018-windows-security-updates-and-antivirus-software\nhttps://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/CVE-2017-5715-and-hyper-v-vms\nhttps://portal.msrc.microsoft.com/en-US/security-guidance/advisory/ADV180002\nhttps://blogs.windows.com/msedgedev/2018/01/03/speculative-execution-mitigations-microsoft-edge-internet-explorer/\nhttps://azure.microsoft.com/en-us/blog/securing-azure-customers-from-cpu-vulnerability/\nhttps://cloudblogs.microsoft.com/microsoftsecure/2018/01/09/understanding-the-performance-impact-of-spectre-and-meltdown-mitigations-on-windows-systems/\nhttps://support.microsoft.com/en-us/help/4073707/windows-os-security-update-block-for-some-amd-based-devices>\n\n### Addendum\n\nNote that Windows systems without antivirus do not appear to receive the ADV180002 update automatically. In order to receive the update through Windows Update, run the following command:\n\n \n`reg add \"HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\QualityCompat\" /v cadca5fe-87d3-4b96-b7fb-a231484277cc /t REG_DWORD /d 0 /f` \nIf a third-party antivirus product does not explicitly indicate compatibility with to the protections provided by ADV180002 using the above registry value, the system will not automatically receive the ADV180002 update \n\n### __ Mozilla \n\nUpdated: January 03, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://blog.mozilla.org/security/2018/01/03/mitigations-landing-new-class-timing-attack/>\n\n### __ NVIDIA \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<http://nvidia.custhelp.com/app/answers/detail/a_id/4609\nhttp://nvidia.custhelp.com/app/answers/detail/a_id/4611\nhttp://nvidia.custhelp.com/app/answers/detail/a_id/4613\nhttp://nvidia.custhelp.com/app/answers/detail/a_id/4614\nhttps://www.nvidia.com/en-us/product-security/>\n\n### __ NetBSD \n\nUpdated: January 08, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### __ OpenBSD \n\nUpdated: January 08, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n[https://marc.info/?l=openbsd-tech&m=151521435721902&w=2](<https://marc.info/?l=openbsd-tech&m=151521435721902&w=2>)\n\n### __ Oracle Corporation \n\nUpdated: February 23, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://www.theregister.co.uk/2018/01/16/oracle_quarterly_patches_jan_2018/>\n\n### __ QUALCOMM Incorporated \n\nUpdated: January 11, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Addendum\n\nThe Register has published the following: <https://www.theregister.co.uk/2018/01/06/qualcomm_processor_security_vulnerabilities/>\n\nIf you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:cert@cert.org?Subject=VU%23584653 Feedback>).\n\n### __ Red Hat, Inc. \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n[https://access.redhat.com/security/security-updates/#/security-advisories?q=&p=1&sort=portal_publication_date%20desc&rows=10&documentKind=PortalProduct](<https://access.redhat.com/security/security-updates/#/security-advisories?q=&p=1&sort=portal_publication_date%20desc&rows=10&documentKind=PortalProduct>)\n\n### __ SUSE Linux \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://www.suse.com/c/suse-addresses-meltdown-spectre-vulnerabilities/\nhttp://lists.suse.com/pipermail/sle-security-updates/2018-January/date.html>\n\n### __ Synology \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://www.synology.com/en-global/support/security/Synology_SA_18_01>\n\n### __ Trend Micro \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://success.trendmicro.com/solution/1119183-important-information-for-trend-micro-solutions-and-microsoft-january-2018-security-updates>\n\n### __ Ubuntu \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/SpectreAndMeltdown>\n\n### __ VMware \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://www.vmware.com/security/advisories/VMSA-2018-0002.html>\n\n### __ Xen \n\nUpdated: January 24, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<http://xenbits.xen.org/xsa/advisory-254.html\nhttps://blog.xenproject.org/2018/01/22/xen-project-spectre-meltdown-faq-jan-22-update/>\n\n### __ openSUSE project \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://lists.opensuse.org/opensuse-security-announce/2018-01/msg00001.html>\n\n### __ NetApp \n\nUpdated: January 08, 2018 \n\n### Status\n\n__ Not Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n[security.netapp.com/advisory/ntap-20180104-0001/](<security.netapp.com/advisory/ntap-20180104-0001/>)\n\n### __ Raspberry Pi \n\nUpdated: January 08, 2018 \n\n### Status\n\n__ Not Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://www.raspberrypi.org/blog/why-raspberry-pi-isnt-vulnerable-to-spectre-or-meltdown/>\n\n### __ __ Technicolor \n\nUpdated: January 08, 2018 \n\n### Status\n\n__ Not Affected\n\n### Vendor Statement\n\nBoth Spectre and Meltdown attacks presupposed \u201copen platforms\u201d, where \nadditional code can be added by a non-privileged user. The Technicolor products \nare not open platforms. Even where 3rd party application can run in containers \nand can be managed via Life Cycle Management, these applications are validated \nand signed before they can be installed on the platform. Technicolor is \ncurrently working with its vendors to identify if additional layers of \nprotection are needed. Yet, as the current platforms are closed and have secure \nbootloading mechanism in place, there is no risk and no privilege acquired by \nan attacker in exploiting such an attack on Technicolor's devices.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### __ ASUSTeK Computer Inc. \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Unknown\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### __ Acer \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Unknown\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### __ F5 Networks, Inc. \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Unknown\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://support.f5.com/csp/article/K91229003>\n\n### __ GIGABYTE \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Unknown\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### __ HP Inc. \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Unknown\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### __ Samsung Semiconductor Inc. \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Unknown\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### __ Toshiba Corporation \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Unknown\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n \n\n\n### CVSS Metrics \n\nGroup | Score | Vector \n---|---|--- \nBase | 4.4 | AV:L/AC:M/Au:S/C:C/I:N/A:N \nTemporal | 3.4 | E:POC/RL:OF/RC:C \nEnvironmental | 5.1 | CDP:ND/TD:H/CR:H/IR:ND/AR:ND \n \n \n\n\n### References \n\n * <https://vuls.cert.org/confluence/display/Wiki/Vulnerabilities+Associated+with+CPU+Speculative+Execution>\n * <https://meltdownattack.com/>\n * <https://meltdownattack.com/meltdown.pdf>\n * <https://spectreattack.com/>\n * <https://spectreattack.com/spectre.pdf>\n * <https://security.googleblog.com/2018/01/todays-cpu-vulnerability-what-you-need.html>\n * <https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html>\n * <https://cyber.wtf/2017/07/28/negative-result-reading-kernel-memory-from-user-mode/>\n * <https://github.com/IAIK/KAISER>\n * <https://gruss.cc/files/kaiser.pdf>\n * <https://gruss.cc/files/prefetch.pdf>\n * <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5aa90a84589282b87666f92b6c3c917c8080a9bf>\n * <https://lkml.org/lkml/2017/12/27/2>\n * <https://lkml.org/lkml/2018/1/4/615>\n * <https://lwn.net/Articles/741878/>\n * <https://lwn.net/Articles/737940/>\n * <https://lwn.net/Articles/742702/>\n * <http://pythonsweetness.tumblr.com/post/169166980422/the-mysterious-case-of-the-linux-page-table>\n * <https://nakedsecurity.sophos.com/2018/01/03/fckwit-aka-kaiser-aka-kpti-intel-cpu-flaw-needs-low-level-os-patches/>\n * <https://en.wikipedia.org/wiki/Kernel_page-table_isolation>\n * <https://chrisam.net/2018/01/04/speculative-execution-side-channel-vulnerabilities-vendor-published-info/>\n * <https://www.raspberrypi.org/blog/why-raspberry-pi-isnt-vulnerable-to-spectre-or-meltdown/>\n * <https://doublepulsar.com/important-information-about-microsoft-meltdown-cpu-security-fixes-antivirus-vendors-and-you-a852ba0292ec>\n * [https://docs.google.com/spreadsheets/d/184wcDt9I9TUNFFbsAVLpzAtckQxYiuirADzf3cL42FQ/htmlview?usp=sharing&sle=true](<https://docs.google.com/spreadsheets/d/184wcDt9I9TUNFFbsAVLpzAtckQxYiuirADzf3cL42FQ/htmlview?usp=sharing&sle=true>)\n * <https://github.com/iadgov/Spectre-and-Meltdown-Guidance>\n * <https://arxiv.org/abs/1802.03802>\n\n### Credit\n\nThese issues were researched and reported by researchers at Google Project Zero (Jann Horn) the Institute of Applied Information Processing and Communications (IAIK) at Graz University of Technology (Gruss et. al.), Paul Kocher, and Anders Fogh. \n\nThis document was written by Art Manion and Will Dormann. \n\n### Other Information\n\n**CVE IDs:** | [CVE-2017-5753, ](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5753>) [CVE-2017-5715, ](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5715>) [CVE-2017-5754](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5754>) \n---|--- \n**Date Public:** | 2018-01-03 \n**Date First Published:** | 2018-01-04 \n**Date Last Updated: ** | 2018-07-03 21:27 UTC \n**Document Revision: ** | 230 \n", "published": "2018-01-04T00:00:00", "modified": "2018-07-03T21:27:00", "cvss": {"score": 4.7, "vector": "AV:LOCAL/AC:MEDIUM/Au:NONE/C:COMPLETE/I:NONE/A:NONE/"}, "href": "https://www.kb.cert.org/vuls/id/584653", "reporter": "CERT", "references": ["https://vuls.cert.org/confluence/display/Wiki/Vulnerabilities+Associated+with+CPU+Speculative+Execution", "https://meltdownattack.com/", "https://meltdownattack.com/meltdown.pdf", "https://spectreattack.com/", "https://spectreattack.com/spectre.pdf", "https://security.googleblog.com/2018/01/todays-cpu-vulnerability-what-you-need.html", "https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html", "https://cyber.wtf/2017/07/28/negative-result-reading-kernel-memory-from-user-mode/", "https://github.com/IAIK/KAISER", "https://gruss.cc/files/kaiser.pdf", "https://gruss.cc/files/prefetch.pdf", "https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5aa90a84589282b87666f92b6c3c917c8080a9bf", "https://lkml.org/lkml/2017/12/27/2", "https://lkml.org/lkml/2018/1/4/615", "https://lwn.net/Articles/741878/", "https://lwn.net/Articles/737940/", "https://lwn.net/Articles/742702/", "http://pythonsweetness.tumblr.com/post/169166980422/the-mysterious-case-of-the-linux-page-table", "https://nakedsecurity.sophos.com/2018/01/03/fckwit-aka-kaiser-aka-kpti-intel-cpu-flaw-needs-low-level-os-patches/", "https://en.wikipedia.org/wiki/Kernel_page-table_isolation", "https://chrisam.net/2018/01/04/speculative-execution-side-channel-vulnerabilities-vendor-published-info/", "https://www.raspberrypi.org/blog/why-raspberry-pi-isnt-vulnerable-to-spectre-or-meltdown/", "https://doublepulsar.com/important-information-about-microsoft-meltdown-cpu-security-fixes-antivirus-vendors-and-you-a852ba0292ec", "https://docs.google.com/spreadsheets/d/184wcDt9I9TUNFFbsAVLpzAtckQxYiuirADzf3cL42FQ/htmlview?usp=sharing&sle=true", "https://github.com/iadgov/Spectre-and-Meltdown-Guidance", "https://arxiv.org/abs/1802.03802"], "cvelist": ["CVE-2017-5715", "CVE-2017-5753", "CVE-2017-5754"], "lastseen": "2018-12-25T20:17:38", "history": [], "viewCount": 842, "enchantments": {"score": {"value": 7.2, "vector": "NONE"}, "dependencies": {"references": [{"type": "f5", "idList": ["F5:K91229003"]}, {"type": "symantec", "idList": ["SMNTC-102378", "SMNTC-102371"]}, {"type": "cve", "idList": ["CVE-2017-5753", "CVE-2017-5754", "CVE-2017-5715"]}, {"type": "redhat", "idList": ["RHSA-2018:0089", "RHSA-2018:0007", "RHSA-2018:0090", "RHSA-2018:0020", "RHSA-2018:0092", "RHSA-2018:0010", "RHSA-2018:0018", "RHSA-2018:0512", "RHSA-2018:0008", "RHSA-2018:0016"]}, {"type": "nessus", "idList": ["REDHAT-RHSA-2018-0496.NASL", "AIX_IJ03035.NASL", "REDHAT-RHSA-2018-0010.NASL", "REDHAT-RHSA-2018-0512.NASL", "REDHAT-RHSA-2018-0011.NASL", "UBUNTU_USN-3516-1.NASL", "ORACLEVM_OVMSA-2018-0029.NASL", "AIX_IJ03033.NASL", "EULEROS_SA-2018-1001.NASL", "ORACLELINUX_ELSA-2018-0007.NASL"]}, {"type": "malwarebytes", "idList": ["MALWAREBYTES:C47D8F4321BF60FB315B6C46B47DF46F"]}, {"type": "xen", "idList": ["XSA-254"]}, {"type": "openvas", "idList": ["OPENVAS:1361412562310882855", "OPENVAS:1361412562310882822", "OPENVAS:1361412562310843474", "OPENVAS:1361412562310812295", "OPENVAS:1361412562310843405", "OPENVAS:1361412562310843424"]}, {"type": "kitploit", "idList": ["KITPLOIT:8752367943592764867"]}, {"type": "suse", "idList": ["SUSE-SU-2018:0131-1", "SUSE-SU-2018:0113-1", "SUSE-SU-2018:0069-1", "SUSE-SU-2018:0171-1", "SUSE-SU-2018:0114-1"]}, {"type": "lenovo", "idList": ["LENOVO:PS500151-NOSID"]}, {"type": "centos", "idList": ["CESA-2018:0008", "CESA-2018:0007", "CESA-2018:0512"]}, {"type": "ubuntu", "idList": ["USN-3597-1", "USN-3540-1", "USN-3541-2", "USN-3516-1"]}, {"type": "threatpost", "idList": ["THREATPOST:0F9EDE9A622A021B9B79C50214D7E8AD"]}, {"type": "oraclelinux", "idList": ["ELSA-2018-4012", "ELSA-2018-0007"]}, {"type": "qualysblog", "idList": ["QUALYSBLOG:F8AA5B21D90BCDD30391A24D6FD47892", "QUALYSBLOG:BD020D07BF02B0790C62701D997BFD4D", "QUALYSBLOG:3ACE52E54FF5FE3EF1B0FC328181FA66"]}, {"type": "securelist", "idList": ["SECURELIST:7CF4DDEB1B5407DAA24EC25BAA7A9654"]}, {"type": "vmware", "idList": ["VMSA-2018-0007"]}, {"type": "huawei", "idList": ["HUAWEI-SA-20180106-01-CPU"]}, {"type": "thn", "idList": ["THN:58CFE19533148E77597FE0AC59963145"]}], "modified": "2018-12-25T20:17:38"}}, "objectVersion": "1.4"}, "lastseen": "2018-12-25T20:17:38", "differentElements": ["description"], "edition": 21}, {"bulletin": {"id": "VU:584653", "hash": "3bb9f756d7625d11395e7702fc2518be", "type": "cert", "bulletinFamily": "info", "title": "CPU hardware vulnerable to side-channel attacks", "description": "### Overview \n\nCPU hardware implementations are vulnerable to cache side-channel attacks. These vulnerabilities are referred to as [Meltdown](<https://meltdownattack.com/>) and [Spectre](<https://spectreattack.com/>).\n\n### Description \n\nCPU hardware implementations are vulnerable to side-channel attacks referred to as [Meltdown](<https://meltdownattack.com/>) and [Spectre](<https://spectreattack.com/>). Both Spectre and Meltdown take advantage of the ability to extract information from instructions that have executed on a CPU using the CPU cache as a side-channel. These attacks are described in detail by [Google Project Zero](<https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html>), the Institute of Applied Information Processing and Communications (IAIK) at Graz University of Technology (TU Graz) and Anders Fogh. The issues are organized into three variants:\n\n * Variant 1 (CVE-2017-5753, [Spectre](<https://spectreattack.com/spectre.pdf>)): Bounds check bypass\n * Variant 2 (CVE-2017-5715, also [Spectre](<https://spectreattack.com/spectre.pdf>)): Branch target injection[](<https://spectreattack.com/spectre.pdf>)\n * Variant 3 (CVE-2017-5754, [Meltdown](<https://meltdownattack.com/meltdown.pdf>)): Rogue data cache load, memory access permission check performed after kernel memory read\n \n**Spectre** \n \nSpectre attacks take advantage of a CPU's branch prediction capabilities. Modern CPUs include a feature called branch prediction, which speculatively executes instructions at a location that the CPU believes it will branch to. Such speculative execution helps to more fully utilize the parts of the CPU, minimizing the time waiting, and therefore improving performance. When a branch is successfully predicted, instructions will retire, which means the outcomes of the instructions such as register and memory writes will be committed. If a branch is mispredicted, the speculatively-executed instructions will be discarded, and the direct side-effects of the instructions are undone. What is not undone are the indirect side-effects, such as CPU cache changes. By measuring latency of memory access operations, the cache can be used to extract values from speculatively-executed instructions. \n \nWith Spectre variant 1 (CVE-2017-5753), the instructions after a conditional branch are speculatively executed as the result of a misprediction. With Spectre variant 2 (CVE-2017-5715), the CPU executes instructions at a location determined by a mispredicted branch target. \n \nWith both variants of the Spectre attack, the impact is that a process may leak sensitive data to other processes on a system. Spectre may also allow one part of an application to access other parts of the same process memory space that would otherwise not be permitted. \n \nWhile the Spectre attack itself does not cross a user/kernel memory privilege boundary, depending on the configuration of the target platform, the Spectre attack may indirectly allow a user-space application to access kernel memory. For example, the[ Project Zero blog post](<https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html>) describes a scenario that uses eBPF to exfiltrate kernel memory contents into user-space code. This is made possible because eBPF JIT allows for userspace applications to inject code that is executed in kernel space. While this code is verified by the kernel, eBPF-compliant code will be allowed to execute with kernel permissions. The exploit described by Project Zero leverages eBPF to execute the Spectre attack in kernel space, while exfiltrating the data to user space. It is possible that other technologies that allow in-kernel code execution may also possibly be leveraged to leak kernel memory using Spectre. \n \n**Meltdown** \n \nMeltdown is related to the Spectre attack in that it also uses a cache side channel to access data that otherwise wouldn't be available. The main difference is that it leverages out-of-order execution capabilities in modern CPUs. Like speculative execution due to branch prediction, as used by Spectre, out-of-order execution on a CPU is a technique for ensuring fullest utilization of the CPU's parts. Although instructions may appear sequentially in the machine language, a CPU that supports out-of-order execution may execute instructions in a non-sequential manner, which can minimize the time that a CPU spends idle. \n \nMeltdown leverages insecure behavior that has been demonstrated in Intel CPUs and may affect CPUs from other vendors. Vulnerable CPUs allow memory reads in out-of-order instruction execution, and also contain a race condition between the raising of exceptions and the out-of-order instruction execution. The Meltdown attack reads a kernel memory value, which raises an exception because code running with user-space privileges are not permitted to directly read kernel memory. However, due to the race condition, out-of-order instructions following the faulting instruction may also execute. Even though instructions appear after the faulting instruction, out-of-order execution allows them to execute, using data retrieved from the instruction that raises the exception. By the time the exception is raised, some number of out-of-order instructions have executed. Although the raised exception causes the CPU to roll back the out-of-order instructions, the cache state is not reverted. This allows data from out-of-order instructions to persist beyond the point when the exception has been raised. \n \nThe impact of Meltdown is that a process running in user space is able to view the contents of kernel memory. Meltdown may also allow Spectre-like memory content leaking that does not cross the user/kernel privilege boundary. \n \nThe Linux kernel mitigations for Meltdown are referred to as KAISER, and subsequently KPTI, which aim to improve separation of kernel and user memory pages. Because the Spectre attacks do not cross user/kernel boundaries, the protections introduced with KAISER/KPTI do not add any protection against them. \n \nThe following table compares Spectre and Meltdown. \n \n| | **Spectre**| **Meltdown** \n---|---|--- \n**CPU mechanism for triggering**| Speculative execution from branch prediction| Out-of-order execution \n**Affected platforms**| CPUs that perform speculative execution from branch prediction| CPUs that allow memory reads in out-of-order instructions \n**Difficulty of successful attack**| High - Requires tailoring to the software environment of the victim process| Low - Kernel memory access exploit code is mostly universal \n**Impact**| Cross- and intra-process (including kernel) memory disclosure| Kernel memory disclosure to userspace \n**Software mitigations**| Variant 1: Compiler changes. Web browser updates to help prevent exploitation from JavaScript \nVariant 2: Indirect Branch Restricted Speculation ([IBRS](<https://lkml.org/lkml/2018/1/4/615>)). \n**Note: **The software mitigation for Spectre variant 2 requires CPU microcode updates| Kernel page-table isolation ([KPTI](<https://en.wikipedia.org/wiki/Kernel_page-table_isolation>)) \n \n### Impact \n\nAn attacker able to execute code with user privileges can achieve various impacts. The Meltdown attack allows reading of kernel memory from userspace. This can result in privilege escalation, disclosure of sensitive information, or it can weaken kernel-level protections, such as KASLR. The Spectre attack can allow inter-process or intra-process data leaks. \n \nTo execute code locally, an attacker would require a valid account or independent compromise of the target. Attacks using JavaScript in web browsers are possible. Multi-user and multi-tenant systems (including virtualized and cloud environments) likely face the greatest risk. Systems used to browse arbitrary web sites are also at risk. Single-user systems that do not readily provide a way for attackers to execute code locally face significantly lower risk. \n \n--- \n \n### Solution \n\n**Apply updates** \n \nOperating system, CPU microcode updates, and some application updates mitigate these attacks. Note that in many cases, the software fixes for these vulnerabilities will have a negative affect on system performance. Also note that Microsoft Windows systems [will no longer receive security updates](<https://doublepulsar.com/important-information-about-microsoft-meltdown-cpu-security-fixes-antivirus-vendors-and-you-a852ba0292ec>) via Windows Update if they are not running compliant anti-virus software. As with deploying any software updates, be sure to prioritize and test updates as necessary. \n \n**Consider CPU Options** \n \nInitial reports from the field indicate that overall system performance is impacted by many of the available patches for these vulnerabilities. Depending on the software workflow and the CPU capabilities present, the performance impact of software mitigations may be non-trivial and therefore may become an ongoing operational concern for some organizations. While we recognize that replacing existing CPUs in already deployed systems is not practical, organizations acquiring new systems should evaluate their CPU selection in light of the expected longevity of this vulnerability in available hardware as well as the performance impacts resulting from the various platform-specific software patches. Deployment contexts and performance requirements vary widely, and must be balanced by informed evaluation of the associated security risks. Contact your system vendor to determine if the CPU and operating system combination will experience a performance penalty due to software mitigations for these vulnerabilities. \n \n--- \n \n### Vendor Information\n\n584653\n\nFilter by status: All Affected Not Affected Unknown\n\nFilter by content: __ Vendor has issued information\n\n__ Sort by: Status Alphabetical\n\nExpand all\n\n__ Affected __ Unknown __ Unaffected \n\n**Javascript is disabled. Click here to view vendors.**\n\n### __ AMD \n\nUpdated: January 03, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://www.amd.com/en/corporate/speculative-execution>\n\n### __ Amazon \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://aws.amazon.com/security/security-bulletins/AWS-2018-013/>\n\n### __ Android Open Source Project \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://source.android.com/security/bulletin/2018-01-01>\n\n### __ Apple \n\nUpdated: February 02, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://support.apple.com/en-us/HT208394\nhttps://support.apple.com/en-us/HT208397\nhttps://support.apple.com/en-us/HT208403\nhttps://support.apple.com/en-us/HT208401\nhttps://support.apple.com/en-ca/HT208465>\n\n### Addendum\n\n<https://twitter.com/aionescu/status/948609809540046849> \n<https://twitter.com/ErrataRob/status/949088097475743744>\n\nIf you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:cert@cert.org?Subject=VU%23584653 Feedback>).\n\n### __ Arm \n\nUpdated: January 03, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://developer.arm.com/support/security-update\nhttps://developer.arm.com/-/media/Files/pdf/Cache_Speculation_Side-channels.pdf>\n\n### Addendum\n\n<https://lwn.net/Articles/740393/>\n\nIf you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:cert@cert.org?Subject=VU%23584653 Feedback>).\n\n### __ CentOS \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://lists.centos.org/pipermail/centos-announce/2018-January/date.html>\n\n### __ Cisco \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20180104-cpusidechannel>\n\n### __ Citrix \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://support.citrix.com/article/CTX231399>\n\n### __ Debian GNU/Linux \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://security-tracker.debian.org/tracker/CVE-2017-5754>\n\n### __ Dell \n\nUpdated: January 08, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<http://www.dell.com/support/contents/us/en/19/article/product-support/self-support-knowledgebase/software-and-downloads/support-for-meltdown-and-spectre>\n\n### __ DragonFly BSD Project \n\nUpdated: January 08, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<http://lists.dragonflybsd.org/pipermail/users/2018-January/313758.html>\n\n### __ Fedora Project \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://fedoramagazine.org/protect-fedora-system-meltdown/>\n\n### __ Fortinet, Inc. \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://fortiguard.com/psirt/FG-IR-18-002>\n\n### __ FreeBSD Project \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://www.freebsd.org/news/newsflash.html#event20180104:01>\n\n### __ Fujitsu \n\nUpdated: January 11, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<http://support.ts.fujitsu.com/content/SideChannelAnalysisMethod.asp?lng=EN>\n\n### __ Google \n\nUpdated: January 03, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://security.googleblog.com/2018/01/todays-cpu-vulnerability-what-you-need.html\nhttps://support.google.com/faqs/answer/7622138>\n\n### __ Hewlett Packard Enterprise \n\nUpdated: January 08, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://www.hpe.com/us/en/services/security-vulnerability.html>\n\n### __ IBM Corporation \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://www.ibm.com/blogs/psirt/potential-cpu-security-issue/>\n\n### __ Intel \n\nUpdated: January 22, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://newsroom.intel.com/news/intel-responds-to-security-research-findings/\nhttps://newsroom.intel.com/news-releases/intel-issues-updates-protect-systems-security-exploits\nhttps://www.intel.com/content/www/us/en/architecture-and-technology/facts-about-side-channel-analysis-and-intel-products.html\nhttps://newsroom.intel.com/news/root-cause-of-reboot-issue-identified-updated-guidance-for-customers-and-partners/\nhttps://newsroom.intel.com/wp-content/uploads/sites/11/2018/01/microcode-update-guidance.pdf>\n\n### __ Lenovo \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://support.lenovo.com/us/en/solutions/len-18282>\n\n### __ Linux Kernel \n\nUpdated: January 04, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://lkml.org/lkml/2017/11/22/956\nhttps://lkml.org/lkml/2018/1/4/174\nhttps://lkml.org/lkml/2018/1/4/615>\n\n### __ Microsoft \n\nUpdated: January 11, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://support.microsoft.com/en-us/help/4073119/protect-against-speculative-execution-side-channel-vulnerabilities-in\nhttps://support.microsoft.com/en-us/help/4072699/january-3-2018-windows-security-updates-and-antivirus-software\nhttps://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/CVE-2017-5715-and-hyper-v-vms\nhttps://portal.msrc.microsoft.com/en-US/security-guidance/advisory/ADV180002\nhttps://blogs.windows.com/msedgedev/2018/01/03/speculative-execution-mitigations-microsoft-edge-internet-explorer/\nhttps://azure.microsoft.com/en-us/blog/securing-azure-customers-from-cpu-vulnerability/\nhttps://cloudblogs.microsoft.com/microsoftsecure/2018/01/09/understanding-the-performance-impact-of-spectre-and-meltdown-mitigations-on-windows-systems/\nhttps://support.microsoft.com/en-us/help/4073707/windows-os-security-update-block-for-some-amd-based-devices>\n\n### Addendum\n\nNote that Windows systems without antivirus do not appear to receive the ADV180002 update automatically. In order to receive the update through Windows Update, run the following command:\n\n \n`reg add \"HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\QualityCompat\" /v cadca5fe-87d3-4b96-b7fb-a231484277cc /t REG_DWORD /d 0 /f` \nIf a third-party antivirus product does not explicitly indicate compatibility with to the protections provided by ADV180002 using the above registry value, the system will not automatically receive the ADV180002 update as well. \n \nOnce a system has the ADV180002 update installed, it must be manually activated using the following commands to make the appropriate registry changes: \n\n\n`reg add \"HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Control\\Session Manager\\Memory Management\" /v FeatureSettingsOverride /t REG_DWORD /d 0 /f` \n`reg add \"HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Control\\Session Manager\\Memory Management\" /v FeatureSettingsOverrideMask /t REG_DWORD /d 3 /f` \n`reg add \"HKLM\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Virtualization\" /v MinVmVersionForCpuBasedMitigations /t REG_SZ /d \"1.0\" /f ` \nAlso note that in addition to the above changes, ADV180002 requires CPU microcode updates to achieve full protection. In some cases, Windows Update may not automatically install the ADV180002 update. An unofficial spreadsheet of antivirus vendor compatibility with this update is maintained here: \n \nOn systems that have not received the ADV180002 update automatically, you may have to install the update manually. Please see for more details. \n \nTo verify that your Windows system has protections against Meltdown and Spectre variant 2, in a PowerShell session running with Administrator privileges, run:\n\n 1. `Install-Module SpeculationControl` \nIf this fails, you may need to install [PackageManagement PowerShell Modules](<https://www.microsoft.com/en-us/download/details.aspx?id=51451>)\n 2. `Get-SpeculationControlSettings` \nIf this fails, you may need to change your PowerShell ExecutionPolicy setting: ` \nSet-ExecutionPolicy RemoteSigned \n`Once you are satisfied with the PowerShell output, you can revert the ExecutionPolicy setting back to the default Restricted setting by running: \n`Set-ExecutionPolicy Restricted`\n` ` \nThe output of this PowerShell command will indicate the status of whether the CPU has the required microcode update, whether Windows has the required software update installed, and whether the mitigations are enabled. Any setting that indicates \"False\" is an indicator of incomplete protection from Meltdown and/or Spectre. \n \nFor example, a system that has the ADV180002 update properly installed and enabled, but is missing the CPU microcode update to fully enable the protections will show output like this: \n \n \nOnce the CPU microcode is updated on such a system (e.g. by way of a BIOS update) , the output will look like this, which indicates that the protections that Microsoft have released are fully enabled: \n \n \nIf the above PowerShell command indicates \"Windows OS support for PCID optimization is enabled: False\", this is a symptom of using a processor that doesn't support process context identifiers (PCID). Such processors cannot take advantage of the performance optimization that avoids a TLB flush. \n \nIf the above PowerShell command indicates \"Hardware requires kernel VA shadowing: False\", this is a symptom of using a processor that doesn't require mitigations for CVE-2017-5754 (Meltdown). \n \nAlso note that Microsoft has not yet provided protection for CVE-2017-5754 (Meltdown) on affected 32-bit platforms. \n\nIf you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:cert@cert.org?Subject=VU%23584653 Feedback>).\n\n### __ Mozilla \n\nUpdated: January 03, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://blog.mozilla.org/security/2018/01/03/mitigations-landing-new-class-timing-attack/>\n\n### __ NVIDIA \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<http://nvidia.custhelp.com/app/answers/detail/a_id/4609\nhttp://nvidia.custhelp.com/app/answers/detail/a_id/4611\nhttp://nvidia.custhelp.com/app/answers/detail/a_id/4613\nhttp://nvidia.custhelp.com/app/answers/detail/a_id/4614\nhttps://www.nvidia.com/en-us/product-security/>\n\n### __ NetBSD \n\nUpdated: January 08, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### __ OpenBSD \n\nUpdated: January 08, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n[https://marc.info/?l=openbsd-tech&m=151521435721902&w=2](<https://marc.info/?l=openbsd-tech&m=151521435721902&w=2>)\n\n### __ Oracle Corporation \n\nUpdated: February 23, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://www.theregister.co.uk/2018/01/16/oracle_quarterly_patches_jan_2018/>\n\n### __ QUALCOMM Incorporated \n\nUpdated: January 11, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Addendum\n\nThe Register has published the following: <https://www.theregister.co.uk/2018/01/06/qualcomm_processor_security_vulnerabilities/>\n\nIf you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:cert@cert.org?Subject=VU%23584653 Feedback>).\n\n### __ Red Hat, Inc. \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n[https://access.redhat.com/security/security-updates/#/security-advisories?q=&p=1&sort=portal_publication_date%20desc&rows=10&documentKind=PortalProduct](<https://access.redhat.com/security/security-updates/#/security-advisories?q=&p=1&sort=portal_publication_date%20desc&rows=10&documentKind=PortalProduct>)\n\n### __ SUSE Linux \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://www.suse.com/c/suse-addresses-meltdown-spectre-vulnerabilities/\nhttp://lists.suse.com/pipermail/sle-security-updates/2018-January/date.html>\n\n### __ Synology \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://www.synology.com/en-global/support/security/Synology_SA_18_01>\n\n### __ Trend Micro \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://success.trendmicro.com/solution/1119183-important-information-for-trend-micro-solutions-and-microsoft-january-2018-security-updates>\n\n### __ Ubuntu \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/SpectreAndMeltdown>\n\n### __ VMware \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://www.vmware.com/security/advisories/VMSA-2018-0002.html>\n\n### __ Xen \n\nUpdated: January 24, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<http://xenbits.xen.org/xsa/advisory-254.html\nhttps://blog.xenproject.org/2018/01/22/xen-project-spectre-meltdown-faq-jan-22-update/>\n\n### __ openSUSE project \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://lists.opensuse.org/opensuse-security-announce/2018-01/msg00001.html>\n\n### __ NetApp \n\nUpdated: January 08, 2018 \n\n### Status\n\n__ Not Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n[security.netapp.com/advisory/ntap-20180104-0001/](<security.netapp.com/advisory/ntap-20180104-0001/>)\n\n### __ Raspberry Pi \n\nUpdated: January 08, 2018 \n\n### Status\n\n__ Not Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://www.raspberrypi.org/blog/why-raspberry-pi-isnt-vulnerable-to-spectre-or-meltdown/>\n\n### __ __ Technicolor \n\nUpdated: January 08, 2018 \n\n### Status\n\n__ Not Affected\n\n### Vendor Statement\n\nBoth Spectre and Meltdown attacks presupposed \u201copen platforms\u201d, where \nadditional code can be added by a non-privileged user. The Technicolor products \nare not open platforms. Even where 3rd party application can run in containers \nand can be managed via Life Cycle Management, these applications are validated \nand signed before they can be installed on the platform. Technicolor is \ncurrently working with its vendors to identify if additional layers of \nprotection are needed. Yet, as the current platforms are closed and have secure \nbootloading mechanism in place, there is no risk and no privilege acquired by \nan attacker in exploiting such an attack on Technicolor's devices.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### __ ASUSTeK Computer Inc. \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Unknown\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### __ Acer \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Unknown\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### __ F5 Networks, Inc. \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Unknown\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://support.f5.com/csp/article/K91229003>\n\n### __ GIGABYTE \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Unknown\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### __ HP Inc. \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Unknown\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### __ Samsung Semiconductor Inc. \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Unknown\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### __ Toshiba Corporation \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Unknown\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n \n\n\n### CVSS Metrics \n\nGroup | Score | Vector \n---|---|--- \nBase | 4.4 | AV:L/AC:M/Au:S/C:C/I:N/A:N \nTemporal | 3.4 | E:POC/RL:OF/RC:C \nEnvironmental | 5.1 | CDP:ND/TD:H/CR:H/IR:ND/AR:ND \n \n \n\n\n### References \n\n * <https://vuls.cert.org/confluence/display/Wiki/Vulnerabilities+Associated+with+CPU+Speculative+Execution>\n * <https://meltdownattack.com/>\n * <https://meltdownattack.com/meltdown.pdf>\n * <https://spectreattack.com/>\n * <https://spectreattack.com/spectre.pdf>\n * <https://security.googleblog.com/2018/01/todays-cpu-vulnerability-what-you-need.html>\n * <https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html>\n * <https://cyber.wtf/2017/07/28/negative-result-reading-kernel-memory-from-user-mode/>\n * <https://github.com/IAIK/KAISER>\n * <https://gruss.cc/files/kaiser.pdf>\n * <https://gruss.cc/files/prefetch.pdf>\n * <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5aa90a84589282b87666f92b6c3c917c8080a9bf>\n * <https://lkml.org/lkml/2017/12/27/2>\n * <https://lkml.org/lkml/2018/1/4/615>\n * <https://lwn.net/Articles/741878/>\n * <https://lwn.net/Articles/737940/>\n * <https://lwn.net/Articles/742702/>\n * <http://pythonsweetness.tumblr.com/post/169166980422/the-mysterious-case-of-the-linux-page-table>\n * <https://nakedsecurity.sophos.com/2018/01/03/fckwit-aka-kaiser-aka-kpti-intel-cpu-flaw-needs-low-level-os-patches/>\n * <https://en.wikipedia.org/wiki/Kernel_page-table_isolation>\n * <https://chrisam.net/2018/01/04/speculative-execution-side-channel-vulnerabilities-vendor-published-info/>\n * <https://www.raspberrypi.org/blog/why-raspberry-pi-isnt-vulnerable-to-spectre-or-meltdown/>\n * <https://doublepulsar.com/important-information-about-microsoft-meltdown-cpu-security-fixes-antivirus-vendors-and-you-a852ba0292ec>\n * [https://docs.google.com/spreadsheets/d/184wcDt9I9TUNFFbsAVLpzAtckQxYiuirADzf3cL42FQ/htmlview?usp=sharing&sle=true](<https://docs.google.com/spreadsheets/d/184wcDt9I9TUNFFbsAVLpzAtckQxYiuirADzf3cL42FQ/htmlview?usp=sharing&sle=true>)\n * <https://github.com/iadgov/Spectre-and-Meltdown-Guidance>\n * <https://arxiv.org/abs/1802.03802>\n\n### Credit\n\nThese issues were researched and reported by researchers at Google Project Zero (Jann Horn) the Institute of Applied Information Processing and Communications (IAIK) at Graz University of Technology (Gruss et. al.), Paul Kocher, and Anders Fogh. \n\nThis document was written by Art Manion and Will Dormann. \n\n### Other Information\n\n**CVE IDs:** | [CVE-2017-5753, ](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5753>) [CVE-2017-5715, ](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5715>) [CVE-2017-5754](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5754>) \n---|--- \n**Date Public:** | 2018-01-03 \n**Date First Published:** | 2018-01-04 \n**Date Last Updated: ** | 2018-07-03 21:27 UTC \n**Document Revision: ** | 230 \n", "published": "2018-01-04T00:00:00", "modified": "2018-07-03T21:27:00", "cvss": {"score": 4.7, "vector": "AV:LOCAL/AC:MEDIUM/Au:NONE/C:COMPLETE/I:NONE/A:NONE/"}, "href": "https://www.kb.cert.org/vuls/id/584653", "reporter": "CERT", "references": ["https://vuls.cert.org/confluence/display/Wiki/Vulnerabilities+Associated+with+CPU+Speculative+Execution", "https://meltdownattack.com/", "https://meltdownattack.com/meltdown.pdf", "https://spectreattack.com/", "https://spectreattack.com/spectre.pdf", "https://security.googleblog.com/2018/01/todays-cpu-vulnerability-what-you-need.html", "https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html", "https://cyber.wtf/2017/07/28/negative-result-reading-kernel-memory-from-user-mode/", "https://github.com/IAIK/KAISER", "https://gruss.cc/files/kaiser.pdf", "https://gruss.cc/files/prefetch.pdf", "https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5aa90a84589282b87666f92b6c3c917c8080a9bf", "https://lkml.org/lkml/2017/12/27/2", "https://lkml.org/lkml/2018/1/4/615", "https://lwn.net/Articles/741878/", "https://lwn.net/Articles/737940/", "https://lwn.net/Articles/742702/", "http://pythonsweetness.tumblr.com/post/169166980422/the-mysterious-case-of-the-linux-page-table", "https://nakedsecurity.sophos.com/2018/01/03/fckwit-aka-kaiser-aka-kpti-intel-cpu-flaw-needs-low-level-os-patches/", "https://en.wikipedia.org/wiki/Kernel_page-table_isolation", "https://chrisam.net/2018/01/04/speculative-execution-side-channel-vulnerabilities-vendor-published-info/", "https://www.raspberrypi.org/blog/why-raspberry-pi-isnt-vulnerable-to-spectre-or-meltdown/", "https://doublepulsar.com/important-information-about-microsoft-meltdown-cpu-security-fixes-antivirus-vendors-and-you-a852ba0292ec", "https://docs.google.com/spreadsheets/d/184wcDt9I9TUNFFbsAVLpzAtckQxYiuirADzf3cL42FQ/htmlview?usp=sharing&sle=true", "https://github.com/iadgov/Spectre-and-Meltdown-Guidance", "https://arxiv.org/abs/1802.03802"], "cvelist": ["CVE-2017-5715", "CVE-2017-5753", "CVE-2017-5754"], "lastseen": "2019-03-14T18:39:23", "history": [], "viewCount": 852, "enchantments": {"score": {"value": 7.2, "vector": "NONE"}, "dependencies": {"references": [{"type": "f5", "idList": ["F5:K91229003"]}, {"type": "symantec", "idList": ["SMNTC-102371", "SMNTC-102378"]}, {"type": "cve", "idList": ["CVE-2017-5753", "CVE-2017-5715", "CVE-2017-5754"]}, {"type": "redhat", "idList": ["RHSA-2018:0089", "RHSA-2018:0090", "RHSA-2018:0007", "RHSA-2018:0020", "RHSA-2018:0010", "RHSA-2018:0092", "RHSA-2018:0512", "RHSA-2018:0018", "RHSA-2018:0292", "RHSA-2018:0496"]}, {"type": "nessus", "idList": ["REDHAT-RHSA-2018-0512.NASL", "REDHAT-RHSA-2018-0010.NASL", "REDHAT-RHSA-2018-0496.NASL", "ORACLEVM_OVMSA-2018-0029.NASL", "EULEROS_SA-2018-1001.NASL", "REDHAT-RHSA-2018-0011.NASL", "AIX_IJ03033.NASL", "UBUNTU_USN-3516-1.NASL", "AIX_IJ03035.NASL", "XEN_SERVER_XSA-254.NASL"]}, {"type": "xen", "idList": ["XSA-254"]}, {"type": "threatpost", "idList": ["THREATPOST:0F9EDE9A622A021B9B79C50214D7E8AD", "THREATPOST:7458AE86ECA810D873D5D35916A93D9F"]}, {"type": "openvas", "idList": ["OPENVAS:1361412562310882855", "OPENVAS:1361412562310882822", "OPENVAS:1361412562310843474", "OPENVAS:1361412562310812295", "OPENVAS:1361412562310843423", "OPENVAS:1361412562310812296", "OPENVAS:1361412562310812740"]}, {"type": "suse", "idList": ["SUSE-SU-2018:0113-1", "SUSE-SU-2018:0131-1", "SUSE-SU-2018:0069-1"]}, {"type": "kitploit", "idList": ["KITPLOIT:8752367943592764867"]}, {"type": "lenovo", "idList": ["LENOVO:PS500151-NOSID"]}, {"type": "centos", "idList": ["CESA-2018:0008", "CESA-2018:0007"]}, {"type": "malwarebytes", "idList": ["MALWAREBYTES:C47D8F4321BF60FB315B6C46B47DF46F", "MALWAREBYTES:3DDE32E41BE8356C194673EE3ED7FDBE"]}, {"type": "oraclelinux", "idList": ["ELSA-2018-4012"]}, {"type": "ubuntu", "idList": ["USN-3597-1", "USN-3540-1", "USN-3516-1"]}, {"type": "vmware", "idList": ["VMSA-2018-0007"]}, {"type": "securelist", "idList": ["SECURELIST:7CF4DDEB1B5407DAA24EC25BAA7A9654"]}, {"type": "qualysblog", "idList": ["QUALYSBLOG:BD020D07BF02B0790C62701D997BFD4D", "QUALYSBLOG:F8AA5B21D90BCDD30391A24D6FD47892", "QUALYSBLOG:D893D4DFB7141FDAD0BE869440074392", "QUALYSBLOG:F7C32BA5E6651A8CE3584BB84A88A0C0"]}, {"type": "thn", "idList": ["THN:788E9312DDA39D9A09855DF379A0FD4D", "THN:58CFE19533148E77597FE0AC59963145"]}, {"type": "cloudfoundry", "idList": ["CFOUNDRY:86B5C35F8F0E334D1CCCDAF1214EDFEF"]}, {"type": "talosblog", "idList": ["TALOSBLOG:6AF8BBB020A686E442B50095CA9B7A36"]}, {"type": "huawei", "idList": ["HUAWEI-SA-20180106-01-CPU"]}], "modified": "2019-03-14T18:39:23"}}, "objectVersion": "1.4"}, "lastseen": "2019-03-14T18:39:23", "differentElements": ["description"], "edition": 22}, {"bulletin": {"id": "VU:584653", "hash": "a2dea5c6d99bc0ab45934be0c3de8de8", "type": "cert", "bulletinFamily": "info", "title": "CPU hardware vulnerable to side-channel attacks", "description": "### Overview \n\nCPU hardware implementations are vulnerable to cache side-channel attacks. These vulnerabilities are referred to as [Meltdown](<https://meltdownattack.com/>) and [Spectre](<https://spectreattack.com/>).\n\n### Description \n\nCPU hardware implementations are vulnerable to side-channel attacks referred to as [Meltdown](<https://meltdownattack.com/>) and [Spectre](<https://spectreattack.com/>). Both Spectre and Meltdown take advantage of the ability to extract information from instructions that have executed on a CPU using the CPU cache as a side-channel. These attacks are described in detail by [Google Project Zero](<https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html>), the Institute of Applied Information Processing and Communications (IAIK) at Graz University of Technology (TU Graz) and Anders Fogh. The issues are organized into three variants:\n\n * Variant 1 (CVE-2017-5753, [Spectre](<https://spectreattack.com/spectre.pdf>)): Bounds check bypass\n * Variant 2 (CVE-2017-5715, also [Spectre](<https://spectreattack.com/spectre.pdf>)): Branch target injection[](<https://spectreattack.com/spectre.pdf>)\n * Variant 3 (CVE-2017-5754, [Meltdown](<https://meltdownattack.com/meltdown.pdf>)): Rogue data cache load, memory access permission check performed after kernel memory read\n \n**Spectre** \n \nSpectre attacks take advantage of a CPU's branch prediction capabilities. Modern CPUs include a feature called branch prediction, which speculatively executes instructions at a location that the CPU believes it will branch to. Such speculative execution helps to more fully utilize the parts of the CPU, minimizing the time waiting, and therefore improving performance. When a branch is successfully predicted, instructions will retire, which means the outcomes of the instructions such as register and memory writes will be committed. If a branch is mispredicted, the speculatively-executed instructions will be discarded, and the direct side-effects of the instructions are undone. What is not undone are the indirect side-effects, such as CPU cache changes. By measuring latency of memory access operations, the cache can be used to extract values from speculatively-executed instructions. \n \nWith Spectre variant 1 (CVE-2017-5753), the instructions after a conditional branch are speculatively executed as the result of a misprediction. With Spectre variant 2 (CVE-2017-5715), the CPU executes instructions at a location determined by a mispredicted branch target. \n \nWith both variants of the Spectre attack, the impact is that a process may leak sensitive data to other processes on a system. Spectre may also allow one part of an application to access other parts of the same process memory space that would otherwise not be permitted. \n \nWhile the Spectre attack itself does not cross a user/kernel memory privilege boundary, depending on the configuration of the target platform, the Spectre attack may indirectly allow a user-space application to access kernel memory. For example, the[ Project Zero blog post](<https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html>) describes a scenario that uses eBPF to exfiltrate kernel memory contents into user-space code. This is made possible because eBPF JIT allows for userspace applications to inject code that is executed in kernel space. While this code is verified by the kernel, eBPF-compliant code will be allowed to execute with kernel permissions. The exploit described by Project Zero leverages eBPF to execute the Spectre attack in kernel space, while exfiltrating the data to user space. It is possible that other technologies that allow in-kernel code execution may also possibly be leveraged to leak kernel memory using Spectre. \n \n**Meltdown** \n \nMeltdown is related to the Spectre attack in that it also uses a cache side channel to access data that otherwise wouldn't be available. The main difference is that it leverages out-of-order execution capabilities in modern CPUs. Like speculative execution due to branch prediction, as used by Spectre, out-of-order execution on a CPU is a technique for ensuring fullest utilization of the CPU's parts. Although instructions may appear sequentially in the machine language, a CPU that supports out-of-order execution may execute instructions in a non-sequential manner, which can minimize the time that a CPU spends idle. \n \nMeltdown leverages insecure behavior that has been demonstrated in Intel CPUs and may affect CPUs from other vendors. Vulnerable CPUs allow memory reads in out-of-order instruction execution, and also contain a race condition between the raising of exceptions and the out-of-order instruction execution. The Meltdown attack reads a kernel memory value, which raises an exception because code running with user-space privileges are not permitted to directly read kernel memory. However, due to the race condition, out-of-order instructions following the faulting instruction may also execute. Even though instructions appear after the faulting instruction, out-of-order execution allows them to execute, using data retrieved from the instruction that raises the exception. By the time the exception is raised, some number of out-of-order instructions have executed. Although the raised exception causes the CPU to roll back the out-of-order instructions, the cache state is not reverted. This allows data from out-of-order instructions to persist beyond the point when the exception has been raised. \n \nThe impact of Meltdown is that a process running in user space is able to view the contents of kernel memory. Meltdown may also allow Spectre-like memory content leaking that does not cross the user/kernel privilege boundary. \n \nThe Linux kernel mitigations for Meltdown are referred to as KAISER, and subsequently KPTI, which aim to improve separation of kernel and user memory pages. Because the Spectre attacks do not cross user/kernel boundaries, the protections introduced with KAISER/KPTI do not add any protection against them. \n \nThe following table compares Spectre and Meltdown. \n \n| | **Spectre**| **Meltdown** \n---|---|--- \n**CPU mechanism for triggering**| Speculative execution from branch prediction| Out-of-order execution \n**Affected platforms**| CPUs that perform speculative execution from branch prediction| CPUs that allow memory reads in out-of-order instructions \n**Difficulty of successful attack**| High - Requires tailoring to the software environment of the victim process| Low - Kernel memory access exploit code is mostly universal \n**Impact**| Cross- and intra-process (including kernel) memory disclosure| Kernel memory disclosure to userspace \n**Software mitigations**| Variant 1: Compiler changes. Web browser updates to help prevent exploitation from JavaScript \nVariant 2: Indirect Branch Restricted Speculation ([IBRS](<https://lkml.org/lkml/2018/1/4/615>)). \n**Note: **The software mitigation for Spectre variant 2 requires CPU microcode updates| Kernel page-table isolation ([KPTI](<https://en.wikipedia.org/wiki/Kernel_page-table_isolation>)) \n \n### Impact \n\nAn attacker able to execute code with user privileges can achieve various impacts. The Meltdown attack allows reading of kernel memory from userspace. This can result in privilege escalation, disclosure of sensitive information, or it can weaken kernel-level protections, such as KASLR. The Spectre attack can allow inter-process or intra-process data leaks. \n \nTo execute code locally, an attacker would require a valid account or independent compromise of the target. Attacks using JavaScript in web browsers are possible. Multi-user and multi-tenant systems (including virtualized and cloud environments) likely face the greatest risk. Systems used to browse arbitrary web sites are also at risk. Single-user systems that do not readily provide a way for attackers to execute code locally face significantly lower risk. \n \n--- \n \n### Solution \n\n**Apply updates** \n \nOperating system, CPU microcode updates, and some application updates mitigate these attacks. Note that in many cases, the software fixes for these vulnerabilities will have a negative affect on system performance. Also note that Microsoft Windows systems [will no longer receive security updates](<https://doublepulsar.com/important-information-about-microsoft-meltdown-cpu-security-fixes-antivirus-vendors-and-you-a852ba0292ec>) via Windows Update if they are not running compliant anti-virus software. As with deploying any software updates, be sure to prioritize and test updates as necessary. \n \n**Consider CPU Options** \n \nInitial reports from the field indicate that overall system performance is impacted by many of the available patches for these vulnerabilities. Depending on the software workflow and the CPU capabilities present, the performance impact of software mitigations may be non-trivial and therefore may become an ongoing operational concern for some organizations. While we recognize that replacing existing CPUs in already deployed systems is not practical, organizations acquiring new systems should evaluate their CPU selection in light of the expected longevity of this vulnerability in available hardware as well as the performance impacts resulting from the various platform-specific software patches. Deployment contexts and performance requirements vary widely, and must be balanced by informed evaluation of the associated security risks. Contact your system vendor to determine if the CPU and operating system combination will experience a performance penalty due to software mitigations for these vulnerabilities. \n \n--- \n \n### Vendor Information\n\n584653\n\nFilter by status: All Affected Not Affected Unknown\n\nFilter by content: __ Vendor has issued information\n\n__ Sort by: Status Alphabetical\n\nExpand all\n\n__ Affected __ Unknown __ Unaffected \n\n**Javascript is disabled. Click here to view vendors.**\n\n### __ AMD \n\nUpdated: January 03, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://www.amd.com/en/corporate/speculative-execution>\n\n### __ Amazon \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://aws.amazon.com/security/security-bulletins/AWS-2018-013/>\n\n### __ Android Open Source Project \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://source.android.com/security/bulletin/2018-01-01>\n\n### __ Apple \n\nUpdated: February 02, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://support.apple.com/en-us/HT208394\nhttps://support.apple.com/en-us/HT208397\nhttps://support.apple.com/en-us/HT208403\nhttps://support.apple.com/en-us/HT208401\nhttps://support.apple.com/en-ca/HT208465>\n\n### Addendum\n\n<https://twitter.com/aionescu/status/948609809540046849> \n<https://twitter.com/ErrataRob/status/949088097475743744>\n\nIf you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:cert@cert.org?Subject=VU%23584653 Feedback>).\n\n### __ Arm \n\nUpdated: January 03, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://developer.arm.com/support/security-update\nhttps://developer.arm.com/-/media/Files/pdf/Cache_Speculation_Side-channels.pdf>\n\n### Addendum\n\n<https://lwn.net/Articles/740393/>\n\nIf you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:cert@cert.org?Subject=VU%23584653 Feedback>).\n\n### __ CentOS \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://lists.centos.org/pipermail/centos-announce/2018-January/date.html>\n\n### __ Cisco \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20180104-cpusidechannel>\n\n### __ Citrix \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://support.citrix.com/article/CTX231399>\n\n### __ Debian GNU/Linux \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://security-tracker.debian.org/tracker/CVE-2017-5754>\n\n### __ Dell \n\nUpdated: January 08, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<http://www.dell.com/support/contents/us/en/19/article/product-support/self-support-knowledgebase/software-and-downloads/support-for-meltdown-and-spectre>\n\n### __ DragonFly BSD Project \n\nUpdated: January 08, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<http://lists.dragonflybsd.org/pipermail/users/2018-January/313758.html>\n\n### __ Fedora Project \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://fedoramagazine.org/protect-fedora-system-meltdown/>\n\n### __ Fortinet, Inc. \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://fortiguard.com/psirt/FG-IR-18-002>\n\n### __ FreeBSD Project \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://www.freebsd.org/news/newsflash.html#event20180104:01>\n\n### __ Fujitsu \n\nUpdated: January 11, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<http://support.ts.fujitsu.com/content/SideChannelAnalysisMethod.asp?lng=EN>\n\n### __ Google \n\nUpdated: January 03, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://security.googleblog.com/2018/01/todays-cpu-vulnerability-what-you-need.html\nhttps://support.google.com/faqs/answer/7622138>\n\n### __ Hewlett Packard Enterprise \n\nUpdated: January 08, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://www.hpe.com/us/en/services/security-vulnerability.html>\n\n### __ IBM Corporation \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://www.ibm.com/blogs/psirt/potential-cpu-security-issue/>\n\n### __ Intel \n\nUpdated: January 22, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://newsroom.intel.com/news/intel-responds-to-security-research-findings/\nhttps://newsroom.intel.com/news-releases/intel-issues-updates-protect-systems-security-exploits\nhttps://www.intel.com/content/www/us/en/architecture-and-technology/facts-about-side-channel-analysis-and-intel-products.html\nhttps://newsroom.intel.com/news/root-cause-of-reboot-issue-identified-updated-guidance-for-customers-and-partners/\nhttps://newsroom.intel.com/wp-content/uploads/sites/11/2018/01/microcode-update-guidance.pdf>\n\n### __ Lenovo \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://support.lenovo.com/us/en/solutions/len-18282>\n\n### __ Linux Kernel \n\nUpdated: January 04, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://lkml.org/lkml/2017/11/22/956\nhttps://lkml.org/lkml/2018/1/4/174\nhttps://lkml.org/lkml/2018/1/4/615>\n\n### __ Microsoft \n\nUpdated: January 11, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://support.microsoft.com/en-us/help/4073119/protect-against-speculative-execution-side-channel-vulnerabilities-in\nhttps://support.microsoft.com/en-us/help/4072699/january-3-2018-windows-security-updates-and-antivirus-software\nhttps://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/CVE-2017-5715-and-hyper-v-vms\nhttps://portal.msrc.microsoft.com/en-US/security-guidance/advisory/ADV180002\nhttps://blogs.windows.com/msedgedev/2018/01/03/speculative-execution-mitigations-microsoft-edge-internet-explorer/\nhttps://azure.microsoft.com/en-us/blog/securing-azure-customers-from-cpu-vulnerability/\nhttps://cloudblogs.microsoft.com/microsoftsecure/2018/01/09/understanding-the-performance-impact-of-spectre-and-meltdown-mitigations-on-windows-systems/\nhttps://support.microsoft.com/en-us/help/4073707/windows-os-security-update-block-for-some-amd-based-devices>\n\n### Addendum\n\nNote that Windows systems without antivirus do not appear to receive the ADV180002 update automatically. In order to receive the update through Windows Update, run the following command:\n\n \n`reg add \"HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\QualityCompat\" /v cadca5fe-87d3-4b96-b7fb-a231484277cc /t REG_DWORD /d 0 /f` \nIf a third-party antivirus product does not explicitly indicate compatibility with to the protections provided by ADV180002 using the above registry value, the system will not automatically receive the ADV180002 update as well. \n \nOnce a system has the ADV180002 update installed, it must be manually activated using the following commands to make the appropriate registry changes: \n\n\n`reg add \"HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Control\\Session Manager\\Memory Management\" /v FeatureSettingsOverride /t REG_DWORD /d 0 /f` \n`reg add \"HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Control\\Session Manager\\Memory Management\" /v FeatureSettingsOverrideMask /t REG_DWORD /d 3 /f` \n`reg add \"HKLM\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Virtualization\" /v MinVmVersionForCpuBasedMitigations /t REG_SZ /d \"1.0\" /f ` \nAlso note that in addition to the above changes, ADV180002 requires CPU microcode updates to achieve full protection. In some cases, Windows Update may not automatically install the ADV180002 update. An unofficial spreadsheet of antivirus vendor compatibility with this update is maintained here: \n \nOn systems that have not received the ADV180002 update automatically, you may have to install the update manually. Please see for more details. \n \nTo verify that your Windows system has protections against Meltdown and Spectre variant 2, in a PowerShell session running with Administrator privileges, run:\n\n 1. `Install-Module SpeculationControl` \nIf this fails, you may need to install [PackageManagement PowerShell Modules](<https://www.microsoft.com/en-us/download/details.aspx?id=51451>)\n 2. `Get-SpeculationControlSettings` \nIf this fails, you may need to change your PowerShell ExecutionPolicy setting: ` \nSet-ExecutionPolicy RemoteSigned \n`Once you are satisfied with the PowerShell output, you can revert the ExecutionPolicy setting back to the default Restricted setting by running: \n`Set-ExecutionPolicy Restricted`\n` ` \nThe output of this PowerShell command will indicate the status of whether the CPU has the required microcode update, whether Windows has the required software update installed, and whether the mitigations are enabled. Any setting that indicates \"False\" is an indicator of incomplete protection from Meltdown and/or Spectre. \n \nFor example, a system that has the ADV180002 update properly installed and enabled, but is missing the CPU microcode update to fully enable the protections will show output like this: \n \n \nOnce the CPU microcode is updated on such a system (e.g. by way of a BIOS update) , the output will look like this, which indicates that the protections that Microsoft have released are fully enabled: \n \n \nIf the above PowerShell command indicates \"Windows OS support for PCID optimization is enabled: False\", this is a symptom of using a processor that doesn't support process context identifiers (PCID). Such processors cannot take advantage of the performance optimization that avoids a TLB flush. \n \nIf the above PowerShell command indicates \"Hardware requires kernel VA shadowing: False\", this is a symptom of using a processor that doesn't require mitigations for CVE-2017-5754 (Meltdown). \n \nAlso note that Microsoft has not yet provided protection for CVE-2017-5754 (Meltdown) on affected 32-bit platforms. \n\nIf you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:cert@cert.org?Subject=VU%23584653 Feedback>).\n\n### __ Mozilla \n\nUpdated: January 03, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://blog.mozilla.org/security/2018/01/03/mitigations-landing-new-class-timing-attack/>\n\n### __ NVIDIA \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<http://nvidia.custhelp.com/app/answers/detail/a_id/4609\nhttp://nvidia.custhelp.com/app/answers/detail/a_id/4611\nhttp://nvidia.custhelp.com/app/answers/detail/a_id/4613\nhttp://nvidia.custhelp.com/app/answers/detail/a_id/4614\nhttps://www.nvidia.com/en-us/product-security/>\n\n### __ NetBSD \n\nUpdated: January 08, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### __ OpenBSD \n\nUpdated: January 08, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n[https://marc.info/?l=openbsd-tech&m=151521435721902&w=2](<https://marc.info/?l=openbsd-tech&m=151521435721902&w=2>)\n\n### __ Oracle Corporation \n\nUpdated: February 23, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://www.theregister.co.uk/2018/01/16/oracle_quarterly_patches_jan_2018/>\n\n### __ QUALCOMM Incorporated \n\nUpdated: January 11, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Addendum\n\nThe Register has published the following: <https://www.theregister.co.uk/2018/01/06/qualcomm_processor_security_vulnerabilities/>\n\nIf you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:cert@cert.org?Subject=VU%23584653 Feedback>).\n\n### __ Red Hat, Inc. \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n[https://access.redhat.com/security/security-updates/#/security-advisories?q=&p=1&sort=portal_publication_date%20desc&rows=10&documentKind=PortalProduct](<https://access.redhat.com/security/security-updates/#/security-advisories?q=&p=1&sort=portal_publication_date%20desc&rows=10&documentKind=PortalProduct>)\n\n### __ SUSE Linux \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://www.suse.com/c/suse-addresses-meltdown-spectre-vulnerabilities/\nhttp://lists.suse.com/pipermail/sle-security-updates/2018-January/date.html>\n\n### __ Synology \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://www.synology.com/en-global/support/security/Synology_SA_18_01>\n\n### __ Trend Micro \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://success.trendmicro.com/solution/1119183-important-information-for-trend-micro-solutions-and-microsoft-january-2018-security-updates>\n\n### __ Ubuntu \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/SpectreAndMeltdown>\n\n### __ VMware \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://www.vmware.com/security/advisories/VMSA-2018-0002.html>\n\n### __ Xen \n\nUpdated: January 24, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<http://xenbits.xen.org/xsa/advisory-254.html\nhttps://blog.xenproject.org/2018/01/22/xen-project-spectre-meltdown-faq-jan-22-update/>\n\n### __ openSUSE project \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://lists.opensuse.org/opensuse-security-announce/2018-01/msg00001.html>\n\n### __ NetApp \n\nUpdated: January 08, 2018 \n\n### Status\n\n__ Not Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n[security.netapp.com/advisory/ntap-20180104-0001/](<security.netapp.com/advisory/ntap-20180104-0001/>)\n\n### __ Raspberry Pi \n\nUpdated: January 08, 2018 \n\n### Status\n\n__ Not Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://www.raspberrypi.org/blog/why-raspberry-pi-isnt-vulnerable-to-spectre-or-meltdown/>\n\n### __ __ Technicolor \n\nUpdated: January 08, 2018 \n\n### Status\n\n__ Not Affected\n\n### Vendor Statement\n\nBoth Spectre and Meltdown attacks presupposed \u201copen platforms\u201d, where \nadditional code can be added by a non-privileged user. The Technicolor products \nare not open platforms. Even where 3rd party application can run in containers \nand can be managed via Life Cycle Management, these applications are validated \nand signed before they can be installed on the platform. Technicolor is \ncurrently working with its vendors to identify if additional layers of \nprotection are needed. Yet, as the current platforms are closed and have secure \nbootloading mechanism in place, there is no risk and no privilege acquired by \nan attacker in exploiting such an attack on Technicolor's devices.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### __ ASUSTeK Computer Inc. \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Unknown\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### __ Acer \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Unknown\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### __ F5 Networks, Inc. \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Unknown\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://support.f5.com/csp/article/K91229003>\n\n### __ GIGABYTE \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Unknown\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### __ HP Inc. \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Unknown\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### __ Samsung Semiconductor Inc. \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Unknown\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### __ Toshiba Corporation \n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Unknown\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\nView all 46 vendors __View less vendors __\n\n \n\n\n### CVSS Metrics \n\nGroup | Score | Vector \n---|---|--- \nBase | 4.4 | AV:L/AC:M/Au:S/C:C/I:N/A:N \nTemporal | 3.4 | E:POC/RL:OF/RC:C \nEnvironmental | 5.1 | CDP:ND/TD:H/CR:H/IR:ND/AR:ND \n \n \n\n\n### References \n\n * <https://vuls.cert.org/confluence/display/Wiki/Vulnerabilities+Associated+with+CPU+Speculative+Execution>\n * <https://meltdownattack.com/>\n * <https://meltdownattack.com/meltdown.pdf>\n * <https://spectreattack.com/>\n * <https://spectreattack.com/spectre.pdf>\n * <https://security.googleblog.com/2018/01/todays-cpu-vulnerability-what-you-need.html>\n * <https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html>\n * <https://cyber.wtf/2017/07/28/negative-result-reading-kernel-memory-from-user-mode/>\n * <https://github.com/IAIK/KAISER>\n * <https://gruss.cc/files/kaiser.pdf>\n * <https://gruss.cc/files/prefetch.pdf>\n * <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5aa90a84589282b87666f92b6c3c917c8080a9bf>\n * <https://lkml.org/lkml/2017/12/27/2>\n * <https://lkml.org/lkml/2018/1/4/615>\n * <https://lwn.net/Articles/741878/>\n * <https://lwn.net/Articles/737940/>\n * <https://lwn.net/Articles/742702/>\n * <http://pythonsweetness.tumblr.com/post/169166980422/the-mysterious-case-of-the-linux-page-table>\n * <https://nakedsecurity.sophos.com/2018/01/03/fckwit-aka-kaiser-aka-kpti-intel-cpu-flaw-needs-low-level-os-patches/>\n * <https://en.wikipedia.org/wiki/Kernel_page-table_isolation>\n * <https://chrisam.net/2018/01/04/speculative-execution-side-channel-vulnerabilities-vendor-published-info/>\n * <https://www.raspberrypi.org/blog/why-raspberry-pi-isnt-vulnerable-to-spectre-or-meltdown/>\n * <https://doublepulsar.com/important-information-about-microsoft-meltdown-cpu-security-fixes-antivirus-vendors-and-you-a852ba0292ec>\n * [https://docs.google.com/spreadsheets/d/184wcDt9I9TUNFFbsAVLpzAtckQxYiuirADzf3cL42FQ/htmlview?usp=sharing&sle=true](<https://docs.google.com/spreadsheets/d/184wcDt9I9TUNFFbsAVLpzAtckQxYiuirADzf3cL42FQ/htmlview?usp=sharing&sle=true>)\n * <https://github.com/iadgov/Spectre-and-Meltdown-Guidance>\n * <https://arxiv.org/abs/1802.03802>\n\n### Credit\n\nThese issues were researched and reported by researchers at Google Project Zero (Jann Horn) the Institute of Applied Information Processing and Communications (IAIK) at Graz University of Technology (Gruss et. al.), Paul Kocher, and Anders Fogh. \n\nThis document was written by Art Manion and Will Dormann. \n\n### Other Information\n\n**CVE IDs:** | [CVE-2017-5753, ](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5753>) [CVE-2017-5715, ](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5715>) [CVE-2017-5754](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5754>) \n---|--- \n**Date Public:** | 2018-01-03 \n**Date First Published:** | 2018-01-04 \n**Date Last Updated: ** | 2018-07-03 21:27 UTC \n**Document Revision: ** | 230 \n", "published": "2018-01-04T00:00:00", "modified": "2018-07-03T21:27:00", "cvss": {"score": 4.7, "vector": "AV:LOCAL/AC:MEDIUM/Au:NONE/C:COMPLETE/I:NONE/A:NONE/"}, "href": "https://www.kb.cert.org/vuls/id/584653", "reporter": "CERT", "references": ["https://vuls.cert.org/confluence/display/Wiki/Vulnerabilities+Associated+with+CPU+Speculative+Execution", "https://meltdownattack.com/", "https://meltdownattack.com/meltdown.pdf", "https://spectreattack.com/", "https://spectreattack.com/spectre.pdf", "https://security.googleblog.com/2018/01/todays-cpu-vulnerability-what-you-need.html", "https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html", "https://cyber.wtf/2017/07/28/negative-result-reading-kernel-memory-from-user-mode/", "https://github.com/IAIK/KAISER", "https://gruss.cc/files/kaiser.pdf", "https://gruss.cc/files/prefetch.pdf", "https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5aa90a84589282b87666f92b6c3c917c8080a9bf", "https://lkml.org/lkml/2017/12/27/2", "https://lkml.org/lkml/2018/1/4/615", "https://lwn.net/Articles/741878/", "https://lwn.net/Articles/737940/", "https://lwn.net/Articles/742702/", "http://pythonsweetness.tumblr.com/post/169166980422/the-mysterious-case-of-the-linux-page-table", "https://nakedsecurity.sophos.com/2018/01/03/fckwit-aka-kaiser-aka-kpti-intel-cpu-flaw-needs-low-level-os-patches/", "https://en.wikipedia.org/wiki/Kernel_page-table_isolation", "https://chrisam.net/2018/01/04/speculative-execution-side-channel-vulnerabilities-vendor-published-info/", "https://www.raspberrypi.org/blog/why-raspberry-pi-isnt-vulnerable-to-spectre-or-meltdown/", "https://doublepulsar.com/important-information-about-microsoft-meltdown-cpu-security-fixes-antivirus-vendors-and-you-a852ba0292ec", "https://docs.google.com/spreadsheets/d/184wcDt9I9TUNFFbsAVLpzAtckQxYiuirADzf3cL42FQ/htmlview?usp=sharing&sle=true", "https://github.com/iadgov/Spectre-and-Meltdown-Guidance", "https://arxiv.org/abs/1802.03802"], "cvelist": ["CVE-2017-5715", "CVE-2017-5753", "CVE-2017-5754"], "lastseen": "2019-03-29T19:06:18", "history": [], "viewCount": 883, "enchantments": {"score": {"value": 7.2, "vector": "NONE"}, "dependencies": {"references": [{"type": "f5", "idList": ["F5:K91229003"]}, {"type": "symantec", "idList": ["SMNTC-102371", "SMNTC-102378"]}, {"type": "cve", "idList": ["CVE-2017-5753", "CVE-2017-5754", "CVE-2017-5715"]}, {"type": "openvas", "idList": ["OPENVAS:1361412562310843429", "OPENVAS:1361412562310812397", "OPENVAS:1361412562310843423", "OPENVAS:1361412562310882822", "OPENVAS:1361412562310843473", "OPENVAS:1361412562310812296", "OPENVAS:1361412562310812295", "OPENVAS:1361412562310843427"]}, {"type": "suse", "idList": ["SUSE-SU-2018:0171-1", "SUSE-SU-2018:0069-1", "SUSE-SU-2018:0131-1"]}, {"type": "redhat", "idList": ["RHSA-2018:0010", "RHSA-2018:0047", "RHSA-2018:0045", "RHSA-2018:0496", "RHSA-2018:0022", "RHSA-2018:0090", "RHSA-2018:0008", "RHSA-2018:0092", "RHSA-2018:0091", "RHSA-2018:0046"]}, {"type": "nessus", "idList": ["AIX_IJ03030.NASL", "XEN_SERVER_XSA-254.NASL", "EULEROS_SA-2018-1002.NASL", "REDHAT-RHSA-2018-0016.NASL", "SL_20180313_KERNEL_ON_SL6_X.NASL", "SUSE_SU-2018-0069-1.NASL", "REDHAT-RHSA-2018-0017.NASL", "UBUNTU_USN-3516-1.NASL", "REDHAT-RHSA-2018-0018.NASL", "REDHAT-RHSA-2018-0011.NASL"]}, {"type": "securelist", "idList": ["SECURELIST:7CF4DDEB1B5407DAA24EC25BAA7A9654"]}, {"type": "centos", "idList": ["CESA-2018:0008"]}, {"type": "ubuntu", "idList": ["USN-3597-2", "USN-3541-1", "USN-3540-1", "USN-3597-1"]}, {"type": "qualysblog", "idList": ["QUALYSBLOG:F8AA5B21D90BCDD30391A24D6FD47892", "QUALYSBLOG:BD020D07BF02B0790C62701D997BFD4D", "QUALYSBLOG:C9F2432F760D960CF69CDC55D87263A8", "QUALYSBLOG:F7C32BA5E6651A8CE3584BB84A88A0C0", "QUALYSBLOG:3ACE52E54FF5FE3EF1B0FC328181FA66"]}, {"type": "cloudfoundry", "idList": ["CFOUNDRY:86B5C35F8F0E334D1CCCDAF1214EDFEF"]}, {"type": "lenovo", "idList": ["LENOVO:PS500151-NOSID"]}, {"type": "threatpost", "idList": ["THREATPOST:0F9EDE9A622A021B9B79C50214D7E8AD", "THREATPOST:DB0542CFA474B0D9C91032709EDE296D"]}, {"type": "seebug", "idList": ["SSV:97059"]}, {"type": "vmware", "idList": ["VMSA-2018-0007"]}, {"type": "thn", "idList": ["THN:58CFE19533148E77597FE0AC59963145"]}, {"type": "oraclelinux", "idList": ["ELSA-2018-4012"]}], "modified": "2019-03-29T19:06:18"}}, "objectVersion": "1.4"}, "lastseen": "2019-03-29T19:06:18", "differentElements": ["description"], "edition": 23}, {"bulletin": {"id": "VU:584653", "hash": "c34b4355f77b23f8f95920a3fb65fc62", "type": "cert", "bulletinFamily": "info", "title": "CPU hardware vulnerable to side-channel attacks", "description": "### Overview \n\nCPU hardware implementations are vulnerable to cache side-channel attacks. These vulnerabilities are referred to as [Meltdown](<https://meltdownattack.com/>) and [Spectre](<https://spectreattack.com/>).\n\n### Description \n\nCPU hardware implementations are vulnerable to side-channel attacks referred to as [Meltdown](<https://meltdownattack.com/>) and [Spectre](<https://spectreattack.com/>). Both Spectre and Meltdown take advantage of the ability to extract information from instructions that have executed on a CPU using the CPU cache as a side-channel. These attacks are described in detail by [Google Project Zero](<https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html>), the Institute of Applied Information Processing and Communications (IAIK) at Graz University of Technology (TU Graz) and Anders Fogh. The issues are organized into three variants:\n\n * Variant 1 (CVE-2017-5753, [Spectre](<https://spectreattack.com/spectre.pdf>)): Bounds check bypass\n * Variant 2 (CVE-2017-5715, also [Spectre](<https://spectreattack.com/spectre.pdf>)): Branch target injection[](<https://spectreattack.com/spectre.pdf>)\n * Variant 3 (CVE-2017-5754, [Meltdown](<https://meltdownattack.com/meltdown.pdf>)): Rogue data cache load, memory access permission check performed after kernel memory read\n \n**Spectre** \n \nSpectre attacks take advantage of a CPU's branch prediction capabilities. Modern CPUs include a feature called branch prediction, which speculatively executes instructions at a location that the CPU believes it will branch to. Such speculative execution helps to more fully utilize the parts of the CPU, minimizing the time waiting, and therefore improving performance. When a branch is successfully predicted, instructions will retire, which means the outcomes of the instructions such as register and memory writes will be committed. If a branch is mispredicted, the speculatively-executed instructions will be discarded, and the direct side-effects of the instructions are undone. What is not undone are the indirect side-effects, such as CPU cache changes. By measuring latency of memory access operations, the cache can be used to extract values from speculatively-executed instructions. \n \nWith Spectre variant 1 (CVE-2017-5753), the instructions after a conditional branch are speculatively executed as the result of a misprediction. With Spectre variant 2 (CVE-2017-5715), the CPU executes instructions at a location determined by a mispredicted branch target. \n \nWith both variants of the Spectre attack, the impact is that a process may leak sensitive data to other processes on a system. Spectre may also allow one part of an application to access other parts of the same process memory space that would otherwise not be permitted. \n \nWhile the Spectre attack itself does not cross a user/kernel memory privilege boundary, depending on the configuration of the target platform, the Spectre attack may indirectly allow a user-space application to access kernel memory. For example, the[ Project Zero blog post](<https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html>) describes a scenario that uses eBPF to exfiltrate kernel memory contents into user-space code. This is made possible because eBPF JIT allows for userspace applications to inject code that is executed in kernel space. While this code is verified by the kernel, eBPF-compliant code will be allowed to execute with kernel permissions. The exploit described by Project Zero leverages eBPF to execute the Spectre attack in kernel space, while exfiltrating the data to user space. It is possible that other technologies that allow in-kernel code execution may also possibly be leveraged to leak kernel memory using Spectre. \n \n**Meltdown** \n \nMeltdown is related to the Spectre attack in that it also uses a cache side channel to access data that otherwise wouldn't be available. The main difference is that it leverages out-of-order execution capabilities in modern CPUs. Like speculative execution due to branch prediction, as used by Spectre, out-of-order execution on a CPU is a technique for ensuring fullest utilization of the CPU's parts. Although instructions may appear sequentially in the machine language, a CPU that supports out-of-order execution may execute instructions in a non-sequential manner, which can minimize the time that a CPU spends idle. \n \nMeltdown leverages insecure behavior that has been demonstrated in Intel CPUs and may affect CPUs from other vendors. Vulnerable CPUs allow memory reads in out-of-order instruction execution, and also contain a race condition between the raising of exceptions and the out-of-order instruction execution. The Meltdown attack reads a kernel memory value, which raises an exception because code running with user-space privileges are not permitted to directly read kernel memory. However, due to the race condition, out-of-order instructions following the faulting instruction may also execute. Even though instructions appear after the faulting instruction, out-of-order execution allows them to execute, using data retrieved from the instruction that raises the exception. By the time the exception is raised, some number of out-of-order instructions have executed. Although the raised exception causes the CPU to roll back the out-of-order instructions, the cache state is not reverted. This allows data from out-of-order instructions to persist beyond the point when the exception has been raised. \n \nThe impact of Meltdown is that a process running in user space is able to view the contents of kernel memory. Meltdown may also allow Spectre-like memory content leaking that does not cross the user/kernel privilege boundary. \n \nThe Linux kernel mitigations for Meltdown are referred to as KAISER, and subsequently KPTI, which aim to improve separation of kernel and user memory pages. Because the Spectre attacks do not cross user/kernel boundaries, the protections introduced with KAISER/KPTI do not add any protection against them. \n \nThe following table compares Spectre and Meltdown. \n \n| | **Spectre**| **Meltdown** \n---|---|--- \n**CPU mechanism for triggering**| Speculative execution from branch prediction| Out-of-order execution \n**Affected platforms**| CPUs that perform speculative execution from branch prediction| CPUs that allow memory reads in out-of-order instructions \n**Difficulty of successful attack**| High - Requires tailoring to the software environment of the victim process| Low - Kernel memory access exploit code is mostly universal \n**Impact**| Cross- and intra-process (including kernel) memory disclosure| Kernel memory disclosure to userspace \n**Software mitigations**| Variant 1: Compiler changes. Web browser updates to help prevent exploitation from JavaScript \nVariant 2: Indirect Branch Restricted Speculation ([IBRS](<https://lkml.org/lkml/2018/1/4/615>)). \n**Note: **The software mitigation for Spectre variant 2 requires CPU microcode updates| Kernel page-table isolation ([KPTI](<https://en.wikipedia.org/wiki/Kernel_page-table_isolation>)) \n \n### Impact \n\nAn attacker able to execute code with user privileges can achieve various impacts. The Meltdown attack allows reading of kernel memory from userspace. This can result in privilege escalation, disclosure of sensitive information, or it can weaken kernel-level protections, such as KASLR. The Spectre attack can allow inter-process or intra-process data leaks. \n \nTo execute code locally, an attacker would require a valid account or independent compromise of the target. Attacks using JavaScript in web browsers are possible. Multi-user and multi-tenant systems (including virtualized and cloud environments) likely face the greatest risk. Systems used to browse arbitrary web sites are also at risk. Single-user systems that do not readily provide a way for attackers to execute code locally face significantly lower risk. \n \n--- \n \n### Solution \n\n**Apply updates** \n \nOperating system, CPU microcode updates, and some application updates mitigate these attacks. Note that in many cases, the software fixes for these vulnerabilities will have a negative affect on system performance. Also note that Microsoft Windows systems [will no longer receive security updates](<https://doublepulsar.com/important-information-about-microsoft-meltdown-cpu-security-fixes-antivirus-vendors-and-you-a852ba0292ec>) via Windows Update if they are not running compliant anti-virus software. As with deploying any software updates, be sure to prioritize and test updates as necessary. \n \n**Consider CPU Options** \n \nInitial reports from the field indicate that overall system performance is impacted by many of the available patches for these vulnerabilities. Depending on the software workflow and the CPU capabilities present, the performance impact of software mitigations may be non-trivial and therefore may become an ongoing operational concern for some organizations. While we recognize that replacing existing CPUs in already deployed systems is not practical, organizations acquiring new systems should evaluate their CPU selection in light of the expected longevity of this vulnerability in available hardware as well as the performance impacts resulting from the various platform-specific software patches. Deployment contexts and performance requirements vary widely, and must be balanced by informed evaluation of the associated security risks. Contact your system vendor to determine if the CPU and operating system combination will experience a performance penalty due to software mitigations for these vulnerabilities. \n \n--- \n \n### Vendor Information\n\n584653\n\nFilter by status: All Affected Not Affected Unknown\n\nFilter by content: __ Vendor has issued information\n\n__ Sort by: Status Alphabetical\n\nExpand all\n\n__ Affected __ Unknown __ Unaffected \n\n**Javascript is disabled. Click here to view vendors.**\n\n### __ AMD\n\nUpdated: January 03, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://www.amd.com/en/corporate/speculative-execution>\n\n### __ Amazon\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://aws.amazon.com/security/security-bulletins/AWS-2018-013/>\n\n### __ Android Open Source Project\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://source.android.com/security/bulletin/2018-01-01>\n\n### __ Apple\n\nUpdated: February 02, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://support.apple.com/en-us/HT208394\nhttps://support.apple.com/en-us/HT208397\nhttps://support.apple.com/en-us/HT208403\nhttps://support.apple.com/en-us/HT208401\nhttps://support.apple.com/en-ca/HT208465>\n\n### Addendum\n\n<https://twitter.com/aionescu/status/948609809540046849> \n<https://twitter.com/ErrataRob/status/949088097475743744>\n\nIf you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:cert@cert.org?Subject=VU%23584653 Feedback>).\n\n### __ Arm\n\nUpdated: January 03, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://developer.arm.com/support/security-update\nhttps://developer.arm.com/-/media/Files/pdf/Cache_Speculation_Side-channels.pdf>\n\n### Addendum\n\n<https://lwn.net/Articles/740393/>\n\nIf you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:cert@cert.org?Subject=VU%23584653 Feedback>).\n\n### __ CentOS\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://lists.centos.org/pipermail/centos-announce/2018-January/date.html>\n\n### __ Cisco\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20180104-cpusidechannel>\n\n### __ Citrix\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://support.citrix.com/article/CTX231399>\n\n### __ Debian GNU/Linux\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://security-tracker.debian.org/tracker/CVE-2017-5754>\n\n### __ Dell\n\nUpdated: January 08, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<http://www.dell.com/support/contents/us/en/19/article/product-support/self-support-knowledgebase/software-and-downloads/support-for-meltdown-and-spectre>\n\n### __ DragonFly BSD Project\n\nUpdated: January 08, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<http://lists.dragonflybsd.org/pipermail/users/2018-January/313758.html>\n\n### __ Fedora Project\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://fedoramagazine.org/protect-fedora-system-meltdown/>\n\n### __ Fortinet, Inc.\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://fortiguard.com/psirt/FG-IR-18-002>\n\n### __ FreeBSD Project\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://www.freebsd.org/news/newsflash.html#event20180104:01>\n\n### __ Fujitsu\n\nUpdated: January 11, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<http://support.ts.fujitsu.com/content/SideChannelAnalysisMethod.asp?lng=EN>\n\n### __ Google\n\nUpdated: January 03, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://security.googleblog.com/2018/01/todays-cpu-vulnerability-what-you-need.html\nhttps://support.google.com/faqs/answer/7622138>\n\n### __ Hewlett Packard Enterprise\n\nUpdated: January 08, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://www.hpe.com/us/en/services/security-vulnerability.html>\n\n### __ IBM Corporation\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://www.ibm.com/blogs/psirt/potential-cpu-security-issue/>\n\n### __ Intel\n\nUpdated: January 22, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://newsroom.intel.com/news/intel-responds-to-security-research-findings/\nhttps://newsroom.intel.com/news-releases/intel-issues-updates-protect-systems-security-exploits\nhttps://www.intel.com/content/www/us/en/architecture-and-technology/facts-about-side-channel-analysis-and-intel-products.html\nhttps://newsroom.intel.com/news/root-cause-of-reboot-issue-identified-updated-guidance-for-customers-and-partners/\nhttps://newsroom.intel.com/wp-content/uploads/sites/11/2018/01/microcode-update-guidance.pdf>\n\n### __ Lenovo\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://support.lenovo.com/us/en/solutions/len-18282>\n\n### __ Linux Kernel\n\nUpdated: January 04, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://lkml.org/lkml/2017/11/22/956\nhttps://lkml.org/lkml/2018/1/4/174\nhttps://lkml.org/lkml/2018/1/4/615>\n\n### __ Microsoft\n\nUpdated: January 11, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://support.microsoft.com/en-us/help/4073119/protect-against-speculative-execution-side-channel-vulnerabilities-in\nhttps://support.microsoft.com/en-us/help/4072699/january-3-2018-windows-security-updates-and-antivirus-software\nhttps://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/CVE-2017-5715-and-hyper-v-vms\nhttps://portal.msrc.microsoft.com/en-US/security-guidance/advisory/ADV180002\nhttps://blogs.windows.com/msedgedev/2018/01/03/speculative-execution-mitigations-microsoft-edge-internet-explorer/\nhttps://azure.microsoft.com/en-us/blog/securing-azure-customers-from-cpu-vulnerability/\nhttps://cloudblogs.microsoft.com/microsoftsecure/2018/01/09/understanding-the-performance-impact-of-spectre-and-meltdown-mitigations-on-windows-systems/\nhttps://support.microsoft.com/en-us/help/4073707/windows-os-security-update-block-for-some-amd-based-devices>\n\n### Addendum\n\nNote that Windows systems without antivirus do not appear to receive the ADV180002 update automatically. In order to receive the update through Windows Update, run the following command:\n\n \n`reg add \"HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\QualityCompat\" /v cadca5fe-87d3-4b96-b7fb-a231484277cc /t REG_DWORD /d 0 /f` \nIf a third-party antivirus product does not explicitly indicate compatibility with to the protections provided by ADV180002 using the above registry value, the system will not automatically receive the ADV180002 update as well. \n \nOnce a system has the ADV180002 update installed, it must be manually activated using the following commands to make the appropriate registry changes: \n\n\n`reg add \"HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Control\\Session Manager\\Memory Management\" /v FeatureSettingsOverride /t REG_DWORD /d 0 /f` \n`reg add \"HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Control\\Session Manager\\Memory Management\" /v FeatureSettingsOverrideMask /t REG_DWORD /d 3 /f` \n`reg add \"HKLM\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Virtualization\" /v MinVmVersionForCpuBasedMitigations /t REG_SZ /d \"1.0\" /f ` \nAlso note that in addition to the above changes, ADV180002 requires CPU microcode updates to achieve full protection. In some cases, Windows Update may not automatically install the ADV180002 update. An unofficial spreadsheet of antivirus vendor compatibility with this update is maintained here: \n \nOn systems that have not received the ADV180002 update automatically, you may have to install the update manually. Please see for more details. \n \nTo verify that your Windows system has protections against Meltdown and Spectre variant 2, in a PowerShell session running with Administrator privileges, run:\n\n 1. `Install-Module SpeculationControl` \nIf this fails, you may need to install [PackageManagement PowerShell Modules](<https://www.microsoft.com/en-us/download/details.aspx?id=51451>)\n 2. `Get-SpeculationControlSettings` \nIf this fails, you may need to change your PowerShell ExecutionPolicy setting: ` \nSet-ExecutionPolicy RemoteSigned \n`Once you are satisfied with the PowerShell output, you can revert the ExecutionPolicy setting back to the default Restricted setting by running: \n`Set-ExecutionPolicy Restricted`\n` ` \nThe output of this PowerShell command will indicate the status of whether the CPU has the required microcode update, whether Windows has the required software update installed, and whether the mitigations are enabled. Any setting that indicates \"False\" is an indicator of incomplete protection from Meltdown and/or Spectre. \n \nFor example, a system that has the ADV180002 update properly installed and enabled, but is missing the CPU microcode update to fully enable the protections will show output like this: \n \n \nOnce the CPU microcode is updated on such a system (e.g. by way of a BIOS update) , the output will look like this, which indicates that the protections that Microsoft have released are fully enabled: \n \n \nIf the above PowerShell command indicates \"Windows OS support for PCID optimization is enabled: False\", this is a symptom of using a processor that doesn't support process context identifiers (PCID). Such processors cannot take advantage of the performance optimization that avoids a TLB flush. \n \nIf the above PowerShell command indicates \"Hardware requires kernel VA shadowing: False\", this is a symptom of using a processor that doesn't require mitigations for CVE-2017-5754 (Meltdown). \n \nAlso note that Microsoft has not yet provided protection for CVE-2017-5754 (Meltdown) on affected 32-bit platforms. \n\nIf you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:cert@cert.org?Subject=VU%23584653 Feedback>).\n\n### __ Mozilla\n\nUpdated: January 03, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://blog.mozilla.org/security/2018/01/03/mitigations-landing-new-class-timing-attack/>\n\n### __ NVIDIA\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<http://nvidia.custhelp.com/app/answers/detail/a_id/4609\nhttp://nvidia.custhelp.com/app/answers/detail/a_id/4611\nhttp://nvidia.custhelp.com/app/answers/detail/a_id/4613\nhttp://nvidia.custhelp.com/app/answers/detail/a_id/4614\nhttps://www.nvidia.com/en-us/product-security/>\n\n### __ NetBSD\n\nUpdated: January 08, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### __ OpenBSD\n\nUpdated: January 08, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n[https://marc.info/?l=openbsd-tech&m=151521435721902&w=2](<https://marc.info/?l=openbsd-tech&m=151521435721902&w=2>)\n\n### __ Oracle Corporation\n\nUpdated: February 23, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://www.theregister.co.uk/2018/01/16/oracle_quarterly_patches_jan_2018/>\n\n### __ QUALCOMM Incorporated\n\nUpdated: January 11, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Addendum\n\nThe Register has published the following: <https://www.theregister.co.uk/2018/01/06/qualcomm_processor_security_vulnerabilities/>\n\nIf you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:cert@cert.org?Subject=VU%23584653 Feedback>).\n\n### __ Red Hat, Inc.\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n[https://access.redhat.com/security/security-updates/#/security-advisories?q=&p=1&sort=portal_publication_date%20desc&rows=10&documentKind=PortalProduct](<https://access.redhat.com/security/security-updates/#/security-advisories?q=&p=1&sort=portal_publication_date%20desc&rows=10&documentKind=PortalProduct>)\n\n### __ SUSE Linux\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://www.suse.com/c/suse-addresses-meltdown-spectre-vulnerabilities/\nhttp://lists.suse.com/pipermail/sle-security-updates/2018-January/date.html>\n\n### __ Synology\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://www.synology.com/en-global/support/security/Synology_SA_18_01>\n\n### __ Trend Micro\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://success.trendmicro.com/solution/1119183-important-information-for-trend-micro-solutions-and-microsoft-january-2018-security-updates>\n\n### __ Ubuntu\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/SpectreAndMeltdown>\n\n### __ VMware\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://www.vmware.com/security/advisories/VMSA-2018-0002.html>\n\n### __ Xen\n\nUpdated: January 24, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<http://xenbits.xen.org/xsa/advisory-254.html\nhttps://blog.xenproject.org/2018/01/22/xen-project-spectre-meltdown-faq-jan-22-update/>\n\n### __ openSUSE project\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://lists.opensuse.org/opensuse-security-announce/2018-01/msg00001.html>\n\n### __ NetApp\n\nUpdated: January 08, 2018 \n\n### Status\n\n__ Not Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n[security.netapp.com/advisory/ntap-20180104-0001/](<security.netapp.com/advisory/ntap-20180104-0001/>)\n\n### __ Raspberry Pi\n\nUpdated: January 08, 2018 \n\n### Status\n\n__ Not Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://www.raspberrypi.org/blog/why-raspberry-pi-isnt-vulnerable-to-spectre-or-meltdown/>\n\n### __ __ Technicolor\n\nUpdated: January 08, 2018 \n\n### Status\n\n__ Not Affected\n\n### Vendor Statement\n\nBoth Spectre and Meltdown attacks presupposed \u201copen platforms\u201d, where \nadditional code can be added by a non-privileged user. The Technicolor products \nare not open platforms. Even where 3rd party application can run in containers \nand can be managed via Life Cycle Management, these applications are validated \nand signed before they can be installed on the platform. Technicolor is \ncurrently working with its vendors to identify if additional layers of \nprotection are needed. Yet, as the current platforms are closed and have secure \nbootloading mechanism in place, there is no risk and no privilege acquired by \nan attacker in exploiting such an attack on Technicolor's devices.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### __ ASUSTeK Computer Inc.\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Unknown\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### __ Acer\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Unknown\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### __ F5 Networks, Inc.\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Unknown\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://support.f5.com/csp/article/K91229003>\n\n### __ GIGABYTE\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Unknown\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### __ HP Inc.\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Unknown\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### __ Samsung Semiconductor Inc.\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Unknown\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### __ Toshiba Corporation\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Unknown\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\nView all 46 vendors __View less vendors __\n\n \n\n\n### CVSS Metrics \n\nGroup | Score | Vector \n---|---|--- \nBase | 4.4 | AV:L/AC:M/Au:S/C:C/I:N/A:N \nTemporal | 3.4 | E:POC/RL:OF/RC:C \nEnvironmental | 5.1 | CDP:ND/TD:H/CR:H/IR:ND/AR:ND \n \n \n\n\n### References \n\n * <https://vuls.cert.org/confluence/display/Wiki/Vulnerabilities+Associated+with+CPU+Speculative+Execution>\n * <https://meltdownattack.com/>\n * <https://meltdownattack.com/meltdown.pdf>\n * <https://spectreattack.com/>\n * <https://spectreattack.com/spectre.pdf>\n * <https://security.googleblog.com/2018/01/todays-cpu-vulnerability-what-you-need.html>\n * <https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html>\n * <https://cyber.wtf/2017/07/28/negative-result-reading-kernel-memory-from-user-mode/>\n * <https://github.com/IAIK/KAISER>\n * <https://gruss.cc/files/kaiser.pdf>\n * <https://gruss.cc/files/prefetch.pdf>\n * <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5aa90a84589282b87666f92b6c3c917c8080a9bf>\n * <https://lkml.org/lkml/2017/12/27/2>\n * <https://lkml.org/lkml/2018/1/4/615>\n * <https://lwn.net/Articles/741878/>\n * <https://lwn.net/Articles/737940/>\n * <https://lwn.net/Articles/742702/>\n * <http://pythonsweetness.tumblr.com/post/169166980422/the-mysterious-case-of-the-linux-page-table>\n * <https://nakedsecurity.sophos.com/2018/01/03/fckwit-aka-kaiser-aka-kpti-intel-cpu-flaw-needs-low-level-os-patches/>\n * <https://en.wikipedia.org/wiki/Kernel_page-table_isolation>\n * <https://chrisam.net/2018/01/04/speculative-execution-side-channel-vulnerabilities-vendor-published-info/>\n * <https://www.raspberrypi.org/blog/why-raspberry-pi-isnt-vulnerable-to-spectre-or-meltdown/>\n * <https://doublepulsar.com/important-information-about-microsoft-meltdown-cpu-security-fixes-antivirus-vendors-and-you-a852ba0292ec>\n * [https://docs.google.com/spreadsheets/d/184wcDt9I9TUNFFbsAVLpzAtckQxYiuirADzf3cL42FQ/htmlview?usp=sharing&sle=true](<https://docs.google.com/spreadsheets/d/184wcDt9I9TUNFFbsAVLpzAtckQxYiuirADzf3cL42FQ/htmlview?usp=sharing&sle=true>)\n * <https://github.com/iadgov/Spectre-and-Meltdown-Guidance>\n * <https://arxiv.org/abs/1802.03802>\n\n### Credit\n\nThese issues were researched and reported by researchers at Google Project Zero (Jann Horn) the Institute of Applied Information Processing and Communications (IAIK) at Graz University of Technology (Gruss et. al.), Paul Kocher, and Anders Fogh. \n\nThis document was written by Art Manion and Will Dormann. \n\n### Other Information\n\n**CVE IDs:** | [CVE-2017-5753, ](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5753>) [CVE-2017-5715, ](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5715>) [CVE-2017-5754](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5754>) \n---|--- \n**Date Public:** | 2018-01-03 \n**Date First Published:** | 2018-01-04 \n**Date Last Updated: ** | 2018-07-03 21:27 UTC \n**Document Revision: ** | 230 \n", "published": "2018-01-04T00:00:00", "modified": "2018-07-03T21:27:00", "cvss": {"score": 4.7, "vector": "AV:LOCAL/AC:MEDIUM/Au:NONE/C:COMPLETE/I:NONE/A:NONE/"}, "href": "https://www.kb.cert.org/vuls/id/584653", "reporter": "CERT", "references": ["https://vuls.cert.org/confluence/display/Wiki/Vulnerabilities+Associated+with+CPU+Speculative+Execution", "https://meltdownattack.com/", "https://meltdownattack.com/meltdown.pdf", "https://spectreattack.com/", "https://spectreattack.com/spectre.pdf", "https://security.googleblog.com/2018/01/todays-cpu-vulnerability-what-you-need.html", "https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html", "https://cyber.wtf/2017/07/28/negative-result-reading-kernel-memory-from-user-mode/", "https://github.com/IAIK/KAISER", "https://gruss.cc/files/kaiser.pdf", "https://gruss.cc/files/prefetch.pdf", "https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5aa90a84589282b87666f92b6c3c917c8080a9bf", "https://lkml.org/lkml/2017/12/27/2", "https://lkml.org/lkml/2018/1/4/615", "https://lwn.net/Articles/741878/", "https://lwn.net/Articles/737940/", "https://lwn.net/Articles/742702/", "http://pythonsweetness.tumblr.com/post/169166980422/the-mysterious-case-of-the-linux-page-table", "https://nakedsecurity.sophos.com/2018/01/03/fckwit-aka-kaiser-aka-kpti-intel-cpu-flaw-needs-low-level-os-patches/", "https://en.wikipedia.org/wiki/Kernel_page-table_isolation", "https://chrisam.net/2018/01/04/speculative-execution-side-channel-vulnerabilities-vendor-published-info/", "https://www.raspberrypi.org/blog/why-raspberry-pi-isnt-vulnerable-to-spectre-or-meltdown/", "https://doublepulsar.com/important-information-about-microsoft-meltdown-cpu-security-fixes-antivirus-vendors-and-you-a852ba0292ec", "https://docs.google.com/spreadsheets/d/184wcDt9I9TUNFFbsAVLpzAtckQxYiuirADzf3cL42FQ/htmlview?usp=sharing&sle=true", "https://github.com/iadgov/Spectre-and-Meltdown-Guidance", "https://arxiv.org/abs/1802.03802"], "cvelist": ["CVE-2017-5715", "CVE-2017-5753", "CVE-2017-5754"], "lastseen": "2019-04-24T19:50:12", "history": [], "viewCount": 885, "enchantments": {"score": {"value": 7.2, "vector": "NONE"}, "dependencies": {"references": [{"type": "f5", "idList": ["F5:K91229003"]}, {"type": "symantec", "idList": ["SMNTC-102371", "SMNTC-102378"]}, {"type": "cve", "idList": ["CVE-2017-5753", "CVE-2017-5754", "CVE-2017-5715"]}, {"type": "nessus", "idList": ["UBUNTU_USN-3516-1.NASL", "REDHAT-RHSA-2018-0018.NASL", "UBUNTU_USN-3597-1.NASL", "EULEROS_SA-2018-1002.NASL", "XEN_SERVER_XSA-254.NASL", "AIX_IJ03030.NASL", "SL_20180313_KERNEL_ON_SL6_X.NASL", "UBUNTU_USN-3541-2.NASL", "ORACLEVM_OVMSA-2018-0029.NASL", "ORACLELINUX_ELSA-2018-0008.NASL"]}, {"type": "openvas", "idList": ["OPENVAS:1361412562310882822", "OPENVAS:1361412562310843423", "OPENVAS:1361412562310812397", "OPENVAS:1361412562310843429", "OPENVAS:1361412562310812295", "OPENVAS:1361412562310843427", "OPENVAS:1361412562310812296", "OPENVAS:1361412562310843473"]}, {"type": "suse", "idList": ["SUSE-SU-2018:0171-1", "SUSE-SU-2018:0069-1", "SUSE-SU-2018:0131-1"]}, {"type": "qualysblog", "idList": ["QUALYSBLOG:F8AA5B21D90BCDD30391A24D6FD47892", "QUALYSBLOG:F7C32BA5E6651A8CE3584BB84A88A0C0", "QUALYSBLOG:C9F2432F760D960CF69CDC55D87263A8", "QUALYSBLOG:3ACE52E54FF5FE3EF1B0FC328181FA66", "QUALYSBLOG:BD020D07BF02B0790C62701D997BFD4D"]}, {"type": "redhat", "idList": ["RHSA-2018:0010", "RHSA-2018:0045", "RHSA-2018:0047", "RHSA-2018:0496", "RHSA-2018:0090", "RHSA-2018:0046", "RHSA-2018:0092", "RHSA-2018:0008", "RHSA-2018:0091", "RHSA-2018:0011"]}, {"type": "ubuntu", "idList": ["USN-3597-2", "USN-3597-1", "USN-3541-1", "USN-3540-1", "USN-3541-2"]}, {"type": "centos", "idList": ["CESA-2018:0008"]}, {"type": "securelist", "idList": ["SECURELIST:7CF4DDEB1B5407DAA24EC25BAA7A9654"]}, {"type": "oraclelinux", "idList": ["ELSA-2018-4012"]}, {"type": "seebug", "idList": ["SSV:97059"]}, {"type": "threatpost", "idList": ["THREATPOST:0F9EDE9A622A021B9B79C50214D7E8AD", "THREATPOST:DB0542CFA474B0D9C91032709EDE296D"]}, {"type": "vmware", "idList": ["VMSA-2018-0007"]}, {"type": "thn", "idList": ["THN:58CFE19533148E77597FE0AC59963145"]}, {"type": "lenovo", "idList": ["LENOVO:PS500151-NOSID"]}, {"type": "cloudfoundry", "idList": ["CFOUNDRY:86B5C35F8F0E334D1CCCDAF1214EDFEF"]}, {"type": "huawei", "idList": ["HUAWEI-SA-20180106-01-CPU"]}, {"type": "paloalto", "idList": ["PAN-SA-2018-0001"]}], "modified": "2019-04-24T19:50:12"}}, "objectVersion": "1.4"}, "lastseen": "2019-04-24T19:50:12", "differentElements": ["description"], "edition": 24}, {"bulletin": {"id": "VU:584653", "hash": "ea82fee30c0c6c5bbfa91b9b606fc41a", "type": "cert", "bulletinFamily": "info", "title": "CPU hardware vulnerable to side-channel attacks", "description": "### Overview \n\nCPU hardware implementations are vulnerable to cache side-channel attacks. These vulnerabilities are referred to as [Meltdown](<https://meltdownattack.com/>) and [Spectre](<https://spectreattack.com/>).\n\n### Description \n\nCPU hardware implementations are vulnerable to side-channel attacks referred to as [Meltdown](<https://meltdownattack.com/>) and [Spectre](<https://spectreattack.com/>). Both Spectre and Meltdown take advantage of the ability to extract information from instructions that have executed on a CPU using the CPU cache as a side-channel. These attacks are described in detail by [Google Project Zero](<https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html>), the Institute of Applied Information Processing and Communications (IAIK) at Graz University of Technology (TU Graz) and Anders Fogh. The issues are organized into three variants:\n\n * Variant 1 (CVE-2017-5753, [Spectre](<https://spectreattack.com/spectre.pdf>)): Bounds check bypass\n * Variant 2 (CVE-2017-5715, also [Spectre](<https://spectreattack.com/spectre.pdf>)): Branch target injection[](<https://spectreattack.com/spectre.pdf>)\n * Variant 3 (CVE-2017-5754, [Meltdown](<https://meltdownattack.com/meltdown.pdf>)): Rogue data cache load, memory access permission check performed after kernel memory read\n \n**Spectre** \n \nSpectre attacks take advantage of a CPU's branch prediction capabilities. Modern CPUs include a feature called branch prediction, which speculatively executes instructions at a location that the CPU believes it will branch to. Such speculative execution helps to more fully utilize the parts of the CPU, minimizing the time waiting, and therefore improving performance. When a branch is successfully predicted, instructions will retire, which means the outcomes of the instructions such as register and memory writes will be committed. If a branch is mispredicted, the speculatively-executed instructions will be discarded, and the direct side-effects of the instructions are undone. What is not undone are the indirect side-effects, such as CPU cache changes. By measuring latency of memory access operations, the cache can be used to extract values from speculatively-executed instructions. \n \nWith Spectre variant 1 (CVE-2017-5753), the instructions after a conditional branch are speculatively executed as the result of a misprediction. With Spectre variant 2 (CVE-2017-5715), the CPU executes instructions at a location determined by a mispredicted branch target. \n \nWith both variants of the Spectre attack, the impact is that a process may leak sensitive data to other processes on a system. Spectre may also allow one part of an application to access other parts of the same process memory space that would otherwise not be permitted. \n \nWhile the Spectre attack itself does not cross a user/kernel memory privilege boundary, depending on the configuration of the target platform, the Spectre attack may indirectly allow a user-space application to access kernel memory. For example, the[ Project Zero blog post](<https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html>) describes a scenario that uses eBPF to exfiltrate kernel memory contents into user-space code. This is made possible because eBPF JIT allows for userspace applications to inject code that is executed in kernel space. While this code is verified by the kernel, eBPF-compliant code will be allowed to execute with kernel permissions. The exploit described by Project Zero leverages eBPF to execute the Spectre attack in kernel space, while exfiltrating the data to user space. It is possible that other technologies that allow in-kernel code execution may also possibly be leveraged to leak kernel memory using Spectre. \n \n**Meltdown** \n \nMeltdown is related to the Spectre attack in that it also uses a cache side channel to access data that otherwise wouldn't be available. The main difference is that it leverages out-of-order execution capabilities in modern CPUs. Like speculative execution due to branch prediction, as used by Spectre, out-of-order execution on a CPU is a technique for ensuring fullest utilization of the CPU's parts. Although instructions may appear sequentially in the machine language, a CPU that supports out-of-order execution may execute instructions in a non-sequential manner, which can minimize the time that a CPU spends idle. \n \nMeltdown leverages insecure behavior that has been demonstrated in Intel CPUs and may affect CPUs from other vendors. Vulnerable CPUs allow memory reads in out-of-order instruction execution, and also contain a race condition between the raising of exceptions and the out-of-order instruction execution. The Meltdown attack reads a kernel memory value, which raises an exception because code running with user-space privileges are not permitted to directly read kernel memory. However, due to the race condition, out-of-order instructions following the faulting instruction may also execute. Even though instructions appear after the faulting instruction, out-of-order execution allows them to execute, using data retrieved from the instruction that raises the exception. By the time the exception is raised, some number of out-of-order instructions have executed. Although the raised exception causes the CPU to roll back the out-of-order instructions, the cache state is not reverted. This allows data from out-of-order instructions to persist beyond the point when the exception has been raised. \n \nThe impact of Meltdown is that a process running in user space is able to view the contents of kernel memory. Meltdown may also allow Spectre-like memory content leaking that does not cross the user/kernel privilege boundary. \n \nThe Linux kernel mitigations for Meltdown are referred to as KAISER, and subsequently KPTI, which aim to improve separation of kernel and user memory pages. Because the Spectre attacks do not cross user/kernel boundaries, the protections introduced with KAISER/KPTI do not add any protection against them. \n \nThe following table compares Spectre and Meltdown. \n \n| | **Spectre**| **Meltdown** \n---|---|--- \n**CPU mechanism for triggering**| Speculative execution from branch prediction| Out-of-order execution \n**Affected platforms**| CPUs that perform speculative execution from branch prediction| CPUs that allow memory reads in out-of-order instructions \n**Difficulty of successful attack**| High - Requires tailoring to the software environment of the victim process| Low - Kernel memory access exploit code is mostly universal \n**Impact**| Cross- and intra-process (including kernel) memory disclosure| Kernel memory disclosure to userspace \n**Software mitigations**| Variant 1: Compiler changes. Web browser updates to help prevent exploitation from JavaScript \nVariant 2: Indirect Branch Restricted Speculation ([IBRS](<https://lkml.org/lkml/2018/1/4/615>)). \n**Note: **The software mitigation for Spectre variant 2 requires CPU microcode updates| Kernel page-table isolation ([KPTI](<https://en.wikipedia.org/wiki/Kernel_page-table_isolation>)) \n \n### Impact \n\nAn attacker able to execute code with user privileges can achieve various impacts. The Meltdown attack allows reading of kernel memory from userspace. This can result in privilege escalation, disclosure of sensitive information, or it can weaken kernel-level protections, such as KASLR. The Spectre attack can allow inter-process or intra-process data leaks. \n \nTo execute code locally, an attacker would require a valid account or independent compromise of the target. Attacks using JavaScript in web browsers are possible. Multi-user and multi-tenant systems (including virtualized and cloud environments) likely face the greatest risk. Systems used to browse arbitrary web sites are also at risk. Single-user systems that do not readily provide a way for attackers to execute code locally face significantly lower risk. \n \n--- \n \n### Solution \n\n**Apply updates** \n \nOperating system, CPU microcode updates, and some application updates mitigate these attacks. Note that in many cases, the software fixes for these vulnerabilities will have a negative affect on system performance. Also note that Microsoft Windows systems [will no longer receive security updates](<https://doublepulsar.com/important-information-about-microsoft-meltdown-cpu-security-fixes-antivirus-vendors-and-you-a852ba0292ec>) via Windows Update if they are not running compliant anti-virus software. As with deploying any software updates, be sure to prioritize and test updates as necessary. \n \n**Consider CPU Options** \n \nInitial reports from the field indicate that overall system performance is impacted by many of the available patches for these vulnerabilities. Depending on the software workflow and the CPU capabilities present, the performance impact of software mitigations may be non-trivial and therefore may become an ongoing operational concern for some organizations. While we recognize that replacing existing CPUs in already deployed systems is not practical, organizations acquiring new systems should evaluate their CPU selection in light of the expected longevity of this vulnerability in available hardware as well as the performance impacts resulting from the various platform-specific software patches. Deployment contexts and performance requirements vary widely, and must be balanced by informed evaluation of the associated security risks. Contact your system vendor to determine if the CPU and operating system combination will experience a performance penalty due to software mitigations for these vulnerabilities. \n \n--- \n \n### Vendor Information\n\n584653\n\nFilter by status: All Affected Not Affected Unknown\n\nFilter by content: __ Vendor has issued information\n\n__ Sort by: Status Alphabetical\n\nExpand all\n\n__ Affected __ Unknown __ Unaffected \n\n**Javascript is disabled. Click here to view vendors.**\n\n### __ AMD\n\nUpdated: January 03, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://www.amd.com/en/corporate/speculative-execution>\n\n### __ Amazon\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://aws.amazon.com/security/security-bulletins/AWS-2018-013/>\n\n### __ Android Open Source Project\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://source.android.com/security/bulletin/2018-01-01>\n\n### __ Apple\n\nUpdated: February 02, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://support.apple.com/en-us/HT208394\nhttps://support.apple.com/en-us/HT208397\nhttps://support.apple.com/en-us/HT208403\nhttps://support.apple.com/en-us/HT208401\nhttps://support.apple.com/en-ca/HT208465>\n\n### Addendum\n\n<https://twitter.com/aionescu/status/948609809540046849> \n<https://twitter.com/ErrataRob/status/949088097475743744>\n\nIf you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:cert@cert.org?Subject=VU%23584653 Feedback>).\n\n### __ Arm\n\nUpdated: January 03, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://developer.arm.com/support/security-update\nhttps://developer.arm.com/-/media/Files/pdf/Cache_Speculation_Side-channels.pdf>\n\n### Addendum\n\n<https://lwn.net/Articles/740393/>\n\nIf you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:cert@cert.org?Subject=VU%23584653 Feedback>).\n\n### __ CentOS\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://lists.centos.org/pipermail/centos-announce/2018-January/date.html>\n\n### __ Cisco\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20180104-cpusidechannel>\n\n### __ Citrix\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://support.citrix.com/article/CTX231399>\n\n### __ Debian GNU/Linux\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://security-tracker.debian.org/tracker/CVE-2017-5754>\n\n### __ Dell\n\nUpdated: January 08, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<http://www.dell.com/support/contents/us/en/19/article/product-support/self-support-knowledgebase/software-and-downloads/support-for-meltdown-and-spectre>\n\n### __ DragonFly BSD Project\n\nUpdated: January 08, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<http://lists.dragonflybsd.org/pipermail/users/2018-January/313758.html>\n\n### __ Fedora Project\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://fedoramagazine.org/protect-fedora-system-meltdown/>\n\n### __ Fortinet, Inc.\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://fortiguard.com/psirt/FG-IR-18-002>\n\n### __ FreeBSD Project\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://www.freebsd.org/news/newsflash.html#event20180104:01>\n\n### __ Fujitsu\n\nUpdated: January 11, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<http://support.ts.fujitsu.com/content/SideChannelAnalysisMethod.asp?lng=EN>\n\n### __ Google\n\nUpdated: January 03, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://security.googleblog.com/2018/01/todays-cpu-vulnerability-what-you-need.html\nhttps://support.google.com/faqs/answer/7622138>\n\n### __ Hewlett Packard Enterprise\n\nUpdated: January 08, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://www.hpe.com/us/en/services/security-vulnerability.html>\n\n### __ IBM Corporation\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://www.ibm.com/blogs/psirt/potential-cpu-security-issue/>\n\n### __ Intel\n\nUpdated: January 22, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://newsroom.intel.com/news/intel-responds-to-security-research-findings/\nhttps://newsroom.intel.com/news-releases/intel-issues-updates-protect-systems-security-exploits\nhttps://www.intel.com/content/www/us/en/architecture-and-technology/facts-about-side-channel-analysis-and-intel-products.html\nhttps://newsroom.intel.com/news/root-cause-of-reboot-issue-identified-updated-guidance-for-customers-and-partners/\nhttps://newsroom.intel.com/wp-content/uploads/sites/11/2018/01/microcode-update-guidance.pdf>\n\n### __ Lenovo\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://support.lenovo.com/us/en/solutions/len-18282>\n\n### __ Linux Kernel\n\nUpdated: January 04, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://lkml.org/lkml/2017/11/22/956\nhttps://lkml.org/lkml/2018/1/4/174\nhttps://lkml.org/lkml/2018/1/4/615>\n\n### __ Microsoft\n\nUpdated: January 11, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://support.microsoft.com/en-us/help/4073119/protect-against-speculative-execution-side-channel-vulnerabilities-in\nhttps://support.microsoft.com/en-us/help/4072699/january-3-2018-windows-security-updates-and-antivirus-software\nhttps://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/CVE-2017-5715-and-hyper-v-vms\nhttps://portal.msrc.microsoft.com/en-US/security-guidance/advisory/ADV180002\nhttps://blogs.windows.com/msedgedev/2018/01/03/speculative-execution-mitigations-microsoft-edge-internet-explorer/\nhttps://azure.microsoft.com/en-us/blog/securing-azure-customers-from-cpu-vulnerability/\nhttps://cloudblogs.microsoft.com/microsoftsecure/2018/01/09/understanding-the-performance-impact-of-spectre-and-meltdown-mitigations-on-windows-systems/\nhttps://support.microsoft.com/en-us/help/4073707/windows-os-security-update-block-for-some-amd-based-devices>\n\n### Addendum\n\nNote that Windows systems without antivirus do not appear to receive the ADV180002 update automatically. In order to receive the update through Windows Update, run the following command:\n\n \n`reg add \"HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\QualityCompat\" /v cadca5fe-87d3-4b96-b7fb-a231484277cc /t REG_DWORD /d 0 /f` \nIf a third-party antivirus product does not explicitly indicate compatibility with to the protections provided by ADV180002 using the above registry value, the system will not automatically receive the ADV180002 update as well. \n \nOnce a system has the ADV180002 update installed, it must be manually activated using the following commands to make the appropriate registry changes: \n\n\n`reg add \"HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Control\\Session Manager\\Memory Management\" /v FeatureSettingsOverride /t REG_DWORD /d 0 /f` \n`reg add \"HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Control\\Session Manager\\Memory Management\" /v FeatureSettingsOverrideMask /t REG_DWORD /d 3 /f` \n`reg add \"HKLM\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Virtualization\" /v MinVmVersionForCpuBasedMitigations /t REG_SZ /d \"1.0\" /f ` \nAlso note that in addition to the above changes, ADV180002 requires CPU microcode updates to achieve full protection. In some cases, Windows Update may not automatically install the ADV180002 update. An unofficial spreadsheet of antivirus vendor compatibility with this update is maintained here: \n \nOn systems that have not received the ADV180002 update automatically, you may have to install the update manually. Please see for more details. \n \nTo verify that your Windows system has protections against Meltdown and Spectre variant 2, in a PowerShell session running with Administrator privileges, run:\n\n 1. `Install-Module SpeculationControl` \nIf this fails, you may need to install [PackageManagement PowerShell Modules](<https://www.microsoft.com/en-us/download/details.aspx?id=51451>)\n 2. `Get-SpeculationControlSettings` \nIf this fails, you may need to change your PowerShell ExecutionPolicy setting: ` \nSet-ExecutionPolicy RemoteSigned \n`Once you are satisfied with the PowerShell output, you can revert the ExecutionPolicy setting back to the default Restricted setting by running: \n`Set-ExecutionPolicy Restricted`\n` ` \nThe output of this PowerShell command will indicate the status of whether the CPU has the required microcode update, whether Windows has the required software update installed, and whether the mitigations are enabled. Any setting that indicates \"False\" is an indicator of incomplete protection from Meltdown and/or Spectre. \n \nFor example, a system that has the ADV180002 update properly installed and enabled, but is missing the CPU microcode update to fully enable the protections will show output like this: \n \n \nOnce the CPU microcode is updated on such a system (e.g. by way of a BIOS update) , the output will look like this, which indicates that the protections that Microsoft have released are fully enabled: \n \n \nIf the above PowerShell command indicates \"Windows OS support for PCID optimization is enabled: False\", this is a symptom of using a processor that doesn't support process context identifiers (PCID). Such processors cannot take advantage of the performance optimization that avoids a TLB flush. \n \nIf the above PowerShell command indicates \"Hardware requires kernel VA shadowing: False\", this is a symptom of using a processor that doesn't require mitigations for CVE-2017-5754 (Meltdown). \n \nAlso note that Microsoft has not yet provided protection for CVE-2017-5754 (Meltdown) on affected 32-bit platforms. \n\nIf you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:cert@cert.org?Subject=VU%23584653 Feedback>).\n\n### __ Mozilla\n\nUpdated: January 03, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://blog.mozilla.org/security/2018/01/03/mitigations-landing-new-class-timing-attack/>\n\n### __ NVIDIA\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<http://nvidia.custhelp.com/app/answers/detail/a_id/4609\nhttp://nvidia.custhelp.com/app/answers/detail/a_id/4611\nhttp://nvidia.custhelp.com/app/answers/detail/a_id/4613\nhttp://nvidia.custhelp.com/app/answers/detail/a_id/4614\nhttps://www.nvidia.com/en-us/product-security/>\n\n### __ NetBSD\n\nUpdated: January 08, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### __ OpenBSD\n\nUpdated: January 08, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n[https://marc.info/?l=openbsd-tech&m=151521435721902&w=2](<https://marc.info/?l=openbsd-tech&m=151521435721902&w=2>)\n\n### __ Oracle Corporation\n\nUpdated: February 23, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://www.theregister.co.uk/2018/01/16/oracle_quarterly_patches_jan_2018/>\n\n### __ QUALCOMM Incorporated\n\nUpdated: January 11, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Addendum\n\nThe Register has published the following: <https://www.theregister.co.uk/2018/01/06/qualcomm_processor_security_vulnerabilities/>\n\nIf you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:cert@cert.org?Subject=VU%23584653 Feedback>).\n\n### __ Red Hat, Inc.\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n[https://access.redhat.com/security/security-updates/#/security-advisories?q=&p=1&sort=portal_publication_date%20desc&rows=10&documentKind=PortalProduct](<https://access.redhat.com/security/security-updates/#/security-advisories?q=&p=1&sort=portal_publication_date%20desc&rows=10&documentKind=PortalProduct>)\n\n### __ SUSE Linux\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://www.suse.com/c/suse-addresses-meltdown-spectre-vulnerabilities/\nhttp://lists.suse.com/pipermail/sle-security-updates/2018-January/date.html>\n\n### __ Synology\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://www.synology.com/en-global/support/security/Synology_SA_18_01>\n\n### __ Trend Micro\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://success.trendmicro.com/solution/1119183-important-information-for-trend-micro-solutions-and-microsoft-january-2018-security-updates>\n\n### __ Ubuntu\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/SpectreAndMeltdown>\n\n### __ VMware\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://www.vmware.com/security/advisories/VMSA-2018-0002.html>\n\n### __ Xen\n\nUpdated: January 24, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<http://xenbits.xen.org/xsa/advisory-254.html\nhttps://blog.xenproject.org/2018/01/22/xen-project-spectre-meltdown-faq-jan-22-update/>\n\n### __ openSUSE project\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://lists.opensuse.org/opensuse-security-announce/2018-01/msg00001.html>\n\n### __ NetApp\n\nUpdated: January 08, 2018 \n\n### Status\n\n__ Not Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n[security.netapp.com/advisory/ntap-20180104-0001/](<security.netapp.com/advisory/ntap-20180104-0001/>)\n\n### __ Raspberry Pi\n\nUpdated: January 08, 2018 \n\n### Status\n\n__ Not Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://www.raspberrypi.org/blog/why-raspberry-pi-isnt-vulnerable-to-spectre-or-meltdown/>\n\n### __ __ Technicolor\n\nUpdated: January 08, 2018 \n\n### Status\n\n__ Not Affected\n\n### Vendor Statement\n\nBoth Spectre and Meltdown attacks presupposed \u201copen platforms\u201d, where \nadditional code can be added by a non-privileged user. The Technicolor products \nare not open platforms. Even where 3rd party application can run in containers \nand can be managed via Life Cycle Management, these applications are validated \nand signed before they can be installed on the platform. Technicolor is \ncurrently working with its vendors to identify if additional layers of \nprotection are needed. Yet, as the current platforms are closed and have secure \nbootloading mechanism in place, there is no risk and no privilege acquired by \nan attacker in exploiting such an attack on Technicolor's devices.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### __ ASUSTeK Computer Inc.\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Unknown\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### __ Acer\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Unknown\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### __ F5 Networks, Inc.\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Unknown\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n<https://support.f5.com/csp/article/K91229003>\n\n### __ GIGABYTE\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Unknown\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### __ HP Inc.\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Unknown\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### __ Samsung Semiconductor Inc.\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Unknown\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### __ Toshiba Corporation\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Unknown\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\nView all 46 vendors __View less vendors __\n\n \n\n\n### CVSS Metrics \n\nGroup | Score | Vector \n---|---|--- \nBase | 4.4 | AV:L/AC:M/Au:S/C:C/I:N/A:N \nTemporal | 3.4 | E:POC/RL:OF/RC:C \nEnvironmental | 5.1 | CDP:ND/TD:H/CR:H/IR:ND/AR:ND \n \n \n\n\n### References \n\n * <https://vuls.cert.org/confluence/display/Wiki/Vulnerabilities+Associated+with+CPU+Speculative+Execution>\n * <https://meltdownattack.com/>\n * <https://meltdownattack.com/meltdown.pdf>\n * <https://spectreattack.com/>\n * <https://spectreattack.com/spectre.pdf>\n * <https://security.googleblog.com/2018/01/todays-cpu-vulnerability-what-you-need.html>\n * <https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html>\n * <https://cyber.wtf/2017/07/28/negative-result-reading-kernel-memory-from-user-mode/>\n * <https://github.com/IAIK/KAISER>\n * <https://gruss.cc/files/kaiser.pdf>\n * <https://gruss.cc/files/prefetch.pdf>\n * <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5aa90a84589282b87666f92b6c3c917c8080a9bf>\n * <https://lkml.org/lkml/2017/12/27/2>\n * <https://lkml.org/lkml/2018/1/4/615>\n * <https://lwn.net/Articles/741878/>\n * <https://lwn.net/Articles/737940/>\n * <https://lwn.net/Articles/742702/>\n * <http://pythonsweetness.tumblr.com/post/169166980422/the-mysterious-case-of-the-linux-page-table>\n * <https://nakedsecurity.sophos.com/2018/01/03/fckwit-aka-kaiser-aka-kpti-intel-cpu-flaw-needs-low-level-os-patches/>\n * <https://en.wikipedia.org/wiki/Kernel_page-table_isolation>\n * <https://chrisam.net/2018/01/04/speculative-execution-side-channel-vulnerabilities-vendor-published-info/>\n * <https://www.raspberrypi.org/blog/why-raspberry-pi-isnt-vulnerable-to-spectre-or-meltdown/>\n * <https://doublepulsar.com/important-information-about-microsoft-meltdown-cpu-security-fixes-antivirus-vendors-and-you-a852ba0292ec>\n * [https://docs.google.com/spreadsheets/d/184wcDt9I9TUNFFbsAVLpzAtckQxYiuirADzf3cL42FQ/htmlview?usp=sharing&sle=true](<https://docs.google.com/spreadsheets/d/184wcDt9I9TUNFFbsAVLpzAtckQxYiuirADzf3cL42FQ/htmlview?usp=sharing&sle=true>)\n * <https://github.com/iadgov/Spectre-and-Meltdown-Guidance>\n * <https://arxiv.org/abs/1802.03802>\n\n### Acknowledgements\n\nThese issues were researched and reported by researchers at Google Project Zero (Jann Horn) the Institute of Applied Information Processing and Communications (IAIK) at Graz University of Technology (Gruss et. al.), Paul Kocher, and Anders Fogh. \n\nThis document was written by Art Manion and Will Dormann. \n\n### Other Information\n\n**CVE IDs:** | [CVE-2017-5753, ](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5753>) [CVE-2017-5715, ](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5715>) [CVE-2017-5754](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5754>) \n---|--- \n**Date Public:** | 2018-01-03 \n**Date First Published:** | 2018-01-04 \n**Date Last Updated: ** | 2018-07-03 21:27 UTC \n**Document Revision: ** | 230 \n", "published": "2018-01-04T00:00:00", "modified": "2018-07-03T21:27:00", "cvss": {"score": 4.7, "vector": "AV:LOCAL/AC:MEDIUM/Au:NONE/C:COMPLETE/I:NONE/A:NONE/"}, "href": "https://www.kb.cert.org/vuls/id/584653", "reporter": "CERT", "references": ["https://vuls.cert.org/confluence/display/Wiki/Vulnerabilities+Associated+with+CPU+Speculative+Execution", "https://meltdownattack.com/", "https://meltdownattack.com/meltdown.pdf", "https://spectreattack.com/", "https://spectreattack.com/spectre.pdf", "https://security.googleblog.com/2018/01/todays-cpu-vulnerability-what-you-need.html", "https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html", "https://cyber.wtf/2017/07/28/negative-result-reading-kernel-memory-from-user-mode/", "https://github.com/IAIK/KAISER", "https://gruss.cc/files/kaiser.pdf", "https://gruss.cc/files/prefetch.pdf", "https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5aa90a84589282b87666f92b6c3c917c8080a9bf", "https://lkml.org/lkml/2017/12/27/2", "https://lkml.org/lkml/2018/1/4/615", "https://lwn.net/Articles/741878/", "https://lwn.net/Articles/737940/", "https://lwn.net/Articles/742702/", "http://pythonsweetness.tumblr.com/post/169166980422/the-mysterious-case-of-the-linux-page-table", "https://nakedsecurity.sophos.com/2018/01/03/fckwit-aka-kaiser-aka-kpti-intel-cpu-flaw-needs-low-level-os-patches/", "https://en.wikipedia.org/wiki/Kernel_page-table_isolation", "https://chrisam.net/2018/01/04/speculative-execution-side-channel-vulnerabilities-vendor-published-info/", "https://www.raspberrypi.org/blog/why-raspberry-pi-isnt-vulnerable-to-spectre-or-meltdown/", "https://doublepulsar.com/important-information-about-microsoft-meltdown-cpu-security-fixes-antivirus-vendors-and-you-a852ba0292ec", "https://docs.google.com/spreadsheets/d/184wcDt9I9TUNFFbsAVLpzAtckQxYiuirADzf3cL42FQ/htmlview?usp=sharing&sle=true", "https://github.com/iadgov/Spectre-and-Meltdown-Guidance", "https://arxiv.org/abs/1802.03802"], "cvelist": ["CVE-2017-5715", "CVE-2017-5753", "CVE-2017-5754"], "lastseen": "2019-05-01T19:50:10", "history": [], "viewCount": 900, "enchantments": {"score": {"value": 7.2, "vector": "NONE"}, "dependencies": {"references": [{"type": "f5", "idList": ["F5:K91229003"]}, {"type": "symantec", "idList": ["SMNTC-102371", "SMNTC-102378"]}, {"type": "cve", "idList": ["CVE-2017-5753", "CVE-2017-5754", "CVE-2017-5715"]}, {"type": "nessus", "idList": ["UBUNTU_USN-3516-1.NASL", "AIX_IJ03035.NASL", "UBUNTU_USN-3597-1.NASL", "CENTOS_RHSA-2018-0512.NASL", "UBUNTU_USN-3541-2.NASL", "REDHAT-RHSA-2018-0018.NASL", "SUSE_SU-2018-0069-1.NASL", "SL_20180313_KERNEL_ON_SL6_X.NASL", "EULEROS_SA-2018-1002.NASL", "REDHAT-RHSA-2018-0016.NASL"]}, {"type": "openvas", "idList": ["OPENVAS:1361412562310882822", "OPENVAS:1361412562310843423", "OPENVAS:1361412562310843429", "OPENVAS:1361412562310812397", "OPENVAS:1361412562310812295", "OPENVAS:1361412562310843473", "OPENVAS:1361412562310843427", "OPENVAS:1361412562310812296", "OPENVAS:1361412562310812740"]}, {"type": "redhat", "idList": ["RHSA-2018:0010", "RHSA-2018:0496", "RHSA-2018:0045", "RHSA-2018:0047", "RHSA-2018:0008", "RHSA-2018:0007", "RHSA-2018:0091", "RHSA-2018:0020", "RHSA-2018:0022", "RHSA-2018:0011"]}, {"type": "qualysblog", "idList": ["QUALYSBLOG:F8AA5B21D90BCDD30391A24D6FD47892", "QUALYSBLOG:F7C32BA5E6651A8CE3584BB84A88A0C0", "QUALYSBLOG:3ACE52E54FF5FE3EF1B0FC328181FA66", "QUALYSBLOG:BD020D07BF02B0790C62701D997BFD4D", "QUALYSBLOG:C9F2432F760D960CF69CDC55D87263A8"]}, {"type": "securelist", "idList": ["SECURELIST:7CF4DDEB1B5407DAA24EC25BAA7A9654"]}, {"type": "suse", "idList": ["SUSE-SU-2018:0171-1", "SUSE-SU-2018:0069-1", "SUSE-SU-2018:0131-1"]}, {"type": "ubuntu", "idList": ["USN-3597-2", "USN-3597-1", "USN-3541-1", "USN-3540-1"]}, {"type": "centos", "idList": ["CESA-2018:0008", "CESA-2018:0512"]}, {"type": "thn", "idList": ["THN:58CFE19533148E77597FE0AC59963145"]}, {"type": "threatpost", "idList": ["THREATPOST:0F9EDE9A622A021B9B79C50214D7E8AD", "THREATPOST:DB0542CFA474B0D9C91032709EDE296D"]}, {"type": "lenovo", "idList": ["LENOVO:PS500151-NOSID"]}, {"type": "cloudfoundry", "idList": ["CFOUNDRY:86B5C35F8F0E334D1CCCDAF1214EDFEF"]}, {"type": "vmware", "idList": ["VMSA-2018-0007"]}, {"type": "oraclelinux", "idList": ["ELSA-2018-4012"]}, {"type": "seebug", "idList": ["SSV:97059"]}, {"type": "kitploit", "idList": ["KITPLOIT:8752367943592764867"]}, {"type": "paloalto", "idList": ["PAN-SA-2018-0001"]}, {"type": "malwarebytes", "idList": ["MALWAREBYTES:C47D8F4321BF60FB315B6C46B47DF46F"]}], "modified": "2019-05-01T19:50:10"}}, "objectVersion": "1.4"}, "lastseen": "2019-05-01T19:50:10", "differentElements": ["description"], "edition": 25}, {"bulletin": {"id": "VU:584653", "hash": "5cbea3251cccec44cbf3915ff6a39977", "type": "cert", "bulletinFamily": "info", "title": "CPU hardware vulnerable to side-channel attacks", "description": "### Overview \n\nCPU hardware implementations are vulnerable to cache side-channel attacks. These vulnerabilities are referred to as [Meltdown](<https://meltdownattack.com/>) and [Spectre](<https://spectreattack.com/>).\n\n### Description \n\nCPU hardware implementations are vulnerable to side-channel attacks referred to as [Meltdown](<https://meltdownattack.com/>) and [Spectre](<https://spectreattack.com/>). Both Spectre and Meltdown take advantage of the ability to extract information from instructions that have executed on a CPU using the CPU cache as a side-channel. These attacks are described in detail by [Google Project Zero](<https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html>), the Institute of Applied Information Processing and Communications (IAIK) at Graz University of Technology (TU Graz) and Anders Fogh. The issues are organized into three variants:\n\n * Variant 1 (CVE-2017-5753, [Spectre](<https://spectreattack.com/spectre.pdf>)): Bounds check bypass\n * Variant 2 (CVE-2017-5715, also [Spectre](<https://spectreattack.com/spectre.pdf>)): Branch target injection[](<https://spectreattack.com/spectre.pdf>)\n * Variant 3 (CVE-2017-5754, [Meltdown](<https://meltdownattack.com/meltdown.pdf>)): Rogue data cache load, memory access permission check performed after kernel memory read\n \n**Spectre** \n \nSpectre attacks take advantage of a CPU's branch prediction capabilities. Modern CPUs include a feature called branch prediction, which speculatively executes instructions at a location that the CPU believes it will branch to. Such speculative execution helps to more fully utilize the parts of the CPU, minimizing the time waiting, and therefore improving performance. When a branch is successfully predicted, instructions will retire, which means the outcomes of the instructions such as register and memory writes will be committed. If a branch is mispredicted, the speculatively-executed instructions will be discarded, and the direct side-effects of the instructions are undone. What is not undone are the indirect side-effects, such as CPU cache changes. By measuring latency of memory access operations, the cache can be used to extract values from speculatively-executed instructions. \n \nWith Spectre variant 1 (CVE-2017-5753), the instructions after a conditional branch are speculatively executed as the result of a misprediction. With Spectre variant 2 (CVE-2017-5715), the CPU executes instructions at a location determined by a mispredicted branch target. \n \nWith both variants of the Spectre attack, the impact is that a process may leak sensitive data to other processes on a system. Spectre may also allow one part of an application to access other parts of the same process memory space that would otherwise not be permitted. \n \nWhile the Spectre attack itself does not cross a user/kernel memory privilege boundary, depending on the configuration of the target platform, the Spectre attack may indirectly allow a user-space application to access kernel memory. For example, the[ Project Zero blog post](<https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html>) describes a scenario that uses eBPF to exfiltrate kernel memory contents into user-space code. This is made possible because eBPF JIT allows for userspace applications to inject code that is executed in kernel space. While this code is verified by the kernel, eBPF-compliant code will be allowed to execute with kernel permissions. The exploit described by Project Zero leverages eBPF to execute the Spectre attack in kernel space, while exfiltrating the data to user space. It is possible that other technologies that allow in-kernel code execution may also possibly be leveraged to leak kernel memory using Spectre. \n \n**Meltdown** \n \nMeltdown is related to the Spectre attack in that it also uses a cache side channel to access data that otherwise wouldn't be available. The main difference is that it leverages out-of-order execution capabilities in modern CPUs. Like speculative execution due to branch prediction, as used by Spectre, out-of-order execution on a CPU is a technique for ensuring fullest utilization of the CPU's parts. Although instructions may appear sequentially in the machine language, a CPU that supports out-of-order execution may execute instructions in a non-sequential manner, which can minimize the time that a CPU spends idle. \n \nMeltdown leverages insecure behavior that has been demonstrated in Intel CPUs and may affect CPUs from other vendors. Vulnerable CPUs allow memory reads in out-of-order instruction execution, and also contain a race condition between the raising of exceptions and the out-of-order instruction execution. The Meltdown attack reads a kernel memory value, which raises an exception because code running with user-space privileges are not permitted to directly read kernel memory. However, due to the race condition, out-of-order instructions following the faulting instruction may also execute. Even though instructions appear after the faulting instruction, out-of-order execution allows them to execute, using data retrieved from the instruction that raises the exception. By the time the exception is raised, some number of out-of-order instructions have executed. Although the raised exception causes the CPU to roll back the out-of-order instructions, the cache state is not reverted. This allows data from out-of-order instructions to persist beyond the point when the exception has been raised. \n \nThe impact of Meltdown is that a process running in user space is able to view the contents of kernel memory. Meltdown may also allow Spectre-like memory content leaking that does not cross the user/kernel privilege boundary. \n \nThe Linux kernel mitigations for Meltdown are referred to as KAISER, and subsequently KPTI, which aim to improve separation of kernel and user memory pages. Because the Spectre attacks do not cross user/kernel boundaries, the protections introduced with KAISER/KPTI do not add any protection against them. \n \nThe following table compares Spectre and Meltdown. \n \n| | **Spectre**| **Meltdown** \n---|---|--- \n**CPU mechanism for triggering**| Speculative execution from branch prediction| Out-of-order execution \n**Affected platforms**| CPUs that perform speculative execution from branch prediction| CPUs that allow memory reads in out-of-order instructions \n**Difficulty of successful attack**| High - Requires tailoring to the software environment of the victim process| Low - Kernel memory access exploit code is mostly universal \n**Impact**| Cross- and intra-process (including kernel) memory disclosure| Kernel memory disclosure to userspace \n**Software mitigations**| Variant 1: Compiler changes. Web browser updates to help prevent exploitation from JavaScript \nVariant 2: Indirect Branch Restricted Speculation ([IBRS](<https://lkml.org/lkml/2018/1/4/615>)). \n**Note: **The software mitigation for Spectre variant 2 requires CPU microcode updates| Kernel page-table isolation ([KPTI](<https://en.wikipedia.org/wiki/Kernel_page-table_isolation>)) \n \n### Impact \n\nAn attacker able to execute code with user privileges can achieve various impacts. The Meltdown attack allows reading of kernel memory from userspace. This can result in privilege escalation, disclosure of sensitive information, or it can weaken kernel-level protections, such as KASLR. The Spectre attack can allow inter-process or intra-process data leaks. \n \nTo execute code locally, an attacker would require a valid account or independent compromise of the target. Attacks using JavaScript in web browsers are possible. Multi-user and multi-tenant systems (including virtualized and cloud environments) likely face the greatest risk. Systems used to browse arbitrary web sites are also at risk. Single-user systems that do not readily provide a way for attackers to execute code locally face significantly lower risk. \n \n--- \n \n### Solution \n\n**Apply updates** \n \nOperating system, CPU microcode updates, and some application updates mitigate these attacks. Note that in many cases, the software fixes for these vulnerabilities will have a negative affect on system performance. Also note that Microsoft Windows systems [will no longer receive security updates](<https://doublepulsar.com/important-information-about-microsoft-meltdown-cpu-security-fixes-antivirus-vendors-and-you-a852ba0292ec>) via Windows Update if they are not running compliant anti-virus software. As with deploying any software updates, be sure to prioritize and test updates as necessary. \n \n**Consider CPU Options** \n \nInitial reports from the field indicate that overall system performance is impacted by many of the available patches for these vulnerabilities. Depending on the software workflow and the CPU capabilities present, the performance impact of software mitigations may be non-trivial and therefore may become an ongoing operational concern for some organizations. While we recognize that replacing existing CPUs in already deployed systems is not practical, organizations acquiring new systems should evaluate their CPU selection in light of the expected longevity of this vulnerability in available hardware as well as the performance impacts resulting from the various platform-specific software patches. Deployment contexts and performance requirements vary widely, and must be balanced by informed evaluation of the associated security risks. Contact your system vendor to determine if the CPU and operating system combination will experience a performance penalty due to software mitigations for these vulnerabilities. \n \n--- \n \n### Vendor Information\n\n584653\n\nFilter by status: All Affected Not Affected Unknown\n\nFilter by content: __ Vendor has issued information\n\n__ Sort by: Status Alphabetical\n\nExpand all\n\n__ Affected __ Unknown __ Unaffected \n\n**Javascript is disabled. Click here to view vendors.**\n\n### __ AMD\n\nUpdated: January 03, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://www.amd.com/en/corporate/speculative-execution>\n\n### __ Amazon\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://aws.amazon.com/security/security-bulletins/AWS-2018-013/>\n\n### __ Android Open Source Project\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://source.android.com/security/bulletin/2018-01-01>\n\n### __ Apple\n\nUpdated: February 02, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://support.apple.com/en-us/HT208394>\n * <https://support.apple.com/en-us/HT208397>\n * <https://support.apple.com/en-us/HT208403>\n * <https://support.apple.com/en-us/HT208401>\n * <https://support.apple.com/en-ca/HT208465>\n\n### Addendum\n\n<https://twitter.com/aionescu/status/948609809540046849> \n<https://twitter.com/ErrataRob/status/949088097475743744>\n\nIf you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:cert@cert.org?Subject=VU%23584653 Feedback>).\n\n### __ Arm\n\nUpdated: January 03, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://developer.arm.com/support/security-update>\n * <https://developer.arm.com/-/media/Files/pdf/Cache_Speculation_Side-channels.pdf>\n\n### Addendum\n\n<https://lwn.net/Articles/740393/>\n\nIf you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:cert@cert.org?Subject=VU%23584653 Feedback>).\n\n### __ CentOS\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://lists.centos.org/pipermail/centos-announce/2018-January/date.html>\n\n### __ Cisco\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20180104-cpusidechannel>\n\n### __ Citrix\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://support.citrix.com/article/CTX231399>\n\n### __ Debian GNU/Linux\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://security-tracker.debian.org/tracker/CVE-2017-5754>\n\n### __ Dell\n\nUpdated: January 08, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://http://www.dell.com/support/contents/us/en/19/article/product-support/self-support-knowledgebase/software-and-downloads/support-for-meltdown-and-spectre>\n\n### __ DragonFly BSD Project\n\nUpdated: January 08, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://http://lists.dragonflybsd.org/pipermail/users/2018-January/313758.html>\n\n### __ Fedora Project\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://fedoramagazine.org/protect-fedora-system-meltdown/>\n\n### __ Fortinet, Inc.\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://fortiguard.com/psirt/FG-IR-18-002>\n\n### __ FreeBSD Project\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://www.freebsd.org/news/newsflash.html#event20180104:01>\n\n### __ Fujitsu\n\nUpdated: January 11, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://http://support.ts.fujitsu.com/content/SideChannelAnalysisMethod.asp?lng=EN>\n\n### __ Google\n\nUpdated: January 03, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://security.googleblog.com/2018/01/todays-cpu-vulnerability-what-you-need.html>\n * <https://support.google.com/faqs/answer/7622138>\n\n### __ Hewlett Packard Enterprise\n\nUpdated: January 08, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://www.hpe.com/us/en/services/security-vulnerability.html>\n\n### __ IBM Corporation\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://www.ibm.com/blogs/psirt/potential-cpu-security-issue/>\n\n### __ Intel\n\nUpdated: January 22, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://newsroom.intel.com/news/intel-responds-to-security-research-findings/>\n * <https://newsroom.intel.com/news-releases/intel-issues-updates-protect-systems-security-exploits>\n * <https://www.intel.com/content/www/us/en/architecture-and-technology/facts-about-side-channel-analysis-and-intel-products.html>\n * <https://newsroom.intel.com/news/root-cause-of-reboot-issue-identified-updated-guidance-for-customers-and-partners/>\n * <https://newsroom.intel.com/wp-content/uploads/sites/11/2018/01/microcode-update-guidance.pdf>\n\n### __ Lenovo\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://support.lenovo.com/us/en/solutions/len-18282>\n\n### __ Linux Kernel\n\nUpdated: January 04, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://lkml.org/lkml/2017/11/22/956>\n * <https://lkml.org/lkml/2018/1/4/174>\n * <https://lkml.org/lkml/2018/1/4/615>\n\n### __ Microsoft\n\nUpdated: January 11, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://support.microsoft.com/en-us/help/4073119/protect-against-speculative-execution-side-channel-vulnerabilities-in>\n * <https://support.microsoft.com/en-us/help/4072699/january-3-2018-windows-security-updates-and-antivirus-software>\n * <https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/CVE-2017-5715-and-hyper-v-vms>\n * <https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/ADV180002>\n * <https://blogs.windows.com/msedgedev/2018/01/03/speculative-execution-mitigations-microsoft-edge-internet-explorer/>\n * <https://azure.microsoft.com/en-us/blog/securing-azure-customers-from-cpu-vulnerability/>\n * <https://cloudblogs.microsoft.com/microsoftsecure/2018/01/09/understanding-the-performance-impact-of-spectre-and-meltdown-mitigations-on-windows-systems/>\n * <https://support.microsoft.com/en-us/help/4073707/windows-os-security-update-block-for-some-amd-based-devices>\n\n### Addendum\n\nNote that Windows systems without antivirus do not appear to receive the ADV180002 update automatically. In order to receive the update through Windows Update, run the following command:\n\n \n`reg add \"HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\QualityCompat\" /v cadca5fe-87d3-4b96-b7fb-a231484277cc /t REG_DWORD /d 0 /f` \nIf a third-party antivirus product does not explicitly indicate compatibility with to the protections provided by ADV180002 using the above registry value, the system will not automatically receive the ADV180002 update as well. \n \nOnce a system has the ADV180002 update installed, it must be manually activated using the following commands to make the appropriate registry changes: \n\n\n`reg add \"HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Control\\Session Manager\\Memory Management\" /v FeatureSettingsOverride /t REG_DWORD /d 0 /f` \n`reg add \"HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Control\\Session Manager\\Memory Management\" /v FeatureSettingsOverrideMask /t REG_DWORD /d 3 /f` \n`reg add \"HKLM\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Virtualization\" /v MinVmVersionForCpuBasedMitigations /t REG_SZ /d \"1.0\" /f ` \nAlso note that in addition to the above changes, ADV180002 requires CPU microcode updates to achieve full protection. In some cases, Windows Update may not automatically install the ADV180002 update. An unofficial spreadsheet of antivirus vendor compatibility with this update is maintained here: \n \nOn systems that have not received the ADV180002 update automatically, you may have to install the update manually. Please see for more details. \n \nTo verify that your Windows system has protections against Meltdown and Spectre variant 2, in a PowerShell session running with Administrator privileges, run:\n\n 1. `Install-Module SpeculationControl` \nIf this fails, you may need to install [PackageManagement PowerShell Modules](<https://www.microsoft.com/en-us/download/details.aspx?id=51451>)\n 2. `Get-SpeculationControlSettings` \nIf this fails, you may need to change your PowerShell ExecutionPolicy setting: ` \nSet-ExecutionPolicy RemoteSigned \n`Once you are satisfied with the PowerShell output, you can revert the ExecutionPolicy setting back to the default Restricted setting by running: \n`Set-ExecutionPolicy Restricted`\n` ` \nThe output of this PowerShell command will indicate the status of whether the CPU has the required microcode update, whether Windows has the required software update installed, and whether the mitigations are enabled. Any setting that indicates \"False\" is an indicator of incomplete protection from Meltdown and/or Spectre. \n \nFor example, a system that has the ADV180002 update properly installed and enabled, but is missing the CPU microcode update to fully enable the protections will show output like this: \n \n \nOnce the CPU microcode is updated on such a system (e.g. by way of a BIOS update) , the output will look like this, which indicates that the protections that Microsoft have released are fully enabled: \n \n \nIf the above PowerShell command indicates \"Windows OS support for PCID optimization is enabled: False\", this is a symptom of using a processor that doesn't support process context identifiers (PCID). Such processors cannot take advantage of the performance optimization that avoids a TLB flush. \n \nIf the above PowerShell command indicates \"Hardware requires kernel VA shadowing: False\", this is a symptom of using a processor that doesn't require mitigations for CVE-2017-5754 (Meltdown). \n \nAlso note that Microsoft has not yet provided protection for CVE-2017-5754 (Meltdown) on affected 32-bit platforms. \n\nIf you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:cert@cert.org?Subject=VU%23584653 Feedback>).\n\n### __ Mozilla\n\nUpdated: January 03, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://blog.mozilla.org/security/2018/01/03/mitigations-landing-new-class-timing-attack/>\n\n### __ NVIDIA\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://http://nvidia.custhelp.com/app/answers/detail/a_id/4609\nhttp://nvidia.custhelp.com/app/answers/detail/a_id/4611\nhttp://nvidia.custhelp.com/app/answers/detail/a_id/4613\nhttp://nvidia.custhelp.com/app/answers/detail/a_id/4614>\n * <https://www.nvidia.com/en-us/product-security/>\n\n### __ NetBSD\n\nUpdated: January 08, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### __ OpenBSD\n\nUpdated: January 08, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * [https://marc.info/?l=openbsd-tech&m=151521435721902&w=2](<https://marc.info/?l=openbsd-tech&m=151521435721902&w=2>)\n\n### __ Oracle Corporation\n\nUpdated: February 23, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://www.theregister.co.uk/2018/01/16/oracle_quarterly_patches_jan_2018/>\n\n### __ QUALCOMM Incorporated\n\nUpdated: January 11, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Addendum\n\nThe Register has published the following: <https://www.theregister.co.uk/2018/01/06/qualcomm_processor_security_vulnerabilities/>\n\nIf you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:cert@cert.org?Subject=VU%23584653 Feedback>).\n\n### __ Red Hat, Inc.\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * [https://access.redhat.com/security/security-updates/#/security-advisories?q=&p=1&sort=portal_publication_date%20desc&rows=10&documentKind=PortalProduct](<https://access.redhat.com/security/security-updates/#/security-advisories?q=&p=1&sort=portal_publication_date%20desc&rows=10&documentKind=PortalProduct>)\n\n### __ SUSE Linux\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://www.suse.com/c/suse-addresses-meltdown-spectre-vulnerabilities/\nhttp://lists.suse.com/pipermail/sle-security-updates/2018-January/date.html>\n\n### __ Synology\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://www.synology.com/en-global/support/security/Synology_SA_18_01>\n\n### __ Trend Micro\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://success.trendmicro.com/solution/1119183-important-information-for-trend-micro-solutions-and-microsoft-january-2018-security-updates>\n\n### __ Ubuntu\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/SpectreAndMeltdown>\n\n### __ VMware\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://www.vmware.com/security/advisories/VMSA-2018-0002.html>\n\n### __ Xen\n\nUpdated: January 24, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://http://xenbits.xen.org/xsa/advisory-254.html>\n * <https://blog.xenproject.org/2018/01/22/xen-project-spectre-meltdown-faq-jan-22-update/>\n\n### __ openSUSE project\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://lists.opensuse.org/opensuse-security-announce/2018-01/msg00001.html>\n\n### __ NetApp\n\nUpdated: January 08, 2018 \n\n### Status\n\n__ Not Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://security.netapp.com/advisory/ntap-20180104-0001/>\n\n### __ Raspberry Pi\n\nUpdated: January 08, 2018 \n\n### Status\n\n__ Not Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://www.raspberrypi.org/blog/why-raspberry-pi-isnt-vulnerable-to-spectre-or-meltdown/>\n\n### __ __ Technicolor\n\nUpdated: January 08, 2018 \n\n### Status\n\n__ Not Affected\n\n### Vendor Statement\n\nBoth Spectre and Meltdown attacks presupposed \u201copen platforms\u201d, where \nadditional code can be added by a non-privileged user. The Technicolor products \nare not open platforms. Even where 3rd party application can run in containers \nand can be managed via Life Cycle Management, these applications are validated \nand signed before they can be installed on the platform. Technicolor is \ncurrently working with its vendors to identify if additional layers of \nprotection are needed. Yet, as the current platforms are closed and have secure \nbootloading mechanism in place, there is no risk and no privilege acquired by \nan attacker in exploiting such an attack on Technicolor's devices.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### __ ASUSTeK Computer Inc.\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Unknown\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### __ Acer\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Unknown\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### __ F5 Networks, Inc.\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Unknown\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://support.f5.com/csp/article/K91229003>\n\n### __ GIGABYTE\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Unknown\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### __ HP Inc.\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Unknown\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### __ Samsung Semiconductor Inc.\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Unknown\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### __ Toshiba Corporation\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Unknown\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\nView all 46 vendors __View less vendors __\n\n \n\n\n### CVSS Metrics \n\nGroup | Score | Vector \n---|---|--- \nBase | 4.4 | AV:L/AC:M/Au:S/C:C/I:N/A:N \nTemporal | 3.4 | E:POC/RL:OF/RC:C \nEnvironmental | 5.1 | CDP:ND/TD:H/CR:H/IR:ND/AR:ND \n \n \n\n\n### References \n\n * <https://vuls.cert.org/confluence/display/Wiki/Vulnerabilities+Associated+with+CPU+Speculative+Execution>\n * <https://meltdownattack.com/>\n * <https://meltdownattack.com/meltdown.pdf>\n * <https://spectreattack.com/>\n * <https://spectreattack.com/spectre.pdf>\n * <https://security.googleblog.com/2018/01/todays-cpu-vulnerability-what-you-need.html>\n * <https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html>\n * <https://cyber.wtf/2017/07/28/negative-result-reading-kernel-memory-from-user-mode/>\n * <https://github.com/IAIK/KAISER>\n * <https://gruss.cc/files/kaiser.pdf>\n * <https://gruss.cc/files/prefetch.pdf>\n * <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5aa90a84589282b87666f92b6c3c917c8080a9bf>\n * <https://lkml.org/lkml/2017/12/27/2>\n * <https://lkml.org/lkml/2018/1/4/615>\n * <https://lwn.net/Articles/741878/>\n * <https://lwn.net/Articles/737940/>\n * <https://lwn.net/Articles/742702/>\n * <http://pythonsweetness.tumblr.com/post/169166980422/the-mysterious-case-of-the-linux-page-table>\n * <https://nakedsecurity.sophos.com/2018/01/03/fckwit-aka-kaiser-aka-kpti-intel-cpu-flaw-needs-low-level-os-patches/>\n * <https://en.wikipedia.org/wiki/Kernel_page-table_isolation>\n * <https://chrisam.net/2018/01/04/speculative-execution-side-channel-vulnerabilities-vendor-published-info/>\n * <https://www.raspberrypi.org/blog/why-raspberry-pi-isnt-vulnerable-to-spectre-or-meltdown/>\n * <https://doublepulsar.com/important-information-about-microsoft-meltdown-cpu-security-fixes-antivirus-vendors-and-you-a852ba0292ec>\n * [https://docs.google.com/spreadsheets/d/184wcDt9I9TUNFFbsAVLpzAtckQxYiuirADzf3cL42FQ/htmlview?usp=sharing&sle=true](<https://docs.google.com/spreadsheets/d/184wcDt9I9TUNFFbsAVLpzAtckQxYiuirADzf3cL42FQ/htmlview?usp=sharing&sle=true>)\n * <https://github.com/iadgov/Spectre-and-Meltdown-Guidance>\n * <https://arxiv.org/abs/1802.03802>\n\n### Acknowledgements\n\nThese issues were researched and reported by researchers at Google Project Zero (Jann Horn) the Institute of Applied Information Processing and Communications (IAIK) at Graz University of Technology (Gruss et. al.), Paul Kocher, and Anders Fogh. \n\nThis document was written by Art Manion and Will Dormann. \n\n### Other Information\n\n**CVE IDs:** | [CVE-2017-5753, ](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5753>) [CVE-2017-5715, ](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5715>) [CVE-2017-5754](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5754>) \n---|--- \n**Date Public:** | 2018-01-03 \n**Date First Published:** | 2018-01-04 \n**Date Last Updated: ** | 2018-07-03 21:27 UTC \n**Document Revision: ** | 230 \n", "published": "2018-01-04T00:00:00", "modified": "2018-07-03T21:27:00", "cvss": {"score": 4.7, "vector": "AV:LOCAL/AC:MEDIUM/Au:NONE/C:COMPLETE/I:NONE/A:NONE/"}, "href": "https://www.kb.cert.org/vuls/id/584653", "reporter": "CERT", "references": ["https://vuls.cert.org/confluence/display/Wiki/Vulnerabilities+Associated+with+CPU+Speculative+Execution", "https://meltdownattack.com/", "https://meltdownattack.com/meltdown.pdf", "https://spectreattack.com/", "https://spectreattack.com/spectre.pdf", "https://security.googleblog.com/2018/01/todays-cpu-vulnerability-what-you-need.html", "https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html", "https://cyber.wtf/2017/07/28/negative-result-reading-kernel-memory-from-user-mode/", "https://github.com/IAIK/KAISER", "https://gruss.cc/files/kaiser.pdf", "https://gruss.cc/files/prefetch.pdf", "https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5aa90a84589282b87666f92b6c3c917c8080a9bf", "https://lkml.org/lkml/2017/12/27/2", "https://lkml.org/lkml/2018/1/4/615", "https://lwn.net/Articles/741878/", "https://lwn.net/Articles/737940/", "https://lwn.net/Articles/742702/", "http://pythonsweetness.tumblr.com/post/169166980422/the-mysterious-case-of-the-linux-page-table", "https://nakedsecurity.sophos.com/2018/01/03/fckwit-aka-kaiser-aka-kpti-intel-cpu-flaw-needs-low-level-os-patches/", "https://en.wikipedia.org/wiki/Kernel_page-table_isolation", "https://chrisam.net/2018/01/04/speculative-execution-side-channel-vulnerabilities-vendor-published-info/", "https://www.raspberrypi.org/blog/why-raspberry-pi-isnt-vulnerable-to-spectre-or-meltdown/", "https://doublepulsar.com/important-information-about-microsoft-meltdown-cpu-security-fixes-antivirus-vendors-and-you-a852ba0292ec", "https://docs.google.com/spreadsheets/d/184wcDt9I9TUNFFbsAVLpzAtckQxYiuirADzf3cL42FQ/htmlview?usp=sharing&sle=true", "https://github.com/iadgov/Spectre-and-Meltdown-Guidance", "https://arxiv.org/abs/1802.03802"], "cvelist": ["CVE-2017-5715", "CVE-2017-5753", "CVE-2017-5754"], "lastseen": "2019-05-21T16:50:51", "history": [], "viewCount": 907, "enchantments": {"score": {"value": 7.2, "vector": "NONE"}, "dependencies": {"references": [{"type": "f5", "idList": ["F5:K91229003"]}, {"type": "symantec", "idList": ["SMNTC-102371", "SMNTC-102378"]}, {"type": "cve", "idList": ["CVE-2017-5753", "CVE-2017-5754", "CVE-2017-5715"]}, {"type": "redhat", "idList": ["RHSA-2018:0007", "RHSA-2018:0020", "RHSA-2018:0090", "RHSA-2018:0011", "RHSA-2018:0022", "RHSA-2018:0091", "RHSA-2018:0092", "RHSA-2018:0008", "RHSA-2018:0046", "RHSA-2018:0045"]}, {"type": "nessus", "idList": ["REDHAT-RHSA-2018-0021.NASL", "SMB_ADV180002_MSSQL.NASL", "REDHAT-RHSA-2018-0046.NASL", "REDHAT-RHSA-2018-0044.NASL", "EULEROS_SA-2018-1001.NASL", "VIRTUOZZO_VZA-2018-006.NASL", "REDHAT-RHSA-2018-0020.NASL", "REDHAT-RHSA-2018-0496.NASL", "ORACLELINUX_ELSA-2018-0512.NASL", "SUSE_SU-2018-0114-1.NASL"]}, {"type": "suse", "idList": ["SUSE-SU-2018:0131-1", "SUSE-SU-2018:0069-1", "SUSE-SU-2018:0171-1", "SUSE-SU-2018:0114-1"]}, {"type": "qualysblog", "idList": ["QUALYSBLOG:C9F2432F760D960CF69CDC55D87263A8", "QUALYSBLOG:BD020D07BF02B0790C62701D997BFD4D", "QUALYSBLOG:F7C32BA5E6651A8CE3584BB84A88A0C0", "QUALYSBLOG:3ACE52E54FF5FE3EF1B0FC328181FA66", "QUALYSBLOG:F8AA5B21D90BCDD30391A24D6FD47892"]}, {"type": "lenovo", "idList": ["LENOVO:PS500151-NOSID"]}, {"type": "threatpost", "idList": ["THREATPOST:0F9EDE9A622A021B9B79C50214D7E8AD", "THREATPOST:DB0542CFA474B0D9C91032709EDE296D"]}, {"type": "oraclelinux", "idList": ["ELSA-2018-4012"]}, {"type": "thn", "idList": ["THN:58CFE19533148E77597FE0AC59963145"]}, {"type": "openvas", "idList": ["OPENVAS:1361412562310843427", "OPENVAS:1361412562310843473", "OPENVAS:1361412562310812296", "OPENVAS:1361412562310812295", "OPENVAS:1361412562310843423", "OPENVAS:1361412562310843429", "OPENVAS:1361412562310882822", "OPENVAS:1361412562310812397"]}, {"type": "seebug", "idList": ["SSV:97059"]}, {"type": "vmware", "idList": ["VMSA-2018-0007"]}, {"type": "ubuntu", "idList": ["USN-3597-1", "USN-3541-1", "USN-3540-1", "USN-3597-2", "USN-3540-2", "USN-3541-2"]}, {"type": "cloudfoundry", "idList": ["CFOUNDRY:86B5C35F8F0E334D1CCCDAF1214EDFEF"]}, {"type": "centos", "idList": ["CESA-2018:0008"]}, {"type": "securelist", "idList": ["SECURELIST:7CF4DDEB1B5407DAA24EC25BAA7A9654"]}, {"type": "kitploit", "idList": ["KITPLOIT:8752367943592764867"]}, {"type": "talosblog", "idList": ["TALOSBLOG:6AF8BBB020A686E442B50095CA9B7A36"]}], "modified": "2019-05-21T16:50:51"}}, "objectVersion": "1.4"}, "lastseen": "2019-05-21T16:50:51", "differentElements": ["description"], "edition": 26}, {"bulletin": {"id": "VU:584653", "hash": "8e76de8b7b74c9b5928b607e3cd73be1", "type": "cert", "bulletinFamily": "info", "title": "CPU hardware vulnerable to side-channel attacks", "description": "### Overview \n\nCPU hardware implementations are vulnerable to cache side-channel attacks. These vulnerabilities are referred to as [Meltdown](<https://meltdownattack.com/>) and [Spectre](<https://spectreattack.com/>).\n\n### Description \n\nCPU hardware implementations are vulnerable to side-channel attacks referred to as [Meltdown](<https://meltdownattack.com/>) and [Spectre](<https://spectreattack.com/>). Both Spectre and Meltdown take advantage of the ability to extract information from instructions that have executed on a CPU using the CPU cache as a side-channel. These attacks are described in detail by [Google Project Zero](<https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html>), the Institute of Applied Information Processing and Communications (IAIK) at Graz University of Technology (TU Graz) and Anders Fogh. The issues are organized into three variants:\n\n * Variant 1 (CVE-2017-5753, [Spectre](<https://spectreattack.com/spectre.pdf>)): Bounds check bypass\n * Variant 2 (CVE-2017-5715, also [Spectre](<https://spectreattack.com/spectre.pdf>)): Branch target injection[](<https://spectreattack.com/spectre.pdf>)\n * Variant 3 (CVE-2017-5754, [Meltdown](<https://meltdownattack.com/meltdown.pdf>)): Rogue data cache load, memory access permission check performed after kernel memory read\n \n**Spectre** \n \nSpectre attacks take advantage of a CPU's branch prediction capabilities. Modern CPUs include a feature called branch prediction, which speculatively executes instructions at a location that the CPU believes it will branch to. Such speculative execution helps to more fully utilize the parts of the CPU, minimizing the time waiting, and therefore improving performance. When a branch is successfully predicted, instructions will retire, which means the outcomes of the instructions such as register and memory writes will be committed. If a branch is mispredicted, the speculatively-executed instructions will be discarded, and the direct side-effects of the instructions are undone. What is not undone are the indirect side-effects, such as CPU cache changes. By measuring latency of memory access operations, the cache can be used to extract values from speculatively-executed instructions. \n \nWith Spectre variant 1 (CVE-2017-5753), the instructions after a conditional branch are speculatively executed as the result of a misprediction. With Spectre variant 2 (CVE-2017-5715), the CPU executes instructions at a location determined by a mispredicted branch target. \n \nWith both variants of the Spectre attack, the impact is that a process may leak sensitive data to other processes on a system. Spectre may also allow one part of an application to access other parts of the same process memory space that would otherwise not be permitted. \n \nWhile the Spectre attack itself does not cross a user/kernel memory privilege boundary, depending on the configuration of the target platform, the Spectre attack may indirectly allow a user-space application to access kernel memory. For example, the[ Project Zero blog post](<https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html>) describes a scenario that uses eBPF to exfiltrate kernel memory contents into user-space code. This is made possible because eBPF JIT allows for userspace applications to inject code that is executed in kernel space. While this code is verified by the kernel, eBPF-compliant code will be allowed to execute with kernel permissions. The exploit described by Project Zero leverages eBPF to execute the Spectre attack in kernel space, while exfiltrating the data to user space. It is possible that other technologies that allow in-kernel code execution may also possibly be leveraged to leak kernel memory using Spectre. \n \n**Meltdown** \n \nMeltdown is related to the Spectre attack in that it also uses a cache side channel to access data that otherwise wouldn't be available. The main difference is that it leverages out-of-order execution capabilities in modern CPUs. Like speculative execution due to branch prediction, as used by Spectre, out-of-order execution on a CPU is a technique for ensuring fullest utilization of the CPU's parts. Although instructions may appear sequentially in the machine language, a CPU that supports out-of-order execution may execute instructions in a non-sequential manner, which can minimize the time that a CPU spends idle. \n \nMeltdown leverages insecure behavior that has been demonstrated in Intel CPUs and may affect CPUs from other vendors. Vulnerable CPUs allow memory reads in out-of-order instruction execution, and also contain a race condition between the raising of exceptions and the out-of-order instruction execution. The Meltdown attack reads a kernel memory value, which raises an exception because code running with user-space privileges are not permitted to directly read kernel memory. However, due to the race condition, out-of-order instructions following the faulting instruction may also execute. Even though instructions appear after the faulting instruction, out-of-order execution allows them to execute, using data retrieved from the instruction that raises the exception. By the time the exception is raised, some number of out-of-order instructions have executed. Although the raised exception causes the CPU to roll back the out-of-order instructions, the cache state is not reverted. This allows data from out-of-order instructions to persist beyond the point when the exception has been raised. \n \nThe impact of Meltdown is that a process running in user space is able to view the contents of kernel memory. Meltdown may also allow Spectre-like memory content leaking that does not cross the user/kernel privilege boundary. \n \nThe Linux kernel mitigations for Meltdown are referred to as KAISER, and subsequently KPTI, which aim to improve separation of kernel and user memory pages. Because the Spectre attacks do not cross user/kernel boundaries, the protections introduced with KAISER/KPTI do not add any protection against them. \n \nThe following table compares Spectre and Meltdown. \n \n| | **Spectre**| **Meltdown** \n---|---|--- \n**CPU mechanism for triggering**| Speculative execution from branch prediction| Out-of-order execution \n**Affected platforms**| CPUs that perform speculative execution from branch prediction| CPUs that allow memory reads in out-of-order instructions \n**Difficulty of successful attack**| High - Requires tailoring to the software environment of the victim process| Low - Kernel memory access exploit code is mostly universal \n**Impact**| Cross- and intra-process (including kernel) memory disclosure| Kernel memory disclosure to userspace \n**Software mitigations**| Variant 1: Compiler changes. Web browser updates to help prevent exploitation from JavaScript \nVariant 2: Indirect Branch Restricted Speculation ([IBRS](<https://lkml.org/lkml/2018/1/4/615>)). \n**Note: **The software mitigation for Spectre variant 2 requires CPU microcode updates| Kernel page-table isolation ([KPTI](<https://en.wikipedia.org/wiki/Kernel_page-table_isolation>)) \n \n### Impact \n\nAn attacker able to execute code with user privileges can achieve various impacts. The Meltdown attack allows reading of kernel memory from userspace. This can result in privilege escalation, disclosure of sensitive information, or it can weaken kernel-level protections, such as KASLR. The Spectre attack can allow inter-process or intra-process data leaks. \n \nTo execute code locally, an attacker would require a valid account or independent compromise of the target. Attacks using JavaScript in web browsers are possible. Multi-user and multi-tenant systems (including virtualized and cloud environments) likely face the greatest risk. Systems used to browse arbitrary web sites are also at risk. Single-user systems that do not readily provide a way for attackers to execute code locally face significantly lower risk. \n \n--- \n \n### Solution \n\n**Apply updates** \n \nOperating system, CPU microcode updates, and some application updates mitigate these attacks. Note that in many cases, the software fixes for these vulnerabilities will have a negative affect on system performance. Also note that Microsoft Windows systems [will no longer receive security updates](<https://doublepulsar.com/important-information-about-microsoft-meltdown-cpu-security-fixes-antivirus-vendors-and-you-a852ba0292ec>) via Windows Update if they are not running compliant anti-virus software. As with deploying any software updates, be sure to prioritize and test updates as necessary. \n \n**Consider CPU Options** \n \nInitial reports from the field indicate that overall system performance is impacted by many of the available patches for these vulnerabilities. Depending on the software workflow and the CPU capabilities present, the performance impact of software mitigations may be non-trivial and therefore may become an ongoing operational concern for some organizations. While we recognize that replacing existing CPUs in already deployed systems is not practical, organizations acquiring new systems should evaluate their CPU selection in light of the expected longevity of this vulnerability in available hardware as well as the performance impacts resulting from the various platform-specific software patches. Deployment contexts and performance requirements vary widely, and must be balanced by informed evaluation of the associated security risks. Contact your system vendor to determine if the CPU and operating system combination will experience a performance penalty due to software mitigations for these vulnerabilities. \n \n--- \n \n### Vendor Information\n\n584653\n\nFilter by status: All Affected Not Affected Unknown\n\nFilter by content: __ Vendor has issued information\n\n__ Sort by: Status Alphabetical\n\nExpand all\n\n__ Affected __ Unknown __ Unaffected \n\n**Javascript is disabled. Click here to view vendors.**\n\n### __ AMD\n\nUpdated: January 03, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://www.amd.com/en/corporate/speculative-execution>\n\n### __ Amazon\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://aws.amazon.com/security/security-bulletins/AWS-2018-013/>\n\n### __ Android Open Source Project\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://source.android.com/security/bulletin/2018-01-01>\n\n### __ Apple\n\nUpdated: February 02, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://support.apple.com/en-us/HT208394>\n * <https://support.apple.com/en-us/HT208397>\n * <https://support.apple.com/en-us/HT208403>\n * <https://support.apple.com/en-us/HT208401>\n * <https://support.apple.com/en-ca/HT208465>\n\n### Addendum\n\n<https://twitter.com/aionescu/status/948609809540046849> \n<https://twitter.com/ErrataRob/status/949088097475743744>\n\nIf you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:cert@cert.org?Subject=VU%23584653 Feedback>).\n\n### __ Arm\n\nUpdated: January 03, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://developer.arm.com/support/security-update>\n * <https://developer.arm.com/-/media/Files/pdf/Cache_Speculation_Side-channels.pdf>\n\n### Addendum\n\n<https://lwn.net/Articles/740393/>\n\nIf you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:cert@cert.org?Subject=VU%23584653 Feedback>).\n\n### __ CentOS\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://lists.centos.org/pipermail/centos-announce/2018-January/date.html>\n\n### __ Cisco\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20180104-cpusidechannel>\n\n### __ Citrix\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://support.citrix.com/article/CTX231399>\n\n### __ Debian GNU/Linux\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://security-tracker.debian.org/tracker/CVE-2017-5754>\n\n### __ Dell\n\nUpdated: January 08, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <http://www.dell.com/support/contents/us/en/19/article/product-support/self-support-knowledgebase/software-and-downloads/support-for-meltdown-and-spectre>\n\n### __ DragonFly BSD Project\n\nUpdated: January 08, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <http://lists.dragonflybsd.org/pipermail/users/2018-January/313758.html>\n\n### __ Fedora Project\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://fedoramagazine.org/protect-fedora-system-meltdown/>\n\n### __ Fortinet, Inc.\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://fortiguard.com/psirt/FG-IR-18-002>\n\n### __ FreeBSD Project\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://www.freebsd.org/news/newsflash.html#event20180104:01>\n\n### __ Fujitsu\n\nUpdated: January 11, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <http://support.ts.fujitsu.com/content/SideChannelAnalysisMethod.asp?lng=EN>\n\n### __ Google\n\nUpdated: January 03, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://security.googleblog.com/2018/01/todays-cpu-vulnerability-what-you-need.html>\n * <https://support.google.com/faqs/answer/7622138>\n\n### __ Hewlett Packard Enterprise\n\nUpdated: January 08, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://www.hpe.com/us/en/services/security-vulnerability.html>\n\n### __ IBM Corporation\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://www.ibm.com/blogs/psirt/potential-cpu-security-issue/>\n\n### __ Intel\n\nUpdated: January 22, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://newsroom.intel.com/news/intel-responds-to-security-research-findings/>\n * <https://newsroom.intel.com/news-releases/intel-issues-updates-protect-systems-security-exploits>\n * <https://www.intel.com/content/www/us/en/architecture-and-technology/facts-about-side-channel-analysis-and-intel-products.html>\n * <https://newsroom.intel.com/news/root-cause-of-reboot-issue-identified-updated-guidance-for-customers-and-partners/>\n * <https://newsroom.intel.com/wp-content/uploads/sites/11/2018/01/microcode-update-guidance.pdf>\n\n### __ Lenovo\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://support.lenovo.com/us/en/solutions/len-18282>\n\n### __ Linux Kernel\n\nUpdated: January 04, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://lkml.org/lkml/2017/11/22/956>\n * <https://lkml.org/lkml/2018/1/4/174>\n * <https://lkml.org/lkml/2018/1/4/615>\n\n### __ Microsoft\n\nUpdated: January 11, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://support.microsoft.com/en-us/help/4073119/protect-against-speculative-execution-side-channel-vulnerabilities-in>\n * <https://support.microsoft.com/en-us/help/4072699/january-3-2018-windows-security-updates-and-antivirus-software>\n * <https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/CVE-2017-5715-and-hyper-v-vms>\n * <https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/ADV180002>\n * <https://blogs.windows.com/msedgedev/2018/01/03/speculative-execution-mitigations-microsoft-edge-internet-explorer/>\n * <https://azure.microsoft.com/en-us/blog/securing-azure-customers-from-cpu-vulnerability/>\n * <https://cloudblogs.microsoft.com/microsoftsecure/2018/01/09/understanding-the-performance-impact-of-spectre-and-meltdown-mitigations-on-windows-systems/>\n * <https://support.microsoft.com/en-us/help/4073707/windows-os-security-update-block-for-some-amd-based-devices>\n\n### Addendum\n\nNote that Windows systems without antivirus do not appear to receive the ADV180002 update automatically. In order to receive the update through Windows Update, run the following command:\n\n \n`reg add \"HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\QualityCompat\" /v cadca5fe-87d3-4b96-b7fb-a231484277cc /t REG_DWORD /d 0 /f` \nIf a third-party antivirus product does not explicitly indicate compatibility with to the protections provided by ADV180002 using the above registry value, the system will not automatically receive the ADV180002 update as well. \n \nOnce a system has the ADV180002 update installed, it must be manually activated using the following commands to make the appropriate registry changes: \n\n\n`reg add \"HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Control\\Session Manager\\Memory Management\" /v FeatureSettingsOverride /t REG_DWORD /d 0 /f` \n`reg add \"HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Control\\Session Manager\\Memory Management\" /v FeatureSettingsOverrideMask /t REG_DWORD /d 3 /f` \n`reg add \"HKLM\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Virtualization\" /v MinVmVersionForCpuBasedMitigations /t REG_SZ /d \"1.0\" /f ` \nAlso note that in addition to the above changes, ADV180002 requires CPU microcode updates to achieve full protection. In some cases, Windows Update may not automatically install the ADV180002 update. An unofficial spreadsheet of antivirus vendor compatibility with this update is maintained here: \n \nOn systems that have not received the ADV180002 update automatically, you may have to install the update manually. Please see for more details. \n \nTo verify that your Windows system has protections against Meltdown and Spectre variant 2, in a PowerShell session running with Administrator privileges, run:\n\n 1. `Install-Module SpeculationControl` \nIf this fails, you may need to install [PackageManagement PowerShell Modules](<https://www.microsoft.com/en-us/download/details.aspx?id=51451>)\n 2. `Get-SpeculationControlSettings` \nIf this fails, you may need to change your PowerShell ExecutionPolicy setting: ` \nSet-ExecutionPolicy RemoteSigned \n`Once you are satisfied with the PowerShell output, you can revert the ExecutionPolicy setting back to the default Restricted setting by running: \n`Set-ExecutionPolicy Restricted`\n` ` \nThe output of this PowerShell command will indicate the status of whether the CPU has the required microcode update, whether Windows has the required software update installed, and whether the mitigations are enabled. Any setting that indicates \"False\" is an indicator of incomplete protection from Meltdown and/or Spectre. \n \nFor example, a system that has the ADV180002 update properly installed and enabled, but is missing the CPU microcode update to fully enable the protections will show output like this: \n \n \nOnce the CPU microcode is updated on such a system (e.g. by way of a BIOS update) , the output will look like this, which indicates that the protections that Microsoft have released are fully enabled: \n \n \nIf the above PowerShell command indicates \"Windows OS support for PCID optimization is enabled: False\", this is a symptom of using a processor that doesn't support process context identifiers (PCID). Such processors cannot take advantage of the performance optimization that avoids a TLB flush. \n \nIf the above PowerShell command indicates \"Hardware requires kernel VA shadowing: False\", this is a symptom of using a processor that doesn't require mitigations for CVE-2017-5754 (Meltdown). \n \nAlso note that Microsoft has not yet provided protection for CVE-2017-5754 (Meltdown) on affected 32-bit platforms. \n\nIf you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:cert@cert.org?Subject=VU%23584653 Feedback>).\n\n### __ Mozilla\n\nUpdated: January 03, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://blog.mozilla.org/security/2018/01/03/mitigations-landing-new-class-timing-attack/>\n\n### __ NVIDIA\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <http://nvidia.custhelp.com/app/answers/detail/a_id/4609>\n * <http://nvidia.custhelp.com/app/answers/detail/a_id/4611>\n * <http://nvidia.custhelp.com/app/answers/detail/a_id/4613>\n * <http://nvidia.custhelp.com/app/answers/detail/a_id/4614>\n * <https://www.nvidia.com/en-us/product-security/>\n\n### __ NetBSD\n\nUpdated: January 08, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### __ OpenBSD\n\nUpdated: January 08, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * [https://marc.info/?l=openbsd-tech&m=151521435721902&w=2](<https://marc.info/?l=openbsd-tech&m=151521435721902&w=2>)\n\n### __ Oracle Corporation\n\nUpdated: February 23, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://www.theregister.co.uk/2018/01/16/oracle_quarterly_patches_jan_2018/>\n\n### __ QUALCOMM Incorporated\n\nUpdated: January 11, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Addendum\n\nThe Register has published the following: <https://www.theregister.co.uk/2018/01/06/qualcomm_processor_security_vulnerabilities/>\n\nIf you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:cert@cert.org?Subject=VU%23584653 Feedback>).\n\n### __ Red Hat, Inc.\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * [https://access.redhat.com/security/security-updates/#/security-advisories?q=&p=1&sort=portal_publication_date%20desc&rows=10&documentKind=PortalProduct](<https://access.redhat.com/security/security-updates/#/security-advisories?q=&p=1&sort=portal_publication_date%20desc&rows=10&documentKind=PortalProduct>)\n\n### __ SUSE Linux\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://www.suse.com/c/suse-addresses-meltdown-spectre-vulnerabilities/>\n * <http://lists.suse.com/pipermail/sle-security-updates/2018-January/date.html>\n\n### __ Synology\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://www.synology.com/en-global/support/security/Synology_SA_18_01>\n\n### __ Trend Micro\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://success.trendmicro.com/solution/1119183-important-information-for-trend-micro-solutions-and-microsoft-january-2018-security-updates>\n\n### __ Ubuntu\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/SpectreAndMeltdown>\n\n### __ VMware\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://www.vmware.com/security/advisories/VMSA-2018-0002.html>\n\n### __ Xen\n\nUpdated: January 24, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <http://xenbits.xen.org/xsa/advisory-254.html>\n * <https://blog.xenproject.org/2018/01/22/xen-project-spectre-meltdown-faq-jan-22-update/>\n\n### __ openSUSE project\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://lists.opensuse.org/opensuse-security-announce/2018-01/msg00001.html>\n\n### __ NetApp\n\nUpdated: January 08, 2018 \n\n### Status\n\n__ Not Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * [httpsecurity.netapp.com/advisory/ntap-20180104-0001/](<httpsecurity.netapp.com/advisory/ntap-20180104-0001/>)\n\n### __ Raspberry Pi\n\nUpdated: January 08, 2018 \n\n### Status\n\n__ Not Affected\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://www.raspberrypi.org/blog/why-raspberry-pi-isnt-vulnerable-to-spectre-or-meltdown/>\n\n### __ __ Technicolor\n\nUpdated: January 08, 2018 \n\n### Status\n\n__ Not Affected\n\n### Vendor Statement\n\nBoth Spectre and Meltdown attacks presupposed \u201copen platforms\u201d, where \nadditional code can be added by a non-privileged user. The Technicolor products \nare not open platforms. Even where 3rd party application can run in containers \nand can be managed via Life Cycle Management, these applications are validated \nand signed before they can be installed on the platform. Technicolor is \ncurrently working with its vendors to identify if additional layers of \nprotection are needed. Yet, as the current platforms are closed and have secure \nbootloading mechanism in place, there is no risk and no privilege acquired by \nan attacker in exploiting such an attack on Technicolor's devices.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### __ ASUSTeK Computer Inc.\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Unknown\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### __ Acer\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Unknown\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### __ F5 Networks, Inc.\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Unknown\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### Vendor References\n\n * <https://support.f5.com/csp/article/K91229003>\n\n### __ GIGABYTE\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Unknown\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### __ HP Inc.\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Unknown\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### __ Samsung Semiconductor Inc.\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Unknown\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\n### __ Toshiba Corporation\n\nUpdated: January 05, 2018 \n\n### Status\n\n__ Unknown\n\n### Vendor Statement\n\nNo statement is currently available from the vendor regarding this vulnerability.\n\n### Vendor Information\n\nWe are not aware of further vendor information regarding this vulnerability.\n\nView all 46 vendors __View less vendors __\n\n \n\n\n### CVSS Metrics \n\nGroup | Score | Vector \n---|---|--- \nBase | 4.4 | AV:L/AC:M/Au:S/C:C/I:N/A:N \nTemporal | 3.4 | E:POC/RL:OF/RC:C \nEnvironmental | 5.1 | CDP:ND/TD:H/CR:H/IR:ND/AR:ND \n \n \n\n\n### References \n\n * <https://vuls.cert.org/confluence/display/Wiki/Vulnerabilities+Associated+with+CPU+Speculative+Execution>\n * <https://meltdownattack.com/>\n * <https://meltdownattack.com/meltdown.pdf>\n * <https://spectreattack.com/>\n * <https://spectreattack.com/spectre.pdf>\n * <https://security.googleblog.com/2018/01/todays-cpu-vulnerability-what-you-need.html>\n * <https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html>\n * <https://cyber.wtf/2017/07/28/negative-result-reading-kernel-memory-from-user-mode/>\n * <https://github.com/IAIK/KAISER>\n * <https://gruss.cc/files/kaiser.pdf>\n * <https://gruss.cc/files/prefetch.pdf>\n * <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5aa90a84589282b87666f92b6c3c917c8080a9bf>\n * <https://lkml.org/lkml/2017/12/27/2>\n * <https://lkml.org/lkml/2018/1/4/615>\n * <https://lwn.net/Articles/741878/>\n * <https://lwn.net/Articles/737940/>\n * <https://lwn.net/Articles/742702/>\n * <http://pythonsweetness.tumblr.com/post/169166980422/the-mysterious-case-of-the-linux-page-table>\n * <https://nakedsecurity.sophos.com/2018/01/03/fckwit-aka-kaiser-aka-kpti-intel-cpu-flaw-needs-low-level-os-patches/>\n * <https://en.wikipedia.org/wiki/Kernel_page-table_isolation>\n * <https://chrisam.net/2018/01/04/speculative-execution-side-channel-vulnerabilities-vendor-published-info/>\n * <https://www.raspberrypi.org/blog/why-raspberry-pi-isnt-vulnerable-to-spectre-or-meltdown/>\n * <https://doublepulsar.com/important-information-about-microsoft-meltdown-cpu-security-fixes-antivirus-vendors-and-you-a852ba0292ec>\n * [https://docs.google.com/spreadsheets/d/184wcDt9I9TUNFFbsAVLpzAtckQxYiuirADzf3cL42FQ/htmlview?usp=sharing&sle=true](<https://docs.google.com/spreadsheets/d/184wcDt9I9TUNFFbsAVLpzAtckQxYiuirADzf3cL42FQ/htmlview?usp=sharing&sle=true>)\n * <https://github.com/iadgov/Spectre-and-Meltdown-Guidance>\n * <https://arxiv.org/abs/1802.03802>\n\n### Acknowledgements\n\nThese issues were researched and reported by researchers at Google Project Zero (Jann Horn) the Institute of Applied Information Processing and Communications (IAIK) at Graz University of Technology (Gruss et. al.), Paul Kocher, and Anders Fogh. \n\nThis document was written by Art Manion and Will Dormann. \n\n### Other Information\n\n**CVE IDs:** | [CVE-2017-5753, ](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5753>) [CVE-2017-5715, ](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5715>) [CVE-2017-5754](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5754>) \n---|--- \n**Date Public:** | 2018-01-03 \n**Date First Published:** | 2018-01-04 \n**Date Last Updated: ** | 2018-07-03 21:27 UTC \n**Document Revision: ** | 230 \n", "published": "2018-01-04T00:00:00", "modified": "2018-07-03T21:27:00", "cvss": {"score": 4.7, "vector": "AV:LOCAL/AC:MEDIUM/Au:NONE/C:COMPLETE/I:NONE/A:NONE/"}, "href": "https://www.kb.cert.org/vuls/id/584653", "reporter": "CERT", "references": ["https://vuls.cert.org/confluence/display/Wiki/Vulnerabilities+Associated+with+CPU+Speculative+Execution", "https://meltdownattack.com/", "https://meltdownattack.com/meltdown.pdf", "https://spectreattack.com/", "https://spectreattack.com/spectre.pdf", "https://security.googleblog.com/2018/01/todays-cpu-vulnerability-what-you-need.html", "https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html", "https://cyber.wtf/2017/07/28/negative-result-reading-kernel-memory-from-user-mode/", "https://github.com/IAIK/KAISER", "https://gruss.cc/files/kaiser.pdf", "https://gruss.cc/files/prefetch.pdf", "https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5aa90a84589282b87666f92b6c3c917c8080a9bf", "https://lkml.org/lkml/2017/12/27/2", "https://lkml.org/lkml/2018/1/4/615", "https://lwn.net/Articles/741878/", "https://lwn.net/Articles/737940/", "https://lwn.net/Articles/742702/", "http://pythonsweetness.tumblr.com/post/169166980422/the-mysterious-case-of-the-linux-page-table", "https://nakedsecurity.sophos.com/2018/01/03/fckwit-aka-kaiser-aka-kpti-intel-cpu-flaw-needs-low-level-os-patches/", "https://en.wikipedia.org/wiki/Kernel_page-table_isolation", "https://chrisam.net/2018/01/04/speculative-execution-side-channel-vulnerabilities-vendor-published-info/", "https://www.raspberrypi.org/blog/why-raspberry-pi-isnt-vulnerable-to-spectre-or-meltdown/", "https://doublepulsar.com/important-information-about-microsoft-meltdown-cpu-security-fixes-antivirus-vendors-and-you-a852ba0292ec", "https://docs.google.com/spreadsheets/d/184wcDt9I9TUNFFbsAVLpzAtckQxYiuirADzf3cL42FQ/htmlview?usp=sharing&sle=true", "https://github.com/iadgov/Spectre-and-Meltdown-Guidance", "https://arxiv.org/abs/1802.03802"], "cvelist": ["CVE-2017-5715", "CVE-2017-5753", "CVE-2017-5754"], "lastseen": "2019-05-22T16:51:54", "history": [], "viewCount": 915, "enchantments": {"score": {"value": 7.2, "vector": "NONE"}, "dependencies": {"references": [{"type": "f5", "idList": ["F5:K91229003"]}, {"type": "symantec", "idList": ["SMNTC-102371", "SMNTC-102378"]}, {"type": "cve", "idList": ["CVE-2017-5753", "CVE-2017-5754", "CVE-2017-5715"]}, {"type": "openvas", "idList": ["OPENVAS:1361412562310843429", "OPENVAS:1361412562310843423", "OPENVAS:1361412562310812397", "OPENVAS:1361412562310882822", "OPENVAS:1361412562310843474", "OPENVAS:1361412562310843405", "OPENVAS:1361412562310812740", "OPENVAS:1361412562310843424", "OPENVAS:1361412562310882855", "OPENVAS:1361412562310812398"]}, {"type": "nessus", "idList": ["AIX_IJ03030.NASL", "REDHAT-RHSA-2018-0016.NASL", "REDHAT-RHSA-2018-0017.NASL", "AIX_IJ03035.NASL", "ORACLEVM_OVMSA-2018-0029.NASL", "SUSE_SU-2018-0069-1.NASL", "UBUNTU_USN-3597-1.NASL", "SL_20180313_KERNEL_ON_SL6_X.NASL", "REDHAT-RHSA-2018-0018.NASL", "ORACLELINUX_ELSA-2018-0008.NASL"]}, {"type": "ubuntu", "idList": ["USN-3597-2", "USN-3516-1", "USN-3541-2", "USN-3540-2"]}, {"type": "redhat", "idList": ["RHSA-2018:0047", "RHSA-2018:0496", "RHSA-2018:0045", "RHSA-2018:0010", "RHSA-2018:0018", "RHSA-2018:0182", "RHSA-2018:0009", "RHSA-2018:0044", "RHSA-2018:0016", "RHSA-2018:0089"]}, {"type": "suse", "idList": ["SUSE-SU-2018:0171-1", "SUSE-SU-2018:0113-1", "SUSE-SU-2018:0114-1"]}, {"type": "centos", "idList": ["CESA-2018:0008", "CESA-2018:0512", "CESA-2018:0007"]}, {"type": "securelist", "idList": ["SECURELIST:7CF4DDEB1B5407DAA24EC25BAA7A9654"]}, {"type": "qualysblog", "idList": ["QUALYSBLOG:F8AA5B21D90BCDD30391A24D6FD47892", "QUALYSBLOG:D893D4DFB7141FDAD0BE869440074392"]}, {"type": "cisco", "idList": ["CISCO-SA-20180104-CPUSIDECHANNEL"]}, {"type": "talosblog", "idList": ["TALOSBLOG:6AF8BBB020A686E442B50095CA9B7A36"]}, {"type": "huawei", "idList": ["HUAWEI-SA-20180106-01-CPU"]}, {"type": "paloalto", "idList": ["PAN-SA-2018-0001"]}, {"type": "thn", "idList": ["THN:788E9312DDA39D9A09855DF379A0FD4D"]}, {"type": "kitploit", "idList": ["KITPLOIT:8752367943592764867"]}, {"type": "oraclelinux", "idList": ["ELSA-2018-0007"]}, {"type": "malwarebytes", "idList": ["MALWAREBYTES:3DDE32E41BE8356C194673EE3ED7FDBE", "MALWAREBYTES:C47D8F4321BF60FB315B6C46B47DF46F"]}, {"type": "xen", "idList": ["XSA-254"]}, {"type": "threatpost", "idList": ["THREATPOST:DB0542CFA474B0D9C91032709EDE296D"]}, {"type": "vmware", "idList": ["VMSA-2018-0007"]}], "modified": "2019-05-22T16:51:54"}}, "objectVersion": "1.4"}, "lastseen": "2019-05-22T16:51:54", "differentElements": ["cvss"], "edition": 27}], "viewCount": 932, "enchantments": {"score": {"value": 7.6, "vector": "NONE", "modified": "2019-05-29T20:42:04"}, "dependencies": {"references": [{"type": "f5", "idList": ["F5:K91229003"]}, {"type": "symantec", "idList": ["SMNTC-102371", "SMNTC-102378"]}, {"type": "cve", "idList": ["CVE-2017-5753", "CVE-2017-5754", "CVE-2017-5715"]}, {"type": "nessus", "idList": ["AIX_IJ03035.NASL", "AIX_IJ03036.NASL", "REDHAT-RHSA-2018-0016.NASL", "REDHAT-RHSA-2018-0011.NASL", "REDHAT-RHSA-2018-0017.NASL", "XEN_SERVER_XSA-254.NASL", "SL_20180313_KERNEL_ON_SL6_X.NASL", "SUSE_SU-2018-0069-1.NASL", "REDHAT-RHSA-2018-0018.NASL", "UBUNTU_USN-3516-1.NASL"]}, {"type": "redhat", "idList": ["RHSA-2018:0045", "RHSA-2018:0496", "RHSA-2018:0010", "RHSA-2018:0047", "RHSA-2018:0008", "RHSA-2018:0007", "RHSA-2018:0020", "RHSA-2018:0011", "RHSA-2018:0091", "RHSA-2018:0092"]}, {"type": "securelist", "idList": ["SECURELIST:7CF4DDEB1B5407DAA24EC25BAA7A9654"]}, {"type": "centos", "idList": ["CESA-2018:0008"]}, {"type": "qualysblog", "idList": ["QUALYSBLOG:F8AA5B21D90BCDD30391A24D6FD47892", "QUALYSBLOG:BD020D07BF02B0790C62701D997BFD4D", "QUALYSBLOG:C9F2432F760D960CF69CDC55D87263A8", "QUALYSBLOG:3ACE52E54FF5FE3EF1B0FC328181FA66", "QUALYSBLOG:F7C32BA5E6651A8CE3584BB84A88A0C0"]}, {"type": "openvas", "idList": ["OPENVAS:1361412562310882822", "OPENVAS:1361412562310843423", "OPENVAS:1361412562310843429", "OPENVAS:1361412562310812397", "OPENVAS:1361412562310812295", "OPENVAS:1361412562310812296", "OPENVAS:1361412562310843427", "OPENVAS:1361412562310843473"]}, {"type": "suse", "idList": ["SUSE-SU-2018:0171-1", "SUSE-SU-2018:0131-1", "SUSE-SU-2018:0069-1"]}, {"type": "ubuntu", "idList": ["USN-3597-2", "USN-3540-1", "USN-3541-1", "USN-3597-1"]}, {"type": "threatpost", "idList": ["THREATPOST:DB0542CFA474B0D9C91032709EDE296D", "THREATPOST:0F9EDE9A622A021B9B79C50214D7E8AD"]}, {"type": "vmware", "idList": ["VMSA-2018-0007"]}, {"type": "oraclelinux", "idList": ["ELSA-2018-4012"]}, {"type": "cloudfoundry", "idList": ["CFOUNDRY:86B5C35F8F0E334D1CCCDAF1214EDFEF"]}, {"type": "lenovo", "idList": ["LENOVO:PS500151-NOSID"]}, {"type": "thn", "idList": ["THN:58CFE19533148E77597FE0AC59963145"]}, {"type": "seebug", "idList": ["SSV:97059"]}], "modified": "2019-05-29T20:42:04"}, "vulnersScore": 7.6}, "objectVersion": "1.4", "_object_type": "robots.models.cert.CertBulletin", "_object_types": ["robots.models.base.Bulletin", "robots.models.cert.CertBulletin"]}
{"f5": [{"lastseen": "2019-09-22T17:51:25", "bulletinFamily": "software", "description": "\nF5 Product Development has assigned IDs 698651, 701445, 701447, 704490, and 704483 (BIG-IP); 702233, 702236, and 702237 (BIG-IQ); 702353, 702354, and 702355 (Enterprise Manager); 702355, 702377, and 702378 (iWorkflow); CPF-24782, CPF-24783, and CPF-24784 (Traffix); LRS-65859, LRS-65860, and LRS-65861 (LineRate) to this vulnerability. Additionally, [BIG-IP iHealth](<https://www.f5.com/support/support-tools/big-ip-ihealth>) may list Heuristic H91229003 on the **Diagnostics** > **Identified** > **Medium** page.\n\nTo determine if your product and version have been evaluated for this vulnerability, refer to the **Applies to (see versions)** box. To determine if your release is known to be vulnerable, the components or features that are affected by the vulnerability, and for information about releases or hotfixes that address the vulnerability, refer to the following table.\n\nProduct | Branch | Versions known to be vulnerable | Fixes introduced in | Severity | CVSSv3 score1 | Vulnerable component or feature \n---|---|---|---|---|---|--- \nBIG-IP (LTM, AAM, AFM, Analytics, APM, ASM, DNS, Edge Gateway, GTM, Link Controller, PEM, WebAccelerator, WebSafe) | 15.x | None | 15.0.0 | Medium (CVE-2017-5715) \nMedium (CVE-2017-5753) \nMedium (CVE-2017-5754) | [6.4](<https://www.first.org/cvss/calculator/3.0#CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N/E:F/RL:U/RC:C>) CVE-2017-5715 \n[5.3](<https://www.first.org/cvss/calculator/3.0#CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N/E:P/RL:U/RC:C>) CVE-2017-5753 \n[6.4](<https://www.first.org/cvss/calculator/3.0#CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N/E:F/RL:U/RC:C>) CVE-2017-5754 | CPU, BIOS, and kernel \n14.x | None | 14.0.02 \n13.x | 13.0.0 - 13.1.0 | 13.1.0.42 \n13.0.12 \n12.x | 12.1.0 - 12.1.3 | 12.1.3.32 \n11.x | 11.6.1 - 11.6.3 \n11.5.1 - 11.5.5 \n11.2.1 | 11.6.3.12 \n11.5.62 \nEnterprise Manager | 3.x | 3.1.1 | None | Medium (CVE-2017-5715) \nMedium (CVE-2017-5753) \nMedium (CVE-2017-5754) | [6.4](<https://www.first.org/cvss/calculator/3.0#CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N/E:F/RL:U/RC:C>) CVE-2017-5715 \n[5.3](<https://www.first.org/cvss/calculator/3.0#CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N/E:P/RL:U/RC:C>) CVE-2017-5753 \n[6.4](<https://www.first.org/cvss/calculator/3.0#CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N/E:F/RL:U/RC:C>) CVE-2017-5754 | CPU, BIOS, and kernel \nBIG-IQ (Cloud, Device, Security, ADC) | 4.x | 4.5.0 | None | Medium (CVE-2017-5715) \nMedium (CVE-2017-5753) \nMedium (CVE-2017-5754) | [6.4](<https://www.first.org/cvss/calculator/3.0#CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N/E:F/RL:U/RC:C>) CVE-2017-5715 \n[5.3](<https://www.first.org/cvss/calculator/3.0#CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N/E:P/RL:U/RC:C>) CVE-2017-5753 \n[6.4](<https://www.first.org/cvss/calculator/3.0#CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N/E:F/RL:U/RC:C>) CVE-2017-5754 | CPU, BIOS, and kernel \nBIG-IQ Centralized Management | 6.x | 6.0.0 | 6.0.12 | Medium (CVE-2017-5715) \nMedium (CVE-2017-5753) \nMedium (CVE-2017-5754) | [6.4](<https://www.first.org/cvss/calculator/3.0#CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N/E:F/RL:U/RC:C>) CVE-2017-5715 \n[5.3](<https://www.first.org/cvss/calculator/3.0#CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N/E:P/RL:U/RC:C>) CVE-2017-5753 \n[6.4](<https://www.first.org/cvss/calculator/3.0#CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N/E:F/RL:U/RC:C>) CVE-2017-5754 | CPU, BIOS, and kernel \n5.x | 5.0.0 - 5.4.0 | None \n4.x | 4.6.0 | None \nBIG-IQ Cloud and Orchestration | 1.x | 1.0.0 | None | Medium (CVE-2017-5715) \nMedium (CVE-2017-5753) \nMedium (CVE-2017-5754) | [6.4](<https://www.first.org/cvss/calculator/3.0#CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N/E:F/RL:U/RC:C>) CVE-2017-5715 \n[5.3](<https://www.first.org/cvss/calculator/3.0#CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N/E:P/RL:U/RC:C>) CVE-2017-5753 \n[6.4](<https://www.first.org/cvss/calculator/3.0#CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N/E:F/RL:U/RC:C>) CVE-2017-5754 | CPU, BIOS, and kernel \nF5 iWorkflow | 2.x | 2.3.0 \n2.2.0 \n2.1.0 \n2.0.1 - 2.0.2 | None | Medium (CVE-2017-5715) \nMedium (CVE-2017-5753) \nMedium (CVE-2017-5754) | [6.4](<https://www.first.org/cvss/calculator/3.0#CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N/E:F/RL:U/RC:C>) CVE-2017-5715 \n[5.3](<https://www.first.org/cvss/calculator/3.0#CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N/E:P/RL:U/RC:C>) CVE-2017-5753 \n[6.4](<https://www.first.org/cvss/calculator/3.0#CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N/E:F/RL:U/RC:C>) CVE-2017-5754 | CPU, BIOS, and kernel \nLineRate | 2.x | 2.6.0 | None | Medium | ** | CPU, BIOS, and kernel \nTraffix SDC | 5.x | 5.0.0 - 5.1.0 | Security bulletin build 93 (5.1.0) \nSecurity bulletin build 32 (5.0.0) | Medium (CVE-2017-5715) \nHigh (CVE-2017-5753) \nHigh (CVE-2017-5754) | [6.7](<https://www.first.org/cvss/calculator/3.0#CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:L/A:N>) (CVE-2017-5715) \n[8.2](<https://www.first.org/cvss/calculator/3.0#CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N>) (CVE-2017-5753) \n[7.9](<https://www.first.org/cvss/calculator/3.0#CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N>) (CVE-2017-5754) | CPU, BIOS, and kernel \n4.x | 4.0.0 - 4.4.0 | Security bulletin build 14 (4.4.0) \n \n1The CVSSv3 score link takes you to a resource outside of AskF5, and it is possible that the document may be removed without our knowledge.\n\n2Notes about fixes for CVE-2017-5753 (Spectre-PHT) and CVE-2017-5754 (Meltdown-US):\n\n**Important**: F5 does not plan to release an official fix for CVE-2017-5715 (Spectre-BTB) that is based on Intel's microcode updates. The rationale for this decision is based on significant performance degradation when enabling Intel's microcode fixes in our platforms. During testing of the microcode fix, F5 has observed from 10 percent to more than 50 percent performance degradation for many workloads.\n\n**Important**: Only CVE-2017-5754 (Meltdown-US) is fixed in BIG-IQ.\n\n * Performance impact: \n * CVE-2017-5753 (Spectre-PHT)\n\nF5 does not anticipate a performance impact as a result of the fix for CVE-2017-5753 Spectre-PHT.\n\n * CVE-2017-5754 (Meltdown-US)\n\nIn most scenarios, the fix for Meltdown-US has a negligible performance impact. F5 recommends testing the performance impact before deploying the fix in a production environment, or testing the fix during a maintenance window with consideration to the possible impact on your specific environment. If you encounter unacceptable performance issues in testing and choose to disable the Meltdown-US fix, you can do so by typing the following command:\n\ntmsh modify sys db kernel.pti value disable\n\n**Note:** This database variable change is applied without requirement for a reboot.\n\n**Important:** If you choose to disable the Meltdown-US fix, the system will be vulnerable to the Meltdown-US vulnerability. However, in order to take advantage of this vulnerability, the attacker must already possess the ability to run arbitrary code on the system. For non-vCMP systems, good access controls and keeping your system up-to-date with security fixes will mitigate this risk. For vCMP systems with multiple tenants, F5 recommends that you leave the Meltdown-US fix enabled.\n\n * Virtual F5 products/vCMP guests:\n\nThe Meltdown-US and Spectre-PHT fixes block the ability for those exploits to be executed on the patched OS. If the exploit allows cross-VM boundary information leaks, then a fixed VM is still vulnerable to attacks from a non-fixed VM or the host. Therefore, it is important to apply fixes to both guest VMs and the host that runs them.\n\n * Known issues:\n\nDue to a known issue with the Meltdown-US fix on BIG-IP platforms equipped with an AMD processor, the system may spontaneously reboot. Refer to the table in the **Impact** section for information about which BIG-IP platforms have an AMD processor. F5 Product Development has assigned ID 719711 to this issue. To work around the issue, you can disable the Meltdown-US fix (BIG-IP platforms with an AMD processor are not vulnerable to Meltdown-US per the table in the** Impact** section). To do so, perform the following procedure:\n\n**Note**: Performing the procedure to disable kernel page-table isolation does not disable the Spectre-PHT fix.\n\n 1. Log in to the BIG-IP command line.\n 2. Disable the kernel page-table isolation (PTI) database key by typing the following command: \n\ntmsh modify sys db kernel.pti value disable\n\n 3. Reboot the BIG-IP system by typing the following command: \n\nreboot\n\n**Note**: A reboot is required for this workaround.\n\n**Important**: This command will interrupt traffic while the BIG-IP system either fails over to a peer system or completes the reboot process. \n\nIf you are running a version listed in the **Versions known to be vulnerable** column, you can eliminate this vulnerability by upgrading to a version listed in the **Fixes introduced in** column. If the table lists only an older version than what you are currently running, or does not list a non-vulnerable version, then no upgrade candidate currently exists.\n\nMitigation\n\nBIG-IP\n\nThe only roles on a BIG-IP system that can exploit these vulnerabilities are the Administrator, Resource Administrator, Manager, and iRules Manager roles. To mitigate against all three vulnerabilities, ensure that you limit access to these roles to only trusted employees.\n\nTo mitigate the Spectre-BTB vulnerability in multi-tenancy vCMP configurations, ensure that all guests are set to at least two **Cores Per Guest**.\n\nTraffix SDC\n\nFixes for CVE-2017-5715, CVE-2017-5753, and CVE-2017-5754 are available from F5 via the following security bulletins for Traffix SDC 5.1.0, 5.0.0, and 4.4.0:\n\n * **5.1.0** \\- security bulletin build 93\n * **5.0.0** \\- security bulletin build 32\n * **4.4.0** \\- security bulletin build 14\n\nFor more information, contact your Traffix SDC Technical Support representative.\n\n * <https://googleprojectzero.blogspot.ca/2018/01/reading-privileged-memory-with-side.html>\n\n**Note**: This link takes you to a resource outside of AskF5. The third party could remove the document without our knowledge.\n\n * <https://meltdownattack.com/>\n\n**Note**: This link takes you to a resource outside of AskF5. The third party could remove the document without our knowledge.\n\n * [K51812227: Understanding Security Advisory versioning](<https://support.f5.com/csp/article/K51812227>)\n * [K9970: Subscribing to email notifications regarding F5 products](<https://support.f5.com/csp/article/K9970>)\n * [K9957: Creating a custom RSS feed to view new and updated documents](<https://support.f5.com/csp/article/K9957>)\n * [K4602: Overview of the F5 security vulnerability response policy](<https://support.f5.com/csp/article/K4602>)\n * [K4918: Overview of the F5 critical issue hotfix policy](<https://support.f5.com/csp/article/K4918>)\n * [K9502: BIG-IP hotfix and point release matrix](<https://support.f5.com/csp/article/K9502>)\n", "modified": "2019-05-28T22:51:00", "published": "2018-01-04T04:46:00", "id": "F5:K91229003", "href": "https://support.f5.com/csp/article/K91229003", "title": "Side-channel processor vulnerabilities CVE-2017-5715, CVE-2017-5753, and CVE-2017-5754", "type": "f5", "cvss": {"score": 4.7, "vector": "AV:L/AC:M/Au:N/C:C/I:N/A:N"}}], "symantec": [{"lastseen": "2018-03-11T18:48:46", "bulletinFamily": "software", "description": "### Description\n\nMultiple CPU Hardware are prone to an information-disclosure vulnerability. Attackers can exploit this issue to obtain sensitive information that may aid in further attacks.\n\n### Technologies Affected\n\n * Apple Mac Os X 10.11.6 \n * Apple iOS 11.2 \n * Apple macOS 10.12.6 \n * Apple macOS 10.13.2 \n * Apple tvOS 11.2 \n * BD Accuri C6 Plus \n * BD Assurity Linc \n * BD BACTEC 9120/9240 \n * BD BACTEC FX \n * BD BACTEC FX40 \n * BD Data Innovations \n * BD EpiCenter \n * BD FACSAria Fusion \n * BD FACSAria I/II/III \n * BD FACSCalibur \n * BD FACSCanto 10-color \n * BD FACSCanto 10-color clinical \n * BD FACSCanto II \n * BD FACSCanto II clinical \n * BD FACSCelesta \n * BD FACSCount \n * BD FACSDuet Sample Prep (ASaP) \n * BD FACSJazz \n * BD FACSLink Interface \n * BD FACSLyric \n * BD FACSMelody \n * BD FACSSample Prep Assistant III \n * BD FACSVerse \n * BD FACSVia \n * BD GenCell CliC \n * BD Influx \n * BD Kiestra TLA/WCA \n * BD LSR II \n * BD LSRFortessa \n * BD LSRFortessa X-20 \n * BD Lyse Wash Assistant \n * BD MAX \n * BD Panel Designer \n * BD Phoenix 100 \n * BD Phoenix M50 \n * BD Pyxis Anesthesia ES \n * BD Pyxis Anesthesia System 3500 \n * BD Pyxis CIISafe -Workstation \n * BD Pyxis CUBIE Replenishment Station \n * BD Pyxis CathRack \n * BD Pyxis DuoStation \n * BD Pyxis EcoStation System \n * BD Pyxis Infant Care Verification \n * BD Pyxis MedStation 3500 \n * BD Pyxis MedStation 4000 \n * BD Pyxis MedStation ES \n * BD Pyxis Medication Administration \n * BD Pyxis Nursing Data Collection \n * BD Pyxis ParAssist System \n * BD Pyxis Parx \n * BD Pyxis Parx handheld \n * BD Pyxis ProcedureStation \n * BD Pyxis ScrubStation System \n * BD Pyxis Specimen Collection Verification \n * BD Pyxis StockStation System \n * BD Pyxis Supply Roller \n * BD Pyxis SupplyStation \n * BD Pyxis Transfusion Verification \n * BD Rowa Dose \n * BD Rowa Smart \n * BD Rowa Vmax System \n * BD Totalys SlidePrep \n * BD Viper LT \n * BD Viper XTR \n * Bluecoat Content Analysis 2.1 \n * Bluecoat Content Analysis 2.2 \n * Bluecoat Malware Analysis Appliance 4.2 \n * Bluecoat Security Analytics 7.1 \n * Bluecoat Security Analytics 7.2 \n * Bluecoat Security Analytics 7.3 \n * Bluecoat X-Series XOS 10.0 \n * Bluecoat X-Series XOS 11.0 \n * Bluecoat X-Series XOS 9.7 \n * Cisco Carrier Routing System 6.6.0.BASE \n * Cisco Unified Computing System 2.2 \n * Cisco Unified Computing System 3.1 \n * Cisco Unified Computing System 3.2 \n * Google Android \n * Google Chrome 0.1.38.1 \n * Google Chrome 0.1.38.2 \n * Google Chrome 0.1.38.4 \n * Google Chrome 0.1.40.1 \n * Google Chrome 0.1.42.2 \n * Google Chrome 0.1.42.3 \n * Google Chrome 0.2.149.27 \n * Google Chrome 0.2.149.29 \n * Google Chrome 0.2.149.30 \n * Google Chrome 0.2.152.1 \n * Google Chrome 0.2.153.1 \n * Google Chrome 0.3.154 9 \n * Google Chrome 0.3.154.0 \n * Google Chrome 0.3.154.3 \n * Google Chrome 0.4.154.18 \n * Google Chrome 0.4.154.22 \n * Google Chrome 0.4.154.31 \n * Google Chrome 0.4.154.33 \n * Google Chrome 1.0.154.36 \n * Google Chrome 1.0.154.39 \n * Google Chrome 1.0.154.42 \n * Google Chrome 1.0.154.43 \n * Google Chrome 1.0.154.46 \n * Google Chrome 1.0.154.48 \n * Google Chrome 1.0.154.52 \n * Google Chrome 1.0.154.53 \n * Google Chrome 1.0.154.55 \n * Google Chrome 1.0.154.59 \n * Google Chrome 1.0.154.61 \n * Google Chrome 1.0.154.64 \n * Google Chrome 1.0.154.65 \n * Google Chrome 10 \n * Google Chrome 10.0.601.0 \n * Google Chrome 10.0.602.0 \n * Google Chrome 10.0.603.0 \n * Google Chrome 10.0.603.2 \n * Google Chrome 10.0.603.3 \n * Google Chrome 10.0.604.0 \n * Google Chrome 10.0.605.0 \n * Google Chrome 10.0.606.0 \n * Google Chrome 10.0.607.0 \n * Google Chrome 10.0.608.0 \n * Google Chrome 10.0.609.0 \n * Google Chrome 10.0.610.0 \n * Google Chrome 10.0.611.0 \n * Google Chrome 10.0.611.1 \n * Google Chrome 10.0.612.0 \n * Google Chrome 10.0.612.1 \n * Google Chrome 10.0.612.2 \n * Google Chrome 10.0.612.3 \n * Google Chrome 10.0.613.0 \n * Google Chrome 10.0.614.0 \n * Google Chrome 10.0.615.0 \n * Google Chrome 10.0.616.0 \n * Google Chrome 10.0.617.0 \n * Google Chrome 10.0.618.0 \n * Google Chrome 10.0.619.0 \n * Google Chrome 10.0.620.0 \n * Google Chrome 10.0.621.0 \n * Google Chrome 10.0.622.0 \n * Google Chrome 10.0.622.1 \n * Google Chrome 10.0.623.0 \n * Google Chrome 10.0.624.0 \n * Google Chrome 10.0.625.0 \n * Google Chrome 10.0.626.0 \n * Google Chrome 10.0.627.0 \n * Google Chrome 10.0.628.0 \n * Google Chrome 10.0.629.0 \n * Google Chrome 10.0.630.0 \n * Google Chrome 10.0.631.0 \n * Google Chrome 10.0.632.0 \n * Google Chrome 10.0.633.0 \n * Google Chrome 10.0.634.0 \n * Google Chrome 10.0.634.1 \n * Google Chrome 10.0.635.0 \n * Google Chrome 10.0.636.0 \n * Google Chrome 10.0.638.0 \n * Google Chrome 10.0.638.1 \n * Google Chrome 10.0.639.0 \n * Google Chrome 10.0.640.0 \n * Google Chrome 10.0.642.0 \n * Google Chrome 10.0.642.1 \n * Google Chrome 10.0.642.2 \n * Google Chrome 10.0.643.0 \n * Google Chrome 10.0.644.0 \n * Google Chrome 10.0.645.0 \n * Google Chrome 10.0.646.0 \n * Google Chrome 10.0.647.0 \n * Google Chrome 10.0.648.0 \n * Google Chrome 10.0.648.1 \n * Google Chrome 10.0.648.10 \n * Google Chrome 10.0.648.101 \n * Google Chrome 10.0.648.103 \n * Google Chrome 10.0.648.105 \n * Google Chrome 10.0.648.107 \n * Google Chrome 10.0.648.11 \n * Google Chrome 10.0.648.114 \n * Google Chrome 10.0.648.116 \n * Google Chrome 10.0.648.118 \n * Google Chrome 10.0.648.119 \n * Google Chrome 10.0.648.12 \n * Google Chrome 10.0.648.120 \n * Google Chrome 10.0.648.121 \n * Google Chrome 10.0.648.122 \n * Google Chrome 10.0.648.123 \n * Google Chrome 10.0.648.124 \n * Google Chrome 10.0.648.125 \n * Google Chrome 10.0.648.126 \n * Google Chrome 10.0.648.127 \n * Google Chrome 10.0.648.128 \n * Google Chrome 10.0.648.129 \n * Google Chrome 10.0.648.13 \n * Google Chrome 10.0.648.130 \n * Google Chrome 10.0.648.131 \n * Google Chrome 10.0.648.132 \n * Google Chrome 10.0.648.133 \n * Google Chrome 10.0.648.134 \n * Google Chrome 10.0.648.135 \n * Google Chrome 10.0.648.151 \n * Google Chrome 10.0.648.18 \n * Google Chrome 10.0.648.2 \n * Google Chrome 10.0.648.201 \n * Google Chrome 10.0.648.203 \n * Google Chrome 10.0.648.204 \n * Google Chrome 10.0.648.205 \n * Google Chrome 10.0.648.23 \n * Google Chrome 10.0.648.26 \n * Google Chrome 10.0.648.28 \n * Google Chrome 10.0.648.3 \n * Google Chrome 10.0.648.32 \n * Google Chrome 10.0.648.35 \n * Google Chrome 10.0.648.38 \n * Google Chrome 10.0.648.4 \n * Google Chrome 10.0.648.42 \n * Google Chrome 10.0.648.45 \n * Google Chrome 10.0.648.49 \n * Google Chrome 10.0.648.5 \n * Google Chrome 10.0.648.54 \n * Google Chrome 10.0.648.56 \n * Google Chrome 10.0.648.59 \n * Google Chrome 10.0.648.6 \n * Google Chrome 10.0.648.62 \n * Google Chrome 10.0.648.66 \n * Google Chrome 10.0.648.68 \n * Google Chrome 10.0.648.7 \n * Google Chrome 10.0.648.70 \n * Google Chrome 10.0.648.72 \n * Google Chrome 10.0.648.76 \n * Google Chrome 10.0.648.79 \n * Google Chrome 10.0.648.8 \n * Google Chrome 10.0.648.82 \n * Google Chrome 10.0.648.84 \n * Google Chrome 10.0.648.87 \n * Google Chrome 10.0.648.9 \n * Google Chrome 10.0.648.90 \n * Google Chrome 10.0.649.0 \n * Google Chrome 10.0.650.0 \n * Google Chrome 10.0.651.0 \n * Google Chrome 11 \n * Google Chrome 11.0.652.0 \n * Google Chrome 11.0.653.0 \n * Google Chrome 11.0.654.0 \n * Google Chrome 11.0.655.0 \n * Google Chrome 11.0.656.0 \n * Google Chrome 11.0.657.0 \n * Google Chrome 11.0.658.0 \n * Google Chrome 11.0.658.1 \n * Google Chrome 11.0.659.0 \n * Google Chrome 11.0.660.0 \n * Google Chrome 11.0.661.0 \n * Google Chrome 11.0.662.0 \n * Google Chrome 11.0.663.0 \n * Google Chrome 11.0.664.1 \n * Google Chrome 11.0.665.0 \n * Google Chrome 11.0.666.0 \n * Google Chrome 11.0.667.0 \n * Google Chrome 11.0.667.2 \n * Google Chrome 11.0.667.3 \n * Google Chrome 11.0.667.4 \n * Google Chrome 11.0.668.0 \n * Google Chrome 11.0.669.0 \n * Google Chrome 11.0.670.0 \n * Google Chrome 11.0.671.0 \n * Google Chrome 11.0.672.0 \n * Google Chrome 11.0.672.1 \n * Google Chrome 11.0.672.2 \n * Google Chrome 11.0.673.0 \n * Google Chrome 11.0.674.0 \n * Google Chrome 11.0.675.0 \n * Google Chrome 11.0.676.0 \n * Google Chrome 11.0.677.0 \n * Google Chrome 11.0.678.0 \n * Google Chrome 11.0.679.0 \n * Google Chrome 11.0.680.0 \n * Google Chrome 11.0.681.0 \n * Google Chrome 11.0.682.0 \n * Google Chrome 11.0.683.0 \n * Google Chrome 11.0.684.0 \n * Google Chrome 11.0.685.0 \n * Google Chrome 11.0.686.0 \n * Google Chrome 11.0.686.1 \n * Google Chrome 11.0.686.2 \n * Google Chrome 11.0.686.3 \n * Google Chrome 11.0.687.0 \n * Google Chrome 11.0.687.1 \n * Google Chrome 11.0.688.0 \n * Google Chrome 11.0.689.0 \n * Google Chrome 11.0.690.0 \n * Google Chrome 11.0.690.1 \n * Google Chrome 11.0.691.0 \n * Google Chrome 11.0.692.0 \n * Google Chrome 11.0.693.0 \n * Google Chrome 11.0.694.0 \n * Google Chrome 11.0.695.0 \n * Google Chrome 11.0.696.0 \n * Google Chrome 11.0.696.1 \n * Google Chrome 11.0.696.10 \n * Google Chrome 11.0.696.11 \n * Google Chrome 11.0.696.12 \n * Google Chrome 11.0.696.13 \n * Google Chrome 11.0.696.14 \n * Google Chrome 11.0.696.15 \n * Google Chrome 11.0.696.16 \n * Google Chrome 11.0.696.17 \n * Google Chrome 11.0.696.18 \n * Google Chrome 11.0.696.19 \n * Google Chrome 11.0.696.2 \n * Google Chrome 11.0.696.20 \n * Google Chrome 11.0.696.21 \n * Google Chrome 11.0.696.22 \n * Google Chrome 11.0.696.23 \n * Google Chrome 11.0.696.24 \n * Google Chrome 11.0.696.25 \n * Google Chrome 11.0.696.26 \n * Google Chrome 11.0.696.27 \n * Google Chrome 11.0.696.28 \n * Google Chrome 11.0.696.29 \n * Google Chrome 11.0.696.3 \n * Google Chrome 11.0.696.30 \n * Google Chrome 11.0.696.31 \n * Google Chrome 11.0.696.32 \n * Google Chrome 11.0.696.33 \n * Google Chrome 11.0.696.34 \n * Google Chrome 11.0.696.35 \n * Google Chrome 11.0.696.36 \n * Google Chrome 11.0.696.37 \n * Google Chrome 11.0.696.38 \n * Google Chrome 11.0.696.39 \n * Google Chrome 11.0.696.4 \n * Google Chrome 11.0.696.40 \n * Google Chrome 11.0.696.41 \n * Google Chrome 11.0.696.42 \n * Google Chrome 11.0.696.43 \n * Google Chrome 11.0.696.44 \n * Google Chrome 11.0.696.45 \n * Google Chrome 11.0.696.46 \n * Google Chrome 11.0.696.47 \n * Google Chrome 11.0.696.48 \n * Google Chrome 11.0.696.49 \n * Google Chrome 11.0.696.5 \n * Google Chrome 11.0.696.50 \n * Google Chrome 11.0.696.51 \n * Google Chrome 11.0.696.52 \n * Google Chrome 11.0.696.53 \n * Google Chrome 11.0.696.54 \n * Google Chrome 11.0.696.55 \n * Google Chrome 11.0.696.56 \n * Google Chrome 11.0.696.57 \n * Google Chrome 11.0.696.58 \n * Google Chrome 11.0.696.59 \n * Google Chrome 11.0.696.60 \n * Google Chrome 11.0.696.61 \n * Google Chrome 11.0.696.62 \n * Google Chrome 11.0.696.63 \n * Google Chrome 11.0.696.64 \n * Google Chrome 11.0.696.65 \n * Google Chrome 11.0.696.66 \n * Google Chrome 11.0.696.67 \n * Google Chrome 11.0.696.68 \n * Google Chrome 11.0.696.69 \n * Google Chrome 11.0.696.7 \n * Google Chrome 11.0.696.70 \n * Google Chrome 11.0.696.71 \n * Google Chrome 11.0.696.72 \n * Google Chrome 11.0.696.77 \n * Google Chrome 11.0.696.8 \n * Google Chrome 11.0.696.9 \n * Google Chrome 11.0.697.0 \n * Google Chrome 11.0.698.0 \n * Google Chrome 11.0.699.0 \n * Google Chrome 12 \n * Google Chrome 12.0.700.0 \n * Google Chrome 12.0.701.0 \n * Google Chrome 12.0.702.0 \n * Google Chrome 12.0.702.1 \n * Google Chrome 12.0.702.2 \n * Google Chrome 12.0.703.0 \n * Google Chrome 12.0.704.0 \n * Google Chrome 12.0.705.0 \n * Google Chrome 12.0.706.0 \n * Google Chrome 12.0.707.0 \n * Google Chrome 12.0.708.0 \n * Google Chrome 12.0.709.0 \n * Google Chrome 12.0.710.0 \n * Google Chrome 12.0.711.0 \n * Google Chrome 12.0.712.0 \n * Google Chrome 12.0.713.0 \n * Google Chrome 12.0.714.0 \n * Google Chrome 12.0.715.0 \n * Google Chrome 12.0.716.0 \n * Google Chrome 12.0.717.0 \n * Google Chrome 12.0.718.0 \n * Google Chrome 12.0.719.0 \n * Google Chrome 12.0.719.1 \n * Google Chrome 12.0.720.0 \n * Google Chrome 12.0.721.0 \n * Google Chrome 12.0.721.1 \n * Google Chrome 12.0.722.0 \n * Google Chrome 12.0.723.0 \n * Google Chrome 12.0.723.1 \n * Google Chrome 12.0.724.0 \n * Google Chrome 12.0.725.0 \n * Google Chrome 12.0.726.0 \n * Google Chrome 12.0.727.0 \n * Google Chrome 12.0.728.0 \n * Google Chrome 12.0.729.0 \n * Google Chrome 12.0.730.0 \n * Google Chrome 12.0.731.0 \n * Google Chrome 12.0.732.0 \n * Google Chrome 12.0.733.0 \n * Google Chrome 12.0.734.0 \n * Google Chrome 12.0.735.0 \n * Google Chrome 12.0.736.0 \n * Google Chrome 12.0.737.0 \n * Google Chrome 12.0.738.0 \n * Google Chrome 12.0.739.0 \n * Google Chrome 12.0.740.0 \n * Google Chrome 12.0.741.0 \n * Google Chrome 12.0.742.0 \n * Google Chrome 12.0.742.1 \n * Google Chrome 12.0.742.10 \n * Google Chrome 12.0.742.100 \n * Google Chrome 12.0.742.105 \n * Google Chrome 12.0.742.11 \n * Google Chrome 12.0.742.111 \n * Google Chrome 12.0.742.112 \n * Google Chrome 12.0.742.113 \n * Google Chrome 12.0.742.114 \n * Google Chrome 12.0.742.115 \n * Google Chrome 12.0.742.12 \n * Google Chrome 12.0.742.120 \n * Google Chrome 12.0.742.121 \n * Google Chrome 12.0.742.122 \n * Google Chrome 12.0.742.123 \n * Google Chrome 12.0.742.124 \n * Google Chrome 12.0.742.13 \n * Google Chrome 12.0.742.14 \n * Google Chrome 12.0.742.15 \n * Google Chrome 12.0.742.16 \n * Google Chrome 12.0.742.17 \n * Google Chrome 12.0.742.18 \n * Google Chrome 12.0.742.19 \n * Google Chrome 12.0.742.2 \n * Google Chrome 12.0.742.20 \n * Google Chrome 12.0.742.21 \n * Google Chrome 12.0.742.22 \n * Google Chrome 12.0.742.3 \n * Google Chrome 12.0.742.30 \n * Google Chrome 12.0.742.4 \n * Google Chrome 12.0.742.41 \n * Google Chrome 12.0.742.42 \n * Google Chrome 12.0.742.43 \n * Google Chrome 12.0.742.44 \n * Google Chrome 12.0.742.45 \n * Google Chrome 12.0.742.46 \n * Google Chrome 12.0.742.47 \n * Google Chrome 12.0.742.48 \n * Google Chrome 12.0.742.49 \n * Google Chrome 12.0.742.5 \n * Google Chrome 12.0.742.50 \n * Google Chrome 12.0.742.51 \n * Google Chrome 12.0.742.52 \n * Google Chrome 12.0.742.53 \n * Google Chrome 12.0.742.54 \n * Google Chrome 12.0.742.55 \n * Google Chrome 12.0.742.56 \n * Google Chrome 12.0.742.57 \n * Google Chrome 12.0.742.58 \n * Google Chrome 12.0.742.59 \n * Google Chrome 12.0.742.6 \n * Google Chrome 12.0.742.60 \n * Google Chrome 12.0.742.61 \n * Google Chrome 12.0.742.63 \n * Google Chrome 12.0.742.64 \n * Google Chrome 12.0.742.65 \n * Google Chrome 12.0.742.66 \n * Google Chrome 12.0.742.67 \n * Google Chrome 12.0.742.68 \n * Google Chrome 12.0.742.69 \n * Google Chrome 12.0.742.70 \n * Google Chrome 12.0.742.71 \n * Google Chrome 12.0.742.72 \n * Google Chrome 12.0.742.73 \n * Google Chrome 12.0.742.74 \n * Google Chrome 12.0.742.75 \n * Google Chrome 12.0.742.77 \n * Google Chrome 12.0.742.8 \n * Google Chrome 12.0.742.82 \n * Google Chrome 12.0.742.9 \n * Google Chrome 12.0.742.91 \n * Google Chrome 12.0.742.92 \n * Google Chrome 12.0.742.93 \n * Google Chrome 12.0.742.94 \n * Google Chrome 12.0.743.0 \n * Google Chrome 12.0.744.0 \n * Google Chrome 12.0.745.0 \n * Google Chrome 12.0.746.0 \n * Google Chrome 12.0.747.0 \n * Google Chrome 13 \n * Google Chrome 13.0.748.0 \n * Google Chrome 13.0.749.0 \n * Google Chrome 13.0.750.0 \n * Google Chrome 13.0.751.0 \n * Google Chrome 13.0.752.0 \n * Google Chrome 13.0.753.0 \n * Google Chrome 13.0.754.0 \n * Google Chrome 13.0.755.0 \n * Google Chrome 13.0.756.0 \n * Google Chrome 13.0.757.0 \n * Google Chrome 13.0.758.0 \n * Google Chrome 13.0.759.0 \n * Google Chrome 13.0.760.0 \n * Google Chrome 13.0.761.0 \n * Google Chrome 13.0.761.1 \n * Google Chrome 13.0.762.0 \n * Google Chrome 13.0.762.1 \n * Google Chrome 13.0.763.0 \n * Google Chrome 13.0.764.0 \n * Google Chrome 13.0.765.0 \n * Google Chrome 13.0.766.0 \n * Google Chrome 13.0.767.0 \n * Google Chrome 13.0.767.1 \n * Google Chrome 13.0.768.0 \n * Google Chrome 13.0.769.0 \n * Google Chrome 13.0.770.0 \n * Google Chrome 13.0.771.0 \n * Google Chrome 13.0.772.0 \n * Google Chrome 13.0.773.0 \n * Google Chrome 13.0.774.0 \n * Google Chrome 13.0.775.0 \n * Google Chrome 13.0.775.1 \n * Google Chrome 13.0.775.2 \n * Google Chrome 13.0.775.4 \n * Google Chrome 13.0.776.0 \n * Google Chrome 13.0.776.1 \n * Google Chrome 13.0.777.0 \n * Google Chrome 13.0.777.1 \n * Google Chrome 13.0.777.2 \n * Google Chrome 13.0.777.3 \n * Google Chrome 13.0.777.4 \n * Google Chrome 13.0.777.5 \n * Google Chrome 13.0.777.6 \n * Google Chrome 13.0.778.0 \n * Google Chrome 13.0.779.0 \n * Google Chrome 13.0.780.0 \n * Google Chrome 13.0.781.0 \n * Google Chrome 13.0.782.0 \n * Google Chrome 13.0.782.1 \n * Google Chrome 13.0.782.10 \n * Google Chrome 13.0.782.100 \n * Google Chrome 13.0.782.101 \n * Google Chrome 13.0.782.102 \n * Google Chrome 13.0.782.103 \n * Google Chrome 13.0.782.104 \n * Google Chrome 13.0.782.105 \n * Google Chrome 13.0.782.106 \n * Google Chrome 13.0.782.107 \n * Google Chrome 13.0.782.108 \n * Google Chrome 13.0.782.109 \n * Google Chrome 13.0.782.11 \n * Google Chrome 13.0.782.112 \n * Google Chrome 13.0.782.12 \n * Google Chrome 13.0.782.13 \n * Google Chrome 13.0.782.14 \n * Google Chrome 13.0.782.15 \n * Google Chrome 13.0.782.16 \n * Google Chrome 13.0.782.17 \n * Google Chrome 13.0.782.18 \n * Google Chrome 13.0.782.19 \n * Google Chrome 13.0.782.20 \n * Google Chrome 13.0.782.21 \n * Google Chrome 13.0.782.210 \n * Google Chrome 13.0.782.211 \n * Google Chrome 13.0.782.212 \n * Google Chrome 13.0.782.213 \n * Google Chrome 13.0.782.214 \n * Google Chrome 13.0.782.215 \n * Google Chrome 13.0.782.216 \n * Google Chrome 13.0.782.217 \n * Google Chrome 13.0.782.218 \n * Google Chrome 13.0.782.219 \n * Google Chrome 13.0.782.220 \n * Google Chrome 13.0.782.23 \n * Google Chrome 13.0.782.237 \n * Google Chrome 13.0.782.238 \n * Google Chrome 13.0.782.24 \n * Google Chrome 13.0.782.25 \n * Google Chrome 13.0.782.26 \n * Google Chrome 13.0.782.27 \n * Google Chrome 13.0.782.28 \n * Google Chrome 13.0.782.29 \n * Google Chrome 13.0.782.3 \n * Google Chrome 13.0.782.30 \n * Google Chrome 13.0.782.31 \n * Google Chrome 13.0.782.32 \n * Google Chrome 13.0.782.33 \n * Google Chrome 13.0.782.34 \n * Google Chrome 13.0.782.35 \n * Google Chrome 13.0.782.36 \n * Google Chrome 13.0.782.37 \n * Google Chrome 13.0.782.38 \n * Google Chrome 13.0.782.39 \n * Google Chrome 13.0.782.4 \n * Google Chrome 13.0.782.40 \n * Google Chrome 13.0.782.41 \n * Google Chrome 13.0.782.42 \n * Google Chrome 13.0.782.43 \n * Google Chrome 13.0.782.44 \n * Google Chrome 13.0.782.45 \n * Google Chrome 13.0.782.46 \n * Google Chrome 13.0.782.47 \n * Google Chrome 13.0.782.48 \n * Google Chrome 13.0.782.49 \n * Google Chrome 13.0.782.50 \n * Google Chrome 13.0.782.51 \n * Google Chrome 13.0.782.52 \n * Google Chrome 13.0.782.53 \n * Google Chrome 13.0.782.55 \n * Google Chrome 13.0.782.56 \n * Google Chrome 13.0.782.6 \n * Google Chrome 13.0.782.7 \n * Google Chrome 13.0.782.81 \n * Google Chrome 13.0.782.82 \n * Google Chrome 13.0.782.83 \n * Google Chrome 13.0.782.84 \n * Google Chrome 13.0.782.85 \n * Google Chrome 13.0.782.86 \n * Google Chrome 13.0.782.87 \n * Google Chrome 13.0.782.88 \n * Google Chrome 13.0.782.89 \n * Google Chrome 13.0.782.90 \n * Google Chrome 13.0.782.91 \n * Google Chrome 13.0.782.92 \n * Google Chrome 13.0.782.93 \n * Google Chrome 13.0.782.94 \n * Google Chrome 13.0.782.95 \n * Google Chrome 13.0.782.96 \n * Google Chrome 13.0.782.97 \n * Google Chrome 13.0.782.98 \n * Google Chrome 13.0.782.99 \n * Google Chrome 14 \n * Google Chrome 14.0.783.0 \n * Google Chrome 14.0.784.0 \n * Google Chrome 14.0.785.0 \n * Google Chrome 14.0.786.0 \n * Google Chrome 14.0.787.0 \n * Google Chrome 14.0.788.0 \n * Google Chrome 14.0.789.0 \n * Google Chrome 14.0.790.0 \n * Google Chrome 14.0.791.0 \n * Google Chrome 14.0.792.0 \n * Google Chrome 14.0.793.0 \n * Google Chrome 14.0.794.0 \n * Google Chrome 14.0.795.0 \n * Google Chrome 14.0.796.0 \n * Google Chrome 14.0.797.0 \n * Google Chrome 14.0.798.0 \n * Google Chrome 14.0.799.0 \n * Google Chrome 14.0.800.0 \n * Google Chrome 14.0.801.0 \n * Google Chrome 14.0.802.0 \n * Google Chrome 14.0.803.0 \n * Google Chrome 14.0.804.0 \n * Google Chrome 14.0.805.0 \n * Google Chrome 14.0.806.0 \n * Google Chrome 14.0.807.0 \n * Google Chrome 14.0.808.0 \n * Google Chrome 14.0.809.0 \n * Google Chrome 14.0.810.0 \n * Google Chrome 14.0.811.0 \n * Google Chrome 14.0.812.0 \n * Google Chrome 14.0.813.0 \n * Google Chrome 14.0.814.0 \n * Google Chrome 14.0.815.0 \n * Google Chrome 14.0.816.0 \n * Google Chrome 14.0.818.0 \n * Google Chrome 14.0.819.0 \n * Google Chrome 14.0.820.0 \n * Google Chrome 14.0.821.0 \n * Google Chrome 14.0.822.0 \n * Google Chrome 14.0.823.0 \n * Google Chrome 14.0.824.0 \n * Google Chrome 14.0.825.0 \n * Google Chrome 14.0.826.0 \n * Google Chrome 14.0.827.0 \n * Google Chrome 14.0.827.10 \n * Google Chrome 14.0.827.12 \n * Google Chrome 14.0.829.1 \n * Google Chrome 14.0.830.0 \n * Google Chrome 14.0.831.0 \n * Google Chrome 14.0.832.0 \n * Google Chrome 14.0.833.0 \n * Google Chrome 14.0.834.0 \n * Google Chrome 14.0.835.0 \n * Google Chrome 14.0.835.1 \n * Google Chrome 14.0.835.100 \n * Google Chrome 14.0.835.101 \n * Google Chrome 14.0.835.102 \n * Google Chrome 14.0.835.103 \n * Google Chrome 14.0.835.104 \n * Google Chrome 14.0.835.105 \n * Google Chrome 14.0.835.106 \n * Google Chrome 14.0.835.107 \n * Google Chrome 14.0.835.108 \n * Google Chrome 14.0.835.109 \n * Google Chrome 14.0.835.11 \n * Google Chrome 14.0.835.110 \n * Google Chrome 14.0.835.111 \n * Google Chrome 14.0.835.112 \n * Google Chrome 14.0.835.113 \n * Google Chrome 14.0.835.114 \n * Google Chrome 14.0.835.115 \n * Google Chrome 14.0.835.116 \n * Google Chrome 14.0.835.117 \n * Google Chrome 14.0.835.118 \n * Google Chrome 14.0.835.119 \n * Google Chrome 14.0.835.120 \n * Google Chrome 14.0.835.121 \n * Google Chrome 14.0.835.122 \n * Google Chrome 14.0.835.123 \n * Google Chrome 14.0.835.124 \n * Google Chrome 14.0.835.125 \n * Google Chrome 14.0.835.126 \n * Google Chrome 14.0.835.127 \n * Google Chrome 14.0.835.128 \n * Google Chrome 14.0.835.13 \n * Google Chrome 14.0.835.14 \n * Google Chrome 14.0.835.149 \n * Google Chrome 14.0.835.15 \n * Google Chrome 14.0.835.150 \n * Google Chrome 14.0.835.151 \n * Google Chrome 14.0.835.152 \n * Google Chrome 14.0.835.153 \n * Google Chrome 14.0.835.154 \n * Google Chrome 14.0.835.155 \n * Google Chrome 14.0.835.156 \n * Google Chrome 14.0.835.157 \n * Google Chrome 14.0.835.158 \n * Google Chrome 14.0.835.159 \n * Google Chrome 14.0.835.16 \n * Google Chrome 14.0.835.160 \n * Google Chrome 14.0.835.161 \n * Google Chrome 14.0.835.162 \n * Google Chrome 14.0.835.163 \n * Google Chrome 14.0.835.18 \n * Google Chrome 14.0.835.184 \n * Google Chrome 14.0.835.186 \n * Google Chrome 14.0.835.187 \n * Google Chrome 14.0.835.2 \n * Google Chrome 14.0.835.20 \n * Google Chrome 14.0.835.202 \n * Google Chrome 14.0.835.203 \n * Google Chrome 14.0.835.204 \n * Google Chrome 14.0.835.21 \n * Google Chrome 14.0.835.22 \n * Google Chrome 14.0.835.23 \n * Google Chrome 14.0.835.24 \n * Google Chrome 14.0.835.25 \n * Google Chrome 14.0.835.26 \n * Google Chrome 14.0.835.27 \n * Google Chrome 14.0.835.28 \n * Google Chrome 14.0.835.29 \n * Google Chrome 14.0.835.30 \n * Google Chrome 14.0.835.31 \n * Google Chrome 14.0.835.32 \n * Google Chrome 14.0.835.33 \n * Google Chrome 14.0.835.34 \n * Google Chrome 14.0.835.35 \n * Google Chrome 14.0.835.4 \n * Google Chrome 14.0.835.8 \n * Google Chrome 14.0.835.86 \n * Google Chrome 14.0.835.87 \n * Google Chrome 14.0.835.88 \n * Google Chrome 14.0.835.89 \n * Google Chrome 14.0.835.9 \n * Google Chrome 14.0.835.90 \n * Google Chrome 14.0.835.91 \n * Google Chrome 14.0.835.92 \n * Google Chrome 14.0.835.93 \n * Google Chrome 14.0.835.94 \n * Google Chrome 14.0.835.95 \n * Google Chrome 14.0.835.96 \n * Google Chrome 14.0.835.97 \n * Google Chrome 14.0.835.98 \n * Google Chrome 14.0.835.99 \n * Google Chrome 14.0.836.0 \n * Google Chrome 14.0.837.0 \n * Google Chrome 14.0.838.0 \n * Google Chrome 14.0.839.0 \n * Google Chrome 15 \n * Google Chrome 15.0.859.0 \n * Google Chrome 15.0.860.0 \n * Google Chrome 15.0.861.0 \n * Google Chrome 15.0.862.0 \n * Google Chrome 15.0.862.1 \n * Google Chrome 15.0.863.0 \n * Google Chrome 15.0.864.0 \n * Google Chrome 15.0.865.0 \n * Google Chrome 15.0.866.0 \n * Google Chrome 15.0.867.0 \n * Google Chrome 15.0.868.0 \n * Google Chrome 15.0.868.1 \n * Google Chrome 15.0.869.0 \n * Google Chrome 15.0.870.0 \n * Google Chrome 15.0.871.0 \n * Google Chrome 15.0.871.1 \n * Google Chrome 15.0.872.0 \n * Google Chrome 15.0.873.0 \n * Google Chrome 15.0.874 102 \n * Google Chrome 15.0.874.0 \n * Google Chrome 15.0.874.1 \n * Google Chrome 15.0.874.10 \n * Google Chrome 15.0.874.101 \n * Google Chrome 15.0.874.102 \n * Google Chrome 15.0.874.103 \n * Google Chrome 15.0.874.104 \n * Google Chrome 15.0.874.106 \n * Google Chrome 15.0.874.11 \n * Google Chrome 15.0.874.116 \n * Google Chrome 15.0.874.117 \n * Google Chrome 15.0.874.119 \n * Google Chrome 15.0.874.12 \n * Google Chrome 15.0.874.120 \n * Google Chrome 15.0.874.121 \n * Google Chrome 15.0.874.13 \n * Google Chrome 15.0.874.14 \n * Google Chrome 15.0.874.15 \n * Google Chrome 15.0.874.16 \n * Google Chrome 15.0.874.17 \n * Google Chrome 15.0.874.18 \n * Google Chrome 15.0.874.19 \n * Google Chrome 15.0.874.2 \n * Google Chrome 15.0.874.20 \n * Google Chrome 15.0.874.21 \n * Google Chrome 15.0.874.22 \n * Google Chrome 15.0.874.23 \n * Google Chrome 15.0.874.24 \n * Google Chrome 15.0.874.3 \n * Google Chrome 15.0.874.4 \n * Google Chrome 15.0.874.44 \n * Google Chrome 15.0.874.45 \n * Google Chrome 15.0.874.46 \n * Google Chrome 15.0.874.47 \n * Google Chrome 15.0.874.48 \n * Google Chrome 15.0.874.49 \n * Google Chrome 15.0.874.5 \n * Google Chrome 15.0.874.6 \n * Google Chrome 15.0.874.7 \n * Google Chrome 15.0.874.8 \n * Google Chrome 15.0.874.9 \n * Google Chrome 16 \n * Google Chrome 16.0.877.0 \n * Google Chrome 16.0.878.0 \n * Google Chrome 16.0.879.0 \n * Google Chrome 16.0.880.0 \n * Google Chrome 16.0.881.0 \n * Google Chrome 16.0.882.0 \n * Google Chrome 16.0.883.0 \n * Google Chrome 16.0.884.0 \n * Google Chrome 16.0.885.0 \n * Google Chrome 16.0.886.0 \n * Google Chrome 16.0.886.1 \n * Google Chrome 16.0.887.0 \n * Google Chrome 16.0.888.0 \n * Google Chrome 16.0.889.0 \n * Google Chrome 16.0.889.2 \n * Google Chrome 16.0.889.3 \n * Google Chrome 16.0.890.0 \n * Google Chrome 16.0.890.1 \n * Google Chrome 16.0.891.0 \n * Google Chrome 16.0.891.1 \n * Google Chrome 16.0.892.0 \n * Google Chrome 16.0.893.0 \n * Google Chrome 16.0.893.1 \n * Google Chrome 16.0.894.0 \n * Google Chrome 16.0.895.0 \n * Google Chrome 16.0.896.0 \n * Google Chrome 16.0.897.0 \n * Google Chrome 16.0.898.0 \n * Google Chrome 16.0.899.0 \n * Google Chrome 16.0.900.0 \n * Google Chrome 16.0.901.0 \n * Google Chrome 16.0.902.0 \n * Google Chrome 16.0.903.0 \n * Google Chrome 16.0.904.0 \n * Google Chrome 16.0.905.0 \n * Google Chrome 16.0.906.0 \n * Google Chrome 16.0.906.1 \n * Google Chrome 16.0.907.0 \n * Google Chrome 16.0.908.0 \n * Google Chrome 16.0.909.0 \n * Google Chrome 16.0.910.0 \n * Google Chrome 16.0.911.0 \n * Google Chrome 16.0.911.1 \n * Google Chrome 16.0.911.2 \n * Google Chrome 16.0.912.0 \n * Google Chrome 16.0.912.1 \n * Google Chrome 16.0.912.10 \n * Google Chrome 16.0.912.11 \n * Google Chrome 16.0.912.12 \n * Google Chrome 16.0.912.13 \n * Google Chrome 16.0.912.14 \n * Google Chrome 16.0.912.15 \n * Google Chrome 16.0.912.19 \n * Google Chrome 16.0.912.2 \n * Google Chrome 16.0.912.20 \n * Google Chrome 16.0.912.21 \n * Google Chrome 16.0.912.22 \n * Google Chrome 16.0.912.23 \n * Google Chrome 16.0.912.24 \n * Google Chrome 16.0.912.25 \n * Google Chrome 16.0.912.26 \n * Google Chrome 16.0.912.27 \n * Google Chrome 16.0.912.28 \n * Google Chrome 16.0.912.29 \n * Google Chrome 16.0.912.3 \n * Google Chrome 16.0.912.30 \n * Google Chrome 16.0.912.31 \n * Google Chrome 16.0.912.32 \n * Google Chrome 16.0.912.33 \n * Google Chrome 16.0.912.34 \n * Google Chrome 16.0.912.35 \n * Google Chrome 16.0.912.36 \n * Google Chrome 16.0.912.37 \n * Google Chrome 16.0.912.38 \n * Google Chrome 16.0.912.39 \n * Google Chrome 16.0.912.4 \n * Google Chrome 16.0.912.40 \n * Google Chrome 16.0.912.41 \n * Google Chrome 16.0.912.42 \n * Google Chrome 16.0.912.43 \n * Google Chrome 16.0.912.5 \n * Google Chrome 16.0.912.6 \n * Google Chrome 16.0.912.62 \n * Google Chrome 16.0.912.63 \n * Google Chrome 16.0.912.66 \n * Google Chrome 16.0.912.7 \n * Google Chrome 16.0.912.74 \n * Google Chrome 16.0.912.75 \n * Google Chrome 16.0.912.76 \n * Google Chrome 16.0.912.77 \n * Google Chrome 16.0.912.8 \n * Google Chrome 16.0.912.9 \n * Google Chrome 17 \n * Google Chrome 17.0.921.3 \n * Google Chrome 17.0.922.0 \n * Google Chrome 17.0.923.0 \n * Google Chrome 17.0.923.1 \n * Google Chrome 17.0.924.0 \n * Google Chrome 17.0.925.0 \n * Google Chrome 17.0.926.0 \n * Google Chrome 17.0.927.0 \n * Google Chrome 17.0.928.0 \n * Google Chrome 17.0.928.1 \n * Google Chrome 17.0.928.2 \n * Google Chrome 17.0.928.3 \n * Google Chrome 17.0.929.0 \n * Google Chrome 17.0.930.0 \n * Google Chrome 17.0.931.0 \n * Google Chrome 17.0.932.0 \n * Google Chrome 17.0.933.0 \n * Google Chrome 17.0.933.1 \n * Google Chrome 17.0.934.0 \n * Google Chrome 17.0.935.0 \n * Google Chrome 17.0.935.1 \n * Google Chrome 17.0.936.0 \n * Google Chrome 17.0.936.1 \n * Google Chrome 17.0.937.0 \n * Google Chrome 17.0.938.0 \n * Google Chrome 17.0.939.0 \n * Google Chrome 17.0.939.1 \n * Google Chrome 17.0.940.0 \n * Google Chrome 17.0.941.0 \n * Google Chrome 17.0.942.0 \n * Google Chrome 17.0.943.0 \n * Google Chrome 17.0.944.0 \n * Google Chrome 17.0.945.0 \n * Google Chrome 17.0.946.0 \n * Google Chrome 17.0.947.0 \n * Google Chrome 17.0.948.0 \n * Google Chrome 17.0.949.0 \n * Google Chrome 17.0.950.0 \n * Google Chrome 17.0.951.0 \n * Google Chrome 17.0.952.0 \n * Google Chrome 17.0.953.0 \n * Google Chrome 17.0.954.0 \n * Google Chrome 17.0.954.1 \n * Google Chrome 17.0.954.2 \n * Google Chrome 17.0.954.3 \n * Google Chrome 17.0.955.0 \n * Google Chrome 17.0.956.0 \n * Google Chrome 17.0.957.0 \n * Google Chrome 17.0.958.0 \n * Google Chrome 17.0.958.1 \n * Google Chrome 17.0.959.0 \n * Google Chrome 17.0.960.0 \n * Google Chrome 17.0.961.0 \n * Google Chrome 17.0.962.0 \n * Google Chrome 17.0.963.0 \n * Google Chrome 17.0.963.1 \n * Google Chrome 17.0.963.10 \n * Google Chrome 17.0.963.11 \n * Google Chrome 17.0.963.12 \n * Google Chrome 17.0.963.13 \n * Google Chrome 17.0.963.14 \n * Google Chrome 17.0.963.15 \n * Google Chrome 17.0.963.16 \n * Google Chrome 17.0.963.17 \n * Google Chrome 17.0.963.18 \n * Google Chrome 17.0.963.19 \n * Google Chrome 17.0.963.2 \n * Google Chrome 17.0.963.20 \n * Google Chrome 17.0.963.21 \n * Google Chrome 17.0.963.22 \n * Google Chrome 17.0.963.23 \n * Google Chrome 17.0.963.24 \n * Google Chrome 17.0.963.25 \n * Google Chrome 17.0.963.26 \n * Google Chrome 17.0.963.27 \n * Google Chrome 17.0.963.28 \n * Google Chrome 17.0.963.29 \n * Google Chrome 17.0.963.3 \n * Google Chrome 17.0.963.30 \n * Google Chrome 17.0.963.31 \n * Google Chrome 17.0.963.32 \n * Google Chrome 17.0.963.33 \n * Google Chrome 17.0.963.34 \n * Google Chrome 17.0.963.35 \n * Google Chrome 17.0.963.36 \n * Google Chrome 17.0.963.37 \n * Google Chrome 17.0.963.38 \n * Google Chrome 17.0.963.39 \n * Google Chrome 17.0.963.4 \n * Google Chrome 17.0.963.40 \n * Google Chrome 17.0.963.41 \n * Google Chrome 17.0.963.42 \n * Google Chrome 17.0.963.43 \n * Google Chrome 17.0.963.44 \n * Google Chrome 17.0.963.45 \n * Google Chrome 17.0.963.46 \n * Google Chrome 17.0.963.47 \n * Google Chrome 17.0.963.48 \n * Google Chrome 17.0.963.49 \n * Google Chrome 17.0.963.5 \n * Google Chrome 17.0.963.50 \n * Google Chrome 17.0.963.51 \n * Google Chrome 17.0.963.52 \n * Google Chrome 17.0.963.53 \n * Google Chrome 17.0.963.54 \n * Google Chrome 17.0.963.55 \n * Google Chrome 17.0.963.56 \n * Google Chrome 17.0.963.57 \n * Google Chrome 17.0.963.59 \n * Google Chrome 17.0.963.6 \n * Google Chrome 17.0.963.60 \n * Google Chrome 17.0.963.61 \n * Google Chrome 17.0.963.62 \n * Google Chrome 17.0.963.63 \n * Google Chrome 17.0.963.64 \n * Google Chrome 17.0.963.65 \n * Google Chrome 17.0.963.66 \n * Google Chrome 17.0.963.67 \n * Google Chrome 17.0.963.69 \n * Google Chrome 17.0.963.7 \n * Google Chrome 17.0.963.70 \n * Google Chrome 17.0.963.74 \n * Google Chrome 17.0.963.75 \n * Google Chrome 17.0.963.76 \n * Google Chrome 17.0.963.77 \n * Google Chrome 17.0.963.78 \n * Google Chrome 17.0.963.79 \n * Google Chrome 17.0.963.8 \n * Google Chrome 17.0.963.80 \n * Google Chrome 17.0.963.81 \n * Google Chrome 17.0.963.82 \n * Google Chrome 17.0.963.83 \n * Google Chrome 17.0.963.84 \n * Google Chrome 17.0.963.9 \n * Google Chrome 18 \n * Google Chrome 18.0.1000.0 \n * Google Chrome 18.0.1001.0 \n * Google Chrome 18.0.1001.1 \n * Google Chrome 18.0.1002.0 \n * Google Chrome 18.0.1003.0 \n * Google Chrome 18.0.1003.1 \n * Google Chrome 18.0.1004.0 \n * Google Chrome 18.0.1005.0 \n * Google Chrome 18.0.1006.0 \n * Google Chrome 18.0.1007.0 \n * Google Chrome 18.0.1008.0 \n * Google Chrome 18.0.1009.0 \n * Google Chrome 18.0.1010.0 \n * Google Chrome 18.0.1010.1 \n * Google Chrome 18.0.1010.2 \n * Google Chrome 18.0.1011.1 \n * Google Chrome 18.0.1012.0 \n * Google Chrome 18.0.1012.1 \n * Google Chrome 18.0.1012.2 \n * Google Chrome 18.0.1013.0 \n * Google Chrome 18.0.1014.0 \n * Google Chrome 18.0.1015.0 \n * Google Chrome 18.0.1016.0 \n * Google Chrome 18.0.1017.0 \n * Google Chrome 18.0.1017.1 \n * Google Chrome 18.0.1017.2 \n * Google Chrome 18.0.1017.3 \n * Google Chrome 18.0.1018.0 \n * Google Chrome 18.0.1019.0 \n * Google Chrome 18.0.1019.1 \n * Google Chrome 18.0.1020.0 \n * Google Chrome 18.0.1021.0 \n * Google Chrome 18.0.1022.0 \n * Google Chrome 18.0.1023.0 \n * Google Chrome 18.0.1024.0 \n * Google Chrome 18.0.1025.0 \n * Google Chrome 18.0.1025.1 \n * Google Chrome 18.0.1025.10 \n * Google Chrome 18.0.1025.100 \n * Google Chrome 18.0.1025.102 \n * Google Chrome 18.0.1025.107 \n * Google Chrome 18.0.1025.108 \n * Google Chrome 18.0.1025.109 \n * Google Chrome 18.0.1025.110 \n * Google Chrome 18.0.1025.111 \n * Google Chrome 18.0.1025.112 \n * Google Chrome 18.0.1025.113 \n * Google Chrome 18.0.1025.114 \n * Google Chrome 18.0.1025.116 \n * Google Chrome 18.0.1025.117 \n * Google Chrome 18.0.1025.118 \n * Google Chrome 18.0.1025.120 \n * Google Chrome 18.0.1025.129 \n * Google Chrome 18.0.1025.130 \n * Google Chrome 18.0.1025.131 \n * Google Chrome 18.0.1025.132 \n * Google Chrome 18.0.1025.133 \n * Google Chrome 18.0.1025.134 \n * Google Chrome 18.0.1025.135 \n * Google Chrome 18.0.1025.136 \n * Google Chrome 18.0.1025.137 \n * Google Chrome 18.0.1025.139 \n * Google Chrome 18.0.1025.140 \n * Google Chrome 18.0.1025.142 \n * Google Chrome 18.0.1025.145 \n * Google Chrome 18.0.1025.146 \n * Google Chrome 18.0.1025.147 \n * Google Chrome 18.0.1025.148 \n * Google Chrome 18.0.1025.149 \n * Google Chrome 18.0.1025.150 \n * Google Chrome 18.0.1025.151 \n * Google Chrome 18.0.1025.162 \n * Google Chrome 18.0.1025.168 \n * Google Chrome 18.0.1025.2 \n * Google Chrome 18.0.1025.29 \n * Google Chrome 18.0.1025.3 \n * Google Chrome 18.0.1025.30 \n * Google Chrome 18.0.1025.31 \n * Google Chrome 18.0.1025.32 \n * Google Chrome 18.0.1025.33 \n * Google Chrome 18.0.1025.35 \n * Google Chrome 18.0.1025.36 \n * Google Chrome 18.0.1025.37 \n * Google Chrome 18.0.1025.38 \n * Google Chrome 18.0.1025.39 \n * Google Chrome 18.0.1025.4 \n * Google Chrome 18.0.1025.40 \n * Google Chrome 18.0.1025.41 \n * Google Chrome 18.0.1025.42 \n * Google Chrome 18.0.1025.43 \n * Google Chrome 18.0.1025.44 \n * Google Chrome 18.0.1025.45 \n * Google Chrome 18.0.1025.46 \n * Google Chrome 18.0.1025.47 \n * Google Chrome 18.0.1025.48 \n * Google Chrome 18.0.1025.49 \n * Google Chrome 18.0.1025.5 \n * Google Chrome 18.0.1025.50 \n * Google Chrome 18.0.1025.51 \n * Google Chrome 18.0.1025.52 \n * Google Chrome 18.0.1025.54 \n * Google Chrome 18.0.1025.55 \n * Google Chrome 18.0.1025.56 \n * Google Chrome 18.0.1025.57 \n * Google Chrome 18.0.1025.58 \n * Google Chrome 18.0.1025.6 \n * Google Chrome 18.0.1025.60 \n * Google Chrome 18.0.1025.7 \n * Google Chrome 18.0.1025.73 \n * Google Chrome 18.0.1025.74 \n * Google Chrome 18.0.1025.8 \n * Google Chrome 18.0.1025.9 \n * Google Chrome 18.0.1025.95 \n * Google Chrome 18.0.1025.96 \n * Google Chrome 18.0.1025.97 \n * Google Chrome 18.0.1025.98 \n * Google Chrome 18.0.1025.99 \n * Google Chrome 19 \n * Google Chrome 19.0.1028.0 \n * Google Chrome 19.0.1029.0 \n * Google Chrome 19.0.1030.0 \n * Google Chrome 19.0.1031.0 \n * Google Chrome 19.0.1032.0 \n * Google Chrome 19.0.1033.0 \n * Google Chrome 19.0.1034.0 \n * Google Chrome 19.0.1035.0 \n * Google Chrome 19.0.1036.0 \n * Google Chrome 19.0.1036.2 \n * Google Chrome 19.0.1036.3 \n * Google Chrome 19.0.1036.4 \n * Google Chrome 19.0.1036.6 \n * Google Chrome 19.0.1036.7 \n * Google Chrome 19.0.1037.0 \n * Google Chrome 19.0.1038.0 \n * Google Chrome 19.0.1039.0 \n * Google Chrome 19.0.1040.0 \n * Google Chrome 19.0.1041.0 \n * Google Chrome 19.0.1042.0 \n * Google Chrome 19.0.1043.0 \n * Google Chrome 19.0.1044.0 \n * Google Chrome 19.0.1045.0 \n * Google Chrome 19.0.1046.0 \n * Google Chrome 19.0.1047.0 \n * Google Chrome 19.0.1048.0 \n * Google Chrome 19.0.1049.0 \n * Google Chrome 19.0.1049.1 \n * Google Chrome 19.0.1049.2 \n * Google Chrome 19.0.1049.3 \n * Google Chrome 19.0.1050.0 \n * Google Chrome 19.0.1051.0 \n * Google Chrome 19.0.1052.0 \n * Google Chrome 19.0.1053.0 \n * Google Chrome 19.0.1054.0 \n * Google Chrome 19.0.1055.0 \n * Google Chrome 19.0.1055.1 \n * Google Chrome 19.0.1055.2 \n * Google Chrome 19.0.1055.3 \n * Google Chrome 19.0.1056.0 \n * Google Chrome 19.0.1056.1 \n * Google Chrome 19.0.1057.0 \n * Google Chrome 19.0.1057.1 \n * Google Chrome 19.0.1057.3 \n * Google Chrome 19.0.1058.0 \n * Google Chrome 19.0.1058.1 \n * Google Chrome 19.0.1059.0 \n * Google Chrome 19.0.1060.0 \n * Google Chrome 19.0.1060.1 \n * Google Chrome 19.0.1061.0 \n * Google Chrome 19.0.1061.1 \n * Google Chrome 19.0.1062.0 \n * Google Chrome 19.0.1062.1 \n * Google Chrome 19.0.1063.0 \n * Google Chrome 19.0.1063.1 \n * Google Chrome 19.0.1064.0 \n * Google Chrome 19.0.1065.0 \n * Google Chrome 19.0.1066.0 \n * Google Chrome 19.0.1067.0 \n * Google Chrome 19.0.1068.0 \n * Google Chrome 19.0.1068.1 \n * Google Chrome 19.0.1069.0 \n * Google Chrome 19.0.1070.0 \n * Google Chrome 19.0.1071.0 \n * Google Chrome 19.0.1072.0 \n * Google Chrome 19.0.1073.0 \n * Google Chrome 19.0.1074.0 \n * Google Chrome 19.0.1075.0 \n * Google Chrome 19.0.1076.0 \n * Google Chrome 19.0.1076.1 \n * Google Chrome 19.0.1077.0 \n * Google Chrome 19.0.1077.1 \n * Google Chrome 19.0.1077.2 \n * Google Chrome 19.0.1077.3 \n * Google Chrome 19.0.1078.0 \n * Google Chrome 19.0.1079.0 \n * Google Chrome 19.0.1080.0 \n * Google Chrome 19.0.1081.0 \n * Google Chrome 19.0.1081.2 \n * Google Chrome 19.0.1082.0 \n * Google Chrome 19.0.1082.1 \n * Google Chrome 19.0.1083.0 \n * Google Chrome 19.0.1084.0 \n * Google Chrome 19.0.1084.1 \n * Google Chrome 19.0.1084.10 \n * Google Chrome 19.0.1084.11 \n * Google Chrome 19.0.1084.12 \n * Google Chrome 19.0.1084.13 \n * Google Chrome 19.0.1084.14 \n * Google Chrome 19.0.1084.15 \n * Google Chrome 19.0.1084.16 \n * Google Chrome 19.0.1084.17 \n * Google Chrome 19.0.1084.18 \n * Google Chrome 19.0.1084.19 \n * Google Chrome 19.0.1084.2 \n * Google Chrome 19.0.1084.20 \n * Google Chrome 19.0.1084.21 \n * Google Chrome 19.0.1084.22 \n * Google Chrome 19.0.1084.23 \n * Google Chrome 19.0.1084.24 \n * Google Chrome 19.0.1084.25 \n * Google Chrome 19.0.1084.26 \n * Google Chrome 19.0.1084.27 \n * Google Chrome 19.0.1084.28 \n * Google Chrome 19.0.1084.29 \n * Google Chrome 19.0.1084.3 \n * Google Chrome 19.0.1084.30 \n * Google Chrome 19.0.1084.31 \n * Google Chrome 19.0.1084.32 \n * Google Chrome 19.0.1084.33 \n * Google Chrome 19.0.1084.35 \n * Google Chrome 19.0.1084.36 \n * Google Chrome 19.0.1084.37 \n * Google Chrome 19.0.1084.38 \n * Google Chrome 19.0.1084.39 \n * Google Chrome 19.0.1084.4 \n * Google Chrome 19.0.1084.40 \n * Google Chrome 19.0.1084.41 \n * Google Chrome 19.0.1084.42 \n * Google Chrome 19.0.1084.43 \n * Google Chrome 19.0.1084.44 \n * Google Chrome 19.0.1084.45 \n * Google Chrome 19.0.1084.46 \n * Google Chrome 19.0.1084.47 \n * Google Chrome 19.0.1084.48 \n * Google Chrome 19.0.1084.5 \n * Google Chrome 19.0.1084.50 \n * Google Chrome 19.0.1084.51 \n * Google Chrome 19.0.1084.52 \n * Google Chrome 19.0.1084.6 \n * Google Chrome 19.0.1084.7 \n * Google Chrome 19.0.1084.8 \n * Google Chrome 19.0.1084.9 \n * Google Chrome 19.0.1085.0 \n * Google Chrome 2.0.156.1 \n * Google Chrome 2.0.157.0 \n * Google Chrome 2.0.157.2 \n * Google Chrome 2.0.158.0 \n * Google Chrome 2.0.159.0 \n * Google Chrome 2.0.169.0 \n * Google Chrome 2.0.169.1 \n * Google Chrome 2.0.170.0 \n * Google Chrome 2.0.172 \n * Google Chrome 2.0.172.2 \n * Google Chrome 2.0.172.27 \n * Google Chrome 2.0.172.28 \n * Google Chrome 2.0.172.30 \n * Google Chrome 2.0.172.31 \n * Google Chrome 2.0.172.33 \n * Google Chrome 2.0.172.37 \n * Google Chrome 2.0.172.38 \n * Google Chrome 2.0.172.43 \n * Google Chrome 2.0.172.8 \n * Google Chrome 20 \n * Google Chrome 20.0.1132.0 \n * Google Chrome 20.0.1132.1 \n * Google Chrome 20.0.1132.10 \n * Google Chrome 20.0.1132.11 \n * Google Chrome 20.0.1132.12 \n * Google Chrome 20.0.1132.13 \n * Google Chrome 20.0.1132.14 \n * Google Chrome 20.0.1132.15 \n * Google Chrome 20.0.1132.16 \n * Google Chrome 20.0.1132.17 \n * Google Chrome 20.0.1132.18 \n * Google Chrome 20.0.1132.19 \n * Google Chrome 20.0.1132.2 \n * Google Chrome 20.0.1132.20 \n * Google Chrome 20.0.1132.21 \n * Google Chrome 20.0.1132.22 \n * Google Chrome 20.0.1132.23 \n * Google Chrome 20.0.1132.24 \n * Google Chrome 20.0.1132.25 \n * Google Chrome 20.0.1132.26 \n * Google Chrome 20.0.1132.27 \n * Google Chrome 20.0.1132.28 \n * Google Chrome 20.0.1132.29 \n * Google Chrome 20.0.1132.3 \n * Google Chrome 20.0.1132.30 \n * Google Chrome 20.0.1132.31 \n * Google Chrome 20.0.1132.32 \n * Google Chrome 20.0.1132.33 \n * Google Chrome 20.0.1132.34 \n * Google Chrome 20.0.1132.35 \n * Google Chrome 20.0.1132.36 \n * Google Chrome 20.0.1132.37 \n * Google Chrome 20.0.1132.38 \n * Google Chrome 20.0.1132.39 \n * Google Chrome 20.0.1132.4 \n * Google Chrome 20.0.1132.40 \n * Google Chrome 20.0.1132.41 \n * Google Chrome 20.0.1132.42 \n * Google Chrome 20.0.1132.43 \n * Google Chrome 20.0.1132.45 \n * Google Chrome 20.0.1132.46 \n * Google Chrome 20.0.1132.47 \n * Google Chrome 20.0.1132.5 \n * Google Chrome 20.0.1132.54 \n * Google Chrome 20.0.1132.55 \n * Google Chrome 20.0.1132.56 \n * Google Chrome 20.0.1132.57 \n * Google Chrome 20.0.1132.6 \n * Google Chrome 20.0.1132.7 \n * Google Chrome 20.0.1132.8 \n * Google Chrome 20.0.1132.9 \n * Google Chrome 21 \n * Google Chrome 21.0.1180.0 \n * Google Chrome 21.0.1180.1 \n * Google Chrome 21.0.1180.2 \n * Google Chrome 21.0.1180.31 \n * Google Chrome 21.0.1180.32 \n * Google Chrome 21.0.1180.33 \n * Google Chrome 21.0.1180.34 \n * Google Chrome 21.0.1180.35 \n * Google Chrome 21.0.1180.36 \n * Google Chrome 21.0.1180.37 \n * Google Chrome 21.0.1180.38 \n * Google Chrome 21.0.1180.39 \n * Google Chrome 21.0.1180.41 \n * Google Chrome 21.0.1180.46 \n * Google Chrome 21.0.1180.47 \n * Google Chrome 21.0.1180.48 \n * Google Chrome 21.0.1180.49 \n * Google Chrome 21.0.1180.50 \n * Google Chrome 21.0.1180.51 \n * Google Chrome 21.0.1180.52 \n * Google Chrome 21.0.1180.53 \n * Google Chrome 21.0.1180.54 \n * Google Chrome 21.0.1180.55 \n * Google Chrome 21.0.1180.56 \n * Google Chrome 21.0.1180.57 \n * Google Chrome 21.0.1180.59 \n * Google Chrome 21.0.1180.60 \n * Google Chrome 21.0.1180.61 \n * Google Chrome 21.0.1180.62 \n * Google Chrome 21.0.1180.63 \n * Google Chrome 21.0.1180.64 \n * Google Chrome 21.0.1180.68 \n * Google Chrome 21.0.1180.69 \n * Google Chrome 21.0.1180.70 \n * Google Chrome 21.0.1180.71 \n * Google Chrome 21.0.1180.72 \n * Google Chrome 21.0.1180.73 \n * Google Chrome 21.0.1180.74 \n * Google Chrome 21.0.1180.75 \n * Google Chrome 21.0.1180.76 \n * Google Chrome 21.0.1180.77 \n * Google Chrome 21.0.1180.78 \n * Google Chrome 21.0.1180.79 \n * Google Chrome 21.0.1180.80 \n * Google Chrome 21.0.1180.81 \n * Google Chrome 21.0.1180.82 \n * Google Chrome 21.0.1180.83 \n * Google Chrome 21.0.1180.84 \n * Google Chrome 21.0.1180.85 \n * Google Chrome 21.0.1180.86 \n * Google Chrome 21.0.1180.87 \n * Google Chrome 21.0.1180.88 \n * Google Chrome 21.0.1180.89 \n * Google Chrome 22 \n * Google Chrome 22.0.1229.0 \n * Google Chrome 22.0.1229.1 \n * Google Chrome 22.0.1229.10 \n * Google Chrome 22.0.1229.11 \n * Google Chrome 22.0.1229.12 \n * Google Chrome 22.0.1229.14 \n * Google Chrome 22.0.1229.16 \n * Google Chrome 22.0.1229.17 \n * Google Chrome 22.0.1229.18 \n * Google Chrome 22.0.1229.2 \n * Google Chrome 22.0.1229.20 \n * Google Chrome 22.0.1229.21 \n * Google Chrome 22.0.1229.22 \n * Google Chrome 22.0.1229.23 \n * Google Chrome 22.0.1229.24 \n * Google Chrome 22.0.1229.25 \n * Google Chrome 22.0.1229.26 \n * Google Chrome 22.0.1229.27 \n * Google Chrome 22.0.1229.28 \n * Google Chrome 22.0.1229.29 \n * Google Chrome 22.0.1229.3 \n * Google Chrome 22.0.1229.31 \n * Google Chrome 22.0.1229.32 \n * Google Chrome 22.0.1229.33 \n * Google Chrome 22.0.1229.35 \n * Google Chrome 22.0.1229.36 \n * Google Chrome 22.0.1229.37 \n * Google Chrome 22.0.1229.39 \n * Google Chrome 22.0.1229.4 \n * Google Chrome 22.0.1229.48 \n * Google Chrome 22.0.1229.49 \n * Google Chrome 22.0.1229.50 \n * Google Chrome 22.0.1229.51 \n * Google Chrome 22.0.1229.52 \n * Google Chrome 22.0.1229.53 \n * Google Chrome 22.0.1229.54 \n * Google Chrome 22.0.1229.55 \n * Google Chrome 22.0.1229.56 \n * Google Chrome 22.0.1229.57 \n * Google Chrome 22.0.1229.58 \n * Google Chrome 22.0.1229.59 \n * Google Chrome 22.0.1229.6 \n * Google Chrome 22.0.1229.60 \n * Google Chrome 22.0.1229.62 \n * Google Chrome 22.0.1229.63 \n * Google Chrome 22.0.1229.64 \n * Google Chrome 22.0.1229.65 \n * Google Chrome 22.0.1229.67 \n * Google Chrome 22.0.1229.7 \n * Google Chrome 22.0.1229.76 \n * Google Chrome 22.0.1229.78 \n * Google Chrome 22.0.1229.79 \n * Google Chrome 22.0.1229.8 \n * Google Chrome 22.0.1229.89 \n * Google Chrome 22.0.1229.9 \n * Google Chrome 22.0.1229.91 \n * Google Chrome 22.0.1229.92 \n * Google Chrome 22.0.1229.94 \n * Google Chrome 22.0.1229.95 \n * Google Chrome 22.0.1229.96 \n * Google Chrome 23.0.1271.0 \n * Google Chrome 23.0.1271.1 \n * Google Chrome 23.0.1271.10 \n * Google Chrome 23.0.1271.11 \n * Google Chrome 23.0.1271.12 \n * Google Chrome 23.0.1271.13 \n * Google Chrome 23.0.1271.14 \n * Google Chrome 23.0.1271.15 \n * Google Chrome 23.0.1271.16 \n * Google Chrome 23.0.1271.17 \n * Google Chrome 23.0.1271.18 \n * Google Chrome 23.0.1271.19 \n * Google Chrome 23.0.1271.2 \n * Google Chrome 23.0.1271.20 \n * Google Chrome 23.0.1271.21 \n * Google Chrome 23.0.1271.22 \n * Google Chrome 23.0.1271.23 \n * Google Chrome 23.0.1271.24 \n * Google Chrome 23.0.1271.26 \n * Google Chrome 23.0.1271.3 \n * Google Chrome 23.0.1271.30 \n * Google Chrome 23.0.1271.31 \n * Google Chrome 23.0.1271.32 \n * Google Chrome 23.0.1271.33 \n * Google Chrome 23.0.1271.35 \n * Google Chrome 23.0.1271.36 \n * Google Chrome 23.0.1271.37 \n * Google Chrome 23.0.1271.38 \n * Google Chrome 23.0.1271.39 \n * Google Chrome 23.0.1271.4 \n * Google Chrome 23.0.1271.40 \n * Google Chrome 23.0.1271.41 \n * Google Chrome 23.0.1271.44 \n * Google Chrome 23.0.1271.45 \n * Google Chrome 23.0.1271.46 \n * Google Chrome 23.0.1271.49 \n * Google Chrome 23.0.1271.5 \n * Google Chrome 23.0.1271.50 \n * Google Chrome 23.0.1271.51 \n * Google Chrome 23.0.1271.52 \n * Google Chrome 23.0.1271.53 \n * Google Chrome 23.0.1271.54 \n * Google Chrome 23.0.1271.55 \n * Google Chrome 23.0.1271.56 \n * Google Chrome 23.0.1271.57 \n * Google Chrome 23.0.1271.58 \n * Google Chrome 23.0.1271.59 \n * Google Chrome 23.0.1271.6 \n * Google Chrome 23.0.1271.60 \n * Google Chrome 23.0.1271.61 \n * Google Chrome 23.0.1271.62 \n * Google Chrome 23.0.1271.64 \n * Google Chrome 23.0.1271.7 \n * Google Chrome 23.0.1271.8 \n * Google Chrome 23.0.1271.83 \n * Google Chrome 23.0.1271.84 \n * Google Chrome 23.0.1271.85 \n * Google Chrome 23.0.1271.86 \n * Google Chrome 23.0.1271.87 \n * Google Chrome 23.0.1271.88 \n * Google Chrome 23.0.1271.89 \n * Google Chrome 23.0.1271.9 \n * Google Chrome 23.0.1271.91 \n * Google Chrome 23.0.1271.95 \n * Google Chrome 23.0.1271.96 \n * Google Chrome 23.0.1271.97 \n * Google Chrome 24.0.1272.0 \n * Google Chrome 24.0.1272.1 \n * Google Chrome 24.0.1273.0 \n * Google Chrome 24.0.1274.0 \n * Google Chrome 24.0.1275.0 \n * Google Chrome 24.0.1276.0 \n * Google Chrome 24.0.1276.1 \n * Google Chrome 24.0.1277.0 \n * Google Chrome 24.0.1278.0 \n * Google Chrome 24.0.1279.0 \n * Google Chrome 24.0.1280.0 \n * Google Chrome 24.0.1281.0 \n * Google Chrome 24.0.1281.1 \n * Google Chrome 24.0.1281.2 \n * Google Chrome 24.0.1281.3 \n * Google Chrome 24.0.1282.0 \n * Google Chrome 24.0.1283.0 \n * Google Chrome 24.0.1284.0 \n * Google Chrome 24.0.1284.1 \n * Google Chrome 24.0.1284.2 \n * Google Chrome 24.0.1285.0 \n * Google Chrome 24.0.1285.1 \n * Google Chrome 24.0.1285.2 \n * Google Chrome 24.0.1286.0 \n * Google Chrome 24.0.1286.1 \n * Google Chrome 24.0.1287.0 \n * Google Chrome 24.0.1287.1 \n * Google Chrome 24.0.1288.0 \n * Google Chrome 24.0.1288.1 \n * Google Chrome 24.0.1289.0 \n * Google Chrome 24.0.1289.1 \n * Google Chrome 24.0.1290.0 \n * Google Chrome 24.0.1291.0 \n * Google Chrome 24.0.1292.0 \n * Google Chrome 24.0.1293.0 \n * Google Chrome 24.0.1294.0 \n * Google Chrome 24.0.1295.0 \n * Google Chrome 24.0.1296.0 \n * Google Chrome 24.0.1297.0 \n * Google Chrome 24.0.1298.0 \n * Google Chrome 24.0.1299.0 \n * Google Chrome 24.0.1300.0 \n * Google Chrome 24.0.1301.0 \n * Google Chrome 24.0.1301.2 \n * Google Chrome 24.0.1302.0 \n * Google Chrome 24.0.1303.0 \n * Google Chrome 24.0.1304.0 \n * Google Chrome 24.0.1304.1 \n * Google Chrome 24.0.1305.0 \n * Google Chrome 24.0.1305.1 \n * Google Chrome 24.0.1305.2 \n * Google Chrome 24.0.1305.3 \n * Google Chrome 24.0.1305.4 \n * Google Chrome 24.0.1306.0 \n * Google Chrome 24.0.1306.1 \n * Google Chrome 24.0.1307.0 \n * Google Chrome 24.0.1307.1 \n * Google Chrome 24.0.1308.0 \n * Google Chrome 24.0.1309.0 \n * Google Chrome 24.0.1310.0 \n * Google Chrome 24.0.1311.0 \n * Google Chrome 24.0.1311.1 \n * Google Chrome 24.0.1312.0 \n * Google Chrome 24.0.1312.1 \n * Google Chrome 24.0.1312.10 \n * Google Chrome 24.0.1312.11 \n * Google Chrome 24.0.1312.12 \n * Google Chrome 24.0.1312.13 \n * Google Chrome 24.0.1312.14 \n * Google Chrome 24.0.1312.15 \n * Google Chrome 24.0.1312.16 \n * Google Chrome 24.0.1312.17 \n * Google Chrome 24.0.1312.18 \n * Google Chrome 24.0.1312.19 \n * Google Chrome 24.0.1312.20 \n * Google Chrome 24.0.1312.21 \n * Google Chrome 24.0.1312.22 \n * Google Chrome 24.0.1312.23 \n * Google Chrome 24.0.1312.24 \n * Google Chrome 24.0.1312.25 \n * Google Chrome 24.0.1312.26 \n * Google Chrome 24.0.1312.27 \n * Google Chrome 24.0.1312.28 \n * Google Chrome 24.0.1312.29 \n * Google Chrome 24.0.1312.30 \n * Google Chrome 24.0.1312.31 \n * Google Chrome 24.0.1312.32 \n * Google Chrome 24.0.1312.33 \n * Google Chrome 24.0.1312.34 \n * Google Chrome 24.0.1312.35 \n * Google Chrome 24.0.1312.36 \n * Google Chrome 24.0.1312.37 \n * Google Chrome 24.0.1312.38 \n * Google Chrome 24.0.1312.39 \n * Google Chrome 24.0.1312.4 \n * Google Chrome 24.0.1312.40 \n * Google Chrome 24.0.1312.41 \n * Google Chrome 24.0.1312.42 \n * Google Chrome 24.0.1312.43 \n * Google Chrome 24.0.1312.44 \n * Google Chrome 24.0.1312.45 \n * Google Chrome 24.0.1312.46 \n * Google Chrome 24.0.1312.47 \n * Google Chrome 24.0.1312.48 \n * Google Chrome 24.0.1312.49 \n * Google Chrome 24.0.1312.5 \n * Google Chrome 24.0.1312.50 \n * Google Chrome 24.0.1312.51 \n * Google Chrome 24.0.1312.52 \n * Google Chrome 24.0.1312.53 \n * Google Chrome 24.0.1312.54 \n * Google Chrome 24.0.1312.55 \n * Google Chrome 24.0.1312.56 \n * Google Chrome 24.0.1312.57 \n * Google Chrome 24.0.1312.6 \n * Google Chrome 24.0.1312.7 \n * Google Chrome 24.0.1312.70 \n * Google Chrome 24.0.1312.8 \n * Google Chrome 24.0.1312.9 \n * Google Chrome 25 \n * Google Chrome 25.0.1364.0 \n * Google Chrome 25.0.1364.1 \n * Google Chrome 25.0.1364.10 \n * Google Chrome 25.0.1364.108 \n * Google Chrome 25.0.1364.11 \n * Google Chrome 25.0.1364.110 \n * Google Chrome 25.0.1364.112 \n * Google Chrome 25.0.1364.113 \n * Google Chrome 25.0.1364.114 \n * Google Chrome 25.0.1364.115 \n * Google Chrome 25.0.1364.116 \n * Google Chrome 25.0.1364.117 \n * Google Chrome 25.0.1364.118 \n * Google Chrome 25.0.1364.119 \n * Google Chrome 25.0.1364.12 \n * Google Chrome 25.0.1364.120 \n * Google Chrome 25.0.1364.121 \n * Google Chrome 25.0.1364.122 \n * Google Chrome 25.0.1364.123 \n * Google Chrome 25.0.1364.124 \n * Google Chrome 25.0.1364.125 \n * Google Chrome 25.0.1364.126 \n * Google Chrome 25.0.1364.13 \n * Google Chrome 25.0.1364.14 \n * Google Chrome 25.0.1364.15 \n * Google Chrome 25.0.1364.152 \n * Google Chrome 25.0.1364.16 \n * Google Chrome 25.0.1364.160 \n * Google Chrome 25.0.1364.17 \n * Google Chrome 25.0.1364.172 \n * Google Chrome 25.0.1364.18 \n * Google Chrome 25.0.1364.19 \n * Google Chrome 25.0.1364.2 \n * Google Chrome 25.0.1364.20 \n * Google Chrome 25.0.1364.21 \n * Google Chrome 25.0.1364.22 \n * Google Chrome 25.0.1364.23 \n * Google Chrome 25.0.1364.24 \n * Google Chrome 25.0.1364.25 \n * Google Chrome 25.0.1364.26 \n * Google Chrome 25.0.1364.27 \n * Google Chrome 25.0.1364.28 \n * Google Chrome 25.0.1364.29 \n * Google Chrome 25.0.1364.3 \n * Google Chrome 25.0.1364.30 \n * Google Chrome 25.0.1364.31 \n * Google Chrome 25.0.1364.32 \n * Google Chrome 25.0.1364.33 \n * Google Chrome 25.0.1364.34 \n * Google Chrome 25.0.1364.35 \n * Google Chrome 25.0.1364.36 \n * Google Chrome 25.0.1364.37 \n * Google Chrome 25.0.1364.38 \n * Google Chrome 25.0.1364.39 \n * Google Chrome 25.0.1364.40 \n * Google Chrome 25.0.1364.41 \n * Google Chrome 25.0.1364.42 \n * Google Chrome 25.0.1364.43 \n * Google Chrome 25.0.1364.44 \n * Google Chrome 25.0.1364.45 \n * Google Chrome 25.0.1364.46 \n * Google Chrome 25.0.1364.47 \n * Google Chrome 25.0.1364.48 \n * Google Chrome 25.0.1364.49 \n * Google Chrome 25.0.1364.5 \n * Google Chrome 25.0.1364.50 \n * Google Chrome 25.0.1364.51 \n * Google Chrome 25.0.1364.52 \n * Google Chrome 25.0.1364.53 \n * Google Chrome 25.0.1364.54 \n * Google Chrome 25.0.1364.55 \n * Google Chrome 25.0.1364.56 \n * Google Chrome 25.0.1364.57 \n * Google Chrome 25.0.1364.58 \n * Google Chrome 25.0.1364.61 \n * Google Chrome 25.0.1364.62 \n * Google Chrome 25.0.1364.63 \n * Google Chrome 25.0.1364.65 \n * Google Chrome 25.0.1364.66 \n * Google Chrome 25.0.1364.67 \n * Google Chrome 25.0.1364.68 \n * Google Chrome 25.0.1364.7 \n * Google Chrome 25.0.1364.70 \n * Google Chrome 25.0.1364.72 \n * Google Chrome 25.0.1364.73 \n * Google Chrome 25.0.1364.74 \n * Google Chrome 25.0.1364.75 \n * Google Chrome 25.0.1364.76 \n * Google Chrome 25.0.1364.77 \n * Google Chrome 25.0.1364.78 \n * Google Chrome 25.0.1364.79 \n * Google Chrome 25.0.1364.8 \n * Google Chrome 25.0.1364.80 \n * Google Chrome 25.0.1364.81 \n * Google Chrome 25.0.1364.82 \n * Google Chrome 25.0.1364.84 \n * Google Chrome 25.0.1364.85 \n * Google Chrome 25.0.1364.86 \n * Google Chrome 25.0.1364.87 \n * Google Chrome 25.0.1364.88 \n * Google Chrome 25.0.1364.89 \n * Google Chrome 25.0.1364.9 \n * Google Chrome 25.0.1364.90 \n * Google Chrome 25.0.1364.91 \n * Google Chrome 25.0.1364.92 \n * Google Chrome 25.0.1364.93 \n * Google Chrome 25.0.1364.95 \n * Google Chrome 25.0.1364.97 \n * Google Chrome 25.0.1364.98 \n * Google Chrome 25.0.1364.99 \n * Google Chrome 26.0.1410.28 \n * Google Chrome 26.0.1410.43 \n * Google Chrome 26.0.1410.46 \n * Google Chrome 26.0.1410.53 \n * Google Chrome 26.0.1410.63 \n * Google Chrome 26.0.1410.64 \n * Google Chrome 27.0.1444.0 \n * Google Chrome 27.0.1444.3 \n * Google Chrome 27.0.1453.0 \n * Google Chrome 27.0.1453.1 \n * Google Chrome 27.0.1453.10 \n * Google Chrome 27.0.1453.102 \n * Google Chrome 27.0.1453.103 \n * Google Chrome 27.0.1453.104 \n * Google Chrome 27.0.1453.105 \n * Google Chrome 27.0.1453.106 \n * Google Chrome 27.0.1453.107 \n * Google Chrome 27.0.1453.108 \n * Google Chrome 27.0.1453.109 \n * Google Chrome 27.0.1453.11 \n * Google Chrome 27.0.1453.110 \n * Google Chrome 27.0.1453.111 \n * Google Chrome 27.0.1453.112 \n * Google Chrome 27.0.1453.113 \n * Google Chrome 27.0.1453.114 \n * Google Chrome 27.0.1453.115 \n * Google Chrome 27.0.1453.116 \n * Google Chrome 27.0.1453.12 \n * Google Chrome 27.0.1453.13 \n * Google Chrome 27.0.1453.15 \n * Google Chrome 27.0.1453.2 \n * Google Chrome 27.0.1453.3 \n * Google Chrome 27.0.1453.34 \n * Google Chrome 27.0.1453.35 \n * Google Chrome 27.0.1453.36 \n * Google Chrome 27.0.1453.37 \n * Google Chrome 27.0.1453.38 \n * Google Chrome 27.0.1453.39 \n * Google Chrome 27.0.1453.4 \n * Google Chrome 27.0.1453.40 \n * Google Chrome 27.0.1453.41 \n * Google Chrome 27.0.1453.42 \n * Google Chrome 27.0.1453.43 \n * Google Chrome 27.0.1453.44 \n * Google Chrome 27.0.1453.45 \n * Google Chrome 27.0.1453.46 \n * Google Chrome 27.0.1453.47 \n * Google Chrome 27.0.1453.49 \n * Google Chrome 27.0.1453.5 \n * Google Chrome 27.0.1453.50 \n * Google Chrome 27.0.1453.51 \n * Google Chrome 27.0.1453.52 \n * Google Chrome 27.0.1453.54 \n * Google Chrome 27.0.1453.55 \n * Google Chrome 27.0.1453.56 \n * Google Chrome 27.0.1453.57 \n * Google Chrome 27.0.1453.58 \n * Google Chrome 27.0.1453.59 \n * Google Chrome 27.0.1453.6 \n * Google Chrome 27.0.1453.60 \n * Google Chrome 27.0.1453.61 \n * Google Chrome 27.0.1453.62 \n * Google Chrome 27.0.1453.63 \n * Google Chrome 27.0.1453.64 \n * Google Chrome 27.0.1453.65 \n * Google Chrome 27.0.1453.66 \n * Google Chrome 27.0.1453.67 \n * Google Chrome 27.0.1453.68 \n * Google Chrome 27.0.1453.69 \n * Google Chrome 27.0.1453.7 \n * Google Chrome 27.0.1453.70 \n * Google Chrome 27.0.1453.71 \n * Google Chrome 27.0.1453.72 \n * Google Chrome 27.0.1453.73 \n * Google Chrome 27.0.1453.74 \n * Google Chrome 27.0.1453.75 \n * Google Chrome 27.0.1453.76 \n * Google Chrome 27.0.1453.77 \n * Google Chrome 27.0.1453.78 \n * Google Chrome 27.0.1453.79 \n * Google Chrome 27.0.1453.8 \n * Google Chrome 27.0.1453.80 \n * Google Chrome 27.0.1453.81 \n * Google Chrome 27.0.1453.82 \n * Google Chrome 27.0.1453.83 \n * Google Chrome 27.0.1453.84 \n * Google Chrome 27.0.1453.85 \n * Google Chrome 27.0.1453.86 \n * Google Chrome 27.0.1453.87 \n * Google Chrome 27.0.1453.88 \n * Google Chrome 27.0.1453.89 \n * Google Chrome 27.0.1453.9 \n * Google Chrome 27.0.1453.90 \n * Google Chrome 27.0.1453.91 \n * Google Chrome 27.0.1453.93 \n * Google Chrome 27.0.1453.94 \n * Google Chrome 28.0.1498.0 \n * Google Chrome 28.0.1500.0 \n * Google Chrome 28.0.1500.10 \n * Google Chrome 28.0.1500.11 \n * Google Chrome 28.0.1500.12 \n * Google Chrome 28.0.1500.13 \n * Google Chrome 28.0.1500.14 \n * Google Chrome 28.0.1500.15 \n * Google Chrome 28.0.1500.16 \n * Google Chrome 28.0.1500.17 \n * Google Chrome 28.0.1500.18 \n * Google Chrome 28.0.1500.19 \n * Google Chrome 28.0.1500.2 \n * Google Chrome 28.0.1500.20 \n * Google Chrome 28.0.1500.21 \n * Google Chrome 28.0.1500.22 \n * Google Chrome 28.0.1500.23 \n * Google Chrome 28.0.1500.24 \n * Google Chrome 28.0.1500.25 \n * Google Chrome 28.0.1500.26 \n * Google Chrome 28.0.1500.27 \n * Google Chrome 28.0.1500.28 \n * Google Chrome 28.0.1500.29 \n * Google Chrome 28.0.1500.3 \n * Google Chrome 28.0.1500.31 \n * Google Chrome 28.0.1500.32 \n * Google Chrome 28.0.1500.33 \n * Google Chrome 28.0.1500.34 \n * Google Chrome 28.0.1500.35 \n * Google Chrome 28.0.1500.36 \n * Google Chrome 28.0.1500.37 \n * Google Chrome 28.0.1500.38 \n * Google Chrome 28.0.1500.39 \n * Google Chrome 28.0.1500.4 \n * Google Chrome 28.0.1500.40 \n * Google Chrome 28.0.1500.41 \n * Google Chrome 28.0.1500.42 \n * Google Chrome 28.0.1500.43 \n * Google Chrome 28.0.1500.44 \n * Google Chrome 28.0.1500.45 \n * Google Chrome 28.0.1500.46 \n * Google Chrome 28.0.1500.47 \n * Google Chrome 28.0.1500.48 \n * Google Chrome 28.0.1500.49 \n * Google Chrome 28.0.1500.5 \n * Google Chrome 28.0.1500.50 \n * Google Chrome 28.0.1500.51 \n * Google Chrome 28.0.1500.52 \n * Google Chrome 28.0.1500.53 \n * Google Chrome 28.0.1500.54 \n * Google Chrome 28.0.1500.56 \n * Google Chrome 28.0.1500.58 \n * Google Chrome 28.0.1500.59 \n * Google Chrome 28.0.1500.6 \n * Google Chrome 28.0.1500.60 \n * Google Chrome 28.0.1500.61 \n * Google Chrome 28.0.1500.62 \n * Google Chrome 28.0.1500.63 \n * Google Chrome 28.0.1500.64 \n * Google Chrome 28.0.1500.66 \n * Google Chrome 28.0.1500.68 \n * Google Chrome 28.0.1500.70 \n * Google Chrome 28.0.1500.71 \n * Google Chrome 28.0.1500.72 \n * Google Chrome 28.0.1500.8 \n * Google Chrome 28.0.1500.89 \n * Google Chrome 28.0.1500.9 \n * Google Chrome 28.0.1500.91 \n * Google Chrome 28.0.1500.93 \n * Google Chrome 28.0.1500.94 \n * Google Chrome 28.0.1500.95 \n * Google Chrome 29.0.1547.0 \n * Google Chrome 29.0.1547.10 \n * Google Chrome 29.0.1547.12 \n * Google Chrome 29.0.1547.14 \n * Google Chrome 29.0.1547.16 \n * Google Chrome 29.0.1547.18 \n * Google Chrome 29.0.1547.2 \n * Google Chrome 29.0.1547.21 \n * Google Chrome 29.0.1547.23 \n * Google Chrome 29.0.1547.28 \n * Google Chrome 29.0.1547.3 \n * Google Chrome 29.0.1547.31 \n * Google Chrome 29.0.1547.33 \n * Google Chrome 29.0.1547.35 \n * Google Chrome 29.0.1547.37 \n * Google Chrome 29.0.1547.39 \n * Google Chrome 29.0.1547.40 \n * Google Chrome 29.0.1547.42 \n * Google Chrome 29.0.1547.46 \n * Google Chrome 29.0.1547.48 \n * Google Chrome 29.0.1547.5 \n * Google Chrome 29.0.1547.51 \n * Google Chrome 29.0.1547.53 \n * Google Chrome 29.0.1547.55 \n * Google Chrome 29.0.1547.57 \n * Google Chrome 29.0.1547.7 \n * Google Chrome 29.0.1547.76 \n * Google Chrome 29.0.1547.9 \n * Google Chrome 3 \n * Google Chrome 3.0 Beta \n * Google Chrome 3.0.182.2 \n * Google Chrome 3.0.190.2 \n * Google Chrome 3.0.193.2 Beta \n * Google Chrome 3.0.195.2 \n * Google Chrome 3.0.195.21 \n * Google Chrome 3.0.195.24 \n * Google Chrome 3.0.195.25 \n * Google Chrome 3.0.195.27 \n * Google Chrome 3.0.195.32 \n * Google Chrome 3.0.195.33 \n * Google Chrome 3.0.195.36 \n * Google Chrome 3.0.195.37 \n * Google Chrome 3.0.195.38 \n * Google Chrome 30.0.1599.0 \n * Google Chrome 30.0.1599.10 \n * Google Chrome 30.0.1599.100 \n * Google Chrome 30.0.1599.101 \n * Google Chrome 30.0.1599.12 \n * Google Chrome 30.0.1599.14 \n * Google Chrome 30.0.1599.16 \n * Google Chrome 30.0.1599.18 \n * Google Chrome 30.0.1599.2 \n * Google Chrome 30.0.1599.21 \n * Google Chrome 30.0.1599.23 \n * Google Chrome 30.0.1599.25 \n * Google Chrome 30.0.1599.27 \n * Google Chrome 30.0.1599.29 \n * Google Chrome 30.0.1599.31 \n * Google Chrome 30.0.1599.33 \n * Google Chrome 30.0.1599.35 \n * Google Chrome 30.0.1599.37 \n * Google Chrome 30.0.1599.39 \n * Google Chrome 30.0.1599.40 \n * Google Chrome 30.0.1599.42 \n * Google Chrome 30.0.1599.44 \n * Google Chrome 30.0.1599.48 \n * Google Chrome 30.0.1599.5 \n * Google Chrome 30.0.1599.51 \n * Google Chrome 30.0.1599.53 \n * Google Chrome 30.0.1599.57 \n * Google Chrome 30.0.1599.59 \n * Google Chrome 30.0.1599.60 \n * Google Chrome 30.0.1599.64 \n * Google Chrome 30.0.1599.66 \n * Google Chrome 30.0.1599.67 \n * Google Chrome 30.0.1599.68 \n * Google Chrome 30.0.1599.69 \n * Google Chrome 30.0.1599.7 \n * Google Chrome 30.0.1599.79 \n * Google Chrome 30.0.1599.80 \n * Google Chrome 30.0.1599.81 \n * Google Chrome 30.0.1599.82 \n * Google Chrome 30.0.1599.84 \n * Google Chrome 30.0.1599.85 \n * Google Chrome 30.0.1599.86 \n * Google Chrome 30.0.1599.87 \n * Google Chrome 30.0.1599.88 \n * Google Chrome 30.0.1599.9 \n * Google Chrome 30.0.1599.90 \n * Google Chrome 31.0.1650.0 \n * Google Chrome 31.0.1650.10 \n * Google Chrome 31.0.1650.11 \n * Google Chrome 31.0.1650.12 \n * Google Chrome 31.0.1650.13 \n * Google Chrome 31.0.1650.14 \n * Google Chrome 31.0.1650.15 \n * Google Chrome 31.0.1650.16 \n * Google Chrome 31.0.1650.17 \n * Google Chrome 31.0.1650.18 \n * Google Chrome 31.0.1650.19 \n * Google Chrome 31.0.1650.2 \n * Google Chrome 31.0.1650.20 \n * Google Chrome 31.0.1650.22 \n * Google Chrome 31.0.1650.23 \n * Google Chrome 31.0.1650.25 \n * Google Chrome 31.0.1650.26 \n * Google Chrome 31.0.1650.27 \n * Google Chrome 31.0.1650.28 \n * Google Chrome 31.0.1650.29 \n * Google Chrome 31.0.1650.3 \n * Google Chrome 31.0.1650.30 \n * Google Chrome 31.0.1650.31 \n * Google Chrome 31.0.1650.32 \n * Google Chrome 31.0.1650.33 \n * Google Chrome 31.0.1650.34 \n * Google Chrome 31.0.1650.35 \n * Google Chrome 31.0.1650.36 \n * Google Chrome 31.0.1650.37 \n * Google Chrome 31.0.1650.38 \n * Google Chrome 31.0.1650.39 \n * Google Chrome 31.0.1650.4 \n * Google Chrome 31.0.1650.41 \n * Google Chrome 31.0.1650.42 \n * Google Chrome 31.0.1650.43 \n * Google Chrome 31.0.1650.44 \n * Google Chrome 31.0.1650.45 \n * Google Chrome 31.0.1650.46 \n * Google Chrome 31.0.1650.47 \n * Google Chrome 31.0.1650.48 \n * Google Chrome 31.0.1650.49 \n * Google Chrome 31.0.1650.5 \n * Google Chrome 31.0.1650.50 \n * Google Chrome 31.0.1650.52 \n * Google Chrome 31.0.1650.54 \n * Google Chrome 31.0.1650.57 \n * Google Chrome 31.0.1650.58 \n * Google Chrome 31.0.1650.6 \n * Google Chrome 31.0.1650.60 \n * Google Chrome 31.0.1650.61 \n * Google Chrome 31.0.1650.62 \n * Google Chrome 31.0.1650.63 \n * Google Chrome 31.0.1650.7 \n * Google Chrome 31.0.1650.8 \n * Google Chrome 31.0.1650.9 \n * Google Chrome 32.0.1651.2 \n * Google Chrome 32.0.1652.1 \n * Google Chrome 32.0.1653.1 \n * Google Chrome 32.0.1654.0 \n * Google Chrome 32.0.1654.3 \n * Google Chrome 32.0.1655.1 \n * Google Chrome 32.0.1656.1 \n * Google Chrome 32.0.1657.0 \n * Google Chrome 32.0.1658.0 \n * Google Chrome 32.0.1658.2 \n * Google Chrome 32.0.1659.1 \n * Google Chrome 32.0.1659.3 \n * Google Chrome 32.0.1660.1 \n * Google Chrome 32.0.1661.0 \n * Google Chrome 32.0.1662.0 \n * Google Chrome 32.0.1662.2 \n * Google Chrome 32.0.1663.1 \n * Google Chrome 32.0.1663.3 \n * Google Chrome 32.0.1664.1 \n * Google Chrome 32.0.1664.3 \n * Google Chrome 32.0.1666.0 \n * Google Chrome 32.0.1667.0 \n * Google Chrome 32.0.1668.0 \n * Google Chrome 32.0.1668.2 \n * Google Chrome 32.0.1668.4 \n * Google Chrome 32.0.1668.6 \n * Google Chrome 32.0.1669.1 \n * Google Chrome 32.0.1669.3 \n * Google Chrome 32.0.1670.1 \n * Google Chrome 32.0.1670.3 \n * Google Chrome 32.0.1670.5 \n * Google Chrome 32.0.1671.2 \n * Google Chrome 32.0.1671.4 \n * Google Chrome 32.0.1671.8 \n * Google Chrome 32.0.1672.2 \n * Google Chrome 32.0.1673.2 \n * Google Chrome 32.0.1673.4 \n * Google Chrome 32.0.1674.1 \n * Google Chrome 32.0.1675.0 \n * Google Chrome 32.0.1675.2 \n * Google Chrome 32.0.1676.0 \n * Google Chrome 32.0.1676.2 \n * Google Chrome 32.0.1677.1 \n * Google Chrome 32.0.1678.1 \n * Google Chrome 32.0.1679.0 \n * Google Chrome 32.0.1680.0 \n * Google Chrome 32.0.1681.0 \n * Google Chrome 32.0.1681.3 \n * Google Chrome 32.0.1682.3 \n * Google Chrome 32.0.1682.5 \n * Google Chrome 32.0.1683.1 \n * Google Chrome 32.0.1684.0 \n * Google Chrome 32.0.1684.2 \n * Google Chrome 32.0.1685.0 \n * Google Chrome 32.0.1685.2 \n * Google Chrome 32.0.1686.0 \n * Google Chrome 32.0.1687.0 \n * Google Chrome 32.0.1688.0 \n * Google Chrome 32.0.1689.0 \n * Google Chrome 32.0.1689.2 \n * Google Chrome 32.0.1690.0 \n * Google Chrome 32.0.1700.0 \n * Google Chrome 32.0.1700.100 \n * Google Chrome 32.0.1700.102 \n * Google Chrome 32.0.1700.103 \n * Google Chrome 32.0.1700.107 \n * Google Chrome 32.0.1700.11 \n * Google Chrome 32.0.1700.13 \n * Google Chrome 32.0.1700.15 \n * Google Chrome 32.0.1700.17 \n * Google Chrome 32.0.1700.19 \n * Google Chrome 32.0.1700.21 \n * Google Chrome 32.0.1700.23 \n * Google Chrome 32.0.1700.26 \n * Google Chrome 32.0.1700.28 \n * Google Chrome 32.0.1700.3 \n * Google Chrome 32.0.1700.31 \n * Google Chrome 32.0.1700.33 \n * Google Chrome 32.0.1700.35 \n * Google Chrome 32.0.1700.39 \n * Google Chrome 32.0.1700.41 \n * Google Chrome 32.0.1700.50 \n * Google Chrome 32.0.1700.52 \n * Google Chrome 32.0.1700.54 \n * Google Chrome 32.0.1700.56 \n * Google Chrome 32.0.1700.58 \n * Google Chrome 32.0.1700.6 \n * Google Chrome 32.0.1700.63 \n * Google Chrome 32.0.1700.65 \n * Google Chrome 32.0.1700.67 \n * Google Chrome 32.0.1700.69 \n * Google Chrome 32.0.1700.70 \n * Google Chrome 32.0.1700.74 \n * Google Chrome 32.0.1700.76 \n * Google Chrome 32.0.1700.77 \n * Google Chrome 32.0.1700.9 \n * Google Chrome 32.0.1700.95 \n * Google Chrome 32.0.1700.97 \n * Google Chrome 32.0.1700.98 \n * Google Chrome 33.0.1750.0 \n * Google Chrome 33.0.1750.10 \n * Google Chrome 33.0.1750.106 \n * Google Chrome 33.0.1750.108 \n * Google Chrome 33.0.1750.11 \n * Google Chrome 33.0.1750.111 \n * Google Chrome 33.0.1750.113 \n * Google Chrome 33.0.1750.116 \n * Google Chrome 33.0.1750.117 \n * Google Chrome 33.0.1750.124 \n * Google Chrome 33.0.1750.125 \n * Google Chrome 33.0.1750.13 \n * Google Chrome 33.0.1750.132 \n * Google Chrome 33.0.1750.135 \n * Google Chrome 33.0.1750.14 \n * Google Chrome 33.0.1750.144 \n * Google Chrome 33.0.1750.146 \n * Google Chrome 33.0.1750.149 \n * Google Chrome 33.0.1750.151 \n * Google Chrome 33.0.1750.152 \n * Google Chrome 33.0.1750.154 \n * Google Chrome 33.0.1750.16 \n * Google Chrome 33.0.1750.166 \n * Google Chrome 33.0.1750.168 \n * Google Chrome 33.0.1750.19 \n * Google Chrome 33.0.1750.20 \n * Google Chrome 33.0.1750.22 \n * Google Chrome 33.0.1750.24 \n * Google Chrome 33.0.1750.26 \n * Google Chrome 33.0.1750.28 \n * Google Chrome 33.0.1750.3 \n * Google Chrome 33.0.1750.31 \n * Google Chrome 33.0.1750.35 \n * Google Chrome 33.0.1750.37 \n * Google Chrome 33.0.1750.39 \n * Google Chrome 33.0.1750.40 \n * Google Chrome 33.0.1750.42 \n * Google Chrome 33.0.1750.44 \n * Google Chrome 33.0.1750.46 \n * Google Chrome 33.0.1750.48 \n * Google Chrome 33.0.1750.5 \n * Google Chrome 33.0.1750.51 \n * Google Chrome 33.0.1750.53 \n * Google Chrome 33.0.1750.55 \n * Google Chrome 33.0.1750.57 \n * Google Chrome 33.0.1750.59 \n * Google Chrome 33.0.1750.60 \n * Google Chrome 33.0.1750.62 \n * Google Chrome 33.0.1750.64 \n * Google Chrome 33.0.1750.66 \n * Google Chrome 33.0.1750.68 \n * Google Chrome 33.0.1750.7 \n * Google Chrome 33.0.1750.71 \n * Google Chrome 33.0.1750.74 \n * Google Chrome 33.0.1750.76 \n * Google Chrome 33.0.1750.79 \n * Google Chrome 33.0.1750.80 \n * Google Chrome 33.0.1750.82 \n * Google Chrome 33.0.1750.85 \n * Google Chrome 33.0.1750.89 \n * Google Chrome 33.0.1750.90 \n * Google Chrome 33.0.1750.92 \n * Google Chrome 34.0.1847.0 \n * Google Chrome 34.0.1847.10 \n * Google Chrome 34.0.1847.101 \n * Google Chrome 34.0.1847.103 \n * Google Chrome 34.0.1847.109 \n * Google Chrome 34.0.1847.112 \n * Google Chrome 34.0.1847.114 \n * Google Chrome 34.0.1847.116 \n * Google Chrome 34.0.1847.118 \n * Google Chrome 34.0.1847.120 \n * Google Chrome 34.0.1847.130 \n * Google Chrome 34.0.1847.131 \n * Google Chrome 34.0.1847.132 \n * Google Chrome 34.0.1847.134 \n * Google Chrome 34.0.1847.136 \n * Google Chrome 34.0.1847.137 \n * Google Chrome 34.0.1847.15 \n * Google Chrome 34.0.1847.23 \n * Google Chrome 34.0.1847.25 \n * Google Chrome 34.0.1847.36 \n * Google Chrome 34.0.1847.38 \n * Google Chrome 34.0.1847.4 \n * Google Chrome 34.0.1847.42 \n * Google Chrome 34.0.1847.44 \n * Google Chrome 34.0.1847.46 \n * Google Chrome 34.0.1847.48 \n * Google Chrome 34.0.1847.5 \n * Google Chrome 34.0.1847.51 \n * Google Chrome 34.0.1847.53 \n * Google Chrome 34.0.1847.55 \n * Google Chrome 34.0.1847.57 \n * Google Chrome 34.0.1847.59 \n * Google Chrome 34.0.1847.60 \n * Google Chrome 34.0.1847.62 \n * Google Chrome 34.0.1847.64 \n * Google Chrome 34.0.1847.66 \n * Google Chrome 34.0.1847.68 \n * Google Chrome 34.0.1847.7 \n * Google Chrome 34.0.1847.72 \n * Google Chrome 34.0.1847.74 \n * Google Chrome 34.0.1847.76 \n * Google Chrome 34.0.1847.78 \n * Google Chrome 34.0.1847.8 \n * Google Chrome 34.0.1847.81 \n * Google Chrome 34.0.1847.83 \n * Google Chrome 34.0.1847.86 \n * Google Chrome 34.0.1847.9 \n * Google Chrome 34.0.1847.92 \n * Google Chrome 34.0.1847.97 \n * Google Chrome 34.0.1847.99 \n * Google Chrome 35.0.1916.0 \n * Google Chrome 35.0.1916.10 \n * Google Chrome 35.0.1916.103 \n * Google Chrome 35.0.1916.105 \n * Google Chrome 35.0.1916.107 \n * Google Chrome 35.0.1916.109 \n * Google Chrome 35.0.1916.110 \n * Google Chrome 35.0.1916.112 \n * Google Chrome 35.0.1916.114 \n * Google Chrome 35.0.1916.13 \n * Google Chrome 35.0.1916.15 \n * Google Chrome 35.0.1916.153 \n * Google Chrome 35.0.1916.18 \n * Google Chrome 35.0.1916.2 \n * Google Chrome 35.0.1916.21 \n * Google Chrome 35.0.1916.23 \n * Google Chrome 35.0.1916.3 \n * Google Chrome 35.0.1916.32 \n * Google Chrome 35.0.1916.34 \n * Google Chrome 35.0.1916.36 \n * Google Chrome 35.0.1916.38 \n * Google Chrome 35.0.1916.4 \n * Google Chrome 35.0.1916.41 \n * Google Chrome 35.0.1916.43 \n * Google Chrome 35.0.1916.45 \n * Google Chrome 35.0.1916.47 \n * Google Chrome 35.0.1916.49 \n * Google Chrome 35.0.1916.51 \n * Google Chrome 35.0.1916.54 \n * Google Chrome 35.0.1916.57 \n * Google Chrome 35.0.1916.6 \n * Google Chrome 35.0.1916.68 \n * Google Chrome 35.0.1916.7 \n * Google Chrome 35.0.1916.72 \n * Google Chrome 35.0.1916.77 \n * Google Chrome 35.0.1916.80 \n * Google Chrome 35.0.1916.84 \n * Google Chrome 35.0.1916.86 \n * Google Chrome 35.0.1916.9 \n * Google Chrome 35.0.1916.92 \n * Google Chrome 35.0.1916.95 \n * Google Chrome 35.0.1916.98 \n * Google Chrome 36.0.1985.122 \n * Google Chrome 36.0.1985.143 \n * Google Chrome 37.0.2062.0 \n * Google Chrome 37.0.2062.10 \n * Google Chrome 37.0.2062.12 \n * Google Chrome 37.0.2062.120 \n * Google Chrome 37.0.2062.124 \n * Google Chrome 37.0.2062.14 \n * Google Chrome 37.0.2062.16 \n * Google Chrome 37.0.2062.18 \n * Google Chrome 37.0.2062.2 \n * Google Chrome 37.0.2062.21 \n * Google Chrome 37.0.2062.23 \n * Google Chrome 37.0.2062.25 \n * Google Chrome 37.0.2062.27 \n * Google Chrome 37.0.2062.29 \n * Google Chrome 37.0.2062.30 \n * Google Chrome 37.0.2062.32 \n * Google Chrome 37.0.2062.34 \n * Google Chrome 37.0.2062.36 \n * Google Chrome 37.0.2062.39 \n * Google Chrome 37.0.2062.43 \n * Google Chrome 37.0.2062.45 \n * Google Chrome 37.0.2062.47 \n * Google Chrome 37.0.2062.49 \n * Google Chrome 37.0.2062.50 \n * Google Chrome 37.0.2062.52 \n * Google Chrome 37.0.2062.54 \n * Google Chrome 37.0.2062.56 \n * Google Chrome 37.0.2062.58 \n * Google Chrome 37.0.2062.6 \n * Google Chrome 37.0.2062.61 \n * Google Chrome 37.0.2062.63 \n * Google Chrome 37.0.2062.65 \n * Google Chrome 37.0.2062.67 \n * Google Chrome 37.0.2062.69 \n * Google Chrome 37.0.2062.70 \n * Google Chrome 37.0.2062.72 \n * Google Chrome 37.0.2062.74 \n * Google Chrome 37.0.2062.76 \n * Google Chrome 37.0.2062.78 \n * Google Chrome 37.0.2062.80 \n * Google Chrome 37.0.2062.89 \n * Google Chrome 37.0.2062.90 \n * Google Chrome 37.0.2062.92 \n * Google Chrome 37.0.2062.94 \n * Google Chrome 37.0.2062.95 \n * Google Chrome 37.0.2062.97 \n * Google Chrome 38.0.2125.101 \n * Google Chrome 38.0.2125.101 ~~~Android~~ \n * Google Chrome 38.0.2125.122 \n * Google Chrome 39.0.2171.63 \n * Google Chrome 39.0.2171.65 \n * Google Chrome 4 \n * Google Chrome 4.0.211.0 \n * Google Chrome 4.0.212.0 \n * Google Chrome 4.0.212.1 \n * Google Chrome 4.0.221.8 \n * Google Chrome 4.0.222.0 \n * Google Chrome 4.0.222.1 \n * Google Chrome 4.0.222.12 \n * Google Chrome 4.0.222.5 \n * Google Chrome 4.0.223.0 \n * Google Chrome 4.0.223.1 \n * Google Chrome 4.0.223.2 \n * Google Chrome 4.0.223.4 \n * Google Chrome 4.0.223.5 \n * Google Chrome 4.0.223.7 \n * Google Chrome 4.0.223.8 \n * Google Chrome 4.0.224.0 \n * Google Chrome 4.0.229.1 \n * Google Chrome 4.0.235.0 \n * Google Chrome 4.0.236.0 \n * Google Chrome 4.0.237.0 \n * Google Chrome 4.0.237.1 \n * Google Chrome 4.0.239.0 \n * Google Chrome 4.0.240.0 \n * Google Chrome 4.0.241.0 \n * Google Chrome 4.0.242.0 \n * Google Chrome 4.0.243.0 \n * Google Chrome 4.0.244.0 \n * Google Chrome 4.0.245.0 \n * Google Chrome 4.0.246.0 \n * Google Chrome 4.0.247.0 \n * Google Chrome 4.0.248.0 \n * Google Chrome 4.0.249.0 \n * Google Chrome 4.0.249.1 \n * Google Chrome 4.0.249.10 \n * Google Chrome 4.0.249.11 \n * Google Chrome 4.0.249.12 \n * Google Chrome 4.0.249.14 \n * Google Chrome 4.0.249.16 \n * Google Chrome 4.0.249.17 \n * Google Chrome 4.0.249.18 \n * Google Chrome 4.0.249.19 \n * Google Chrome 4.0.249.2 \n * Google Chrome 4.0.249.20 \n * Google Chrome 4.0.249.21 \n * Google Chrome 4.0.249.22 \n * Google Chrome 4.0.249.23 \n * Google Chrome 4.0.249.24 \n * Google Chrome 4.0.249.25 \n * Google Chrome 4.0.249.26 \n * Google Chrome 4.0.249.27 \n * Google Chrome 4.0.249.28 \n * Google Chrome 4.0.249.29 \n * Google Chrome 4.0.249.3 \n * Google Chrome 4.0.249.30 \n * Google Chrome 4.0.249.31 \n * Google Chrome 4.0.249.32 \n * Google Chrome 4.0.249.33 \n * Google Chrome 4.0.249.34 \n * Google Chrome 4.0.249.35 \n * Google Chrome 4.0.249.36 \n * Google Chrome 4.0.249.37 \n * Google Chrome 4.0.249.38 \n * Google Chrome 4.0.249.39 \n * Google Chrome 4.0.249.4 \n * Google Chrome 4.0.249.40 \n * Google Chrome 4.0.249.41 \n * Google Chrome 4.0.249.42 \n * Google Chrome 4.0.249.43 \n * Google Chrome 4.0.249.44 \n * Google Chrome 4.0.249.45 \n * Google Chrome 4.0.249.46 \n * Google Chrome 4.0.249.47 \n * Google Chrome 4.0.249.48 \n * Google Chrome 4.0.249.49 \n * Google Chrome 4.0.249.5 \n * Google Chrome 4.0.249.50 \n * Google Chrome 4.0.249.51 \n * Google Chrome 4.0.249.52 \n * Google Chrome 4.0.249.53 \n * Google Chrome 4.0.249.54 \n * Google Chrome 4.0.249.55 \n * Google Chrome 4.0.249.56 \n * Google Chrome 4.0.249.57 \n * Google Chrome 4.0.249.58 \n * Google Chrome 4.0.249.59 \n * Google Chrome 4.0.249.6 \n * Google Chrome 4.0.249.60 \n * Google Chrome 4.0.249.61 \n * Google Chrome 4.0.249.62 \n * Google Chrome 4.0.249.63 \n * Google Chrome 4.0.249.64 \n * Google Chrome 4.0.249.65 \n * Google Chrome 4.0.249.66 \n * Google Chrome 4.0.249.67 \n * Google Chrome 4.0.249.68 \n * Google Chrome 4.0.249.69 \n * Google Chrome 4.0.249.7 \n * Google Chrome 4.0.249.70 \n * Google Chrome 4.0.249.71 \n * Google Chrome 4.0.249.72 \n * Google Chrome 4.0.249.73 \n * Google Chrome 4.0.249.74 \n * Google Chrome 4.0.249.75 \n * Google Chrome 4.0.249.76 \n * Google Chrome 4.0.249.77 \n * Google Chrome 4.0.249.78 \n * Google Chrome 4.0.249.78 Beta \n * Google Chrome 4.0.249.79 \n * Google Chrome 4.0.249.8 \n * Google Chrome 4.0.249.80 \n * Google Chrome 4.0.249.81 \n * Google Chrome 4.0.249.82 \n * Google Chrome 4.0.249.89 \n * Google Chrome 4.0.249.9 \n * Google Chrome 4.0.250.0 \n * Google Chrome 4.0.250.2 \n * Google Chrome 4.0.251.0 \n * Google Chrome 4.0.252.0 \n * Google Chrome 4.0.254.0 \n * Google Chrome 4.0.255.0 \n * Google Chrome 4.0.256.0 \n * Google Chrome 4.0.257.0 \n * Google Chrome 4.0.258.0 \n * Google Chrome 4.0.259.0 \n * Google Chrome 4.0.260.0 \n * Google Chrome 4.0.261.0 \n * Google Chrome 4.0.262.0 \n * Google Chrome 4.0.263.0 \n * Google Chrome 4.0.264.0 \n * Google Chrome 4.0.265.0 \n * Google Chrome 4.0.266.0 \n * Google Chrome 4.0.267.0 \n * Google Chrome 4.0.268.0 \n * Google Chrome 4.0.269.0 \n * Google Chrome 4.0.271.0 \n * Google Chrome 4.0.272.0 \n * Google Chrome 4.0.275.0 \n * Google Chrome 4.0.275.1 \n * Google Chrome 4.0.276.0 \n * Google Chrome 4.0.277.0 \n * Google Chrome 4.0.278.0 \n * Google Chrome 4.0.286.0 \n * Google Chrome 4.0.287.0 \n * Google Chrome 4.0.288.0 \n * Google Chrome 4.0.288.1 \n * Google Chrome 4.0.289.0 \n * Google Chrome 4.0.290.0 \n * Google Chrome 4.0.292.0 \n * Google Chrome 4.0.294.0 \n * Google Chrome 4.0.295.0 \n * Google Chrome 4.0.296.0 \n * Google Chrome 4.0.299.0 \n * Google Chrome 4.0.300.0 \n * Google Chrome 4.0.301.0 \n * Google Chrome 4.0.302.0 \n * Google Chrome 4.0.302.1 \n * Google Chrome 4.0.302.2 \n * Google Chrome 4.0.302.3 \n * Google Chrome 4.0.303.0 \n * Google Chrome 4.0.304.0 \n * Google Chrome 4.0.305.0 \n * Google Chrome 4.1 Beta \n * Google Chrome 4.1.249.0 \n * Google Chrome 4.1.249.1001 \n * Google Chrome 4.1.249.1004 \n * Google Chrome 4.1.249.1006 \n * Google Chrome 4.1.249.1007 \n * Google Chrome 4.1.249.1008 \n * Google Chrome 4.1.249.1009 \n * Google Chrome 4.1.249.1010 \n * Google Chrome 4.1.249.1011 \n * Google Chrome 4.1.249.1012 \n * Google Chrome 4.1.249.1013 \n * Google Chrome 4.1.249.1014 \n * Google Chrome 4.1.249.1015 \n * Google Chrome 4.1.249.1016 \n * Google Chrome 4.1.249.1017 \n * Google Chrome 4.1.249.1018 \n * Google Chrome 4.1.249.1019 \n * Google Chrome 4.1.249.1020 \n * Google Chrome 4.1.249.1021 \n * Google Chrome 4.1.249.1022 \n * Google Chrome 4.1.249.1023 \n * Google Chrome 4.1.249.1024 \n * Google Chrome 4.1.249.1025 \n * Google Chrome 4.1.249.1026 \n * Google Chrome 4.1.249.1027 \n * Google Chrome 4.1.249.1028 \n * Google Chrome 4.1.249.1029 \n * Google Chrome 4.1.249.1030 \n * Google Chrome 4.1.249.1031 \n * Google Chrome 4.1.249.1032 \n * Google Chrome 4.1.249.1033 \n * Google Chrome 4.1.249.1034 \n * Google Chrome 4.1.249.1035 \n * Google Chrome 4.1.249.1036 \n * Google Chrome 4.1.249.1037 \n * Google Chrome 4.1.249.1038 \n * Google Chrome 4.1.249.1039 \n * Google Chrome 4.1.249.1040 \n * Google Chrome 4.1.249.1041 \n * Google Chrome 4.1.249.1042 \n * Google Chrome 4.1.249.1043 \n * Google Chrome 4.1.249.1044 \n * Google Chrome 4.1.249.1045 \n * Google Chrome 4.1.249.1046 \n * Google Chrome 4.1.249.1047 \n * Google Chrome 4.1.249.1048 \n * Google Chrome 4.1.249.1049 \n * Google Chrome 4.1.249.1050 \n * Google Chrome 4.1.249.1051 \n * Google Chrome 4.1.249.1052 \n * Google Chrome 4.1.249.1053 \n * Google Chrome 4.1.249.1054 \n * Google Chrome 4.1.249.1055 \n * Google Chrome 4.1.249.1056 \n * Google Chrome 4.1.249.1057 \n * Google Chrome 4.1.249.1058 \n * Google Chrome 4.1.249.1059 \n * Google Chrome 4.1.249.1060 \n * Google Chrome 4.1.249.1061 \n * Google Chrome 4.1.249.1062 \n * Google Chrome 4.1.249.1063 \n * Google Chrome 4.1.249.1064 \n * Google Chrome 40.0.2214.111 \n * Google Chrome 40.0.2214.115 \n * Google Chrome 40.0.2214.85 \n * Google Chrome 40.0.2214.89 ~~~Android~~ \n * Google Chrome 40.0.2214.91 \n * Google Chrome 41.0.2272 \n * Google Chrome 41.0.2272.118 \n * Google Chrome 41.0.2272.76 \n * Google Chrome 42.0.2311 \n * Google Chrome 42.0.2311.135 \n * Google Chrome 42.0.2311.90 \n * Google Chrome 43.0.2357 \n * Google Chrome 43.0.2357.130 \n * Google Chrome 43.0.2357.65 \n * Google Chrome 44.0.2403 \n * Google Chrome 44.0.2403.157 \n * Google Chrome 44.0.2403.89 \n * Google Chrome 45.0.2454 \n * Google Chrome 45.0.2454.101 \n * Google Chrome 45.0.2454.85 \n * Google Chrome 46.0.2490 \n * Google Chrome 46.0.2490.71 \n * Google Chrome 46.0.2490.76 \n * Google Chrome 46.0.2490.86 \n * Google Chrome 47.0 \n * Google Chrome 47.0.2526.106 \n * Google Chrome 47.0.2526.73 \n * Google Chrome 47.0.2526.80 \n * Google Chrome 48.0.2564.109 \n * Google Chrome 48.0.2564.116 \n * Google Chrome 48.0.2564.82 \n * Google Chrome 49.0.2566.0 \n * Google Chrome 49.0.2623.108 \n * Google Chrome 49.0.2623.75 \n * Google Chrome 49.0.2623.87 \n * Google Chrome 5.0.306.0 \n * Google Chrome 5.0.306.1 \n * Google Chrome 5.0.307.1 \n * Google Chrome 5.0.307.10 \n * Google Chrome 5.0.307.11 \n * Google Chrome 5.0.307.3 \n * Google Chrome 5.0.307.4 \n * Google Chrome 5.0.307.5 \n * Google Chrome 5.0.307.6 \n * Google Chrome 5.0.307.7 \n * Google Chrome 5.0.307.8 \n * Google Chrome 5.0.307.9 \n * Google Chrome 5.0.308.0 \n * Google Chrome 5.0.309.0 \n * Google Chrome 5.0.313.0 \n * Google Chrome 5.0.314.0 \n * Google Chrome 5.0.314.1 \n * Google Chrome 5.0.315.0 \n * Google Chrome 5.0.316.0 \n * Google Chrome 5.0.317.0 \n * Google Chrome 5.0.317.1 \n * Google Chrome 5.0.317.2 \n * Google Chrome 5.0.318.0 \n * Google Chrome 5.0.319.0 \n * Google Chrome 5.0.320.0 \n * Google Chrome 5.0.321.0 \n * Google Chrome 5.0.322.0 \n * Google Chrome 5.0.322.1 \n * Google Chrome 5.0.322.2 \n * Google Chrome 5.0.323.0 \n * Google Chrome 5.0.324.0 \n * Google Chrome 5.0.325.0 \n * Google Chrome 5.0.326.0 \n * Google Chrome 5.0.327.0 \n * Google Chrome 5.0.328.0 \n * Google Chrome 5.0.329.0 \n * Google Chrome 5.0.330.0 \n * Google Chrome 5.0.332.0 \n * Google Chrome 5.0.333.0 \n * Google Chrome 5.0.334.0 \n * Google Chrome 5.0.335.0 \n * Google Chrome 5.0.335.1 \n * Google Chrome 5.0.335.2 \n * Google Chrome 5.0.335.3 \n * Google Chrome 5.0.335.4 \n * Google Chrome 5.0.336.0 \n * Google Chrome 5.0.337.0 \n * Google Chrome 5.0.338.0 \n * Google Chrome 5.0.339.0 \n * Google Chrome 5.0.340.0 \n * Google Chrome 5.0.341.0 \n * Google Chrome 5.0.342.0 \n * Google Chrome 5.0.342.1 \n * Google Chrome 5.0.342.2 \n * Google Chrome 5.0.342.3 \n * Google Chrome 5.0.342.4 \n * Google Chrome 5.0.342.5 \n * Google Chrome 5.0.342.6 \n * Google Chrome 5.0.342.7 \n * Google Chrome 5.0.342.7 Beta Mac \n * Google Chrome 5.0.342.8 \n * Google Chrome 5.0.342.9 \n * Google Chrome 5.0.343.0 \n * Google Chrome 5.0.344.0 \n * Google Chrome 5.0.345.0 \n * Google Chrome 5.0.346.0 \n * Google Chrome 5.0.347.0 \n * Google Chrome 5.0.348.0 \n * Google Chrome 5.0.349.0 \n * Google Chrome 5.0.350.0 \n * Google Chrome 5.0.350.1 \n * Google Chrome 5.0.351.0 \n * Google Chrome 5.0.353.0 \n * Google Chrome 5.0.354.0 \n * Google Chrome 5.0.354.1 \n * Google Chrome 5.0.355.0 \n * Google Chrome 5.0.356.0 \n * Google Chrome 5.0.356.1 \n * Google Chrome 5.0.356.2 \n * Google Chrome 5.0.357.0 \n * Google Chrome 5.0.358.0 \n * Google Chrome 5.0.359.0 \n * Google Chrome 5.0.360.0 \n * Google Chrome 5.0.360.3 \n * Google Chrome 5.0.360.4 \n * Google Chrome 5.0.360.5 \n * Google Chrome 5.0.361.0 \n * Google Chrome 5.0.362.0 \n * Google Chrome 5.0.363.0 \n * Google Chrome 5.0.364.0 \n * Google Chrome 5.0.365.0 \n * Google Chrome 5.0.366.0 \n * Google Chrome 5.0.366.1 \n * Google Chrome 5.0.366.2 \n * Google Chrome 5.0.366.3 \n * Google Chrome 5.0.366.4 \n * Google Chrome 5.0.367.0 \n * Google Chrome 5.0.368.0 \n * Google Chrome 5.0.369.0 \n * Google Chrome 5.0.369.1 \n * Google Chrome 5.0.369.2 \n * Google Chrome 5.0.370.0 \n * Google Chrome 5.0.371.0 \n * Google Chrome 5.0.372.0 \n * Google Chrome 5.0.373.0 \n * Google Chrome 5.0.374.0 \n * Google Chrome 5.0.375.0 \n * Google Chrome 5.0.375.1 \n * Google Chrome 5.0.375.10 \n * Google Chrome 5.0.375.11 \n * Google Chrome 5.0.375.12 \n * Google Chrome 5.0.375.125 \n * Google Chrome 5.0.375.126 \n * Google Chrome 5.0.375.127 \n * Google Chrome 5.0.375.13 \n * Google Chrome 5.0.375.14 \n * Google Chrome 5.0.375.15 \n * Google Chrome 5.0.375.16 \n * Google Chrome 5.0.375.17 \n * Google Chrome 5.0.375.18 \n * Google Chrome 5.0.375.19 \n * Google Chrome 5.0.375.2 \n * Google Chrome 5.0.375.20 \n * Google Chrome 5.0.375.21 \n * Google Chrome 5.0.375.22 \n * Google Chrome 5.0.375.23 \n * Google Chrome 5.0.375.25 \n * Google Chrome 5.0.375.26 \n * Google Chrome 5.0.375.27 \n * Google Chrome 5.0.375.28 \n * Google Chrome 5.0.375.29 \n * Google Chrome 5.0.375.3 \n * Google Chrome 5.0.375.30 \n * Google Chrome 5.0.375.31 \n * Google Chrome 5.0.375.32 \n * Google Chrome 5.0.375.33 \n * Google Chrome 5.0.375.34 \n * Google Chrome 5.0.375.35 \n * Google Chrome 5.0.375.36 \n * Google Chrome 5.0.375.37 \n * Google Chrome 5.0.375.38 \n * Google Chrome 5.0.375.39 \n * Google Chrome 5.0.375.4 \n * Google Chrome 5.0.375.40 \n * Google Chrome 5.0.375.41 \n * Google Chrome 5.0.375.42 \n * Google Chrome 5.0.375.43 \n * Google Chrome 5.0.375.44 \n * Google Chrome 5.0.375.45 \n * Google Chrome 5.0.375.46 \n * Google Chrome 5.0.375.47 \n * Google Chrome 5.0.375.48 \n * Google Chrome 5.0.375.49 \n * Google Chrome 5.0.375.5 \n * Google Chrome 5.0.375.50 \n * Google Chrome 5.0.375.51 \n * Google Chrome 5.0.375.52 \n * Google Chrome 5.0.375.53 \n * Google Chrome 5.0.375.54 \n * Google Chrome 5.0.375.55 \n * Google Chrome 5.0.375.56 \n * Google Chrome 5.0.375.57 \n * Google Chrome 5.0.375.58 \n * Google Chrome 5.0.375.59 \n * Google Chrome 5.0.375.6 \n * Google Chrome 5.0.375.60 \n * Google Chrome 5.0.375.61 \n * Google Chrome 5.0.375.62 \n * Google Chrome 5.0.375.63 \n * Google Chrome 5.0.375.64 \n * Google Chrome 5.0.375.65 \n * Google Chrome 5.0.375.66 \n * Google Chrome 5.0.375.67 \n * Google Chrome 5.0.375.68 \n * Google Chrome 5.0.375.69 \n * Google Chrome 5.0.375.7 \n * Google Chrome 5.0.375.70 \n * Google Chrome 5.0.375.71 \n * Google Chrome 5.0.375.72 \n * Google Chrome 5.0.375.73 \n * Google Chrome 5.0.375.74 \n * Google Chrome 5.0.375.75 \n * Google Chrome 5.0.375.76 \n * Google Chrome 5.0.375.77 \n * Google Chrome 5.0.375.78 \n * Google Chrome 5.0.375.79 \n * Google Chrome 5.0.375.8 \n * Google Chrome 5.0.375.80 \n * Google Chrome 5.0.375.81 \n * Google Chrome 5.0.375.82 \n * Google Chrome 5.0.375.83 \n * Google Chrome 5.0.375.84 \n * Google Chrome 5.0.375.85 \n * Google Chrome 5.0.375.86 \n * Google Chrome 5.0.375.87 \n * Google Chrome 5.0.375.88 \n * Google Chrome 5.0.375.89 \n * Google Chrome 5.0.375.9 \n * Google Chrome 5.0.375.90 \n * Google Chrome 5.0.375.91 \n * Google Chrome 5.0.375.92 \n * Google Chrome 5.0.375.93 \n * Google Chrome 5.0.375.94 \n * Google Chrome 5.0.375.95 \n * Google Chrome 5.0.375.96 \n * Google Chrome 5.0.375.97 \n * Google Chrome 5.0.375.98 \n * Google Chrome 5.0.375.99 \n * Google Chrome 5.0.376.0 \n * Google Chrome 5.0.378.0 \n * Google Chrome 5.0.379.0 \n * Google Chrome 5.0.380.0 \n * Google Chrome 5.0.381.0 \n * Google Chrome 5.0.382.0 \n * Google Chrome 5.0.382.3 \n * Google Chrome 5.0.383.0 \n * Google Chrome 5.0.384.0 \n * Google Chrome 5.0.385.0 \n * Google Chrome 5.0.386.0 \n * Google Chrome 5.0.387.0 \n * Google Chrome 5.0.390.0 \n * Google Chrome 5.0.391.0 \n * Google Chrome 5.0.392.0 \n * Google Chrome 5.0.393.0 \n * Google Chrome 5.0.394.0 \n * Google Chrome 5.0.395.0 \n * Google Chrome 5.0.396.0 \n * Google Chrome 50.0.2661.102 \n * Google Chrome 50.0.2661.75 \n * Google Chrome 50.0.2661.94 \n * Google Chrome 51.0.2704.103 \n * Google Chrome 51.0.2704.63 \n * Google Chrome 51.0.2704.79 \n * Google Chrome 52.0.2743.116 \n * Google Chrome 52.0.2743.82 \n * Google Chrome 53.0.2785.113 \n * Google Chrome 53.0.2785.143 \n * Google Chrome 53.0.2785.89 \n * Google Chrome 54.0.2840.59 \n * Google Chrome 54.0.2840.85 \n * Google Chrome 54.0.2840.87 \n * Google Chrome 54.0.2840.90 \n * Google Chrome 54.0.2840.98 \n * Google Chrome 54.0.2840.99 \n * Google Chrome 55.0.2883.75 \n * Google Chrome 56.0.2924.76 \n * Google Chrome 57.0.2987.133 \n * Google Chrome 57.0.2987.98 \n * Google Chrome 58.0.3029.81 \n * Google Chrome 58.0.3029.96 \n * Google Chrome 59.0.3071.104 \n * Google Chrome 59.0.3071.115 \n * Google Chrome 59.0.3071.86 \n * Google Chrome 6.0.397.0 \n * Google Chrome 6.0.398.0 \n * Google Chrome 6.0.399.0 \n * Google Chrome 6.0.400.0 \n * Google Chrome 6.0.401.0 \n * Google Chrome 6.0.401.1 \n * Google Chrome 6.0.403.0 \n * Google Chrome 6.0.404.0 \n * Google Chrome 6.0.404.1 \n * Google Chrome 6.0.404.2 \n * Google Chrome 6.0.405.0 \n * Google Chrome 6.0.406.0 \n * Google Chrome 6.0.407.0 \n * Google Chrome 6.0.408.0 \n * Google Chrome 6.0.408.1 \n * Google Chrome 6.0.408.10 \n * Google Chrome 6.0.408.2 \n * Google Chrome 6.0.408.3 \n * Google Chrome 6.0.408.4 \n * Google Chrome 6.0.408.5 \n * Google Chrome 6.0.408.6 \n * Google Chrome 6.0.408.7 \n * Google Chrome 6.0.408.8 \n * Google Chrome 6.0.408.9 \n * Google Chrome 6.0.409.0 \n * Google Chrome 6.0.410.0 \n * Google Chrome 6.0.411.0 \n * Google Chrome 6.0.412.0 \n * Google Chrome 6.0.413.0 \n * Google Chrome 6.0.414.0 \n * Google Chrome 6.0.415.0 \n * Google Chrome 6.0.415.1 \n * Google Chrome 6.0.416.0 \n * Google Chrome 6.0.416.1 \n * Google Chrome 6.0.417.0 \n * Google Chrome 6.0.418.0 \n * Google Chrome 6.0.418.1 \n * Google Chrome 6.0.418.2 \n * Google Chrome 6.0.418.3 \n * Google Chrome 6.0.418.4 \n * Google Chrome 6.0.418.5 \n * Google Chrome 6.0.418.6 \n * Google Chrome 6.0.418.7 \n * Google Chrome 6.0.418.8 \n * Google Chrome 6.0.418.9 \n * Google Chrome 6.0.419.0 \n * Google Chrome 6.0.421.0 \n * Google Chrome 6.0.422.0 \n * Google Chrome 6.0.423.0 \n * Google Chrome 6.0.424.0 \n * Google Chrome 6.0.425.0 \n * Google Chrome 6.0.426.0 \n * Google Chrome 6.0.427.0 \n * Google Chrome 6.0.428.0 \n * Google Chrome 6.0.430.0 \n * Google Chrome 6.0.431.0 \n * Google Chrome 6.0.432.0 \n * Google Chrome 6.0.433.0 \n * Google Chrome 6.0.434.0 \n * Google Chrome 6.0.435.0 \n * Google Chrome 6.0.436.0 \n * Google Chrome 6.0.437.0 \n * Google Chrome 6.0.437.1 \n * Google Chrome 6.0.437.2 \n * Google Chrome 6.0.437.3 \n * Google Chrome 6.0.438.0 \n * Google Chrome 6.0.440.0 \n * Google Chrome 6.0.441.0 \n * Google Chrome 6.0.443.0 \n * Google Chrome 6.0.444.0 \n * Google Chrome 6.0.445.0 \n * Google Chrome 6.0.445.1 \n * Google Chrome 6.0.446.0 \n * Google Chrome 6.0.447.0 \n * Google Chrome 6.0.447.1 \n * Google Chrome 6.0.447.2 \n * Google Chrome 6.0.449.0 \n * Google Chrome 6.0.450.0 \n * Google Chrome 6.0.450.1 \n * Google Chrome 6.0.450.2 \n * Google Chrome 6.0.450.3 \n * Google Chrome 6.0.450.4 \n * Google Chrome 6.0.451.0 \n * Google Chrome 6.0.452.0 \n * Google Chrome 6.0.452.1 \n * Google Chrome 6.0.453.0 \n * Google Chrome 6.0.453.1 \n * Google Chrome 6.0.454.0 \n * Google Chrome 6.0.455.0 \n * Google Chrome 6.0.456.0 \n * Google Chrome 6.0.457.0 \n * Google Chrome 6.0.458.0 \n * Google Chrome 6.0.458.1 \n * Google Chrome 6.0.458.2 \n * Google Chrome 6.0.459.0 \n * Google Chrome 6.0.460.0 \n * Google Chrome 6.0.461.0 \n * Google Chrome 6.0.462.0 \n * Google Chrome 6.0.464.1 \n * Google Chrome 6.0.465.1 \n * Google Chrome 6.0.465.2 \n * Google Chrome 6.0.466.0 \n * Google Chrome 6.0.466.1 \n * Google Chrome 6.0.466.2 \n * Google Chrome 6.0.466.3 \n * Google Chrome 6.0.466.4 \n * Google Chrome 6.0.466.5 \n * Google Chrome 6.0.466.6 \n * Google Chrome 6.0.467.0 \n * Google Chrome 6.0.469.0 \n * Google Chrome 6.0.470.0 \n * Google Chrome 6.0.471.0 \n * Google Chrome 6.0.472.0 \n * Google Chrome 6.0.472.1 \n * Google Chrome 6.0.472.10 \n * Google Chrome 6.0.472.11 \n * Google Chrome 6.0.472.12 \n * Google Chrome 6.0.472.13 \n * Google Chrome 6.0.472.14 \n * Google Chrome 6.0.472.15 \n * Google Chrome 6.0.472.16 \n * Google Chrome 6.0.472.17 \n * Google Chrome 6.0.472.18 \n * Google Chrome 6.0.472.19 \n * Google Chrome 6.0.472.2 \n * Google Chrome 6.0.472.20 \n * Google Chrome 6.0.472.21 \n * Google Chrome 6.0.472.22 \n * Google Chrome 6.0.472.23 \n * Google Chrome 6.0.472.24 \n * Google Chrome 6.0.472.25 \n * Google Chrome 6.0.472.26 \n * Google Chrome 6.0.472.27 \n * Google Chrome 6.0.472.28 \n * Google Chrome 6.0.472.29 \n * Google Chrome 6.0.472.3 \n * Google Chrome 6.0.472.30 \n * Google Chrome 6.0.472.31 \n * Google Chrome 6.0.472.32 \n * Google Chrome 6.0.472.33 \n * Google Chrome 6.0.472.34 \n * Google Chrome 6.0.472.35 \n * Google Chrome 6.0.472.36 \n * Google Chrome 6.0.472.37 \n * Google Chrome 6.0.472.38 \n * Google Chrome 6.0.472.39 \n * Google Chrome 6.0.472.4 \n * Google Chrome 6.0.472.40 \n * Google Chrome 6.0.472.41 \n * Google Chrome 6.0.472.42 \n * Google Chrome 6.0.472.43 \n * Google Chrome 6.0.472.44 \n * Google Chrome 6.0.472.45 \n * Google Chrome 6.0.472.46 \n * Google Chrome 6.0.472.47 \n * Google Chrome 6.0.472.48 \n * Google Chrome 6.0.472.49 \n * Google Chrome 6.0.472.5 \n * Google Chrome 6.0.472.50 \n * Google Chrome 6.0.472.51 \n * Google Chrome 6.0.472.52 \n * Google Chrome 6.0.472.53 \n * Google Chrome 6.0.472.54 \n * Google Chrome 6.0.472.55 \n * Google Chrome 6.0.472.56 \n * Google Chrome 6.0.472.57 \n * Google Chrome 6.0.472.58 \n * Google Chrome 6.0.472.59 \n * Google Chrome 6.0.472.6 \n * Google Chrome 6.0.472.60 \n * Google Chrome 6.0.472.61 \n * Google Chrome 6.0.472.62 \n * Google Chrome 6.0.472.63 \n * Google Chrome 6.0.472.7 \n * Google Chrome 6.0.472.8 \n * Google Chrome 6.0.472.9 \n * Google Chrome 6.0.473.0 \n * Google Chrome 6.0.474.0 \n * Google Chrome 6.0.475.0 \n * Google Chrome 6.0.476.0 \n * Google Chrome 6.0.477.0 \n * Google Chrome 6.0.478.0 \n * Google Chrome 6.0.479.0 \n * Google Chrome 6.0.480.0 \n * Google Chrome 6.0.481.0 \n * Google Chrome 6.0.482.0 \n * Google Chrome 6.0.483.0 \n * Google Chrome 6.0.484.0 \n * Google Chrome 6.0.485.0 \n * Google Chrome 6.0.486.0 \n * Google Chrome 6.0.487.0 \n * Google Chrome 6.0.488.0 \n * Google Chrome 6.0.489.0 \n * Google Chrome 6.0.490.0 \n * Google Chrome 6.0.490.1 \n * Google Chrome 6.0.491.0 \n * Google Chrome 6.0.492.0 \n * Google Chrome 6.0.493.0 \n * Google Chrome 6.0.494.0 \n * Google Chrome 6.0.495.0 \n * Google Chrome 6.0.495.1 \n * Google Chrome 6.0.496.0 \n * Google Chrome 60.0.3080.5 \n * Google Chrome 60.0.3112.78 \n * Google Chrome 60.0.3112.80 \n * Google Chrome 61.0.3163.100 \n * Google Chrome 61.0.3163.79 \n * Google Chrome 62.0.3202.62 \n * Google Chrome 62.0.3202.75 \n * Google Chrome 62.0.3202.89 \n * Google Chrome 64 \n * Google Chrome 65 \n * Google Chrome 65.72 \n * Google Chrome 7.0.497.0 \n * Google Chrome 7.0.498.0 \n * Google Chrome 7.0.499.0 \n * Google Chrome 7.0.499.1 \n * Google Chrome 7.0.500.0 \n * Google Chrome 7.0.500.1 \n * Google Chrome 7.0.503.0 \n * Google Chrome 7.0.503.1 \n * Google Chrome 7.0.504.0 \n * Google Chrome 7.0.505.0 \n * Google Chrome 7.0.506.0 \n * Google Chrome 7.0.507.0 \n * Google Chrome 7.0.507.1 \n * Google Chrome 7.0.507.2 \n * Google Chrome 7.0.507.3 \n * Google Chrome 7.0.509.0 \n * Google Chrome 7.0.510.0 \n * Google Chrome 7.0.511.1 \n * Google Chrome 7.0.511.2 \n * Google Chrome 7.0.511.4 \n * Google Chrome 7.0.512.0 \n * Google Chrome 7.0.513.0 \n * Google Chrome 7.0.514.0 \n * Google Chrome 7.0.514.1 \n * Google Chrome 7.0.515.0 \n * Google Chrome 7.0.516.0 \n * Google Chrome 7.0.517.0 \n * Google Chrome 7.0.517.10 \n * Google Chrome 7.0.517.11 \n * Google Chrome 7.0.517.12 \n * Google Chrome 7.0.517.13 \n * Google Chrome 7.0.517.14 \n * Google Chrome 7.0.517.16 \n * Google Chrome 7.0.517.17 \n * Google Chrome 7.0.517.18 \n * Google Chrome 7.0.517.19 \n * Google Chrome 7.0.517.2 \n * Google Chrome 7.0.517.20 \n * Google Chrome 7.0.517.21 \n * Google Chrome 7.0.517.22 \n * Google Chrome 7.0.517.23 \n * Google Chrome 7.0.517.24 \n * Google Chrome 7.0.517.25 \n * Google Chrome 7.0.517.26 \n * Google Chrome 7.0.517.27 \n * Google Chrome 7.0.517.28 \n * Google Chrome 7.0.517.29 \n * Google Chrome 7.0.517.30 \n * Google Chrome 7.0.517.31 \n * Google Chrome 7.0.517.32 \n * Google Chrome 7.0.517.33 \n * Google Chrome 7.0.517.34 \n * Google Chrome 7.0.517.35 \n * Google Chrome 7.0.517.36 \n * Google Chrome 7.0.517.37 \n * Google Chrome 7.0.517.38 \n * Google Chrome 7.0.517.39 \n * Google Chrome 7.0.517.4 \n * Google Chrome 7.0.517.40 \n * Google Chrome 7.0.517.41 \n * Google Chrome 7.0.517.42 \n * Google Chrome 7.0.517.43 \n * Google Chrome 7.0.517.44 \n * Google Chrome 7.0.517.5 \n * Google Chrome 7.0.517.6 \n * Google Chrome 7.0.517.7 \n * Google Chrome 7.0.517.8 \n * Google Chrome 7.0.517.9 \n * Google Chrome 7.0.518.0 \n * Google Chrome 7.0.519.0 \n * Google Chrome 7.0.520.0 \n * Google Chrome 7.0.521.0 \n * Google Chrome 7.0.522.0 \n * Google Chrome 7.0.524.0 \n * Google Chrome 7.0.525.0 \n * Google Chrome 7.0.526.0 \n * Google Chrome 7.0.528.0 \n * Google Chrome 7.0.529.0 \n * Google Chrome 7.0.529.1 \n * Google Chrome 7.0.529.2 \n * Google Chrome 7.0.530.0 \n * Google Chrome 7.0.531.0 \n * Google Chrome 7.0.531.1 \n * Google Chrome 7.0.531.2 \n * Google Chrome 7.0.535.1 \n * Google Chrome 7.0.535.2 \n * Google Chrome 7.0.536.0 \n * Google Chrome 7.0.536.1 \n * Google Chrome 7.0.536.2 \n * Google Chrome 7.0.536.3 \n * Google Chrome 7.0.536.4 \n * Google Chrome 7.0.537.0 \n * Google Chrome 7.0.538.0 \n * Google Chrome 7.0.539.0 \n * Google Chrome 7.0.540.0 \n * Google Chrome 7.0.541.0 \n * Google Chrome 7.0.542.0 \n * Google Chrome 7.0.544.0 \n * Google Chrome 7.0.547.0 \n * Google Chrome 7.0.547.1 \n * Google Chrome 7.0.548.0 \n * Google Chrome 8.0.549.0 \n * Google Chrome 8.0.550.0 \n * Google Chrome 8.0.551.0 \n * Google Chrome 8.0.551.1 \n * Google Chrome 8.0.552.0 \n * Google Chrome 8.0.552.1 \n * Google Chrome 8.0.552.10 \n * Google Chrome 8.0.552.100 \n * Google Chrome 8.0.552.101 \n * Google Chrome 8.0.552.102 \n * Google Chrome 8.0.552.103 \n * Google Chrome 8.0.552.104 \n * Google Chrome 8.0.552.105 \n * Google Chrome 8.0.552.11 \n * Google Chrome 8.0.552.12 \n * Google Chrome 8.0.552.13 \n * Google Chrome 8.0.552.14 \n * Google Chrome 8.0.552.15 \n * Google Chrome 8.0.552.16 \n * Google Chrome 8.0.552.17 \n * Google Chrome 8.0.552.18 \n * Google Chrome 8.0.552.19 \n * Google Chrome 8.0.552.2 \n * Google Chrome 8.0.552.20 \n * Google Chrome 8.0.552.200 \n * Google Chrome 8.0.552.201 \n * Google Chrome 8.0.552.202 \n * Google Chrome 8.0.552.203 \n * Google Chrome 8.0.552.204 \n * Google Chrome 8.0.552.205 \n * Google Chrome 8.0.552.206 \n * Google Chrome 8.0.552.207 \n * Google Chrome 8.0.552.208 \n * Google Chrome 8.0.552.209 \n * Google Chrome 8.0.552.21 \n * Google Chrome 8.0.552.210 \n * Google Chrome 8.0.552.211 \n * Google Chrome 8.0.552.212 \n * Google Chrome 8.0.552.213 \n * Google Chrome 8.0.552.214 \n * Google Chrome 8.0.552.215 \n * Google Chrome 8.0.552.216 \n * Google Chrome 8.0.552.217 \n * Google Chrome 8.0.552.218 \n * Google Chrome 8.0.552.219 \n * Google Chrome 8.0.552.220 \n * Google Chrome 8.0.552.221 \n * Google Chrome 8.0.552.222 \n * Google Chrome 8.0.552.223 \n * Google Chrome 8.0.552.224 \n * Google Chrome 8.0.552.225 \n * Google Chrome 8.0.552.226 \n * Google Chrome 8.0.552.227 \n * Google Chrome 8.0.552.228 \n * Google Chrome 8.0.552.229 \n * Google Chrome 8.0.552.23 \n * Google Chrome 8.0.552.230 \n * Google Chrome 8.0.552.231 \n * Google Chrome 8.0.552.232 \n * Google Chrome 8.0.552.233 \n * Google Chrome 8.0.552.234 \n * Google Chrome 8.0.552.235 \n * Google Chrome 8.0.552.237 \n * Google Chrome 8.0.552.24 \n * Google Chrome 8.0.552.25 \n * Google Chrome 8.0.552.26 \n * Google Chrome 8.0.552.27 \n * Google Chrome 8.0.552.28 \n * Google Chrome 8.0.552.29 \n * Google Chrome 8.0.552.300 \n * Google Chrome 8.0.552.301 \n * Google Chrome 8.0.552.302 \n * Google Chrome 8.0.552.303 \n * Google Chrome 8.0.552.304 \n * Google Chrome 8.0.552.305 \n * Google Chrome 8.0.552.306 \n * Google Chrome 8.0.552.307 \n * Google Chrome 8.0.552.308 \n * Google Chrome 8.0.552.309 \n * Google Chrome 8.0.552.310 \n * Google Chrome 8.0.552.311 \n * Google Chrome 8.0.552.312 \n * Google Chrome 8.0.552.313 \n * Google Chrome 8.0.552.315 \n * Google Chrome 8.0.552.316 \n * Google Chrome 8.0.552.317 \n * Google Chrome 8.0.552.318 \n * Google Chrome 8.0.552.319 \n * Google Chrome 8.0.552.320 \n * Google Chrome 8.0.552.321 \n * Google Chrome 8.0.552.322 \n * Google Chrome 8.0.552.323 \n * Google Chrome 8.0.552.324 \n * Google Chrome 8.0.552.325 \n * Google Chrome 8.0.552.326 \n * Google Chrome 8.0.552.327 \n * Google Chrome 8.0.552.328 \n * Google Chrome 8.0.552.329 \n * Google Chrome 8.0.552.330 \n * Google Chrome 8.0.552.331 \n * Google Chrome 8.0.552.332 \n * Google Chrome 8.0.552.333 \n * Google Chrome 8.0.552.334 \n * Google Chrome 8.0.552.335 \n * Google Chrome 8.0.552.336 \n * Google Chrome 8.0.552.337 \n * Google Chrome 8.0.552.338 \n * Google Chrome 8.0.552.339 \n * Google Chrome 8.0.552.340 \n * Google Chrome 8.0.552.341 \n * Google Chrome 8.0.552.342 \n * Google Chrome 8.0.552.343 \n * Google Chrome 8.0.552.344 \n * Google Chrome 8.0.552.35 \n * Google Chrome 8.0.552.4 \n * Google Chrome 8.0.552.40 \n * Google Chrome 8.0.552.41 \n * Google Chrome 8.0.552.42 \n * Google Chrome 8.0.552.43 \n * Google Chrome 8.0.552.44 \n * Google Chrome 8.0.552.45 \n * Google Chrome 8.0.552.47 \n * Google Chrome 8.0.552.48 \n * Google Chrome 8.0.552.49 \n * Google Chrome 8.0.552.5 \n * Google Chrome 8.0.552.50 \n * Google Chrome 8.0.552.51 \n * Google Chrome 8.0.552.52 \n * Google Chrome 8.0.552.6 \n * Google Chrome 8.0.552.7 \n * Google Chrome 8.0.552.8 \n * Google Chrome 8.0.552.9 \n * Google Chrome 8.0.553.0 \n * Google Chrome 8.0.554.0 \n * Google Chrome 8.0.556.0 \n * Google Chrome 8.0.557.0 \n * Google Chrome 8.0.558.0 \n * Google Chrome 8.0.559.0 \n * Google Chrome 8.0.560.0 \n * Google Chrome 8.0.561.0 \n * Google Chrome 9 \n * Google Chrome 9.0.562.0 \n * Google Chrome 9.0.563.0 \n * Google Chrome 9.0.564.0 \n * Google Chrome 9.0.565.0 \n * Google Chrome 9.0.566.0 \n * Google Chrome 9.0.567.0 \n * Google Chrome 9.0.568.0 \n * Google Chrome 9.0.569.0 \n * Google Chrome 9.0.570.0 \n * Google Chrome 9.0.570.1 \n * Google Chrome 9.0.571.0 \n * Google Chrome 9.0.572.0 \n * Google Chrome 9.0.572.1 \n * Google Chrome 9.0.573.0 \n * Google Chrome 9.0.574.0 \n * Google Chrome 9.0.575.0 \n * Google Chrome 9.0.576.0 \n * Google Chrome 9.0.577.0 \n * Google Chrome 9.0.578.0 \n * Google Chrome 9.0.579.0 \n * Google Chrome 9.0.580.0 \n * Google Chrome 9.0.581.0 \n * Google Chrome 9.0.582.0 \n * Google Chrome 9.0.583.0 \n * Google Chrome 9.0.584.0 \n * Google Chrome 9.0.585.0 \n * Google Chrome 9.0.586.0 \n * Google Chrome 9.0.587.0 \n * Google Chrome 9.0.587.1 \n * Google Chrome 9.0.588.0 \n * Google Chrome 9.0.589.0 \n * Google Chrome 9.0.590.0 \n * Google Chrome 9.0.591.0 \n * Google Chrome 9.0.592.0 \n * Google Chrome 9.0.593.0 \n * Google Chrome 9.0.594.0 \n * Google Chrome 9.0.595.0 \n * Google Chrome 9.0.596.0 \n * Google Chrome 9.0.597.0 \n * Google Chrome 9.0.597.1 \n * Google Chrome 9.0.597.10 \n * Google Chrome 9.0.597.100 \n * Google Chrome 9.0.597.101 \n * Google Chrome 9.0.597.102 \n * Google Chrome 9.0.597.106 \n * Google Chrome 9.0.597.107 \n * Google Chrome 9.0.597.11 \n * Google Chrome 9.0.597.12 \n * Google Chrome 9.0.597.14 \n * Google Chrome 9.0.597.15 \n * Google Chrome 9.0.597.16 \n * Google Chrome 9.0.597.17 \n * Google Chrome 9.0.597.18 \n * Google Chrome 9.0.597.19 \n * Google Chrome 9.0.597.2 \n * Google Chrome 9.0.597.20 \n * Google Chrome 9.0.597.21 \n * Google Chrome 9.0.597.22 \n * Google Chrome 9.0.597.23 \n * Google Chrome 9.0.597.24 \n * Google Chrome 9.0.597.25 \n * Google Chrome 9.0.597.26 \n * Google Chrome 9.0.597.27 \n * Google Chrome 9.0.597.28 \n * Google Chrome 9.0.597.29 \n * Google Chrome 9.0.597.30 \n * Google Chrome 9.0.597.31 \n * Google Chrome 9.0.597.32 \n * Google Chrome 9.0.597.33 \n * Google Chrome 9.0.597.34 \n * Google Chrome 9.0.597.35 \n * Google Chrome 9.0.597.36 \n * Google Chrome 9.0.597.37 \n * Google Chrome 9.0.597.38 \n * Google Chrome 9.0.597.39 \n * Google Chrome 9.0.597.4 \n * Google Chrome 9.0.597.40 \n * Google Chrome 9.0.597.41 \n * Google Chrome 9.0.597.42 \n * Google Chrome 9.0.597.44 \n * Google Chrome 9.0.597.45 \n * Google Chrome 9.0.597.46 \n * Google Chrome 9.0.597.47 \n * Google Chrome 9.0.597.5 \n * Google Chrome 9.0.597.54 \n * Google Chrome 9.0.597.55 \n * Google Chrome 9.0.597.56 \n * Google Chrome 9.0.597.57 \n * Google Chrome 9.0.597.58 \n * Google Chrome 9.0.597.59 \n * Google Chrome 9.0.597.60 \n * Google Chrome 9.0.597.62 \n * Google Chrome 9.0.597.63 \n * Google Chrome 9.0.597.64 \n * Google Chrome 9.0.597.65 \n * Google Chrome 9.0.597.66 \n * Google Chrome 9.0.597.67 \n * Google Chrome 9.0.597.68 \n * Google Chrome 9.0.597.69 \n * Google Chrome 9.0.597.7 \n * Google Chrome 9.0.597.70 \n * Google Chrome 9.0.597.71 \n * Google Chrome 9.0.597.72 \n * Google Chrome 9.0.597.73 \n * Google Chrome 9.0.597.74 \n * Google Chrome 9.0.597.75 \n * Google Chrome 9.0.597.76 \n * Google Chrome 9.0.597.77 \n * Google Chrome 9.0.597.78 \n * Google Chrome 9.0.597.79 \n * Google Chrome 9.0.597.96 \n * Google Chrome 9.0.597.97 \n * Google Chrome 9.0.597.98 \n * Google Chrome 9.0.597.99 \n * Google Chrome 9.0.598.0 \n * Google Chrome 9.0.599.0 \n * Google Chrome 9.0.600.0 \n * Google Chrome OS 0.10.140.0 \n * Google Chrome OS 0.9.110.6 \n * Google Chrome OS 0.9.126.0 \n * Google Chrome OS 0.9.128.3 \n * Google Chrome OS 0.9.130.14 Beta \n * Google Chrome OS 0.9.131.0 \n * Google Chrome OS 0.9.134.14 \n * Google Chrome OS 20.0.1132.0 \n * Google Chrome OS 20.0.1132.1 \n * Google Chrome OS 20.0.1132.10 \n * Google Chrome OS 20.0.1132.11 \n * Google Chrome OS 20.0.1132.12 \n * Google Chrome OS 20.0.1132.13 \n * Google Chrome OS 20.0.1132.14 \n * Google Chrome OS 20.0.1132.15 \n * Google Chrome OS 20.0.1132.16 \n * Google Chrome OS 20.0.1132.17 \n * Google Chrome OS 20.0.1132.18 \n * Google Chrome OS 20.0.1132.19 \n * Google Chrome OS 20.0.1132.2 \n * Google Chrome OS 20.0.1132.20 \n * Google Chrome OS 20.0.1132.21 \n * Google Chrome OS 20.0.1132.3 \n * Google Chrome OS 20.0.1132.4 \n * Google Chrome OS 20.0.1132.5 \n * Google Chrome OS 20.0.1132.6 \n * Google Chrome OS 20.0.1132.7 \n * Google Chrome OS 20.0.1132.8 \n * Google Chrome OS 20.0.1132.9 \n * Google Chrome OS 21.0.1180.0 \n * Google Chrome OS 21.0.1180.1 \n * Google Chrome OS 21.0.1180.10 \n * Google Chrome OS 21.0.1180.11 \n * Google Chrome OS 21.0.1180.13 \n * Google Chrome OS 21.0.1180.14 \n * Google Chrome OS 21.0.1180.15 \n * Google Chrome OS 21.0.1180.17 \n * Google Chrome OS 21.0.1180.18 \n * Google Chrome OS 21.0.1180.2 \n * Google Chrome OS 21.0.1180.3 \n * Google Chrome OS 21.0.1180.31 \n * Google Chrome OS 21.0.1180.32 \n * Google Chrome OS 21.0.1180.33 \n * Google Chrome OS 21.0.1180.34 \n * Google Chrome OS 21.0.1180.35 \n * Google Chrome OS 21.0.1180.36 \n * Google Chrome OS 21.0.1180.37 \n * Google Chrome OS 21.0.1180.38 \n * Google Chrome OS 21.0.1180.39 \n * Google Chrome OS 21.0.1180.4 \n * Google Chrome OS 21.0.1180.41 \n * Google Chrome OS 21.0.1180.46 \n * Google Chrome OS 21.0.1180.47 \n * Google Chrome OS 21.0.1180.48 \n * Google Chrome OS 21.0.1180.49 \n * Google Chrome OS 21.0.1180.5 \n * Google Chrome OS 21.0.1180.50 \n * Google Chrome OS 21.0.1180.51 \n * Google Chrome OS 21.0.1180.52 \n * Google Chrome OS 21.0.1180.53 \n * Google Chrome OS 21.0.1180.54 \n * Google Chrome OS 21.0.1180.55 \n * Google Chrome OS 21.0.1180.56 \n * Google Chrome OS 21.0.1180.57 \n * Google Chrome OS 21.0.1180.6 \n * Google Chrome OS 21.0.1180.7 \n * Google Chrome OS 21.0.1180.79 \n * Google Chrome OS 21.0.1180.8 \n * Google Chrome OS 21.0.1180.81 \n * Google Chrome OS 21.0.1180.9 \n * Google Chrome OS 21.0.1183.0 \n * Google Chrome OS 23.0.1271.94 \n * Google Chrome OS 25.0.1364.0 \n * Google Chrome OS 25.0.1364.1 \n * Google Chrome OS 25.0.1364.10 \n * Google Chrome OS 25.0.1364.108 \n * Google Chrome OS 25.0.1364.11 \n * Google Chrome OS 25.0.1364.110 \n * Google Chrome OS 25.0.1364.112 \n * Google Chrome OS 25.0.1364.113 \n * Google Chrome OS 25.0.1364.114 \n * Google Chrome OS 25.0.1364.115 \n * Google Chrome OS 25.0.1364.116 \n * Google Chrome OS 25.0.1364.117 \n * Google Chrome OS 25.0.1364.118 \n * Google Chrome OS 25.0.1364.119 \n * Google Chrome OS 25.0.1364.12 \n * Google Chrome OS 25.0.1364.120 \n * Google Chrome OS 25.0.1364.121 \n * Google Chrome OS 25.0.1364.122 \n * Google Chrome OS 25.0.1364.123 \n * Google Chrome OS 25.0.1364.124 \n * Google Chrome OS 25.0.1364.125 \n * Google Chrome OS 25.0.1364.126 \n * Google Chrome OS 25.0.1364.13 \n * Google Chrome OS 25.0.1364.14 \n * Google Chrome OS 25.0.1364.15 \n * Google Chrome OS 25.0.1364.152 \n * Google Chrome OS 25.0.1364.154 \n * Google Chrome OS 25.0.1364.155 \n * Google Chrome OS 25.0.1364.156 \n * Google Chrome OS 25.0.1364.159 \n * Google Chrome OS 25.0.1364.16 \n * Google Chrome OS 25.0.1364.160 \n * Google Chrome OS 25.0.1364.161 \n * Google Chrome OS 25.0.1364.168 \n * Google Chrome OS 25.0.1364.169 \n * Google Chrome OS 25.0.1364.17 \n * Google Chrome OS 25.0.1364.170 \n * Google Chrome OS 25.0.1364.171 \n * Google Chrome OS 25.0.1364.172 \n * Google Chrome OS 25.0.1364.173 \n * Google Chrome OS 25.0.1364.18 \n * Google Chrome OS 25.0.1364.19 \n * Google Chrome OS 25.0.1364.2 \n * Google Chrome OS 25.0.1364.20 \n * Google Chrome OS 25.0.1364.21 \n * Google Chrome OS 25.0.1364.22 \n * Google Chrome OS 25.0.1364.23 \n * Google Chrome OS 25.0.1364.24 \n * Google Chrome OS 25.0.1364.25 \n * Google Chrome OS 25.0.1364.26 \n * Google Chrome OS 25.0.1364.27 \n * Google Chrome OS 25.0.1364.28 \n * Google Chrome OS 25.0.1364.29 \n * Google Chrome OS 25.0.1364.3 \n * Google Chrome OS 25.0.1364.30 \n * Google Chrome OS 25.0.1364.31 \n * Google Chrome OS 25.0.1364.32 \n * Google Chrome OS 25.0.1364.33 \n * Google Chrome OS 25.0.1364.34 \n * Google Chrome OS 25.0.1364.35 \n * Google Chrome OS 25.0.1364.36 \n * Google Chrome OS 25.0.1364.37 \n * Google Chrome OS 25.0.1364.38 \n * Google Chrome OS 25.0.1364.39 \n * Google Chrome OS 25.0.1364.40 \n * Google Chrome OS 25.0.1364.41 \n * Google Chrome OS 25.0.1364.42 \n * Google Chrome OS 25.0.1364.43 \n * Google Chrome OS 25.0.1364.44 \n * Google Chrome OS 25.0.1364.45 \n * Google Chrome OS 25.0.1364.46 \n * Google Chrome OS 25.0.1364.47 \n * Google Chrome OS 25.0.1364.48 \n * Google Chrome OS 25.0.1364.49 \n * Google Chrome OS 25.0.1364.5 \n * Google Chrome OS 25.0.1364.50 \n * Google Chrome OS 25.0.1364.51 \n * Google Chrome OS 25.0.1364.52 \n * Google Chrome OS 25.0.1364.53 \n * Google Chrome OS 25.0.1364.54 \n * Google Chrome OS 25.0.1364.55 \n * Google Chrome OS 25.0.1364.56 \n * Google Chrome OS 25.0.1364.57 \n * Google Chrome OS 25.0.1364.58 \n * Google Chrome OS 25.0.1364.61 \n * Google Chrome OS 25.0.1364.62 \n * Google Chrome OS 25.0.1364.63 \n * Google Chrome OS 25.0.1364.65 \n * Google Chrome OS 25.0.1364.66 \n * Google Chrome OS 25.0.1364.67 \n * Google Chrome OS 25.0.1364.68 \n * Google Chrome OS 25.0.1364.7 \n * Google Chrome OS 25.0.1364.70 \n * Google Chrome OS 25.0.1364.72 \n * Google Chrome OS 25.0.1364.73 \n * Google Chrome OS 25.0.1364.74 \n * Google Chrome OS 25.0.1364.75 \n * Google Chrome OS 25.0.1364.76 \n * Google Chrome OS 25.0.1364.77 \n * Google Chrome OS 25.0.1364.78 \n * Google Chrome OS 25.0.1364.79 \n * Google Chrome OS 25.0.1364.8 \n * Google Chrome OS 25.0.1364.80 \n * Google Chrome OS 25.0.1364.81 \n * Google Chrome OS 25.0.1364.82 \n * Google Chrome OS 25.0.1364.84 \n * Google Chrome OS 25.0.1364.85 \n * Google Chrome OS 25.0.1364.86 \n * Google Chrome OS 25.0.1364.87 \n * Google Chrome OS 25.0.1364.88 \n * Google Chrome OS 25.0.1364.89 \n * Google Chrome OS 25.0.1364.9 \n * Google Chrome OS 25.0.1364.90 \n * Google Chrome OS 25.0.1364.91 \n * Google Chrome OS 25.0.1364.92 \n * Google Chrome OS 25.0.1364.93 \n * Google Chrome OS 25.0.1364.95 \n * Google Chrome OS 25.0.1364.98 \n * Google Chrome OS 25.0.1364.99 \n * Google Chrome OS 26.0.1410.0 \n * Google Chrome OS 26.0.1410.1 \n * Google Chrome OS 26.0.1410.10 \n * Google Chrome OS 26.0.1410.11 \n * Google Chrome OS 26.0.1410.12 \n * Google Chrome OS 26.0.1410.14 \n * Google Chrome OS 26.0.1410.15 \n * Google Chrome OS 26.0.1410.16 \n * Google Chrome OS 26.0.1410.17 \n * Google Chrome OS 26.0.1410.18 \n * Google Chrome OS 26.0.1410.19 \n * Google Chrome OS 26.0.1410.20 \n * Google Chrome OS 26.0.1410.21 \n * Google Chrome OS 26.0.1410.22 \n * Google Chrome OS 26.0.1410.23 \n * Google Chrome OS 26.0.1410.24 \n * Google Chrome OS 26.0.1410.25 \n * Google Chrome OS 26.0.1410.26 \n * Google Chrome OS 26.0.1410.27 \n * Google Chrome OS 26.0.1410.28 \n * Google Chrome OS 26.0.1410.29 \n * Google Chrome OS 26.0.1410.3 \n * Google Chrome OS 26.0.1410.30 \n * Google Chrome OS 26.0.1410.31 \n * Google Chrome OS 26.0.1410.32 \n * Google Chrome OS 26.0.1410.33 \n * Google Chrome OS 26.0.1410.34 \n * Google Chrome OS 26.0.1410.35 \n * Google Chrome OS 26.0.1410.36 \n * Google Chrome OS 26.0.1410.37 \n * Google Chrome OS 26.0.1410.38 \n * Google Chrome OS 26.0.1410.39 \n * Google Chrome OS 26.0.1410.4 \n * Google Chrome OS 26.0.1410.40 \n * Google Chrome OS 26.0.1410.41 \n * Google Chrome OS 26.0.1410.42 \n * Google Chrome OS 26.0.1410.43 \n * Google Chrome OS 26.0.1410.44 \n * Google Chrome OS 26.0.1410.45 \n * Google Chrome OS 26.0.1410.46 \n * Google Chrome OS 26.0.1410.47 \n * Google Chrome OS 26.0.1410.48 \n * Google Chrome OS 26.0.1410.49 \n * Google Chrome OS 26.0.1410.5 \n * Google Chrome OS 26.0.1410.50 \n * Google Chrome OS 26.0.1410.51 \n * Google Chrome OS 26.0.1410.52 \n * Google Chrome OS 26.0.1410.54 \n * Google Chrome OS 26.0.1410.55 \n * Google Chrome OS 26.0.1410.56 \n * Google Chrome OS 26.0.1410.57 \n * Google Chrome OS 26.0.1410.6 \n * Google Chrome OS 26.0.1410.7 \n * Google Chrome OS 26.0.1410.8 \n * Google Chrome OS 26.0.1410.9 \n * Google Chrome OS 28.0.1500.71 \n * Google Chrome OS 28.0.1500.95 \n * Google Chrome OS 32.0.1700.95 \n * Google Chrome OS 33.0.1750.152 \n * Google Chrome OS 35.0.1916.155 \n * Google Chrome OS 37.0.2062.119 \n * Google Chrome OS 40.0.2214.114 \n * Google Chrome OS 48.0.2564.116 \n * Google Chrome OS 48.0.2564.92 \n * Google Chrome OS 52.0.2743.85 \n * Google Chrome OS 53.0.2785.103 \n * Google Chrome OS 53.0.2785.144 \n * Google Chrome OS 54.0.2840.79 \n * Google Chrome OS 57.0.2987.137 \n * Google Chrome OS 58.0.3029.89 \n * Google Chrome OS 59.0.3071.91 \n * Google Chrome OS 59.0.3071.92 \n * Google Chrome OS 60.0.3112.114 \n * Google Chrome OS 61.0.3163.113 \n * Google Chrome OS 62.0.3202.97 \n * Google Chrome OS 8.0.552.342 \n * Google Chrome OS 8.0.552.343 \n * Google Chrome OS 8.0.552.344 \n * Google Nexus 5X \n * Google Nexus 6P \n * Google Pixel 2 XL \n * Google Pixel C \n * Google Pixel XL \n * Google V8 \n * HP ProLiant DL385 Gen10 Server 1.02 \n * IBM AIX 5.3 \n * IBM AIX 6.1 \n * IBM AIX 7.1 \n * IBM Aix 7.2 \n * IBM Vios 2.2.0 \n * Intel Xeon CPU E5-1650 v3 \n * Linux kernel 4.14.7 \n * Linux kernel 4.9.74 \n * Microsoft Edge \n * Microsoft Internet Explorer 11 \n * Microsoft SQL Server 2008 R2 for 32-bit Systems Service Pack 3 \n * Microsoft SQL Server 2008 R2 for x64-based Systems Service Pack 3 \n * Microsoft SQL Server 2008 for 32-bit Systems Service Pack 4 \n * Microsoft SQL Server 2008 for x64-based Systems Service Pack 4 \n * Microsoft SQL Server 2012 for 32-bit Systems Service Pack 3 \n * Microsoft SQL Server 2012 for 32-bit Systems Service Pack 4 \n * Microsoft SQL Server 2012 for x64-based Systems Service Pack 3 \n * Microsoft SQL Server 2012 for x64-based Systems Service Pack 4 \n * Microsoft SQL Server 2014 for 32-bit Systems Service Pack 2 \n * Microsoft SQL Server 2014 for x64-based Systems Service Pack 2 \n * Microsoft SQL Server 2016 for x64-based Systems \n * Microsoft SQL Server 2016 for x64-based Systems Service Pack 1 \n * Microsoft SQL Server 2017 for x64-based Systems \n * Microsoft Windows 10 Version 1607 for 32-bit Systems \n * Microsoft Windows 10 Version 1607 for x64-based Systems \n * Microsoft Windows 10 for 32-bit Systems \n * Microsoft Windows 10 for x64-based Systems \n * Microsoft Windows 10 version 1511 for 32-bit Systems \n * Microsoft Windows 10 version 1511 for x64-based Systems \n * Microsoft Windows 10 version 1703 for 32-bit Systems \n * Microsoft Windows 10 version 1703 for x64-based Systems \n * Microsoft Windows 10 version 1709 for 32-bit Systems \n * Microsoft Windows 7 for 32-bit Systems SP1 \n * Microsoft Windows 7 for x64-based Systems SP1 \n * Microsoft Windows 8.1 for 32-bit Systems \n * Microsoft Windows 8.1 for x64-based Systems \n * Microsoft Windows Server 2008 R2 for Itanium-based Systems SP1 \n * Microsoft Windows Server 2008 R2 for x64-based Systems SP1 \n * Microsoft Windows Server 2012 \n * Microsoft Windows Server 2012 R2 \n * Microsoft Windows Server 2016 \n * Oracle VM VirtualBox 5.0 \n * Oracle VM VirtualBox 5.0.10 \n * Oracle VM VirtualBox 5.0.11 \n * Oracle VM VirtualBox 5.0.12 \n * Oracle VM VirtualBox 5.0.13 \n * Oracle VM VirtualBox 5.0.14 \n * Oracle VM VirtualBox 5.0.16 \n * Oracle VM VirtualBox 5.0.18 \n * Oracle VM VirtualBox 5.0.22 \n * Oracle VM VirtualBox 5.0.26 \n * Oracle VM VirtualBox 5.0.28 \n * Oracle VM VirtualBox 5.0.32 \n * Oracle VM VirtualBox 5.0.34 \n * Oracle VM VirtualBox 5.0.38 \n * Oracle VM VirtualBox 5.0.8 \n * Oracle VM VirtualBox 5.0.9 \n * Oracle VM VirtualBox 5.1.10 \n * Oracle VM VirtualBox 5.1.14 \n * Oracle VM VirtualBox 5.1.16 \n * Oracle VM VirtualBox 5.1.20 \n * Oracle VM VirtualBox 5.1.24 \n * Oracle VM VirtualBox 5.1.30 \n * Oracle VM VirtualBox 5.1.8 \n * Oracle VM VirtualBox 5.2.0 \n * Oracle VM VirtualBox 5.2.2 \n * Oracle VM VirtualBox 5.2.4 \n * Oracle X86 Servers SW 1.0 \n * Oracle X86 Servers SW 2.0 \n * Redhat Enterprise Linux 5 \n * Redhat Enterprise Linux 6 \n * Redhat Enterprise Linux 7 \n * Redhat Enterprise Linux Desktop 6 \n * Redhat Enterprise Linux Desktop 7 \n * Redhat Enterprise Linux EUS Compute Node 6.7 \n * Redhat Enterprise Linux EUS Compute Node 7.3 \n * Redhat Enterprise Linux EUS Compute Node 7.4 \n * Redhat Enterprise Linux Server (for IBM Power LE) - 4 Year Extended Upd 7.3 \n * Redhat Enterprise Linux Server (for IBM Power LE) - 4 Year Extended Update Support 7.4 \n * Redhat Enterprise Linux Server - 4 Year Extended Update Support 7.2 \n * Redhat Enterprise Linux Server - 4 Year Extended Update Support 7.3 \n * Redhat Enterprise Linux Server - 4 Year Extended Update Support 7.4 \n * Redhat Enterprise Linux Server - AUS 6.6 \n * Redhat Enterprise Linux Server - AUS 7.2 \n * Redhat Enterprise Linux Server - AUS 7.3 \n * Redhat Enterprise Linux Server - AUS 7.4 \n * Redhat Enterprise Linux Server - Extended Update Support 6.7 \n * Redhat Enterprise Linux Server - Extended Update Support 7.3 \n * Redhat Enterprise Linux Server - Extended Update Support 7.4 \n * Redhat Enterprise Linux Server - TUS 6.6 \n * Redhat Enterprise Linux Server - TUS 7.2 \n * Redhat Enterprise Linux Server - TUS 7.3 \n * Redhat Enterprise Linux Server - TUS 7.4 \n * Redhat Enterprise Linux Server 6 \n * Redhat Enterprise Linux Server 7 \n * Redhat Enterprise Linux Workstation 6 \n * Redhat Enterprise Linux Workstation 7 \n * Redhat Enterprise Linux for IBM z Systems - Extended Update Support 6.7 \n * Redhat Enterprise Linux for IBM z Systems - Extended Update Support 7.4 \n * Redhat Enterprise Linux for IBM z Systems 6 \n * Redhat Enterprise Linux for IBM z Systems 7 \n * Redhat Enterprise Linux for Power, big endian - Extended Update Support 6.7 \n * Redhat Enterprise Linux for Power, big endian - Extended Update Support 7.3 \n * Redhat Enterprise Linux for Power, big endian - Extended Update Support 7.4 \n * Redhat Enterprise Linux for Power, big endian 6 \n * Redhat Enterprise Linux for Power, big endian 7 \n * Redhat Enterprise Linux for Power, little endian - Extended Update Supp 7.3 \n * Redhat Enterprise Linux for Power, little endian - Extended Update Supp 7.4 \n * Redhat Enterprise Linux for Power, little endian 7 \n * Redhat Enterprise Linux for Real Time 7 \n * Redhat Enterprise Linux for Real Time for NFV 7 \n * Redhat Enterprise Linux for Scientific Computing 6 \n * Redhat Enterprise Linux for Scientific Computing 7 \n * Redhat Enterprise Mrg 2 \n * Redhat Virtualization Host 4 \n * VMWare ESXi 5.5 \n * VMWare Esxi 6.0 \n * VMWare Esxi 6.5 \n * VMWare Fusion 8.0 \n * VMWare Fusion 8.0.1 \n * VMWare Fusion 8.0.2 \n * VMWare Fusion 8.1.0 \n * VMWare Fusion 8.1.1 \n * VMWare Fusion 8.5 \n * VMWare Fusion 8.5.2 \n * VMWare Fusion 8.5.4 \n * VMWare Fusion 8.5.5 \n * VMWare Fusion 8.5.6 \n * VMWare Fusion 8.5.8 \n * VMWare Identity Manager 2.0 \n * VMWare Identity Manager 2.7 \n * VMWare Identity Manager 2.7.1 \n * VMWare Identity Manager 3.0 \n * VMWare Workstation 12.0 \n * VMWare Workstation 12.5.3 \n * VMWare Workstation 12.5.5 \n * VMWare Workstation 12.5.7 \n * VMWare vCenter Server 6.0 \n * VMWare vCenter Server 6.5 \n * VMWare vCloud Usage Meter 3.0 \n * VMWare vCloud Usage Meter 3.3 \n * VMWare vCloud Usage Meter 3.3.3 \n * VMWare vRealize Automation 6.0 \n * VMWare vRealize Automation 6.1 \n * VMWare vRealize Automation 6.2 \n * VMWare vRealize Automation 6.2.4 \n * VMWare vRealize Automation 6.2.4.1 \n * VMWare vRealize Automation 6.2.5 \n * VMWare vRealize Automation 7.0 \n * VMWare vRealize Automation 7.1 \n * VMWare vRealize Automation 7.2.0 \n * VMWare vRealize Automation 7.3.0 \n * VMWare vSphere Data Protection 6.0 \n * VMWare vSphere Data Protection 6.0.0 \n * VMWare vSphere Data Protection 6.0.5 \n * VMWare vSphere Data Protection 6.0.6 \n * VMWare vSphere Data Protection 6.0.7 \n * VMWare vSphere Data Protection 6.1 \n * VMWare vSphere Data Protection 6.1.0 \n * VMWare vSphere Data Protection 6.1.4 \n * VMWare vSphere Data Protection 6.1.5 \n * VMWare vSphere Data Protection 6.1.6 \n * VMWare vSphere Integrated Containers 1.0 \n * VMWare vSphere Integrated Containers 1.1 \n * VMWare vSphere Integrated Containers 1.2 \n * VMWare vSphere Integrated Containers 1.3 \n * Xen Xen \n\n### Recommendations\n\n**Permit local access for trusted individuals only. Where possible, use restricted environments and restricted shells.** \nGiven the local nature of this issue, grant only trusted and accountable individuals access to affected computers. \n\nUpdates are available. Please see the references or vendor advisory for more information.\n", "modified": "2018-01-03T00:00:00", "published": "2018-01-03T00:00:00", "href": "https://www.symantec.com/content/symantec/english/en/security-center/vulnerabilities/writeup.html/102378", "id": "SMNTC-102378", "type": "symantec", "title": "Multiple CPU Hardware CVE-2017-5754 Information Disclosure Vulnerability", "cvss": {"score": 4.7, "vector": "AV:LOCAL/AC:MEDIUM/Au:NONE/C:COMPLETE/I:NONE/A:NONE/"}}, {"lastseen": "2018-03-11T18:48:52", "bulletinFamily": "software", "description": "### Description\n\nMultiple CPU Hardware are prone to an information-disclosure vulnerability. Attackers can exploit this issue to obtain sensitive information that may aid in further attacks.\n\n### Technologies Affected\n\n * AMD FX(tm)-8320 Eight-Core Processor \n * AMD PRO A8-9600 R7, 10 COMPUTE CORES 4C+6G \n * ARM Cortex A57 \n * Apple Mac Os X 10.11.6 \n * Apple Safari 1.0.0 \n * Apple Safari 1.0.0 \n * Apple Safari 1.0.3 \n * Apple Safari 1.1.0 \n * Apple Safari 1.1.1 \n * Apple Safari 1.2.0 \n * Apple Safari 1.2.1 \n * Apple Safari 1.2.2 \n * Apple Safari 1.2.3 \n * Apple Safari 1.2.4 \n * Apple Safari 1.2.5 \n * Apple Safari 1.3.0 \n * Apple Safari 1.3.0 \n * Apple Safari 1.3.1 \n * Apple Safari 1.3.2 312.5 \n * Apple Safari 1.3.2 312.6 \n * Apple Safari 1.3.2 \n * Apple Safari 10 \n * Apple Safari 10.0.1 \n * Apple Safari 10.0.2 \n * Apple Safari 10.0.3 \n * Apple Safari 10.1 \n * Apple Safari 10.1.1 \n * Apple Safari 10.1.2 \n * Apple Safari 11 \n * Apple Safari 2 \n * Apple Safari 2.0.1 \n * Apple Safari 2.0.2 \n * Apple Safari 2.0.3 417.8 \n * Apple Safari 2.0.3 417.9 \n * Apple Safari 2.0.3 417.9.2 \n * Apple Safari 2.0.3 417.9.3 \n * Apple Safari 2.0.3 \n * Apple Safari 2.0.4 419.3 \n * Apple Safari 2.0.4 \n * Apple Safari 3 \n * Apple Safari 3 \n * Apple Safari 3.0.0 \n * Apple Safari 3.1 \n * Apple Safari 3.1.0B \n * Apple Safari 3.1.1 \n * Apple Safari 3.1.2 \n * Apple Safari 3.2 \n * Apple Safari 3.2.1 \n * Apple Safari 3.2.2 \n * Apple Safari 3.2.3 \n * Apple Safari 3.52 \n * Apple Safari 4 \n * Apple Safari 4.0 \n * Apple Safari 4.0.1 \n * Apple Safari 4.0.2 \n * Apple Safari 4.0.3 \n * Apple Safari 4.0.4 \n * Apple Safari 4.0.5 \n * Apple Safari 4.1 \n * Apple Safari 4.1.1 \n * Apple Safari 4.1.2 \n * Apple Safari 4.1.3 \n * Apple Safari 4.28 \n * Apple Safari 4.30 \n * Apple Safari 4.31 \n * Apple Safari 5.0 \n * Apple Safari 5.0.1 \n * Apple Safari 5.0.2 \n * Apple Safari 5.0.3 \n * Apple Safari 5.0.4 \n * Apple Safari 5.0.5 \n * Apple Safari 5.0.6 \n * Apple Safari 5.1 \n * Apple Safari 5.1.1 \n * Apple Safari 5.1.10 \n * Apple Safari 5.1.2 \n * Apple Safari 5.1.3 \n * Apple Safari 5.1.4 \n * Apple Safari 5.1.5 \n * Apple Safari 5.1.6 \n * Apple Safari 5.1.7 \n * Apple Safari 5.31 \n * Apple Safari 5.33 \n * Apple Safari 5.34 \n * Apple Safari 6.0 \n * Apple Safari 6.0.1 \n * Apple Safari 6.0.2 \n * Apple Safari 6.0.3 \n * Apple Safari 6.0.4 \n * Apple Safari 6.0.5 \n * Apple Safari 6.1 \n * Apple Safari 6.1.1 \n * Apple Safari 6.1.2 \n * Apple Safari 6.1.3 \n * Apple Safari 6.1.4 \n * Apple Safari 6.1.5 \n * Apple Safari 6.1.6 \n * Apple Safari 6.2 \n * Apple Safari 6.2.1 \n * Apple Safari 6.2.2 \n * Apple Safari 6.2.3 \n * Apple Safari 6.2.4 \n * Apple Safari 6.2.5 \n * Apple Safari 6.2.6 \n * Apple Safari 6.2.7 \n * Apple Safari 6.2.8 \n * Apple Safari 7.0.1 \n * Apple Safari 7.0.2 \n * Apple Safari 7.0.3 \n * Apple Safari 7.0.4 \n * Apple Safari 7.0.5 \n * Apple Safari 7.0.6 \n * Apple Safari 7.1 \n * Apple Safari 7.1.0 \n * Apple Safari 7.1.1 \n * Apple Safari 7.1.2 \n * Apple Safari 7.1.3 \n * Apple Safari 7.1.4 \n * Apple Safari 7.1.5 \n * Apple Safari 7.1.6 \n * Apple Safari 7.1.7 \n * Apple Safari 7.1.8 \n * Apple Safari 8.0 \n * Apple Safari 8.0.1 \n * Apple Safari 8.0.2 \n * Apple Safari 8.0.3 \n * Apple Safari 8.0.4 \n * Apple Safari 8.0.5 \n * Apple Safari 8.0.6 \n * Apple Safari 8.0.7 \n * Apple Safari 8.0.8 \n * Apple Safari 9 \n * Apple Safari 9.0.1 \n * Apple Safari 9.0.2 \n * Apple Safari 9.0.3 \n * Apple Safari 9.1 \n * Apple Safari 9.1.1 \n * Apple Safari 9.1.2 \n * Apple Safari 9.1.3 \n * Apple Safari \n * Apple iOS 10 \n * Apple iOS 10.0.1 \n * Apple iOS 10.1 \n * Apple iOS 10.2 \n * Apple iOS 10.2.1 \n * Apple iOS 10.3 \n * Apple iOS 10.3.1 \n * Apple iOS 10.3.2 \n * Apple iOS 10.3.3 \n * Apple iOS 11 \n * Apple iOS 11.1 \n * Apple iOS 11.2 \n * Apple iOS 11.2.1 \n * Apple iOS 2.0 \n * Apple iOS 2.1 \n * Apple iOS 3 \n * Apple iOS 3.0 \n * Apple iOS 3.1 \n * Apple iOS 3.2 \n * Apple iOS 3.2.1 \n * Apple iOS 3.2.2 \n * Apple iOS 4 \n * Apple iOS 4 \n * Apple iOS 4.0.1 \n * Apple iOS 4.0.2 \n * Apple iOS 4.1 \n * Apple iOS 4.2 \n * Apple iOS 4.2.1 \n * Apple iOS 4.2.10 \n * Apple iOS 4.2.5 \n * Apple iOS 4.2.6 \n * Apple iOS 4.2.7 \n * Apple iOS 4.2.8 \n * Apple iOS 4.2.9 \n * Apple iOS 4.3 \n * Apple iOS 4.3.1 \n * Apple iOS 4.3.2 \n * Apple iOS 4.3.3 \n * Apple iOS 4.3.4 \n * Apple iOS 4.3.5 \n * Apple iOS 5 \n * Apple iOS 5 \n * Apple iOS 5.0.1 \n * Apple iOS 5.1 \n * Apple iOS 5.1.1 \n * Apple iOS 6 \n * Apple iOS 6.0.1 \n * Apple iOS 6.0.2 \n * Apple iOS 6.1 \n * Apple iOS 6.1.3 \n * Apple iOS 6.1.4 \n * Apple iOS 6.1.6 \n * Apple iOS 6.3.1 \n * Apple iOS 7 \n * Apple iOS 7.0.1 \n * Apple iOS 7.0.2 \n * Apple iOS 7.0.3 \n * Apple iOS 7.0.4 \n * Apple iOS 7.0.5 \n * Apple iOS 7.0.6 \n * Apple iOS 7.1 \n * Apple iOS 7.1.1 \n * Apple iOS 7.1.2 \n * Apple iOS 7.2.0 \n * Apple iOS 8 \n * Apple iOS 8.1 \n * Apple iOS 8.1.1 \n * Apple iOS 8.1.2 \n * Apple iOS 8.1.3 \n * Apple iOS 8.2 \n * Apple iOS 8.3 \n * Apple iOS 8.4 \n * Apple iOS 8.4.1 \n * Apple iOS 9 \n * Apple iOS 9.0.1 \n * Apple iOS 9.0.2 \n * Apple iOS 9.1 \n * Apple iOS 9.2 \n * Apple iOS 9.2.1 \n * Apple iOS 9.3 \n * Apple iOS 9.3.1 \n * Apple iOS 9.3.2 \n * Apple iOS 9.3.3 \n * Apple iOS 9.3.4 \n * Apple iOS 9.3.5 \n * Apple iPad Air \n * Apple iPhone \n * Apple iPod Touch \n * Apple macOS 10.12.6 \n * Apple macOS \n * Apple tvOS \n * Apple watchOS \n * BD Accuri C6 Plus \n * BD Alaris Systems Manager \n * BD Assurity Linc \n * BD BACTEC 9050 \n * BD BACTEC 9120/9240 \n * BD BACTEC FX \n * BD BACTEC FX40 \n * BD Data Innovations \n * BD FACSAria Fusion \n * BD FACSAria I/II/III \n * BD FACSCalibur \n * BD FACSCanto 10-color \n * BD FACSCanto 10-color clinical \n * BD FACSCanto II \n * BD FACSCanto II clinical \n * BD FACSCelesta \n * BD FACSCount \n * BD FACSDuet Sample Prep (ASaP) \n * BD FACSJazz \n * BD FACSLink Interface \n * BD FACSLyric \n * BD FACSMelody \n * BD FACSPresto \n * BD FACSSample Prep Assistant (SPA) III \n * BD FACSVerse \n * BD FACSVia \n * BD Focal Point - Linux \n * BD Focal Point - Solaris \n * BD GenCell CliC \n * BD Influx \n * BD Innova \n * BD Kiestra InoqulA Standalone \n * BD Kiestra TLA/WCA \n * BD LSR II \n * BD LSRFortessa \n * BD LSRFortessa X-20 \n * BD Lyse Wash Assistant \n * BD Panel Designer \n * BD Phoenix \n * BD PrepStain \n * BD Pyxis Anesthesia ES \n * BD Pyxis Anesthesia System 3500 \n * BD Pyxis CIISafe -Workstation \n * BD Pyxis CUBIE Replenishment Station \n * BD Pyxis CathRack v8 \n * BD Pyxis DuoStation \n * BD Pyxis EcoStation System \n * BD Pyxis Infant Care Verification \n * BD Pyxis MedStation 3500 \n * BD Pyxis MedStation 4000 Console \n * BD Pyxis MedStation ES \n * BD Pyxis Medication Administration \n * BD Pyxis Nursing Data Collection \n * BD Pyxis ParAssist System \n * BD Pyxis Parx \n * BD Pyxis Parx handheld \n * BD Pyxis ProcedureStation \n * BD Pyxis ScrubStation System \n * BD Pyxis Specimen Collection Verification \n * BD Pyxis StockStation System \n * BD Pyxis Supply Roller \n * BD Pyxis SupplyStation \n * BD Pyxis Transfusion Verification \n * BD Rowa Dose \n * BD Rowa Smart \n * BD Rowa Vmax System \n * BD Totalys Multiprocessor \n * BD Totalys SlidePrep \n * BD Veritor Plus System \n * BD Viper LT \n * BD Viper XTR \n * Bluecoat Content Analysis 2.1 \n * Bluecoat Content Analysis 2.2 \n * Bluecoat Malware Analysis Appliance 4.2 \n * Bluecoat Security Analytics 7.1 \n * Bluecoat Security Analytics 7.2 \n * Bluecoat Security Analytics 7.3 \n * Bluecoat X-Series XOS 10.0 \n * Bluecoat X-Series XOS 11.0 \n * Bluecoat X-Series XOS 9.7 \n * Cisco Carrier Routing System 6.6.0.BASE \n * Cisco Unified Computing System 2.2 \n * Cisco Unified Computing System 3.1 \n * Cisco Unified Computing System 3.2 \n * Google Android \n * Google Chrome 0.1.38.1 \n * Google Chrome 0.1.38.2 \n * Google Chrome 0.1.38.4 \n * Google Chrome 0.1.40.1 \n * Google Chrome 0.1.42.2 \n * Google Chrome 0.1.42.3 \n * Google Chrome 0.2.149.27 \n * Google Chrome 0.2.149.29 \n * Google Chrome 0.2.149.30 \n * Google Chrome 0.2.152.1 \n * Google Chrome 0.2.153.1 \n * Google Chrome 0.3.154 9 \n * Google Chrome 0.3.154.0 \n * Google Chrome 0.3.154.3 \n * Google Chrome 0.4.154.18 \n * Google Chrome 0.4.154.22 \n * Google Chrome 0.4.154.31 \n * Google Chrome 0.4.154.33 \n * Google Chrome 1.0.154.36 \n * Google Chrome 1.0.154.39 \n * Google Chrome 1.0.154.42 \n * Google Chrome 1.0.154.43 \n * Google Chrome 1.0.154.46 \n * Google Chrome 1.0.154.48 \n * Google Chrome 1.0.154.52 \n * Google Chrome 1.0.154.53 \n * Google Chrome 1.0.154.55 \n * Google Chrome 1.0.154.59 \n * Google Chrome 1.0.154.61 \n * Google Chrome 1.0.154.64 \n * Google Chrome 1.0.154.65 \n * Google Chrome 10 \n * Google Chrome 10.0.601.0 \n * Google Chrome 10.0.602.0 \n * Google Chrome 10.0.603.0 \n * Google Chrome 10.0.603.2 \n * Google Chrome 10.0.603.3 \n * Google Chrome 10.0.604.0 \n * Google Chrome 10.0.605.0 \n * Google Chrome 10.0.606.0 \n * Google Chrome 10.0.607.0 \n * Google Chrome 10.0.608.0 \n * Google Chrome 10.0.609.0 \n * Google Chrome 10.0.610.0 \n * Google Chrome 10.0.611.0 \n * Google Chrome 10.0.611.1 \n * Google Chrome 10.0.612.0 \n * Google Chrome 10.0.612.1 \n * Google Chrome 10.0.612.2 \n * Google Chrome 10.0.612.3 \n * Google Chrome 10.0.613.0 \n * Google Chrome 10.0.614.0 \n * Google Chrome 10.0.615.0 \n * Google Chrome 10.0.616.0 \n * Google Chrome 10.0.617.0 \n * Google Chrome 10.0.618.0 \n * Google Chrome 10.0.619.0 \n * Google Chrome 10.0.620.0 \n * Google Chrome 10.0.621.0 \n * Google Chrome 10.0.622.0 \n * Google Chrome 10.0.622.1 \n * Google Chrome 10.0.623.0 \n * Google Chrome 10.0.624.0 \n * Google Chrome 10.0.625.0 \n * Google Chrome 10.0.626.0 \n * Google Chrome 10.0.627.0 \n * Google Chrome 10.0.628.0 \n * Google Chrome 10.0.629.0 \n * Google Chrome 10.0.630.0 \n * Google Chrome 10.0.631.0 \n * Google Chrome 10.0.632.0 \n * Google Chrome 10.0.633.0 \n * Google Chrome 10.0.634.0 \n * Google Chrome 10.0.634.1 \n * Google Chrome 10.0.635.0 \n * Google Chrome 10.0.636.0 \n * Google Chrome 10.0.638.0 \n * Google Chrome 10.0.638.1 \n * Google Chrome 10.0.639.0 \n * Google Chrome 10.0.640.0 \n * Google Chrome 10.0.642.0 \n * Google Chrome 10.0.642.1 \n * Google Chrome 10.0.642.2 \n * Google Chrome 10.0.643.0 \n * Google Chrome 10.0.644.0 \n * Google Chrome 10.0.645.0 \n * Google Chrome 10.0.646.0 \n * Google Chrome 10.0.647.0 \n * Google Chrome 10.0.648.0 \n * Google Chrome 10.0.648.1 \n * Google Chrome 10.0.648.10 \n * Google Chrome 10.0.648.101 \n * Google Chrome 10.0.648.103 \n * Google Chrome 10.0.648.105 \n * Google Chrome 10.0.648.107 \n * Google Chrome 10.0.648.11 \n * Google Chrome 10.0.648.114 \n * Google Chrome 10.0.648.116 \n * Google Chrome 10.0.648.118 \n * Google Chrome 10.0.648.119 \n * Google Chrome 10.0.648.12 \n * Google Chrome 10.0.648.120 \n * Google Chrome 10.0.648.121 \n * Google Chrome 10.0.648.122 \n * Google Chrome 10.0.648.123 \n * Google Chrome 10.0.648.124 \n * Google Chrome 10.0.648.125 \n * Google Chrome 10.0.648.126 \n * Google Chrome 10.0.648.127 \n * Google Chrome 10.0.648.128 \n * Google Chrome 10.0.648.129 \n * Google Chrome 10.0.648.13 \n * Google Chrome 10.0.648.130 \n * Google Chrome 10.0.648.131 \n * Google Chrome 10.0.648.132 \n * Google Chrome 10.0.648.133 \n * Google Chrome 10.0.648.134 \n * Google Chrome 10.0.648.135 \n * Google Chrome 10.0.648.151 \n * Google Chrome 10.0.648.18 \n * Google Chrome 10.0.648.2 \n * Google Chrome 10.0.648.201 \n * Google Chrome 10.0.648.203 \n * Google Chrome 10.0.648.204 \n * Google Chrome 10.0.648.205 \n * Google Chrome 10.0.648.23 \n * Google Chrome 10.0.648.26 \n * Google Chrome 10.0.648.28 \n * Google Chrome 10.0.648.3 \n * Google Chrome 10.0.648.32 \n * Google Chrome 10.0.648.35 \n * Google Chrome 10.0.648.38 \n * Google Chrome 10.0.648.4 \n * Google Chrome 10.0.648.42 \n * Google Chrome 10.0.648.45 \n * Google Chrome 10.0.648.49 \n * Google Chrome 10.0.648.5 \n * Google Chrome 10.0.648.54 \n * Google Chrome 10.0.648.56 \n * Google Chrome 10.0.648.59 \n * Google Chrome 10.0.648.6 \n * Google Chrome 10.0.648.62 \n * Google Chrome 10.0.648.66 \n * Google Chrome 10.0.648.68 \n * Google Chrome 10.0.648.7 \n * Google Chrome 10.0.648.70 \n * Google Chrome 10.0.648.72 \n * Google Chrome 10.0.648.76 \n * Google Chrome 10.0.648.79 \n * Google Chrome 10.0.648.8 \n * Google Chrome 10.0.648.82 \n * Google Chrome 10.0.648.84 \n * Google Chrome 10.0.648.87 \n * Google Chrome 10.0.648.9 \n * Google Chrome 10.0.648.90 \n * Google Chrome 10.0.649.0 \n * Google Chrome 10.0.650.0 \n * Google Chrome 10.0.651.0 \n * Google Chrome 11 \n * Google Chrome 11.0.652.0 \n * Google Chrome 11.0.653.0 \n * Google Chrome 11.0.654.0 \n * Google Chrome 11.0.655.0 \n * Google Chrome 11.0.656.0 \n * Google Chrome 11.0.657.0 \n * Google Chrome 11.0.658.0 \n * Google Chrome 11.0.658.1 \n * Google Chrome 11.0.659.0 \n * Google Chrome 11.0.660.0 \n * Google Chrome 11.0.661.0 \n * Google Chrome 11.0.662.0 \n * Google Chrome 11.0.663.0 \n * Google Chrome 11.0.664.1 \n * Google Chrome 11.0.665.0 \n * Google Chrome 11.0.666.0 \n * Google Chrome 11.0.667.0 \n * Google Chrome 11.0.667.2 \n * Google Chrome 11.0.667.3 \n * Google Chrome 11.0.667.4 \n * Google Chrome 11.0.668.0 \n * Google Chrome 11.0.669.0 \n * Google Chrome 11.0.670.0 \n * Google Chrome 11.0.671.0 \n * Google Chrome 11.0.672.0 \n * Google Chrome 11.0.672.1 \n * Google Chrome 11.0.672.2 \n * Google Chrome 11.0.673.0 \n * Google Chrome 11.0.674.0 \n * Google Chrome 11.0.675.0 \n * Google Chrome 11.0.676.0 \n * Google Chrome 11.0.677.0 \n * Google Chrome 11.0.678.0 \n * Google Chrome 11.0.679.0 \n * Google Chrome 11.0.680.0 \n * Google Chrome 11.0.681.0 \n * Google Chrome 11.0.682.0 \n * Google Chrome 11.0.683.0 \n * Google Chrome 11.0.684.0 \n * Google Chrome 11.0.685.0 \n * Google Chrome 11.0.686.0 \n * Google Chrome 11.0.686.1 \n * Google Chrome 11.0.686.2 \n * Google Chrome 11.0.686.3 \n * Google Chrome 11.0.687.0 \n * Google Chrome 11.0.687.1 \n * Google Chrome 11.0.688.0 \n * Google Chrome 11.0.689.0 \n * Google Chrome 11.0.690.0 \n * Google Chrome 11.0.690.1 \n * Google Chrome 11.0.691.0 \n * Google Chrome 11.0.692.0 \n * Google Chrome 11.0.693.0 \n * Google Chrome 11.0.694.0 \n * Google Chrome 11.0.695.0 \n * Google Chrome 11.0.696.0 \n * Google Chrome 11.0.696.1 \n * Google Chrome 11.0.696.10 \n * Google Chrome 11.0.696.11 \n * Google Chrome 11.0.696.12 \n * Google Chrome 11.0.696.13 \n * Google Chrome 11.0.696.14 \n * Google Chrome 11.0.696.15 \n * Google Chrome 11.0.696.16 \n * Google Chrome 11.0.696.17 \n * Google Chrome 11.0.696.18 \n * Google Chrome 11.0.696.19 \n * Google Chrome 11.0.696.2 \n * Google Chrome 11.0.696.20 \n * Google Chrome 11.0.696.21 \n * Google Chrome 11.0.696.22 \n * Google Chrome 11.0.696.23 \n * Google Chrome 11.0.696.24 \n * Google Chrome 11.0.696.25 \n * Google Chrome 11.0.696.26 \n * Google Chrome 11.0.696.27 \n * Google Chrome 11.0.696.28 \n * Google Chrome 11.0.696.29 \n * Google Chrome 11.0.696.3 \n * Google Chrome 11.0.696.30 \n * Google Chrome 11.0.696.31 \n * Google Chrome 11.0.696.32 \n * Google Chrome 11.0.696.33 \n * Google Chrome 11.0.696.34 \n * Google Chrome 11.0.696.35 \n * Google Chrome 11.0.696.36 \n * Google Chrome 11.0.696.37 \n * Google Chrome 11.0.696.38 \n * Google Chrome 11.0.696.39 \n * Google Chrome 11.0.696.4 \n * Google Chrome 11.0.696.40 \n * Google Chrome 11.0.696.41 \n * Google Chrome 11.0.696.42 \n * Google Chrome 11.0.696.43 \n * Google Chrome 11.0.696.44 \n * Google Chrome 11.0.696.45 \n * Google Chrome 11.0.696.46 \n * Google Chrome 11.0.696.47 \n * Google Chrome 11.0.696.48 \n * Google Chrome 11.0.696.49 \n * Google Chrome 11.0.696.5 \n * Google Chrome 11.0.696.50 \n * Google Chrome 11.0.696.51 \n * Google Chrome 11.0.696.52 \n * Google Chrome 11.0.696.53 \n * Google Chrome 11.0.696.54 \n * Google Chrome 11.0.696.55 \n * Google Chrome 11.0.696.56 \n * Google Chrome 11.0.696.57 \n * Google Chrome 11.0.696.58 \n * Google Chrome 11.0.696.59 \n * Google Chrome 11.0.696.60 \n * Google Chrome 11.0.696.61 \n * Google Chrome 11.0.696.62 \n * Google Chrome 11.0.696.63 \n * Google Chrome 11.0.696.64 \n * Google Chrome 11.0.696.65 \n * Google Chrome 11.0.696.66 \n * Google Chrome 11.0.696.67 \n * Google Chrome 11.0.696.68 \n * Google Chrome 11.0.696.69 \n * Google Chrome 11.0.696.7 \n * Google Chrome 11.0.696.70 \n * Google Chrome 11.0.696.71 \n * Google Chrome 11.0.696.72 \n * Google Chrome 11.0.696.77 \n * Google Chrome 11.0.696.8 \n * Google Chrome 11.0.696.9 \n * Google Chrome 11.0.697.0 \n * Google Chrome 11.0.698.0 \n * Google Chrome 11.0.699.0 \n * Google Chrome 12 \n * Google Chrome 12.0.700.0 \n * Google Chrome 12.0.701.0 \n * Google Chrome 12.0.702.0 \n * Google Chrome 12.0.702.1 \n * Google Chrome 12.0.702.2 \n * Google Chrome 12.0.703.0 \n * Google Chrome 12.0.704.0 \n * Google Chrome 12.0.705.0 \n * Google Chrome 12.0.706.0 \n * Google Chrome 12.0.707.0 \n * Google Chrome 12.0.708.0 \n * Google Chrome 12.0.709.0 \n * Google Chrome 12.0.710.0 \n * Google Chrome 12.0.711.0 \n * Google Chrome 12.0.712.0 \n * Google Chrome 12.0.713.0 \n * Google Chrome 12.0.714.0 \n * Google Chrome 12.0.715.0 \n * Google Chrome 12.0.716.0 \n * Google Chrome 12.0.717.0 \n * Google Chrome 12.0.718.0 \n * Google Chrome 12.0.719.0 \n * Google Chrome 12.0.719.1 \n * Google Chrome 12.0.720.0 \n * Google Chrome 12.0.721.0 \n * Google Chrome 12.0.721.1 \n * Google Chrome 12.0.722.0 \n * Google Chrome 12.0.723.0 \n * Google Chrome 12.0.723.1 \n * Google Chrome 12.0.724.0 \n * Google Chrome 12.0.725.0 \n * Google Chrome 12.0.726.0 \n * Google Chrome 12.0.727.0 \n * Google Chrome 12.0.728.0 \n * Google Chrome 12.0.729.0 \n * Google Chrome 12.0.730.0 \n * Google Chrome 12.0.731.0 \n * Google Chrome 12.0.732.0 \n * Google Chrome 12.0.733.0 \n * Google Chrome 12.0.734.0 \n * Google Chrome 12.0.735.0 \n * Google Chrome 12.0.736.0 \n * Google Chrome 12.0.737.0 \n * Google Chrome 12.0.738.0 \n * Google Chrome 12.0.739.0 \n * Google Chrome 12.0.740.0 \n * Google Chrome 12.0.741.0 \n * Google Chrome 12.0.742.0 \n * Google Chrome 12.0.742.1 \n * Google Chrome 12.0.742.10 \n * Google Chrome 12.0.742.100 \n * Google Chrome 12.0.742.105 \n * Google Chrome 12.0.742.11 \n * Google Chrome 12.0.742.111 \n * Google Chrome 12.0.742.112 \n * Google Chrome 12.0.742.113 \n * Google Chrome 12.0.742.114 \n * Google Chrome 12.0.742.115 \n * Google Chrome 12.0.742.12 \n * Google Chrome 12.0.742.120 \n * Google Chrome 12.0.742.121 \n * Google Chrome 12.0.742.122 \n * Google Chrome 12.0.742.123 \n * Google Chrome 12.0.742.124 \n * Google Chrome 12.0.742.13 \n * Google Chrome 12.0.742.14 \n * Google Chrome 12.0.742.15 \n * Google Chrome 12.0.742.16 \n * Google Chrome 12.0.742.17 \n * Google Chrome 12.0.742.18 \n * Google Chrome 12.0.742.19 \n * Google Chrome 12.0.742.2 \n * Google Chrome 12.0.742.20 \n * Google Chrome 12.0.742.21 \n * Google Chrome 12.0.742.22 \n * Google Chrome 12.0.742.3 \n * Google Chrome 12.0.742.30 \n * Google Chrome 12.0.742.4 \n * Google Chrome 12.0.742.41 \n * Google Chrome 12.0.742.42 \n * Google Chrome 12.0.742.43 \n * Google Chrome 12.0.742.44 \n * Google Chrome 12.0.742.45 \n * Google Chrome 12.0.742.46 \n * Google Chrome 12.0.742.47 \n * Google Chrome 12.0.742.48 \n * Google Chrome 12.0.742.49 \n * Google Chrome 12.0.742.5 \n * Google Chrome 12.0.742.50 \n * Google Chrome 12.0.742.51 \n * Google Chrome 12.0.742.52 \n * Google Chrome 12.0.742.53 \n * Google Chrome 12.0.742.54 \n * Google Chrome 12.0.742.55 \n * Google Chrome 12.0.742.56 \n * Google Chrome 12.0.742.57 \n * Google Chrome 12.0.742.58 \n * Google Chrome 12.0.742.59 \n * Google Chrome 12.0.742.6 \n * Google Chrome 12.0.742.60 \n * Google Chrome 12.0.742.61 \n * Google Chrome 12.0.742.63 \n * Google Chrome 12.0.742.64 \n * Google Chrome 12.0.742.65 \n * Google Chrome 12.0.742.66 \n * Google Chrome 12.0.742.67 \n * Google Chrome 12.0.742.68 \n * Google Chrome 12.0.742.69 \n * Google Chrome 12.0.742.70 \n * Google Chrome 12.0.742.71 \n * Google Chrome 12.0.742.72 \n * Google Chrome 12.0.742.73 \n * Google Chrome 12.0.742.74 \n * Google Chrome 12.0.742.75 \n * Google Chrome 12.0.742.77 \n * Google Chrome 12.0.742.8 \n * Google Chrome 12.0.742.82 \n * Google Chrome 12.0.742.9 \n * Google Chrome 12.0.742.91 \n * Google Chrome 12.0.742.92 \n * Google Chrome 12.0.742.93 \n * Google Chrome 12.0.742.94 \n * Google Chrome 12.0.743.0 \n * Google Chrome 12.0.744.0 \n * Google Chrome 12.0.745.0 \n * Google Chrome 12.0.746.0 \n * Google Chrome 12.0.747.0 \n * Google Chrome 13 \n * Google Chrome 13.0.748.0 \n * Google Chrome 13.0.749.0 \n * Google Chrome 13.0.750.0 \n * Google Chrome 13.0.751.0 \n * Google Chrome 13.0.752.0 \n * Google Chrome 13.0.753.0 \n * Google Chrome 13.0.754.0 \n * Google Chrome 13.0.755.0 \n * Google Chrome 13.0.756.0 \n * Google Chrome 13.0.757.0 \n * Google Chrome 13.0.758.0 \n * Google Chrome 13.0.759.0 \n * Google Chrome 13.0.760.0 \n * Google Chrome 13.0.761.0 \n * Google Chrome 13.0.761.1 \n * Google Chrome 13.0.762.0 \n * Google Chrome 13.0.762.1 \n * Google Chrome 13.0.763.0 \n * Google Chrome 13.0.764.0 \n * Google Chrome 13.0.765.0 \n * Google Chrome 13.0.766.0 \n * Google Chrome 13.0.767.0 \n * Google Chrome 13.0.767.1 \n * Google Chrome 13.0.768.0 \n * Google Chrome 13.0.769.0 \n * Google Chrome 13.0.770.0 \n * Google Chrome 13.0.771.0 \n * Google Chrome 13.0.772.0 \n * Google Chrome 13.0.773.0 \n * Google Chrome 13.0.774.0 \n * Google Chrome 13.0.775.0 \n * Google Chrome 13.0.775.1 \n * Google Chrome 13.0.775.2 \n * Google Chrome 13.0.775.4 \n * Google Chrome 13.0.776.0 \n * Google Chrome 13.0.776.1 \n * Google Chrome 13.0.777.0 \n * Google Chrome 13.0.777.1 \n * Google Chrome 13.0.777.2 \n * Google Chrome 13.0.777.3 \n * Google Chrome 13.0.777.4 \n * Google Chrome 13.0.777.5 \n * Google Chrome 13.0.777.6 \n * Google Chrome 13.0.778.0 \n * Google Chrome 13.0.779.0 \n * Google Chrome 13.0.780.0 \n * Google Chrome 13.0.781.0 \n * Google Chrome 13.0.782.0 \n * Google Chrome 13.0.782.1 \n * Google Chrome 13.0.782.10 \n * Google Chrome 13.0.782.100 \n * Google Chrome 13.0.782.101 \n * Google Chrome 13.0.782.102 \n * Google Chrome 13.0.782.103 \n * Google Chrome 13.0.782.104 \n * Google Chrome 13.0.782.105 \n * Google Chrome 13.0.782.106 \n * Google Chrome 13.0.782.107 \n * Google Chrome 13.0.782.108 \n * Google Chrome 13.0.782.109 \n * Google Chrome 13.0.782.11 \n * Google Chrome 13.0.782.112 \n * Google Chrome 13.0.782.12 \n * Google Chrome 13.0.782.13 \n * Google Chrome 13.0.782.14 \n * Google Chrome 13.0.782.15 \n * Google Chrome 13.0.782.16 \n * Google Chrome 13.0.782.17 \n * Google Chrome 13.0.782.18 \n * Google Chrome 13.0.782.19 \n * Google Chrome 13.0.782.20 \n * Google Chrome 13.0.782.21 \n * Google Chrome 13.0.782.210 \n * Google Chrome 13.0.782.211 \n * Google Chrome 13.0.782.212 \n * Google Chrome 13.0.782.213 \n * Google Chrome 13.0.782.214 \n * Google Chrome 13.0.782.215 \n * Google Chrome 13.0.782.216 \n * Google Chrome 13.0.782.217 \n * Google Chrome 13.0.782.218 \n * Google Chrome 13.0.782.219 \n * Google Chrome 13.0.782.220 \n * Google Chrome 13.0.782.23 \n * Google Chrome 13.0.782.237 \n * Google Chrome 13.0.782.238 \n * Google Chrome 13.0.782.24 \n * Google Chrome 13.0.782.25 \n * Google Chrome 13.0.782.26 \n * Google Chrome 13.0.782.27 \n * Google Chrome 13.0.782.28 \n * Google Chrome 13.0.782.29 \n * Google Chrome 13.0.782.3 \n * Google Chrome 13.0.782.30 \n * Google Chrome 13.0.782.31 \n * Google Chrome 13.0.782.32 \n * Google Chrome 13.0.782.33 \n * Google Chrome 13.0.782.34 \n * Google Chrome 13.0.782.35 \n * Google Chrome 13.0.782.36 \n * Google Chrome 13.0.782.37 \n * Google Chrome 13.0.782.38 \n * Google Chrome 13.0.782.39 \n * Google Chrome 13.0.782.4 \n * Google Chrome 13.0.782.40 \n * Google Chrome 13.0.782.41 \n * Google Chrome 13.0.782.42 \n * Google Chrome 13.0.782.43 \n * Google Chrome 13.0.782.44 \n * Google Chrome 13.0.782.45 \n * Google Chrome 13.0.782.46 \n * Google Chrome 13.0.782.47 \n * Google Chrome 13.0.782.48 \n * Google Chrome 13.0.782.49 \n * Google Chrome 13.0.782.50 \n * Google Chrome 13.0.782.51 \n * Google Chrome 13.0.782.52 \n * Google Chrome 13.0.782.53 \n * Google Chrome 13.0.782.55 \n * Google Chrome 13.0.782.56 \n * Google Chrome 13.0.782.6 \n * Google Chrome 13.0.782.7 \n * Google Chrome 13.0.782.81 \n * Google Chrome 13.0.782.82 \n * Google Chrome 13.0.782.83 \n * Google Chrome 13.0.782.84 \n * Google Chrome 13.0.782.85 \n * Google Chrome 13.0.782.86 \n * Google Chrome 13.0.782.87 \n * Google Chrome 13.0.782.88 \n * Google Chrome 13.0.782.89 \n * Google Chrome 13.0.782.90 \n * Google Chrome 13.0.782.91 \n * Google Chrome 13.0.782.92 \n * Google Chrome 13.0.782.93 \n * Google Chrome 13.0.782.94 \n * Google Chrome 13.0.782.95 \n * Google Chrome 13.0.782.96 \n * Google Chrome 13.0.782.97 \n * Google Chrome 13.0.782.98 \n * Google Chrome 13.0.782.99 \n * Google Chrome 14 \n * Google Chrome 14.0.783.0 \n * Google Chrome 14.0.784.0 \n * Google Chrome 14.0.785.0 \n * Google Chrome 14.0.786.0 \n * Google Chrome 14.0.787.0 \n * Google Chrome 14.0.788.0 \n * Google Chrome 14.0.789.0 \n * Google Chrome 14.0.790.0 \n * Google Chrome 14.0.791.0 \n * Google Chrome 14.0.792.0 \n * Google Chrome 14.0.793.0 \n * Google Chrome 14.0.794.0 \n * Google Chrome 14.0.795.0 \n * Google Chrome 14.0.796.0 \n * Google Chrome 14.0.797.0 \n * Google Chrome 14.0.798.0 \n * Google Chrome 14.0.799.0 \n * Google Chrome 14.0.800.0 \n * Google Chrome 14.0.801.0 \n * Google Chrome 14.0.802.0 \n * Google Chrome 14.0.803.0 \n * Google Chrome 14.0.804.0 \n * Google Chrome 14.0.805.0 \n * Google Chrome 14.0.806.0 \n * Google Chrome 14.0.807.0 \n * Google Chrome 14.0.808.0 \n * Google Chrome 14.0.809.0 \n * Google Chrome 14.0.810.0 \n * Google Chrome 14.0.811.0 \n * Google Chrome 14.0.812.0 \n * Google Chrome 14.0.813.0 \n * Google Chrome 14.0.814.0 \n * Google Chrome 14.0.815.0 \n * Google Chrome 14.0.816.0 \n * Google Chrome 14.0.818.0 \n * Google Chrome 14.0.819.0 \n * Google Chrome 14.0.820.0 \n * Google Chrome 14.0.821.0 \n * Google Chrome 14.0.822.0 \n * Google Chrome 14.0.823.0 \n * Google Chrome 14.0.824.0 \n * Google Chrome 14.0.825.0 \n * Google Chrome 14.0.826.0 \n * Google Chrome 14.0.827.0 \n * Google Chrome 14.0.827.10 \n * Google Chrome 14.0.827.12 \n * Google Chrome 14.0.829.1 \n * Google Chrome 14.0.830.0 \n * Google Chrome 14.0.831.0 \n * Google Chrome 14.0.832.0 \n * Google Chrome 14.0.833.0 \n * Google Chrome 14.0.834.0 \n * Google Chrome 14.0.835.0 \n * Google Chrome 14.0.835.1 \n * Google Chrome 14.0.835.100 \n * Google Chrome 14.0.835.101 \n * Google Chrome 14.0.835.102 \n * Google Chrome 14.0.835.103 \n * Google Chrome 14.0.835.104 \n * Google Chrome 14.0.835.105 \n * Google Chrome 14.0.835.106 \n * Google Chrome 14.0.835.107 \n * Google Chrome 14.0.835.108 \n * Google Chrome 14.0.835.109 \n * Google Chrome 14.0.835.11 \n * Google Chrome 14.0.835.110 \n * Google Chrome 14.0.835.111 \n * Google Chrome 14.0.835.112 \n * Google Chrome 14.0.835.113 \n * Google Chrome 14.0.835.114 \n * Google Chrome 14.0.835.115 \n * Google Chrome 14.0.835.116 \n * Google Chrome 14.0.835.117 \n * Google Chrome 14.0.835.118 \n * Google Chrome 14.0.835.119 \n * Google Chrome 14.0.835.120 \n * Google Chrome 14.0.835.121 \n * Google Chrome 14.0.835.122 \n * Google Chrome 14.0.835.123 \n * Google Chrome 14.0.835.124 \n * Google Chrome 14.0.835.125 \n * Google Chrome 14.0.835.126 \n * Google Chrome 14.0.835.127 \n * Google Chrome 14.0.835.128 \n * Google Chrome 14.0.835.13 \n * Google Chrome 14.0.835.14 \n * Google Chrome 14.0.835.149 \n * Google Chrome 14.0.835.15 \n * Google Chrome 14.0.835.150 \n * Google Chrome 14.0.835.151 \n * Google Chrome 14.0.835.152 \n * Google Chrome 14.0.835.153 \n * Google Chrome 14.0.835.154 \n * Google Chrome 14.0.835.155 \n * Google Chrome 14.0.835.156 \n * Google Chrome 14.0.835.157 \n * Google Chrome 14.0.835.158 \n * Google Chrome 14.0.835.159 \n * Google Chrome 14.0.835.16 \n * Google Chrome 14.0.835.160 \n * Google Chrome 14.0.835.161 \n * Google Chrome 14.0.835.162 \n * Google Chrome 14.0.835.163 \n * Google Chrome 14.0.835.18 \n * Google Chrome 14.0.835.184 \n * Google Chrome 14.0.835.186 \n * Google Chrome 14.0.835.187 \n * Google Chrome 14.0.835.2 \n * Google Chrome 14.0.835.20 \n * Google Chrome 14.0.835.202 \n * Google Chrome 14.0.835.203 \n * Google Chrome 14.0.835.204 \n * Google Chrome 14.0.835.21 \n * Google Chrome 14.0.835.22 \n * Google Chrome 14.0.835.23 \n * Google Chrome 14.0.835.24 \n * Google Chrome 14.0.835.25 \n * Google Chrome 14.0.835.26 \n * Google Chrome 14.0.835.27 \n * Google Chrome 14.0.835.28 \n * Google Chrome 14.0.835.29 \n * Google Chrome 14.0.835.30 \n * Google Chrome 14.0.835.31 \n * Google Chrome 14.0.835.32 \n * Google Chrome 14.0.835.33 \n * Google Chrome 14.0.835.34 \n * Google Chrome 14.0.835.35 \n * Google Chrome 14.0.835.4 \n * Google Chrome 14.0.835.8 \n * Google Chrome 14.0.835.86 \n * Google Chrome 14.0.835.87 \n * Google Chrome 14.0.835.88 \n * Google Chrome 14.0.835.89 \n * Google Chrome 14.0.835.9 \n * Google Chrome 14.0.835.90 \n * Google Chrome 14.0.835.91 \n * Google Chrome 14.0.835.92 \n * Google Chrome 14.0.835.93 \n * Google Chrome 14.0.835.94 \n * Google Chrome 14.0.835.95 \n * Google Chrome 14.0.835.96 \n * Google Chrome 14.0.835.97 \n * Google Chrome 14.0.835.98 \n * Google Chrome 14.0.835.99 \n * Google Chrome 14.0.836.0 \n * Google Chrome 14.0.837.0 \n * Google Chrome 14.0.838.0 \n * Google Chrome 14.0.839.0 \n * Google Chrome 15 \n * Google Chrome 15.0.859.0 \n * Google Chrome 15.0.860.0 \n * Google Chrome 15.0.861.0 \n * Google Chrome 15.0.862.0 \n * Google Chrome 15.0.862.1 \n * Google Chrome 15.0.863.0 \n * Google Chrome 15.0.864.0 \n * Google Chrome 15.0.865.0 \n * Google Chrome 15.0.866.0 \n * Google Chrome 15.0.867.0 \n * Google Chrome 15.0.868.0 \n * Google Chrome 15.0.868.1 \n * Google Chrome 15.0.869.0 \n * Google Chrome 15.0.870.0 \n * Google Chrome 15.0.871.0 \n * Google Chrome 15.0.871.1 \n * Google Chrome 15.0.872.0 \n * Google Chrome 15.0.873.0 \n * Google Chrome 15.0.874 102 \n * Google Chrome 15.0.874.0 \n * Google Chrome 15.0.874.1 \n * Google Chrome 15.0.874.10 \n * Google Chrome 15.0.874.101 \n * Google Chrome 15.0.874.102 \n * Google Chrome 15.0.874.103 \n * Google Chrome 15.0.874.104 \n * Google Chrome 15.0.874.106 \n * Google Chrome 15.0.874.11 \n * Google Chrome 15.0.874.116 \n * Google Chrome 15.0.874.117 \n * Google Chrome 15.0.874.119 \n * Google Chrome 15.0.874.12 \n * Google Chrome 15.0.874.120 \n * Google Chrome 15.0.874.121 \n * Google Chrome 15.0.874.13 \n * Google Chrome 15.0.874.14 \n * Google Chrome 15.0.874.15 \n * Google Chrome 15.0.874.16 \n * Google Chrome 15.0.874.17 \n * Google Chrome 15.0.874.18 \n * Google Chrome 15.0.874.19 \n * Google Chrome 15.0.874.2 \n * Google Chrome 15.0.874.20 \n * Google Chrome 15.0.874.21 \n * Google Chrome 15.0.874.22 \n * Google Chrome 15.0.874.23 \n * Google Chrome 15.0.874.24 \n * Google Chrome 15.0.874.3 \n * Google Chrome 15.0.874.4 \n * Google Chrome 15.0.874.44 \n * Google Chrome 15.0.874.45 \n * Google Chrome 15.0.874.46 \n * Google Chrome 15.0.874.47 \n * Google Chrome 15.0.874.48 \n * Google Chrome 15.0.874.49 \n * Google Chrome 15.0.874.5 \n * Google Chrome 15.0.874.6 \n * Google Chrome 15.0.874.7 \n * Google Chrome 15.0.874.8 \n * Google Chrome 15.0.874.9 \n * Google Chrome 16 \n * Google Chrome 16.0.877.0 \n * Google Chrome 16.0.878.0 \n * Google Chrome 16.0.879.0 \n * Google Chrome 16.0.880.0 \n * Google Chrome 16.0.881.0 \n * Google Chrome 16.0.882.0 \n * Google Chrome 16.0.883.0 \n * Google Chrome 16.0.884.0 \n * Google Chrome 16.0.885.0 \n * Google Chrome 16.0.886.0 \n * Google Chrome 16.0.886.1 \n * Google Chrome 16.0.887.0 \n * Google Chrome 16.0.888.0 \n * Google Chrome 16.0.889.0 \n * Google Chrome 16.0.889.2 \n * Google Chrome 16.0.889.3 \n * Google Chrome 16.0.890.0 \n * Google Chrome 16.0.890.1 \n * Google Chrome 16.0.891.0 \n * Google Chrome 16.0.891.1 \n * Google Chrome 16.0.892.0 \n * Google Chrome 16.0.893.0 \n * Google Chrome 16.0.893.1 \n * Google Chrome 16.0.894.0 \n * Google Chrome 16.0.895.0 \n * Google Chrome 16.0.896.0 \n * Google Chrome 16.0.897.0 \n * Google Chrome 16.0.898.0 \n * Google Chrome 16.0.899.0 \n * Google Chrome 16.0.900.0 \n * Google Chrome 16.0.901.0 \n * Google Chrome 16.0.902.0 \n * Google Chrome 16.0.903.0 \n * Google Chrome 16.0.904.0 \n * Google Chrome 16.0.905.0 \n * Google Chrome 16.0.906.0 \n * Google Chrome 16.0.906.1 \n * Google Chrome 16.0.907.0 \n * Google Chrome 16.0.908.0 \n * Google Chrome 16.0.909.0 \n * Google Chrome 16.0.910.0 \n * Google Chrome 16.0.911.0 \n * Google Chrome 16.0.911.1 \n * Google Chrome 16.0.911.2 \n * Google Chrome 16.0.912.0 \n * Google Chrome 16.0.912.1 \n * Google Chrome 16.0.912.10 \n * Google Chrome 16.0.912.11 \n * Google Chrome 16.0.912.12 \n * Google Chrome 16.0.912.13 \n * Google Chrome 16.0.912.14 \n * Google Chrome 16.0.912.15 \n * Google Chrome 16.0.912.19 \n * Google Chrome 16.0.912.2 \n * Google Chrome 16.0.912.20 \n * Google Chrome 16.0.912.21 \n * Google Chrome 16.0.912.22 \n * Google Chrome 16.0.912.23 \n * Google Chrome 16.0.912.24 \n * Google Chrome 16.0.912.25 \n * Google Chrome 16.0.912.26 \n * Google Chrome 16.0.912.27 \n * Google Chrome 16.0.912.28 \n * Google Chrome 16.0.912.29 \n * Google Chrome 16.0.912.3 \n * Google Chrome 16.0.912.30 \n * Google Chrome 16.0.912.31 \n * Google Chrome 16.0.912.32 \n * Google Chrome 16.0.912.33 \n * Google Chrome 16.0.912.34 \n * Google Chrome 16.0.912.35 \n * Google Chrome 16.0.912.36 \n * Google Chrome 16.0.912.37 \n * Google Chrome 16.0.912.38 \n * Google Chrome 16.0.912.39 \n * Google Chrome 16.0.912.4 \n * Google Chrome 16.0.912.40 \n * Google Chrome 16.0.912.41 \n * Google Chrome 16.0.912.42 \n * Google Chrome 16.0.912.43 \n * Google Chrome 16.0.912.5 \n * Google Chrome 16.0.912.6 \n * Google Chrome 16.0.912.62 \n * Google Chrome 16.0.912.63 \n * Google Chrome 16.0.912.66 \n * Google Chrome 16.0.912.7 \n * Google Chrome 16.0.912.74 \n * Google Chrome 16.0.912.75 \n * Google Chrome 16.0.912.76 \n * Google Chrome 16.0.912.77 \n * Google Chrome 16.0.912.8 \n * Google Chrome 16.0.912.9 \n * Google Chrome 17 \n * Google Chrome 17.0.921.3 \n * Google Chrome 17.0.922.0 \n * Google Chrome 17.0.923.0 \n * Google Chrome 17.0.923.1 \n * Google Chrome 17.0.924.0 \n * Google Chrome 17.0.925.0 \n * Google Chrome 17.0.926.0 \n * Google Chrome 17.0.927.0 \n * Google Chrome 17.0.928.0 \n * Google Chrome 17.0.928.1 \n * Google Chrome 17.0.928.2 \n * Google Chrome 17.0.928.3 \n * Google Chrome 17.0.929.0 \n * Google Chrome 17.0.930.0 \n * Google Chrome 17.0.931.0 \n * Google Chrome 17.0.932.0 \n * Google Chrome 17.0.933.0 \n * Google Chrome 17.0.933.1 \n * Google Chrome 17.0.934.0 \n * Google Chrome 17.0.935.0 \n * Google Chrome 17.0.935.1 \n * Google Chrome 17.0.936.0 \n * Google Chrome 17.0.936.1 \n * Google Chrome 17.0.937.0 \n * Google Chrome 17.0.938.0 \n * Google Chrome 17.0.939.0 \n * Google Chrome 17.0.939.1 \n * Google Chrome 17.0.940.0 \n * Google Chrome 17.0.941.0 \n * Google Chrome 17.0.942.0 \n * Google Chrome 17.0.943.0 \n * Google Chrome 17.0.944.0 \n * Google Chrome 17.0.945.0 \n * Google Chrome 17.0.946.0 \n * Google Chrome 17.0.947.0 \n * Google Chrome 17.0.948.0 \n * Google Chrome 17.0.949.0 \n * Google Chrome 17.0.950.0 \n * Google Chrome 17.0.951.0 \n * Google Chrome 17.0.952.0 \n * Google Chrome 17.0.953.0 \n * Google Chrome 17.0.954.0 \n * Google Chrome 17.0.954.1 \n * Google Chrome 17.0.954.2 \n * Google Chrome 17.0.954.3 \n * Google Chrome 17.0.955.0 \n * Google Chrome 17.0.956.0 \n * Google Chrome 17.0.957.0 \n * Google Chrome 17.0.958.0 \n * Google Chrome 17.0.958.1 \n * Google Chrome 17.0.959.0 \n * Google Chrome 17.0.960.0 \n * Google Chrome 17.0.961.0 \n * Google Chrome 17.0.962.0 \n * Google Chrome 17.0.963.0 \n * Google Chrome 17.0.963.1 \n * Google Chrome 17.0.963.10 \n * Google Chrome 17.0.963.11 \n * Google Chrome 17.0.963.12 \n * Google Chrome 17.0.963.13 \n * Google Chrome 17.0.963.14 \n * Google Chrome 17.0.963.15 \n * Google Chrome 17.0.963.16 \n * Google Chrome 17.0.963.17 \n * Google Chrome 17.0.963.18 \n * Google Chrome 17.0.963.19 \n * Google Chrome 17.0.963.2 \n * Google Chrome 17.0.963.20 \n * Google Chrome 17.0.963.21 \n * Google Chrome 17.0.963.22 \n * Google Chrome 17.0.963.23 \n * Google Chrome 17.0.963.24 \n * Google Chrome 17.0.963.25 \n * Google Chrome 17.0.963.26 \n * Google Chrome 17.0.963.27 \n * Google Chrome 17.0.963.28 \n * Google Chrome 17.0.963.29 \n * Google Chrome 17.0.963.3 \n * Google Chrome 17.0.963.30 \n * Google Chrome 17.0.963.31 \n * Google Chrome 17.0.963.32 \n * Google Chrome 17.0.963.33 \n * Google Chrome 17.0.963.34 \n * Google Chrome 17.0.963.35 \n * Google Chrome 17.0.963.36 \n * Google Chrome 17.0.963.37 \n * Google Chrome 17.0.963.38 \n * Google Chrome 17.0.963.39 \n * Google Chrome 17.0.963.4 \n * Google Chrome 17.0.963.40 \n * Google Chrome 17.0.963.41 \n * Google Chrome 17.0.963.42 \n * Google Chrome 17.0.963.43 \n * Google Chrome 17.0.963.44 \n * Google Chrome 17.0.963.45 \n * Google Chrome 17.0.963.46 \n * Google Chrome 17.0.963.47 \n * Google Chrome 17.0.963.48 \n * Google Chrome 17.0.963.49 \n * Google Chrome 17.0.963.5 \n * Google Chrome 17.0.963.50 \n * Google Chrome 17.0.963.51 \n * Google Chrome 17.0.963.52 \n * Google Chrome 17.0.963.53 \n * Google Chrome 17.0.963.54 \n * Google Chrome 17.0.963.55 \n * Google Chrome 17.0.963.56 \n * Google Chrome 17.0.963.57 \n * Google Chrome 17.0.963.59 \n * Google Chrome 17.0.963.6 \n * Google Chrome 17.0.963.60 \n * Google Chrome 17.0.963.61 \n * Google Chrome 17.0.963.62 \n * Google Chrome 17.0.963.63 \n * Google Chrome 17.0.963.64 \n * Google Chrome 17.0.963.65 \n * Google Chrome 17.0.963.66 \n * Google Chrome 17.0.963.67 \n * Google Chrome 17.0.963.69 \n * Google Chrome 17.0.963.7 \n * Google Chrome 17.0.963.70 \n * Google Chrome 17.0.963.74 \n * Google Chrome 17.0.963.75 \n * Google Chrome 17.0.963.76 \n * Google Chrome 17.0.963.77 \n * Google Chrome 17.0.963.78 \n * Google Chrome 17.0.963.79 \n * Google Chrome 17.0.963.8 \n * Google Chrome 17.0.963.80 \n * Google Chrome 17.0.963.81 \n * Google Chrome 17.0.963.82 \n * Google Chrome 17.0.963.83 \n * Google Chrome 17.0.963.84 \n * Google Chrome 17.0.963.9 \n * Google Chrome 18 \n * Google Chrome 18.0.1000.0 \n * Google Chrome 18.0.1001.0 \n * Google Chrome 18.0.1001.1 \n * Google Chrome 18.0.1002.0 \n * Google Chrome 18.0.1003.0 \n * Google Chrome 18.0.1003.1 \n * Google Chrome 18.0.1004.0 \n * Google Chrome 18.0.1005.0 \n * Google Chrome 18.0.1006.0 \n * Google Chrome 18.0.1007.0 \n * Google Chrome 18.0.1008.0 \n * Google Chrome 18.0.1009.0 \n * Google Chrome 18.0.1010.0 \n * Google Chrome 18.0.1010.1 \n * Google Chrome 18.0.1010.2 \n * Google Chrome 18.0.1011.1 \n * Google Chrome 18.0.1012.0 \n * Google Chrome 18.0.1012.1 \n * Google Chrome 18.0.1012.2 \n * Google Chrome 18.0.1013.0 \n * Google Chrome 18.0.1014.0 \n * Google Chrome 18.0.1015.0 \n * Google Chrome 18.0.1016.0 \n * Google Chrome 18.0.1017.0 \n * Google Chrome 18.0.1017.1 \n * Google Chrome 18.0.1017.2 \n * Google Chrome 18.0.1017.3 \n * Google Chrome 18.0.1018.0 \n * Google Chrome 18.0.1019.0 \n * Google Chrome 18.0.1019.1 \n * Google Chrome 18.0.1020.0 \n * Google Chrome 18.0.1021.0 \n * Google Chrome 18.0.1022.0 \n * Google Chrome 18.0.1023.0 \n * Google Chrome 18.0.1024.0 \n * Google Chrome 18.0.1025.0 \n * Google Chrome 18.0.1025.1 \n * Google Chrome 18.0.1025.10 \n * Google Chrome 18.0.1025.100 \n * Google Chrome 18.0.1025.102 \n * Google Chrome 18.0.1025.107 \n * Google Chrome 18.0.1025.108 \n * Google Chrome 18.0.1025.109 \n * Google Chrome 18.0.1025.110 \n * Google Chrome 18.0.1025.111 \n * Google Chrome 18.0.1025.112 \n * Google Chrome 18.0.1025.113 \n * Google Chrome 18.0.1025.114 \n * Google Chrome 18.0.1025.116 \n * Google Chrome 18.0.1025.117 \n * Google Chrome 18.0.1025.118 \n * Google Chrome 18.0.1025.120 \n * Google Chrome 18.0.1025.129 \n * Google Chrome 18.0.1025.130 \n * Google Chrome 18.0.1025.131 \n * Google Chrome 18.0.1025.132 \n * Google Chrome 18.0.1025.133 \n * Google Chrome 18.0.1025.134 \n * Google Chrome 18.0.1025.135 \n * Google Chrome 18.0.1025.136 \n * Google Chrome 18.0.1025.137 \n * Google Chrome 18.0.1025.139 \n * Google Chrome 18.0.1025.140 \n * Google Chrome 18.0.1025.142 \n * Google Chrome 18.0.1025.145 \n * Google Chrome 18.0.1025.146 \n * Google Chrome 18.0.1025.147 \n * Google Chrome 18.0.1025.148 \n * Google Chrome 18.0.1025.149 \n * Google Chrome 18.0.1025.150 \n * Google Chrome 18.0.1025.151 \n * Google Chrome 18.0.1025.162 \n * Google Chrome 18.0.1025.168 \n * Google Chrome 18.0.1025.2 \n * Google Chrome 18.0.1025.29 \n * Google Chrome 18.0.1025.3 \n * Google Chrome 18.0.1025.30 \n * Google Chrome 18.0.1025.31 \n * Google Chrome 18.0.1025.32 \n * Google Chrome 18.0.1025.33 \n * Google Chrome 18.0.1025.35 \n * Google Chrome 18.0.1025.36 \n * Google Chrome 18.0.1025.37 \n * Google Chrome 18.0.1025.38 \n * Google Chrome 18.0.1025.39 \n * Google Chrome 18.0.1025.4 \n * Google Chrome 18.0.1025.40 \n * Google Chrome 18.0.1025.41 \n * Google Chrome 18.0.1025.42 \n * Google Chrome 18.0.1025.43 \n * Google Chrome 18.0.1025.44 \n * Google Chrome 18.0.1025.45 \n * Google Chrome 18.0.1025.46 \n * Google Chrome 18.0.1025.47 \n * Google Chrome 18.0.1025.48 \n * Google Chrome 18.0.1025.49 \n * Google Chrome 18.0.1025.5 \n * Google Chrome 18.0.1025.50 \n * Google Chrome 18.0.1025.51 \n * Google Chrome 18.0.1025.52 \n * Google Chrome 18.0.1025.54 \n * Google Chrome 18.0.1025.55 \n * Google Chrome 18.0.1025.56 \n * Google Chrome 18.0.1025.57 \n * Google Chrome 18.0.1025.58 \n * Google Chrome 18.0.1025.6 \n * Google Chrome 18.0.1025.60 \n * Google Chrome 18.0.1025.7 \n * Google Chrome 18.0.1025.73 \n * Google Chrome 18.0.1025.74 \n * Google Chrome 18.0.1025.8 \n * Google Chrome 18.0.1025.9 \n * Google Chrome 18.0.1025.95 \n * Google Chrome 18.0.1025.96 \n * Google Chrome 18.0.1025.97 \n * Google Chrome 18.0.1025.98 \n * Google Chrome 18.0.1025.99 \n * Google Chrome 19 \n * Google Chrome 19.0.1028.0 \n * Google Chrome 19.0.1029.0 \n * Google Chrome 19.0.1030.0 \n * Google Chrome 19.0.1031.0 \n * Google Chrome 19.0.1032.0 \n * Google Chrome 19.0.1033.0 \n * Google Chrome 19.0.1034.0 \n * Google Chrome 19.0.1035.0 \n * Google Chrome 19.0.1036.0 \n * Google Chrome 19.0.1036.2 \n * Google Chrome 19.0.1036.3 \n * Google Chrome 19.0.1036.4 \n * Google Chrome 19.0.1036.6 \n * Google Chrome 19.0.1036.7 \n * Google Chrome 19.0.1037.0 \n * Google Chrome 19.0.1038.0 \n * Google Chrome 19.0.1039.0 \n * Google Chrome 19.0.1040.0 \n * Google Chrome 19.0.1041.0 \n * Google Chrome 19.0.1042.0 \n * Google Chrome 19.0.1043.0 \n * Google Chrome 19.0.1044.0 \n * Google Chrome 19.0.1045.0 \n * Google Chrome 19.0.1046.0 \n * Google Chrome 19.0.1047.0 \n * Google Chrome 19.0.1048.0 \n * Google Chrome 19.0.1049.0 \n * Google Chrome 19.0.1049.1 \n * Google Chrome 19.0.1049.2 \n * Google Chrome 19.0.1049.3 \n * Google Chrome 19.0.1050.0 \n * Google Chrome 19.0.1051.0 \n * Google Chrome 19.0.1052.0 \n * Google Chrome 19.0.1053.0 \n * Google Chrome 19.0.1054.0 \n * Google Chrome 19.0.1055.0 \n * Google Chrome 19.0.1055.1 \n * Google Chrome 19.0.1055.2 \n * Google Chrome 19.0.1055.3 \n * Google Chrome 19.0.1056.0 \n * Google Chrome 19.0.1056.1 \n * Google Chrome 19.0.1057.0 \n * Google Chrome 19.0.1057.1 \n * Google Chrome 19.0.1057.3 \n * Google Chrome 19.0.1058.0 \n * Google Chrome 19.0.1058.1 \n * Google Chrome 19.0.1059.0 \n * Google Chrome 19.0.1060.0 \n * Google Chrome 19.0.1060.1 \n * Google Chrome 19.0.1061.0 \n * Google Chrome 19.0.1061.1 \n * Google Chrome 19.0.1062.0 \n * Google Chrome 19.0.1062.1 \n * Google Chrome 19.0.1063.0 \n * Google Chrome 19.0.1063.1 \n * Google Chrome 19.0.1064.0 \n * Google Chrome 19.0.1065.0 \n * Google Chrome 19.0.1066.0 \n * Google Chrome 19.0.1067.0 \n * Google Chrome 19.0.1068.0 \n * Google Chrome 19.0.1068.1 \n * Google Chrome 19.0.1069.0 \n * Google Chrome 19.0.1070.0 \n * Google Chrome 19.0.1071.0 \n * Google Chrome 19.0.1072.0 \n * Google Chrome 19.0.1073.0 \n * Google Chrome 19.0.1074.0 \n * Google Chrome 19.0.1075.0 \n * Google Chrome 19.0.1076.0 \n * Google Chrome 19.0.1076.1 \n * Google Chrome 19.0.1077.0 \n * Google Chrome 19.0.1077.1 \n * Google Chrome 19.0.1077.2 \n * Google Chrome 19.0.1077.3 \n * Google Chrome 19.0.1078.0 \n * Google Chrome 19.0.1079.0 \n * Google Chrome 19.0.1080.0 \n * Google Chrome 19.0.1081.0 \n * Google Chrome 19.0.1081.2 \n * Google Chrome 19.0.1082.0 \n * Google Chrome 19.0.1082.1 \n * Google Chrome 19.0.1083.0 \n * Google Chrome 19.0.1084.0 \n * Google Chrome 19.0.1084.1 \n * Google Chrome 19.0.1084.10 \n * Google Chrome 19.0.1084.11 \n * Google Chrome 19.0.1084.12 \n * Google Chrome 19.0.1084.13 \n * Google Chrome 19.0.1084.14 \n * Google Chrome 19.0.1084.15 \n * Google Chrome 19.0.1084.16 \n * Google Chrome 19.0.1084.17 \n * Google Chrome 19.0.1084.18 \n * Google Chrome 19.0.1084.19 \n * Google Chrome 19.0.1084.2 \n * Google Chrome 19.0.1084.20 \n * Google Chrome 19.0.1084.21 \n * Google Chrome 19.0.1084.22 \n * Google Chrome 19.0.1084.23 \n * Google Chrome 19.0.1084.24 \n * Google Chrome 19.0.1084.25 \n * Google Chrome 19.0.1084.26 \n * Google Chrome 19.0.1084.27 \n * Google Chrome 19.0.1084.28 \n * Google Chrome 19.0.1084.29 \n * Google Chrome 19.0.1084.3 \n * Google Chrome 19.0.1084.30 \n * Google Chrome 19.0.1084.31 \n * Google Chrome 19.0.1084.32 \n * Google Chrome 19.0.1084.33 \n * Google Chrome 19.0.1084.35 \n * Google Chrome 19.0.1084.36 \n * Google Chrome 19.0.1084.37 \n * Google Chrome 19.0.1084.38 \n * Google Chrome 19.0.1084.39 \n * Google Chrome 19.0.1084.4 \n * Google Chrome 19.0.1084.40 \n * Google Chrome 19.0.1084.41 \n * Google Chrome 19.0.1084.42 \n * Google Chrome 19.0.1084.43 \n * Google Chrome 19.0.1084.44 \n * Google Chrome 19.0.1084.45 \n * Google Chrome 19.0.1084.46 \n * Google Chrome 19.0.1084.47 \n * Google Chrome 19.0.1084.48 \n * Google Chrome 19.0.1084.5 \n * Google Chrome 19.0.1084.50 \n * Google Chrome 19.0.1084.51 \n * Google Chrome 19.0.1084.52 \n * Google Chrome 19.0.1084.6 \n * Google Chrome 19.0.1084.7 \n * Google Chrome 19.0.1084.8 \n * Google Chrome 19.0.1084.9 \n * Google Chrome 19.0.1085.0 \n * Google Chrome 2.0.156.1 \n * Google Chrome 2.0.157.0 \n * Google Chrome 2.0.157.2 \n * Google Chrome 2.0.158.0 \n * Google Chrome 2.0.159.0 \n * Google Chrome 2.0.169.0 \n * Google Chrome 2.0.169.1 \n * Google Chrome 2.0.170.0 \n * Google Chrome 2.0.172 \n * Google Chrome 2.0.172.2 \n * Google Chrome 2.0.172.27 \n * Google Chrome 2.0.172.28 \n * Google Chrome 2.0.172.30 \n * Google Chrome 2.0.172.31 \n * Google Chrome 2.0.172.33 \n * Google Chrome 2.0.172.37 \n * Google Chrome 2.0.172.38 \n * Google Chrome 2.0.172.43 \n * Google Chrome 2.0.172.8 \n * Google Chrome 20 \n * Google Chrome 20.0.1132.0 \n * Google Chrome 20.0.1132.1 \n * Google Chrome 20.0.1132.10 \n * Google Chrome 20.0.1132.11 \n * Google Chrome 20.0.1132.12 \n * Google Chrome 20.0.1132.13 \n * Google Chrome 20.0.1132.14 \n * Google Chrome 20.0.1132.15 \n * Google Chrome 20.0.1132.16 \n * Google Chrome 20.0.1132.17 \n * Google Chrome 20.0.1132.18 \n * Google Chrome 20.0.1132.19 \n * Google Chrome 20.0.1132.2 \n * Google Chrome 20.0.1132.20 \n * Google Chrome 20.0.1132.21 \n * Google Chrome 20.0.1132.22 \n * Google Chrome 20.0.1132.23 \n * Google Chrome 20.0.1132.24 \n * Google Chrome 20.0.1132.25 \n * Google Chrome 20.0.1132.26 \n * Google Chrome 20.0.1132.27 \n * Google Chrome 20.0.1132.28 \n * Google Chrome 20.0.1132.29 \n * Google Chrome 20.0.1132.3 \n * Google Chrome 20.0.1132.30 \n * Google Chrome 20.0.1132.31 \n * Google Chrome 20.0.1132.32 \n * Google Chrome 20.0.1132.33 \n * Google Chrome 20.0.1132.34 \n * Google Chrome 20.0.1132.35 \n * Google Chrome 20.0.1132.36 \n * Google Chrome 20.0.1132.37 \n * Google Chrome 20.0.1132.38 \n * Google Chrome 20.0.1132.39 \n * Google Chrome 20.0.1132.4 \n * Google Chrome 20.0.1132.40 \n * Google Chrome 20.0.1132.41 \n * Google Chrome 20.0.1132.42 \n * Google Chrome 20.0.1132.43 \n * Google Chrome 20.0.1132.45 \n * Google Chrome 20.0.1132.46 \n * Google Chrome 20.0.1132.47 \n * Google Chrome 20.0.1132.5 \n * Google Chrome 20.0.1132.54 \n * Google Chrome 20.0.1132.55 \n * Google Chrome 20.0.1132.56 \n * Google Chrome 20.0.1132.57 \n * Google Chrome 20.0.1132.6 \n * Google Chrome 20.0.1132.7 \n * Google Chrome 20.0.1132.8 \n * Google Chrome 20.0.1132.9 \n * Google Chrome 21 \n * Google Chrome 21.0.1180.0 \n * Google Chrome 21.0.1180.1 \n * Google Chrome 21.0.1180.2 \n * Google Chrome 21.0.1180.31 \n * Google Chrome 21.0.1180.32 \n * Google Chrome 21.0.1180.33 \n * Google Chrome 21.0.1180.34 \n * Google Chrome 21.0.1180.35 \n * Google Chrome 21.0.1180.36 \n * Google Chrome 21.0.1180.37 \n * Google Chrome 21.0.1180.38 \n * Google Chrome 21.0.1180.39 \n * Google Chrome 21.0.1180.41 \n * Google Chrome 21.0.1180.46 \n * Google Chrome 21.0.1180.47 \n * Google Chrome 21.0.1180.48 \n * Google Chrome 21.0.1180.49 \n * Google Chrome 21.0.1180.50 \n * Google Chrome 21.0.1180.51 \n * Google Chrome 21.0.1180.52 \n * Google Chrome 21.0.1180.53 \n * Google Chrome 21.0.1180.54 \n * Google Chrome 21.0.1180.55 \n * Google Chrome 21.0.1180.56 \n * Google Chrome 21.0.1180.57 \n * Google Chrome 21.0.1180.59 \n * Google Chrome 21.0.1180.60 \n * Google Chrome 21.0.1180.61 \n * Google Chrome 21.0.1180.62 \n * Google Chrome 21.0.1180.63 \n * Google Chrome 21.0.1180.64 \n * Google Chrome 21.0.1180.68 \n * Google Chrome 21.0.1180.69 \n * Google Chrome 21.0.1180.70 \n * Google Chrome 21.0.1180.71 \n * Google Chrome 21.0.1180.72 \n * Google Chrome 21.0.1180.73 \n * Google Chrome 21.0.1180.74 \n * Google Chrome 21.0.1180.75 \n * Google Chrome 21.0.1180.76 \n * Google Chrome 21.0.1180.77 \n * Google Chrome 21.0.1180.78 \n * Google Chrome 21.0.1180.79 \n * Google Chrome 21.0.1180.80 \n * Google Chrome 21.0.1180.81 \n * Google Chrome 21.0.1180.82 \n * Google Chrome 21.0.1180.83 \n * Google Chrome 21.0.1180.84 \n * Google Chrome 21.0.1180.85 \n * Google Chrome 21.0.1180.86 \n * Google Chrome 21.0.1180.87 \n * Google Chrome 21.0.1180.88 \n * Google Chrome 21.0.1180.89 \n * Google Chrome 22 \n * Google Chrome 22.0.1229.0 \n * Google Chrome 22.0.1229.1 \n * Google Chrome 22.0.1229.10 \n * Google Chrome 22.0.1229.11 \n * Google Chrome 22.0.1229.12 \n * Google Chrome 22.0.1229.14 \n * Google Chrome 22.0.1229.16 \n * Google Chrome 22.0.1229.17 \n * Google Chrome 22.0.1229.18 \n * Google Chrome 22.0.1229.2 \n * Google Chrome 22.0.1229.20 \n * Google Chrome 22.0.1229.21 \n * Google Chrome 22.0.1229.22 \n * Google Chrome 22.0.1229.23 \n * Google Chrome 22.0.1229.24 \n * Google Chrome 22.0.1229.25 \n * Google Chrome 22.0.1229.26 \n * Google Chrome 22.0.1229.27 \n * Google Chrome 22.0.1229.28 \n * Google Chrome 22.0.1229.29 \n * Google Chrome 22.0.1229.3 \n * Google Chrome 22.0.1229.31 \n * Google Chrome 22.0.1229.32 \n * Google Chrome 22.0.1229.33 \n * Google Chrome 22.0.1229.35 \n * Google Chrome 22.0.1229.36 \n * Google Chrome 22.0.1229.37 \n * Google Chrome 22.0.1229.39 \n * Google Chrome 22.0.1229.4 \n * Google Chrome 22.0.1229.48 \n * Google Chrome 22.0.1229.49 \n * Google Chrome 22.0.1229.50 \n * Google Chrome 22.0.1229.51 \n * Google Chrome 22.0.1229.52 \n * Google Chrome 22.0.1229.53 \n * Google Chrome 22.0.1229.54 \n * Google Chrome 22.0.1229.55 \n * Google Chrome 22.0.1229.56 \n * Google Chrome 22.0.1229.57 \n * Google Chrome 22.0.1229.58 \n * Google Chrome 22.0.1229.59 \n * Google Chrome 22.0.1229.6 \n * Google Chrome 22.0.1229.60 \n * Google Chrome 22.0.1229.62 \n * Google Chrome 22.0.1229.63 \n * Google Chrome 22.0.1229.64 \n * Google Chrome 22.0.1229.65 \n * Google Chrome 22.0.1229.67 \n * Google Chrome 22.0.1229.7 \n * Google Chrome 22.0.1229.76 \n * Google Chrome 22.0.1229.78 \n * Google Chrome 22.0.1229.79 \n * Google Chrome 22.0.1229.8 \n * Google Chrome 22.0.1229.89 \n * Google Chrome 22.0.1229.9 \n * Google Chrome 22.0.1229.91 \n * Google Chrome 22.0.1229.92 \n * Google Chrome 22.0.1229.94 \n * Google Chrome 22.0.1229.95 \n * Google Chrome 22.0.1229.96 \n * Google Chrome 23.0.1271.0 \n * Google Chrome 23.0.1271.1 \n * Google Chrome 23.0.1271.10 \n * Google Chrome 23.0.1271.11 \n * Google Chrome 23.0.1271.12 \n * Google Chrome 23.0.1271.13 \n * Google Chrome 23.0.1271.14 \n * Google Chrome 23.0.1271.15 \n * Google Chrome 23.0.1271.16 \n * Google Chrome 23.0.1271.17 \n * Google Chrome 23.0.1271.18 \n * Google Chrome 23.0.1271.19 \n * Google Chrome 23.0.1271.2 \n * Google Chrome 23.0.1271.20 \n * Google Chrome 23.0.1271.21 \n * Google Chrome 23.0.1271.22 \n * Google Chrome 23.0.1271.23 \n * Google Chrome 23.0.1271.24 \n * Google Chrome 23.0.1271.26 \n * Google Chrome 23.0.1271.3 \n * Google Chrome 23.0.1271.30 \n * Google Chrome 23.0.1271.31 \n * Google Chrome 23.0.1271.32 \n * Google Chrome 23.0.1271.33 \n * Google Chrome 23.0.1271.35 \n * Google Chrome 23.0.1271.36 \n * Google Chrome 23.0.1271.37 \n * Google Chrome 23.0.1271.38 \n * Google Chrome 23.0.1271.39 \n * Google Chrome 23.0.1271.4 \n * Google Chrome 23.0.1271.40 \n * Google Chrome 23.0.1271.41 \n * Google Chrome 23.0.1271.44 \n * Google Chrome 23.0.1271.45 \n * Google Chrome 23.0.1271.46 \n * Google Chrome 23.0.1271.49 \n * Google Chrome 23.0.1271.5 \n * Google Chrome 23.0.1271.50 \n * Google Chrome 23.0.1271.51 \n * Google Chrome 23.0.1271.52 \n * Google Chrome 23.0.1271.53 \n * Google Chrome 23.0.1271.54 \n * Google Chrome 23.0.1271.55 \n * Google Chrome 23.0.1271.56 \n * Google Chrome 23.0.1271.57 \n * Google Chrome 23.0.1271.58 \n * Google Chrome 23.0.1271.59 \n * Google Chrome 23.0.1271.6 \n * Google Chrome 23.0.1271.60 \n * Google Chrome 23.0.1271.61 \n * Google Chrome 23.0.1271.62 \n * Google Chrome 23.0.1271.64 \n * Google Chrome 23.0.1271.7 \n * Google Chrome 23.0.1271.8 \n * Google Chrome 23.0.1271.83 \n * Google Chrome 23.0.1271.84 \n * Google Chrome 23.0.1271.85 \n * Google Chrome 23.0.1271.86 \n * Google Chrome 23.0.1271.87 \n * Google Chrome 23.0.1271.88 \n * Google Chrome 23.0.1271.89 \n * Google Chrome 23.0.1271.9 \n * Google Chrome 23.0.1271.91 \n * Google Chrome 23.0.1271.95 \n * Google Chrome 23.0.1271.96 \n * Google Chrome 23.0.1271.97 \n * Google Chrome 24.0.1272.0 \n * Google Chrome 24.0.1272.1 \n * Google Chrome 24.0.1273.0 \n * Google Chrome 24.0.1274.0 \n * Google Chrome 24.0.1275.0 \n * Google Chrome 24.0.1276.0 \n * Google Chrome 24.0.1276.1 \n * Google Chrome 24.0.1277.0 \n * Google Chrome 24.0.1278.0 \n * Google Chrome 24.0.1279.0 \n * Google Chrome 24.0.1280.0 \n * Google Chrome 24.0.1281.0 \n * Google Chrome 24.0.1281.1 \n * Google Chrome 24.0.1281.2 \n * Google Chrome 24.0.1281.3 \n * Google Chrome 24.0.1282.0 \n * Google Chrome 24.0.1283.0 \n * Google Chrome 24.0.1284.0 \n * Google Chrome 24.0.1284.1 \n * Google Chrome 24.0.1284.2 \n * Google Chrome 24.0.1285.0 \n * Google Chrome 24.0.1285.1 \n * Google Chrome 24.0.1285.2 \n * Google Chrome 24.0.1286.0 \n * Google Chrome 24.0.1286.1 \n * Google Chrome 24.0.1287.0 \n * Google Chrome 24.0.1287.1 \n * Google Chrome 24.0.1288.0 \n * Google Chrome 24.0.1288.1 \n * Google Chrome 24.0.1289.0 \n * Google Chrome 24.0.1289.1 \n * Google Chrome 24.0.1290.0 \n * Google Chrome 24.0.1291.0 \n * Google Chrome 24.0.1292.0 \n * Google Chrome 24.0.1293.0 \n * Google Chrome 24.0.1294.0 \n * Google Chrome 24.0.1295.0 \n * Google Chrome 24.0.1296.0 \n * Google Chrome 24.0.1297.0 \n * Google Chrome 24.0.1298.0 \n * Google Chrome 24.0.1299.0 \n * Google Chrome 24.0.1300.0 \n * Google Chrome 24.0.1301.0 \n * Google Chrome 24.0.1301.2 \n * Google Chrome 24.0.1302.0 \n * Google Chrome 24.0.1303.0 \n * Google Chrome 24.0.1304.0 \n * Google Chrome 24.0.1304.1 \n * Google Chrome 24.0.1305.0 \n * Google Chrome 24.0.1305.1 \n * Google Chrome 24.0.1305.2 \n * Google Chrome 24.0.1305.3 \n * Google Chrome 24.0.1305.4 \n * Google Chrome 24.0.1306.0 \n * Google Chrome 24.0.1306.1 \n * Google Chrome 24.0.1307.0 \n * Google Chrome 24.0.1307.1 \n * Google Chrome 24.0.1308.0 \n * Google Chrome 24.0.1309.0 \n * Google Chrome 24.0.1310.0 \n * Google Chrome 24.0.1311.0 \n * Google Chrome 24.0.1311.1 \n * Google Chrome 24.0.1312.0 \n * Google Chrome 24.0.1312.1 \n * Google Chrome 24.0.1312.10 \n * Google Chrome 24.0.1312.11 \n * Google Chrome 24.0.1312.12 \n * Google Chrome 24.0.1312.13 \n * Google Chrome 24.0.1312.14 \n * Google Chrome 24.0.1312.15 \n * Google Chrome 24.0.1312.16 \n * Google Chrome 24.0.1312.17 \n * Google Chrome 24.0.1312.18 \n * Google Chrome 24.0.1312.19 \n * Google Chrome 24.0.1312.20 \n * Google Chrome 24.0.1312.21 \n * Google Chrome 24.0.1312.22 \n * Google Chrome 24.0.1312.23 \n * Google Chrome 24.0.1312.24 \n * Google Chrome 24.0.1312.25 \n * Google Chrome 24.0.1312.26 \n * Google Chrome 24.0.1312.27 \n * Google Chrome 24.0.1312.28 \n * Google Chrome 24.0.1312.29 \n * Google Chrome 24.0.1312.30 \n * Google Chrome 24.0.1312.31 \n * Google Chrome 24.0.1312.32 \n * Google Chrome 24.0.1312.33 \n * Google Chrome 24.0.1312.34 \n * Google Chrome 24.0.1312.35 \n * Google Chrome 24.0.1312.36 \n * Google Chrome 24.0.1312.37 \n * Google Chrome 24.0.1312.38 \n * Google Chrome 24.0.1312.39 \n * Google Chrome 24.0.1312.4 \n * Google Chrome 24.0.1312.40 \n * Google Chrome 24.0.1312.41 \n * Google Chrome 24.0.1312.42 \n * Google Chrome 24.0.1312.43 \n * Google Chrome 24.0.1312.44 \n * Google Chrome 24.0.1312.45 \n * Google Chrome 24.0.1312.46 \n * Google Chrome 24.0.1312.47 \n * Google Chrome 24.0.1312.48 \n * Google Chrome 24.0.1312.49 \n * Google Chrome 24.0.1312.5 \n * Google Chrome 24.0.1312.50 \n * Google Chrome 24.0.1312.51 \n * Google Chrome 24.0.1312.52 \n * Google Chrome 24.0.1312.53 \n * Google Chrome 24.0.1312.54 \n * Google Chrome 24.0.1312.55 \n * Google Chrome 24.0.1312.56 \n * Google Chrome 24.0.1312.57 \n * Google Chrome 24.0.1312.6 \n * Google Chrome 24.0.1312.7 \n * Google Chrome 24.0.1312.70 \n * Google Chrome 24.0.1312.8 \n * Google Chrome 24.0.1312.9 \n * Google Chrome 25 \n * Google Chrome 25.0.1364.0 \n * Google Chrome 25.0.1364.1 \n * Google Chrome 25.0.1364.10 \n * Google Chrome 25.0.1364.108 \n * Google Chrome 25.0.1364.11 \n * Google Chrome 25.0.1364.110 \n * Google Chrome 25.0.1364.112 \n * Google Chrome 25.0.1364.113 \n * Google Chrome 25.0.1364.114 \n * Google Chrome 25.0.1364.115 \n * Google Chrome 25.0.1364.116 \n * Google Chrome 25.0.1364.117 \n * Google Chrome 25.0.1364.118 \n * Google Chrome 25.0.1364.119 \n * Google Chrome 25.0.1364.12 \n * Google Chrome 25.0.1364.120 \n * Google Chrome 25.0.1364.121 \n * Google Chrome 25.0.1364.122 \n * Google Chrome 25.0.1364.123 \n * Google Chrome 25.0.1364.124 \n * Google Chrome 25.0.1364.125 \n * Google Chrome 25.0.1364.126 \n * Google Chrome 25.0.1364.13 \n * Google Chrome 25.0.1364.14 \n * Google Chrome 25.0.1364.15 \n * Google Chrome 25.0.1364.152 \n * Google Chrome 25.0.1364.16 \n * Google Chrome 25.0.1364.160 \n * Google Chrome 25.0.1364.17 \n * Google Chrome 25.0.1364.172 \n * Google Chrome 25.0.1364.18 \n * Google Chrome 25.0.1364.19 \n * Google Chrome 25.0.1364.2 \n * Google Chrome 25.0.1364.20 \n * Google Chrome 25.0.1364.21 \n * Google Chrome 25.0.1364.22 \n * Google Chrome 25.0.1364.23 \n * Google Chrome 25.0.1364.24 \n * Google Chrome 25.0.1364.25 \n * Google Chrome 25.0.1364.26 \n * Google Chrome 25.0.1364.27 \n * Google Chrome 25.0.1364.28 \n * Google Chrome 25.0.1364.29 \n * Google Chrome 25.0.1364.3 \n * Google Chrome 25.0.1364.30 \n * Google Chrome 25.0.1364.31 \n * Google Chrome 25.0.1364.32 \n * Google Chrome 25.0.1364.33 \n * Google Chrome 25.0.1364.34 \n * Google Chrome 25.0.1364.35 \n * Google Chrome 25.0.1364.36 \n * Google Chrome 25.0.1364.37 \n * Google Chrome 25.0.1364.38 \n * Google Chrome 25.0.1364.39 \n * Google Chrome 25.0.1364.40 \n * Google Chrome 25.0.1364.41 \n * Google Chrome 25.0.1364.42 \n * Google Chrome 25.0.1364.43 \n * Google Chrome 25.0.1364.44 \n * Google Chrome 25.0.1364.45 \n * Google Chrome 25.0.1364.46 \n * Google Chrome 25.0.1364.47 \n * Google Chrome 25.0.1364.48 \n * Google Chrome 25.0.1364.49 \n * Google Chrome 25.0.1364.5 \n * Google Chrome 25.0.1364.50 \n * Google Chrome 25.0.1364.51 \n * Google Chrome 25.0.1364.52 \n * Google Chrome 25.0.1364.53 \n * Google Chrome 25.0.1364.54 \n * Google Chrome 25.0.1364.55 \n * Google Chrome 25.0.1364.56 \n * Google Chrome 25.0.1364.57 \n * Google Chrome 25.0.1364.58 \n * Google Chrome 25.0.1364.61 \n * Google Chrome 25.0.1364.62 \n * Google Chrome 25.0.1364.63 \n * Google Chrome 25.0.1364.65 \n * Google Chrome 25.0.1364.66 \n * Google Chrome 25.0.1364.67 \n * Google Chrome 25.0.1364.68 \n * Google Chrome 25.0.1364.7 \n * Google Chrome 25.0.1364.70 \n * Google Chrome 25.0.1364.72 \n * Google Chrome 25.0.1364.73 \n * Google Chrome 25.0.1364.74 \n * Google Chrome 25.0.1364.75 \n * Google Chrome 25.0.1364.76 \n * Google Chrome 25.0.1364.77 \n * Google Chrome 25.0.1364.78 \n * Google Chrome 25.0.1364.79 \n * Google Chrome 25.0.1364.8 \n * Google Chrome 25.0.1364.80 \n * Google Chrome 25.0.1364.81 \n * Google Chrome 25.0.1364.82 \n * Google Chrome 25.0.1364.84 \n * Google Chrome 25.0.1364.85 \n * Google Chrome 25.0.1364.86 \n * Google Chrome 25.0.1364.87 \n * Google Chrome 25.0.1364.88 \n * Google Chrome 25.0.1364.89 \n * Google Chrome 25.0.1364.9 \n * Google Chrome 25.0.1364.90 \n * Google Chrome 25.0.1364.91 \n * Google Chrome 25.0.1364.92 \n * Google Chrome 25.0.1364.93 \n * Google Chrome 25.0.1364.95 \n * Google Chrome 25.0.1364.97 \n * Google Chrome 25.0.1364.98 \n * Google Chrome 25.0.1364.99 \n * Google Chrome 26.0.1410.28 \n * Google Chrome 26.0.1410.43 \n * Google Chrome 26.0.1410.46 \n * Google Chrome 26.0.1410.53 \n * Google Chrome 26.0.1410.63 \n * Google Chrome 26.0.1410.64 \n * Google Chrome 27.0.1444.0 \n * Google Chrome 27.0.1444.3 \n * Google Chrome 27.0.1453.0 \n * Google Chrome 27.0.1453.1 \n * Google Chrome 27.0.1453.10 \n * Google Chrome 27.0.1453.102 \n * Google Chrome 27.0.1453.103 \n * Google Chrome 27.0.1453.104 \n * Google Chrome 27.0.1453.105 \n * Google Chrome 27.0.1453.106 \n * Google Chrome 27.0.1453.107 \n * Google Chrome 27.0.1453.108 \n * Google Chrome 27.0.1453.109 \n * Google Chrome 27.0.1453.11 \n * Google Chrome 27.0.1453.110 \n * Google Chrome 27.0.1453.111 \n * Google Chrome 27.0.1453.112 \n * Google Chrome 27.0.1453.113 \n * Google Chrome 27.0.1453.114 \n * Google Chrome 27.0.1453.115 \n * Google Chrome 27.0.1453.116 \n * Google Chrome 27.0.1453.12 \n * Google Chrome 27.0.1453.13 \n * Google Chrome 27.0.1453.15 \n * Google Chrome 27.0.1453.2 \n * Google Chrome 27.0.1453.3 \n * Google Chrome 27.0.1453.34 \n * Google Chrome 27.0.1453.35 \n * Google Chrome 27.0.1453.36 \n * Google Chrome 27.0.1453.37 \n * Google Chrome 27.0.1453.38 \n * Google Chrome 27.0.1453.39 \n * Google Chrome 27.0.1453.4 \n * Google Chrome 27.0.1453.40 \n * Google Chrome 27.0.1453.41 \n * Google Chrome 27.0.1453.42 \n * Google Chrome 27.0.1453.43 \n * Google Chrome 27.0.1453.44 \n * Google Chrome 27.0.1453.45 \n * Google Chrome 27.0.1453.46 \n * Google Chrome 27.0.1453.47 \n * Google Chrome 27.0.1453.49 \n * Google Chrome 27.0.1453.5 \n * Google Chrome 27.0.1453.50 \n * Google Chrome 27.0.1453.51 \n * Google Chrome 27.0.1453.52 \n * Google Chrome 27.0.1453.54 \n * Google Chrome 27.0.1453.55 \n * Google Chrome 27.0.1453.56 \n * Google Chrome 27.0.1453.57 \n * Google Chrome 27.0.1453.58 \n * Google Chrome 27.0.1453.59 \n * Google Chrome 27.0.1453.6 \n * Google Chrome 27.0.1453.60 \n * Google Chrome 27.0.1453.61 \n * Google Chrome 27.0.1453.62 \n * Google Chrome 27.0.1453.63 \n * Google Chrome 27.0.1453.64 \n * Google Chrome 27.0.1453.65 \n * Google Chrome 27.0.1453.66 \n * Google Chrome 27.0.1453.67 \n * Google Chrome 27.0.1453.68 \n * Google Chrome 27.0.1453.69 \n * Google Chrome 27.0.1453.7 \n * Google Chrome 27.0.1453.70 \n * Google Chrome 27.0.1453.71 \n * Google Chrome 27.0.1453.72 \n * Google Chrome 27.0.1453.73 \n * Google Chrome 27.0.1453.74 \n * Google Chrome 27.0.1453.75 \n * Google Chrome 27.0.1453.76 \n * Google Chrome 27.0.1453.77 \n * Google Chrome 27.0.1453.78 \n * Google Chrome 27.0.1453.79 \n * Google Chrome 27.0.1453.8 \n * Google Chrome 27.0.1453.80 \n * Google Chrome 27.0.1453.81 \n * Google Chrome 27.0.1453.82 \n * Google Chrome 27.0.1453.83 \n * Google Chrome 27.0.1453.84 \n * Google Chrome 27.0.1453.85 \n * Google Chrome 27.0.1453.86 \n * Google Chrome 27.0.1453.87 \n * Google Chrome 27.0.1453.88 \n * Google Chrome 27.0.1453.89 \n * Google Chrome 27.0.1453.9 \n * Google Chrome 27.0.1453.90 \n * Google Chrome 27.0.1453.91 \n * Google Chrome 27.0.1453.93 \n * Google Chrome 27.0.1453.94 \n * Google Chrome 28.0.1498.0 \n * Google Chrome 28.0.1500.0 \n * Google Chrome 28.0.1500.10 \n * Google Chrome 28.0.1500.11 \n * Google Chrome 28.0.1500.12 \n * Google Chrome 28.0.1500.13 \n * Google Chrome 28.0.1500.14 \n * Google Chrome 28.0.1500.15 \n * Google Chrome 28.0.1500.16 \n * Google Chrome 28.0.1500.17 \n * Google Chrome 28.0.1500.18 \n * Google Chrome 28.0.1500.19 \n * Google Chrome 28.0.1500.2 \n * Google Chrome 28.0.1500.20 \n * Google Chrome 28.0.1500.21 \n * Google Chrome 28.0.1500.22 \n * Google Chrome 28.0.1500.23 \n * Google Chrome 28.0.1500.24 \n * Google Chrome 28.0.1500.25 \n * Google Chrome 28.0.1500.26 \n * Google Chrome 28.0.1500.27 \n * Google Chrome 28.0.1500.28 \n * Google Chrome 28.0.1500.29 \n * Google Chrome 28.0.1500.3 \n * Google Chrome 28.0.1500.31 \n * Google Chrome 28.0.1500.32 \n * Google Chrome 28.0.1500.33 \n * Google Chrome 28.0.1500.34 \n * Google Chrome 28.0.1500.35 \n * Google Chrome 28.0.1500.36 \n * Google Chrome 28.0.1500.37 \n * Google Chrome 28.0.1500.38 \n * Google Chrome 28.0.1500.39 \n * Google Chrome 28.0.1500.4 \n * Google Chrome 28.0.1500.40 \n * Google Chrome 28.0.1500.41 \n * Google Chrome 28.0.1500.42 \n * Google Chrome 28.0.1500.43 \n * Google Chrome 28.0.1500.44 \n * Google Chrome 28.0.1500.45 \n * Google Chrome 28.0.1500.46 \n * Google Chrome 28.0.1500.47 \n * Google Chrome 28.0.1500.48 \n * Google Chrome 28.0.1500.49 \n * Google Chrome 28.0.1500.5 \n * Google Chrome 28.0.1500.50 \n * Google Chrome 28.0.1500.51 \n * Google Chrome 28.0.1500.52 \n * Google Chrome 28.0.1500.53 \n * Google Chrome 28.0.1500.54 \n * Google Chrome 28.0.1500.56 \n * Google Chrome 28.0.1500.58 \n * Google Chrome 28.0.1500.59 \n * Google Chrome 28.0.1500.6 \n * Google Chrome 28.0.1500.60 \n * Google Chrome 28.0.1500.61 \n * Google Chrome 28.0.1500.62 \n * Google Chrome 28.0.1500.63 \n * Google Chrome 28.0.1500.64 \n * Google Chrome 28.0.1500.66 \n * Google Chrome 28.0.1500.68 \n * Google Chrome 28.0.1500.70 \n * Google Chrome 28.0.1500.71 \n * Google Chrome 28.0.1500.72 \n * Google Chrome 28.0.1500.8 \n * Google Chrome 28.0.1500.89 \n * Google Chrome 28.0.1500.9 \n * Google Chrome 28.0.1500.91 \n * Google Chrome 28.0.1500.93 \n * Google Chrome 28.0.1500.94 \n * Google Chrome 28.0.1500.95 \n * Google Chrome 29.0.1547.0 \n * Google Chrome 29.0.1547.10 \n * Google Chrome 29.0.1547.12 \n * Google Chrome 29.0.1547.14 \n * Google Chrome 29.0.1547.16 \n * Google Chrome 29.0.1547.18 \n * Google Chrome 29.0.1547.2 \n * Google Chrome 29.0.1547.21 \n * Google Chrome 29.0.1547.23 \n * Google Chrome 29.0.1547.28 \n * Google Chrome 29.0.1547.3 \n * Google Chrome 29.0.1547.31 \n * Google Chrome 29.0.1547.33 \n * Google Chrome 29.0.1547.35 \n * Google Chrome 29.0.1547.37 \n * Google Chrome 29.0.1547.39 \n * Google Chrome 29.0.1547.40 \n * Google Chrome 29.0.1547.42 \n * Google Chrome 29.0.1547.46 \n * Google Chrome 29.0.1547.48 \n * Google Chrome 29.0.1547.5 \n * Google Chrome 29.0.1547.51 \n * Google Chrome 29.0.1547.53 \n * Google Chrome 29.0.1547.55 \n * Google Chrome 29.0.1547.57 \n * Google Chrome 29.0.1547.7 \n * Google Chrome 29.0.1547.76 \n * Google Chrome 29.0.1547.9 \n * Google Chrome 3 \n * Google Chrome 3.0 Beta \n * Google Chrome 3.0.182.2 \n * Google Chrome 3.0.190.2 \n * Google Chrome 3.0.193.2 Beta \n * Google Chrome 3.0.195.2 \n * Google Chrome 3.0.195.21 \n * Google Chrome 3.0.195.24 \n * Google Chrome 3.0.195.25 \n * Google Chrome 3.0.195.27 \n * Google Chrome 3.0.195.32 \n * Google Chrome 3.0.195.33 \n * Google Chrome 3.0.195.36 \n * Google Chrome 3.0.195.37 \n * Google Chrome 3.0.195.38 \n * Google Chrome 30.0.1599.0 \n * Google Chrome 30.0.1599.10 \n * Google Chrome 30.0.1599.100 \n * Google Chrome 30.0.1599.101 \n * Google Chrome 30.0.1599.12 \n * Google Chrome 30.0.1599.14 \n * Google Chrome 30.0.1599.16 \n * Google Chrome 30.0.1599.18 \n * Google Chrome 30.0.1599.2 \n * Google Chrome 30.0.1599.21 \n * Google Chrome 30.0.1599.23 \n * Google Chrome 30.0.1599.25 \n * Google Chrome 30.0.1599.27 \n * Google Chrome 30.0.1599.29 \n * Google Chrome 30.0.1599.31 \n * Google Chrome 30.0.1599.33 \n * Google Chrome 30.0.1599.35 \n * Google Chrome 30.0.1599.37 \n * Google Chrome 30.0.1599.39 \n * Google Chrome 30.0.1599.40 \n * Google Chrome 30.0.1599.42 \n * Google Chrome 30.0.1599.44 \n * Google Chrome 30.0.1599.48 \n * Google Chrome 30.0.1599.5 \n * Google Chrome 30.0.1599.51 \n * Google Chrome 30.0.1599.53 \n * Google Chrome 30.0.1599.57 \n * Google Chrome 30.0.1599.59 \n * Google Chrome 30.0.1599.60 \n * Google Chrome 30.0.1599.64 \n * Google Chrome 30.0.1599.66 \n * Google Chrome 30.0.1599.67 \n * Google Chrome 30.0.1599.68 \n * Google Chrome 30.0.1599.69 \n * Google Chrome 30.0.1599.7 \n * Google Chrome 30.0.1599.79 \n * Google Chrome 30.0.1599.80 \n * Google Chrome 30.0.1599.81 \n * Google Chrome 30.0.1599.82 \n * Google Chrome 30.0.1599.84 \n * Google Chrome 30.0.1599.85 \n * Google Chrome 30.0.1599.86 \n * Google Chrome 30.0.1599.87 \n * Google Chrome 30.0.1599.88 \n * Google Chrome 30.0.1599.9 \n * Google Chrome 30.0.1599.90 \n * Google Chrome 31.0.1650.0 \n * Google Chrome 31.0.1650.10 \n * Google Chrome 31.0.1650.11 \n * Google Chrome 31.0.1650.12 \n * Google Chrome 31.0.1650.13 \n * Google Chrome 31.0.1650.14 \n * Google Chrome 31.0.1650.15 \n * Google Chrome 31.0.1650.16 \n * Google Chrome 31.0.1650.17 \n * Google Chrome 31.0.1650.18 \n * Google Chrome 31.0.1650.19 \n * Google Chrome 31.0.1650.2 \n * Google Chrome 31.0.1650.20 \n * Google Chrome 31.0.1650.22 \n * Google Chrome 31.0.1650.23 \n * Google Chrome 31.0.1650.25 \n * Google Chrome 31.0.1650.26 \n * Google Chrome 31.0.1650.27 \n * Google Chrome 31.0.1650.28 \n * Google Chrome 31.0.1650.29 \n * Google Chrome 31.0.1650.3 \n * Google Chrome 31.0.1650.30 \n * Google Chrome 31.0.1650.31 \n * Google Chrome 31.0.1650.32 \n * Google Chrome 31.0.1650.33 \n * Google Chrome 31.0.1650.34 \n * Google Chrome 31.0.1650.35 \n * Google Chrome 31.0.1650.36 \n * Google Chrome 31.0.1650.37 \n * Google Chrome 31.0.1650.38 \n * Google Chrome 31.0.1650.39 \n * Google Chrome 31.0.1650.4 \n * Google Chrome 31.0.1650.41 \n * Google Chrome 31.0.1650.42 \n * Google Chrome 31.0.1650.43 \n * Google Chrome 31.0.1650.44 \n * Google Chrome 31.0.1650.45 \n * Google Chrome 31.0.1650.46 \n * Google Chrome 31.0.1650.47 \n * Google Chrome 31.0.1650.48 \n * Google Chrome 31.0.1650.49 \n * Google Chrome 31.0.1650.5 \n * Google Chrome 31.0.1650.50 \n * Google Chrome 31.0.1650.52 \n * Google Chrome 31.0.1650.54 \n * Google Chrome 31.0.1650.57 \n * Google Chrome 31.0.1650.58 \n * Google Chrome 31.0.1650.6 \n * Google Chrome 31.0.1650.60 \n * Google Chrome 31.0.1650.61 \n * Google Chrome 31.0.1650.62 \n * Google Chrome 31.0.1650.63 \n * Google Chrome 31.0.1650.7 \n * Google Chrome 31.0.1650.8 \n * Google Chrome 31.0.1650.9 \n * Google Chrome 32.0.1651.2 \n * Google Chrome 32.0.1652.1 \n * Google Chrome 32.0.1653.1 \n * Google Chrome 32.0.1654.0 \n * Google Chrome 32.0.1654.3 \n * Google Chrome 32.0.1655.1 \n * Google Chrome 32.0.1656.1 \n * Google Chrome 32.0.1657.0 \n * Google Chrome 32.0.1658.0 \n * Google Chrome 32.0.1658.2 \n * Google Chrome 32.0.1659.1 \n * Google Chrome 32.0.1659.3 \n * Google Chrome 32.0.1660.1 \n * Google Chrome 32.0.1661.0 \n * Google Chrome 32.0.1662.0 \n * Google Chrome 32.0.1662.2 \n * Google Chrome 32.0.1663.1 \n * Google Chrome 32.0.1663.3 \n * Google Chrome 32.0.1664.1 \n * Google Chrome 32.0.1664.3 \n * Google Chrome 32.0.1666.0 \n * Google Chrome 32.0.1667.0 \n * Google Chrome 32.0.1668.0 \n * Google Chrome 32.0.1668.2 \n * Google Chrome 32.0.1668.4 \n * Google Chrome 32.0.1668.6 \n * Google Chrome 32.0.1669.1 \n * Google Chrome 32.0.1669.3 \n * Google Chrome 32.0.1670.1 \n * Google Chrome 32.0.1670.3 \n * Google Chrome 32.0.1670.5 \n * Google Chrome 32.0.1671.2 \n * Google Chrome 32.0.1671.4 \n * Google Chrome 32.0.1671.8 \n * Google Chrome 32.0.1672.2 \n * Google Chrome 32.0.1673.2 \n * Google Chrome 32.0.1673.4 \n * Google Chrome 32.0.1674.1 \n * Google Chrome 32.0.1675.0 \n * Google Chrome 32.0.1675.2 \n * Google Chrome 32.0.1676.0 \n * Google Chrome 32.0.1676.2 \n * Google Chrome 32.0.1677.1 \n * Google Chrome 32.0.1678.1 \n * Google Chrome 32.0.1679.0 \n * Google Chrome 32.0.1680.0 \n * Google Chrome 32.0.1681.0 \n * Google Chrome 32.0.1681.3 \n * Google Chrome 32.0.1682.3 \n * Google Chrome 32.0.1682.5 \n * Google Chrome 32.0.1683.1 \n * Google Chrome 32.0.1684.0 \n * Google Chrome 32.0.1684.2 \n * Google Chrome 32.0.1685.0 \n * Google Chrome 32.0.1685.2 \n * Google Chrome 32.0.1686.0 \n * Google Chrome 32.0.1687.0 \n * Google Chrome 32.0.1688.0 \n * Google Chrome 32.0.1689.0 \n * Google Chrome 32.0.1689.2 \n * Google Chrome 32.0.1690.0 \n * Google Chrome 32.0.1700.0 \n * Google Chrome 32.0.1700.100 \n * Google Chrome 32.0.1700.102 \n * Google Chrome 32.0.1700.103 \n * Google Chrome 32.0.1700.107 \n * Google Chrome 32.0.1700.11 \n * Google Chrome 32.0.1700.13 \n * Google Chrome 32.0.1700.15 \n * Google Chrome 32.0.1700.17 \n * Google Chrome 32.0.1700.19 \n * Google Chrome 32.0.1700.21 \n * Google Chrome 32.0.1700.23 \n * Google Chrome 32.0.1700.26 \n * Google Chrome 32.0.1700.28 \n * Google Chrome 32.0.1700.3 \n * Google Chrome 32.0.1700.31 \n * Google Chrome 32.0.1700.33 \n * Google Chrome 32.0.1700.35 \n * Google Chrome 32.0.1700.39 \n * Google Chrome 32.0.1700.41 \n * Google Chrome 32.0.1700.50 \n * Google Chrome 32.0.1700.52 \n * Google Chrome 32.0.1700.54 \n * Google Chrome 32.0.1700.56 \n * Google Chrome 32.0.1700.58 \n * Google Chrome 32.0.1700.6 \n * Google Chrome 32.0.1700.63 \n * Google Chrome 32.0.1700.65 \n * Google Chrome 32.0.1700.67 \n * Google Chrome 32.0.1700.69 \n * Google Chrome 32.0.1700.70 \n * Google Chrome 32.0.1700.74 \n * Google Chrome 32.0.1700.76 \n * Google Chrome 32.0.1700.77 \n * Google Chrome 32.0.1700.9 \n * Google Chrome 32.0.1700.95 \n * Google Chrome 32.0.1700.97 \n * Google Chrome 32.0.1700.98 \n * Google Chrome 33.0.1750.0 \n * Google Chrome 33.0.1750.10 \n * Google Chrome 33.0.1750.106 \n * Google Chrome 33.0.1750.108 \n * Google Chrome 33.0.1750.11 \n * Google Chrome 33.0.1750.111 \n * Google Chrome 33.0.1750.113 \n * Google Chrome 33.0.1750.116 \n * Google Chrome 33.0.1750.117 \n * Google Chrome 33.0.1750.124 \n * Google Chrome 33.0.1750.125 \n * Google Chrome 33.0.1750.13 \n * Google Chrome 33.0.1750.132 \n * Google Chrome 33.0.1750.135 \n * Google Chrome 33.0.1750.14 \n * Google Chrome 33.0.1750.144 \n * Google Chrome 33.0.1750.146 \n * Google Chrome 33.0.1750.149 \n * Google Chrome 33.0.1750.151 \n * Google Chrome 33.0.1750.152 \n * Google Chrome 33.0.1750.154 \n * Google Chrome 33.0.1750.16 \n * Google Chrome 33.0.1750.166 \n * Google Chrome 33.0.1750.168 \n * Google Chrome 33.0.1750.19 \n * Google Chrome 33.0.1750.20 \n * Google Chrome 33.0.1750.22 \n * Google Chrome 33.0.1750.24 \n * Google Chrome 33.0.1750.26 \n * Google Chrome 33.0.1750.28 \n * Google Chrome 33.0.1750.3 \n * Google Chrome 33.0.1750.31 \n * Google Chrome 33.0.1750.35 \n * Google Chrome 33.0.1750.37 \n * Google Chrome 33.0.1750.39 \n * Google Chrome 33.0.1750.40 \n * Google Chrome 33.0.1750.42 \n * Google Chrome 33.0.1750.44 \n * Google Chrome 33.0.1750.46 \n * Google Chrome 33.0.1750.48 \n * Google Chrome 33.0.1750.5 \n * Google Chrome 33.0.1750.51 \n * Google Chrome 33.0.1750.53 \n * Google Chrome 33.0.1750.55 \n * Google Chrome 33.0.1750.57 \n * Google Chrome 33.0.1750.59 \n * Google Chrome 33.0.1750.60 \n * Google Chrome 33.0.1750.62 \n * Google Chrome 33.0.1750.64 \n * Google Chrome 33.0.1750.66 \n * Google Chrome 33.0.1750.68 \n * Google Chrome 33.0.1750.7 \n * Google Chrome 33.0.1750.71 \n * Google Chrome 33.0.1750.74 \n * Google Chrome 33.0.1750.76 \n * Google Chrome 33.0.1750.79 \n * Google Chrome 33.0.1750.80 \n * Google Chrome 33.0.1750.82 \n * Google Chrome 33.0.1750.85 \n * Google Chrome 33.0.1750.89 \n * Google Chrome 33.0.1750.90 \n * Google Chrome 33.0.1750.92 \n * Google Chrome 34.0.1847.0 \n * Google Chrome 34.0.1847.10 \n * Google Chrome 34.0.1847.101 \n * Google Chrome 34.0.1847.103 \n * Google Chrome 34.0.1847.109 \n * Google Chrome 34.0.1847.112 \n * Google Chrome 34.0.1847.114 \n * Google Chrome 34.0.1847.116 \n * Google Chrome 34.0.1847.118 \n * Google Chrome 34.0.1847.120 \n * Google Chrome 34.0.1847.130 \n * Google Chrome 34.0.1847.131 \n * Google Chrome 34.0.1847.132 \n * Google Chrome 34.0.1847.134 \n * Google Chrome 34.0.1847.136 \n * Google Chrome 34.0.1847.137 \n * Google Chrome 34.0.1847.15 \n * Google Chrome 34.0.1847.23 \n * Google Chrome 34.0.1847.25 \n * Google Chrome 34.0.1847.36 \n * Google Chrome 34.0.1847.38 \n * Google Chrome 34.0.1847.4 \n * Google Chrome 34.0.1847.42 \n * Google Chrome 34.0.1847.44 \n * Google Chrome 34.0.1847.46 \n * Google Chrome 34.0.1847.48 \n * Google Chrome 34.0.1847.5 \n * Google Chrome 34.0.1847.51 \n * Google Chrome 34.0.1847.53 \n * Google Chrome 34.0.1847.55 \n * Google Chrome 34.0.1847.57 \n * Google Chrome 34.0.1847.59 \n * Google Chrome 34.0.1847.60 \n * Google Chrome 34.0.1847.62 \n * Google Chrome 34.0.1847.64 \n * Google Chrome 34.0.1847.66 \n * Google Chrome 34.0.1847.68 \n * Google Chrome 34.0.1847.7 \n * Google Chrome 34.0.1847.72 \n * Google Chrome 34.0.1847.74 \n * Google Chrome 34.0.1847.76 \n * Google Chrome 34.0.1847.78 \n * Google Chrome 34.0.1847.8 \n * Google Chrome 34.0.1847.81 \n * Google Chrome 34.0.1847.83 \n * Google Chrome 34.0.1847.86 \n * Google Chrome 34.0.1847.9 \n * Google Chrome 34.0.1847.92 \n * Google Chrome 34.0.1847.97 \n * Google Chrome 34.0.1847.99 \n * Google Chrome 35.0.1916.0 \n * Google Chrome 35.0.1916.10 \n * Google Chrome 35.0.1916.103 \n * Google Chrome 35.0.1916.105 \n * Google Chrome 35.0.1916.107 \n * Google Chrome 35.0.1916.109 \n * Google Chrome 35.0.1916.110 \n * Google Chrome 35.0.1916.112 \n * Google Chrome 35.0.1916.114 \n * Google Chrome 35.0.1916.13 \n * Google Chrome 35.0.1916.15 \n * Google Chrome 35.0.1916.153 \n * Google Chrome 35.0.1916.18 \n * Google Chrome 35.0.1916.2 \n * Google Chrome 35.0.1916.21 \n * Google Chrome 35.0.1916.23 \n * Google Chrome 35.0.1916.3 \n * Google Chrome 35.0.1916.32 \n * Google Chrome 35.0.1916.34 \n * Google Chrome 35.0.1916.36 \n * Google Chrome 35.0.1916.38 \n * Google Chrome 35.0.1916.4 \n * Google Chrome 35.0.1916.41 \n * Google Chrome 35.0.1916.43 \n * Google Chrome 35.0.1916.45 \n * Google Chrome 35.0.1916.47 \n * Google Chrome 35.0.1916.49 \n * Google Chrome 35.0.1916.51 \n * Google Chrome 35.0.1916.54 \n * Google Chrome 35.0.1916.57 \n * Google Chrome 35.0.1916.6 \n * Google Chrome 35.0.1916.68 \n * Google Chrome 35.0.1916.7 \n * Google Chrome 35.0.1916.72 \n * Google Chrome 35.0.1916.77 \n * Google Chrome 35.0.1916.80 \n * Google Chrome 35.0.1916.84 \n * Google Chrome 35.0.1916.86 \n * Google Chrome 35.0.1916.9 \n * Google Chrome 35.0.1916.92 \n * Google Chrome 35.0.1916.95 \n * Google Chrome 35.0.1916.98 \n * Google Chrome 36.0.1985.122 \n * Google Chrome 36.0.1985.143 \n * Google Chrome 37.0.2062.0 \n * Google Chrome 37.0.2062.10 \n * Google Chrome 37.0.2062.12 \n * Google Chrome 37.0.2062.120 \n * Google Chrome 37.0.2062.124 \n * Google Chrome 37.0.2062.14 \n * Google Chrome 37.0.2062.16 \n * Google Chrome 37.0.2062.18 \n * Google Chrome 37.0.2062.2 \n * Google Chrome 37.0.2062.21 \n * Google Chrome 37.0.2062.23 \n * Google Chrome 37.0.2062.25 \n * Google Chrome 37.0.2062.27 \n * Google Chrome 37.0.2062.29 \n * Google Chrome 37.0.2062.30 \n * Google Chrome 37.0.2062.32 \n * Google Chrome 37.0.2062.34 \n * Google Chrome 37.0.2062.36 \n * Google Chrome 37.0.2062.39 \n * Google Chrome 37.0.2062.43 \n * Google Chrome 37.0.2062.45 \n * Google Chrome 37.0.2062.47 \n * Google Chrome 37.0.2062.49 \n * Google Chrome 37.0.2062.50 \n * Google Chrome 37.0.2062.52 \n * Google Chrome 37.0.2062.54 \n * Google Chrome 37.0.2062.56 \n * Google Chrome 37.0.2062.58 \n * Google Chrome 37.0.2062.6 \n * Google Chrome 37.0.2062.61 \n * Google Chrome 37.0.2062.63 \n * Google Chrome 37.0.2062.65 \n * Google Chrome 37.0.2062.67 \n * Google Chrome 37.0.2062.69 \n * Google Chrome 37.0.2062.70 \n * Google Chrome 37.0.2062.72 \n * Google Chrome 37.0.2062.74 \n * Google Chrome 37.0.2062.76 \n * Google Chrome 37.0.2062.78 \n * Google Chrome 37.0.2062.80 \n * Google Chrome 37.0.2062.89 \n * Google Chrome 37.0.2062.90 \n * Google Chrome 37.0.2062.92 \n * Google Chrome 37.0.2062.94 \n * Google Chrome 37.0.2062.95 \n * Google Chrome 37.0.2062.97 \n * Google Chrome 38.0.2125.101 \n * Google Chrome 38.0.2125.101 ~~~Android~~ \n * Google Chrome 38.0.2125.122 \n * Google Chrome 39.0.2171.63 \n * Google Chrome 39.0.2171.65 \n * Google Chrome 4 \n * Google Chrome 4.0.211.0 \n * Google Chrome 4.0.212.0 \n * Google Chrome 4.0.212.1 \n * Google Chrome 4.0.221.8 \n * Google Chrome 4.0.222.0 \n * Google Chrome 4.0.222.1 \n * Google Chrome 4.0.222.12 \n * Google Chrome 4.0.222.5 \n * Google Chrome 4.0.223.0 \n * Google Chrome 4.0.223.1 \n * Google Chrome 4.0.223.2 \n * Google Chrome 4.0.223.4 \n * Google Chrome 4.0.223.5 \n * Google Chrome 4.0.223.7 \n * Google Chrome 4.0.223.8 \n * Google Chrome 4.0.224.0 \n * Google Chrome 4.0.229.1 \n * Google Chrome 4.0.235.0 \n * Google Chrome 4.0.236.0 \n * Google Chrome 4.0.237.0 \n * Google Chrome 4.0.237.1 \n * Google Chrome 4.0.239.0 \n * Google Chrome 4.0.240.0 \n * Google Chrome 4.0.241.0 \n * Google Chrome 4.0.242.0 \n * Google Chrome 4.0.243.0 \n * Google Chrome 4.0.244.0 \n * Google Chrome 4.0.245.0 \n * Google Chrome 4.0.246.0 \n * Google Chrome 4.0.247.0 \n * Google Chrome 4.0.248.0 \n * Google Chrome 4.0.249.0 \n * Google Chrome 4.0.249.1 \n * Google Chrome 4.0.249.10 \n * Google Chrome 4.0.249.11 \n * Google Chrome 4.0.249.12 \n * Google Chrome 4.0.249.14 \n * Google Chrome 4.0.249.16 \n * Google Chrome 4.0.249.17 \n * Google Chrome 4.0.249.18 \n * Google Chrome 4.0.249.19 \n * Google Chrome 4.0.249.2 \n * Google Chrome 4.0.249.20 \n * Google Chrome 4.0.249.21 \n * Google Chrome 4.0.249.22 \n * Google Chrome 4.0.249.23 \n * Google Chrome 4.0.249.24 \n * Google Chrome 4.0.249.25 \n * Google Chrome 4.0.249.26 \n * Google Chrome 4.0.249.27 \n * Google Chrome 4.0.249.28 \n * Google Chrome 4.0.249.29 \n * Google Chrome 4.0.249.3 \n * Google Chrome 4.0.249.30 \n * Google Chrome 4.0.249.31 \n * Google Chrome 4.0.249.32 \n * Google Chrome 4.0.249.33 \n * Google Chrome 4.0.249.34 \n * Google Chrome 4.0.249.35 \n * Google Chrome 4.0.249.36 \n * Google Chrome 4.0.249.37 \n * Google Chrome 4.0.249.38 \n * Google Chrome 4.0.249.39 \n * Google Chrome 4.0.249.4 \n * Google Chrome 4.0.249.40 \n * Google Chrome 4.0.249.41 \n * Google Chrome 4.0.249.42 \n * Google Chrome 4.0.249.43 \n * Google Chrome 4.0.249.44 \n * Google Chrome 4.0.249.45 \n * Google Chrome 4.0.249.46 \n * Google Chrome 4.0.249.47 \n * Google Chrome 4.0.249.48 \n * Google Chrome 4.0.249.49 \n * Google Chrome 4.0.249.5 \n * Google Chrome 4.0.249.50 \n * Google Chrome 4.0.249.51 \n * Google Chrome 4.0.249.52 \n * Google Chrome 4.0.249.53 \n * Google Chrome 4.0.249.54 \n * Google Chrome 4.0.249.55 \n * Google Chrome 4.0.249.56 \n * Google Chrome 4.0.249.57 \n * Google Chrome 4.0.249.58 \n * Google Chrome 4.0.249.59 \n * Google Chrome 4.0.249.6 \n * Google Chrome 4.0.249.60 \n * Google Chrome 4.0.249.61 \n * Google Chrome 4.0.249.62 \n * Google Chrome 4.0.249.63 \n * Google Chrome 4.0.249.64 \n * Google Chrome 4.0.249.65 \n * Google Chrome 4.0.249.66 \n * Google Chrome 4.0.249.67 \n * Google Chrome 4.0.249.68 \n * Google Chrome 4.0.249.69 \n * Google Chrome 4.0.249.7 \n * Google Chrome 4.0.249.70 \n * Google Chrome 4.0.249.71 \n * Google Chrome 4.0.249.72 \n * Google Chrome 4.0.249.73 \n * Google Chrome 4.0.249.74 \n * Google Chrome 4.0.249.75 \n * Google Chrome 4.0.249.76 \n * Google Chrome 4.0.249.77 \n * Google Chrome 4.0.249.78 \n * Google Chrome 4.0.249.78 Beta \n * Google Chrome 4.0.249.79 \n * Google Chrome 4.0.249.8 \n * Google Chrome 4.0.249.80 \n * Google Chrome 4.0.249.81 \n * Google Chrome 4.0.249.82 \n * Google Chrome 4.0.249.89 \n * Google Chrome 4.0.249.9 \n * Google Chrome 4.0.250.0 \n * Google Chrome 4.0.250.2 \n * Google Chrome 4.0.251.0 \n * Google Chrome 4.0.252.0 \n * Google Chrome 4.0.254.0 \n * Google Chrome 4.0.255.0 \n * Google Chrome 4.0.256.0 \n * Google Chrome 4.0.257.0 \n * Google Chrome 4.0.258.0 \n * Google Chrome 4.0.259.0 \n * Google Chrome 4.0.260.0 \n * Google Chrome 4.0.261.0 \n * Google Chrome 4.0.262.0 \n * Google Chrome 4.0.263.0 \n * Google Chrome 4.0.264.0 \n * Google Chrome 4.0.265.0 \n * Google Chrome 4.0.266.0 \n * Google Chrome 4.0.267.0 \n * Google Chrome 4.0.268.0 \n * Google Chrome 4.0.269.0 \n * Google Chrome 4.0.271.0 \n * Google Chrome 4.0.272.0 \n * Google Chrome 4.0.275.0 \n * Google Chrome 4.0.275.1 \n * Google Chrome 4.0.276.0 \n * Google Chrome 4.0.277.0 \n * Google Chrome 4.0.278.0 \n * Google Chrome 4.0.286.0 \n * Google Chrome 4.0.287.0 \n * Google Chrome 4.0.288.0 \n * Google Chrome 4.0.288.1 \n * Google Chrome 4.0.289.0 \n * Google Chrome 4.0.290.0 \n * Google Chrome 4.0.292.0 \n * Google Chrome 4.0.294.0 \n * Google Chrome 4.0.295.0 \n * Google Chrome 4.0.296.0 \n * Google Chrome 4.0.299.0 \n * Google Chrome 4.0.300.0 \n * Google Chrome 4.0.301.0 \n * Google Chrome 4.0.302.0 \n * Google Chrome 4.0.302.1 \n * Google Chrome 4.0.302.2 \n * Google Chrome 4.0.302.3 \n * Google Chrome 4.0.303.0 \n * Google Chrome 4.0.304.0 \n * Google Chrome 4.0.305.0 \n * Google Chrome 4.1 Beta \n * Google Chrome 4.1.249.0 \n * Google Chrome 4.1.249.1001 \n * Google Chrome 4.1.249.1004 \n * Google Chrome 4.1.249.1006 \n * Google Chrome 4.1.249.1007 \n * Google Chrome 4.1.249.1008 \n * Google Chrome 4.1.249.1009 \n * Google Chrome 4.1.249.1010 \n * Google Chrome 4.1.249.1011 \n * Google Chrome 4.1.249.1012 \n * Google Chrome 4.1.249.1013 \n * Google Chrome 4.1.249.1014 \n * Google Chrome 4.1.249.1015 \n * Google Chrome 4.1.249.1016 \n * Google Chrome 4.1.249.1017 \n * Google Chrome 4.1.249.1018 \n * Google Chrome 4.1.249.1019 \n * Google Chrome 4.1.249.1020 \n * Google Chrome 4.1.249.1021 \n * Google Chrome 4.1.249.1022 \n * Google Chrome 4.1.249.1023 \n * Google Chrome 4.1.249.1024 \n * Google Chrome 4.1.249.1025 \n * Google Chrome 4.1.249.1026 \n * Google Chrome 4.1.249.1027 \n * Google Chrome 4.1.249.1028 \n * Google Chrome 4.1.249.1029 \n * Google Chrome 4.1.249.1030 \n * Google Chrome 4.1.249.1031 \n * Google Chrome 4.1.249.1032 \n * Google Chrome 4.1.249.1033 \n * Google Chrome 4.1.249.1034 \n * Google Chrome 4.1.249.1035 \n * Google Chrome 4.1.249.1036 \n * Google Chrome 4.1.249.1037 \n * Google Chrome 4.1.249.1038 \n * Google Chrome 4.1.249.1039 \n * Google Chrome 4.1.249.1040 \n * Google Chrome 4.1.249.1041 \n * Google Chrome 4.1.249.1042 \n * Google Chrome 4.1.249.1043 \n * Google Chrome 4.1.249.1044 \n * Google Chrome 4.1.249.1045 \n * Google Chrome 4.1.249.1046 \n * Google Chrome 4.1.249.1047 \n * Google Chrome 4.1.249.1048 \n * Google Chrome 4.1.249.1049 \n * Google Chrome 4.1.249.1050 \n * Google Chrome 4.1.249.1051 \n * Google Chrome 4.1.249.1052 \n * Google Chrome 4.1.249.1053 \n * Google Chrome 4.1.249.1054 \n * Google Chrome 4.1.249.1055 \n * Google Chrome 4.1.249.1056 \n * Google Chrome 4.1.249.1057 \n * Google Chrome 4.1.249.1058 \n * Google Chrome 4.1.249.1059 \n * Google Chrome 4.1.249.1060 \n * Google Chrome 4.1.249.1061 \n * Google Chrome 4.1.249.1062 \n * Google Chrome 4.1.249.1063 \n * Google Chrome 4.1.249.1064 \n * Google Chrome 40.0.2214.111 \n * Google Chrome 40.0.2214.115 \n * Google Chrome 40.0.2214.85 \n * Google Chrome 40.0.2214.91 \n * Google Chrome 41.0.2272 \n * Google Chrome 41.0.2272.118 \n * Google Chrome 41.0.2272.76 \n * Google Chrome 42.0.2311 \n * Google Chrome 42.0.2311.135 \n * Google Chrome 42.0.2311.90 \n * Google Chrome 43.0.2357 \n * Google Chrome 43.0.2357.130 \n * Google Chrome 43.0.2357.65 \n * Google Chrome 44.0.2403 \n * Google Chrome 44.0.2403.157 \n * Google Chrome 44.0.2403.89 \n * Google Chrome 45.0.2454 \n * Google Chrome 45.0.2454.101 \n * Google Chrome 45.0.2454.85 \n * Google Chrome 46.0.2490 \n * Google Chrome 46.0.2490.71 \n * Google Chrome 46.0.2490.76 \n * Google Chrome 46.0.2490.86 \n * Google Chrome 47.0 \n * Google Chrome 47.0.2526.106 \n * Google Chrome 47.0.2526.73 \n * Google Chrome 47.0.2526.80 \n * Google Chrome 48.0.2564.109 \n * Google Chrome 48.0.2564.116 \n * Google Chrome 48.0.2564.82 \n * Google Chrome 49.0.2566.0 \n * Google Chrome 49.0.2623.108 \n * Google Chrome 49.0.2623.75 \n * Google Chrome 49.0.2623.87 \n * Google Chrome 5.0.306.0 \n * Google Chrome 5.0.306.1 \n * Google Chrome 5.0.307.1 \n * Google Chrome 5.0.307.10 \n * Google Chrome 5.0.307.11 \n * Google Chrome 5.0.307.3 \n * Google Chrome 5.0.307.4 \n * Google Chrome 5.0.307.5 \n * Google Chrome 5.0.307.6 \n * Google Chrome 5.0.307.7 \n * Google Chrome 5.0.307.8 \n * Google Chrome 5.0.307.9 \n * Google Chrome 5.0.308.0 \n * Google Chrome 5.0.309.0 \n * Google Chrome 5.0.313.0 \n * Google Chrome 5.0.314.0 \n * Google Chrome 5.0.314.1 \n * Google Chrome 5.0.315.0 \n * Google Chrome 5.0.316.0 \n * Google Chrome 5.0.317.0 \n * Google Chrome 5.0.317.1 \n * Google Chrome 5.0.317.2 \n * Google Chrome 5.0.318.0 \n * Google Chrome 5.0.319.0 \n * Google Chrome 5.0.320.0 \n * Google Chrome 5.0.321.0 \n * Google Chrome 5.0.322.0 \n * Google Chrome 5.0.322.1 \n * Google Chrome 5.0.322.2 \n * Google Chrome 5.0.323.0 \n * Google Chrome 5.0.324.0 \n * Google Chrome 5.0.325.0 \n * Google Chrome 5.0.326.0 \n * Google Chrome 5.0.327.0 \n * Google Chrome 5.0.328.0 \n * Google Chrome 5.0.329.0 \n * Google Chrome 5.0.330.0 \n * Google Chrome 5.0.332.0 \n * Google Chrome 5.0.333.0 \n * Google Chrome 5.0.334.0 \n * Google Chrome 5.0.335.0 \n * Google Chrome 5.0.335.1 \n * Google Chrome 5.0.335.2 \n * Google Chrome 5.0.335.3 \n * Google Chrome 5.0.335.4 \n * Google Chrome 5.0.336.0 \n * Google Chrome 5.0.337.0 \n * Google Chrome 5.0.338.0 \n * Google Chrome 5.0.339.0 \n * Google Chrome 5.0.340.0 \n * Google Chrome 5.0.341.0 \n * Google Chrome 5.0.342.0 \n * Google Chrome 5.0.342.1 \n * Google Chrome 5.0.342.2 \n * Google Chrome 5.0.342.3 \n * Google Chrome 5.0.342.4 \n * Google Chrome 5.0.342.5 \n * Google Chrome 5.0.342.6 \n * Google Chrome 5.0.342.7 \n * Google Chrome 5.0.342.7 Beta Mac \n * Google Chrome 5.0.342.8 \n * Google Chrome 5.0.342.9 \n * Google Chrome 5.0.343.0 \n * Google Chrome 5.0.344.0 \n * Google Chrome 5.0.345.0 \n * Google Chrome 5.0.346.0 \n * Google Chrome 5.0.347.0 \n * Google Chrome 5.0.348.0 \n * Google Chrome 5.0.349.0 \n * Google Chrome 5.0.350.0 \n * Google Chrome 5.0.350.1 \n * Google Chrome 5.0.351.0 \n * Google Chrome 5.0.353.0 \n * Google Chrome 5.0.354.0 \n * Google Chrome 5.0.354.1 \n * Google Chrome 5.0.355.0 \n * Google Chrome 5.0.356.0 \n * Google Chrome 5.0.356.1 \n * Google Chrome 5.0.356.2 \n * Google Chrome 5.0.357.0 \n * Google Chrome 5.0.358.0 \n * Google Chrome 5.0.359.0 \n * Google Chrome 5.0.360.0 \n * Google Chrome 5.0.360.3 \n * Google Chrome 5.0.360.4 \n * Google Chrome 5.0.360.5 \n * Google Chrome 5.0.361.0 \n * Google Chrome 5.0.362.0 \n * Google Chrome 5.0.363.0 \n * Google Chrome 5.0.364.0 \n * Google Chrome 5.0.365.0 \n * Google Chrome 5.0.366.0 \n * Google Chrome 5.0.366.1 \n * Google Chrome 5.0.366.2 \n * Google Chrome 5.0.366.3 \n * Google Chrome 5.0.366.4 \n * Google Chrome 5.0.367.0 \n * Google Chrome 5.0.368.0 \n * Google Chrome 5.0.369.0 \n * Google Chrome 5.0.369.1 \n * Google Chrome 5.0.369.2 \n * Google Chrome 5.0.370.0 \n * Google Chrome 5.0.371.0 \n * Google Chrome 5.0.372.0 \n * Google Chrome 5.0.373.0 \n * Google Chrome 5.0.374.0 \n * Google Chrome 5.0.375.0 \n * Google Chrome 5.0.375.1 \n * Google Chrome 5.0.375.10 \n * Google Chrome 5.0.375.11 \n * Google Chrome 5.0.375.12 \n * Google Chrome 5.0.375.125 \n * Google Chrome 5.0.375.126 \n * Google Chrome 5.0.375.127 \n * Google Chrome 5.0.375.13 \n * Google Chrome 5.0.375.14 \n * Google Chrome 5.0.375.15 \n * Google Chrome 5.0.375.16 \n * Google Chrome 5.0.375.17 \n * Google Chrome 5.0.375.18 \n * Google Chrome 5.0.375.19 \n * Google Chrome 5.0.375.2 \n * Google Chrome 5.0.375.20 \n * Google Chrome 5.0.375.21 \n * Google Chrome 5.0.375.22 \n * Google Chrome 5.0.375.23 \n * Google Chrome 5.0.375.25 \n * Google Chrome 5.0.375.26 \n * Google Chrome 5.0.375.27 \n * Google Chrome 5.0.375.28 \n * Google Chrome 5.0.375.29 \n * Google Chrome 5.0.375.3 \n * Google Chrome 5.0.375.30 \n * Google Chrome 5.0.375.31 \n * Google Chrome 5.0.375.32 \n * Google Chrome 5.0.375.33 \n * Google Chrome 5.0.375.34 \n * Google Chrome 5.0.375.35 \n * Google Chrome 5.0.375.36 \n * Google Chrome 5.0.375.37 \n * Google Chrome 5.0.375.38 \n * Google Chrome 5.0.375.39 \n * Google Chrome 5.0.375.4 \n * Google Chrome 5.0.375.40 \n * Google Chrome 5.0.375.41 \n * Google Chrome 5.0.375.42 \n * Google Chrome 5.0.375.43 \n * Google Chrome 5.0.375.44 \n * Google Chrome 5.0.375.45 \n * Google Chrome 5.0.375.46 \n * Google Chrome 5.0.375.47 \n * Google Chrome 5.0.375.48 \n * Google Chrome 5.0.375.49 \n * Google Chrome 5.0.375.5 \n * Google Chrome 5.0.375.50 \n * Google Chrome 5.0.375.51 \n * Google Chrome 5.0.375.52 \n * Google Chrome 5.0.375.53 \n * Google Chrome 5.0.375.54 \n * Google Chrome 5.0.375.55 \n * Google Chrome 5.0.375.56 \n * Google Chrome 5.0.375.57 \n * Google Chrome 5.0.375.58 \n * Google Chrome 5.0.375.59 \n * Google Chrome 5.0.375.6 \n * Google Chrome 5.0.375.60 \n * Google Chrome 5.0.375.61 \n * Google Chrome 5.0.375.62 \n * Google Chrome 5.0.375.63 \n * Google Chrome 5.0.375.64 \n * Google Chrome 5.0.375.65 \n * Google Chrome 5.0.375.66 \n * Google Chrome 5.0.375.67 \n * Google Chrome 5.0.375.68 \n * Google Chrome 5.0.375.69 \n * Google Chrome 5.0.375.7 \n * Google Chrome 5.0.375.70 \n * Google Chrome 5.0.375.71 \n * Google Chrome 5.0.375.72 \n * Google Chrome 5.0.375.73 \n * Google Chrome 5.0.375.74 \n * Google Chrome 5.0.375.75 \n * Google Chrome 5.0.375.76 \n * Google Chrome 5.0.375.77 \n * Google Chrome 5.0.375.78 \n * Google Chrome 5.0.375.79 \n * Google Chrome 5.0.375.8 \n * Google Chrome 5.0.375.80 \n * Google Chrome 5.0.375.81 \n * Google Chrome 5.0.375.82 \n * Google Chrome 5.0.375.83 \n * Google Chrome 5.0.375.84 \n * Google Chrome 5.0.375.85 \n * Google Chrome 5.0.375.86 \n * Google Chrome 5.0.375.87 \n * Google Chrome 5.0.375.88 \n * Google Chrome 5.0.375.89 \n * Google Chrome 5.0.375.9 \n * Google Chrome 5.0.375.90 \n * Google Chrome 5.0.375.91 \n * Google Chrome 5.0.375.92 \n * Google Chrome 5.0.375.93 \n * Google Chrome 5.0.375.94 \n * Google Chrome 5.0.375.95 \n * Google Chrome 5.0.375.96 \n * Google Chrome 5.0.375.97 \n * Google Chrome 5.0.375.98 \n * Google Chrome 5.0.375.99 \n * Google Chrome 5.0.376.0 \n * Google Chrome 5.0.378.0 \n * Google Chrome 5.0.379.0 \n * Google Chrome 5.0.380.0 \n * Google Chrome 5.0.381.0 \n * Google Chrome 5.0.382.0 \n * Google Chrome 5.0.382.3 \n * Google Chrome 5.0.383.0 \n * Google Chrome 5.0.384.0 \n * Google Chrome 5.0.385.0 \n * Google Chrome 5.0.386.0 \n * Google Chrome 5.0.387.0 \n * Google Chrome 5.0.390.0 \n * Google Chrome 5.0.391.0 \n * Google Chrome 5.0.392.0 \n * Google Chrome 5.0.393.0 \n * Google Chrome 5.0.394.0 \n * Google Chrome 5.0.395.0 \n * Google Chrome 5.0.396.0 \n * Google Chrome 50.0.2661.102 \n * Google Chrome 50.0.2661.75 \n * Google Chrome 50.0.2661.94 \n * Google Chrome 51.0.2704.103 \n * Google Chrome 51.0.2704.63 \n * Google Chrome 51.0.2704.79 \n * Google Chrome 52.0.2743.116 \n * Google Chrome 52.0.2743.82 \n * Google Chrome 53.0.2785.113 \n * Google Chrome 53.0.2785.143 \n * Google Chrome 53.0.2785.89 \n * Google Chrome 54.0.2840.59 \n * Google Chrome 54.0.2840.85 \n * Google Chrome 54.0.2840.87 \n * Google Chrome 54.0.2840.90 \n * Google Chrome 54.0.2840.98 \n * Google Chrome 54.0.2840.99 \n * Google Chrome 55.0.2883.75 \n * Google Chrome 56.0.2924.76 \n * Google Chrome 57.0.2987.133 \n * Google Chrome 57.0.2987.98 \n * Google Chrome 58.0.3029.81 \n * Google Chrome 58.0.3029.96 \n * Google Chrome 59.0.3071.104 \n * Google Chrome 59.0.3071.115 \n * Google Chrome 59.0.3071.86 \n * Google Chrome 6.0.397.0 \n * Google Chrome 6.0.398.0 \n * Google Chrome 6.0.399.0 \n * Google Chrome 6.0.400.0 \n * Google Chrome 6.0.401.0 \n * Google Chrome 6.0.401.1 \n * Google Chrome 6.0.403.0 \n * Google Chrome 6.0.404.0 \n * Google Chrome 6.0.404.1 \n * Google Chrome 6.0.404.2 \n * Google Chrome 6.0.405.0 \n * Google Chrome 6.0.406.0 \n * Google Chrome 6.0.407.0 \n * Google Chrome 6.0.408.0 \n * Google Chrome 6.0.408.1 \n * Google Chrome 6.0.408.10 \n * Google Chrome 6.0.408.2 \n * Google Chrome 6.0.408.3 \n * Google Chrome 6.0.408.4 \n * Google Chrome 6.0.408.5 \n * Google Chrome 6.0.408.6 \n * Google Chrome 6.0.408.7 \n * Google Chrome 6.0.408.8 \n * Google Chrome 6.0.408.9 \n * Google Chrome 6.0.409.0 \n * Google Chrome 6.0.410.0 \n * Google Chrome 6.0.411.0 \n * Google Chrome 6.0.412.0 \n * Google Chrome 6.0.413.0 \n * Google Chrome 6.0.414.0 \n * Google Chrome 6.0.415.0 \n * Google Chrome 6.0.415.1 \n * Google Chrome 6.0.416.0 \n * Google Chrome 6.0.416.1 \n * Google Chrome 6.0.417.0 \n * Google Chrome 6.0.418.0 \n * Google Chrome 6.0.418.1 \n * Google Chrome 6.0.418.2 \n * Google Chrome 6.0.418.3 \n * Google Chrome 6.0.418.4 \n * Google Chrome 6.0.418.5 \n * Google Chrome 6.0.418.6 \n * Google Chrome 6.0.418.7 \n * Google Chrome 6.0.418.8 \n * Google Chrome 6.0.418.9 \n * Google Chrome 6.0.419.0 \n * Google Chrome 6.0.421.0 \n * Google Chrome 6.0.422.0 \n * Google Chrome 6.0.423.0 \n * Google Chrome 6.0.424.0 \n * Google Chrome 6.0.425.0 \n * Google Chrome 6.0.426.0 \n * Google Chrome 6.0.427.0 \n * Google Chrome 6.0.428.0 \n * Google Chrome 6.0.430.0 \n * Google Chrome 6.0.431.0 \n * Google Chrome 6.0.432.0 \n * Google Chrome 6.0.433.0 \n * Google Chrome 6.0.434.0 \n * Google Chrome 6.0.435.0 \n * Google Chrome 6.0.436.0 \n * Google Chrome 6.0.437.0 \n * Google Chrome 6.0.437.1 \n * Google Chrome 6.0.437.2 \n * Google Chrome 6.0.437.3 \n * Google Chrome 6.0.438.0 \n * Google Chrome 6.0.440.0 \n * Google Chrome 6.0.441.0 \n * Google Chrome 6.0.443.0 \n * Google Chrome 6.0.444.0 \n * Google Chrome 6.0.445.0 \n * Google Chrome 6.0.445.1 \n * Google Chrome 6.0.446.0 \n * Google Chrome 6.0.447.0 \n * Google Chrome 6.0.447.1 \n * Google Chrome 6.0.447.2 \n * Google Chrome 6.0.449.0 \n * Google Chrome 6.0.450.0 \n * Google Chrome 6.0.450.1 \n * Google Chrome 6.0.450.2 \n * Google Chrome 6.0.450.3 \n * Google Chrome 6.0.450.4 \n * Google Chrome 6.0.451.0 \n * Google Chrome 6.0.452.0 \n * Google Chrome 6.0.452.1 \n * Google Chrome 6.0.453.0 \n * Google Chrome 6.0.453.1 \n * Google Chrome 6.0.454.0 \n * Google Chrome 6.0.455.0 \n * Google Chrome 6.0.456.0 \n * Google Chrome 6.0.457.0 \n * Google Chrome 6.0.458.0 \n * Google Chrome 6.0.458.1 \n * Google Chrome 6.0.458.2 \n * Google Chrome 6.0.459.0 \n * Google Chrome 6.0.460.0 \n * Google Chrome 6.0.461.0 \n * Google Chrome 6.0.462.0 \n * Google Chrome 6.0.464.1 \n * Google Chrome 6.0.465.1 \n * Google Chrome 6.0.465.2 \n * Google Chrome 6.0.466.0 \n * Google Chrome 6.0.466.1 \n * Google Chrome 6.0.466.2 \n * Google Chrome 6.0.466.3 \n * Google Chrome 6.0.466.4 \n * Google Chrome 6.0.466.5 \n * Google Chrome 6.0.466.6 \n * Google Chrome 6.0.467.0 \n * Google Chrome 6.0.469.0 \n * Google Chrome 6.0.470.0 \n * Google Chrome 6.0.471.0 \n * Google Chrome 6.0.472.0 \n * Google Chrome 6.0.472.1 \n * Google Chrome 6.0.472.10 \n * Google Chrome 6.0.472.11 \n * Google Chrome 6.0.472.12 \n * Google Chrome 6.0.472.13 \n * Google Chrome 6.0.472.14 \n * Google Chrome 6.0.472.15 \n * Google Chrome 6.0.472.16 \n * Google Chrome 6.0.472.17 \n * Google Chrome 6.0.472.18 \n * Google Chrome 6.0.472.19 \n * Google Chrome 6.0.472.2 \n * Google Chrome 6.0.472.20 \n * Google Chrome 6.0.472.21 \n * Google Chrome 6.0.472.22 \n * Google Chrome 6.0.472.23 \n * Google Chrome 6.0.472.24 \n * Google Chrome 6.0.472.25 \n * Google Chrome 6.0.472.26 \n * Google Chrome 6.0.472.27 \n * Google Chrome 6.0.472.28 \n * Google Chrome 6.0.472.29 \n * Google Chrome 6.0.472.3 \n * Google Chrome 6.0.472.30 \n * Google Chrome 6.0.472.31 \n * Google Chrome 6.0.472.32 \n * Google Chrome 6.0.472.33 \n * Google Chrome 6.0.472.34 \n * Google Chrome 6.0.472.35 \n * Google Chrome 6.0.472.36 \n * Google Chrome 6.0.472.37 \n * Google Chrome 6.0.472.38 \n * Google Chrome 6.0.472.39 \n * Google Chrome 6.0.472.4 \n * Google Chrome 6.0.472.40 \n * Google Chrome 6.0.472.41 \n * Google Chrome 6.0.472.42 \n * Google Chrome 6.0.472.43 \n * Google Chrome 6.0.472.44 \n * Google Chrome 6.0.472.45 \n * Google Chrome 6.0.472.46 \n * Google Chrome 6.0.472.47 \n * Google Chrome 6.0.472.48 \n * Google Chrome 6.0.472.49 \n * Google Chrome 6.0.472.5 \n * Google Chrome 6.0.472.50 \n * Google Chrome 6.0.472.51 \n * Google Chrome 6.0.472.52 \n * Google Chrome 6.0.472.53 \n * Google Chrome 6.0.472.54 \n * Google Chrome 6.0.472.55 \n * Google Chrome 6.0.472.56 \n * Google Chrome 6.0.472.57 \n * Google Chrome 6.0.472.58 \n * Google Chrome 6.0.472.59 \n * Google Chrome 6.0.472.6 \n * Google Chrome 6.0.472.60 \n * Google Chrome 6.0.472.61 \n * Google Chrome 6.0.472.62 \n * Google Chrome 6.0.472.63 \n * Google Chrome 6.0.472.7 \n * Google Chrome 6.0.472.8 \n * Google Chrome 6.0.472.9 \n * Google Chrome 6.0.473.0 \n * Google Chrome 6.0.474.0 \n * Google Chrome 6.0.475.0 \n * Google Chrome 6.0.476.0 \n * Google Chrome 6.0.477.0 \n * Google Chrome 6.0.478.0 \n * Google Chrome 6.0.479.0 \n * Google Chrome 6.0.480.0 \n * Google Chrome 6.0.481.0 \n * Google Chrome 6.0.482.0 \n * Google Chrome 6.0.483.0 \n * Google Chrome 6.0.484.0 \n * Google Chrome 6.0.485.0 \n * Google Chrome 6.0.486.0 \n * Google Chrome 6.0.487.0 \n * Google Chrome 6.0.488.0 \n * Google Chrome 6.0.489.0 \n * Google Chrome 6.0.490.0 \n * Google Chrome 6.0.490.1 \n * Google Chrome 6.0.491.0 \n * Google Chrome 6.0.492.0 \n * Google Chrome 6.0.493.0 \n * Google Chrome 6.0.494.0 \n * Google Chrome 6.0.495.0 \n * Google Chrome 6.0.495.1 \n * Google Chrome 6.0.496.0 \n * Google Chrome 60.0.3080.5 \n * Google Chrome 60.0.3112.78 \n * Google Chrome 60.0.3112.80 \n * Google Chrome 61.0.3163.100 \n * Google Chrome 61.0.3163.79 \n * Google Chrome 62.0.3202.62 \n * Google Chrome 62.0.3202.75 \n * Google Chrome 62.0.3202.89 \n * Google Chrome 7.0.497.0 \n * Google Chrome 7.0.498.0 \n * Google Chrome 7.0.499.0 \n * Google Chrome 7.0.499.1 \n * Google Chrome 7.0.500.0 \n * Google Chrome 7.0.500.1 \n * Google Chrome 7.0.503.0 \n * Google Chrome 7.0.503.1 \n * Google Chrome 7.0.504.0 \n * Google Chrome 7.0.505.0 \n * Google Chrome 7.0.506.0 \n * Google Chrome 7.0.507.0 \n * Google Chrome 7.0.507.1 \n * Google Chrome 7.0.507.2 \n * Google Chrome 7.0.507.3 \n * Google Chrome 7.0.509.0 \n * Google Chrome 7.0.510.0 \n * Google Chrome 7.0.511.1 \n * Google Chrome 7.0.511.2 \n * Google Chrome 7.0.511.4 \n * Google Chrome 7.0.512.0 \n * Google Chrome 7.0.513.0 \n * Google Chrome 7.0.514.0 \n * Google Chrome 7.0.514.1 \n * Google Chrome 7.0.515.0 \n * Google Chrome 7.0.516.0 \n * Google Chrome 7.0.517.0 \n * Google Chrome 7.0.517.10 \n * Google Chrome 7.0.517.11 \n * Google Chrome 7.0.517.12 \n * Google Chrome 7.0.517.13 \n * Google Chrome 7.0.517.14 \n * Google Chrome 7.0.517.16 \n * Google Chrome 7.0.517.17 \n * Google Chrome 7.0.517.18 \n * Google Chrome 7.0.517.19 \n * Google Chrome 7.0.517.2 \n * Google Chrome 7.0.517.20 \n * Google Chrome 7.0.517.21 \n * Google Chrome 7.0.517.22 \n * Google Chrome 7.0.517.23 \n * Google Chrome 7.0.517.24 \n * Google Chrome 7.0.517.25 \n * Google Chrome 7.0.517.26 \n * Google Chrome 7.0.517.27 \n * Google Chrome 7.0.517.28 \n * Google Chrome 7.0.517.29 \n * Google Chrome 7.0.517.30 \n * Google Chrome 7.0.517.31 \n * Google Chrome 7.0.517.32 \n * Google Chrome 7.0.517.33 \n * Google Chrome 7.0.517.34 \n * Google Chrome 7.0.517.35 \n * Google Chrome 7.0.517.36 \n * Google Chrome 7.0.517.37 \n * Google Chrome 7.0.517.38 \n * Google Chrome 7.0.517.39 \n * Google Chrome 7.0.517.4 \n * Google Chrome 7.0.517.40 \n * Google Chrome 7.0.517.41 \n * Google Chrome 7.0.517.42 \n * Google Chrome 7.0.517.43 \n * Google Chrome 7.0.517.44 \n * Google Chrome 7.0.517.5 \n * Google Chrome 7.0.517.6 \n * Google Chrome 7.0.517.7 \n * Google Chrome 7.0.517.8 \n * Google Chrome 7.0.517.9 \n * Google Chrome 7.0.518.0 \n * Google Chrome 7.0.519.0 \n * Google Chrome 7.0.520.0 \n * Google Chrome 7.0.521.0 \n * Google Chrome 7.0.522.0 \n * Google Chrome 7.0.524.0 \n * Google Chrome 7.0.525.0 \n * Google Chrome 7.0.526.0 \n * Google Chrome 7.0.528.0 \n * Google Chrome 7.0.529.0 \n * Google Chrome 7.0.529.1 \n * Google Chrome 7.0.529.2 \n * Google Chrome 7.0.530.0 \n * Google Chrome 7.0.531.0 \n * Google Chrome 7.0.531.1 \n * Google Chrome 7.0.531.2 \n * Google Chrome 7.0.535.1 \n * Google Chrome 7.0.535.2 \n * Google Chrome 7.0.536.0 \n * Google Chrome 7.0.536.1 \n * Google Chrome 7.0.536.2 \n * Google Chrome 7.0.536.3 \n * Google Chrome 7.0.536.4 \n * Google Chrome 7.0.537.0 \n * Google Chrome 7.0.538.0 \n * Google Chrome 7.0.539.0 \n * Google Chrome 7.0.540.0 \n * Google Chrome 7.0.541.0 \n * Google Chrome 7.0.542.0 \n * Google Chrome 7.0.544.0 \n * Google Chrome 7.0.547.0 \n * Google Chrome 7.0.547.1 \n * Google Chrome 7.0.548.0 \n * Google Chrome 8.0.549.0 \n * Google Chrome 8.0.550.0 \n * Google Chrome 8.0.551.0 \n * Google Chrome 8.0.551.1 \n * Google Chrome 8.0.552.0 \n * Google Chrome 8.0.552.1 \n * Google Chrome 8.0.552.10 \n * Google Chrome 8.0.552.100 \n * Google Chrome 8.0.552.101 \n * Google Chrome 8.0.552.102 \n * Google Chrome 8.0.552.103 \n * Google Chrome 8.0.552.104 \n * Google Chrome 8.0.552.105 \n * Google Chrome 8.0.552.11 \n * Google Chrome 8.0.552.12 \n * Google Chrome 8.0.552.13 \n * Google Chrome 8.0.552.14 \n * Google Chrome 8.0.552.15 \n * Google Chrome 8.0.552.16 \n * Google Chrome 8.0.552.17 \n * Google Chrome 8.0.552.18 \n * Google Chrome 8.0.552.19 \n * Google Chrome 8.0.552.2 \n * Google Chrome 8.0.552.20 \n * Google Chrome 8.0.552.200 \n * Google Chrome 8.0.552.201 \n * Google Chrome 8.0.552.202 \n * Google Chrome 8.0.552.203 \n * Google Chrome 8.0.552.204 \n * Google Chrome 8.0.552.205 \n * Google Chrome 8.0.552.206 \n * Google Chrome 8.0.552.207 \n * Google Chrome 8.0.552.208 \n * Google Chrome 8.0.552.209 \n * Google Chrome 8.0.552.21 \n * Google Chrome 8.0.552.210 \n * Google Chrome 8.0.552.211 \n * Google Chrome 8.0.552.212 \n * Google Chrome 8.0.552.213 \n * Google Chrome 8.0.552.214 \n * Google Chrome 8.0.552.215 \n * Google Chrome 8.0.552.216 \n * Google Chrome 8.0.552.217 \n * Google Chrome 8.0.552.218 \n * Google Chrome 8.0.552.219 \n * Google Chrome 8.0.552.220 \n * Google Chrome 8.0.552.221 \n * Google Chrome 8.0.552.222 \n * Google Chrome 8.0.552.223 \n * Google Chrome 8.0.552.224 \n * Google Chrome 8.0.552.225 \n * Google Chrome 8.0.552.226 \n * Google Chrome 8.0.552.227 \n * Google Chrome 8.0.552.228 \n * Google Chrome 8.0.552.229 \n * Google Chrome 8.0.552.23 \n * Google Chrome 8.0.552.230 \n * Google Chrome 8.0.552.231 \n * Google Chrome 8.0.552.232 \n * Google Chrome 8.0.552.233 \n * Google Chrome 8.0.552.234 \n * Google Chrome 8.0.552.235 \n * Google Chrome 8.0.552.237 \n * Google Chrome 8.0.552.24 \n * Google Chrome 8.0.552.25 \n * Google Chrome 8.0.552.26 \n * Google Chrome 8.0.552.27 \n * Google Chrome 8.0.552.28 \n * Google Chrome 8.0.552.29 \n * Google Chrome 8.0.552.300 \n * Google Chrome 8.0.552.301 \n * Google Chrome 8.0.552.302 \n * Google Chrome 8.0.552.303 \n * Google Chrome 8.0.552.304 \n * Google Chrome 8.0.552.305 \n * Google Chrome 8.0.552.306 \n * Google Chrome 8.0.552.307 \n * Google Chrome 8.0.552.308 \n * Google Chrome 8.0.552.309 \n * Google Chrome 8.0.552.310 \n * Google Chrome 8.0.552.311 \n * Google Chrome 8.0.552.312 \n * Google Chrome 8.0.552.313 \n * Google Chrome 8.0.552.315 \n * Google Chrome 8.0.552.316 \n * Google Chrome 8.0.552.317 \n * Google Chrome 8.0.552.318 \n * Google Chrome 8.0.552.319 \n * Google Chrome 8.0.552.320 \n * Google Chrome 8.0.552.321 \n * Google Chrome 8.0.552.322 \n * Google Chrome 8.0.552.323 \n * Google Chrome 8.0.552.324 \n * Google Chrome 8.0.552.325 \n * Google Chrome 8.0.552.326 \n * Google Chrome 8.0.552.327 \n * Google Chrome 8.0.552.328 \n * Google Chrome 8.0.552.329 \n * Google Chrome 8.0.552.330 \n * Google Chrome 8.0.552.331 \n * Google Chrome 8.0.552.332 \n * Google Chrome 8.0.552.333 \n * Google Chrome 8.0.552.334 \n * Google Chrome 8.0.552.335 \n * Google Chrome 8.0.552.336 \n * Google Chrome 8.0.552.337 \n * Google Chrome 8.0.552.338 \n * Google Chrome 8.0.552.339 \n * Google Chrome 8.0.552.340 \n * Google Chrome 8.0.552.341 \n * Google Chrome 8.0.552.342 \n * Google Chrome 8.0.552.343 \n * Google Chrome 8.0.552.344 \n * Google Chrome 8.0.552.35 \n * Google Chrome 8.0.552.4 \n * Google Chrome 8.0.552.40 \n * Google Chrome 8.0.552.41 \n * Google Chrome 8.0.552.42 \n * Google Chrome 8.0.552.43 \n * Google Chrome 8.0.552.44 \n * Google Chrome 8.0.552.45 \n * Google Chrome 8.0.552.47 \n * Google Chrome 8.0.552.48 \n * Google Chrome 8.0.552.49 \n * Google Chrome 8.0.552.5 \n * Google Chrome 8.0.552.50 \n * Google Chrome 8.0.552.51 \n * Google Chrome 8.0.552.52 \n * Google Chrome 8.0.552.6 \n * Google Chrome 8.0.552.7 \n * Google Chrome 8.0.552.8 \n * Google Chrome 8.0.552.9 \n * Google Chrome 8.0.553.0 \n * Google Chrome 8.0.554.0 \n * Google Chrome 8.0.556.0 \n * Google Chrome 8.0.557.0 \n * Google Chrome 8.0.558.0 \n * Google Chrome 8.0.559.0 \n * Google Chrome 8.0.560.0 \n * Google Chrome 8.0.561.0 \n * Google Chrome 9 \n * Google Chrome 9.0.562.0 \n * Google Chrome 9.0.563.0 \n * Google Chrome 9.0.564.0 \n * Google Chrome 9.0.565.0 \n * Google Chrome 9.0.566.0 \n * Google Chrome 9.0.567.0 \n * Google Chrome 9.0.568.0 \n * Google Chrome 9.0.569.0 \n * Google Chrome 9.0.570.0 \n * Google Chrome 9.0.570.1 \n * Google Chrome 9.0.571.0 \n * Google Chrome 9.0.572.0 \n * Google Chrome 9.0.572.1 \n * Google Chrome 9.0.573.0 \n * Google Chrome 9.0.574.0 \n * Google Chrome 9.0.575.0 \n * Google Chrome 9.0.576.0 \n * Google Chrome 9.0.577.0 \n * Google Chrome 9.0.578.0 \n * Google Chrome 9.0.579.0 \n * Google Chrome 9.0.580.0 \n * Google Chrome 9.0.581.0 \n * Google Chrome 9.0.582.0 \n * Google Chrome 9.0.583.0 \n * Google Chrome 9.0.584.0 \n * Google Chrome 9.0.585.0 \n * Google Chrome 9.0.586.0 \n * Google Chrome 9.0.587.0 \n * Google Chrome 9.0.587.1 \n * Google Chrome 9.0.588.0 \n * Google Chrome 9.0.589.0 \n * Google Chrome 9.0.590.0 \n * Google Chrome 9.0.591.0 \n * Google Chrome 9.0.592.0 \n * Google Chrome 9.0.593.0 \n * Google Chrome 9.0.594.0 \n * Google Chrome 9.0.595.0 \n * Google Chrome 9.0.596.0 \n * Google Chrome 9.0.597.0 \n * Google Chrome 9.0.597.1 \n * Google Chrome 9.0.597.10 \n * Google Chrome 9.0.597.100 \n * Google Chrome 9.0.597.101 \n * Google Chrome 9.0.597.102 \n * Google Chrome 9.0.597.106 \n * Google Chrome 9.0.597.107 \n * Google Chrome 9.0.597.11 \n * Google Chrome 9.0.597.12 \n * Google Chrome 9.0.597.14 \n * Google Chrome 9.0.597.15 \n * Google Chrome 9.0.597.16 \n * Google Chrome 9.0.597.17 \n * Google Chrome 9.0.597.18 \n * Google Chrome 9.0.597.19 \n * Google Chrome 9.0.597.2 \n * Google Chrome 9.0.597.20 \n * Google Chrome 9.0.597.21 \n * Google Chrome 9.0.597.22 \n * Google Chrome 9.0.597.23 \n * Google Chrome 9.0.597.24 \n * Google Chrome 9.0.597.25 \n * Google Chrome 9.0.597.26 \n * Google Chrome 9.0.597.27 \n * Google Chrome 9.0.597.28 \n * Google Chrome 9.0.597.29 \n * Google Chrome 9.0.597.30 \n * Google Chrome 9.0.597.31 \n * Google Chrome 9.0.597.32 \n * Google Chrome 9.0.597.33 \n * Google Chrome 9.0.597.34 \n * Google Chrome 9.0.597.35 \n * Google Chrome 9.0.597.36 \n * Google Chrome 9.0.597.37 \n * Google Chrome 9.0.597.38 \n * Google Chrome 9.0.597.39 \n * Google Chrome 9.0.597.4 \n * Google Chrome 9.0.597.40 \n * Google Chrome 9.0.597.41 \n * Google Chrome 9.0.597.42 \n * Google Chrome 9.0.597.44 \n * Google Chrome 9.0.597.45 \n * Google Chrome 9.0.597.46 \n * Google Chrome 9.0.597.47 \n * Google Chrome 9.0.597.5 \n * Google Chrome 9.0.597.54 \n * Google Chrome 9.0.597.55 \n * Google Chrome 9.0.597.56 \n * Google Chrome 9.0.597.57 \n * Google Chrome 9.0.597.58 \n * Google Chrome 9.0.597.59 \n * Google Chrome 9.0.597.60 \n * Google Chrome 9.0.597.62 \n * Google Chrome 9.0.597.63 \n * Google Chrome 9.0.597.64 \n * Google Chrome 9.0.597.65 \n * Google Chrome 9.0.597.66 \n * Google Chrome 9.0.597.67 \n * Google Chrome 9.0.597.68 \n * Google Chrome 9.0.597.69 \n * Google Chrome 9.0.597.7 \n * Google Chrome 9.0.597.70 \n * Google Chrome 9.0.597.71 \n * Google Chrome 9.0.597.72 \n * Google Chrome 9.0.597.73 \n * Google Chrome 9.0.597.74 \n * Google Chrome 9.0.597.75 \n * Google Chrome 9.0.597.76 \n * Google Chrome 9.0.597.77 \n * Google Chrome 9.0.597.78 \n * Google Chrome 9.0.597.79 \n * Google Chrome 9.0.597.8 \n * Google Chrome 9.0.597.80 \n * Google Chrome 9.0.597.81 \n * Google Chrome 9.0.597.82 \n * Google Chrome 9.0.597.83 \n * Google Chrome 9.0.597.84 \n * Google Chrome 9.0.597.85 \n * Google Chrome 9.0.597.86 \n * Google Chrome 9.0.597.88 \n * Google Chrome 9.0.597.9 \n * Google Chrome 9.0.597.90 \n * Google Chrome 9.0.597.92 \n * Google Chrome 9.0.597.94 \n * Google Chrome 9.0.597.96 \n * Google Chrome 9.0.597.97 \n * Google Chrome 9.0.597.98 \n * Google Chrome 9.0.597.99 \n * Google Chrome 9.0.598.0 \n * Google Chrome 9.0.599.0 \n * Google Chrome 9.0.600.0 \n * Google Chrome OS 0.10.140.0 \n * Google Chrome OS 0.9.110.6 \n * Google Chrome OS 0.9.126.0 \n * Google Chrome OS 0.9.128.3 \n * Google Chrome OS 0.9.130.14 Beta \n * Google Chrome OS 0.9.131.0 \n * Google Chrome OS 0.9.134.14 \n * Google Chrome OS 20.0.1132.0 \n * Google Chrome OS 20.0.1132.1 \n * Google Chrome OS 20.0.1132.10 \n * Google Chrome OS 20.0.1132.11 \n * Google Chrome OS 20.0.1132.12 \n * Google Chrome OS 20.0.1132.13 \n * Google Chrome OS 20.0.1132.14 \n * Google Chrome OS 20.0.1132.15 \n * Google Chrome OS 20.0.1132.16 \n * Google Chrome OS 20.0.1132.17 \n * Google Chrome OS 20.0.1132.18 \n * Google Chrome OS 20.0.1132.19 \n * Google Chrome OS 20.0.1132.2 \n * Google Chrome OS 20.0.1132.20 \n * Google Chrome OS 20.0.1132.21 \n * Google Chrome OS 20.0.1132.3 \n * Google Chrome OS 20.0.1132.4 \n * Google Chrome OS 20.0.1132.5 \n * Google Chrome OS 20.0.1132.6 \n * Google Chrome OS 20.0.1132.7 \n * Google Chrome OS 20.0.1132.8 \n * Google Chrome OS 20.0.1132.9 \n * Google Chrome OS 21.0.1180.0 \n * Google Chrome OS 21.0.1180.1 \n * Google Chrome OS 21.0.1180.10 \n * Google Chrome OS 21.0.1180.11 \n * Google Chrome OS 21.0.1180.13 \n * Google Chrome OS 21.0.1180.14 \n * Google Chrome OS 21.0.1180.15 \n * Google Chrome OS 21.0.1180.17 \n * Google Chrome OS 21.0.1180.18 \n * Google Chrome OS 21.0.1180.2 \n * Google Chrome OS 21.0.1180.3 \n * Google Chrome OS 21.0.1180.31 \n * Google Chrome OS 21.0.1180.32 \n * Google Chrome OS 21.0.1180.33 \n * Google Chrome OS 21.0.1180.34 \n * Google Chrome OS 21.0.1180.35 \n * Google Chrome OS 21.0.1180.36 \n * Google Chrome OS 21.0.1180.37 \n * Google Chrome OS 21.0.1180.38 \n * Google Chrome OS 21.0.1180.39 \n * Google Chrome OS 21.0.1180.4 \n * Google Chrome OS 21.0.1180.41 \n * Google Chrome OS 21.0.1180.46 \n * Google Chrome OS 21.0.1180.47 \n * Google Chrome OS 21.0.1180.48 \n * Google Chrome OS 21.0.1180.49 \n * Google Chrome OS 21.0.1180.5 \n * Google Chrome OS 21.0.1180.50 \n * Google Chrome OS 21.0.1180.51 \n * Google Chrome OS 21.0.1180.52 \n * Google Chrome OS 21.0.1180.53 \n * Google Chrome OS 21.0.1180.54 \n * Google Chrome OS 21.0.1180.55 \n * Google Chrome OS 21.0.1180.56 \n * Google Chrome OS 21.0.1180.57 \n * Google Chrome OS 21.0.1180.6 \n * Google Chrome OS 21.0.1180.7 \n * Google Chrome OS 21.0.1180.79 \n * Google Chrome OS 21.0.1180.8 \n * Google Chrome OS 21.0.1180.81 \n * Google Chrome OS 21.0.1180.9 \n * Google Chrome OS 21.0.1183.0 \n * Google Chrome OS 23.0.1271.94 \n * Google Chrome OS 25.0.1364.0 \n * Google Chrome OS 25.0.1364.1 \n * Google Chrome OS 25.0.1364.10 \n * Google Chrome OS 25.0.1364.108 \n * Google Chrome OS 25.0.1364.11 \n * Google Chrome OS 25.0.1364.110 \n * Google Chrome OS 25.0.1364.112 \n * Google Chrome OS 25.0.1364.113 \n * Google Chrome OS 25.0.1364.114 \n * Google Chrome OS 25.0.1364.115 \n * Google Chrome OS 25.0.1364.116 \n * Google Chrome OS 25.0.1364.117 \n * Google Chrome OS 25.0.1364.118 \n * Google Chrome OS 25.0.1364.119 \n * Google Chrome OS 25.0.1364.12 \n * Google Chrome OS 25.0.1364.120 \n * Google Chrome OS 25.0.1364.121 \n * Google Chrome OS 25.0.1364.122 \n * Google Chrome OS 25.0.1364.123 \n * Google Chrome OS 25.0.1364.124 \n * Google Chrome OS 25.0.1364.125 \n * Google Chrome OS 25.0.1364.126 \n * Google Chrome OS 25.0.1364.13 \n * Google Chrome OS 25.0.1364.14 \n * Google Chrome OS 25.0.1364.15 \n * Google Chrome OS 25.0.1364.152 \n * Google Chrome OS 25.0.1364.154 \n * Google Chrome OS 25.0.1364.155 \n * Google Chrome OS 25.0.1364.156 \n * Google Chrome OS 25.0.1364.159 \n * Google Chrome OS 25.0.1364.16 \n * Google Chrome OS 25.0.1364.160 \n * Google Chrome OS 25.0.1364.161 \n * Google Chrome OS 25.0.1364.168 \n * Google Chrome OS 25.0.1364.169 \n * Google Chrome OS 25.0.1364.17 \n * Google Chrome OS 25.0.1364.170 \n * Google Chrome OS 25.0.1364.171 \n * Google Chrome OS 25.0.1364.172 \n * Google Chrome OS 25.0.1364.173 \n * Google Chrome OS 25.0.1364.18 \n * Google Chrome OS 25.0.1364.19 \n * Google Chrome OS 25.0.1364.2 \n * Google Chrome OS 25.0.1364.20 \n * Google Chrome OS 25.0.1364.21 \n * Google Chrome OS 25.0.1364.22 \n * Google Chrome OS 25.0.1364.23 \n * Google Chrome OS 25.0.1364.24 \n * Google Chrome OS 25.0.1364.25 \n * Google Chrome OS 25.0.1364.26 \n * Google Chrome OS 25.0.1364.27 \n * Google Chrome OS 25.0.1364.28 \n * Google Chrome OS 25.0.1364.29 \n * Google Chrome OS 25.0.1364.3 \n * Google Chrome OS 25.0.1364.30 \n * Google Chrome OS 25.0.1364.31 \n * Google Chrome OS 25.0.1364.32 \n * Google Chrome OS 25.0.1364.33 \n * Google Chrome OS 25.0.1364.34 \n * Google Chrome OS 25.0.1364.35 \n * Google Chrome OS 25.0.1364.36 \n * Google Chrome OS 25.0.1364.37 \n * Google Chrome OS 25.0.1364.38 \n * Google Chrome OS 25.0.1364.39 \n * Google Chrome OS 25.0.1364.40 \n * Google Chrome OS 25.0.1364.41 \n * Google Chrome OS 25.0.1364.42 \n * Google Chrome OS 25.0.1364.43 \n * Google Chrome OS 25.0.1364.44 \n * Google Chrome OS 25.0.1364.45 \n * Google Chrome OS 25.0.1364.46 \n * Google Chrome OS 25.0.1364.47 \n * Google Chrome OS 25.0.1364.48 \n * Google Chrome OS 25.0.1364.49 \n * Google Chrome OS 25.0.1364.5 \n * Google Chrome OS 25.0.1364.50 \n * Google Chrome OS 25.0.1364.51 \n * Google Chrome OS 25.0.1364.52 \n * Google Chrome OS 25.0.1364.53 \n * Google Chrome OS 25.0.1364.54 \n * Google Chrome OS 25.0.1364.55 \n * Google Chrome OS 25.0.1364.56 \n * Google Chrome OS 25.0.1364.57 \n * Google Chrome OS 25.0.1364.58 \n * Google Chrome OS 25.0.1364.61 \n * Google Chrome OS 25.0.1364.62 \n * Google Chrome OS 25.0.1364.63 \n * Google Chrome OS 25.0.1364.65 \n * Google Chrome OS 25.0.1364.66 \n * Google Chrome OS 25.0.1364.67 \n * Google Chrome OS 25.0.1364.68 \n * Google Chrome OS 25.0.1364.7 \n * Google Chrome OS 25.0.1364.70 \n * Google Chrome OS 25.0.1364.72 \n * Google Chrome OS 25.0.1364.73 \n * Google Chrome OS 25.0.1364.74 \n * Google Chrome OS 25.0.1364.75 \n * Google Chrome OS 25.0.1364.76 \n * Google Chrome OS 25.0.1364.77 \n * Google Chrome OS 25.0.1364.78 \n * Google Chrome OS 25.0.1364.79 \n * Google Chrome OS 25.0.1364.8 \n * Google Chrome OS 25.0.1364.80 \n * Google Chrome OS 25.0.1364.81 \n * Google Chrome OS 25.0.1364.82 \n * Google Chrome OS 25.0.1364.84 \n * Google Chrome OS 25.0.1364.85 \n * Google Chrome OS 25.0.1364.86 \n * Google Chrome OS 25.0.1364.87 \n * Google Chrome OS 25.0.1364.88 \n * Google Chrome OS 25.0.1364.89 \n * Google Chrome OS 25.0.1364.9 \n * Google Chrome OS 25.0.1364.90 \n * Google Chrome OS 25.0.1364.91 \n * Google Chrome OS 25.0.1364.92 \n * Google Chrome OS 25.0.1364.93 \n * Google Chrome OS 25.0.1364.95 \n * Google Chrome OS 25.0.1364.98 \n * Google Chrome OS 25.0.1364.99 \n * Google Chrome OS 26.0.1410.0 \n * Google Chrome OS 26.0.1410.1 \n * Google Chrome OS 26.0.1410.10 \n * Google Chrome OS 26.0.1410.11 \n * Google Chrome OS 26.0.1410.12 \n * Google Chrome OS 26.0.1410.14 \n * Google Chrome OS 26.0.1410.15 \n * Google Chrome OS 26.0.1410.16 \n * Google Chrome OS 26.0.1410.17 \n * Google Chrome OS 26.0.1410.18 \n * Google Chrome OS 26.0.1410.19 \n * Google Chrome OS 26.0.1410.20 \n * Google Chrome OS 26.0.1410.21 \n * Google Chrome OS 26.0.1410.22 \n * Google Chrome OS 26.0.1410.23 \n * Google Chrome OS 26.0.1410.24 \n * Google Chrome OS 26.0.1410.25 \n * Google Chrome OS 26.0.1410.26 \n * Google Chrome OS 26.0.1410.27 \n * Google Chrome OS 26.0.1410.28 \n * Google Chrome OS 26.0.1410.29 \n * Google Chrome OS 26.0.1410.3 \n * Google Chrome OS 26.0.1410.30 \n * Google Chrome OS 26.0.1410.31 \n * Google Chrome OS 26.0.1410.32 \n * Google Chrome OS 26.0.1410.33 \n * Google Chrome OS 26.0.1410.34 \n * Google Chrome OS 26.0.1410.35 \n * Google Chrome OS 26.0.1410.36 \n * Google Chrome OS 26.0.1410.37 \n * Google Chrome OS 26.0.1410.38 \n * Google Chrome OS 26.0.1410.39 \n * Google Chrome OS 26.0.1410.4 \n * Google Chrome OS 26.0.1410.40 \n * Google Chrome OS 26.0.1410.41 \n * Google Chrome OS 26.0.1410.42 \n * Google Chrome OS 26.0.1410.43 \n * Google Chrome OS 26.0.1410.44 \n * Google Chrome OS 26.0.1410.45 \n * Google Chrome OS 26.0.1410.46 \n * Google Chrome OS 26.0.1410.47 \n * Google Chrome OS 26.0.1410.48 \n * Google Chrome OS 26.0.1410.49 \n * Google Chrome OS 26.0.1410.5 \n * Google Chrome OS 26.0.1410.50 \n * Google Chrome OS 26.0.1410.51 \n * Google Chrome OS 26.0.1410.52 \n * Google Chrome OS 26.0.1410.54 \n * Google Chrome OS 26.0.1410.55 \n * Google Chrome OS 26.0.1410.56 \n * Google Chrome OS 26.0.1410.57 \n * Google Chrome OS 26.0.1410.6 \n * Google Chrome OS 26.0.1410.7 \n * Google Chrome OS 26.0.1410.8 \n * Google Chrome OS 26.0.1410.9 \n * Google Chrome OS 28.0.1500.71 \n * Google Chrome OS 28.0.1500.95 \n * Google Chrome OS 32.0.1700.95 \n * Google Chrome OS 33.0.1750.152 \n * Google Chrome OS 35.0.1916.155 \n * Google Chrome OS 37.0.2062.119 \n * Google Chrome OS 40.0.2214.114 \n * Google Chrome OS 48.0.2564.116 \n * Google Chrome OS 48.0.2564.92 \n * Google Chrome OS 52.0.2743.85 \n * Google Chrome OS 53.0.2785.103 \n * Google Chrome OS 53.0.2785.144 \n * Google Chrome OS 54.0.2840.79 \n * Google Chrome OS 57.0.2987.137 \n * Google Chrome OS 58.0.3029.89 \n * Google Chrome OS 59.0.3071.91 \n * Google Chrome OS 59.0.3071.92 \n * Google Chrome OS 60.0.3112.114 \n * Google Chrome OS 61.0.3163.113 \n * Google Chrome OS 62.0.3202.97 \n * Google Chrome OS 8.0.552.342 \n * Google Chrome OS 8.0.552.343 \n * Google Chrome OS 8.0.552.344 \n * Google Nexus 5X \n * Google Nexus 6P \n * Google Pixel 2 XL \n * Google Pixel C \n * Google Pixel XL \n * Google V8 \n * HP ProLiant DL385 Gen10 Server 1.02 \n * IBM AIX 5.3 \n * IBM AIX 6.1 \n * IBM AIX 7.1 \n * IBM Aix 7.2 \n * IBM Vios 2.2.0 \n * Intel Xeon CPU E5-1650 v3 \n * Linux kernel 4.14.11 \n * Linux kernel 4.9.74 \n * Microsoft Edge \n * Microsoft Internet Explorer 11 \n * Microsoft SQL Server 2008 R2 for 32-bit Systems Service Pack 3 \n * Microsoft SQL Server 2008 R2 for x64-based Systems Service Pack 3 \n * Microsoft SQL Server 2008 for 32-bit Systems Service Pack 4 \n * Microsoft SQL Server 2008 for x64-based Systems Service Pack 4 \n * Microsoft SQL Server 2012 for 32-bit Systems Service Pack 3 \n * Microsoft SQL Server 2012 for 32-bit Systems Service Pack 4 \n * Microsoft SQL Server 2012 for x64-based Systems Service Pack 3 \n * Microsoft SQL Server 2012 for x64-based Systems Service Pack 4 \n * Microsoft SQL Server 2014 for 32-bit Systems Service Pack 2 \n * Microsoft SQL Server 2014 for x64-based Systems Service Pack 2 \n * Microsoft SQL Server 2016 for x64-based Systems \n * Microsoft SQL Server 2016 for x64-based Systems Service Pack 1 \n * Microsoft SQL Server 2017 for x64-based Systems \n * Microsoft Windows 10 Version 1607 for 32-bit Systems \n * Microsoft Windows 10 Version 1607 for x64-based Systems \n * Microsoft Windows 10 for 32-bit Systems \n * Microsoft Windows 10 for x64-based Systems \n * Microsoft Windows 10 version 1511 for 32-bit Systems \n * Microsoft Windows 10 version 1511 for x64-based Systems \n * Microsoft Windows 10 version 1703 for 32-bit Systems \n * Microsoft Windows 10 version 1703 for x64-based Systems \n * Microsoft Windows 10 version 1709 for 32-bit Systems \n * Microsoft Windows 7 for 32-bit Systems SP1 \n * Microsoft Windows 7 for x64-based Systems SP1 \n * Microsoft Windows 8.1 for 32-bit Systems \n * Microsoft Windows 8.1 for x64-based Systems \n * Microsoft Windows Server 2008 R2 for Itanium-based Systems SP1 \n * Microsoft Windows Server 2008 R2 for x64-based Systems SP1 \n * Microsoft Windows Server 2012 \n * Microsoft Windows Server 2012 R2 \n * Microsoft Windows Server 2016 \n * Mozilla Firefox 0.1 \n * Mozilla Firefox 0.10.0 \n * Mozilla Firefox 0.10.1 \n * Mozilla Firefox 0.2 \n * Mozilla Firefox 0.3 \n * Mozilla Firefox 0.4 \n * Mozilla Firefox 0.5 \n * Mozilla Firefox 0.6 \n * Mozilla Firefox 0.6.1 \n * Mozilla Firefox 0.7 \n * Mozilla Firefox 0.7.1 \n * Mozilla Firefox 0.8.0 \n * Mozilla Firefox 0.9.0 \n * Mozilla Firefox 0.9.1 \n * Mozilla Firefox 0.9.2 \n * Mozilla Firefox 0.9.3 \n * Mozilla Firefox 1.0.0 \n * Mozilla Firefox 1.0.1 \n * Mozilla Firefox 1.0.2 \n * Mozilla Firefox 1.0.3 \n * Mozilla Firefox 1.0.4 \n * Mozilla Firefox 1.0.5 \n * Mozilla Firefox 1.0.6 \n * Mozilla Firefox 1.0.7 \n * Mozilla Firefox 1.0.8 \n * Mozilla Firefox 1.4.1 \n * Mozilla Firefox 1.5.0 12 \n * Mozilla Firefox 1.5.0 \n * Mozilla Firefox 1.5.0.1 \n * Mozilla Firefox 1.5.0.10 \n * Mozilla Firefox 1.5.0.11 \n * Mozilla Firefox 1.5.0.2 \n * Mozilla Firefox 1.5.0.3 \n * Mozilla Firefox 1.5.0.4 \n * Mozilla Firefox 1.5.0.5 \n * Mozilla Firefox 1.5.0.6 \n * Mozilla Firefox 1.5.0.7 \n * Mozilla Firefox 1.5.0.8 \n * Mozilla Firefox 1.5.0.9 \n * Mozilla Firefox 1.5.1 \n * Mozilla Firefox 1.5.2 \n * Mozilla Firefox 1.5.3 \n * Mozilla Firefox 1.5.4 \n * Mozilla Firefox 1.5.5 \n * Mozilla Firefox 1.5.6 \n * Mozilla Firefox 1.5.7 \n * Mozilla Firefox 1.5.8 \n * Mozilla Firefox 1.8 \n * Mozilla Firefox 10 \n * Mozilla Firefox 10.0 \n * Mozilla Firefox 10.0.1 \n * Mozilla Firefox 10.0.10 \n * Mozilla Firefox 10.0.11 \n * Mozilla Firefox 10.0.12 \n * Mozilla Firefox 10.0.2 \n * Mozilla Firefox 10.0.3 \n * Mozilla Firefox 10.0.4 \n * Mozilla Firefox 10.0.5 \n * Mozilla Firefox 10.0.6 \n * Mozilla Firefox 10.0.7 \n * Mozilla Firefox 10.0.8 \n * Mozilla Firefox 10.0.9 \n * Mozilla Firefox 11.0 \n * Mozilla Firefox 12.0 \n * Mozilla Firefox 13.0 \n * Mozilla Firefox 13.0.1 \n * Mozilla Firefox 14 \n * Mozilla Firefox 14.0 \n * Mozilla Firefox 14.0.1 \n * Mozilla Firefox 14.01 \n * Mozilla Firefox 15 \n * Mozilla Firefox 15.0 \n * Mozilla Firefox 15.0.1 \n * Mozilla Firefox 16 \n * Mozilla Firefox 16.0 \n * Mozilla Firefox 16.0.1 \n * Mozilla Firefox 16.0.2 \n * Mozilla Firefox 17.0 \n * Mozilla Firefox 17.0.1 \n * Mozilla Firefox 17.0.10 \n * Mozilla Firefox 17.0.11 \n * Mozilla Firefox 17.0.2 \n * Mozilla Firefox 17.0.3 \n * Mozilla Firefox 17.0.4 \n * Mozilla Firefox 17.0.5 \n * Mozilla Firefox 17.0.6 \n * Mozilla Firefox 17.0.7 \n * Mozilla Firefox 17.0.8 \n * Mozilla Firefox 17.0.9 \n * Mozilla Firefox 18.0 \n * Mozilla Firefox 18.0.1 \n * Mozilla Firefox 18.0.2 \n * Mozilla Firefox 19.0 \n * Mozilla Firefox 19.0.1 \n * Mozilla Firefox 19.0.2 \n * Mozilla Firefox 2.0 .1 \n * Mozilla Firefox 2.0 .10 \n * Mozilla Firefox 2.0 .4 \n * Mozilla Firefox 2.0 .5 \n * Mozilla Firefox 2.0 .6 \n * Mozilla Firefox 2.0 .7 \n * Mozilla Firefox 2.0 .9 \n * Mozilla Firefox 2.0 8 \n * Mozilla Firefox 2.0 \n * Mozilla Firefox 2.0.0 .19 \n * Mozilla Firefox 2.0.0 20 \n * Mozilla Firefox 2.0.0.1 \n * Mozilla Firefox 2.0.0.10 \n * Mozilla Firefox 2.0.0.11 \n * Mozilla Firefox 2.0.0.12 \n * Mozilla Firefox 2.0.0.13 \n * Mozilla Firefox 2.0.0.14 \n * Mozilla Firefox 2.0.0.15 \n * Mozilla Firefox 2.0.0.16 \n * Mozilla Firefox 2.0.0.17 \n * Mozilla Firefox 2.0.0.18 \n * Mozilla Firefox 2.0.0.19 \n * Mozilla Firefox 2.0.0.2 \n * Mozilla Firefox 2.0.0.21 \n * Mozilla Firefox 2.0.0.3 \n * Mozilla Firefox 2.0.0.4 \n * Mozilla Firefox 2.0.0.5 \n * Mozilla Firefox 2.0.0.6 \n * Mozilla Firefox 2.0.0.7 \n * Mozilla Firefox 2.0.0.8 \n * Mozilla Firefox 2.0.0.9 \n * Mozilla Firefox 20.0 \n * Mozilla Firefox 20.0.1 \n * Mozilla Firefox 21.0 \n * Mozilla Firefox 22.0 \n * Mozilla Firefox 22.0.0.4917 \n * Mozilla Firefox 23.0 \n * Mozilla Firefox 23.0.1 \n * Mozilla Firefox 24.0 \n * Mozilla Firefox 24.1 \n * Mozilla Firefox 24.1.1 \n * Mozilla Firefox 25.0 \n * Mozilla Firefox 25.0.1 \n * Mozilla Firefox 26 \n * Mozilla Firefox 26.0 \n * Mozilla Firefox 27 \n * Mozilla Firefox 27.0 \n * Mozilla Firefox 27.0.1 \n * Mozilla Firefox 28 \n * Mozilla Firefox 28.0 \n * Mozilla Firefox 28.0.1 \n * Mozilla Firefox 29 \n * Mozilla Firefox 29.0 \n * Mozilla Firefox 29.0.1 \n * Mozilla Firefox 3.0 \n * Mozilla Firefox 3.0.1 \n * Mozilla Firefox 3.0.10 \n * Mozilla Firefox 3.0.11 \n * Mozilla Firefox 3.0.12 \n * Mozilla Firefox 3.0.13 \n * Mozilla Firefox 3.0.14 \n * Mozilla Firefox 3.0.15 \n * Mozilla Firefox 3.0.16 \n * Mozilla Firefox 3.0.17 \n * Mozilla Firefox 3.0.18 \n * Mozilla Firefox 3.0.19 \n * Mozilla Firefox 3.0.2 \n * Mozilla Firefox 3.0.3 \n * Mozilla Firefox 3.0.4 \n * Mozilla Firefox 3.0.5 \n * Mozilla Firefox 3.0.6 \n * Mozilla Firefox 3.0.7 \n * Mozilla Firefox 3.0.8 \n * Mozilla Firefox 3.0.9 \n * Mozilla Firefox 3.1 \n * Mozilla Firefox 3.5.0 \n * Mozilla Firefox 3.5.1 \n * Mozilla Firefox 3.5.10 \n * Mozilla Firefox 3.5.11 \n * Mozilla Firefox 3.5.12 \n * Mozilla Firefox 3.5.13 \n * Mozilla Firefox 3.5.14 \n * Mozilla Firefox 3.5.15 \n * Mozilla Firefox 3.5.16 \n * Mozilla Firefox 3.5.17 \n * Mozilla Firefox 3.5.18 \n * Mozilla Firefox 3.5.19 \n * Mozilla Firefox 3.5.2 \n * Mozilla Firefox 3.5.3 \n * Mozilla Firefox 3.5.4 \n * Mozilla Firefox 3.5.5 \n * Mozilla Firefox 3.5.6 \n * Mozilla Firefox 3.5.7 \n * Mozilla Firefox 3.5.8 \n * Mozilla Firefox 3.5.9 \n * Mozilla Firefox 3.6 \n * Mozilla Firefox 3.6.1 \n * Mozilla Firefox 3.6.10 \n * Mozilla Firefox 3.6.11 \n * Mozilla Firefox 3.6.12 \n * Mozilla Firefox 3.6.13 \n * Mozilla Firefox 3.6.14 \n * Mozilla Firefox 3.6.15 \n * Mozilla Firefox 3.6.16 \n * Mozilla Firefox 3.6.17 \n * Mozilla Firefox 3.6.18 \n * Mozilla Firefox 3.6.19 \n * Mozilla Firefox 3.6.2 \n * Mozilla Firefox 3.6.20 \n * Mozilla Firefox 3.6.21 \n * Mozilla Firefox 3.6.22 \n * Mozilla Firefox 3.6.23 \n * Mozilla Firefox 3.6.24 \n * Mozilla Firefox 3.6.25 \n * Mozilla Firefox 3.6.26 \n * Mozilla Firefox 3.6.27 \n * Mozilla Firefox 3.6.28 \n * Mozilla Firefox 3.6.3 \n * Mozilla Firefox 3.6.4 \n * Mozilla Firefox 3.6.5 \n * Mozilla Firefox 3.6.6 \n * Mozilla Firefox 3.6.7 \n * Mozilla Firefox 3.6.8 \n * Mozilla Firefox 3.6.9 \n * Mozilla Firefox 30 \n * Mozilla Firefox 30.0 \n * Mozilla Firefox 31 \n * Mozilla Firefox 31.0 \n * Mozilla Firefox 31.1 \n * Mozilla Firefox 31.1.0 \n * Mozilla Firefox 31.6 \n * Mozilla Firefox 31.8 \n * Mozilla Firefox 31.8.0 \n * Mozilla Firefox 32 \n * Mozilla Firefox 32.0 \n * Mozilla Firefox 32.0.3 \n * Mozilla Firefox 33 \n * Mozilla Firefox 33.0 \n * Mozilla Firefox 34 \n * Mozilla Firefox 34.0.5 \n * Mozilla Firefox 35 \n * Mozilla Firefox 35.0.1 \n * Mozilla Firefox 36 \n * Mozilla Firefox 36.0.3 \n * Mozilla Firefox 36.0.4 \n * Mozilla Firefox 37 \n * Mozilla Firefox 37.0.1 \n * Mozilla Firefox 37.0.2 \n * Mozilla Firefox 38 \n * Mozilla Firefox 39 \n * Mozilla Firefox 39.0.3 \n * Mozilla Firefox 4.0 \n * Mozilla Firefox 4.0.1 \n * Mozilla Firefox 40 \n * Mozilla Firefox 40.0.3 \n * Mozilla Firefox 41 \n * Mozilla Firefox 41.0.2 \n * Mozilla Firefox 42 \n * Mozilla Firefox 43 \n * Mozilla Firefox 43.0.1 \n * Mozilla Firefox 43.0.2 \n * Mozilla Firefox 44 \n * Mozilla Firefox 44.0.2 \n * Mozilla Firefox 45 \n * Mozilla Firefox 45.0.2 \n * Mozilla Firefox 46 \n * Mozilla Firefox 46.0.1 \n * Mozilla Firefox 47 \n * Mozilla Firefox 48 \n * Mozilla Firefox 49 \n * Mozilla Firefox 49.0.1 \n * Mozilla Firefox 49.0.2 \n * Mozilla Firefox 5.0 \n * Mozilla Firefox 5.0.1 \n * Mozilla Firefox 50 \n * Mozilla Firefox 50.0.1 \n * Mozilla Firefox 50.0.2 \n * Mozilla Firefox 50.1 \n * Mozilla Firefox 51 \n * Mozilla Firefox 52 \n * Mozilla Firefox 52.0.1 \n * Mozilla Firefox 53 \n * Mozilla Firefox 53.0.2 \n * Mozilla Firefox 54 \n * Mozilla Firefox 55 \n * Mozilla Firefox 56 \n * Mozilla Firefox 57 \n * Mozilla Firefox 57.0.1 \n * Mozilla Firefox 57.0.2 \n * Mozilla Firefox 6 \n * Mozilla Firefox 6.0 \n * Mozilla Firefox 6.0.1 \n * Mozilla Firefox 6.0.2 \n * Mozilla Firefox 7 \n * Mozilla Firefox 7.0 \n * Mozilla Firefox 7.0.1 \n * Mozilla Firefox 8.0 \n * Mozilla Firefox 8.0.1 \n * Mozilla Firefox 9.0 \n * Mozilla Firefox 9.0.1 \n * Redhat Enterprise Linux 5 \n * Redhat Enterprise Linux 6 \n * Redhat Enterprise Linux 7 \n * Redhat Enterprise Linux Desktop 6 \n * Redhat Enterprise Linux Desktop 7 \n * Redhat Enterprise Linux EUS Compute Node 6.7 \n * Redhat Enterprise Linux EUS Compute Node 7.3 \n * Redhat Enterprise Linux EUS Compute Node 7.4 \n * Redhat Enterprise Linux Server (for IBM Power LE) - 4 Year Extended Upd 7.3 \n * Redhat Enterprise Linux Server (for IBM Power LE) - 4 Year Extended Update Support 7.4 \n * Redhat Enterprise Linux Server - 4 Year Extended Update Support 7.2 \n * Redhat Enterprise Linux Server - 4 Year Extended Update Support 7.3 \n * Redhat Enterprise Linux Server - 4 Year Extended Update Support 7.4 \n * Redhat Enterprise Linux Server - AUS 6.6 \n * Redhat Enterprise Linux Server - AUS 7.2 \n * Redhat Enterprise Linux Server - AUS 7.3 \n * Redhat Enterprise Linux Server - AUS 7.4 \n * Redhat Enterprise Linux Server - Extended Update Support 6.7 \n * Redhat Enterprise Linux Server - Extended Update Support 7.3 \n * Redhat Enterprise Linux Server - Extended Update Support 7.4 \n * Redhat Enterprise Linux Server - TUS 6.6 \n * Redhat Enterprise Linux Server - TUS 7.2 \n * Redhat Enterprise Linux Server - TUS 7.3 \n * Redhat Enterprise Linux Server - TUS 7.4 \n * Redhat Enterprise Linux Server 6 \n * Redhat Enterprise Linux Server 7 \n * Redhat Enterprise Linux Workstation 6 \n * Redhat Enterprise Linux Workstation 7 \n * Redhat Enterprise Linux for IBM z Systems - Extended Update Support 6.7 \n * Redhat Enterprise Linux for IBM z Systems - Extended Update Support 7.4 \n * Redhat Enterprise Linux for IBM z Systems 6 \n * Redhat Enterprise Linux for IBM z Systems 7 \n * Redhat Enterprise Linux for Power, big endian - Extended Update Support 6.7 \n * Redhat Enterprise Linux for Power, big endian - Extended Update Support 7.3 \n * Redhat Enterprise Linux for Power, big endian - Extended Update Support 7.4 \n * Redhat Enterprise Linux for Power, big endian 6 \n * Redhat Enterprise Linux for Power, big endian 7 \n * Redhat Enterprise Linux for Power, little endian - Extended Update Supp 7.3 \n * Redhat Enterprise Linux for Power, little endian - Extended Update Supp 7.4 \n * Redhat Enterprise Linux for Power, little endian 7 \n * Redhat Enterprise Linux for Real Time 7 \n * Redhat Enterprise Linux for Real Time for NFV 7 \n * Redhat Enterprise Linux for Scientific Computing 6 \n * Redhat Enterprise Linux for Scientific Computing 7 \n * Redhat Enterprise Mrg 2 \n * Redhat Virtualization Host 4 \n * VMWare ESXi 5.5 \n * VMWare Esxi 6.0 \n * VMWare Esxi 6.5 \n * VMWare Fusion 8.0 \n * VMWare Fusion 8.0.1 \n * VMWare Fusion 8.0.2 \n * VMWare Fusion 8.1.0 \n * VMWare Fusion 8.1.1 \n * VMWare Fusion 8.5 \n * VMWare Fusion 8.5.2 \n * VMWare Fusion 8.5.4 \n * VMWare Fusion 8.5.5 \n * VMWare Fusion 8.5.6 \n * VMWare Fusion 8.5.8 \n * VMWare Identity Manager 2.0 \n * VMWare Identity Manager 2.7 \n * VMWare Identity Manager 2.7.1 \n * VMWare Identity Manager 3.0 \n * VMWare Workstation 12.0 \n * VMWare Workstation 12.5.3 \n * VMWare Workstation 12.5.5 \n * VMWare Workstation 12.5.7 \n * VMWare vCenter Server 6.0 \n * VMWare vCenter Server 6.5 \n * VMWare vCloud Usage Meter 3.0 \n * VMWare vCloud Usage Meter 3.3 \n * VMWare vCloud Usage Meter 3.3.3 \n * VMWare vRealize Automation 6.0 \n * VMWare vRealize Automation 6.1 \n * VMWare vRealize Automation 6.2 \n * VMWare vRealize Automation 6.2.4 \n * VMWare vRealize Automation 6.2.4.1 \n * VMWare vRealize Automation 6.2.5 \n * VMWare vRealize Automation 7.0 \n * VMWare vRealize Automation 7.1 \n * VMWare vRealize Automation 7.2.0 \n * VMWare vRealize Automation 7.3.0 \n * VMWare vSphere Data Protection 6.0 \n * VMWare vSphere Data Protection 6.0.0 \n * VMWare vSphere Data Protection 6.0.5 \n * VMWare vSphere Data Protection 6.0.6 \n * VMWare vSphere Data Protection 6.0.7 \n * VMWare vSphere Data Protection 6.1 \n * VMWare vSphere Data Protection 6.1.0 \n * VMWare vSphere Data Protection 6.1.4 \n * VMWare vSphere Data Protection 6.1.5 \n * VMWare vSphere Data Protection 6.1.6 \n * VMWare vSphere Integrated Containers 1.0 \n * VMWare vSphere Integrated Containers 1.1 \n * VMWare vSphere Integrated Containers 1.2 \n * VMWare vSphere Integrated Containers 1.3 \n * Xen Xen \n\n### Recommendations\n\n**Permit local access for trusted individuals only. Where possible, use restricted environments and restricted shells.** \nGiven the local nature of this issue, grant only trusted and accountable individuals access to affected computers. \n\nUpdates are available. Please see the references or vendor advisory for more information.\n", "modified": "2018-01-03T00:00:00", "published": "2018-01-03T00:00:00", "href": "https://www.symantec.com/content/symantec/english/en/security-center/vulnerabilities/writeup.html/102371", "id": "SMNTC-102371", "type": "symantec", "title": "Multiple CPU Hardware CVE-2017-5753 Information Disclosure Vulnerability", "cvss": {"score": 4.7, "vector": "AV:LOCAL/AC:MEDIUM/Au:NONE/C:COMPLETE/I:NONE/A:NONE/"}}], "cve": [{"lastseen": "2019-07-02T16:59:33", "bulletinFamily": "NVD", "description": "Systems with microprocessors utilizing speculative execution and branch prediction may allow unauthorized disclosure of information to an attacker with local user access via a side-channel analysis.", "modified": "2019-04-23T19:30:00", "id": "CVE-2017-5753", "href": "https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5753", "published": "2018-01-04T13:29:00", "title": "CVE-2017-5753", "type": "cve", "cvss": {"score": 4.7, "vector": "AV:L/AC:M/Au:N/C:C/I:N/A:N"}}, {"lastseen": "2019-07-02T16:59:33", "bulletinFamily": "NVD", "description": "Systems with microprocessors utilizing speculative execution and indirect branch prediction may allow unauthorized disclosure of information to an attacker with local user access via a side-channel analysis of the data cache.", "modified": "2019-04-23T19:30:00", "id": "CVE-2017-5754", "href": "https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5754", "published": "2018-01-04T13:29:00", "title": "CVE-2017-5754", "type": "cve", "cvss": {"score": 4.7, "vector": "AV:L/AC:M/Au:N/C:C/I:N/A:N"}}, {"lastseen": "2019-07-24T12:04:59", "bulletinFamily": "NVD", "description": "Systems with microprocessors utilizing speculative execution and indirect branch prediction may allow unauthorized disclosure of information to an attacker with local user access via a side-channel analysis.", "modified": "2018-11-30T21:31:00", "id": "CVE-2017-5715", "href": "https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5715", "published": "2018-01-04T13:29:00", "title": "CVE-2017-5715", "type": "cve", "cvss": {"score": 4.7, "vector": "AV:L/AC:M/Au:N/C:C/I:N/A:N"}}], "nessus": [{"lastseen": "2019-02-21T01:36:47", "bulletinFamily": "scanner", "description": "According to its self-reported version number, the Xen hypervisor installed on the remote host is affected by multiple vulnerabilities.\n\nNote that Nessus has checked the changeset versions based on the xen.git change log. Nessus did not check guest hardware configurations or if patches were applied manually to the source code before a recompile and reinstall.", "modified": "2018-08-07T00:00:00", "id": "XEN_SERVER_XSA-254.NASL", "href": "https://www.tenable.com/plugins/index.php?view=single&id=106902", "published": "2018-02-20T00:00:00", "title": "Xen Multiple Vulnerabilities (Spectre) (Meltdown) (XSA-254)", "type": "nessus", "sourceData": "#\n# (C) Tenable Network Security, Inc.\n#\n\ninclude(\"compat.inc\");\n\nif (description)\n{\n script_id(106902);\n script_version(\"1.5\");\n script_cvs_date(\"Date: 2018/08/07 16:46:51\");\n\n script_cve_id(\n \"CVE-2017-5715\",\n \"CVE-2017-5753\",\n \"CVE-2017-5754\"\n );\n script_bugtraq_id(\n 102371,\n 102376,\n 102378\n );\n script_xref(name:\"IAVA\", value:\"2018-A-0019\");\n script_xref(name:\"IAVA\", value:\"2018-A-0020\");\n\n script_name(english:\"Xen Multiple Vulnerabilities (Spectre) (Meltdown) (XSA-254)\");\n script_summary(english:\"Checks 'xl info' output for the Xen hypervisor version.\");\n\n script_set_attribute(attribute:\"synopsis\", value:\n\"The remote Xen hypervisor installation is missing a security update.\");\n script_set_attribute(attribute:\"description\", value:\n\"According to its self-reported version number, the Xen hypervisor\ninstalled on the remote host is affected by multiple vulnerabilities.\n\nNote that Nessus has checked the changeset versions based on the\nxen.git change log. Nessus did not check guest hardware configurations\nor if patches were applied manually to the source code before a\nrecompile and reinstall.\");\n script_set_attribute(attribute:\"see_also\", value:\"http://xenbits.xen.org/xsa/advisory-254.html\");\n script_set_attribute(attribute:\"see_also\", value:\"https://xenbits.xen.org/gitweb/?p=xen.git;a=summary\");\n script_set_attribute(attribute:\"solution\", value:\n\"Apply the appropriate patch according to the vendor advisory.\");\n script_set_cvss_base_vector(\"CVSS2#AV:L/AC:M/Au:N/C:C/I:N/A:N\");\n script_set_cvss_temporal_vector(\"CVSS2#E:H/RL:OF/RC:C\");\n script_set_cvss3_base_vector(\"CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N\");\n script_set_cvss3_temporal_vector(\"CVSS:3.0/E:H/RL:O/RC:C\");\n script_set_attribute(attribute:\"exploitability_ease\", value:\"Exploits are available\");\n script_set_attribute(attribute:\"exploit_available\", value:\"true\");\n script_set_attribute(attribute:\"exploited_by_malware\", value:\"true\");\n script_set_attribute(attribute:\"exploit_framework_canvas\", value:\"true\");\n script_set_attribute(attribute:\"canvas_package\", value:'CANVAS');\n\n script_set_attribute(attribute:\"vuln_publication_date\", value:\"2018/01/02\");\n script_set_attribute(attribute:\"patch_publication_date\", value:\"2018/02/14\");\n script_set_attribute(attribute:\"plugin_publication_date\", value:\"2018/02/20\");\n\n script_set_attribute(attribute:\"plugin_type\", value:\"local\");\n script_set_attribute(attribute:\"cpe\", value:\"cpe:/o:xen:xen\");\n script_set_attribute(attribute:\"potential_vulnerability\", value:\"true\");\n script_set_attribute(attribute:\"stig_severity\", value:\"I\");\n script_end_attributes();\n\n script_category(ACT_GATHER_INFO);\n script_family(english:\"Misc.\");\n\n script_copyright(english:\"This script is Copyright (C) 2018 Tenable Network Security, Inc.\");\n\n script_dependencies(\"xen_server_detect.nbin\");\n script_require_keys(\"installed_sw/Xen Hypervisor\", \"Settings/ParanoidReport\");\n\n exit(0);\n}\n\ninclude(\"audit.inc\");\ninclude(\"global_settings.inc\");\ninclude(\"install_func.inc\");\ninclude(\"misc_func.inc\");\n\napp_name = \"Xen Hypervisor\";\ninstall = get_single_install(app_name:app_name);\nif (report_paranoia < 2) audit(AUDIT_PARANOID);\n\nversion = install['version'];\ndisplay_version = install['display_version'];\npath = install['path'];\nmanaged_status = install['Managed status'];\nchangeset = install['Changeset'];\n\nif (!empty_or_null(changeset))\n display_version += \" (changeset \" + changeset + \")\";\n\n# Installations that are vendor-managed are handled by OS-specific local package checks\nif (managed_status == \"managed\")\n audit(AUDIT_INST_PATH_NOT_VULN, app_name, display_version, path);\n\nfixes['4.6']['fixed_ver'] = '4.6.6';\nfixes['4.6']['fixed_ver_display'] = '4.6.6 (changeset 4d21549)';\nfixes['4.6']['affected_ver_regex'] = '^4\\\\.6\\\\.';\nfixes['4.6']['affected_changesets'] = make_list(\"ff4800c\", \"2613a1b\",\n \"8335c8a\", \"ab20c5c\", \"9089da9\", \"8edfc82\", \"af5b61a\", \"ec05090\",\n \"75263f7\", \"f7e273a\", \"03c7d2c\", \"9ce1a71\", \"a735c7a\", \"44ad7f6\",\n \"91dc902\", \"a065841\", \"c6e9e60\", \"f94c11d\", \"45ddc4e\", \"1ca93b7\",\n \"8c0c36e\", \"6e43623\", \"47d3e73\", \"ea80245\", \"37bb22b\", \"9b0c2a2\",\n \"8d3fe28\", \"be63d66\", \"9454e30\", \"aad5a67\", \"d8b0ebf\", \"f0208a4\",\n \"42b2c82\", \"57318e1\", \"9f22d72\", \"e0353b4\", \"76f1549\", \"9bac910\",\n \"c7a43e3\", \"913d4f8\", \"c5881c5\", \"b0239cd\", \"78fd0c3\", \"9079e0d\",\n \"1658a87\", \"22b6dfa\", \"a8cd231\", \"629eddd\", \"64c03bb\", \"b4660b4\",\n \"1ac8162\", \"747df3c\", \"5ae011e\", \"f974d32\", \"3300ad3\", \"d708b69\");\n\nfixes['4.7']['fixed_ver'] = '4.7.5';\nfixes['4.7']['fixed_ver_display'] = '4.7.5-pre (changeset e9220b4)';\nfixes['4.7']['affected_ver_regex'] = '^4\\\\.7\\\\.';\nfixes['4.7']['affected_changesets'] = make_list(\"f961688\", \"91f7e46\",\n \"f291c01\", \"3cf4e29\", \"8860219\", \"62a2624\", \"c3f8df3\", \"3877c02\",\n \"f0ed5f9\", \"160b53c\", \"e131309\", \"9ede1ac\", \"d0cfbe8\", \"d596e6a\",\n \"f50ea84\", \"de3bdaa\", \"766990b\", \"4ac0229\", \"bafd63f\", \"d5bb425\",\n \"003ec3e\", \"fd884d6\", \"50c68df\", \"1bdcc9f\", \"2914ef5\", \"62b9706\",\n \"624abdc\", \"d7b73ed\", \"112c49c\", \"a5b0fa4\", \"e19d0af\", \"e19517a\",\n \"9b76908\", \"46025e3\", \"0e6c6fc\", \"40c4410\", \"f3b76b6\", \"4c937e2\",\n \"2307798\", \"7089465\", \"375896d\", \"99474d1\", \"f407332\", \"1c58d74\",\n \"d02140f\", \"fae9dd5\", \"caae052\", \"c90b5c1\", \"5b1c9fe\", \"2e6775e\",\n \"f2d19fb\", \"0baeec6\", \"664433a\", \"b3dfadc\", \"8f14027\", \"1967ced\",\n \"c3ddeca\", \"b9c150e\", \"5a99156\", \"4f34d9f\", \"4133de7\", \"b3981ea\",\n \"184f259\", \"67966a9\", \"af3f585\");\n\nfixes['4.8']['fixed_ver'] = '4.8.4';\nfixes['4.8']['fixed_ver_display'] = '4.8.4-pre (changeset 532ccf4)';\nfixes['4.8']['affected_ver_regex'] = '^4\\\\.8\\\\.';\nfixes['4.8']['affected_changesets'] = make_list(\"da49e51\", \"ca9583d\",\n \"479b879\", \"2eefd92\", \"60c50f2\", \"1838e21\", \"5732a8e\", \"987b08d\",\n \"eadcd83\", \"ef2464c\", \"17bfbc8\", \"499391b\", \"87cb0e2\", \"393de92\");\n\nfixes['4.9']['fixed_ver'] = '4.9.2';\nfixes['4.9']['fixed_ver_display'] = '4.9.2-pre (changeset 7648049)';\nfixes['4.9']['affected_ver_regex'] = '^4\\\\.9\\\\.';\nfixes['4.9']['affected_changesets'] = make_list(\"602633e\", \"6fef46d\",\n \"30b9929\", \"447dce8\", \"29df8a5\", \"6403b50\", \"628b6af\", \"237a58b\",\n \"f0f7ce5\", \"d6e9725\", \"9aaa208\", \"40f9ae9\", \"ade9554\", \"a0ed034\",\n \"4d01dbc\", \"22379b6\", \"6e13ad7\", \"0d32237\", \"4ba59bd\", \"2997c5e\",\n \"751c879\", \"a2567d6\", \"9f79e8d\", \"fba48ef\", \"3790833\", \"50450c1\",\n \"2ec7ccb\", \"dc7d465\", \"1e09746\", \"87ea781\", \"96990e2\", \"2213ffe\",\n \"c3774d1\", \"f559d50\", \"f877aab\", \"0c3d524\", \"4d190d7\", \"a4a4abf\",\n \"432f715\", \"389df4f\", \"d6fe186\", \"6a39a56\", \"d9ade82\", \"c09e166\",\n \"df6db6c\", \"986fcb8\", \"da8c866\", \"47a7e3b\", \"57205c4\", \"09d7c30\",\n \"8edff60\", \"fe1147d\", \"78c61ba\", \"c9afe26\", \"4bd6306\", \"a20f838\",\n \"984bb18\", \"1b0029c\", \"32e364c\", \"d3db9e3\", \"c553285\", \"6260c47\",\n \"d1cca07\", \"0a0dcdc\", \"fb51cab\", \"61c13ed\", \"52ad651\");\n\nfixes['4.10']['fixed_ver'] = '4.10.1';\nfixes['4.10']['fixed_ver_display'] = '4.10.1-pre (changeset 65ee6e0)';\nfixes['4.10']['affected_ver_regex'] = '^4\\\\.10\\\\.';\nfixes['4.10']['affected_changesets'] = make_list(\"129880d\", \"c513244\",\n \"0e12c2c\", \"6aaf353\", \"32babfc\", \"47bbcb2\", \"8743fc2\", \"1830b20\",\n \"ab95cb0\", \"d02ef3d\", \"e32f814\", \"c534ab4\", \"be3138b\", \"79012ea\",\n \"bbd093c\", \"a69a8b5\", \"f167ebf\", \"c4c0187\", \"19ad8a7\", \"3caf32c\",\n \"df7be94\", \"f379b70\", \"728fadb\", \"9281129\", \"cae6e15\", \"d1f4283\",\n \"0f7a4fa\", \"b829d42\", \"7cccd6f\", \"234f481\", \"57dc197\", \"7209b8b\",\n \"910dd00\", \"50d24b9\", \"c89c622\", \"3b8d88d\", \"cdb1fb4\", \"a401864\",\n \"a87ec48\", \"9dc5eda\", \"135b67e\", \"682a9d8\", \"19dcd8e\", \"e5364c3\",\n \"e2dc7b5\", \"c8f4f45\", \"4150501\", \"ab7be6c\", \"f3fb667\");\n\nfix = NULL;\nforeach ver_branch (keys(fixes))\n{\n if (version =~ fixes[ver_branch]['affected_ver_regex'])\n {\n ret = ver_compare(ver:version, fix:fixes[ver_branch]['fixed_ver']);\n if (ret < 0)\n fix = fixes[ver_branch]['fixed_ver_display'];\n else if (ret == 0)\n {\n if (empty_or_null(changeset))\n fix = fixes[ver_branch]['fixed_ver_display'];\n else\n foreach affected_changeset (fixes[ver_branch]['affected_changesets'])\n if (changeset == affected_changeset)\n fix = fixes[ver_branch]['fixed_ver_display'];\n }\n }\n}\n\nif (empty_or_null(fix))\n audit(AUDIT_INST_PATH_NOT_VULN, app_name, display_version, path);\n\nitems = make_array(\n \"Installed version\", display_version,\n \"Fixed version\", fix,\n \"Path\", path\n);\n\norder = make_list(\"Path\", \"Installed version\", \"Fixed version\");\nreport = report_items_str(report_items:items, ordered_fields:order) + '\\n';\n\nsecurity_report_v4(port:0, extra:report, severity:SECURITY_WARNING);\n", "cvss": {"score": 4.7, "vector": "AV:LOCAL/AC:MEDIUM/Au:NONE/C:COMPLETE/I:NONE/A:NONE/"}}, {"lastseen": "2019-02-21T01:35:16", "bulletinFamily": "scanner", "description": "It was discovered that speculative execution performed by modern CPUs could leak information through a timing side-channel attack, and that this could be exploited in web browser JavaScript engines. If a user were tricked in to opening a specially crafted website, an attacker could potentially exploit this to obtain sensitive information from other domains, bypassing same-origin restrictions. (CVE-2017-5715, CVE-2017-5753, CVE-2017-5754).\n\nNote that Tenable Network Security has extracted the preceding description block directly from the Ubuntu security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.", "modified": "2018-12-01T00:00:00", "id": "UBUNTU_USN-3516-1.NASL", "href": "https://www.tenable.com/plugins/index.php?view=single&id=105649", "published": "2018-01-08T00:00:00", "title": "Ubuntu 14.04 LTS / 16.04 LTS / 17.04 / 17.10 : firefox vulnerabilities (USN-3516-1) (Meltdown) (Spectre)", "type": "nessus", "sourceData": "#\n# (C) Tenable Network Security, Inc.\n#\n# The descriptive text and package checks in this plugin were\n# extracted from Ubuntu Security Notice USN-3516-1. The text \n# itself is copyright (C) Canonical, Inc. See \n# <http://www.ubuntu.com/usn/>. Ubuntu(R) is a registered \n# trademark of Canonical, Inc.\n#\n\ninclude(\"compat.inc\");\n\nif (description)\n{\n script_id(105649);\n script_version(\"3.10\");\n script_cvs_date(\"Date: 2018/12/01 15:12:41\");\n\n script_cve_id(\"CVE-2017-5715\", \"CVE-2017-5753\", \"CVE-2017-5754\");\n script_xref(name:\"USN\", value:\"3516-1\");\n script_xref(name:\"IAVA\", value:\"2018-A-0019\");\n script_xref(name:\"IAVA\", value:\"2018-A-0020\");\n\n script_name(english:\"Ubuntu 14.04 LTS / 16.04 LTS / 17.04 / 17.10 : firefox vulnerabilities (USN-3516-1) (Meltdown) (Spectre)\");\n script_summary(english:\"Checks dpkg output for updated package.\");\n\n script_set_attribute(\n attribute:\"synopsis\", \n value:\"The remote Ubuntu host is missing a security-related patch.\"\n );\n script_set_attribute(\n attribute:\"description\", \n value:\n\"It was discovered that speculative execution performed by modern CPUs\ncould leak information through a timing side-channel attack, and that\nthis could be exploited in web browser JavaScript engines. If a user\nwere tricked in to opening a specially crafted website, an attacker\ncould potentially exploit this to obtain sensitive information from\nother domains, bypassing same-origin restrictions. (CVE-2017-5715,\nCVE-2017-5753, CVE-2017-5754).\n\nNote that Tenable Network Security has extracted the preceding\ndescription block directly from the Ubuntu security advisory. Tenable\nhas attempted to automatically clean and format it as much as possible\nwithout introducing additional issues.\"\n );\n script_set_attribute(\n attribute:\"see_also\",\n value:\"https://usn.ubuntu.com/3516-1/\"\n );\n script_set_attribute(\n attribute:\"solution\", \n value:\"Update the affected firefox package.\"\n );\n script_set_cvss_base_vector(\"CVSS2#AV:L/AC:M/Au:N/C:C/I:N/A:N\");\n script_set_cvss_temporal_vector(\"CVSS2#E:H/RL:OF/RC:C\");\n script_set_cvss3_base_vector(\"CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N\");\n script_set_cvss3_temporal_vector(\"CVSS:3.0/E:H/RL:O/RC:C\");\n script_set_attribute(attribute:\"exploitability_ease\", value:\"Exploits are available\");\n script_set_attribute(attribute:\"exploit_available\", value:\"true\");\n script_set_attribute(attribute:\"exploited_by_malware\", value:\"true\");\n script_set_attribute(attribute:\"exploit_framework_canvas\", value:\"true\");\n script_set_attribute(attribute:\"canvas_package\", value:'CANVAS');\n\n script_set_attribute(attribute:\"plugin_type\", value:\"local\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:canonical:ubuntu_linux:firefox\");\n script_set_attribute(attribute:\"cpe\", value:\"cpe:/o:canonical:ubuntu_linux:14.04\");\n script_set_attribute(attribute:\"cpe\", value:\"cpe:/o:canonical:ubuntu_linux:16.04\");\n script_set_attribute(attribute:\"cpe\", value:\"cpe:/o:canonical:ubuntu_linux:17.04\");\n script_set_attribute(attribute:\"cpe\", value:\"cpe:/o:canonical:ubuntu_linux:17.10\");\n\n script_set_attribute(attribute:\"patch_publication_date\", value:\"2018/01/05\");\n script_set_attribute(attribute:\"in_the_news\", value:\"true\");\n script_set_attribute(attribute:\"plugin_publication_date\", value:\"2018/01/08\");\n script_set_attribute(attribute:\"stig_severity\", value:\"I\");\n script_end_attributes();\n\n script_category(ACT_GATHER_INFO);\n script_copyright(english:\"Ubuntu Security Notice (C) 2018 Canonical, Inc. / NASL script (C) 2018 and is owned by Tenable, Inc. or an Affiliate thereof.\");\n script_family(english:\"Ubuntu Local Security Checks\");\n\n script_dependencies(\"ssh_get_info.nasl\");\n script_require_keys(\"Host/cpu\", \"Host/Ubuntu\", \"Host/Ubuntu/release\", \"Host/Debian/dpkg-l\");\n\n exit(0);\n}\n\n\ninclude(\"audit.inc\");\ninclude(\"ubuntu.inc\");\ninclude(\"misc_func.inc\");\n\nif ( ! get_kb_item(\"Host/local_checks_enabled\") ) audit(AUDIT_LOCAL_CHECKS_NOT_ENABLED);\nrelease = get_kb_item(\"Host/Ubuntu/release\");\nif ( isnull(release) ) audit(AUDIT_OS_NOT, \"Ubuntu\");\nrelease = chomp(release);\nif (! ereg(pattern:\"^(14\\.04|16\\.04|17\\.04|17\\.10)$\", string:release)) audit(AUDIT_OS_NOT, \"Ubuntu 14.04 / 16.04 / 17.04 / 17.10\", \"Ubuntu \" + release);\nif ( ! get_kb_item(\"Host/Debian/dpkg-l\") ) audit(AUDIT_PACKAGE_LIST_MISSING);\n\ncpu = get_kb_item(\"Host/cpu\");\nif (isnull(cpu)) audit(AUDIT_UNKNOWN_ARCH);\nif (\"x86_64\" >!< cpu && cpu !~ \"^i[3-6]86$\") audit(AUDIT_LOCAL_CHECKS_NOT_IMPLEMENTED, \"Ubuntu\", cpu);\n\nflag = 0;\n\nif (ubuntu_check(osver:\"14.04\", pkgname:\"firefox\", pkgver:\"57.0.4+build1-0ubuntu0.14.04.1\")) flag++;\nif (ubuntu_check(osver:\"16.04\", pkgname:\"firefox\", pkgver:\"57.0.4+build1-0ubuntu0.16.04.1\")) flag++;\nif (ubuntu_check(osver:\"17.04\", pkgname:\"firefox\", pkgver:\"57.0.4+build1-0ubuntu0.17.04.1\")) flag++;\nif (ubuntu_check(osver:\"17.10\", pkgname:\"firefox\", pkgver:\"57.0.4+build1-0ubuntu0.17.10.1\")) flag++;\n\nif (flag)\n{\n security_report_v4(\n port : 0,\n severity : SECURITY_WARNING,\n extra : ubuntu_report_get()\n );\n exit(0);\n}\nelse\n{\n tested = ubuntu_pkg_tests_get();\n if (tested) audit(AUDIT_PACKAGE_NOT_AFFECTED, tested);\n else audit(AUDIT_PACKAGE_NOT_INSTALLED, \"firefox\");\n}\n", "cvss": {"score": 4.7, "vector": "AV:LOCAL/AC:MEDIUM/Au:NONE/C:COMPLETE/I:NONE/A:NONE/"}}, {"lastseen": "2019-02-21T01:34:51", "bulletinFamily": "scanner", "description": "An update for kernel is now available for Red Hat Enterprise Linux 6.6 Advanced Update Support and Red Hat Enterprise Linux 6.6 Telco Extended Update Support.\n\nRed Hat Product Security has rated this update as having a security impact of Important. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) in the References section.\n\nThe kernel packages contain the Linux kernel, the core of any Linux operating system.\n\nSecurity Fix(es) :\n\nAn industry-wide issue was found in the way many modern microprocessor designs have implemented speculative execution of instructions (a commonly used performance optimization). There are three primary variants of the issue which differ in the way the speculative execution can be exploited.\n\nNote: This issue is present in hardware and cannot be fully fixed via software update. The updated kernel packages provide software mitigation for this hardware issue at a cost of potential performance penalty. Please refer to References section for further information about this issue and the performance impact.\n\nIn this update mitigations for x86-64 architecture are provided.\n\nVariant CVE-2017-5753 triggers the speculative execution by performing a bounds-check bypass. It relies on the presence of a precisely-defined instruction sequence in the privileged code as well as the fact that memory accesses may cause allocation into the microprocessor's data cache even for speculatively executed instructions that never actually commit (retire). As a result, an unprivileged attacker could use this flaw to cross the syscall boundary and read privileged memory by conducting targeted cache side-channel attacks. (CVE-2017-5753, Important)\n\nVariant CVE-2017-5715 triggers the speculative execution by utilizing branch target injection. It relies on the presence of a precisely-defined instruction sequence in the privileged code as well as the fact that memory accesses may cause allocation into the microprocessor's data cache even for speculatively executed instructions that never actually commit (retire). As a result, an unprivileged attacker could use this flaw to cross the syscall and guest/host boundaries and read privileged memory by conducting targeted cache side-channel attacks. (CVE-2017-5715, Important)\n\nVariant CVE-2017-5754 relies on the fact that, on impacted microprocessors, during speculative execution of instruction permission faults, exception generation triggered by a faulting access is suppressed until the retirement of the whole instruction block. In a combination with the fact that memory accesses may populate the cache even when the block is being dropped and never committed (executed), an unprivileged local attacker could use this flaw to read privileged (kernel space) memory by conducting targeted cache side-channel attacks. (CVE-2017-5754, Important)\n\nNote: CVE-2017-5754 affects Intel x86-64 microprocessors. AMD x86-64 microprocessors are not affected by this issue.\n\nRed Hat would like to thank Google Project Zero for reporting these issues.", "modified": "2018-11-26T00:00:00", "id": "REDHAT-RHSA-2018-0017.NASL", "href": "https://www.tenable.com/plugins/index.php?view=single&id=105533", "published": "2018-01-04T00:00:00", "title": "RHEL 6 : kernel (RHSA-2018:0017) (Meltdown) (Spectre)", "type": "nessus", "sourceData": "#\n# (C) Tenable Network Security, Inc.\n#\n# The descriptive text and package checks in this plugin were \n# extracted from Red Hat Security Advisory RHSA-2018:0017. The text \n# itself is copyright (C) Red Hat, Inc.\n#\n\ninclude(\"compat.inc\");\n\nif (description)\n{\n script_id(105533);\n script_version(\"3.13\");\n script_cvs_date(\"Date: 2018/11/26 11:02:16\");\n\n script_cve_id(\"CVE-2017-5715\", \"CVE-2017-5753\", \"CVE-2017-5754\");\n script_xref(name:\"RHSA\", value:\"2018:0017\");\n script_xref(name:\"IAVA\", value:\"2018-A-0017\");\n script_xref(name:\"IAVA\", value:\"2018-A-0019\");\n script_xref(name:\"IAVA\", value:\"2018-A-0020\");\n\n script_name(english:\"RHEL 6 : kernel (RHSA-2018:0017) (Meltdown) (Spectre)\");\n script_summary(english:\"Checks the rpm output for the updated packages\");\n\n script_set_attribute(\n attribute:\"synopsis\", \n value:\"The remote Red Hat host is missing one or more security updates.\"\n );\n script_set_attribute(\n attribute:\"description\", \n value:\n\"An update for kernel is now available for Red Hat Enterprise Linux 6.6\nAdvanced Update Support and Red Hat Enterprise Linux 6.6 Telco\nExtended Update Support.\n\nRed Hat Product Security has rated this update as having a security\nimpact of Important. A Common Vulnerability Scoring System (CVSS) base\nscore, which gives a detailed severity rating, is available for each\nvulnerability from the CVE link(s) in the References section.\n\nThe kernel packages contain the Linux kernel, the core of any Linux\noperating system.\n\nSecurity Fix(es) :\n\nAn industry-wide issue was found in the way many modern microprocessor\ndesigns have implemented speculative execution of instructions (a\ncommonly used performance optimization). There are three primary\nvariants of the issue which differ in the way the speculative\nexecution can be exploited.\n\nNote: This issue is present in hardware and cannot be fully fixed via\nsoftware update. The updated kernel packages provide software\nmitigation for this hardware issue at a cost of potential performance\npenalty. Please refer to References section for further information\nabout this issue and the performance impact.\n\nIn this update mitigations for x86-64 architecture are provided.\n\nVariant CVE-2017-5753 triggers the speculative execution by performing\na bounds-check bypass. It relies on the presence of a\nprecisely-defined instruction sequence in the privileged code as well\nas the fact that memory accesses may cause allocation into the\nmicroprocessor's data cache even for speculatively executed\ninstructions that never actually commit (retire). As a result, an\nunprivileged attacker could use this flaw to cross the syscall\nboundary and read privileged memory by conducting targeted cache\nside-channel attacks. (CVE-2017-5753, Important)\n\nVariant CVE-2017-5715 triggers the speculative execution by utilizing\nbranch target injection. It relies on the presence of a\nprecisely-defined instruction sequence in the privileged code as well\nas the fact that memory accesses may cause allocation into the\nmicroprocessor's data cache even for speculatively executed\ninstructions that never actually commit (retire). As a result, an\nunprivileged attacker could use this flaw to cross the syscall and\nguest/host boundaries and read privileged memory by conducting\ntargeted cache side-channel attacks. (CVE-2017-5715, Important)\n\nVariant CVE-2017-5754 relies on the fact that, on impacted\nmicroprocessors, during speculative execution of instruction\npermission faults, exception generation triggered by a faulting access\nis suppressed until the retirement of the whole instruction block. In\na combination with the fact that memory accesses may populate the\ncache even when the block is being dropped and never committed\n(executed), an unprivileged local attacker could use this flaw to read\nprivileged (kernel space) memory by conducting targeted cache\nside-channel attacks. (CVE-2017-5754, Important)\n\nNote: CVE-2017-5754 affects Intel x86-64 microprocessors. AMD x86-64\nmicroprocessors are not affected by this issue.\n\nRed Hat would like to thank Google Project Zero for reporting these\nissues.\"\n );\n # https://access.redhat.com/security/vulnerabilities/speculativeexecution\n script_set_attribute(\n attribute:\"see_also\",\n value:\"http://www.nessus.org/u?892ef523\"\n );\n script_set_attribute(\n attribute:\"see_also\",\n value:\"https://access.redhat.com/security/cve/cve-2017-5753\"\n );\n script_set_attribute(\n attribute:\"see_also\",\n value:\"https://access.redhat.com/security/cve/cve-2017-5715\"\n );\n script_set_attribute(\n attribute:\"see_also\",\n value:\"https://access.redhat.com/security/cve/cve-2017-5754\"\n );\n script_set_attribute(\n attribute:\"see_also\",\n value:\"https://access.redhat.com/errata/RHSA-2018:0017\"\n );\n script_set_attribute(attribute:\"solution\", value:\"Update the affected packages.\");\n script_set_cvss_base_vector(\"CVSS2#AV:L/AC:M/Au:N/C:C/I:N/A:N\");\n script_set_cvss_temporal_vector(\"CVSS2#E:H/RL:OF/RC:C\");\n script_set_cvss3_base_vector(\"CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N\");\n script_set_cvss3_temporal_vector(\"CVSS:3.0/E:H/RL:O/RC:C\");\n script_set_attribute(attribute:\"exploitability_ease\", value:\"Exploits are available\");\n script_set_attribute(attribute:\"exploit_available\", value:\"true\");\n script_set_attribute(attribute:\"exploited_by_malware\", value:\"true\");\n script_set_attribute(attribute:\"exploit_framework_canvas\", value:\"true\");\n script_set_attribute(attribute:\"canvas_package\", value:'CANVAS');\n\n script_set_attribute(attribute:\"plugin_type\", value:\"local\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:redhat:enterprise_linux:kernel\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:redhat:enterprise_linux:kernel-abi-whitelists\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:redhat:enterprise_linux:kernel-debug\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:redhat:enterprise_linux:kernel-debug-debuginfo\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:redhat:enterprise_linux:kernel-debug-devel\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:redhat:enterprise_linux:kernel-debuginfo\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:redhat:enterprise_linux:kernel-debuginfo-common-x86_64\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:redhat:enterprise_linux:kernel-devel\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:redhat:enterprise_linux:kernel-doc\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:redhat:enterprise_linux:kernel-firmware\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:redhat:enterprise_linux:kernel-headers\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:redhat:enterprise_linux:perf\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:redhat:enterprise_linux:perf-debuginfo\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:redhat:enterprise_linux:python-perf\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:redhat:enterprise_linux:python-perf-debuginfo\");\n script_set_attribute(attribute:\"cpe\", value:\"cpe:/o:redhat:enterprise_linux:6.6\");\n\n script_set_attribute(attribute:\"patch_publication_date\", value:\"2018/01/04\");\n script_set_attribute(attribute:\"in_the_news\", value:\"true\");\n script_set_attribute(attribute:\"plugin_publication_date\", value:\"2018/01/04\");\n script_set_attribute(attribute:\"stig_severity\", value:\"I\");\n script_end_attributes();\n\n script_category(ACT_GATHER_INFO);\n script_copyright(english:\"This script is Copyright (C) 2018 and is owned by Tenable, Inc. or an Affiliate thereof.\");\n script_family(english:\"Red Hat Local Security Checks\");\n\n script_dependencies(\"ssh_get_info.nasl\");\n script_require_keys(\"Host/local_checks_enabled\", \"Host/RedHat/release\", \"Host/RedHat/rpm-list\", \"Host/cpu\");\n\n exit(0);\n}\n\n\ninclude(\"audit.inc\");\ninclude(\"global_settings.inc\");\ninclude(\"misc_func.inc\");\ninclude(\"rpm.inc\");\n\nif (!get_kb_item(\"Host/local_checks_enabled\")) audit(AUDIT_LOCAL_CHECKS_NOT_ENABLED);\nrelease = get_kb_item(\"Host/RedHat/release\");\nif (isnull(release) || \"Red Hat\" >!< release) audit(AUDIT_OS_NOT, \"Red Hat\");\nos_ver = eregmatch(pattern: \"Red Hat Enterprise Linux.*release ([0-9]+(\\.[0-9]+)?)\", string:release);\nif (isnull(os_ver)) audit(AUDIT_UNKNOWN_APP_VER, \"Red Hat\");\nos_ver = os_ver[1];\nif (! ereg(pattern:\"^6\\.6([^0-9]|$)\", string:os_ver)) audit(AUDIT_OS_NOT, \"Red Hat 6.6\", \"Red Hat \" + os_ver);\n\nif (!get_kb_item(\"Host/RedHat/rpm-list\")) audit(AUDIT_PACKAGE_LIST_MISSING);\n\ncpu = get_kb_item(\"Host/cpu\");\nif (isnull(cpu)) audit(AUDIT_UNKNOWN_ARCH);\nif (\"x86_64\" >!< cpu && cpu !~ \"^i[3-6]86$\" && \"s390\" >!< cpu) audit(AUDIT_LOCAL_CHECKS_NOT_IMPLEMENTED, \"Red Hat\", cpu);\n\nyum_updateinfo = get_kb_item(\"Host/RedHat/yum-updateinfo\");\nif (!empty_or_null(yum_updateinfo)) \n{\n rhsa = \"RHSA-2018:0017\";\n yum_report = redhat_generate_yum_updateinfo_report(rhsa:rhsa);\n if (!empty_or_null(yum_report))\n {\n security_report_v4(\n port : 0,\n severity : SECURITY_WARNING,\n extra : yum_report \n );\n exit(0);\n }\n else\n {\n audit_message = \"affected by Red Hat security advisory \" + rhsa;\n audit(AUDIT_OS_NOT, audit_message);\n }\n}\nelse\n{\n flag = 0;\n if (rpm_check(release:\"RHEL6\", sp:\"6\", cpu:\"x86_64\", reference:\"kernel-2.6.32-504.64.4.el6\")) flag++;\n if (rpm_check(release:\"RHEL6\", sp:\"6\", reference:\"kernel-abi-whitelists-2.6.32-504.64.4.el6\")) flag++;\n if (rpm_check(release:\"RHEL6\", sp:\"6\", cpu:\"x86_64\", reference:\"kernel-debug-2.6.32-504.64.4.el6\")) flag++;\n if (rpm_check(release:\"RHEL6\", sp:\"6\", cpu:\"x86_64\", reference:\"kernel-debug-debuginfo-2.6.32-504.64.4.el6\")) flag++;\n if (rpm_check(release:\"RHEL6\", sp:\"6\", cpu:\"x86_64\", reference:\"kernel-debug-devel-2.6.32-504.64.4.el6\")) flag++;\n if (rpm_check(release:\"RHEL6\", sp:\"6\", cpu:\"x86_64\", reference:\"kernel-debuginfo-2.6.32-504.64.4.el6\")) flag++;\n if (rpm_check(release:\"RHEL6\", sp:\"6\", cpu:\"x86_64\", reference:\"kernel-debuginfo-common-x86_64-2.6.32-504.64.4.el6\")) flag++;\n if (rpm_check(release:\"RHEL6\", sp:\"6\", cpu:\"x86_64\", reference:\"kernel-devel-2.6.32-504.64.4.el6\")) flag++;\n if (rpm_check(release:\"RHEL6\", sp:\"6\", reference:\"kernel-doc-2.6.32-504.64.4.el6\")) flag++;\n if (rpm_check(release:\"RHEL6\", sp:\"6\", reference:\"kernel-firmware-2.6.32-504.64.4.el6\")) flag++;\n if (rpm_check(release:\"RHEL6\", sp:\"6\", cpu:\"x86_64\", reference:\"kernel-headers-2.6.32-504.64.4.el6\")) flag++;\n if (rpm_check(release:\"RHEL6\", sp:\"6\", cpu:\"x86_64\", reference:\"perf-2.6.32-504.64.4.el6\")) flag++;\n if (rpm_check(release:\"RHEL6\", sp:\"6\", cpu:\"x86_64\", reference:\"perf-debuginfo-2.6.32-504.64.4.el6\")) flag++;\n if (rpm_check(release:\"RHEL6\", sp:\"6\", cpu:\"x86_64\", reference:\"python-perf-2.6.32-504.64.4.el6\")) flag++;\n if (rpm_check(release:\"RHEL6\", sp:\"6\", cpu:\"x86_64\", reference:\"python-perf-debuginfo-2.6.32-504.64.4.el6\")) flag++;\n\n if (flag)\n {\n security_report_v4(\n port : 0,\n severity : SECURITY_WARNING,\n extra : rpm_report_get() + redhat_report_package_caveat()\n );\n exit(0);\n }\n else\n {\n tested = pkg_tests_get();\n if (tested) audit(AUDIT_PACKAGE_NOT_AFFECTED, tested);\n else audit(AUDIT_PACKAGE_NOT_INSTALLED, \"kernel / kernel-abi-whitelists / kernel-debug / etc\");\n }\n}\n", "cvss": {"score": 4.7, "vector": "AV:LOCAL/AC:MEDIUM/Au:NONE/C:COMPLETE/I:NONE/A:NONE/"}}, {"lastseen": "2019-02-21T01:34:50", "bulletinFamily": "scanner", "description": "An update for kernel is now available for Red Hat Enterprise Linux 6.7 Extended Update Support.\n\nRed Hat Product Security has rated this update as having a security impact of Important. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) in the References section.\n\n[Updated 23rd January 2019] The text has been updated to correct the list of architectures addressed by the CVE-2017-5753 mitigation. No changes have been made to the packages.\n\nThe kernel packages contain the Linux kernel, the core of any Linux operating system.\n\nSecurity Fix(es) :\n\nAn industry-wide issue was found in the way many modern microprocessor designs have implemented speculative execution of instructions (a commonly used performance optimization). There are three primary variants of the issue which differ in the way the speculative execution can be exploited.\n\nNote: This issue is present in hardware and cannot be fully fixed via software update. The updated kernel packages provide software mitigation for this hardware issue at a cost of potential performance penalty. Please refer to References section for further information about this issue and the performance impact.\n\nIn this update, mitigations for x86 (CVE-2017-5753) and x86-64 (CVE-2017-5753, CVE-2017-5715, and CVE-2017-5754) architectures are provided.\n\nVariant CVE-2017-5753 triggers the speculative execution by performing a bounds-check bypass. It relies on the presence of a precisely-defined instruction sequence in the privileged code as well as the fact that memory accesses may cause allocation into the microprocessor's data cache even for speculatively executed instructions that never actually commit (retire). As a result, an unprivileged attacker could use this flaw to cross the syscall boundary and read privileged memory by conducting targeted cache side-channel attacks. (CVE-2017-5753, Important)\n\nVariant CVE-2017-5715 triggers the speculative execution by utilizing branch target injection. It relies on the presence of a precisely-defined instruction sequence in the privileged code as well as the fact that memory accesses may cause allocation into the microprocessor's data cache even for speculatively executed instructions that never actually commit (retire). As a result, an unprivileged attacker could use this flaw to cross the syscall and guest/host boundaries and read privileged memory by conducting targeted cache side-channel attacks. (CVE-2017-5715, Important)\n\nVariant CVE-2017-5754 relies on the fact that, on impacted microprocessors, during speculative execution of instruction permission faults, exception generation triggered by a faulting access is suppressed until the retirement of the whole instruction block. In a combination with the fact that memory accesses may populate the cache even when the block is being dropped and never committed (executed), an unprivileged local attacker could use this flaw to read privileged (kernel space) memory by conducting targeted cache side-channel attacks. (CVE-2017-5754, Important)\n\nNote: CVE-2017-5754 affects Intel x86-64 microprocessors. AMD x86-64 microprocessors are not affected by this issue.\n\nRed Hat would like to thank Google Project Zero for reporting these issues.", "modified": "2019-01-30T00:00:00", "id": "REDHAT-RHSA-2018-0011.NASL", "href": "https://www.tenable.com/plugins/index.php?view=single&id=105527", "published": "2018-01-04T00:00:00", "title": "RHEL 6 : kernel (RHSA-2018:0011) (Meltdown) (Spectre)", "type": "nessus", "sourceData": "#\n# (C) Tenable Network Security, Inc.\n#\n# The descriptive text and package checks in this plugin were \n# extracted from Red Hat Security Advisory RHSA-2018:0011. The text \n# itself is copyright (C) Red Hat, Inc.\n#\n\ninclude(\"compat.inc\");\n\nif (description)\n{\n script_id(105527);\n script_version(\"3.14\");\n script_cvs_date(\"Date: 2019/01/30 9:29:41\");\n\n script_cve_id(\"CVE-2017-5715\", \"CVE-2017-5753\", \"CVE-2017-5754\");\n script_xref(name:\"RHSA\", value:\"2018:0011\");\n script_xref(name:\"IAVA\", value:\"2018-A-0017\");\n script_xref(name:\"IAVA\", value:\"2018-A-0019\");\n script_xref(name:\"IAVA\", value:\"2018-A-0020\");\n\n script_name(english:\"RHEL 6 : kernel (RHSA-2018:0011) (Meltdown) (Spectre)\");\n script_summary(english:\"Checks the rpm output for the updated packages\");\n\n script_set_attribute(\n attribute:\"synopsis\", \n value:\"The remote Red Hat host is missing one or more security updates.\"\n );\n script_set_attribute(\n attribute:\"description\", \n value:\n\"An update for kernel is now available for Red Hat Enterprise Linux 6.7\nExtended Update Support.\n\nRed Hat Product Security has rated this update as having a security\nimpact of Important. A Common Vulnerability Scoring System (CVSS) base\nscore, which gives a detailed severity rating, is available for each\nvulnerability from the CVE link(s) in the References section.\n\n[Updated 23rd January 2019] The text has been updated to correct the\nlist of architectures addressed by the CVE-2017-5753 mitigation. No\nchanges have been made to the packages.\n\nThe kernel packages contain the Linux kernel, the core of any Linux\noperating system.\n\nSecurity Fix(es) :\n\nAn industry-wide issue was found in the way many modern microprocessor\ndesigns have implemented speculative execution of instructions (a\ncommonly used performance optimization). There are three primary\nvariants of the issue which differ in the way the speculative\nexecution can be exploited.\n\nNote: This issue is present in hardware and cannot be fully fixed via\nsoftware update. The updated kernel packages provide software\nmitigation for this hardware issue at a cost of potential performance\npenalty. Please refer to References section for further information\nabout this issue and the performance impact.\n\nIn this update, mitigations for x86 (CVE-2017-5753) and x86-64\n(CVE-2017-5753, CVE-2017-5715, and CVE-2017-5754) architectures are\nprovided.\n\nVariant CVE-2017-5753 triggers the speculative execution by performing\na bounds-check bypass. It relies on the presence of a\nprecisely-defined instruction sequence in the privileged code as well\nas the fact that memory accesses may cause allocation into the\nmicroprocessor's data cache even for speculatively executed\ninstructions that never actually commit (retire). As a result, an\nunprivileged attacker could use this flaw to cross the syscall\nboundary and read privileged memory by conducting targeted cache\nside-channel attacks. (CVE-2017-5753, Important)\n\nVariant CVE-2017-5715 triggers the speculative execution by utilizing\nbranch target injection. It relies on the presence of a\nprecisely-defined instruction sequence in the privileged code as well\nas the fact that memory accesses may cause allocation into the\nmicroprocessor's data cache even for speculatively executed\ninstructions that never actually commit (retire). As a result, an\nunprivileged attacker could use this flaw to cross the syscall and\nguest/host boundaries and read privileged memory by conducting\ntargeted cache side-channel attacks. (CVE-2017-5715, Important)\n\nVariant CVE-2017-5754 relies on the fact that, on impacted\nmicroprocessors, during speculative execution of instruction\npermission faults, exception generation triggered by a faulting access\nis suppressed until the retirement of the whole instruction block. In\na combination with the fact that memory accesses may populate the\ncache even when the block is being dropped and never committed\n(executed), an unprivileged local attacker could use this flaw to read\nprivileged (kernel space) memory by conducting targeted cache\nside-channel attacks. (CVE-2017-5754, Important)\n\nNote: CVE-2017-5754 affects Intel x86-64 microprocessors. AMD x86-64\nmicroprocessors are not affected by this issue.\n\nRed Hat would like to thank Google Project Zero for reporting these\nissues.\"\n );\n # https://access.redhat.com/security/vulnerabilities/speculativeexecution\n script_set_attribute(\n attribute:\"see_also\",\n value:\"http://www.nessus.org/u?892ef523\"\n );\n script_set_attribute(\n attribute:\"see_also\",\n value:\"https://access.redhat.com/security/cve/cve-2017-5753\"\n );\n script_set_attribute(\n attribute:\"see_also\",\n value:\"https://access.redhat.com/security/cve/cve-2017-5715\"\n );\n script_set_attribute(\n attribute:\"see_also\",\n value:\"https://access.redhat.com/security/cve/cve-2017-5754\"\n );\n script_set_attribute(\n attribute:\"see_also\",\n value:\"https://access.redhat.com/errata/RHSA-2018:0011\"\n );\n script_set_attribute(attribute:\"solution\", value:\"Update the affected packages.\");\n script_set_cvss_base_vector(\"CVSS2#AV:L/AC:M/Au:N/C:C/I:N/A:N\");\n script_set_cvss_temporal_vector(\"CVSS2#E:H/RL:OF/RC:C\");\n script_set_cvss3_base_vector(\"CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N\");\n script_set_cvss3_temporal_vector(\"CVSS:3.0/E:H/RL:O/RC:C\");\n script_set_attribute(attribute:\"exploitability_ease\", value:\"Exploits are available\");\n script_set_attribute(attribute:\"exploit_available\", value:\"true\");\n script_set_attribute(attribute:\"exploited_by_malware\", value:\"true\");\n script_set_attribute(attribute:\"exploit_framework_canvas\", value:\"true\");\n script_set_attribute(attribute:\"canvas_package\", value:'CANVAS');\n\n script_set_attribute(attribute:\"plugin_type\", value:\"local\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:redhat:enterprise_linux:kernel\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:redhat:enterprise_linux:kernel-abi-whitelists\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:redhat:enterprise_linux:kernel-debug\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:redhat:enterprise_linux:kernel-debug-debuginfo\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:redhat:enterprise_linux:kernel-debug-devel\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:redhat:enterprise_linux:kernel-debuginfo\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:redhat:enterprise_linux:kernel-debuginfo-common-i686\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:redhat:enterprise_linux:kernel-debuginfo-common-s390
| Spectre| Meltdown
