Incident: Rowhammer Attack Exploits Android Phones via GLitch Technique

Published Date: 2018-05-03

Postmortem Analysis
Timeline 1. The software failure incident of the Rowhammer attack on Android phones, known as "GLitch," happened in February of the previous year, as mentioned in the article [71440].
System 1. Android phones running Snapdragon 800 and 801 systems-on-a-chip [71440]
Responsible Organization 1. Hackers - The software failure incident was caused by hackers who developed a new form of the Rowhammer attack called "GLitch" to exploit Android phones over the internet [71440].
Impacted Organization 1. Android phones [71440]
Software Causes 1. The software cause of the failure incident was the exploitation of the Rowhammer vulnerability in Android phones through a new technique called "GLitch" [71440].
Non-software Causes 1. The failure incident was caused by a hacking technique known as "Rowhammer," which manipulates the physical electric charge in memory chips to corrupt data in unexpected ways, exploiting the fundamental properties of computer hardware [71440].
Impacts 1. The software failure incident involving the Rowhammer attack known as "GLitch" impacted Android phones by allowing hackers to run malicious code remotely when victims visited specific web pages [71440]. 2. The attack exploited the GPU in Android phones to induce bit flips in memory, potentially leading to the theft of credentials or spying on browsing habits [71440]. 3. The incident highlighted vulnerabilities in older Android phones like the LG Nexus 5, HTC One M8, or LG G2, which were proven to be susceptible to the attack [71440]. 4. Google and Mozilla responded by making software changes to Chrome and Firefox browsers to block the researchers' implementation of the attack, showing the need for ongoing security updates to mitigate such vulnerabilities [71440].
Preventions 1. Implementing hardware-based solutions such as more recent forms of smartphone memory like DDR4 that offer safeguards against Rowhammer attacks by frequently refreshing memory cells to prevent electric leakage from changing their values [71440]. 2. Restricting how code like WebGL can access memory to make it harder for attackers to exploit vulnerabilities like Rowhammer [71440].
Fixes 1. Hardware-based solutions such as more recent forms of smartphone memory like DDR4 that refresh memory cells more frequently to prevent bit flips [71440].
References 1. Researchers from the VUSec research group at Vrije Universiteit in Amsterdam [71440]

Software Taxonomy of Faults

