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": "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": [{"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}], "viewCount": 863, "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": "vmware", "idList": ["VMSA-2018-0007"]}, {"type": "redhat", "idList": ["RHSA-2018:0512", "RHSA-2018:0018", "RHSA-2018:0010", "RHSA-2018:0092", "RHSA-2018:0007", "RHSA-2018:0020", "RHSA-2018:0090", "RHSA-2018:0089", "RHSA-2018:0091", "RHSA-2018:0496"]}, {"type": "centos", "idList": ["CESA-2018:0007", "CESA-2018:0008"]}, {"type": "nessus", "idList": ["REDHAT-RHSA-2018-0020.NASL", "ORACLELINUX_ELSA-2018-0007.NASL", "REDHAT-RHSA-2018-0044.NASL", "REDHAT-RHSA-2018-0292.NASL", "XEN_SERVER_XSA-254.NASL", "AIX_IJ03034.NASL", "SL_20180103_KERNEL_ON_SL6_X.NASL", "REDHAT-RHSA-2018-0046.NASL", "UBUNTU_USN-3597-1.NASL", "SL_20180313_KERNEL_ON_SL6_X.NASL"]}, {"type": "suse", "idList": ["SUSE-SU-2018:0069-1", "SUSE-SU-2018:0113-1", "SUSE-SU-2018:0131-1"]}, {"type": "openvas", "idList": ["OPENVAS:1361412562310812295", "OPENVAS:1361412562310882822", "OPENVAS:1361412562310882855", "OPENVAS:1361412562310843474", "OPENVAS:1361412562310812740", "OPENVAS:1361412562310843423", "OPENVAS:1361412562310812296"]}, {"type": "ubuntu", "idList": ["USN-3540-1", "USN-3597-1"]}, {"type": "qualysblog", "idList": ["QUALYSBLOG:F8AA5B21D90BCDD30391A24D6FD47892", "QUALYSBLOG:BD020D07BF02B0790C62701D997BFD4D", "QUALYSBLOG:F7C32BA5E6651A8CE3584BB84A88A0C0", "QUALYSBLOG:D893D4DFB7141FDAD0BE869440074392"]}, {"type": "securelist", "idList": ["SECURELIST:7CF4DDEB1B5407DAA24EC25BAA7A9654"]}, {"type": "malwarebytes", "idList": ["MALWAREBYTES:C47D8F4321BF60FB315B6C46B47DF46F", "MALWAREBYTES:3DDE32E41BE8356C194673EE3ED7FDBE"]}, {"type": "oraclelinux", "idList": ["ELSA-2018-4012"]}, {"type": "xen", "idList": ["XSA-254"]}, {"type": "kitploit", "idList": ["KITPLOIT:8752367943592764867"]}, {"type": "lenovo", "idList": ["LENOVO:PS500151-NOSID"]}, {"type": "threatpost", "idList": ["THREATPOST:0F9EDE9A622A021B9B79C50214D7E8AD", "THREATPOST:7458AE86ECA810D873D5D35916A93D9F"]}, {"type": "talosblog", "idList": ["TALOSBLOG:6AF8BBB020A686E442B50095CA9B7A36"]}, {"type": "cloudfoundry", "idList": ["CFOUNDRY:86B5C35F8F0E334D1CCCDAF1214EDFEF"]}, {"type": "thn", "idList": ["THN:788E9312DDA39D9A09855DF379A0FD4D"]}], "modified": "2019-03-29T19:06:18"}, "vulnersScore": 7.2}, "objectVersion": "1.4", "_object_type": "robots.models.cert.CertBulletin", "_object_types": ["robots.models.cert.CertBulletin", "robots.models.base.Bulletin"]}
{"f5": [{"lastseen": "2019-04-19T02:20:56", "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) | 14.x | None | 14.0.02 | 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 \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-02-22T21:22: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:LOCAL/AC:MEDIUM/Au:NONE/C:COMPLETE/I:NONE/A:NONE/"}}], "symantec": [{"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/"}}, {"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/"}}], "cve": [{"lastseen": "2019-04-02T11:29:54", "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-01T17:29:00", "published": "2018-01-04T08:29:00", "id": "CVE-2017-5753", "href": "https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5753", "title": "CVE-2017-5753", "type": "cve", "cvss": {"score": 4.7, "vector": "AV:LOCAL/AC:MEDIUM/Au:NONE/C:COMPLETE/I:NONE/A:NONE/"}}, {"lastseen": "2018-12-01T12:03:07", "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-30T16:31:52", "published": "2018-01-04T08:29:00", "id": "CVE-2017-5715", "href": "https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5715", "title": "CVE-2017-5715", "type": "cve", "cvss": {"score": 4.7, "vector": "AV:LOCAL/AC:MEDIUM/Au:NONE/C:COMPLETE/I:NONE/A:NONE/"}}, {"lastseen": "2018-12-08T11:57:19", "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": "2018-12-07T06:29:01", "published": "2018-01-04T08:29:00", "id": "CVE-2017-5754", "href": "https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-5754", "title": "CVE-2017-5754", "type": "cve", "cvss": {"score": 4.7, "vector": "AV:LOCAL/AC:MEDIUM/Au:NONE/C:COMPLETE/I:NONE/A:NONE/"}}], "openvas": [{"lastseen": "2019-03-14T14:17:50", "bulletinFamily": "scanner", "description": "The remote host is missing an update for the ", "modified": "2019-03-13T00:00:00", "published": "2018-01-23T00:00:00", "id": "OPENVAS:1361412562310843429", "href": "http://plugins.openvas.org/nasl.php?oid=1361412562310843429", "title": "Ubuntu Update for linux-aws USN-3540-2", "type": "openvas", "sourceData": "###############################################################################\n# OpenVAS Vulnerability Test\n# $Id: gb_ubuntu_USN_3540_2.nasl 14140 2019-03-13 12:26:09Z cfischer $\n#\n# Ubuntu Update for linux-aws USN-3540-2\n#\n# Authors:\n# System Generated Check\n#\n# Copyright:\n# Copyright (C) 2018 Greenbone Networks GmbH, http://www.greenbone.net\n#\n# This program is free software; you can redistribute it and/or modify\n# it under the terms of the GNU General Public License version 2\n# (or any later version), as published by the Free Software Foundation.\n#\n# This program is distributed in the hope that it will be useful,\n# but WITHOUT ANY WARRANTY; without even the implied warranty of\n# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n# GNU General Public License for more details.\n#\n# You should have received a copy of the GNU General Public License\n# along with this program; if not, write to the Free Software\n# Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA.\n###############################################################################\n\nif(description)\n{\n script_oid(\"1.3.6.1.4.1.25623.1.0.843429\");\n script_version(\"$Revision: 14140 $\");\n script_tag(name:\"last_modification\", value:\"$Date: 2019-03-13 13:26:09 +0100 (Wed, 13 Mar 2019) $\");\n script_tag(name:\"creation_date\", value:\"2018-01-23 07:38:31 +0100 (Tue, 23 Jan 2018)\");\n script_cve_id(\"CVE-2017-5753\", \"CVE-2017-5715\", \"CVE-2017-5754\");\n script_tag(name:\"cvss_base\", value:\"4.7\");\n script_tag(name:\"cvss_base_vector\", value:\"AV:L/AC:M/Au:N/C:C/I:N/A:N\");\n script_tag(name:\"qod_type\", value:\"package\");\n script_name(\"Ubuntu Update for linux-aws USN-3540-2\");\n script_tag(name:\"summary\", value:\"The remote host is missing an update for the 'linux-aws'\n package(s) announced via the referenced advisory.\");\n script_tag(name:\"vuldetect\", value:\"Checks if a vulnerable version is present on the target host.\");\n script_tag(name:\"insight\", value:\"USN-3540-1 addressed vulnerabilities in the\n Linux kernel for Ubuntu 16.04 LTS. This update provides the corresponding\n updates for the Linux Hardware Enablement (HWE) kernel from Ubuntu 16.04 LTS for\n Ubuntu 14.04 LTS. Jann Horn discovered that microprocessors utilizing\n speculative execution and branch prediction may allow unauthorized memory reads\n via sidechannel attacks. This flaw is known as Spectre. A local attacker could\n use this to expose sensitive information, including kernel memory. This update\n provides mitigations for the i386 (CVE-2017-5753 only), amd64, ppc64el, and\n s390x architectures. (CVE-2017-5715, CVE-2017-5753) USN-3522-2 mitigated\n CVE-2017-5754 (Meltdown) for the amd64 architecture in the Linux Hardware\n Enablement (HWE) kernel from Ubuntu 16.04 LTS for Ubuntu 14.04 LTS. This update\n provides the corresponding mitigations for the ppc64el architecture. Original\n advisory details: Jann Horn discovered that microprocessors utilizing\n speculative execution and indirect branch prediction may allow unauthorized\n memory reads via sidechannel attacks. This flaw is known as Meltdown. A local\n attacker could use this to expose sensitive information, including kernel\n memory. (CVE-2017-5754)\");\n script_tag(name:\"affected\", value:\"linux-aws on Ubuntu 14.04 LTS\");\n script_tag(name:\"solution\", value:\"Please Install the Updated Packages.\");\n\n script_xref(name:\"USN\", value:\"3540-2\");\n script_xref(name:\"URL\", value:\"http://www.ubuntu.com/usn/usn-3540-2/\");\n script_tag(name:\"solution_type\", value:\"VendorFix\");\n script_category(ACT_GATHER_INFO);\n script_copyright(\"Copyright (C) 2018 Greenbone Networks GmbH\");\n script_family(\"Ubuntu Local Security Checks\");\n script_dependencies(\"gather-package-list.nasl\");\n script_mandatory_keys(\"ssh/login/ubuntu_linux\", \"ssh/login/packages\", re:\"ssh/login/release=UBUNTU14\\.04 LTS\");\n\n exit(0);\n}\n\ninclude(\"revisions-lib.inc\");\ninclude(\"pkg-lib-deb.inc\");\n\nrelease = dpkg_get_ssh_release();\nif(!release)\n exit(0);\n\nres = \"\";\n\nif(release == \"UBUNTU14.04 LTS\")\n{\n\n if ((res = isdpkgvuln(pkg:\"linux-image-4.4.0-1011-aws\", ver:\"4.4.0-1011.11\", rls:\"UBUNTU14.04 LTS\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isdpkgvuln(pkg:\"linux-image-4.4.0-111-generic\", ver:\"4.4.0-111.134~14.04.1\", rls:\"UBUNTU14.04 LTS\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isdpkgvuln(pkg:\"linux-image-4.4.0-111-lowlatency\", ver:\"4.4.0-111.134~14.04.1\", rls:\"UBUNTU14.04 LTS\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isdpkgvuln(pkg:\"linux-image-4.4.0-111-powerpc-e500mc\", ver:\"4.4.0-111.134~14.04.1\", rls:\"UBUNTU14.04 LTS\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isdpkgvuln(pkg:\"linux-image-4.4.0-111-powerpc-smp\", ver:\"4.4.0-111.134~14.04.1\", rls:\"UBUNTU14.04 LTS\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isdpkgvuln(pkg:\"linux-image-4.4.0-111-powerpc64-emb\", ver:\"4.4.0-111.134~14.04.1\", rls:\"UBUNTU14.04 LTS\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isdpkgvuln(pkg:\"linux-image-4.4.0-111-powerpc64-smp\", ver:\"4.4.0-111.134~14.04.1\", rls:\"UBUNTU14.04 LTS\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isdpkgvuln(pkg:\"linux-image-aws\", ver:\"4.4.0.1011.11\", rls:\"UBUNTU14.04 LTS\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isdpkgvuln(pkg:\"linux-image-generic-lts-xenial\", ver:\"4.4.0.111.95\", rls:\"UBUNTU14.04 LTS\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isdpkgvuln(pkg:\"linux-image-lowlatency-lts-xenial\", ver:\"4.4.0.111.95\", rls:\"UBUNTU14.04 LTS\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isdpkgvuln(pkg:\"linux-image-powerpc-e500mc-lts-xenial\", ver:\"4.4.0.111.95\", rls:\"UBUNTU14.04 LTS\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isdpkgvuln(pkg:\"linux-image-powerpc-smp-lts-xenial\", ver:\"4.4.0.111.95\", rls:\"UBUNTU14.04 LTS\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isdpkgvuln(pkg:\"linux-image-powerpc64-emb-lts-xenial\", ver:\"4.4.0.111.95\", rls:\"UBUNTU14.04 LTS\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isdpkgvuln(pkg:\"linux-image-powerpc64-smp-lts-xenial\", ver:\"4.4.0.111.95\", rls:\"UBUNTU14.04 LTS\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isdpkgvuln(pkg:\"Please\", ver:\"note that fully mitigating CVE-2017-5715 (Spectre Variant 2)\", rls:\"UBUNTU14.04 LTS\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isdpkgvuln(pkg:\"in\", ver:\"virtual environments, hypervisor updates. On i386 and amd64\", rls:\"UBUNTU14.04 LTS\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isdpkgvuln(pkg:\"kernel\", ver:\"mitigations. Ubuntu is working with Intel and AMD to provide\", rls:\"UBUNTU14.04 LTS\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isdpkgvuln(pkg:\"contact\", ver:\"the vendor to identify necessary firmware updates. Ubuntu\", rls:\"UBUNTU14.04 LTS\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isdpkgvuln(pkg:\"self-hosted\", ver:\"virtual environments in coordination with upstream QEMU.\", rls:\"UBUNTU14.04 LTS\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isdpkgvuln(pkg:\"CPU\", ver:\"features to virtual machines.\", rls:\"UBUNTU14.04 LTS\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if (__pkg_match) exit(99);\n exit(0);\n}\n", "cvss": {"score": 4.7, "vector": "AV:LOCAL/AC:MEDIUM/Au:NONE/C:COMPLETE/I:NONE/A:NONE/"}}, {"lastseen": "2018-11-23T15:06:28", "bulletinFamily": "scanner", "description": "The remote host is missing an update for the ", "modified": "2018-11-23T00:00:00", "published": "2018-01-05T00:00:00", "id": "OPENVAS:1361412562310812397", "href": "http://plugins.openvas.org/nasl.php?oid=1361412562310812397", "title": "RedHat Update for kernel RHSA-2018:0007-01", "type": "openvas", "sourceData": "###############################################################################\n# OpenVAS Vulnerability Test\n# $Id: gb_RHSA-2018_0007-01_kernel.nasl 12497 2018-11-23 08:28:21Z cfischer $\n#\n# RedHat Update for kernel RHSA-2018:0007-01\n#\n# Authors:\n# System Generated Check\n#\n# Copyright:\n# Copyright (C) 2018 Greenbone Networks GmbH, http://www.greenbone.net\n#\n# This program is free software; you can redistribute it and/or modify\n# it under the terms of the GNU General Public License version 2\n# (or any later version), as published by the Free Software Foundation.\n#\n# This program is distributed in the hope that it will be useful,\n# but WITHOUT ANY WARRANTY; without even the implied warranty of\n# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n# GNU General Public License for more details.\n#\n# You should have received a copy of the GNU General Public License\n# along with this program; if not, write to the Free Software\n# Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA.\n###############################################################################\n\nif(description)\n{\n script_oid(\"1.3.6.1.4.1.25623.1.0.812397\");\n script_version(\"$Revision: 12497 $\");\n script_tag(name:\"last_modification\", value:\"$Date: 2018-11-23 09:28:21 +0100 (Fri, 23 Nov 2018) $\");\n script_tag(name:\"creation_date\", value:\"2018-01-05 23:54:03 +0100 (Fri, 05 Jan 2018)\");\n script_cve_id(\"CVE-2017-5753\", \"CVE-2017-5715\", \"CVE-2017-5754\");\n script_tag(name:\"cvss_base\", value:\"4.7\");\n script_tag(name:\"cvss_base_vector\", value:\"AV:L/AC:M/Au:N/C:C/I:N/A:N\");\n script_tag(name:\"qod_type\", value:\"package\");\n script_name(\"RedHat Update for kernel RHSA-2018:0007-01\");\n script_tag(name:\"summary\", value:\"The remote host is missing an update for the 'kernel'\n package(s) announced via the referenced advisory.\");\n script_tag(name:\"vuldetect\", value:\"Checks if a vulnerable version is present on the target host.\");\n script_tag(name:\"insight\", value:\"The kernel packages contain the Linux\n kernel, the core of any Linux operating system. Security Fix(es): An\n industry-wide issue was found in the way many modern microprocessor designs have\n implemented speculative execution of instructions (a commonly used performance\n optimization). There are three primary variants of the issue which differ in the\n way the speculative execution can be exploited. Note: This issue is present in\n hardware and cannot be fully fixed via software update. The updated kernel\n packages provide software mitigation for this hardware issue at a cost of\n potential performance penalty. Please refer to References section for further\n information about this issue and the performance impact. In this update\n mitigations for x86-64 architecture are provided. Variant CVE-2017-5753 triggers\n the speculative execution by performing a bounds-check bypass. It relies on the\n presence of a precisely-defined instruction sequence in the privileged code as\n well as the fact that memory accesses may cause allocation into the\n microprocessor's data cache even for speculatively executed instructions that\n never actually commit (retire). As a result, an unprivileged attacker could use\n this flaw to cross the syscall boundary and read privileged memory by conducting\n targeted cache side-channel attacks. (CVE-2017-5753, Important) Variant\n CVE-2017-5715 triggers the speculative execution by utilizing branch target\n injection. It relies on the presence of a precisely-defined instruction sequence\n in the privileged code as well as the fact that memory accesses may cause\n allocation into the microprocessor's data cache even for speculatively executed\n instructions that never actually commit (retire). As a result, an unprivileged\n attacker could use this flaw to cross the syscall and guest/host boundaries and\n read privileged memory by conducting targeted cache side-channel attacks.\n (CVE-2017-5715, Important) Variant CVE-2017-5754 relies on the fact that, on\n impacted microprocessors, during speculative execution of instruction permission\n faults, exception generation triggered by a faulting access is suppressed until\n the retirement of the whole instruction block. In a combination with the fact\n that memory accesses may populate the cache even when the block is being dropped\n and never committed (executed), an unprivileged local attacker could use this\n flaw to read privileged (kernel space) memory by conducting targeted cache\n side-channel attacks. (CVE-2017-5754, Important) Note: CVE-2017-5754 affects\n Intel x86-64 microprocessors. AMD x86-64 microprocessors are not affected by\n this issue. Red Hat would like to thank Google Project Zero for reporting these\n issues.\");\n script_tag(name:\"affected\", value:\"kernel on Red Hat Enterprise Linux Server (v. 7)\");\n script_tag(name:\"solution\", value:\"Please Install the Updated Packages.\");\n\n script_xref(name:\"RHSA\", value:\"2018:0007-01\");\n script_xref(name:\"URL\", value:\"https://www.redhat.com/archives/rhsa-announce/2018-January/msg00008.html\");\n script_tag(name:\"solution_type\", value:\"VendorFix\");\n script_category(ACT_GATHER_INFO);\n script_copyright(\"Copyright (C) 2018 Greenbone Networks GmbH\");\n script_family(\"Red Hat Local Security Checks\");\n script_dependencies(\"gather-package-list.nasl\");\n script_mandatory_keys(\"ssh/login/rhel\", \"ssh/login/rpms\", re:\"ssh/login/release=RHENT_7\");\n\n exit(0);\n}\n\ninclude(\"revisions-lib.inc\");\ninclude(\"pkg-lib-rpm.inc\");\n\nrelease = rpm_get_ssh_release();\nif(!release) exit(0);\n\nres = \"\";\n\nif(release == \"RHENT_7\")\n{\n\n if ((res = isrpmvuln(pkg:\"kernel-abi-whitelists\", rpm:\"kernel-abi-whitelists~3.10.0~693.11.6.el7\", rls:\"RHENT_7\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isrpmvuln(pkg:\"kernel-doc\", rpm:\"kernel-doc~3.10.0~693.11.6.el7\", rls:\"RHENT_7\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isrpmvuln(pkg:\"kernel\", rpm:\"kernel~3.10.0~693.11.6.el7\", rls:\"RHENT_7\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isrpmvuln(pkg:\"kernel-debug\", rpm:\"kernel-debug~3.10.0~693.11.6.el7\", rls:\"RHENT_7\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isrpmvuln(pkg:\"kernel-debug-debuginfo\", rpm:\"kernel-debug-debuginfo~3.10.0~693.11.6.el7\", rls:\"RHENT_7\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isrpmvuln(pkg:\"kernel-debug-devel\", rpm:\"kernel-debug-devel~3.10.0~693.11.6.el7\", rls:\"RHENT_7\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isrpmvuln(pkg:\"kernel-debuginfo\", rpm:\"kernel-debuginfo~3.10.0~693.11.6.el7\", rls:\"RHENT_7\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isrpmvuln(pkg:\"kernel-debuginfo-common-x86_64\", rpm:\"kernel-debuginfo-common-x86_64~3.10.0~693.11.6.el7\", rls:\"RHENT_7\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isrpmvuln(pkg:\"kernel-devel\", rpm:\"kernel-devel~3.10.0~693.11.6.el7\", rls:\"RHENT_7\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isrpmvuln(pkg:\"kernel-headers\", rpm:\"kernel-headers~3.10.0~693.11.6.el7\", rls:\"RHENT_7\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isrpmvuln(pkg:\"kernel-tools\", rpm:\"kernel-tools~3.10.0~693.11.6.el7\", rls:\"RHENT_7\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isrpmvuln(pkg:\"kernel-tools-debuginfo\", rpm:\"kernel-tools-debuginfo~3.10.0~693.11.6.el7\", rls:\"RHENT_7\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isrpmvuln(pkg:\"kernel-tools-libs\", rpm:\"kernel-tools-libs~3.10.0~693.11.6.el7\", rls:\"RHENT_7\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isrpmvuln(pkg:\"perf\", rpm:\"perf~3.10.0~693.11.6.el7\", rls:\"RHENT_7\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isrpmvuln(pkg:\"perf-debuginfo\", rpm:\"perf-debuginfo~3.10.0~693.11.6.el7\", rls:\"RHENT_7\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isrpmvuln(pkg:\"python-perf\", rpm:\"python-perf~3.10.0~693.11.6.el7\", rls:\"RHENT_7\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isrpmvuln(pkg:\"python-perf-debuginfo\", rpm:\"python-perf-debuginfo~3.10.0~693.11.6.el7\", rls:\"RHENT_7\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if (__pkg_match) exit(99);\n exit(0);\n}\n", "cvss": {"score": 4.7, "vector": "AV:LOCAL/AC:MEDIUM/Au:NONE/C:COMPLETE/I:NONE/A:NONE/"}}, {"lastseen": "2019-03-11T14:32:12", "bulletinFamily": "scanner", "description": "Check the version of kernel", "modified": "2019-03-08T00:00:00", "published": "2018-01-05T00:00:00", "id": "OPENVAS:1361412562310882822", "href": "http://plugins.openvas.org/nasl.php?oid=1361412562310882822", "title": "CentOS Update for kernel CESA-2018:0008 centos6", "type": "openvas", "sourceData": "###############################################################################\n# OpenVAS Vulnerability Test\n# $Id: gb_CESA-2018_0008_kernel_centos6.nasl 14058 2019-03-08 13:25:52Z cfischer $\n#\n# CentOS Update for kernel CESA-2018:0008 centos6\n#\n# Authors:\n# System Generated Check\n#\n# Copyright:\n# Copyright (C) 2018 Greenbone Networks GmbH, http://www.greenbone.net\n#\n# This program is free software; you can redistribute it and/or modify\n# it under the terms of the GNU General Public License version 2\n# (or any later version), as published by the Free Software Foundation.\n#\n# This program is distributed in the hope that it will be useful,\n# but WITHOUT ANY WARRANTY; without even the implied warranty of\n# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n# GNU General Public License for more details.\n#\n# You should have received a copy of the GNU General Public License\n# along with this program; if not, write to the Free Software\n# Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA.\n###############################################################################\n\nif(description)\n{\n script_oid(\"1.3.6.1.4.1.25623.1.0.882822\");\n script_version(\"$Revision: 14058 $\");\n script_tag(name:\"last_modification\", value:\"$Date: 2019-03-08 14:25:52 +0100 (Fri, 08 Mar 2019) $\");\n script_tag(name:\"creation_date\", value:\"2018-01-05 23:54:55 +0100 (Fri, 05 Jan 2018)\");\n script_cve_id(\"CVE-2017-5753\", \"CVE-2017-5715\", \"CVE-2017-5754\");\n script_tag(name:\"cvss_base\", value:\"4.7\");\n script_tag(name:\"cvss_base_vector\", value:\"AV:L/AC:M/Au:N/C:C/I:N/A:N\");\n script_tag(name:\"qod_type\", value:\"package\");\n script_name(\"CentOS Update for kernel CESA-2018:0008 centos6\");\n script_tag(name:\"summary\", value:\"Check the version of kernel\");\n script_tag(name:\"vuldetect\", value:\"Checks if a vulnerable version is present on the target host.\");\n script_tag(name:\"insight\", value:\"The kernel packages contain the Linux\nkernel, the core of any Linux operating 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 commonly\nused performance optimization). There are three primary variants of the\nissue 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\nsoftware update. The updated kernel packages provide software mitigation\nfor this hardware issue at a cost of potential performance penalty. Please\nrefer to References section for further information about this issue and\nthe 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\nbounds-check bypass. It relies on the presence of a precisely-defined\ninstruction sequence in the privileged code as well as the fact that memory\naccesses may cause allocation into the microprocessor's data cache even for\nspeculatively executed instructions that never actually commit (retire). As\na result, an unprivileged 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 precisely-defined\ninstruction sequence in the privileged code as well as the fact that memory\naccesses may cause allocation into the microprocessor's data cache even for\nspeculatively executed instructions that never actually commit (retire). As\na result, an unprivileged attacker could use this flaw to cross the syscall\nand guest/host boundaries and read privileged memory by conducting targeted\ncache side-channel attacks. (CVE-2017-5715, Important)\n\nVariant CVE-2017-5754 relies on the fact that, on impacted microprocessors,\nduring speculative execution of instruction permission faults, exception\ngeneration triggered by a faulting access is suppressed until the\nretirement of the whole instruction block. In a combination with the fact\nthat memory accesses may populate the cache even when the block is being\ndropped and never committed (executed), an unprivileged local attacker\ncould use this flaw to read privileged (kernel space) memory by conducting\ntargeted cache side-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 issues.\");\n script_tag(name:\"affected\", value:\"kernel on CentOS 6\");\n script_tag(name:\"solution\", value:\"Please Install the Updated Packages.\");\n\n script_xref(name:\"CESA\", value:\"2018:0008\");\n script_xref(name:\"URL\", value:\"http://lists.centos.org/pipermail/centos-announce/2018-January/022701.html\");\n script_tag(name:\"solution_type\", value:\"VendorFix\");\n script_category(ACT_GATHER_INFO);\n script_copyright(\"Copyright (C) 2018 Greenbone Networks GmbH\");\n script_family(\"CentOS Local Security Checks\");\n script_dependencies(\"gather-package-list.nasl\");\n script_mandatory_keys(\"ssh/login/centos\", \"ssh/login/rpms\", re:\"ssh/login/release=CentOS6\");\n exit(0);\n}\n\ninclude(\"revisions-lib.inc\");\ninclude(\"pkg-lib-rpm.inc\");\n\nrelease = rpm_get_ssh_release();\nif(!release)\n exit(0);\n\nres = \"\";\n\nif(release == \"CentOS6\")\n{\n\n if ((res = isrpmvuln(pkg:\"kernel\", rpm:\"kernel~2.6.32~696.18.7.el6\", rls:\"CentOS6\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isrpmvuln(pkg:\"kernel-abi-whitelists\", rpm:\"kernel-abi-whitelists~2.6.32~696.18.7.el6\", rls:\"CentOS6\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isrpmvuln(pkg:\"kernel-debug\", rpm:\"kernel-debug~2.6.32~696.18.7.el6\", rls:\"CentOS6\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isrpmvuln(pkg:\"kernel-debug-devel\", rpm:\"kernel-debug-devel~2.6.32~696.18.7.el6\", rls:\"CentOS6\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isrpmvuln(pkg:\"kernel-devel\", rpm:\"kernel-devel~2.6.32~696.18.7.el6\", rls:\"CentOS6\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isrpmvuln(pkg:\"kernel-doc\", rpm:\"kernel-doc~2.6.32~696.18.7.el6\", rls:\"CentOS6\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isrpmvuln(pkg:\"kernel-firmware\", rpm:\"kernel-firmware~2.6.32~696.18.7.el6\", rls:\"CentOS6\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isrpmvuln(pkg:\"kernel-headers\", rpm:\"kernel-headers~2.6.32~696.18.7.el6\", rls:\"CentOS6\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isrpmvuln(pkg:\"perf\", rpm:\"perf~2.6.32~696.18.7.el6\", rls:\"CentOS6\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isrpmvuln(pkg:\"python-perf\", rpm:\"python-perf~2.6.32~696.18.7.el6\", rls:\"CentOS6\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if (__pkg_match) exit(99);\n exit(0);\n}\n", "cvss": {"score": 4.7, "vector": "AV:LOCAL/AC:MEDIUM/Au:NONE/C:COMPLETE/I:NONE/A:NONE/"}}, {"lastseen": "2019-03-14T14:18:10", "bulletinFamily": "scanner", "description": "The remote host is missing an update for the ", "modified": "2019-03-13T00:00:00", "published": "2018-01-23T00:00:00", "id": "OPENVAS:1361412562310843423", "href": "http://plugins.openvas.org/nasl.php?oid=1361412562310843423", "title": "Ubuntu Update for linux USN-3540-1", "type": "openvas", "sourceData": "###############################################################################\n# OpenVAS Vulnerability Test\n# $Id: gb_ubuntu_USN_3540_1.nasl 14140 2019-03-13 12:26:09Z cfischer $\n#\n# Ubuntu Update for linux USN-3540-1\n#\n# Authors:\n# System Generated Check\n#\n# Copyright:\n# Copyright (C) 2018 Greenbone Networks GmbH, http://www.greenbone.net\n#\n# This program is free software; you can redistribute it and/or modify\n# it under the terms of the GNU General Public License version 2\n# (or any later version), as published by the Free Software Foundation.\n#\n# This program is distributed in the hope that it will be useful,\n# but WITHOUT ANY WARRANTY; without even the implied warranty of\n# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n# GNU General Public License for more details.\n#\n# You should have received a copy of the GNU General Public License\n# along with this program; if not, write to the Free Software\n# Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA.\n###############################################################################\n\nif(description)\n{\n script_oid(\"1.3.6.1.4.1.25623.1.0.843423\");\n script_version(\"$Revision: 14140 $\");\n script_tag(name:\"last_modification\", value:\"$Date: 2019-03-13 13:26:09 +0100 (Wed, 13 Mar 2019) $\");\n script_tag(name:\"creation_date\", value:\"2018-01-23 07:37:45 +0100 (Tue, 23 Jan 2018)\");\n script_cve_id(\"CVE-2017-5753\", \"CVE-2017-5715\", \"CVE-2017-5754\");\n script_tag(name:\"cvss_base\", value:\"4.7\");\n script_tag(name:\"cvss_base_vector\", value:\"AV:L/AC:M/Au:N/C:C/I:N/A:N\");\n script_tag(name:\"qod_type\", value:\"package\");\n script_name(\"Ubuntu Update for linux USN-3540-1\");\n script_tag(name:\"summary\", value:\"The remote host is missing an update for the 'linux'\n package(s) announced via the referenced advisory.\");\n script_tag(name:\"vuldetect\", value:\"Checks if a vulnerable version is present on the target host.\");\n script_tag(name:\"insight\", value:\"Jann Horn discovered that microprocessors\n utilizing speculative execution and branch prediction may allow unauthorized\n memory reads via sidechannel attacks. This flaw is known as Spectre. A local\n attacker could use this to expose sensitive information, including kernel\n memory. This update provides mitigations for the i386 (CVE-2017-5753 only),\n amd64, ppc64el, and s390x architectures. (CVE-2017-5715, CVE-2017-5753)\n USN-3522-1 mitigated CVE-2017-5754 (Meltdown) for the amd64 architecture in\n Ubuntu 16.04 LTS. This update provides the corresponding mitigations for the\n ppc64el architecture. Original advisory details: Jann Horn discovered that\n microprocessors utilizing speculative execution and indirect branch prediction\n may allow unauthorized memory reads via sidechannel attacks. This flaw is known\n as Meltdown. A local attacker could use this to expose sensitive information,\n including kernel memory. (CVE-2017-5754)\");\n script_tag(name:\"affected\", value:\"linux on Ubuntu 16.04 LTS\");\n script_tag(name:\"solution\", value:\"Please Install the Updated Packages.\");\n\n script_xref(name:\"USN\", value:\"3540-1\");\n script_xref(name:\"URL\", value:\"http://www.ubuntu.com/usn/usn-3540-1/\");\n script_tag(name:\"solution_type\", value:\"VendorFix\");\n script_category(ACT_GATHER_INFO);\n script_copyright(\"Copyright (C) 2018 Greenbone Networks GmbH\");\n script_family(\"Ubuntu Local Security Checks\");\n script_dependencies(\"gather-package-list.nasl\");\n script_mandatory_keys(\"ssh/login/ubuntu_linux\", \"ssh/login/packages\", re:\"ssh/login/release=UBUNTU16\\.04 LTS\");\n\n exit(0);\n}\n\ninclude(\"revisions-lib.inc\");\ninclude(\"pkg-lib-deb.inc\");\n\nrelease = dpkg_get_ssh_release();\nif(!release)\n exit(0);\n\nres = \"\";\n\nif(release == \"UBUNTU16.04 LTS\")\n{\n\n if ((res = isdpkgvuln(pkg:\"linux-image-4.4.0-1049-aws\", ver:\"4.4.0-1049.58\", rls:\"UBUNTU16.04 LTS\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isdpkgvuln(pkg:\"linux-image-4.4.0-112-generic\", ver:\"4.4.0-112.135\", rls:\"UBUNTU16.04 LTS\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isdpkgvuln(pkg:\"linux-image-4.4.0-112-generic-lpae\", ver:\"4.4.0-112.135\", rls:\"UBUNTU16.04 LTS\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isdpkgvuln(pkg:\"linux-image-4.4.0-112-lowlatency\", ver:\"4.4.0-112.135\", rls:\"UBUNTU16.04 LTS\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isdpkgvuln(pkg:\"linux-image-4.4.0-112-powerpc-e500mc\", ver:\"4.4.0-112.135\", rls:\"UBUNTU16.04 LTS\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isdpkgvuln(pkg:\"linux-image-4.4.0-112-powerpc-smp\", ver:\"4.4.0-112.135\", rls:\"UBUNTU16.04 LTS\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isdpkgvuln(pkg:\"linux-image-4.4.0-112-powerpc64-emb\", ver:\"4.4.0-112.135\", rls:\"UBUNTU16.04 LTS\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isdpkgvuln(pkg:\"linux-image-4.4.0-112-powerpc64-smp\", ver:\"4.4.0-112.135\", rls:\"UBUNTU16.04 LTS\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isdpkgvuln(pkg:\"linux-image-4.4.0-9023-euclid\", ver:\"4.4.0-9023.24\", rls:\"UBUNTU16.04 LTS\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isdpkgvuln(pkg:\"linux-image-aws\", ver:\"4.4.0.1049.51\", rls:\"UBUNTU16.04 LTS\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isdpkgvuln(pkg:\"linux-image-euclid\", ver:\"4.4.0.9023.24\", rls:\"UBUNTU16.04 LTS\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isdpkgvuln(pkg:\"linux-image-generic\", ver:\"4.4.0.112.118\", rls:\"UBUNTU16.04 LTS\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isdpkgvuln(pkg:\"linux-image-generic-lpae\", ver:\"4.4.0.112.118\", rls:\"UBUNTU16.04 LTS\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isdpkgvuln(pkg:\"linux-image-lowlatency\", ver:\"4.4.0.112.118\", rls:\"UBUNTU16.04 LTS\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isdpkgvuln(pkg:\"linux-image-powerpc-e500mc\", ver:\"4.4.0.112.118\", rls:\"UBUNTU16.04 LTS\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isdpkgvuln(pkg:\"linux-image-powerpc-smp\", ver:\"4.4.0.112.118\", rls:\"UBUNTU16.04 LTS\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isdpkgvuln(pkg:\"linux-image-powerpc64-emb\", ver:\"4.4.0.112.118\", rls:\"UBUNTU16.04 LTS\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isdpkgvuln(pkg:\"linux-image-powerpc64-smp\", ver:\"4.4.0.112.118\", rls:\"UBUNTU16.04 LTS\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isdpkgvuln(pkg:\"Please\", ver:\"note that fully mitigating CVE-2017-5715 (Spectre Variant 2)\", rls:\"UBUNTU16.04 LTS\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isdpkgvuln(pkg:\"in\", ver:\"virtual environments, hypervisor updates. On i386 and amd64\", rls:\"UBUNTU16.04 LTS\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isdpkgvuln(pkg:\"kernel\", ver:\"mitigations. Ubuntu is working with Intel and AMD to provide\", rls:\"UBUNTU16.04 LTS\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isdpkgvuln(pkg:\"contact\", ver:\"the vendor to identify necessary firmware updates. Ubuntu\", rls:\"UBUNTU16.04 LTS\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isdpkgvuln(pkg:\"self-hosted\", ver:\"virtual environments in coordination with upstream QEMU.\", rls:\"UBUNTU16.04 LTS\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isdpkgvuln(pkg:\"CPU\", ver:\"features to virtual machines.\", rls:\"UBUNTU16.04 LTS\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if (__pkg_match) exit(99);\n exit(0);\n}\n", "cvss": {"score": 4.7, "vector": "AV:LOCAL/AC:MEDIUM/Au:NONE/C:COMPLETE/I:NONE/A:NONE/"}}, {"lastseen": "2019-03-14T14:17:34", "bulletinFamily": "scanner", "description": "The remote host is missing an update for the ", "modified": "2019-03-13T00:00:00", "published": "2018-01-23T00:00:00", "id": "OPENVAS:1361412562310843427", "href": "http://plugins.openvas.org/nasl.php?oid=1361412562310843427", "title": "Ubuntu Update for linux-azure USN-3541-2", "type": "openvas", "sourceData": "###############################################################################\n# OpenVAS Vulnerability Test\n# $Id: gb_ubuntu_USN_3541_2.nasl 14140 2019-03-13 12:26:09Z cfischer $\n#\n# Ubuntu Update for linux-azure USN-3541-2\n#\n# Authors:\n# System Generated Check\n#\n# Copyright:\n# Copyright (C) 2018 Greenbone Networks GmbH, http://www.greenbone.net\n#\n# This program is free software; you can redistribute it and/or modify\n# it under the terms of the GNU General Public License version 2\n# (or any later version), as published by the Free Software Foundation.\n#\n# This program is distributed in the hope that it will be useful,\n# but WITHOUT ANY WARRANTY; without even the implied warranty of\n# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n# GNU General Public License for more details.\n#\n# You should have received a copy of the GNU General Public License\n# along with this program; if not, write to the Free Software\n# Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA.\n###############################################################################\n\nif(description)\n{\n script_oid(\"1.3.6.1.4.1.25623.1.0.843427\");\n script_version(\"$Revision: 14140 $\");\n script_tag(name:\"last_modification\", value:\"$Date: 2019-03-13 13:26:09 +0100 (Wed, 13 Mar 2019) $\");\n script_tag(name:\"creation_date\", value:\"2018-01-23 07:38:18 +0100 (Tue, 23 Jan 2018)\");\n script_cve_id(\"CVE-2017-5753\", \"CVE-2017-5715\", \"CVE-2017-5754\");\n script_tag(name:\"cvss_base\", value:\"4.7\");\n script_tag(name:\"cvss_base_vector\", value:\"AV:L/AC:M/Au:N/C:C/I:N/A:N\");\n script_tag(name:\"qod_type\", value:\"package\");\n script_name(\"Ubuntu Update for linux-azure USN-3541-2\");\n script_tag(name:\"summary\", value:\"The remote host is missing an update for the 'linux-azure'\n package(s) announced via the referenced advisory.\");\n script_tag(name:\"vuldetect\", value:\"Checks if a vulnerable version is present on the target host.\");\n script_tag(name:\"insight\", value:\"USN-3541-1 addressed vulnerabilities in the\n Linux kernel for Ubuntu 17.10. This update provides the corresponding updates\n for the Linux Hardware Enablement (HWE) kernel from Ubuntu 17.10 for Ubuntu\n 16.04 LTS. Jann Horn discovered that microprocessors utilizing speculative\n execution and branch prediction may allow unauthorized memory reads via\n sidechannel attacks. This flaw is known as Spectre. A local attacker could use\n this to expose sensitive information, including kernel memory. This update\n provides mitigations for the i386 (CVE-2017-5753 only), amd64, ppc64el, and\n s390x architectures. (CVE-2017-5715, CVE-2017-5753) USN-3523-2 mitigated\n CVE-2017-5754 (Meltdown) for the amd64 architecture in the Linux Hardware\n Enablement (HWE) kernel from Ubuntu 17.10 for Ubuntu 16.04 LTS. This update\n provides the corresponding mitigations for the ppc64el architecture. Original\n advisory details: Jann Horn discovered that microprocessors utilizing\n speculative execution and indirect branch prediction may allow unauthorized\n memory reads via sidechannel attacks. This flaw is known as Meltdown. A local\n attacker could use this to expose sensitive information, including kernel\n memory. (CVE-2017-5754)\");\n script_tag(name:\"affected\", value:\"linux-azure on Ubuntu 16.04 LTS\");\n script_tag(name:\"solution\", value:\"Please Install the Updated Packages.\");\n\n script_xref(name:\"USN\", value:\"3541-2\");\n script_xref(name:\"URL\", value:\"http://www.ubuntu.com/usn/usn-3541-2/\");\n script_tag(name:\"solution_type\", value:\"VendorFix\");\n script_category(ACT_GATHER_INFO);\n script_copyright(\"Copyright (C) 2018 Greenbone Networks GmbH\");\n script_family(\"Ubuntu Local Security Checks\");\n script_dependencies(\"gather-package-list.nasl\");\n script_mandatory_keys(\"ssh/login/ubuntu_linux\", \"ssh/login/packages\", re:\"ssh/login/release=UBUNTU16\\.04 LTS\");\n\n exit(0);\n}\n\ninclude(\"revisions-lib.inc\");\ninclude(\"pkg-lib-deb.inc\");\n\nrelease = dpkg_get_ssh_release();\nif(!release)\n exit(0);\n\nres = \"\";\n\nif(release == \"UBUNTU16.04 LTS\")\n{\n\n if ((res = isdpkgvuln(pkg:\"linux-image-4.13.0-1006-azure\", ver:\"4.13.0-1006.8\", rls:\"UBUNTU16.04 LTS\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isdpkgvuln(pkg:\"linux-image-4.13.0-1007-gcp\", ver:\"4.13.0-1007.10\", rls:\"UBUNTU16.04 LTS\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isdpkgvuln(pkg:\"linux-image-4.13.0-1017-oem\", ver:\"4.13.0-1017.18\", rls:\"UBUNTU16.04 LTS\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isdpkgvuln(pkg:\"linux-image-4.13.0-31-generic\", ver:\"4.13.0-31.34~16.04.1\", rls:\"UBUNTU16.04 LTS\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isdpkgvuln(pkg:\"linux-image-4.13.0-31-lowlatency\", ver:\"4.13.0-31.34~16.04.1\", rls:\"UBUNTU16.04 LTS\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isdpkgvuln(pkg:\"linux-image-azure\", ver:\"4.13.0.1006.7\", rls:\"UBUNTU16.04 LTS\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isdpkgvuln(pkg:\"linux-image-gcp\", ver:\"4.13.0.1007.9\", rls:\"UBUNTU16.04 LTS\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isdpkgvuln(pkg:\"linux-image-generic-hwe-16.04\", ver:\"4.13.0.31.51\", rls:\"UBUNTU16.04 LTS\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isdpkgvuln(pkg:\"linux-image-gke\", ver:\"4.13.0.1007.9\", rls:\"UBUNTU16.04 LTS\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isdpkgvuln(pkg:\"linux-image-lowlatency-hwe-16.04\", ver:\"4.13.0.31.51\", rls:\"UBUNTU16.04 LTS\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isdpkgvuln(pkg:\"linux-image-oem\", ver:\"4.13.0.1017.21\", rls:\"UBUNTU16.04 LTS\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isdpkgvuln(pkg:\"Please\", ver:\"note that fully mitigating CVE-2017-5715 (Spectre Variant 2)\", rls:\"UBUNTU16.04 LTS\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isdpkgvuln(pkg:\"in\", ver:\"virtual environments, hypervisor updates. On i386 and amd64\", rls:\"UBUNTU16.04 LTS\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isdpkgvuln(pkg:\"kernel\", ver:\"mitigations. Ubuntu is working with Intel and AMD to provide\", rls:\"UBUNTU16.04 LTS\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isdpkgvuln(pkg:\"contact\", ver:\"the vendor to identify necessary firmware updates. Ubuntu\", rls:\"UBUNTU16.04 LTS\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isdpkgvuln(pkg:\"self-hosted\", ver:\"virtual environments in coordination with upstream QEMU.\", rls:\"UBUNTU16.04 LTS\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isdpkgvuln(pkg:\"CPU\", ver:\"features to virtual machines.\", rls:\"UBUNTU16.04 LTS\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if (__pkg_match) exit(99);\n exit(0);\n}\n", "cvss": {"score": 4.7, "vector": "AV:LOCAL/AC:MEDIUM/Au:NONE/C:COMPLETE/I:NONE/A:NONE/"}}, {"lastseen": "2018-10-26T14:33:59", "bulletinFamily": "scanner", "description": "This host is installed with\n Mozilla Firefox and is prone to multiple vulnerabilities.", "modified": "2018-10-25T00:00:00", "published": "2018-01-05T00:00:00", "id": "OPENVAS:1361412562310812295", "href": "http://plugins.openvas.org/nasl.php?oid=1361412562310812295", "title": "Mozilla Firefox Security Updates(mfsa_2018-01_2018-01)-Windows", "type": "openvas", "sourceData": "###############################################################################\n# OpenVAS Vulnerability Test\n# $Id: gb_mozilla_firefox_mfsa_2018-01_2018-01_win.nasl 12068 2018-10-25 07:21:15Z mmartin $\n#\n# Mozilla Firefox Security Updates(mfsa_2018-01_2018-01)-Windows\n#\n# Authors:\n# Rinu Kuriakose <krinu@secpod.com>\n#\n# Copyright:\n# Copyright (C) 2018 Greenbone Networks GmbH, http://www.greenbone.net\n#\n# This program is free software; you can redistribute it and/or modify\n# it under the terms of the GNU General Public License version 2\n# (or any later version), as published by the Free Software Foundation.\n#\n# This program is distributed in the hope that it will be useful,\n# but WITHOUT ANY WARRANTY; without even the implied warranty of\n# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n# GNU General Public License for more details.\n#\n# You should have received a copy of the GNU General Public License\n# along with this program; if not, write to the Free Software\n# Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA.\n###############################################################################\n\nCPE = \"cpe:/a:mozilla:firefox\";\n\nif(description)\n{\n script_oid(\"1.3.6.1.4.1.25623.1.0.812295\");\n script_version(\"$Revision: 12068 $\");\n script_cve_id(\"CVE-2017-5753\", \"CVE-2017-5715\", \"CVE-2017-5754\");\n script_tag(name:\"cvss_base\", value:\"4.7\");\n script_tag(name:\"cvss_base_vector\", value:\"AV:L/AC:M/Au:N/C:C/I:N/A:N\");\n script_tag(name:\"last_modification\", value:\"$Date: 2018-10-25 09:21:15 +0200 (Thu, 25 Oct 2018) $\");\n script_tag(name:\"creation_date\", value:\"2018-01-05 14:36:19 +0530 (Fri, 05 Jan 2018)\");\n script_name(\"Mozilla Firefox Security Updates(mfsa_2018-01_2018-01)-Windows\");\n\n script_tag(name:\"summary\", value:\"This host is installed with\n Mozilla Firefox and is prone to multiple vulnerabilities.\");\n\n script_tag(name:\"vuldetect\", value:\"Checks if a vulnerable version is present on the target host.\");\n\n script_tag(name:\"insight\", value:\"The multiple flaws exists due to\n multiple errors leading to 'speculative execution side-channel attacks'\n that affect many modern processors, operating systems and browser\n JavaScript engines.\");\n\n script_tag(name:\"impact\", value:\"Successful exploitation of these\n vulnerabilities will allow code on a malicious web page to read data from\n other web sites (violating the same-origin policy) or private data from the\n browser itself.\");\n\n script_tag(name:\"affected\", value:\"Mozilla Firefox version before 57.0.4 on Windows.\");\n\n script_tag(name:\"solution\", value:\"Upgrade to Mozilla Firefox version 57.0.4\n or later.\");\n\n script_tag(name:\"solution_type\", value:\"VendorFix\");\n script_tag(name:\"qod_type\", value:\"registry\");\n script_xref(name:\"URL\", value:\"https://www.mozilla.org/en-US/security/advisories/mfsa2018-01/\");\n script_category(ACT_GATHER_INFO);\n script_copyright(\"Copyright (C) 2018 Greenbone Networks GmbH\");\n script_family(\"General\");\n script_dependencies(\"gb_firefox_detect_portable_win.nasl\");\n script_mandatory_keys(\"Firefox/Win/Ver\");\n script_xref(name:\"URL\", value:\"http://www.mozilla.com/en-US/firefox/all.html\");\n exit(0);\n}\n\ninclude(\"host_details.inc\");\ninclude(\"version_func.inc\");\n\nif(!infos = get_app_version_and_location(cpe:CPE, exit_no_version:TRUE)) exit(0);\nffVer = infos['version'];\nffPath = infos['location'];\n\nif(version_is_less(version:ffVer, test_version:\"57.0.4\"))\n{\n report = report_fixed_ver(installed_version:ffVer, fixed_version:\"57.0.4\", install_path:ffPath);\n security_message(data:report);\n exit(0);\n}\n\nexit(99);\n", "cvss": {"score": 4.7, "vector": "AV:LOCAL/AC:MEDIUM/Au:NONE/C:COMPLETE/I:NONE/A:NONE/"}}, {"lastseen": "2018-10-26T14:33:59", "bulletinFamily": "scanner", "description": "This host is installed with\n Mozilla Firefox and is prone to multiple vulnerabilities.", "modified": "2018-10-25T00:00:00", "published": "2018-01-05T00:00:00", "id": "OPENVAS:1361412562310812296", "href": "http://plugins.openvas.org/nasl.php?oid=1361412562310812296", "title": "Mozilla Firefox Security Updates(mfsa_2018-01_2018-01)-MAC OS X", "type": "openvas", "sourceData": "###############################################################################\n# OpenVAS Vulnerability Test\n# $Id: gb_mozilla_firefox_mfsa_2018-01_2018-01_macosx.nasl 12068 2018-10-25 07:21:15Z mmartin $\n#\n# Mozilla Firefox Security Updates(mfsa_2018-01_2018-01)-MAC OS X\n#\n# Authors:\n# Rinu Kuriakose <krinu@secpod.com>\n#\n# Copyright:\n# Copyright (C) 2018 Greenbone Networks GmbH, http://www.greenbone.net\n#\n# This program is free software; you can redistribute it and/or modify\n# it under the terms of the GNU General Public License version 2\n# (or any later version), as published by the Free Software Foundation.\n#\n# This program is distributed in the hope that it will be useful,\n# but WITHOUT ANY WARRANTY; without even the implied warranty of\n# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n# GNU General Public License for more details.\n#\n# You should have received a copy of the GNU General Public License\n# along with this program; if not, write to the Free Software\n# Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA.\n###############################################################################\n\nCPE = \"cpe:/a:mozilla:firefox\";\n\nif(description)\n{\n script_oid(\"1.3.6.1.4.1.25623.1.0.812296\");\n script_version(\"$Revision: 12068 $\");\n script_cve_id(\"CVE-2017-5753\", \"CVE-2017-5715\", \"CVE-2017-5754\");\n script_tag(name:\"cvss_base\", value:\"4.7\");\n script_tag(name:\"cvss_base_vector\", value:\"AV:L/AC:M/Au:N/C:C/I:N/A:N\");\n script_tag(name:\"last_modification\", value:\"$Date: 2018-10-25 09:21:15 +0200 (Thu, 25 Oct 2018) $\");\n script_tag(name:\"creation_date\", value:\"2018-01-05 14:36:34 +0530 (Fri, 05 Jan 2018)\");\n script_name(\"Mozilla Firefox Security Updates(mfsa_2018-01_2018-01)-MAC OS X\");\n\n script_tag(name:\"summary\", value:\"This host is installed with\n Mozilla Firefox and is prone to multiple vulnerabilities.\");\n\n script_tag(name:\"vuldetect\", value:\"Checks if a vulnerable version is present on the target host.\");\n\n script_tag(name:\"insight\", value:\"The multiple flaws exists due to\n multiple errors leading to 'speculative execution side-channel attacks'\n that affect many modern processors, operating systems and browser\n JavaScript engines.\");\n\n script_tag(name:\"impact\", value:\"Successful exploitation of these\n vulnerabilities will allow code on a malicious web page to read data from\n other web sites (violating the same-origin policy) or private data from the\n browser itself.\");\n\n script_tag(name:\"affected\", value:\"Mozilla Firefox version before 57.0.4 on MAC OS X.\");\n\n script_tag(name:\"solution\", value:\"Upgrade to Mozilla Firefox version 57.0.4\n or later.\");\n\n script_tag(name:\"solution_type\", value:\"VendorFix\");\n script_tag(name:\"qod_type\", value:\"executable_version\");\n script_xref(name:\"URL\", value:\"https://www.mozilla.org/en-US/security/advisories/mfsa2018-01\");\n script_category(ACT_GATHER_INFO);\n script_copyright(\"Copyright (C) 2018 Greenbone Networks GmbH\");\n script_family(\"General\");\n script_dependencies(\"gb_mozilla_prdts_detect_macosx.nasl\");\n script_mandatory_keys(\"Mozilla/Firefox/MacOSX/Version\");\n script_xref(name:\"URL\", value:\"http://www.mozilla.com/en-US/firefox/all.html\");\n exit(0);\n}\n\ninclude(\"host_details.inc\");\ninclude(\"version_func.inc\");\n\nif(!infos = get_app_version_and_location(cpe:CPE, exit_no_version:TRUE)) exit(0);\nffVer = infos['version'];\nffPath = infos['location'];\n\nif(version_is_less(version:ffVer, test_version:\"57.0.4\"))\n{\n report = report_fixed_ver(installed_version:ffVer, fixed_version:\"57.0.4\", install_path:ffPath);\n security_message(data:report);\n exit(0);\n}\n\nexit(99);\n", "cvss": {"score": 4.7, "vector": "AV:LOCAL/AC:MEDIUM/Au:NONE/C:COMPLETE/I:NONE/A:NONE/"}}, {"lastseen": "2019-03-14T14:17:59", "bulletinFamily": "scanner", "description": "The remote host is missing an update for the ", "modified": "2019-03-13T00:00:00", "published": "2018-03-15T00:00:00", "id": "OPENVAS:1361412562310843473", "href": "http://plugins.openvas.org/nasl.php?oid=1361412562310843473", "title": "Ubuntu Update for linux USN-3597-1", "type": "openvas", "sourceData": "###############################################################################\n# OpenVAS Vulnerability Test\n# $Id: gb_ubuntu_USN_3597_1.nasl 14140 2019-03-13 12:26:09Z cfischer $\n#\n# Ubuntu Update for linux USN-3597-1\n#\n# Authors:\n# System Generated Check\n#\n# Copyright:\n# Copyright (C) 2018 Greenbone Networks GmbH, http://www.greenbone.net\n#\n# This program is free software; you can redistribute it and/or modify\n# it under the terms of the GNU General Public License version 2\n# (or any later version), as published by the Free Software Foundation.\n#\n# This program is distributed in the hope that it will be useful,\n# but WITHOUT ANY WARRANTY; without even the implied warranty of\n# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n# GNU General Public License for more details.\n#\n# You should have received a copy of the GNU General Public License\n# along with this program; if not, write to the Free Software\n# Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA.\n###############################################################################\n\nif(description)\n{\n script_oid(\"1.3.6.1.4.1.25623.1.0.843473\");\n script_version(\"$Revision: 14140 $\");\n script_tag(name:\"last_modification\", value:\"$Date: 2019-03-13 13:26:09 +0100 (Wed, 13 Mar 2019) $\");\n script_tag(name:\"creation_date\", value:\"2018-03-15 08:47:33 +0100 (Thu, 15 Mar 2018)\");\n script_cve_id(\"CVE-2017-5715\", \"CVE-2017-5753\", \"CVE-2017-5754\");\n script_tag(name:\"cvss_base\", value:\"4.7\");\n script_tag(name:\"cvss_base_vector\", value:\"AV:L/AC:M/Au:N/C:C/I:N/A:N\");\n script_tag(name:\"qod_type\", value:\"package\");\n script_name(\"Ubuntu Update for linux USN-3597-1\");\n script_tag(name:\"summary\", value:\"The remote host is missing an update for the 'linux'\n package(s) announced via the referenced advisory.\");\n script_tag(name:\"vuldetect\", value:\"Checks if a vulnerable version is present on the target host.\");\n script_tag(name:\"insight\", value:\"USNS 3541-1 and 3523-1 provided mitigations\n for Spectre and Meltdown (CVE-2017-5715, CVE-2017-5753, CVE-2017-5754) for the\n i386, amd64, and ppc64el architectures in Ubuntu 17.10. This update provides the\n corresponding mitigations for the arm64 architecture. Original advisory details:\n Jann Horn discovered that microprocessors utilizing speculative execution and\n indirect branch prediction may allow unauthorized memory reads via sidechannel\n attacks. This flaw is known as Meltdown. A local attacker could use this to\n expose sensitive information, including kernel memory. (CVE-2017-5754) Jann Horn\n discovered that microprocessors utilizing speculative execution and branch\n prediction may allow unauthorized memory reads via sidechannel attacks. This\n flaw is known as Spectre. A local attacker could use this to expose sensitive\n information, including kernel memory. (CVE-2017-5715, CVE-2017-5753)\");\n script_tag(name:\"affected\", value:\"linux on Ubuntu 17.10\");\n script_tag(name:\"solution\", value:\"Please Install the Updated Packages.\");\n\n script_xref(name:\"USN\", value:\"3597-1\");\n script_xref(name:\"URL\", value:\"http://www.ubuntu.com/usn/usn-3597-1/\");\n script_tag(name:\"solution_type\", value:\"VendorFix\");\n script_category(ACT_GATHER_INFO);\n script_copyright(\"Copyright (C) 2018 Greenbone Networks GmbH\");\n script_family(\"Ubuntu Local Security Checks\");\n script_dependencies(\"gather-package-list.nasl\");\n script_mandatory_keys(\"ssh/login/ubuntu_linux\", \"ssh/login/packages\", re:\"ssh/login/release=UBUNTU17\\.10\");\n\n exit(0);\n}\n\ninclude(\"revisions-lib.inc\");\ninclude(\"pkg-lib-deb.inc\");\n\nrelease = dpkg_get_ssh_release();\nif(!release)\n exit(0);\n\nres = \"\";\n\nif(release == \"UBUNTU17.10\")\n{\n\n if ((res = isdpkgvuln(pkg:\"linux-image-4.13.0-1015-raspi2\", ver:\"4.13.0-1015.16\", rls:\"UBUNTU17.10\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isdpkgvuln(pkg:\"linux-image-4.13.0-37-generic\", ver:\"4.13.0-37.42\", rls:\"UBUNTU17.10\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isdpkgvuln(pkg:\"linux-image-4.13.0-37-generic-lpae\", ver:\"4.13.0-37.42\", rls:\"UBUNTU17.10\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isdpkgvuln(pkg:\"linux-image-4.13.0-37-lowlatency\", ver:\"4.13.0-37.42\", rls:\"UBUNTU17.10\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isdpkgvuln(pkg:\"linux-image-generic\", ver:\"4.13.0.37.40\", rls:\"UBUNTU17.10\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isdpkgvuln(pkg:\"linux-image-generic-lpae\", ver:\"4.13.0.37.40\", rls:\"UBUNTU17.10\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isdpkgvuln(pkg:\"linux-image-lowlatency\", ver:\"4.13.0.37.40\", rls:\"UBUNTU17.10\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if ((res = isdpkgvuln(pkg:\"linux-image-raspi2\", ver:\"4.13.0.1015.13\", rls:\"UBUNTU17.10\")) != NULL)\n {\n security_message(data:res);\n exit(0);\n }\n\n if (__pkg_match) exit(99);\n exit(0);\n}\n", "cvss": {"score": 4.7, "vector": "AV:LOCAL/AC:MEDIUM/Au:NONE/C:COMPLETE/I:NONE/A:NONE/"}}], "ubuntu": [{"lastseen": "2018-08-31T00:08:45", "bulletinFamily": "unix", "description": "USN-3597-1 fixed vulnerabilities in the Linux kernel for Ubuntu 17.10. This update provides the corresponding updates for the Linux Hardware Enablement (HWE) kernel from Ubuntu 17.10 for Ubuntu 16.04 LTS.\n\nUSNS 3541-2 and 3523-2 provided mitigations for Spectre and Meltdown (CVE-2017-5715, CVE-2017-5753, CVE-2017-5754) for the i386, amd64, and ppc64el architectures for Ubuntu 16.04 LTS. This update provides the corresponding mitigations for the arm64 architecture. Original advisory details:\n\nJann Horn discovered that microprocessors utilizing speculative execution and indirect branch prediction may allow unauthorized memory reads via sidechannel attacks. This flaw is known as Meltdown. A local attacker could use this to expose sensitive information, including kernel memory. (CVE-2017-5754)\n\nJann Horn discovered that microprocessors utilizing speculative execution and branch prediction may allow unauthorized memory reads via sidechannel attacks. This flaw is known as Spectre. A local attacker could use this to expose sensitive information, including kernel memory. (CVE-2017-5715, CVE-2017-5753)", "modified": "2018-03-15T00:00:00", "published": "2018-03-15T00:00:00", "id": "USN-3597-2", "href": "https://usn.ubuntu.com/3597-2/", "title": "Linux kernel (HWE) vulnerabilities", "type": "ubuntu", "cvss": {"score": 4.7, "vector": "AV:LOCAL/AC:MEDIUM/Au:NONE/C:COMPLETE/I:NONE/A:NONE/"}}, {"lastseen": "2019-01-29T20:32:35", "bulletinFamily": "unix", "description": "USNS 3541-1 and 3523-1 provided mitigations for Spectre and Meltdown (CVE-2017-5715, CVE-2017-5753, CVE-2017-5754) for the i386, amd64, and ppc64el architectures in Ubuntu 17.10. This update provides the corresponding mitigations for the arm64 architecture. Original advisory details:\n\nJann Horn discovered that microprocessors utilizing speculative execution and indirect branch prediction may allow unauthorized memory reads via sidechannel attacks. This flaw is known as Meltdown. A local attacker could use this to expose sensitive information, including kernel memory. (CVE-2017-5754)\n\nJann Horn discovered that microprocessors utilizing speculative execution and branch prediction may allow unauthorized memory reads via sidechannel attacks. This flaw is known as Spectre. A local attacker could use this to expose sensitive information, including kernel memory. (CVE-2017-5715, CVE-2017-5753)", "modified": "2018-03-15T00:00:00", "published": "2018-03-15T00:00:00", "id": "USN-3597-1", "href": "https://usn.ubuntu.com/3597-1/", "title": "Linux kernel vulnerabilities", "type": "ubuntu", "cvss": {"score": 4.7, "vector": "AV:LOCAL/AC:MEDIUM/Au:NONE/C:COMPLETE/I:NONE/A:NONE/"}}, {"lastseen": "2018-08-31T00:08:33", "bulletinFamily": "unix", "description": "Jann Horn discovered that microprocessors utilizing speculative execution and branch prediction may allow unauthorized memory reads via sidechannel attacks. This flaw is known as Spectre. A local attacker could use this to expose sensitive information, including kernel memory. This update provides mitigations for the i386 (CVE-2017-5753 only), amd64, ppc64el, and s390x architectures. (CVE-2017-5715, CVE-2017-5753)\n\nUSN-3523-1 mitigated CVE-2017-5754 (Meltdown) for the amd64 architecture in Ubuntu 17.10. This update provides the corresponding mitigations for the ppc64el architecture. Original advisory details:\n\nJann Horn discovered that microprocessors utilizing speculative execution and indirect branch prediction may allow unauthorized memory reads via sidechannel attacks. This flaw is known as Meltdown. A local attacker could use this to expose sensitive information, including kernel memory. (CVE-2017-5754)", "modified": "2018-01-23T00:00:00", "published": "2018-01-23T00:00:00", "id": "USN-3541-1", "href": "https://usn.ubuntu.com/3541-1/", "title": "Linux kernel vulnerabilities", "type": "ubuntu", "cvss": {"score": 4.7, "vector": "AV:LOCAL/AC:MEDIUM/Au:NONE/C:COMPLETE/I:NONE/A:NONE/"}}, {"lastseen": "2019-01-29T20:34:34", "bulletinFamily": "unix", "description": "Jann Horn discovered that microprocessors utilizing speculative execution and branch prediction may allow unauthorized memory reads via sidechannel attacks. This flaw is known as Spectre. A local attacker could use this to expose sensitive information, including kernel memory. This update provides mitigations for the i386 (CVE-2017-5753 only), amd64, ppc64el, and s390x architectures. (CVE-2017-5715, CVE-2017-5753)\n\nUSN-3522-1 mitigated CVE-2017-5754 (Meltdown) for the amd64 architecture in Ubuntu 16.04 LTS. This update provides the corresponding mitigations for the ppc64el architecture. Original advisory details:\n\nJann Horn discovered that microprocessors utilizing speculative execution and indirect branch prediction may allow unauthorized memory reads via sidechannel attacks. This flaw is known as Meltdown. A local attacker could use this to expose sensitive information, including kernel memory. (CVE-2017-5754)", "modified": "2018-01-23T00:00:00", "published": "2018-01-23T00:00:00", "id": "USN-3540-1", "href": "https://usn.ubuntu.com/3540-1/", "title": "Linux kernel vulnerabilities", "type": "ubuntu", "cvss": {"score": 4.7, "vector": "AV:LOCAL/AC:MEDIUM/Au:NONE/C:COMPLETE/I:NONE/A:NONE/"}}, {"lastseen": "2019-01-29T20:34:29", "bulletinFamily": "unix", "description": "USN-3540-1 addressed vulnerabilities in the Linux kernel for Ubuntu 16.04 LTS. This update provides the corresponding updates for the Linux Hardware Enablement (HWE) kernel from Ubuntu 16.04 LTS for Ubuntu 14.04 LTS.\n\nJann Horn discovered that microprocessors utilizing speculative execution and branch prediction may allow unauthorized memory reads via sidechannel attacks. This flaw is known as Spectre. A local attacker could use this to expose sensitive information, including kernel memory. This update provides mitigations for the i386 (CVE-2017-5753 only), amd64, ppc64el, and s390x architectures. (CVE-2017-5715, CVE-2017-5753)\n\nUSN-3522-2 mitigated CVE-2017-5754 (Meltdown) for the amd64 architecture in the Linux Hardware Enablement (HWE) kernel from Ubuntu 16.04 LTS for Ubuntu 14.04 LTS. This update provides the corresponding mitigations for the ppc64el architecture. Original advisory details:\n\nJann Horn discovered that microprocessors utilizing speculative execution and indirect branch prediction may allow unauthorized memory reads via sidechannel attacks. This flaw is known as Meltdown. A local attacker could use this to expose sensitive information, including kernel memory. (CVE-2017-5754)", "modified": "2018-01-23T00:00:00", "published": "2018-01-23T00:00:00", "id": "USN-3540-2", "href": "https://usn.ubuntu.com/3540-2/", "title": "Linux kernel (Xenial HWE) vulnerabilities", "type": "ubuntu", "cvss": {"score": 4.7, "vector": "AV:LOCAL/AC:MEDIUM/Au:NONE/C:COMPLETE/I:NONE/A:NONE/"}}], "redhat": [{"lastseen": "2018-12-11T17:43:27", "bulletinFamily": "unix", "description": "The ovirt-node-ng packages provide the Red Hat Virtualization Host. These packages include redhat-release-virtualization-host, ovirt-node, and rhev-hypervisor. Red Hat Virtualization Hosts (RHVH) are installed using a special build of Red Hat Enterprise Linux with only the packages required to host virtual machines. RHVH features a Cockpit user interface for monitoring the host's resources and performing administrative tasks.\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\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-01-05T20:37:28", "published": "2018-01-05T20:36:05", "id": "RHSA-2018:0047", "href": "https://access.redhat.com/errata/RHSA-2018:0047", "type": "redhat", "title": "(RHSA-2018:0047) Important: redhat-virtualization-host security update", "cvss": {"score": 4.7, "vector": "AV:LOCAL/AC:MEDIUM/Au:NONE/C:COMPLETE/I:NONE/A:NONE/"}}, {"lastseen": "2018-12-11T17:45:39", "bulletinFamily": "unix", "description": "The RHV-M Virtual Appliance automates the process of installing and configuring the Red Hat Virtualization Manager. The appliance is available to download as an OVA file from the Customer Portal.\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\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-03-19T16:29:44", "published": "2018-01-05T20:35:48", "id": "RHSA-2018:0045", "href": "https://access.redhat.com/errata/RHSA-2018:0045", "type": "redhat", "title": "(RHSA-2018:0045) Important: rhvm-appliance security update", "cvss": {"score": 4.7, "vector": "AV:LOCAL/AC:MEDIUM/Au:NONE/C:COMPLETE/I:NONE/A:NONE/"}}, {"lastseen": "2018-12-11T17:45:43", "bulletinFamily": "unix", "description": "The 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-01-04T03:42:21", "published": "2018-01-04T03:33:58", "id": "RHSA-2018:0010", "href": "https://access.redhat.com/errata/RHSA-2018:0010", "type": "redhat", "title": "(RHSA-2018:0010) Important: kernel security update", "cvss": {"score": 4.7, "vector": "AV:LOCAL/AC:MEDIUM/Au:NONE/C:COMPLETE/I:NONE/A:NONE/"}}, {"lastseen": "2018-12-11T17:42:05", "bulletinFamily": "unix", "description": "The kernel packages contain the Linux kernel, the core of any Linux operating system.\n\nSecurity Fix(es):\n\n* hw: cpu: speculative execution branch target injection (s390-only) (CVE-2017-5715, Important)\n\n* hw: cpu: speculative execution bounds-check bypass (s390 and powerpc) (CVE-2017-5753, Important)\n\n* hw: cpu: speculative execution permission faults handling (powerpc-only) (CVE-2017-5754)\n\nFor more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.\n\nBug Fix(es):\n\n* If an NFSv3 client mounted a subdirectory of an exported file system, a directory entry to the mount hosting the export was incorrectly held even after clearing the cache. Consequently, attempts to unmount the subdirectory with the umount command failed with the EBUSY error. With this update, the underlying source code has been fixed, and the unmount operation now succeeds as expected in the described situation. (BZ#1538587)\n\n* The Return Trampoline (Retpoline) mechanism mitigates the branch target injection, also known as the Spectre variant 2 vulnerability. With this update, Retpoline has been implemented into the Red Hat Enterprise Linux kernel. (BZ#1543023)", "modified": "2018-03-13T18:19:08", "published": "2018-03-13T18:14:17", "id": "RHSA-2018:0496", "href": "https://access.redhat.com/errata/RHSA-2018:0496", "type": "redhat", "title": "(RHSA-2018:0496) Important: kernel security and bug fix update", "cvss": {"score": 4.7, "vector": "AV:LOCAL/AC:MEDIUM/Au:NONE/C:COMPLETE/I:NONE/A:NONE/"}}, {"lastseen": "2018-12-11T17:41:41", "bulletinFamily": "unix", "description": "The rhev-hypervisor7 package provides a Red Hat Enterprise Virtualization Hypervisor ISO disk image. The Red Hat Enterprise Virtualization Hypervisor is a dedicated Kernel-based Virtual Machine (KVM) hypervisor. It includes everything necessary to run and manage virtual machines: A subset of the Red Hat Enterprise Linux operating environment and the Red Hat Enterprise Virtualization Agent.\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\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-01-05T20:40:16", "published": "2018-01-05T20:35:57", "id": "RHSA-2018:0046", "href": "https://access.redhat.com/errata/RHSA-2018:0046", "type": "redhat", "title": "(RHSA-2018:0046) Important: rhev-hypervisor7 security update", "cvss": {"score": 4.7, "vector": "AV:LOCAL/AC:MEDIUM/Au:NONE/C:COMPLETE/I:NONE/A:NONE/"}}, {"lastseen": "2018-12-11T17:44:00", "bulletinFamily": "unix", "description": "The 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-04-12T03:32:56", "published": "2018-01-04T03:30:46", "id": "RHSA-2018:0007", "href": "https://access.redhat.com/errata/RHSA-2018:0007", "type": "redhat", "title": "(RHSA-2018:0007) Important: kernel security update", "cvss": {"score": 4.7, "vector": "AV:LOCAL/AC:MEDIUM/Au:NONE/C:COMPLETE/I:NONE/A:NONE/"}}, {"lastseen": "2018-01-15T22:07:22", "bulletinFamily": "unix", "description": "The kernel packages contain the Linux kernel, the core of any Linux operating system. CloudForms virtual machines include a copy of the Linux Kernel.\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-01-16T02:33:41", "published": "2018-01-16T02:33:22", "id": "RHSA-2018:0090", "href": "https://access.redhat.com/errata/RHSA-2018:0090", "type": "redhat", "title": "(RHSA-2018:0090) Important: Red Hat CloudForms 4.2 security update", "cvss": {"score": 4.7, "vector": "AV:LOCAL/AC:MEDIUM/Au:NONE/C:COMPLETE/I:NONE/A:NONE/"}}, {"lastseen": "2018-12-11T17:44:20", "bulletinFamily": "unix", "description": "The 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-01-04T20:08:30", "published": "2018-01-04T20:05:39", "id": "RHSA-2018:0020", "href": "https://access.redhat.com/errata/RHSA-2018:0020", "type": "redhat", "title": "(RHSA-2018:0020) Important: kernel security update", "cvss": {"score": 4.7, "vector": "AV:LOCAL/AC:MEDIUM/Au:NONE/C:COMPLETE/I:NONE/A:NONE/"}}, {"lastseen": "2018-12-11T17:42:24", "bulletinFamily": "unix", "description": "The kernel packages contain the Linux kernel, the core of any Linux operating system. CloudForms virtual machines include a copy of the Linux Kernel.\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-01-17T01:03:04", "published": "2018-01-17T01:01:38", "id": "RHSA-2018:0092", "href": "https://access.redhat.com/errata/RHSA-2018:0092", "type": "redhat", "title": "(RHSA-2018:0092) Important: Red Hat CloudForms 4.0 security update", "cvss": {"score": 4.7, "vector": "AV:LOCAL/AC:MEDIUM/Au:NONE/C:COMPLETE/I:NONE/A:NONE/"}}, {"lastseen": "2018-01-15T22:07:43", "bulletinFamily": "unix", "description": "The kernel packages contain the Linux kernel, the core of any Linux operating system. CloudForms virtual machines include a copy of the Linux Kernel.\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-01-16T02:33:52", "published": "2018-01-16T02:33:25", "id": "RHSA-2018:0091", "href": "https://access.redhat.com/errata/RHSA-2018:0091", "type": "redhat", "title": "(RHSA-2018:0091) Important: Red Hat CloudForms 4.5 security update", "cvss": {"score": 4.7, "vector": "AV:LOCAL/AC:MEDIUM/Au:NONE/C:COMPLETE/I:NONE/A:NONE/"}}], "nessus": [{"lastseen": "2019-02-21T01:37:22", "bulletinFamily": "scanner", "description": "An update for kernel is now available for Red Hat Enterprise Linux 6.\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\n* hw: cpu: speculative execution branch target injection (s390-only) (CVE-2017-5715, Important)\n\n* hw: cpu: speculative execution bounds-check bypass (s390 and powerpc) (CVE-2017-5753, Important)\n\n* hw: cpu: speculative execution permission faults handling (powerpc-only) (CVE-2017-5754)\n\nFor more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.\n\nBug Fixes :\n\n* If a fibre channel (FC) switch was powered down and then powered on again, the SCSI device driver stopped permanently the SCSI device's request queue. Consequently, the FC port login failed, leaving the port state as 'Bypassed' instead of 'Online', and users had to reboot the operating system. This update fixes the driver to avoid the permanent stop of the request queue. As a result, SCSI device now continues working as expected after power cycling the FC switch.\n(BZ#1519857)\n\n* Previously, on final close or unlink of a file, the find_get_pages() function in the memory management sometimes found no pages even if there were some pages left to save. Consequently, a kernel crash occurred when attempting to enter the unlink() function. This update fixes the find_get_pages() function in the memory management code to not return 0 too early. As a result, the kernel no longer crashes due to this behavior.(BZ# 1527811)\n\n* Using IPsec connections under a heavy load could previously lead to a network performance degradation, especially when using the aesni-intel module. This update fixes the issue by making the cryptd queue length configurable so that it can be increased to prevent an overflow and packet drop. As a result, using IPsec under a heavy load no longer reduces network performance. (BZ#1527802)\n\n* Previously, a deadlock in the bnx2fc driver caused all adapters to block and the SCSI error handler to become unresponsive. As a result, data transferring through the adapter was sometimes blocked. This update fixes bnx2fc, and data transferring through the adapter is no longer blocked due to this behavior. (BZ#1523783)\n\n* If an NFSv3 client mounted a subdirectory of an exported file system, a directory entry to the mount hosting the export was incorrectly held even after clearing the cache. Consequently, attempts to unmount the subdirectory with the umount command failed with the EBUSY error. With this update, the underlying source code has been fixed, and the unmount operation now succeeds as expected in the described situation. (BZ#1535938)\n\nUsers of kernel are advised to upgrade to these updated packages, which fix these bugs. The system must be rebooted for this update to take effect.", "modified": "2019-02-04T00:00:00", "id": "CENTOS_RHSA-2018-0512.NASL", "href": "https://www.tenable.com/plugins/index.php?view=single&id=108341", "published": "2018-03-15T00:00:00", "title": "CentOS 6 : kernel (CESA-2018:0512) (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:0512 and \n# CentOS Errata and Security Advisory 2018:0512 respectively.\n#\n\nif (NASL_LEVEL < 3000) exit(0);\n\ninclude(\"compat.inc\");\n\nif (description)\n{\n script_id(108341);\n script_version(\"1.3\");\n script_cvs_date(\"Date: 2019/02/04 10:02:18\");\n\n script_cve_id(\"CVE-2017-5715\", \"CVE-2017-5753\", \"CVE-2017-5754\");\n script_xref(name:\"RHSA\", value:\"2018:0512\");\n\n script_name(english:\"CentOS 6 : kernel (CESA-2018:0512) (Meltdown) (Spectre)\");\n script_summary(english:\"Checks rpm output for the updated packages\");\n\n script_set_attribute(\n attribute:\"synopsis\", \n value:\"The remote CentOS 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.\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\n* hw: cpu: speculative execution branch target injection (s390-only)\n(CVE-2017-5715, Important)\n\n* hw: cpu: speculative execution bounds-check bypass (s390 and\npowerpc) (CVE-2017-5753, Important)\n\n* hw: cpu: speculative execution permission faults handling\n(powerpc-only) (CVE-2017-5754)\n\nFor more details about the security issue(s), including the impact, a\nCVSS score, acknowledgments, and other related information, refer to\nthe CVE page(s) listed in the References section.\n\nBug Fixes :\n\n* If a fibre channel (FC) switch was powered down and then powered on\nagain, the SCSI device driver stopped permanently the SCSI device's\nrequest queue. Consequently, the FC port login failed, leaving the\nport state as 'Bypassed' instead of 'Online', and users had to reboot\nthe operating system. This update fixes the driver to avoid the\npermanent stop of the request queue. As a result, SCSI device now\ncontinues working as expected after power cycling the FC switch.\n(BZ#1519857)\n\n* Previously, on final close or unlink of a file, the find_get_pages()\nfunction in the memory management sometimes found no pages even if\nthere were some pages left to save. Consequently, a kernel crash\noccurred when attempting to enter the unlink() function. This update\nfixes the find_get_pages() function in the memory management code to\nnot return 0 too early. As a result, the kernel no longer crashes due\nto this behavior.(BZ# 1527811)\n\n* Using IPsec connections under a heavy load could previously lead to\na network performance degradation, especially when using the\naesni-intel module. This update fixes the issue by making the cryptd\nqueue length configurable so that it can be increased to prevent an\noverflow and packet drop. As a result, using IPsec under a heavy load\nno longer reduces network performance. (BZ#1527802)\n\n* Previously, a deadlock in the bnx2fc driver caused all adapters to\nblock and the SCSI error handler to become unresponsive. As a result,\ndata transferring through the adapter was sometimes blocked. This\nupdate fixes bnx2fc, and data transferring through the adapter is no\nlonger blocked due to this behavior. (BZ#1523783)\n\n* If an NFSv3 client mounted a subdirectory of an exported file\nsystem, a directory entry to the mount hosting the export was\nincorrectly held even after clearing the cache. Consequently, attempts\nto unmount the subdirectory with the umount command failed with the\nEBUSY error. With this update, the underlying source code has been\nfixed, and the unmount operation now succeeds as expected in the\ndescribed situation. (BZ#1535938)\n\nUsers of kernel are advised to upgrade to these updated packages,\nwhich fix these bugs. The system must be rebooted for this update to\ntake effect.\"\n );\n # https://lists.centos.org/pipermail/centos-announce/2018-March/022801.html\n script_set_attribute(\n attribute:\"see_also\",\n value:\"http://www.nessus.org/u?3314062b\"\n );\n script_set_attribute(\n attribute:\"solution\", \n value:\"Update the affected kernel packages.\"\n );\n script_set_cvss_base_vector(\"CVSS2#AV:L/AC:M/Au:N/C:C/I:N/A:N\");\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_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:centos:centos:kernel\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:centos:centos:kernel-abi-whitelists\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:centos:centos:kernel-debug\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:centos:centos:kernel-debug-devel\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:centos:centos:kernel-devel\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:centos:centos:kernel-doc\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:centos:centos:kernel-firmware\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:centos:centos:kernel-headers\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:centos:centos:perf\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:centos:centos:python-perf\");\n script_set_attribute(attribute:\"cpe\", value:\"cpe:/o:centos:centos:6\");\n\n script_set_attribute(attribute:\"vuln_publication_date\", value:\"2018/01/04\");\n script_set_attribute(attribute:\"patch_publication_date\", value:\"2018/03/14\");\n script_set_attribute(attribute:\"plugin_publication_date\", value:\"2018/03/15\");\n script_set_attribute(attribute:\"in_the_news\", value:\"true\");\n script_set_attribute(attribute:\"generated_plugin\", value:\"current\");\n script_end_attributes();\n\n script_category(ACT_GATHER_INFO);\n script_copyright(english:\"This script is Copyright (C) 2018-2019 and is owned by Tenable, Inc. or an Affiliate thereof.\");\n script_family(english:\"CentOS Local Security Checks\");\n\n script_dependencies(\"ssh_get_info.nasl\");\n script_require_keys(\"Host/local_checks_enabled\", \"Host/CentOS/release\", \"Host/CentOS/rpm-list\");\n\n exit(0);\n}\n\n\ninclude(\"audit.inc\");\ninclude(\"global_settings.inc\");\ninclude(\"rpm.inc\");\n\n\nif (!get_kb_item(\"Host/local_checks_enabled\")) audit(AUDIT_LOCAL_CHECKS_NOT_ENABLED);\nif (!get_kb_item(\"Host/CentOS/release\")) audit(AUDIT_OS_NOT, \"CentOS\");\nif (!get_kb_item(\"Host/CentOS/rpm-list\")) audit(AUDIT_PACKAGE_LIST_MISSING);\n\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, \"CentOS\", cpu);\n\n\nflag = 0;\nif (rpm_check(release:\"CentOS-6\", reference:\"kernel-2.6.32-696.23.1.el6\")) flag++;\nif (rpm_check(release:\"CentOS-6\", reference:\"kernel-abi-whitelists-2.6.32-696.23.1.el6\")) flag++;\nif (rpm_check(release:\"CentOS-6\", reference:\"kernel-debug-2.6.32-696.23.1.el6\")) flag++;\nif (rpm_check(release:\"CentOS-6\", reference:\"kernel-debug-devel-2.6.32-696.23.1.el6\")) flag++;\nif (rpm_check(release:\"CentOS-6\", reference:\"kernel-devel-2.6.32-696.23.1.el6\")) flag++;\nif (rpm_check(release:\"CentOS-6\", reference:\"kernel-doc-2.6.32-696.23.1.el6\")) flag++;\nif (rpm_check(release:\"CentOS-6\", reference:\"kernel-firmware-2.6.32-696.23.1.el6\")) flag++;\nif (rpm_check(release:\"CentOS-6\", reference:\"kernel-headers-2.6.32-696.23.1.el6\")) flag++;\nif (rpm_check(release:\"CentOS-6\", reference:\"perf-2.6.32-696.23.1.el6\")) flag++;\nif (rpm_check(release:\"CentOS-6\", reference:\"python-perf-2.6.32-696.23.1.el6\")) flag++;\n\n\nif (flag)\n{\n if (report_verbosity > 0) security_warning(port:0, extra:rpm_report_get());\n else security_warning(0);\n exit(0);\n}\nelse audit(AUDIT_HOST_NOT, \"affected\");\n", "cvss": {"score": 4.7, "vector": "AV:LOCAL/AC:MEDIUM/Au:NONE/C:COMPLETE/I:NONE/A:NONE/"}}, {"lastseen": "2019-02-21T01:35:57", "bulletinFamily": "scanner", "description": "USN-3541-1 addressed vulnerabilities in the Linux kernel for Ubuntu 17.10. This update provides the corresponding updates for the Linux Hardware Enablement (HWE) kernel from Ubuntu 17.10 for Ubuntu 16.04 LTS.\n\nJann Horn discovered that microprocessors utilizing speculative execution and branch prediction may allow unauthorized memory reads via sidechannel attacks. This flaw is known as Spectre. A local attacker could use this to expose sensitive information, including kernel memory. This update provides mitigations for the i386 (CVE-2017-5753 only), amd64, ppc64el, and s390x architectures.\n(CVE-2017-5715, CVE-2017-5753)\n\nUSN-3523-2 mitigated CVE-2017-5754 (Meltdown) for the amd64 architecture in the Linux Hardware Enablement (HWE) kernel from Ubuntu 17.10 for Ubuntu 16.04 LTS. This update provides the corresponding mitigations for the ppc64el architecture. \n\nJann Horn discovered that microprocessors utilizing speculative execution and indirect branch prediction may allow unauthorized memory reads via sidechannel attacks. This flaw is known as Meltdown. A local attacker could use this to expose sensitive information, including kernel memory. (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-3541-2.NASL", "href": "https://www.tenable.com/plugins/index.php?view=single&id=106271", "published": "2018-01-23T00:00:00", "title": "Ubuntu 16.04 LTS : linux-hwe, linux-azure, linux-gcp, linux-oem vulnerabilities (USN-3541-2) (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-3541-2. 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(106271);\n script_version(\"3.8\");\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:\"3541-2\");\n script_xref(name:\"IAVA\", value:\"2018-A-0019\");\n script_xref(name:\"IAVA\", value:\"2018-A-0020\");\n\n script_name(english:\"Ubuntu 16.04 LTS : linux-hwe, linux-azure, linux-gcp, linux-oem vulnerabilities (USN-3541-2) (Meltdown) (Spectre)\");\n script_summary(english:\"Checks dpkg output for updated packages.\");\n\n script_set_attribute(\n attribute:\"synopsis\", \n value:\n\"The remote Ubuntu host is missing one or more security-related\npatches.\"\n );\n script_set_attribute(\n attribute:\"description\", \n value:\n\"USN-3541-1 addressed vulnerabilities in the Linux kernel for Ubuntu\n17.10. This update provides the corresponding updates for the Linux\nHardware Enablement (HWE) kernel from Ubuntu 17.10 for Ubuntu 16.04\nLTS.\n\nJann Horn discovered that microprocessors utilizing speculative\nexecution and branch prediction may allow unauthorized memory reads\nvia sidechannel attacks. This flaw is known as Spectre. A local\nattacker could use this to expose sensitive information, including\nkernel memory. This update provides mitigations for the i386\n(CVE-2017-5753 only), amd64, ppc64el, and s390x architectures.\n(CVE-2017-5715, CVE-2017-5753)\n\nUSN-3523-2 mitigated CVE-2017-5754 (Meltdown) for the amd64\narchitecture in the Linux Hardware Enablement (HWE) kernel from Ubuntu\n17.10 for Ubuntu 16.04 LTS. This update provides the corresponding\nmitigations for the ppc64el architecture. \n\nJann Horn discovered that microprocessors utilizing speculative\nexecution and indirect branch prediction may allow unauthorized memory\nreads via sidechannel attacks. This flaw is known as Meltdown. A local\nattacker could use this to expose sensitive information, including\nkernel memory. (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/3541-2/\"\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:canonical:ubuntu_linux:linux-image-4.13-azure\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:canonical:ubuntu_linux:linux-image-4.13-gcp\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:canonical:ubuntu_linux:linux-image-4.13-generic\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:canonical:ubuntu_linux:linux-image-4.13-lowlatency\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:canonical:ubuntu_linux:linux-image-4.13-oem\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:canonical:ubuntu_linux:linux-image-azure\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:canonical:ubuntu_linux:linux-image-gcp\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:canonical:ubuntu_linux:linux-image-generic-hwe-16.04\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:canonical:ubuntu_linux:linux-image-gke\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:canonical:ubuntu_linux:linux-image-lowlatency-hwe-16.04\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:canonical:ubuntu_linux:linux-image-oem\");\n script_set_attribute(attribute:\"cpe\", value:\"cpe:/o:canonical:ubuntu_linux:16.04\");\n\n script_set_attribute(attribute:\"patch_publication_date\", value:\"2018/01/22\");\n script_set_attribute(attribute:\"in_the_news\", value:\"true\");\n script_set_attribute(attribute:\"plugin_publication_date\", value:\"2018/01/23\");\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:\"^(16\\.04)$\", string:release)) audit(AUDIT_OS_NOT, \"Ubuntu 16.04\", \"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:\"16.04\", pkgname:\"linux-image-4.13.0-1006-azure\", pkgver:\"4.13.0-1006.8\")) flag++;\nif (ubuntu_check(osver:\"16.04\", pkgname:\"linux-image-4.13.0-1007-gcp\", pkgver:\"4.13.0-1007.10\")) flag++;\nif (ubuntu_check(osver:\"16.04\", pkgname:\"linux-image-4.13.0-1017-oem\", pkgver:\"4.13.0-1017.18\")) flag++;\nif (ubuntu_check(osver:\"16.04\", pkgname:\"linux-image-4.13.0-31-generic\", pkgver:\"4.13.0-31.34~16.04.1\")) flag++;\nif (ubuntu_check(osver:\"16.04\", pkgname:\"linux-image-4.13.0-31-lowlatency\", pkgver:\"4.13.0-31.34~16.04.1\")) flag++;\nif (ubuntu_check(osver:\"16.04\", pkgname:\"linux-image-azure\", pkgver:\"4.13.0.1006.7\")) flag++;\nif (ubuntu_check(osver:\"16.04\", pkgname:\"linux-image-gcp\", pkgver:\"4.13.0.1007.9\")) flag++;\nif (ubuntu_check(osver:\"16.04\", pkgname:\"linux-image-generic-hwe-16.04\", pkgver:\"4.13.0.31.51\")) flag++;\nif (ubuntu_check(osver:\"16.04\", pkgname:\"linux-image-gke\", pkgver:\"4.13.0.1007.9\")) flag++;\nif (ubuntu_check(osver:\"16.04\", pkgname:\"linux-image-lowlatency-hwe-16.04\", pkgver:\"4.13.0.31.51\")) flag++;\nif (ubuntu_check(osver:\"16.04\", pkgname:\"linux-image-oem\", pkgver:\"4.13.0.1017.21\")) 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, \"linux-image-4.13-azure / linux-image-4.13-gcp / etc\");\n}\n", "cvss": {"score": 4.7, "vector": "AV:LOCAL/AC:MEDIUM/Au:NONE/C:COMPLETE/I:NONE/A:NONE/"}}, {"lastseen": "2019-02-21T01:36:01", "bulletinFamily": "scanner", "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": "2019-01-15T00:00:00", "id": "AIX_IJ03030.NASL", "href": "https://www.tenable.com/plugins/index.php?view=single&id=106311", "published": "2018-01-25T00:00:00", "title": "AIX 6.1 TL 9 : spectre_meltdown (IJ03030) (Meltdown) (Spectre)", "type": "nessus", "sourceData": "#\n# (C) Tenable Network Security, Inc.\n#\n# The text in the description was extracted from AIX Security\n# Advisory spectre_meltdown_advisory.asc.\n#\n\ninclude(\"compat.inc\");\n\nif (description)\n{\n script_id(106311);\n script_version(\"3.9\");\n script_cvs_date(\"Date: 2019/01/15 15:17:26\");\n\n script_cve_id(\"CVE-2017-5715\", \"CVE-2017-5753\", \"CVE-2017-5754\");\n script_xref(name:\"IAVA\", value:\"2018-A-0019\");\n script_xref(name:\"IAVA\", value:\"2018-A-0020\");\n\n script_name(english:\"AIX 6.1 TL 9 : spectre_meltdown (IJ03030) (Meltdown) (Spectre)\");\n script_summary(english:\"Check for APAR IJ03030\");\n\n script_set_attribute(\n attribute:\"synopsis\", \n value:\"The remote AIX host is missing a security patch.\"\n );\n script_set_attribute(\n attribute:\"description\", \n value:\n\"Systems with microprocessors utilizing speculative execution and indirect\nbranch prediction may allow unauthorized disclosure of information to an\nattacker with local user access via a side-channel analysis.\"\n );\n # http://aix.software.ibm.com/aix/efixes/security/spectre_meltdown_advisory.asc\n script_set_attribute(\n attribute:\"see_also\",\n value:\"http://www.nessus.org/u?0ecfba9a\"\n );\n script_set_attribute(\n attribute:\"solution\", \n value:\"Install the appropriate interim fix.\"\n );\n script_set_cvss_base_vector(\"CVSS2#AV:L/AC:M/Au:N/C:C/I:N/A:N\");\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_attribute(attribute:\"cvss_score_source\", value:\"CVE-2017-5715\");\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:\"cpe:/o:ibm:aix:6.1\");\n\n script_set_attribute(attribute:\"vuln_publication_date\", value:\"2018/01/25\");\n script_set_attribute(attribute:\"patch_publication_date\", value:\"2018/01/25\");\n script_set_attribute(attribute:\"in_the_news\", value:\"true\");\n script_set_attribute(attribute:\"generated_plugin\", value:\"former\");\n script_set_attribute(attribute:\"plugin_publication_date\", value:\"2018/01/25\");\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) 2019 and is owned by Tenable, Inc. or an Affiliate thereof.\");\n script_family(english:\"AIX Local Security Checks\");\n\n script_dependencies(\"ssh_get_info.nasl\");\n script_require_keys(\"Host/AIX/lslpp\", \"Host/local_checks_enabled\", \"Host/AIX/version\");\n\n exit(0);\n}\n\n\n\ninclude(\"audit.inc\");\ninclude(\"global_settings.inc\");\ninclude(\"aix.inc\");\ninclude(\"misc_func.inc\");\n\nif ( ! get_kb_item(\"Host/local_checks_enabled\") ) audit(AUDIT_LOCAL_CHECKS_NOT_ENABLED);\nif ( ! get_kb_item(\"Host/AIX/version\") ) audit(AUDIT_OS_NOT, \"AIX\");\nif ( ! get_kb_item(\"Host/AIX/lslpp\") ) audit(AUDIT_PACKAGE_LIST_MISSING);\n\nif ( get_kb_item(\"Host/AIX/emgr_failure\" ) ) exit(0, \"This iFix check is disabled because : \"+get_kb_item(\"Host/AIX/emgr_failure\") );\n\nflag = 0;\n\nif (aix_check_ifix(release:\"6.1\", ml:\"09\", sp:\"08\", patch:\"IJ03030m8a\", package:\"bos.mp64\", minfilesetver:\"6.1.9.0\", maxfilesetver:\"6.1.9.300\") < 0) flag++;\nif (aix_check_ifix(release:\"6.1\", ml:\"09\", sp:\"09\", patch:\"IJ03030m9a\", package:\"bos.mp64\", minfilesetver:\"6.1.9.0\", maxfilesetver:\"6.1.9.300\") < 0) flag++;\nif (aix_check_ifix(release:\"6.1\", ml:\"09\", sp:\"10\", patch:\"IJ03030mAa\", package:\"bos.mp64\", minfilesetver:\"6.1.9.0\", maxfilesetver:\"6.1.9.300\") < 0) flag++;\n\nif (flag)\n{\n if (report_verbosity > 0) security_warning(port:0, extra:aix_report_get());\n else security_warning(0);\n exit(0);\n}\nelse audit(AUDIT_HOST_NOT, \"affected\");\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-rt is now available for Red Hat Enterprise Linux 7.\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-rt packages provide the Real Time Linux Kernel, which enables fine-tuning for systems with extremely high determinism requirements.\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-0016.NASL", "href": "https://www.tenable.com/plugins/index.php?view=single&id=105532", "published": "2018-01-04T00:00:00", "title": "RHEL 7 : kernel-rt (RHSA-2018:0016) (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:0016. The text \n# itself is copyright (C) Red Hat, Inc.\n#\n\ninclude(\"compat.inc\");\n\nif (description)\n{\n script_id(105532);\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:0016\");\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 7 : kernel-rt (RHSA-2018:0016) (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-rt is now available for Red Hat Enterprise Linux\n7.\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-rt packages provide the Real Time Linux Kernel, which\nenables fine-tuning for systems with extremely high determinism\nrequirements.\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:0016\"\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-rt\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:redhat:enterprise_linux:kernel-rt-debug\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:redhat:enterprise_linux:kernel-rt-debug-debuginfo\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:redhat:enterprise_linux:kernel-rt-debug-devel\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:redhat:enterprise_linux:kernel-rt-debug-kvm\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:redhat:enterprise_linux:kernel-rt-debug-kvm-debuginfo\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:redhat:enterprise_linux:kernel-rt-debuginfo\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:redhat:enterprise_linux:kernel-rt-debuginfo-common-x86_64\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:redhat:enterprise_linux:kernel-rt-devel\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:redhat:enterprise_linux:kernel-rt-doc\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:redhat:enterprise_linux:kernel-rt-kvm\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:redhat:enterprise_linux:kernel-rt-kvm-debuginfo\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:redhat:enterprise_linux:kernel-rt-trace\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:redhat:enterprise_linux:kernel-rt-trace-debuginfo\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:redhat:enterprise_linux:kernel-rt-trace-devel\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:redhat:enterprise_linux:kernel-rt-trace-kvm\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:redhat:enterprise_linux:kernel-rt-trace-kvm-debuginfo\");\n script_set_attribute(attribute:\"cpe\", value:\"cpe:/o:redhat:enterprise_linux:7\");\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:\"^7([^0-9]|$)\", string:os_ver)) audit(AUDIT_OS_NOT, \"Red Hat 7.x\", \"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:0016\";\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:\"RHEL7\", cpu:\"x86_64\", reference:\"kernel-rt-3.10.0-693.11.1.rt56.639.el7\")) flag++;\n if (rpm_check(release:\"RHEL7\", cpu:\"x86_64\", reference:\"kernel-rt-debug-3.10.0-693.11.1.rt56.639.el7\")) flag++;\n if (rpm_check(release:\"RHEL7\", cpu:\"x86_64\", reference:\"kernel-rt-debug-debuginfo-3.10.0-693.11.1.rt56.639.el7\")) flag++;\n if (rpm_check(release:\"RHEL7\", cpu:\"x86_64\", reference:\"kernel-rt-debug-devel-3.10.0-693.11.1.rt56.639.el7\")) flag++;\n if (rpm_check(release:\"RHEL7\", cpu:\"x86_64\", reference:\"kernel-rt-debug-kvm-3.10.0-693.11.1.rt56.639.el7\")) flag++;\n if (rpm_check(release:\"RHEL7\", cpu:\"x86_64\", reference:\"kernel-rt-debug-kvm-debuginfo-3.10.0-693.11.1.rt56.639.el7\")) flag++;\n if (rpm_check(release:\"RHEL7\", cpu:\"x86_64\", reference:\"kernel-rt-debuginfo-3.10.0-693.11.1.rt56.639.el7\")) flag++;\n if (rpm_check(release:\"RHEL7\", cpu:\"x86_64\", reference:\"kernel-rt-debuginfo-common-x86_64-3.10.0-693.11.1.rt56.639.el7\")) flag++;\n if (rpm_check(release:\"RHEL7\", cpu:\"x86_64\", reference:\"kernel-rt-devel-3.10.0-693.11.1.rt56.639.el7\")) flag++;\n if (rpm_check(release:\"RHEL7\", reference:\"kernel-rt-doc-3.10.0-693.11.1.rt56.639.el7\")) flag++;\n if (rpm_check(release:\"RHEL7\", cpu:\"x86_64\", reference:\"kernel-rt-kvm-3.10.0-693.11.1.rt56.639.el7\")) flag++;\n if (rpm_check(release:\"RHEL7\", cpu:\"x86_64\", reference:\"kernel-rt-kvm-debuginfo-3.10.0-693.11.1.rt56.639.el7\")) flag++;\n if (rpm_check(release:\"RHEL7\", cpu:\"x86_64\", reference:\"kernel-rt-trace-3.10.0-693.11.1.rt56.639.el7\")) flag++;\n if (rpm_check(release:\"RHEL7\", cpu:\"x86_64\", reference:\"kernel-rt-trace-debuginfo-3.10.0-693.11.1.rt56.639.el7\")) flag++;\n if (rpm_check(release:\"RHEL7\", cpu:\"x86_64\", reference:\"kernel-rt-trace-devel-3.10.0-693.11.1.rt56.639.el7\")) flag++;\n if (rpm_check(release:\"RHEL7\", cpu:\"x86_64\", reference:\"kernel-rt-trace-kvm-3.10.0-693.11.1.rt56.639.el7\")) flag++;\n if (rpm_check(release:\"RHEL7\", cpu:\"x86_64\", reference:\"kernel-rt-trace-kvm-debuginfo-3.10.0-693.11.1.rt56.639.el7\")) 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-rt / kernel-rt-debug / kernel-rt-debug-debuginfo / 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:35:17", "bulletinFamily": "scanner", "description": "According to the versions of the kernel packages installed, the EulerOS installation on the remote host is affected by the following vulnerabilities :\n\n - The recent speculative execution CVEs address three potential attacks across a wide variety of architectures and hardware platforms.\n\n - Note: This issue is present in hardware and cannot be fully fixed via software update. The nature of these vulnerabilities and their fixes introduces the possibility of reduced performance on patched systems.\n The performance impact depends on the hardware and the applications in place.\n\n - The first two variants abuse speculative execution to perform bounds-check bypass (CVE-2017-5753), or by utilizing branch target injection (CVE-2017-5715) to cause kernel code at an address under attacker control to execute speculatively. Collectively these are known as 'Spectre'.\n\n - Variant CVE-2017-5715 fixes require CPU microcode to update.And advise to contact hardware vendors to receive the appropriate microcode for your processor.\n\n - The third variant (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.\n Researchers have called this exploit 'Meltdown'.\n\n - Note: Upgrade and performance specifications,please see http://developer.huawei.com/ict/en/performance_update_2 .1\n\nNote that Tenable Network Security has extracted the preceding description block directly from the EulerOS security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.", "modified": "2018-11-13T00:00:00", "id": "EULEROS_SA-2018-1002.NASL", "href": "https://www.tenable.com/plugins/index.php?view=single&id=105655", "published": "2018-01-09T00:00:00", "title": "EulerOS 2.0 SP1 : kernel (EulerOS-SA-2018-1002)", "type": "nessus", "sourceData": "#\n# (C) Tenable Network Security, Inc.\n#\n\ninclude(\"compat.inc\");\n\nif (description)\n{\n script_id(105655);\n script_version(\"3.17\");\n script_cvs_date(\"Date: 2018/11/13 12:30:47\");\n\n script_cve_id(\n \"CVE-2017-5715\",\n \"CVE-2017-5753\",\n \"CVE-2017-5754\"\n );\n\n script_name(english:\"EulerOS 2.0 SP1 : kernel (EulerOS-SA-2018-1002)\");\n script_summary(english:\"Checks the rpm output for the updated packages.\");\n\n script_set_attribute(attribute:\"synopsis\", value:\n\"The remote EulerOS host is missing multiple security updates.\");\n script_set_attribute(attribute:\"description\", value:\n\"According to the versions of the kernel packages installed, the\nEulerOS installation on the remote host is affected by the following\nvulnerabilities :\n\n - The recent speculative execution CVEs address three\n potential attacks across a wide variety of\n architectures and hardware platforms.\n\n - Note: This issue is present in hardware and cannot be\n fully fixed via software update. The nature of these\n vulnerabilities and their fixes introduces the\n possibility of reduced performance on patched systems.\n The performance impact depends on the hardware and the\n applications in place.\n\n - The first two variants abuse speculative execution to\n perform bounds-check bypass (CVE-2017-5753), or by\n utilizing branch target injection (CVE-2017-5715) to\n cause kernel code at an address under attacker control\n to execute speculatively. Collectively these are known\n as 'Spectre'.\n\n - Variant CVE-2017-5715 fixes require CPU microcode to\n update.And advise to contact hardware vendors to\n receive the appropriate microcode for your processor.\n\n - The third variant (CVE-2017-5754) relies on the fact\n that, on impacted microprocessors, during speculative\n execution of instruction permission faults, exception\n generation triggered by a faulting access is suppressed\n until the retirement of the whole instruction block.\n Researchers have called this exploit 'Meltdown'.\n\n - Note: Upgrade and performance specifications,please see\n http://developer.huawei.com/ict/en/performance_update_2\n .1\n\nNote that Tenable Network Security has extracted the preceding\ndescription block directly from the EulerOS security advisory. Tenable\nhas attempted to automatically clean and format it as much as possible\nwithout introducing additional issues.\");\n # https://developer.huawei.com/ict/en/site-euleros/euleros/security-advisories/EulerOS-SA-2018-1002\n script_set_attribute(attribute:\"see_also\", value:\"http://www.nessus.org/u?704ad337\");\n script_set_attribute(attribute:\"solution\", value:\n\"Update the affected kernel 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:\"patch_publication_date\", value:\"2018/01/09\");\n\n script_set_attribute(attribute:\"plugin_type\", value:\"local\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:huawei:euleros:kernel\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:huawei:euleros:kernel-debug\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:huawei:euleros:kernel-debuginfo\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:huawei:euleros:kernel-debuginfo-common-x86_64\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:huawei:euleros:kernel-devel\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:huawei:euleros:kernel-headers\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:huawei:euleros:kernel-tools\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:huawei:euleros:kernel-tools-libs\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:huawei:euleros:perf\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:huawei:euleros:python-perf\");\n script_set_attribute(attribute:\"cpe\", value:\"cpe:/o:huawei:euleros:2.0\");\n script_set_attribute(attribute:\"plugin_publication_date\", value:\"2018/01/09\");\n script_end_attributes();\n\n script_category(ACT_GATHER_INFO);\n script_family(english:\"Huawei Local Security Checks\");\n\n script_copyright(english:\"This script is Copyright (C) 2018 and is owned by Tenable, Inc. or an Affiliate thereof.\");\n\n script_dependencies(\"ssh_get_info.nasl\");\n script_require_keys(\"Host/local_checks_enabled\", \"Host/EulerOS/release\", \"Host/EulerOS/rpm-list\", \"Host/EulerOS/sp\");\n script_exclude_keys(\"Host/EulerOS/uvp_version\");\n\n exit(0);\n}\n\ninclude(\"audit.inc\");\ninclude(\"global_settings.inc\");\ninclude(\"rpm.inc\");\n\nif (!get_kb_item(\"Host/local_checks_enabled\")) audit(AUDIT_LOCAL_CHECKS_NOT_ENABLED);\n\nrelease = get_kb_item(\"Host/EulerOS/release\");\nif (isnull(release) || release !~ \"^EulerOS\") audit(AUDIT_OS_NOT, \"EulerOS\");\nif (release !~ \"^EulerOS release 2\\.0(\\D|$)\") audit(AUDIT_OS_NOT, \"EulerOS 2.0\");\n\nsp = get_kb_item(\"Host/EulerOS/sp\");\nif (isnull(sp) || sp !~ \"^(1)$\") audit(AUDIT_OS_NOT, \"EulerOS 2.0 SP1\");\n\nuvp = get_kb_item(\"Host/EulerOS/uvp_version\");\nif (!empty_or_null(uvp)) audit(AUDIT_OS_NOT, \"EulerOS 2.0 SP1\", \"EulerOS UVP \" + uvp);\n\nif (!get_kb_item(\"Host/EulerOS/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$\") audit(AUDIT_LOCAL_CHECKS_NOT_IMPLEMENTED, \"EulerOS\", cpu);\n\nflag = 0;\n\npkgs = [\"kernel-3.10.0-229.49.1.170\",\n \"kernel-debug-3.10.0-229.49.1.170\",\n \"kernel-debuginfo-3.10.0-229.49.1.170\",\n \"kernel-debuginfo-common-x86_64-3.10.0-229.49.1.170\",\n \"kernel-devel-3.10.0-229.49.1.170\",\n \"kernel-headers-3.10.0-229.49.1.170\",\n \"kernel-tools-3.10.0-229.49.1.170\",\n \"kernel-tools-libs-3.10.0-229.49.1.170\",\n \"perf-3.10.0-229.49.1.170\",\n \"python-perf-3.10.0-229.49.1.170\"];\n\nforeach (pkg in pkgs)\n if (rpm_check(release:\"EulerOS-2.0\", sp:\"1\", reference:pkg)) flag++;\n\nif (flag)\n{\n security_report_v4(\n port : 0,\n severity : SECURITY_WARNING,\n extra : rpm_report_get()\n );\n exit(0);\n}\nelse\n{\n tested = pkg_tests_get();\n if (tested) audit(AUDIT_PACKAGE_NOT_AFFECTED, tested);\n else audit(AUDIT_PACKAGE_NOT_INSTALLED, \"kernel\");\n}\n", "cvss": {"score": 4.7, "vector": "AV:LOCAL/AC:MEDIUM/Au:NONE/C:COMPLETE/I:NONE/A:NONE/"}}, {"lastseen": "2019-02-21T01:34:58", "bulletinFamily": "scanner", "description": "An update for kernel is now available for Red Hat Enterprise Linux 6.4 Advanced 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-0018.NASL", "href": "https://www.tenable.com/plugins/index.php?view=single&id=105561", "published": "2018-01-04T00:00:00", "title": "RHEL 6 : kernel (RHSA-2018:0018) (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:0018. The text \n# itself is copyright (C) Red Hat, Inc.\n#\n\ninclude(\"compat.inc\");\n\nif (description)\n{\n script_id(105561);\n script_version(\"3.12\");\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:0018\");\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:0018) (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.4\nAdvanced 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:0018\"\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-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.4\");\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\\.4([^0-9]|$)\", string:os_ver)) audit(AUDIT_OS_NOT, \"Red Hat 6.4\", \"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:0018\";\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:\"4\", cpu:\"x86_64\", reference:\"kernel-2.6.32-358.84.2.el6\")) flag++;\n if (rpm_check(release:\"RHEL6\", sp:\"4\", cpu:\"x86_64\", reference:\"kernel-debug-2.6.32-358.84.2.el6\")) flag++;\n if (rpm_check(release:\"RHEL6\", sp:\"4\", cpu:\"x86_64\", reference:\"kernel-debug-debuginfo-2.6.32-358.84.2.el6\")) flag++;\n if (rpm_check(release:\"RHEL6\", sp:\"4\", cpu:\"x86_64\", reference:\"kernel-debug-devel-2.6.32-358.84.2.el6\")) flag++;\n if (rpm_check(release:\"RHEL6\", sp:\"4\", cpu:\"x86_64\", reference:\"kernel-debuginfo-2.6.32-358.84.2.el6\")) flag++;\n if (rpm_check(release:\"RHEL6\", sp:\"4\", cpu:\"x86_64\", reference:\"kernel-debuginfo-common-x86_64-2.6.32-358.84.2.el6\")) flag++;\n if (rpm_check(release:\"RHEL6\", sp:\"4\", cpu:\"x86_64\", reference:\"kernel-devel-2.6.32-358.84.2.el6\")) flag++;\n if (rpm_check(release:\"RHEL6\", sp:\"4\", reference:\"kernel-doc-2.6.32-358.84.2.el6\")) flag++;\n if (rpm_check(release:\"RHEL6\", sp:\"4\", reference:\"kernel-firmware-2.6.32-358.84.2.el6\")) flag++;\n if (rpm_check(release:\"RHEL6\", sp:\"4\", cpu:\"x86_64\", reference:\"kernel-headers-2.6.32-358.84.2.el6\")) flag++;\n if (rpm_check(release:\"RHEL6\", sp:\"4\", cpu:\"x86_64\", reference:\"perf-2.6.32-358.84.2.el6\")) flag++;\n if (rpm_check(release:\"RHEL6\", sp:\"4\", cpu:\"x86_64\", reference:\"perf-debuginfo-2.6.32-358.84.2.el6\")) flag++;\n if (rpm_check(release:\"RHEL6\", sp:\"4\", cpu:\"x86_64\", reference:\"python-perf-2.6.32-358.84.2.el6\")) flag++;\n if (rpm_check(release:\"RHEL6\", sp:\"4\", cpu:\"x86_64\", reference:\"python-perf-debuginfo-2.6.32-358.84.2.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-debug / kernel-debug-debuginfo / kernel-debug-devel / 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:36:04", "bulletinFamily": "scanner", "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": "2019-01-15T00:00:00", "id": "AIX_IJ03036.NASL", "href": "https://www.tenable.com/plugins/index.php?view=single&id=106316", "published": "2018-01-25T00:00:00", "title": "AIX 7.2 TL 2 : spectre_meltdown (IJ03036) (Meltdown) (Spectre)", "type": "nessus", "sourceData": "#\n# (C) Tenable Network Security, Inc.\n#\n# The text in the description was extracted from AIX Security\n# Advisory spectre_meltdown_advisory.asc.\n#\n\ninclude(\"compat.inc\");\n\nif (description)\n{\n script_id(106316);\n script_version(\"1.7\");\n script_cvs_date(\"Date: 2019/01/15 15:17:26\");\n\n script_cve_id(\"CVE-2017-5715\", \"CVE-2017-5753\", \"CVE-2017-5754\");\n script_xref(name:\"IAVA\", value:\"2018-A-0019\");\n script_xref(name:\"IAVA\", value:\"2018-A-0020\");\n\n script_name(english:\"AIX 7.2 TL 2 : spectre_meltdown (IJ03036) (Meltdown) (Spectre)\");\n script_summary(english:\"Check for APAR IJ03036\");\n\n script_set_attribute(\n attribute:\"synopsis\", \n value:\"The remote AIX host is missing a security patch.\"\n );\n script_set_attribute(\n attribute:\"description\", \n value:\n\"Systems with microprocessors utilizing speculative execution and indirect\nbranch prediction may allow unauthorized disclosure of information to an\nattacker with local user access via a side-channel analysis.\"\n );\n # http://aix.software.ibm.com/aix/efixes/security/spectre_meltdown_advisory.asc\n script_set_attribute(\n attribute:\"see_also\",\n value:\"http://www.nessus.org/u?0ecfba9a\"\n );\n script_set_attribute(\n attribute:\"solution\", \n value:\"Install the appropriate interim fix.\"\n );\n script_set_cvss_base_vector(\"CVSS2#AV:L/AC:M/Au:N/C:C/I:N/A:N\");\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_attribute(attribute:\"cvss_score_source\", value:\"CVE-2017-5715\");\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:\"cpe:/o:ibm:aix:7.2\");\n\n script_set_attribute(attribute:\"vuln_publication_date\", value:\"2018/01/25\");\n script_set_attribute(attribute:\"patch_publication_date\", value:\"2018/01/25\");\n script_set_attribute(attribute:\"in_the_news\", value:\"true\");\n script_set_attribute(attribute:\"generated_plugin\", value:\"former\");\n script_set_attribute(attribute:\"plugin_publication_date\", value:\"2018/01/25\");\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) 2019 and is owned by Tenable, Inc. or an Affiliate thereof.\");\n script_family(english:\"AIX Local Security Checks\");\n\n script_dependencies(\"ssh_get_info.nasl\");\n script_require_keys(\"Host/AIX/lslpp\", \"Host/local_checks_enabled\", \"Host/AIX/version\");\n\n exit(0);\n}\n\n\n\ninclude(\"audit.inc\");\ninclude(\"global_settings.inc\");\ninclude(\"aix.inc\");\ninclude(\"misc_func.inc\");\n\nif ( ! get_kb_item(\"Host/local_checks_enabled\") ) audit(AUDIT_LOCAL_CHECKS_NOT_ENABLED);\nif ( ! get_kb_item(\"Host/AIX/version\") ) audit(AUDIT_OS_NOT, \"AIX\");\nif ( ! get_kb_item(\"Host/AIX/lslpp\") ) audit(AUDIT_PACKAGE_LIST_MISSING);\n\nif ( get_kb_item(\"Host/AIX/emgr_failure\" ) ) exit(0, \"This iFix check is disabled because : \"+get_kb_item(\"Host/AIX/emgr_failure\") );\n\nflag = 0;\n\nif (aix_check_ifix(release:\"7.2\", ml:\"02\", sp:\"00\", patch:\"IJ03036m1a\", package:\"bos.mp64\", minfilesetver:\"7.2.2.0\", maxfilesetver:\"7.2.2.0\") < 0) flag++;\nif (aix_check_ifix(release:\"7.2\", ml:\"02\", sp:\"01\", patch:\"IJ03036m1a\", package:\"bos.mp64\", minfilesetver:\"7.2.2.0\", maxfilesetver:\"7.2.2.0\") < 0) flag++;\n\nif (flag)\n{\n if (report_verbosity > 0) security_warning(port:0, extra:aix_report_get());\n else security_warning(0);\n exit(0);\n}\nelse audit(AUDIT_HOST_NOT, \"affected\");\n", "cvss": {"score": 4.7, "vector": "AV:LOCAL/AC:MEDIUM/Au:NONE/C:COMPLETE/I:NONE/A:NONE/"}}, {"lastseen": "2019-02-21T01:35:30", "bulletinFamily": "scanner", "description": "The SUSE Linux Enterprise 11 SP4 kernel was updated to receive various security and bugfixes. This update is only provided as a fix update for IBM Z platform.\n\n - CVE-2017-5753 / 'Spectre Attack': IBM Z fixes were included but not enabled in the previous update. This update enables those fixes.\n\n - CVE-2017-5715 / 'Spectre Attack': IBM Z fixes were already included in the previous update. A bugfix for the patches has been applied on top.\n\n - CVE-2017-5754: The IBM Z architecture is not affected by the 'Meltdown' attack.\n\nNote that Tenable Network Security has extracted the preceding description block directly from the SUSE 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": "SUSE_SU-2018-0069-1.NASL", "href": "https://www.tenable.com/plugins/index.php?view=single&id=105765", "published": "2018-01-12T00:00:00", "title": "SUSE SLES12 Security Update : kernel (SUSE-SU-2018:0069-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 SUSE update advisory SUSE-SU-2018:0069-1.\n# The text itself is copyright (C) SUSE.\n#\n\ninclude(\"compat.inc\");\n\nif (description)\n{\n script_id(105765);\n script_version(\"3.9\");\n script_cvs_date(\"Date: 2018/12/01 13:19:04\");\n\n script_cve_id(\"CVE-2017-5715\", \"CVE-2017-5753\", \"CVE-2017-5754\");\n script_xref(name:\"IAVA\", value:\"2018-A-0019\");\n script_xref(name:\"IAVA\", value:\"2018-A-0020\");\n\n script_name(english:\"SUSE SLES12 Security Update : kernel (SUSE-SU-2018:0069-1) (Meltdown) (Spectre)\");\n script_summary(english:\"Checks rpm output for the updated packages.\");\n\n script_set_attribute(\n attribute:\"synopsis\", \n value:\"The remote SUSE host is missing one or more security updates.\"\n );\n script_set_attribute(\n attribute:\"description\", \n value:\n\"The SUSE Linux Enterprise 11 SP4 kernel was updated to receive various\nsecurity and bugfixes. This update is only provided as a fix update\nfor IBM Z platform.\n\n - CVE-2017-5753 / 'Spectre Attack': IBM Z fixes were\n included but not enabled in the previous update. This\n update enables those fixes.\n\n - CVE-2017-5715 / 'Spectre Attack': IBM Z fixes were\n already included in the previous update. A bugfix for\n the patches has been applied on top.\n\n - CVE-2017-5754: The IBM Z architecture is not affected by\n the 'Meltdown' attack.\n\nNote that Tenable Network Security has extracted the preceding\ndescription block directly from the SUSE 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://bugzilla.suse.com/show_bug.cgi?id=1068032\"\n );\n script_set_attribute(\n attribute:\"see_also\",\n value:\"https://www.suse.com/security/cve/CVE-2017-5715/\"\n );\n script_set_attribute(\n attribute:\"see_also\",\n value:\"https://www.suse.com/security/cve/CVE-2017-5753/\"\n );\n # https://www.suse.com/support/update/announcement/2018/suse-su-20180069-1/\n script_set_attribute(\n attribute:\"see_also\",\n value:\"http://www.nessus.org/u?fbd883d8\"\n );\n script_set_attribute(\n attribute:\"solution\", \n value:\n\"To install this SUSE Security Update use YaST online_update.\nAlternatively you can run the command listed for your product :\n\nSUSE Linux Enterprise Software Development Kit 12-SP2:zypper in -t\npatch SUSE-SLE-SDK-12-SP2-2018-48=1\n\nSUSE Linux Enterprise Server 12-SP2:zypper in -t patch\nSUSE-SLE-SERVER-12-SP2-2018-48=1\n\nSUSE Linux Enterprise High Availability 12-SP2:zypper in -t patch\nSUSE-SLE-HA-12-SP2-2018-48=1\n\nTo bring your system up-to-date, use 'zypper patch'.\"\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:novell:suse_linux:kernel-default\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:novell:suse_linux:kernel-default-base\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:novell:suse_linux:kernel-default-base-debuginfo\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:novell:suse_linux:kernel-default-debuginfo\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:novell:suse_linux:kernel-default-debugsource\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:novell:suse_linux:kernel-default-devel\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:novell:suse_linux:kernel-default-man\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:novell:suse_linux:kernel-syms\");\n script_set_attribute(attribute:\"cpe\", value:\"cpe:/o:novell:suse_linux:12\");\n\n script_set_attribute(attribute:\"patch_publication_date\", value:\"2018/01/11\");\n script_set_attribute(attribute:\"in_the_news\", value:\"true\");\n script_set_attribute(attribute:\"plugin_publication_date\", value:\"2018/01/12\");\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:\"SuSE Local Security Checks\");\n\n script_dependencies(\"ssh_get_info.nasl\");\n script_require_keys(\"Host/local_checks_enabled\", \"Host/cpu\", \"Host/SuSE/release\", \"Host/SuSE/rpm-list\");\n\n exit(0);\n}\n\n\ninclude(\"audit.inc\");\ninclude(\"global_settings.inc\");\ninclude(\"rpm.inc\");\n\n\nif (!get_kb_item(\"Host/local_checks_enabled\")) audit(AUDIT_LOCAL_CHECKS_NOT_ENABLED);\nrelease = get_kb_item(\"Host/SuSE/release\");\nif (isnull(release) || release !~ \"^(SLED|SLES)\") audit(AUDIT_OS_NOT, \"SUSE\");\nos_ver = eregmatch(pattern: \"^(SLE(S|D)\\d+)\", string:release);\nif (isnull(os_ver)) audit(AUDIT_UNKNOWN_APP_VER, \"SUSE\");\nos_ver = os_ver[1];\nif (! ereg(pattern:\"^(SLES12)$\", string:os_ver)) audit(AUDIT_OS_NOT, \"SUSE SLES12\", \"SUSE \" + os_ver);\n\nif (!get_kb_item(\"Host/SuSE/rpm-list\")) audit(AUDIT_PACKAGE_LIST_MISSING);\n\ncpu = get_kb_item(\"Host/cpu\");\nif (isnull(cpu)) audit(AUDIT_UNKNOWN_ARCH);\nif (cpu !~ \"^i[3-6]86$\" && \"x86_64\" >!< cpu && \"s390x\" >!< cpu) audit(AUDIT_LOCAL_CHECKS_NOT_IMPLEMENTED, \"SUSE \" + os_ver, cpu);\nif (cpu >!< \"s390x\") audit(AUDIT_ARCH_NOT, \"s390x\", cpu);\n\n\nsp = get_kb_item(\"Host/SuSE/patchlevel\");\nif (isnull(sp)) sp = \"0\";\nif (os_ver == \"SLES12\" && (! ereg(pattern:\"^(2)$\", string:sp))) audit(AUDIT_OS_NOT, \"SLES12 SP2\", os_ver + \" SP\" + sp);\n\n\nflag = 0;\nif (rpm_check(release:\"SLES12\", sp:\"2\", cpu:\"s390x\", reference:\"kernel-default-4.4.103-92.59.1\")) flag++;\nif (rpm_check(release:\"SLES12\", sp:\"2\", cpu:\"s390x\", reference:\"kernel-default-base-4.4.103-92.59.1\")) flag++;\nif (rpm_check(release:\"SLES12\", sp:\"2\", cpu:\"s390x\", reference:\"kernel-default-base-debuginfo-4.4.103-92.59.1\")) flag++;\nif (rpm_check(release:\"SLES12\", sp:\"2\", cpu:\"s390x\", reference:\"kernel-default-debuginfo-4.4.103-92.59.1\")) flag++;\nif (rpm_check(release:\"SLES12\", sp:\"2\", cpu:\"s390x\", reference:\"kernel-default-debugsource-4.4.103-92.59.1\")) flag++;\nif (rpm_check(release:\"SLES12\", sp:\"2\", cpu:\"s390x\", reference:\"kernel-default-devel-4.4.103-92.59.1\")) flag++;\nif (rpm_check(release:\"SLES12\", sp:\"2\", cpu:\"s390x\", reference:\"kernel-default-man-4.4.103-92.59.1\")) flag++;\nif (rpm_check(release:\"SLES12\", sp:\"2\", cpu:\"s390x\", reference:\"kernel-syms-4.4.103-92.59.1\")) flag++;\n\n\nif (flag)\n{\n if (report_verbosity > 0) security_warning(port:0, extra:rpm_report_get());\n else security_warning(0);\n exit(0);\n}\nelse\n{\n tested = pkg_tests_get();\n if (tested) audit(AUDIT_PACKAGE_NOT_AFFECTED, tested);\n else audit(AUDIT_PACKAGE_NOT_INSTALLED, \"kernel\");\n}\n", "cvss": {"score": 4.7, "vector": "AV:LOCAL/AC:MEDIUM/Au:NONE/C:COMPLETE/I:NONE/A:NONE/"}}, {"lastseen": "2019-02-21T01:35:07", "bulletinFamily": "scanner", "description": "From Red Hat Security Advisory 2018:0008 :\n\nAn update for kernel is now available for Red Hat Enterprise Linux 6.\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": "ORACLELINUX_ELSA-2018-0008.NASL", "href": "https://www.tenable.com/plugins/index.php?view=single&id=105599", "published": "2018-01-05T00:00:00", "title": "Oracle Linux 6 : kernel (ELSA-2018-0008) (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:0008 and \n# Oracle Linux Security Advisory ELSA-2018-0008 respectively.\n#\n\nif (NASL_LEVEL < 3000) exit(0);\n\ninclude(\"compat.inc\");\n\nif (description)\n{\n script_id(105599);\n script_version(\"3.12\");\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:0008\");\n script_xref(name:\"IAVA\", value:\"2018-A-0019\");\n script_xref(name:\"IAVA\", value:\"2018-A-0020\");\n\n script_name(english:\"Oracle Linux 6 : kernel (ELSA-2018-0008) (Meltdown) (Spectre)\");\n script_summary(english:\"Checks rpm output for the updated packages\");\n\n script_set_attribute(\n attribute:\"synopsis\", \n value:\"The remote Oracle Linux host is missing one or more security updates.\"\n );\n script_set_attribute(\n attribute:\"description\", \n value:\n\"From Red Hat Security Advisory 2018:0008 :\n\nAn update for kernel is now available for Red Hat Enterprise Linux 6.\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 script_set_attribute(\n attribute:\"see_also\",\n value:\"https://oss.oracle.com/pipermail/el-errata/2018-January/007436.html\"\n );\n script_set_attribute(\n attribute:\"solution\", \n value:\"Update the affected kernel packages.\"\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:oracle:linux:kernel\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:oracle:linux:kernel-abi-whitelists\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:oracle:linux:kernel-debug\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:oracle:linux:kernel-debug-devel\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:oracle:linux:kernel-devel\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:oracle:linux:kernel-doc\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:oracle:linux:kernel-firmware\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:oracle:linux:kernel-headers\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:oracle:linux:perf\");\n script_set_attribute(attribute:\"cpe\", value:\"p-cpe:/a:oracle:linux:python-perf\");\n script_set_attribute(attribute:\"cpe\", value:\"cpe:/o:oracle:linux:6\");\n\n script_set_attribute(attribute:\"vuln_publication_date\", value:\"2018/01/04\");\n script_set_attribute(attribute:\"patch_publication_date\", value:\"2018/01/04\");\n script_set_attribute(attribute:\"plugin_publication_date\", value:\"2018/01/05\");\n script_set_attribute(attribute:\"in_the_news\", value:\"true\");\n script_set_attribute(attribute:\"generated_plugin\", value:\"current\");\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-2019 and is owned by Tenable, Inc. or an Affiliate thereof.\");\n script_family(english:\"Oracle Linux Local Security Checks\");\n\n script_dependencies(\"ssh_get_info.nasl\");\n script_require_keys(\"Host/local_checks_enabled\", \"Host/OracleLinux\", \"Host/RedHat/release\", \"Host/RedHat/rpm-list\");\n\n exit(0);\n}\n\n\ninclude(\"audit.inc\");\ninclude(\"global_settings.inc\");\ninclude(\"rpm.inc\");\n\n\nif (!get_kb_item(\"Host/local_checks_enabled\")) audit(AUDIT_LOCAL_CHECKS_NOT_ENABLED);\nif (!get_kb_item(\"Host/OracleLinux\")) audit(AUDIT_OS_NOT, \"Oracle Linux\");\nrelease = get_kb_item(\"Host/RedHat/release\");\nif (isnull(release) || !eregmatch(pattern: \"Oracle (?:Linux Server|Enterprise Linux)\", string:release)) audit(AUDIT_OS_NOT, \"Oracle Linux\");\nos_ver = eregmatch(pattern: \"Oracle (?:Linux Server|Enterprise Linux) .*release ([0-9]+(\\.[0-9]+)?)\", string:release);\nif (isnull(os_ver)) audit(AUDIT_UNKNOWN_APP_VER, \"Oracle Linux\");\nos_ver = os_ver[1];\nif (! ereg(pattern:\"^6([^0-9]|$)\", string:os_ver)) audit(AUDIT_OS_NOT, \"Oracle Linux 6\", \"Oracle Linux \" + 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$\") audit(AUDIT_LOCAL_CHECKS_NOT_IMPLEMENTED, \"Oracle Linux\", cpu);\n\nflag = 0;\nif (rpm_exists(release:\"EL6\", rpm:\"kernel-2.6.32\") && rpm_check(release:\"EL6\", reference:\"kernel-2.6.32-696.18.7.el6\")) flag++;\nif (rpm_exists(release:\"EL6\", rpm:\"kernel-abi-whitelists-2.6.32\") && rpm_check(release:\"EL6\", reference:\"kernel-abi-whitelists-2.6.32-696.18.7.el6\")) flag++;\nif (rpm_exists(release:\"EL6\", rpm:\"kernel-debug-2.6.32\") && rpm_check(release:\"EL6\", reference:\"kernel-debug-2.6.32-696.18.7.el6\")) flag++;\nif (rpm_exists(release:\"EL6\", rpm:\"kernel-debug-devel-2.6.32\") && rpm_check(release:\"EL6\", reference:\"kernel-debug-devel-2.6.32-696.18.7.el6\")) flag++;\nif (rpm_exists(release:\"EL6\", rpm:\"kernel-devel-2.6.32\") && rpm_check(release:\"EL6\", reference:\"kernel-devel-2.6.32-696.18.7.el6\")) flag++;\nif (rpm_exists(release:\"EL6\", rpm:\"kernel-doc-2.6.32\") && rpm_check(release:\"EL6\", reference:\"kernel-doc-2.6.32-696.18.7.el6\")) flag++;\nif (rpm_exists(release:\"EL6\", rpm:\"kernel-firmware-2.6.32\") && rpm_check(release:\"EL6\", reference:\"kernel-firmware-2.6.32-696.18.7.el6\")) flag++;\nif (rpm_exists(release:\"EL6\", rpm:\"kernel-headers-2.6.32\") && rpm_check(release:\"EL6\", reference:\"kernel-headers-2.6.32-696.18.7.el6\")) flag++;\nif (rpm_check(release:\"EL6\", reference:\"perf-2.6.32-696.18.7.el6\")) flag++;\nif (rpm_check(release:\"EL6\", cpu:\"x86_64\", reference:\"python-perf-2.6.32-696.18.7.el6\")) flag++;\n\n\nif (flag)\n{\n if (report_verbosity > 0) security_warning(port:0, extra:rpm_report_get());\n else security_warning(0);\n exit(0);\n}\nelse\n{\n tested = pkg_tests_get();\n if (tested) audit(AUDIT_PACKAGE_NOT_AFFECTED, tested);\n else audit(AUDIT_PACKAGE_NOT_INSTALLED, \"affected kernel\");\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/"}}], "securelist": [{"lastseen": "2018-05-15T21:13:49", "bulletinFamily": "blog", "description": "\n\n## Targeted attacks and malware campaigns\n\n### Skygofree: sophisticated mobile surveillance\n\nIn January, we uncovered a sophisticated mobile implant that provides attackers with remote control of infected Android devices. The malware, called [Skygofree](<https://securelist.com/skygofree-following-in-the-footsteps-of-hackingteam/83603/>) (after one of the domains it uses), is a targeted cyber-surveillance tool that has been in development since 2014. The malware is spread by means of spoofed web pages that mimic leading mobile providers. The campaign is ongoing and our telemetry indicates that there have been several victims, all in Italy. We feel confident that the developer of Skygofree is an Italian IT company that works on surveillance solutions.\n\n[](<https://media.kasperskycontenthub.com/wp-content/uploads/sites/43/2018/05/07110447/180507-malware-report-q1-18-1.png>)\n\nThe latest version of Skygofree includes functionality that has so far not been seen in the wild. Features include the ability to eavesdrop on conversations when the victim moves into a specific location; using Accessibility Services to capture WhatsApp messages and the ability to force an infected device to Wi-Fi networks controlled by the attackers. The malware includes multiple exploits for root access and is capable of stealing pictures and videos, capturing call records, SMS, geo-location, calendar events and business-related data stored in the device's memory. The Skygofree implant puts itself in the list of 'protected apps', so that it doesn't get switched off when the screen is off (this is to work around a battery-saving technique that has been implemented by one of the top device vendors.)\n\nOur investigation also uncovered several spyware tools for Windows that form an implant for stealing sensitive data from a target computer. The version we found was created at the start of 2017: at the moment, we do not know if this implant has been used in the wild.\n\nSince then we have also found a version for iOS that uses a rogue [MDM](<https://en.wikipedia.org/wiki/Mobile_device_management>) (Mobile Device Management) server in order to infect devices.\n\n### Olympic Destroyer\u2026 but who did the 'destroying'?\n\nThe issue of attribution was thrown into sharp relief following the malware attack on the Olympic infrastructure just before the opening of the games in February. [Olympic Destroyer](<https://securelist.com/olympicdestroyer-is-here-to-trick-the-industry/84295/>) shut down display monitors, killed Wi-Fi and took down the Olympics web site \u2013 preventing visitors from to printing tickets. The attack also affected other organizations in the region \u2013 for example, ski gates and ski lifts were disabled at several South Korean ski resorts.\n\nOlympic Destroyer is a network worm, the main purpose of which is to deliver and start a wiper payload that tries to destroy files on remote network shares in the following 60 minutes. In the meantime, the main module collects user passwords from the browser and Windows storage and crafts a new generation of the worm that contains old and freshly-collected compromised credentials. This new generation worm is pushed to accessible local network computers and starts using the PsExec tool, drawing on the stolen credentials and current user privileges. Once the wiper has run for 60 minutes it cleans Windows event logs, resets backups, deletes shadow copies from the file system, disables the recovery item in the Windows boot menu, disables all services on the system and reboots the computer. Those files on the network shares that it was able to wipe within 60 minutes remain destroyed. The malware doesn't use any persistence and even contains protection against recurring reinfection.\n\n[](<https://media.kasperskycontenthub.com/wp-content/uploads/sites/43/2018/05/07110500/180507-malware-report-q1-18-2.png>)\n\nOne of the most notable aspects of this incident was the 'attribution hell' that followed. In the days after the attack, research teams and media companies around the world variously attributed the attack to Russia, China and North Korea \u2013 based on a number of features previously attributed to cyber-espionage and sabotage groups allegedly based in these countries or working for the governments of these countries.\n\nOur own researchers were also trying to understand which group was behind the attack. At one stage during our research, we discovered something that seemed to indicate that the Lazarus group was behind the attack. We found a unique trace left by the attackers that exactly matched a previously known Lazarus malware component. However, the lack of obvious motive and inconsistencies with known Lazarus TTPs (tactics, techniques and procedures) that we found during our on-site investigation at a compromised facility in South Korea led us to look again at this artefact. When we did so, we discovered that the set of features didn't match the code \u2013 it had been forged to perfectly match the fingerprint used by Lazarus. So we concluded that the 'fingerprint' was a very sophisticated false flag, intentionally placed inside the malware in order to give threat hunters the impression that they had found a 'smoking gun' and diverting them from a more accurate attribution.\n\nThe problems associated with attribution must be taken seriously. Given how politicised cyberspace has recently become, incorrect attribution could lead to severe consequences; and it's possible that threat actors might try to manipulate the opinion of the security community in order to influence the geo-political agenda.\n\n### Sofacy turns eastwards\n\nSofacy (aka APT28, Fancy Bear and Tsar Team) is a highly active and prolific cyber-espionage group that Kaspersky Lab has been tracking for many years. In February, we published an [overview of Sofacy activities in 2017](<https://securelist.com/a-slice-of-2017-sofacy-activity/83930/>), revealing a gradual moved away from NATO-related targets at the start of 2017, towards targets in the Middle East, Central Asia and beyond. Sofacy uses spear-phishing and watering-hole attacks to steal information, including account credentials, sensitive communications and documents. This threat actor also makes use of zero-day vulnerabilities to deploy its malware\n\nSofacy uses different tools for different target profiles. Early in 2017, the group's 'Dealer's Choice' campaign was used to target military and diplomatic organizations (mainly in NATO countries and Ukraine).\n\n[](<https://media.kasperskycontenthub.com/wp-content/uploads/sites/43/2018/05/07110512/180507-malware-report-q1-18-3.png>)\n\nLater in the year, the group used other tools from its arsenal, 'Zebrocy' and 'SPLM', to target a broader range of organizations, including science and engineering centers and press services, with more of a focus on Central Asia and the Far East.\n\n[](<https://media.kasperskycontenthub.com/wp-content/uploads/sites/43/2018/05/07110525/180507-malware-report-q1-18-4.png>)\n\nSophisticated threat actors such as Sofacy continually develop the tools they use. The group maintains a high level of operational security and focuses on making its malware hard to detect. In the case of groups such as Sofacy, once any signs of their activity have been found in a network, it's important to review logins and unusual administrator access on systems, thoroughly scan and sandbox incoming attachments, and maintain two-factor authentication for services such as e-mail and VPN access. The use of [APT intelligence reports](<https://www.kaspersky.co.uk/enterprise-security/apt-intelligence-reporting>), threat hunting tools such as [YARA](<https://en.wikipedia.org/wiki/YARA>) and advanced detection solutions such as [KATA](<https://www.kaspersky.co.uk/enterprise-security/anti-targeted-attack-platform>) (Kaspersky Anti Targeted Attack Platform) will help you to understand their targeting and provide powerful ways of detecting their activities.\n\nOur research shows that Sofacy is not the only threat actor operating in the Far East and this sometimes results in a target [overlap between very different threat actors](<https://securelist.com/masha-and-these-bears/84311/>). We have seen cases where Sofacy's Zebrocy malware has competed for access to victim's computers with the Russian-speaking Mosquito Turla clusters; and where its SPLM backdoor has competed with the traditional Turla and Chinese-speaking Danti attacks. The shared targets included government administration, technology, science and military-related organizations in or from Central Asia.\n\nThe most intriguing overlap is probably that between Sofacy and the English-speaking threat actor behind The Lamberts. The connection was discovered after researchers detected the presence of Sofacy on a server that threat intelligence had previously identified as compromised by Grey Lambert malware. The server belongs to a Chinese conglomerate that designs and manufactures aerospace and air defense technologies. However, in this case the original SPLM delivery vector remains unknown. This raises a number of hypothetical possibilities, including the fact that Sofacy could be using a new and as yet undetected exploit or a new strain of its backdoor, or that Sofacy somehow managed to harness Grey Lambert's communication channels to download its malware. It could even be a false flag, planted during the previous Lambert infection. We think that the most likely answer is that an unknown new PowerShell script or legitimate but vulnerable web app was exploited to load and execute the SPLM code.\n\n### Slingshot: a route[r] into the network\n\nOne of the presentations at this year's Kaspersky [Security Analyst Summit](<https://sas.kaspersky.com/>) was a report on a sophisticated cyber-espionage platform that has targeted victims in the Middle East and Africa since 2012.\n\n[Slingshot](<https://securelist.com/apt-slingshot/84312/>) uses an unusual (and, as far as we know, unique) attack vector. Many of the victims were attacked by means of compromised MikroTik routers. The exact method for compromising the routers is not clear, but the attackers have found a way to add a malicious DLL to the device. This DLL is a downloader for other malicious files that are then stored on the router. When a system administrator logs in to configure the router, the router's management software downloads and runs a malicious module on the administrator's computer.\n\nSlingshot loads a number of modules onto the victim's computer, including two huge and powerful ones: Cahnadr, a kernel mode module, and GollumApp, a user mode module. The two modules are connected and support each other in gathering information, persistence and data exfiltration. GollumApp is the most sophisticated of the modules: it contains nearly 1,500 user-code functions and provides most of the routines for persistence, file system control and C2 (Command-and-Control) communications. Cahnadr (also known as NDriver) contains low-level routines for network, IO operations and so on. Its kernel-mode program is able to execute malicious code without crashing the whole file system or causing a blue screen \u2013 a remarkable achievement. Cahnadr, written in pure C language, provides full access to the hard drive and operating memory, notwithstanding device security restrictions, and carries out integrity control of various system components to avoid debugging and security detection.\n\nSlingshot incorporates a number of techniques to help it evade detection. These include encrypting all strings in its modules, calling system services directly in order to bypass security-product hooks, using a number of anti-debugging techniques and selecting which process to inject depending on the installed and running security solution processes.\n\n**Further information on target**ed** attack activity in the first quarter of 2018 can be found in the **[**APT trends report for Q1 2018.**](<https://securelist.com/apt-trends-report-q1-2018/85280/>)\n\n## Malware stories\n\n### A Spectre is haunting Europe \u2013 and anywhere else with vulnerable CPUs\n\nTwo severe vulnerabilities affecting Intel CPUs were reported early in 2018. Dubbed 'Meltdown' and 'Spectre', they respectively allow an attacker to read memory from any process and from its own process. The vulnerabilities have been around since at least 2011.\n\nRumours of a new attack on Intel CPUs emerged at the start of December 2017 when e-mails on the [LKML](<https://en.wikipedia.org/wiki/Linux_kernel_mailing_list>) (Linux kernel mailing list) appeared about adding the [KAISER](<https://en.wikipedia.org/wiki/Kernel_page-table_isolation>) patches to the Linux kernel. These patches, designed to separate the user address space from the kernel address space, were originally intended to 'close all hardware side channels on kernel address information'. It was the impact of this seemingly drastic measure, with its clear performance impact, that had prompted the rumours.\n\nThis attack, now known as Meltdown (CVE-2017-5754), is able to read data from any process on the host system. While code execution is required, this can be obtained in various ways \u2013 for example, through a software bug or by visiting a malicious website that loads JavaScript code that executes the Meltdown attack. This means that all the data residing in memory (passwords, encryption keys, PINs, etc.) could be read if the vulnerability is exploited properly. Meltdown affects most Intel CPUs and some ARM CPUs.\n\nVendors were quick to publish patches for the most popular operating systems. The Microsoft update, released on 3 January, was not compatible with all anti-virus programs \u2013 possibly resulting in a BSoD (Blue Screen of Death) on incompatible systems. So updates could only be installed if an anti-virus product had first set a specific registry key, to indicate that there were no compatibility problems.\n\nSpectre (CVE-2017-5753 and CVE-2017-5715) is slightly different. Unlike Meltdown, this attack also works on other architectures (such as AMD and ARM). Also, Spectre is only able to read the memory space of the exploited process, and not that of any process. More importantly, aside from some counter-measures in some browsers, no universal solution is readily available for Spectre.\n\nIt became clear in the weeks following the reports of the vulnerabilities that they are not easily fixable. Spectre in particular opened new ways of exploitation that might affect different software in the months and years to come. Most of the released patches have reduced the attack surface, mitigating against known ways of exploiting them, but do not eradicate it completely. Since the problem is fundamental to the working of the vulnerable CPUs, it's likely that vendors will have to deal with new ways of exploiting the vulnerabilities for years to come.\n\n### O smart new world\u2026\n\nThese days we're surrounded by smart devices. This includes everyday household objects such as TVs, smart meters, thermostats, baby monitors and children's toys. But it also includes cars, medical devices, CCTV cameras and parking meters. We're even seeing the emergence of smart cities. However, this offers a greater attack surface to anyone looking to take advantage of security weaknesses \u2013 for whatever purpose. Securing traditional computers is difficult. But things are more problematic with the Internet of Things, where lack of standardization leaves developers able to ignore security, or to consider it as an afterthought. There are plenty of examples to illustrate this.\n\nWe've looked before at vulnerabilities in smart devices around the home. But some of our researchers recently explored the possibility that a [smart hub might be vulnerable to attack](<https://securelist.com/iot-hack-how-to-break-a-smart-home-again/84092/>). A smart hub lets you control the operation of other smart devices in the home, receiving information and issuing commands. Smart hubs might be controlled through a touch screen, or through a mobile app or web interface. If it's vulnerable, it would potentially provide a single point of failure. While the smart hub our researchers investigated didn't contain significant vulnerabilities, there were logical mistakes that were enough to allow our researchers to obtain remote access.\n\nResearchers at Kaspersky Lab ICS CERT recently [checked a popular smart camera](<https://securelist.com/somebodys-watching-when-cameras-are-more-than-just-smart/84309/>), to see how well protected it is from hackers. Smart cameras are now part of everyday life. Many now connect to the cloud, allowing someone to monitor what's happening at a remote location \u2013to check on pets, for security surveillance, etc. The model our researchers investigated is marketed as an all-purpose tool \u2013 suitable for use as a baby monitor, or as part of a security system. The camera is able to see in the dark, follow a moving object, stream footage to a smartphone or tablet and play back sound through a built-in speaker. Unfortunately, the camera turned out to have 13 vulnerabilities \u2013 almost as many as it has features \u2013 that could allow an attacker to change the administrator password, execute arbitrary code on the device, build a botnet of compromised cameras or stop it functioning completely.\n\nBefore buying any connected device, it's important to keep security in mind.\n\n * Consider if you really need the device. If you do, check the functions available and disable any that you don't need, to reduce your attack surface.\n * Look online for information about any vulnerabilities that have been reported.\n * Check to see if it's possible to update the firmware on the device.\n * Always change the default password and replace it with a unique, complex password.\n * Don't share serial numbers, IP addresses and other sensitive data relating to the device online.\n\nYou can use the [free Kaspersky IoT Scanner](<https://www.kaspersky.com/blog/kaspersky-iot-scanner/18449/>) to check your Wi-Fi network and tell you if the devices connected to it are safe.\n\nPotential problems are not limited to consumer devices. Recently, Ido Naor, a researcher from our Global Research and Analysis Team and Amihai Neiderman, then at Azimuth Security, [discovered a vulnerability in an automation device for a gas station](<https://securelist.com/expensive-gas/83542/>). This device was directly connected to the Internet and was responsible for managing every component of the station, including fuel dispensers and payment terminals. Even more alarming, the web interface for the device was accessible with default credentials. Further investigation revealed that it was possible to shut down all fueling systems, cause fuel a leakage, change the price, circumvent the payment terminal (in order to steal money), capture vehicle license plates and driver identities, execute code on the controller unit and even move freely across the gas station network.\n\nIt's no less important for vendors to improve their security approach to ensure that security is considered when products are being designed. Kaspersky Lab, as a member of the ITU-T Study Group 20, was a contributor to the development of [Recommendation ITU-T T.4806](<https://www.itu.int/ITU-T/recommendations/rec.aspx?rec=13391&lang=en>), designed to classify security issues, examine potential threats and determine how cyber-security measures can support the safe execution of IoT systems tasks. This applies mostly to safety-critical IoT systems such as industrial automation, automotive systems, transportation, smart cities, and wearable and standalone medical devices.\n\n### IoT-medicine under siege\n\nTechnology is driving improvements in healthcare. It has the power to transform the quality and reduce the cost of health and care services. It can also give patients and citizens more control over their care, empower carers and support the development of new medicines and treatments. However, new healthcare technologies and mobile working practices are producing more data than ever before, at the same time providing more opportunities for data to be lost or stolen. We've highlighted the issues several times over the last few years \u2013 for example, in the articles '[Hospitals are under attack in 2016](<https://securelist.com/hospitals-are-under-attack-in-2016/74249/>)', '[The mistakes of smart medicine](<https://securelist.com/the-mistakes-of-smart-medicine/77855/>)' and '[Connected medicine and its diagnosis](<https://securelist.com/connected-medicine-and-its-diagnosis/81857/>)'.\n\nThe number of medical data breaches continues to increase:\n\n[](<https://media.kasperskycontenthub.com/wp-content/uploads/sites/43/2018/05/07110535/180507-malware-report-q1-18-5.png>)\n\nOver the last year we've continued to track the activities of cybercriminals, looking at how they penetrate medical networks, how they find data on publicly available medical resources and how they exfiltrate it. This includes open ports:\n\n[](<https://media.kasperskycontenthub.com/wp-content/uploads/sites/43/2018/05/07110543/180507-malware-report-q1-18-6.png>)\n\nAnd the services that sit behind them:\n\n[](<https://media.kasperskycontenthub.com/wp-content/uploads/sites/43/2018/05/07110553/180507-malware-report-q1-18-7.png>)\n\nMore than 60 per cent of medical organizations had some kind of malware on their computers:\n\n[](<https://media.kasperskycontenthub.com/wp-content/uploads/sites/43/2018/05/07110602/180507-malware-report-q1-18-8.png>)\n\nWe saw even more attacks on organizations closely connected to hospitals, clinics and doctors \u2013 that is, in the pharmaceutical industry:\n\n[](<https://media.kasperskycontenthub.com/wp-content/uploads/sites/43/2018/05/07110611/180507-malware-report-q1-18-9.png>)\n\nIt's vital that medical facilities remove all nodes that process personal medical data, update software and remove applications that are no longer needed, and do not connect expensive medical equipment to the main LAN. You can find more detailed tips [here](<https://securelist.com/connected-medicine-and-its-diagnosis/81857/>).\n\n### Crypto-currency mining is the new black\n\nIn the legitimate economy, capital tends to flow into areas where it will be most profitable. It's no different with cybercrime. Malware development is focused in areas that are likely to be more lucrative. So it's no surprise that, as crypto-currencies become a mainstream feature of society, we've seen a [growth in the number of malicious crypto-currency miners](<https://securelist.com/mining-is-the-new-black/84232/>). In 2017, we blocked malicious [miners](<https://securelist.com/threats/mining-cryptocurrency-glossary/ ?utm_source=securelist&utm_medium=blog&utm_campaign=termin-explanation>) on the computers of 2.7 million Kaspersky Lab customers \u2013 compared to 1.87 million in 2016. This is now beginning to eclipse ransomware as a way of making money illegally.\n\n[](<https://media.kasperskycontenthub.com/wp-content/uploads/sites/43/2018/05/07110622/180507-malware-report-q1-18-10.png>)\n\nAs the name suggests, crypto-currency miners are programs designed to hijack the victim's CPU in order to mine crypto-currencies. Like ransomware, the business model is simple: infect victim's computer, use the processing power of their [CPU](<https://en.wikipedia.org/wiki/Central_processing_unit>) or [GPU](<https://en.wikipedia.org/wiki/Graphics_processing_unit>) to generate coins and earn real-world money through legal exchanges and transactions. Unlike ransomware, it's not obvious to the victim that they are infected \u2013 most people seldom use most of their computer's processing power; and miners harness the 70 to 80 per cent that is not being used for anything else.\n\nCrypto-miners are installed \u2013 on the computers of consumers and businesses alike \u2013 alongside adware, cracked games and pirated content. It's becoming easy for cybercriminals to create miners, because of ready to use partner programs, open mining pools and miner-builders. Another method is web mining, where cybercriminals insert a script into a compromised web site that mines crypto-currencies while the victim browses the site. Other criminal groups are more selective, using exploits to install miners on the servers of large companies, rather than trying to infect lots of individuals.\n\nSome of the ways cybercriminals install malicious miners in the network of corporate victims are very sophisticated, resembling the methods of APT attackers. Our researchers identified a case where the attackers used a process-hollowing technique. The infection starts with the download of a potentially unwanted application (PUA) that contains the miner. This miner installer drops the legitimate Windows utility 'msiexec' with a random name, which downloads and executes a malicious module from a remote server. The next step is to install a malicious scheduler task that drops the body of the miner. This executes the legitimate system process and uses a process-hollowing technique whereby the legitimate process code is switched for malicious code. A special system critical flag is set for this new process: if the victim tries to kill this process, Windows reboots.\n\n[](<https://media.kasperskycontenthub.com/wp-content/uploads/sites/43/2018/05/07110631/180507-malware-report-q1-18-11.png>) \n[](<https://media.kasperskycontenthub.com/wp-content/uploads/sites/43/2018/05/07110639/180507-malware-report-q1-18-12.png>)\n\nUsing such techniques, we estimate that mining botnets generated more than $7,000,000 in the second half of 2017.\n\nYou can find tips on securing businesses from malicious miners [here](<https://www.kaspersky.com/blog/miners-threaten-your-business/21482/>).\n\n### Our data in their hands\n\nPersonal data is valuable. This is evident from the regular news reports of data breaches. These include the [theft of huge amounts of data](<https://www.reuters.com/article/us-under-armour-databreach/under-armour-says-150-million-myfitnesspal-accounts-breached-idUSKBN1H532W>) and the [re-use of stolen credentials](<http://www.theregister.co.uk/2018/04/11/great_western_rail_password_reset/>). However, the recent [scandal involving the use, by Cambridge Analytica, of Facebook data](<https://www.theguardian.com/commentisfree/2018/apr/16/how-many-people-data-cambridge-analytica-facebook>) is a reminder that personal information is not just valuable to cybercriminals.\n\nIn many cases, personal data is the price people pay to obtain a product or service \u2013 'free' browsers, 'free' e-mail accounts, 'free' social network accounts, etc. But not always. Increasingly, we're surrounded by smart devices that are capable of gathering details on the minutiae of our lives. Earlier this year, one [journalist turned her apartment into a smart home in order to measure how much data was being collected by the firms that made the devices](<http://www.bbc.co.uk/news/technology-43747421>). Since we generally pay for such devices, the harvesting of data can hardly be seen as the price we pay for the benefits they bring in these cases.\n\nThe issues surrounding security and privacy of data continue to make headlines, not least as we approach 25 May, 2018 and the implementation of the EU General Data Protection Regulation. It will, of course, be interesting to see what impact the legislation has. But we should not forget that we should all consider what data we share, with whom, and how it might be used. It's vital to take steps to secure our data, by using unique, complex passwords for each account and by using two-factor authentication where it's available.", "modified": "2018-05-14T10:00:08", "published": "2018-05-14T10:00:08", "id": "SECURELIST:7CF4DDEB1B5407DAA24EC25BAA7A9654", "href": "https://securelist.com/it-threat-evolution-q1-2018/85469/", "type": "securelist", "title": "IT threat evolution Q1 2018", "cvss": {"score": 4.7, "vector": "AV:LOCAL/AC:MEDIUM/Au:NONE/C:COMPLETE/I:NONE/A:NONE/"}}], "suse": [{"lastseen": "2018-01-22T18:53:35", "bulletinFamily": "unix", "description": "The SUSE Linux Enterprise 11 SP3 LTSS kernel was updated to receive\n various security and bugfixes.\n\n This update is only provided as a fix update for IBM Z platform.\n\n - CVE-2017-5753 / "Spectre Attack": IBM Z fixes were included but not\n enabled in the previous update. This update enables those fixes.\n - CVE-2017-5715 / "Spectre Attack": IBM Z fixes were already included in\n the previous update. A bugfix for the patches has been applied on top.\n - CVE-2017-5754: The IBM Z architecture is not affected by the "Meltdown"\n attack.\n\n", "modified": "2018-01-22T15:08:49", "published": "2018-01-22T15:08:49", "href": "http://lists.opensuse.org/opensuse-security-announce/2018-01/msg00051.html", "id": "SUSE-SU-2018:0171-1", "title": "Security update for the Linux Kernel (important)", "type": "suse", "cvss": {"score": 4.7, "vector": "AV:LOCAL/AC:MEDIUM/Au:NONE/C:COMPLETE/I:NONE/A:NONE/"}}, {"lastseen": "2018-01-18T18:53:15", "bulletinFamily": "unix", "description": "The SUSE Linux Enterprise 11 SP4 kernel was updated to receive various\n security and bugfixes.\n\n This update is only provided as a fix update for IBM Z platform.\n\n - CVE-2017-5753 / "Spectre Attack": IBM Z fixes were included but not\n enabled in the previous update. This update enables those fixes.\n - CVE-2017-5715 / "Spectre Attack": IBM Z fixes were already included in\n the previous update. A bugfix for the patches has been applied on top.\n - CVE-2017-5754: The IBM Z architecture is not affected by the "Meltdown"\n attack.\n\n", "modified": "2018-01-18T15:10:57", "published": "2018-01-18T15:10:57", "href": "http://lists.opensuse.org/opensuse-security-announce/2018-01/msg00046.html", "id": "SUSE-SU-2018:0131-1", "title": "Security update for the Linux Kernel (important)", "type": "suse", "cvss": {"score": 4.7, "vector": "AV:LOCAL/AC:MEDIUM/Au:NONE/C:COMPLETE/I:NONE/A:NONE/"}}, {"lastseen": "2018-01-11T22:52:40", "bulletinFamily": "unix", "description": "The SUSE Linux Enterprise 11 SP4 kernel was updated to receive various\n security and bugfixes.\n\n This update is only provided as a fix update for IBM Z platform.\n\n - CVE-2017-5753 / "Spectre Attack": IBM Z fixes were included but not\n enabled in the previous update. This update enables those fixes.\n - CVE-2017-5715 / "Spectre Attack": IBM Z fixes were already included in\n the previous update. A bugfix for the patches has been applied on top.\n - CVE-2017-5754: The IBM Z architecture is not affected by the "Meltdown"\n attack.\n\n", "modified": "2018-01-11T18:10:26", "published": "2018-01-11T18:10:26", "href": "http://lists.opensuse.org/opensuse-security-announce/2018-01/msg00034.html", "id": "SUSE-SU-2018:0069-1", "type": "suse", "title": "Security update for the Linux Kernel (important)", "cvss": {"score": 4.7, "vector": "AV:LOCAL/AC:MEDIUM/Au:NONE/C:COMPLETE/I:NONE/A:NONE/"}}], "centos": [{"lastseen": "2019-01-23T15:51:57", "bulletinFamily": "unix", "description": "**CentOS Errata and Security Advisory** CESA-2018:0008\n\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.\n\n**Merged security bulletin from advisories:**\nhttp://lists.centos.org/pipermail/centos-announce/2018-January/022701.html\n\n**Affected packages:**\nkernel\nkernel-abi-whitelists\nkernel-debug\nkernel-debug-devel\nkernel-devel\nkernel-doc\nkernel-firmware\nkernel-headers\nperf\npython-perf\n\n**Upstream details at:**\n", "modified": "2018-01-04T19:46:26", "published": "2018-01-04T19:46:26", "id": "CESA-2018:0008", "href": "http://lists.centos.org/pipermail/centos-announce/2018-January/022701.html", "title": "kernel, perf, python security update", "type": "centos", "cvss": {"score": 4.7, "vector": "AV:LOCAL/AC:MEDIUM/Au:NONE/C:COMPLETE/I:NONE/A:NONE/"}}], "qualysblog": [{"lastseen": "2019-01-23T20:50:13", "bulletinFamily": "blog", "description": "In light of the recently released information about two security vulnerabilities, Qualys has considered the impact on the Qualys Cloud Platform and associated services. Qualys [released a detailed advisory](<https://blog.qualys.com/securitylabs/2018/01/03/processor-vulnerabilities-meltdown-and-spectre>) for customers of the Qualys Cloud Platform to help customers identify these vulnerabilities and to assist customers in their internal security assessment. \n\nBelow, please find information about how Qualys has performed its assessment and is taking steps to protect its environment and the Qualys Cloud Platform:\n\n### **About Meltdown and Spectre**\n\n[Meltdown](<https://meltdownattack.com/>) (CVE-2017-5754) and[ Spectre](<https://spectreattack.com/>) (CVE-2017-5715 and CVE-2017-5753) exploit physical implementations of modern microprocessors, rather than relying on any software-based flaw or defect.\n\n### **Impact**\n\nAs of this writing, there is no known exploit for these vulnerabilities. Qualys is in the process of assessing and patching our environment. Additionally, we have increased our security monitoring posture to identify unusual activity. We are leveraging the Qualys Cloud Platform to identify impacted assets.\n\n#### **Scanner Appliances**\n\nQualys scanner appliances are not directly affected by Spectre/Meltdown vulnerabilities and do not require any patches to the appliance operating system, scanning software or virtual scanner images. The security of Qualys scanner appliances does not depend on the type of privilege separation which is affected by these vulnerabilities, and the vulnerabilities would not provide a potential attacker with a higher level of access. Additionally appliances are only bound to the Qualys Cloud Platform and have no ability to be accessed directly.\n\n#### **Virtual Scanner Appliances**\n\nQualys virtual scanner appliances can still be indirectly affected by Spectre/Meltdown if the vulnerability is exploitable at the hypervisor level. We recommend that customers patch the underlying hypervisor as per their vendor recommendations.\n\n#### **Cloud Agent**\n\nCloud Agent binary across all platforms is not directly impacted and as such does not require any patch from Qualys. However it is essential that customers ensure the underlying asset operating systems are patched by customers as per vendor recommendations.\n\nThe Cloud Agent [can be used to assess this](<https://blog.qualys.com/technology/2018/01/05/visualizing-spectre-meltdown-impact-and-remediation-progress>). \n\n#### **Qualys Cloud Platform**\n\nCurrently, we are testing the vendor released patches and are deploying across our shared environment. Please note that may require a scheduled emergency downtime.\n\n#### **Qualys Private Cloud Platform**\n\n#### Hardware Private Cloud Platform\n\nQualys will closely coordinate with customers to individually assess their platform and deploy patches on the platform and underlying infrastructure on a mutually agreed schedule.\n\n#### Virtual Private Cloud Platform\n\nQualys will closely coordinate with customers to deploy patches on the platform. Customers are responsible for deploying patches to the underlying infrastructure and should immediately work with their vendors to deploy patches.\n\n#### **Qualys Corporate Environment**\n\nQualys has tested and pushed out patches to our corporate servers and is currently aggressively rolling out patches to our end-user machines.", "modified": "2018-01-09T02:36:19", "published": "2018-01-09T02:36:19", "id": "QUALYSBLOG:F8AA5B21D90BCDD30391A24D6FD47892", "href": "https://blog.qualys.com/securitylabs/2018/01/08/meltdown-spectre-and-qualys-cloud-platform", "type": "qualysblog", "title": "Meltdown/Spectre and Qualys Cloud Platform", "cvss": {"score": 4.7, "vector": "AV:LOCAL/AC:MEDIUM/Au:NONE/C:COMPLETE/I:NONE/A:NONE/"}}, {"lastseen": "2019-01-23T20:50:13", "bulletinFamily": "blog", "description": "Apple has been all over InfoSec news in the past week or so, along with Spectre / Meltdown developments, a tax season scam alert from the feds, and an apparent solution to the Winter Olympics' hack whodunit. In addition, researchers warned about a new trend of using Memcached servers to significantly boost DDoS attacks, as GitHub became a victim of this new tactic.\n\n### Apple under siege\n\n_A digital forensics vendor claims it can crack iOS devices, including the iPhone X, pictured here. (Photo credit: Apple)_\n\nThe second half of February was intense for Apple on the security front. A digital forensics vendor claimed having the ability to unlock all iPhone models, including the X, while a researcher warned about a Trojan targeting MacOs computers that\u2019s not detected by anti-virus products. Oh, and Apple had to squash another one of those pesky bugs that let people crash iPhones via texting. \n\n_Unlocking iPhones_\n\nForbes dropped a news bomb on Monday when it [reported](<https://www.forbes.com/sites/thomasbrewster/2018/02/26/government-can-access-any-apple-iphone-cellebrite/#cb3ce1f667a0>) that Cellebrite recently started telling its customers -- which are primarily government, military and corporate investigative teams -- that it's able to unlock and extract data from devices running iOS 11, such the iPhone X, as well as other iPhones, iPads and iPods.\n\nWhile Cellebrite isn\u2019t publicly trumpeting this capability, anonymous sources told Forbes that in recent months the company \u201chas developed undisclosed techniques to get into iOS 11 and is advertising them to law enforcement and private forensics folk across the globe.\u201d\n\nAs Forbes noted, Cellebrite has posted a [brochure](<https://media.cellebrite.com/wp-content/uploads/2017/12/advanced-unlocking-extraction-datasheet-jan2018.pdf>) on its website where it details its ability to unlock these Apple products as well as several Android devices, and extract data from them. The way it works is that customers ship the devices to Cellebrite, where its engineers work their magic. Cellebrite can\u2019t (or won\u2019t) crack devices remotely.\n\nForbes also found a [warrant](<https://www.documentcloud.org/documents/4386077-iPhone-X-Cellebrite-Extraction.html>) that states that as part of an investigation, a research specialist from the U.S. Department of Homeland Security who received training from Cellebrite managed to extract data from a suspect's iPhone X.\n\nApple has so far offered no commentary other than to say its customers should make sure they\u2019re [running the latest iOS version](<https://threatpost.com/apple-tackles-cellebrite-unlock-claims-sort-of/130111/>), which is 11.2.6, a version whose security Cellebrite claims it can circumvent.\n\nIn the meantime, the implications for the security and privacy of iPhone users are, needless to say, enormous, as are the concerns that whatever technique and knowledge Cellebrite may possess could fall into the hands of criminals, or be independently replicated by bad actors.\n\n\u201cSuch a technique has ramifications for all users of Apple products. Because if Cellebrite has found a way to do this, the ability could also potentially be found by others -- including law enforcement agencies and dodgy authoritarian regimes,\u201d [wrote](<https://www.grahamcluley.com/phone-cracking-firm-advertises-can-unlock-iphone/>) security analyst Graham Cluley. \u201cAnd if they haven't discovered how to do it\u2026 well, they could always pay Cellebrite to do it for them.\u201d\n\nThe situation also highlights the ongoing tug-of-war between tech vendors and law enforcement agencies, as the former resist watering down encryption on their products, while the latter argue they need access to devices and data for their investigations.\n\nIn a follow-up Forbes [article](<https://www.forbes.com/sites/thomasbrewster/2018/03/01/apple-iphone-vulnerabilities-kept-secret-by-cellebrite/#6c26c22167fa>) on Thursday, Cellebrite's marketing chief sought to calm fears about his company's ability to crack iOS security, saying \"there's nothing inherent in the technology that means it's open to misuse.\"\n\nStill, there's a high level of concern among privacy and security experts. \"All of us who're walking around with this vulnerability are in danger,\" Electronic Frontier Foundation's senior staff attorney Adam Schwartz told Forbes.\n\n_MacOS targeted by RAT_\n\nBecause when it rains it pours, a researcher has sounded the alarm that a nasty remote access Trojan that targets MacOS has been around apparently for almost two years and isn\u2019t detected by AV tools.\n\nThe Trojan, called Coldroot, can, among other things, log keystrokes and steal passwords. Disconcertingly, anti-virus vendors apparently have ignored its existence even though the malware has been [available on Github](<https://www.bleepingcomputer.com/news/security/coldroot-rat-still-undetectable-despite-being-uploaded-on-github-two-years-ago/>) since late March 2016.\n\n \n\n_AV tools fail to detect the Coldroot malware that targets MacOS. (Photo credit: Digita Security)_\n\n \n\nThe warning comes from Patrick Wardle, chief research officer at Digita Security, who provided all the ugly details of the malware in a [blog post](<https://digitasecurity.com/blog/2018/02/19/coldroot/>).\n\nAs ZDnet [explains](<http://www.zdnet.com/article/coldroot-nasty-mac-trojan-went-undetected-for-years/>): \u201cThe malware when activated can record and steal passwords, list files, rename and delete files, download and upload documents, remotely view the desktop in real time, and shut down the system.\u201d\n\nWhile AV vendors update their tools to detect Coldroot, Wardle advises MacOS users to upgrade to Sierra or High Sierra, which contain a feature that blocks the malware\u2019s attempt to modify the operating system\u2019s privacy database in order to gain accessibility rights.\n\n_Texts cause iCrash_\n\nProving that bad things come in threes, Apple also had to [patch](<https://support.apple.com/en-us/HT201222>) a bug in several of its operating systems -- including iOS, WatchOS, and MacOS -- that caused app crashes and system malfunctions when a character representing a letter of India\u2019s Telugu language was displayed.\n\nCiting Apple\u2019s brief technical description of the bug, Threatpost [explained](<https://threatpost.com/apple-rushes-fix-for-latest-text-bomb-bug-as-abuse-spreads/129987/>) that the flaw occurred when affected Apple products processed a maliciously crafted string that could lead to a heap corruption. \u201cA memory corruption issue was addressed through improved input validation,\u201d the Apple advisory reads, according to Threatpost.\n\n### Memcached servers used for DDoS attacks\n\nA troubling trend is emerging in which hackers are using unprotected Memcached servers to dramatically amplify the intensity of their DDoS attacks.\n\n[Reporting on Dark Reading](<https://www.darkreading.com/attacks-breaches/memcached-servers-being-exploited-in-huge-ddos-attacks/d/d-id/1331149?>), Jai Vijayan explai
| Spectre| Meltdown
