As it became known to the public that Meltdown and Specter bugs could attack vulnerabilities in hardware and firmware, security vulnerabilities became more alert. This article has compiled 33 particularly threatening hardware-related bugs.
In January 2018, new CPU security bugs named Meltdown and Specter were discovered, putting the entire industry in an emergency. This is because the basic concept of operating system security, which separates CPU memory into kernel space and user space, was broken by two bugs. This security flaw stems from one of the characteristics of modern CPUs, 'guess execution', and to fix the flaw, CPU makers, device makers, and operating system developers had to make some of the biggest adjustments in history.
Vulnerabilities stemming from hardware design existed before Meltdown and Specter. However, the wide range of damage that the two bugs can cause has attracted a lot of attention, especially from the security community. Academia and civilian researchers are discovering more problems than ever by studying low-level processes of operation on CPUs and other hardware components.
Some of the security vulnerabilities in hardware can be improved by releasing new components, while others can be improved by upgrading the firmware built into the hardware chip. In either case, applying a patch is not that simple, so these flaws can last a long time.
Although attention was drawn to Meltdown, hardware-related vulnerabilities continued to exist. Here's a look at some of the hardware-related vulnerabilities that are worth noting.
CPU side-channel attacks
Specter Variant 1-CVE-2017-5753
Attackers can take advantage of the latest CPU's branch prediction capabilities through CVE-2017-5753, also known as the bound check bypass. By using the CPU cache as a subchannel, information in the memory allocated to other processes is extracted. In this case, not only one process may leak important information of another process, but it may also bypass the privilege boundary between user memory and kernel memory. Intel, IBM, and some ARM CPUs are exposed to this vulnerability.
Specter Variant 2-CVE-2017-5715
Specter Variant 2 has the same impact as Variant 1 but uses a technique called branch target injection. To effectively prevent this variant of Specter, you need to update the CPU's microcode. This can be done by BIOS and UEFI updates or by the operating system.
Meltdown Variant 3-CVE-2017-5754
Meltdown bug, also called bad data cache loading (RDCL) or a third CPU speculative execution function flaw, is a vulnerability that exploits the out-of-order instruction execution function of the latest Intel CPUs. By using this vulnerability, it is possible to read the protected kernel memory across the security boundary set for each user process. To fix vulnerabilities, only the operating system needs to be updated, and this involves a more rigorous separation of kernel memory, which contains sensitive information. For example, separation can be done through mechanisms such as Linux's Kernel Page Table Separation (KPTI).
Meltdown-GP-CVE-2018-3640
Meltdown variant or variant 3a collects subchannel information using speculative reads of system registers. For this reason, it is also called Rogue System Register Read (RSRE). To prevent this, you need to update your microcode.
Meltdown-NM-CVE-2018-3665
The speculative execution flaw is related to a meltdown called LazyFP. This flaw can be used by the FP to leak the status information of the floating-point unit (FPU). The FPU is a specialized computational coprocessor used to accelerate mathematical operations and is built into Intel's latest CPUs. This vulnerability can be prevented by applying “eager” instead of a “lazy” FPU when switching processes
Specter-NG-CVE-2018-3639
This is called Specter Variant 4 or Speculative Store Bypass (SSB). The memory is forced to be shared, and then one application accesses the information of another application To fix this vulnerability, the microcode, and operating system must be updated.
Specter-PHT-CVE-2018-3693
Also known as Specter 1.1. The Specter variant utilizes a speculative store to create a speculative buffer overflow, even if software mitigations were taken on Specter, it was possible to circumvent those measures with this variant should be updated.
Meltdown -RW
Specter 1.2 vulnerability known as speculative execution is made bitter by utilizing storage overwrite a read-only code and data pointers, which should update the operating system to mitigate the violation is vulnerabilities in a software security sandbox.
Foreshadow OS - CVE-2018-3620
Fore Shadow (Foreshadow) has been named L1 terminal fault. Foreshadow is a speculative execution attack that steals information from the Intel CPU's L1 data cache. Particular attention should be paid to this attack in virtual machines that divide the same physical CPU into multiple virtual CPUs. This is because these virtual CPUs use the same L1 cache. An attacker could use this variant to extract information from the operating system or SMM (system management mode). SMM is an alternative operating mode for the CPU that exists separately from the operating system. It is designed to be used by BIOS and UEFI or low-level OEM code.
Foreshadow-VMM-CVE-2018-3646
This vulnerability, a variant of Foreshadow, affects virtual machines. It is possible that a guest operating system running on a virtual machine could use this variant to read the sensitive memory of another guest's virtual machine or hypervisor.
Foreshadow
SGX -CVE-2018-3615 A variant of Foreshadow that allows an attacker to read the enclave memory of Intel's SGX (Software Guard Extension). SGX is an execution environment provided by some Intel CPUs. Even if the operating system itself is compromised, developers can store data and safely execute code in SGX.
Meltdown-PK and Meltdown-BND
Meltdown-PK (Protection Key Bypass) and Meltdown-BND (Bound Check Bypass) are two variants of Meltdown that were announced in the academic world in November 2018. Meltdown-PK affects Intel CPUs, and Meltdown-BND affects both Intel and AMD.
These are variants of Specter that utilize the PHT (Pattern History Table) of the Specter-PHT -CA-OP, Specter-PHT-CA-IP, and Specter- PHT -SA-OP CPUs. It was found at the same time as Meltdown-PK and Meltdown-BND.
It is a variant of the Specter attack that utilizes the Specter-BTB -SA-IP and Specter- BTB -SA-OP branch target buffer (BTB). It is a Specter variant discovered by the team that discovered Meltdown-PK and Meltdown-BND in November 2018. At the time, the team concluded that "not all variants can be completely prevented with most defenses, including existing defenses."
Fall Out - CVE-2018-1226
Also known as micro-architecture store buffer data sampling (MSBDS) Fall Out is similar to the meltdown. Through this vulnerability, hackers can cross security boundaries and leak sensitive information in protected memory areas. This is one of the new types of side-channel attacks targeting the CPU. Intel calls this microarchitecture data sampling (MDS). Fallout makes both the operating system and hypervisor vulnerable and can be resolved through CPU microcode updates.
RIDL-CVE-2018-1127 and CVE-2018-1230
Microarchitectural Load Port Data Sampling (MLPDS) and Microarchitectural Fill Buffer Data Sampling (MFBDS) MDS attacks. As with Fallout, the CPU microcode must be updated to fix this vulnerability.
Zombie Road-CVE-2019-11091
Star bleed
Star bleed (Starbleed) is a design flaw in the bitstream encryption process of the Xilinx field-programmable gate array (FPGA) (Xilinx) is made. Unlike CPUs that perform computing tasks according to pre-set instructions, FPGAs are integrated circuits that allow customers to fully program their logic. Unlike general-purpose CPUs, FPGAs are specialized for one specific task and are widely used in business or safety-critical applications in areas such as aerospace, finance, and defense.
The configuration file that the customer loads into the FPGA is called a bitstream. FPGA manufacturers, like Xilinx, who account for 50% of the FPGA market, have added encryption and bitstream verification mechanisms to help protect intellectual property and other confidentiality that may be included in their customers' FPGAs. A research team studying IT security at the Horst Guerz Institute at Ruhr University in Bochum, Germany, discovered a design flaw in the bitstream security mechanisms of Xilinx 7-series and Virtex-6 FPGAs that could decrypt and fix bitstreams.
In a paper to be presented at the 29th USENIX Security Symposium, "As a result of the attack, the research team not only avoided the bitstream encryption process of all Xilinx 7-series devices but also partially secured bitstreams in Virtex-6 devices. "We could have cracked the code."
They "can also manipulate the bitstream by adjusting the HMAC. In general, setting up an out attack is the same as is common in major practice. The attacker only needs to access the field FPGA's configuration interface. Secret. The decryption key is already stored in the FPGA, for example, the key is stored in internal battery-backed RAM (BBRAM) or eFUS after the device is manufactured The attacker uses the FPGA where the key is stored as an oracle to decrypt the bitstream. I can do it."
Initiating a Starbleed attack requires access to the FPGA's hardware configuration interface. That means you need to have physical access to the device. However, some FPGAs can be programmed and reprogrammed through a separate microcontroller and connected to the network. In this case, the attack can also be executed remotely.
Because this design flaw exists in silicon, it cannot be fixed with a patch, and we have no choice but to expect it to be improved in the Xilinx FPGA successor. The company was notified of the vulnerability before the research team's paper was published and sent recommendations to the customer.
Platinum Perth
Platinum Perth (PLATYPUS) is a side-channel attack abusing the RAPL (running mean power limitation) interface that is used to measure the power consumption of the CPU core. It is present in the Intel CPU (Sandy Bridge) that appeared in 2011. This is the first differential power analysis attack that can be executed remotely to leak secrets such as cryptographic keys in Linux kernel memory and Intel SGX security enclosures.
The attack was devised by a team of researchers at the University of Birmingham in the UK and the Helmholtz Information Security Center at CISPA and was announced in November 2020. Linux kernel developers addressed the vulnerabilities CVE-2020-8694 and CVE-2020-8695 by preventing unauthorized applications from accessing RAPL energy consumption data.
However, it doesn't deal with vector privileged attacks targeting Intel Software Guard Extensions (SGX). SGX is a Trusted Execution Environment (TEE) built into the CPU, and its natural role is to securely protect important encrypted data even if the operating system is completely damaged. To prevent this attack, you need to distribute CPU microcode updates released by Intel.
In an attempt to attack Intel CPUs, the researchers warned that CPUs from other chipmakers, including AMD, Nvidia, and ARM, also have on-board energy meters that can be accessed and may be vulnerable to such attacks.
Hammer Attack Low DRAM memory (DRAM memory Rowhammer attacks)
Low hammers
Low Hammer is a physical effect that can occur when you read several times faster physically the same row of memory cells in the SDRAM chip. This effect is also called hammering. The electric charge generated by the cell in the row being hammered leaks into the adjacent row, changing the value of the cell in the row. Known as bit flip, this effect can occur because of the increased cell density of modern SDRAM chips such as DDR3 and DDR4.
The low hammer effect has been known for a long time. Members of Google's Project Zero team demonstrated for the first time in March 2015 that they could have security implications when they uncovered two cases of privilege escalation exploits using a low hammer.
Low Hammer.js
Low Hammer.js is a low hammer attack implemented using JavaScript. As long as this vulnerability exists, it has been found that remote attacks could be accomplished simply by visiting a malicious web page. Browser vendors have taken steps to mitigate this attack.
Murray drain - CVE-2016-6728
Drain Murray (Drammer) is a known low of the hammer type of attack that goes to the destination device, the Android. Memory chips in mobile devices were not considered to be in the affected area until the Drammer was discovered. This is a low hammer attack against the
Flip Feng Shui
A malicious guest virtual machine can flip a bit in physical memory and affect other virtual machines under control. The research team proved this by turning off OpenSSH public key authentication on the target virtual machine.
ECCPloit
ECCploit is an attack that shows that a low hammer type attack can occur even on SDRAM chips with error correction code (ECC) capabilities. The theory is that this type of memory commonly used in servers can prevent row hammers.
Throwhammer
Throwhammer refers to a low hammer attack that can attack the entire network by using the RDMA (Remote Direct Memory Access) function mounted on a high-speed network card similar to that used in servers.
Ram bleed
Ram bleed (RAMBleed) is the first attack claimed that it is possible that if you use a low-hammer effect seized the data from the memory cell. In the past, the low hammer attack weakened the memory integrity function through bit-flip and could induce other conditions for an attack such as elevation of privilege. Meanwhile, the rambleed attack is accomplished by using row hammering and side channels. This is because the purpose is to extract data by inferring information on adjacent memory cells. In that respect, Rambled is similar to Meltdown and Specter.
Firmware Vulnerability
With Broad Impact
Bluebone Bluebone is a vulnerability announced in 2017 during the implementation of the Bluetooth stack for Linux, Android, Windows, and macOS. It has been estimated that this vulnerability affects more than 5 billion devices. In the case of computers, the vulnerability can be fixed relatively easily by simply updating the OS. On the other hand, Bluetooth enabled smartwatches, TVs, medical devices, automotive infotainment systems, wearables, and other IoT devices require firmware updates. The researchers estimate that in 2018, a year later, more than 2 billion devices will remain exposed.
Krack
The KRACK or key reinstallation attack exploits the weaknesses of the WPA2 wireless security standard. The WPA2 wireless security standard is used to secure most wireless networks in use today. However, due to weaknesses in the standard itself, there were problems implementing WPA2 on all types of devices, including home routers and other IoT devices. Firmware updates were required to mitigate this vulnerability, and devices that have ended support remain vulnerable to this day.
Bad USB
In 2014, it turned out that a microcontroller in a USB thumb drive could be reprogrammed to spoof keyboards and other devices and then use it to control a computer or filter data. Many USB thumb drives remain under attack.
ThunderStrike and ThunderStrike 2
This refers to an attack that targets a vulnerability in the Apple MacBook's firmware to install a firmware rootkit in the process of connecting a malicious device to a Thunderbolt port. Thunder Strike 2 is damaged by a Thunderbolt device newly inserted was also making room for this worm can be active.
Thunderclap
Thunderclap is an attack that has shown that a computer equipped with a Thunderbolt port can execute privileged code.
ROCA
Corpus Miss attack returns(ROCA) is an attack targeting Infineon Technologies' Trusted Platform Module (TPM) and security chip (SE). TPMs and SEs are used in tens of millions of business computers, servers, hardware authentication tokens, and various types of smart cards, including national ID cards. RSA keys generated through various methods are increasingly vulnerable to factorization, an attack designed to recover keys. The researchers estimated that recovering individual 2048-bit RSA keys generated on multiple devices would cost about $20,000, and about $40 for 1024-bit RSA keys.
Intel Management Engine The
Intel Management Engine (ME) is a dedicated coprocessor and subsystem on several Intel CPUs and is used for out-of-band management tasks. Intel ME runs its own lightweight operating system completely separate from the user-installed operating system. For this reason, it was often referred to as a backdoor in the security community. Serious vulnerabilities have been discovered in Intel ME over the past few years, and to fix them, you need to install a firmware update from the computer manufacturer. This means that many older systems that have ended support are less likely to receive updates.
0 Comments