Category Option Rationale
Recurring one_organization, multiple_organization (a) The software failure incident related to the Rowhammer attack has happened again at the same organization, Vrije Universiteit in Amsterdam. Researchers from the VUSec research group at Vrije Universiteit published a paper detailing a new form of the Rowhammer attack called "GLitch," which targets Android phones [71440]. (b) The software failure incident has also happened at multiple organizations. The researchers demonstrated that the Rowhammer attack could work on Android phones, specifically targeting older phones like the LG Nexus 5, HTC One M8, or LG G2. Additionally, Google mentioned that they tested the attack on newer phones and found them to be susceptible to Rowhammer as well [71440].
Phase (Design/Operation) design (a) The software failure incident described in the articles is primarily related to the design phase. The failure is attributed to a hacking technique known as "Rowhammer," which manipulates the physical electric charge in memory chips to corrupt data in unexpected ways. This attack exploits the fundamental properties of computer hardware, making it difficult to fully fix with a software patch [71440]. The attack involves inducing bit flips in memory to change data stored there, allowing hackers to run malicious code on Android phones remotely when victims visit specific web pages. The attack targets specific hardware components like ARM processors and GPUs, demonstrating a deep understanding of the system's design vulnerabilities [71440]. (b) The software failure incident is not directly related to operation or misuse of the system. Instead, it focuses on the exploitation of hardware vulnerabilities through a sophisticated hacking technique. The attack does not rely on user operation or misuse but rather on the inherent design flaws in the system's hardware components [71440].
Boundary (Internal/External) within_system, outside_system (a) The software failure incident described in the articles is primarily within_system. The failure is related to a hacking technique known as "Rowhammer" that manipulates the physical electric charge in memory chips to corrupt data in unexpected ways. This attack exploits the fundamental properties of computer hardware, specifically memory chips, to induce bit flips and gain control over the system. The attack targets Android phones by running malicious code when a victim visits a specially crafted web page, demonstrating a vulnerability within the system's memory handling mechanisms [71440]. (b) Additionally, the articles mention that the software failure incident involves some elements that originate from outside the system. For example, the attack is executed remotely over the internet, indicating an external source initiating the attack on the Android phones. The attack leverages the GPU and a browser-based graphics code library (WebGL) to induce bit flips in memory, showcasing how external factors can be utilized to exploit vulnerabilities within the system [71440].
Nature (Human/Non-human) non-human_actions, human_actions (a) The software failure incident in the articles is primarily due to non-human actions. The incident involves a hacking technique known as "Rowhammer," which manipulates the physical electric charge in memory chips to corrupt data in unexpected ways. This attack exploits the fundamental properties of computer hardware, specifically the electric charge leakage in memory cells, to induce bit flips and gain control over the system. The attack is not caused by human actions but rather by exploiting the inherent physics of how computers function [71440]. (b) While the software failure incident is primarily due to non-human actions as described above, it is important to note that the researchers who discovered and demonstrated the GLitch attack, a new form of the Rowhammer attack, are human actors. These researchers from the VUSec research group at Vrije Universiteit in Amsterdam developed the technique to run malicious code on Android phones remotely by exploiting the Rowhammer vulnerability. Their actions in researching and developing this attack contributed to the software failure incident [71440].
Dimension (Hardware/Software) hardware, software (a) The software failure incident in the articles is primarily related to hardware. The incident involves a hacking technique known as "Rowhammer," which manipulates the physical electric charge in memory chips to corrupt data in unexpected ways. This attack exploits the fundamental properties of computer hardware, specifically memory chips, to induce bit flips and gain control over the system [71440]. (b) The software failure incident also has elements related to software. While the attack technique itself is based on hardware vulnerabilities, the researchers were able to run malicious code on Android phones by exploiting these hardware vulnerabilities remotely through a carefully crafted web page. This demonstrates a software-related vulnerability in the browser that allowed the attackers to execute code within the privileges of the browser [71440].
Objective (Malicious/Non-malicious) malicious (a) The software failure incident described in the articles is malicious in nature. The incident involves a hacking technique known as "Rowhammer" being used against Android phones over the internet by manipulating the physical electric charge in memory chips to corrupt data in unexpected ways. The attack, named "GLitch," allows hackers to run malicious code on Android phones when the victim visits a carefully crafted web page, demonstrating a remote, smartphone-targeted implementation of the Rowhammer attack [71440]. The attack is intentional and aims to exploit vulnerabilities in the system for malicious purposes.
Intent (Poor/Accidental Decisions) unknown (a) The intent of the software failure incident: - The software failure incident related to the Rowhammer attack on Android phones was not due to poor decisions but rather due to exploiting the physical properties of computer hardware to manipulate memory and induce bit flips [71440].
Capability (Incompetence/Accidental) accidental (a) The software failure incident described in the articles is not related to development incompetence. The incident involves a sophisticated hacking technique known as "Rowhammer" being used against Android phones over the internet, exploiting the physical properties of computer hardware to induce bit flips in memory and run malicious code on smartphones remotely [71440]. (b) The software failure incident is accidental in nature as it involves hackers finding a way to use the Rowhammer attack against Android phones by manipulating the physical electric charge in memory chips to corrupt data in unexpected ways. This attack was not caused by incompetence but rather by exploiting the actual physics inherent in how computers function [71440].
Duration temporary The software failure incident described in the articles is more aligned with a **temporary** failure rather than a permanent one. This is evident from the fact that the attack described, known as "GLitch," is a specific technique that exploits the Rowhammer vulnerability in Android phones by inducing bit flips in memory to run malicious code on the device. The attack is detailed as a new form of the Rowhammer attack and requires a specific pattern of bit flips to gain control over the browser when a victim visits a crafted web page. The attack is also limited to certain older Android phones and the Firefox browser, indicating a specific set of circumstances under which it can be executed [71440].
Behaviour value, other (a) crash: The articles do not mention any instances of a crash related to the software failure incident. [71440] (b) omission: The software failure incident does not involve the system omitting to perform its intended functions at an instance(s). [71440] (c) timing: The software failure incident does not involve the system performing its intended functions correctly, but too late or too early. [71440] (d) value: The software failure incident involves the system performing its intended functions incorrectly. The Rowhammer attack manipulates the physical electric charge in memory chips to corrupt data in unexpected ways, inducing bit flips in memory to change ones to zeros and vice versa, leading to running malicious code on Android phones when victims visit a carefully crafted web page. This results in the system performing its functions incorrectly. [71440] (e) byzantine: The software failure incident does not involve the system behaving erroneously with inconsistent responses and interactions. [71440] (f) other: The software failure incident involves the system behaving in a way not described in the options (a to e). The attack exploits the most fundamental properties of computer hardware by manipulating the physical electric charge in memory chips to corrupt data in unexpected ways, leading to running malicious code on Android phones remotely when victims visit a specific web page. This behavior is not a typical failure mode like a crash, omission, timing, or byzantine behavior. [71440]

IoT System Layer

Layer Option Rationale
Perception None None
Communication None None
Application None None

Other Details

Category Option Rationale
Consequence harm, theoretical_consequence (a) unknown (b) unknown (c) unknown (d) unknown (e) unknown (f) unknown (g) no_consequence (h) theoretical_consequence (i) harm: The software failure incident did not result in any real observed consequences, but there were discussions about potential harm and vulnerabilities that could be exploited in the future. The attack demonstrated by the researchers could potentially lead to stealing credentials or spying on browsing habits, but it did not result in any actual harm at the time of the article. The potential for harm was highlighted by researchers and experts in the field, indicating that such attacks could become more sophisticated and pose a threat to Android devices in the future [71440].
Domain information, finance, other (a) The failed system was related to the information industry as it involved a hacking technique known as "Rowhammer" that manipulates the physical electric charge in memory chips to corrupt data [71440]. The attack exploited the fundamental properties of computer hardware, making it difficult to fully fix with a software patch. (h) The incident also has implications for the finance industry as it involved a remote, smartphone-targeted implementation of the Rowhammer attack, potentially allowing hackers to steal credentials or spy on browsing habits [71440]. (m) The incident could have implications for other industries not explicitly mentioned in the options, as the attack targeted Android phones and exploited vulnerabilities in the hardware and software systems of these devices [71440].

Sources

Back to List