Fault Injection Attack - Revision history

NKirnbauer: expired link changed with link from wayback machine

2024-10-10T08:12:07Z

expired link changed with link from wayback machine

← Older revision		Revision as of 08:12, 10 October 2024
Line 81:		Line 81:
	<references>		<references>
	<ref name="FI">Y. Li, M. Chen and J. Wang, "Introduction to side-channel attacks and fault attacks," 2016 Asia-Pacific International Symposium on Electromagnetic Compatibility (APEMC), 2016, pp. 573-575, doi: 10.1109/APEMC.2016.7522801.</ref>		<ref name="FI">Y. Li, M. Chen and J. Wang, "Introduction to side-channel attacks and fault attacks," 2016 Asia-Pacific International Symposium on Electromagnetic Compatibility (APEMC), 2016, pp. 573-575, doi: 10.1109/APEMC.2016.7522801.</ref>
	<ref name="FI2">https://payatu.com/blog/asmita-jha/fault-injection-basics</ref>		<ref name="FI2">http://web.archive.org/web/20210304184552/https://payatu.com/blog/asmita-jha/fault-injection-basics</ref>

	</references>		</references>

NKirnbauer: fixed link

2024-09-25T09:48:16Z

fixed link

← Older revision		Revision as of 09:48, 25 September 2024
Line 6:		Line 6:
	== Introduction ==		== Introduction ==

	Fault Injection Attack is a type of a [[Side Channel Attack]]. It is a physical attack issued on a cryptographic device or a system. Adversaries inject faults to change the normal process of a cryptographic operation. By doing this and by analyzing the generated outputs, the system security features can be bypassed or the overall system behaviour can be compromised to get secret information and keys. Usually this type of attack can be done by tempering with the voltage, the clock or the electromagnetic emissions of a system. But also optical laser injection is one technique. When it comes to the actual attack, adversaries can either choose to attack the software or the hardware of a system. The injected faults are short-lived and the are used in a differential analysis for the secrets/key stealing.<ref name="FI"/><ref name="FI2"/>		Fault Injection Attack is a type of a [[Side Channel Attacks\| Side Channel Attack]]. It is a physical attack issued on a cryptographic device or a system. Adversaries inject faults to change the normal process of a cryptographic operation. By doing this and by analyzing the generated outputs, the system security features can be bypassed or the overall system behaviour can be compromised to get secret information and keys. Usually this type of attack can be done by tempering with the voltage, the clock or the electromagnetic emissions of a system. But also optical laser injection is one technique. When it comes to the actual attack, adversaries can either choose to attack the software or the hardware of a system. The injected faults are short-lived and the are used in a differential analysis for the secrets/key stealing.<ref name="FI"/><ref name="FI2"/>

	== Attack Techniques ==		== Attack Techniques ==

NKirnbauer: fixed link

2024-09-25T09:47:32Z

fixed link

← Older revision		Revision as of 09:47, 25 September 2024
Line 6:		Line 6:
	== Introduction ==		== Introduction ==

	Fault Injection Attack is a type of a Side-Channel Attack. It is a physical attack issued on a cryptographic device or a system. Adversaries inject faults to change the normal process of a cryptographic operation. By doing this and by analyzing the generated outputs, the system security features can be bypassed or the overall system behaviour can be compromised to get secret information and keys. Usually this type of attack can be done by tempering with the voltage, the clock or the electromagnetic emissions of a system. But also optical laser injection is one technique. When it comes to the actual attack, adversaries can either choose to attack the software or the hardware of a system. The injected faults are short-lived and the are used in a differential analysis for the secrets/key stealing.<ref name="FI"/><ref name="FI2"/>		Fault Injection Attack is a type of a [[Side Channel Attack]]. It is a physical attack issued on a cryptographic device or a system. Adversaries inject faults to change the normal process of a cryptographic operation. By doing this and by analyzing the generated outputs, the system security features can be bypassed or the overall system behaviour can be compromised to get secret information and keys. Usually this type of attack can be done by tempering with the voltage, the clock or the electromagnetic emissions of a system. But also optical laser injection is one technique. When it comes to the actual attack, adversaries can either choose to attack the software or the hardware of a system. The injected faults are short-lived and the are used in a differential analysis for the secrets/key stealing.<ref name="FI"/><ref name="FI2"/>

	== Attack Techniques ==		== Attack Techniques ==

Ikramer at 12:32, 30 November 2023

2023-11-30T12:32:23Z

← Older revision		Revision as of 12:32, 30 November 2023
Line 86:		Line 86:


	[[Category:~~Basic~~]]		[[Category:Pentesting]]

SVrdoljak at 22:12, 21 December 2021

2021-12-21T22:12:15Z

← Older revision		Revision as of 22:12, 21 December 2021
Line 2:		Line 2:
	== Summary==		== Summary==

	~~'''~~Fault Injection Attacks~~'''~~ are physical attacks where adversaries try to inject malicious faults into a cryptographic device or system. By injecting faults, the usual behaviour of the cryptographic operations is changed and the erroneous outputs of the faults is analysed to steal secrets/keys or sensible information.		Fault Injection Attacks are physical attacks where adversaries try to inject malicious faults into a cryptographic device or system. By injecting faults, the usual behaviour of the cryptographic operations is changed and the erroneous outputs of the faults is analysed to steal secrets/keys or sensible information.

	== Introduction ==		== Introduction ==

	~~'''~~Fault Injection Attack~~'''~~ is a type of a ~~'''~~Side-Channel Attack~~'''~~. It is a physical attack issued on a cryptographic device or a system. Adversaries inject faults to change the normal process of a cryptographic operation. By doing this and by analyzing the generated outputs, the system security features can be bypassed or the overall system behaviour can be compromised to get secret information and keys. Usually this type of attack can be done by tempering with the voltage, the clock or the electromagnetic emissions of a system. But also optical laser injection is one technique. When it comes to the actual attack, adversaries can either choose to attack the software or the hardware of a system. The injected faults are short-lived and the are used in a differential analysis for the secrets/key stealing.<ref name="FI"/><ref name="FI2"/>		Fault Injection Attack is a type of a Side-Channel Attack. It is a physical attack issued on a cryptographic device or a system. Adversaries inject faults to change the normal process of a cryptographic operation. By doing this and by analyzing the generated outputs, the system security features can be bypassed or the overall system behaviour can be compromised to get secret information and keys. Usually this type of attack can be done by tempering with the voltage, the clock or the electromagnetic emissions of a system. But also optical laser injection is one technique. When it comes to the actual attack, adversaries can either choose to attack the software or the hardware of a system. The injected faults are short-lived and the are used in a differential analysis for the secrets/key stealing.<ref name="FI"/><ref name="FI2"/>

	== Attack Techniques ==		== Attack Techniques ==

SVrdoljak at 21:58, 21 December 2021

2021-12-21T21:58:01Z

← Older revision		Revision as of 21:58, 21 December 2021
Line 64:		Line 64:
	Currently people are researching for countermeasures against Fault Injection Attacks. Some of the countermeasures that are already used today are listed below:<ref name="FI2"/>		Currently people are researching for countermeasures against Fault Injection Attacks. Some of the countermeasures that are already used today are listed below:<ref name="FI2"/>

	- Proper shielding		* Proper shielding

	- Proper physical hardening of systems and devices		* Proper physical hardening of systems and devices

	- Fault detection mechanisms		* Fault detection mechanisms

	- Resistance against [[Side Channel Attacks]]		* Resistance against [[Side Channel Attacks]]

	- Redundancy for critical control signals		* Redundancy for critical control signals

			== Courses ==

			* [[Ausgewählte Kapitel der IT-Security]] (2021)

	== References ==		== References ==

SVrdoljak at 21:42, 21 December 2021

2021-12-21T21:42:40Z

← Older revision		Revision as of 21:42, 21 December 2021
Line 65:		Line 65:

	- Proper shielding		- Proper shielding

	- Proper physical hardening of systems and devices		- Proper physical hardening of systems and devices

	- Fault detection mechanisms		- Fault detection mechanisms

	- Resistance against [[Side Channel Attacks]]		- Resistance against [[Side Channel Attacks]]

	- Redundancy for critical control signals		- Redundancy for critical control signals

SVrdoljak at 21:42, 21 December 2021

2021-12-21T21:42:25Z

← Older revision		Revision as of 21:42, 21 December 2021
Line 62:		Line 62:
	== Countermeasures ==		== Countermeasures ==

			Currently people are researching for countermeasures against Fault Injection Attacks. Some of the countermeasures that are already used today are listed below:<ref name="FI2"/>

	~~=== Shielding ===~~		- Proper shielding
			- Proper physical hardening of systems and devices
			- Fault detection mechanisms
	~~=== Detection ===~~		- Resistance against [[Side Channel Attacks]]
			- Redundancy for critical control signals

	== References ==		== References ==

SVrdoljak at 21:38, 21 December 2021

2021-12-21T21:38:26Z

← Older revision		Revision as of 21:38, 21 December 2021
Line 58:		Line 58:
	Also known as CVE-2020-15808, is a Fault Injection Attack which uses the buffer overflow vulnerability in the CDC communicaation interface code. When this exploit is exploited, attackers can access sensitive information, keys, secrets or obtain firmware.<ref name="FI2"/>		Also known as CVE-2020-15808, is a Fault Injection Attack which uses the buffer overflow vulnerability in the CDC communicaation interface code. When this exploit is exploited, attackers can access sensitive information, keys, secrets or obtain firmware.<ref name="FI2"/>

	Reference: [https://i.blackhat.com/asia-20/Friday/asia-20-Wypych-Raiden-Glitching-Framework.pdf Black Hat Asia 2020], [https://twitter.com/horac341/status/1311911734572208129 Grzegorz Wypych] [https://github.com/IBM/raiden Raiden]		Reference: [https://i.blackhat.com/asia-20/Friday/asia-20-Wypych-Raiden-Glitching-Framework.pdf Black Hat Asia 2020], [https://twitter.com/horac341/status/1311911734572208129 Grzegorz Wypych], [https://github.com/IBM/raiden Raiden]

	== Countermeasures ==		== Countermeasures ==

SVrdoljak at 21:38, 21 December 2021

2021-12-21T21:38:11Z

← Older revision		Revision as of 21:38, 21 December 2021
Line 10:		Line 10:
	== Attack Techniques ==		== Attack Techniques ==

			Fault injection can be done using various techniques the most common ones are the following:

			# Clock Glitch
			# Voltage Glitch
			# Electromagnetic Glitch
			# Optical Injection

	=== Clock Glitch ===		=== Clock Glitch ===

			Glock glitching is a method where the system clock of a cryptographic device or system is being tampered with. Usually systems have their internally system clock. In order for the integrated circuits (ICs) to properly work and for the operations to being successfully executed, the system clock time period needs to be greater that the maximum propagation delay (including offset). Faults injected to the clock results in the attacker bypassing security checks. All it takes it the injection of short pulses in the circuit, at the right time.<ref name="FI2"/>

	=== Voltage Glitch ===		=== Voltage Glitch ===

			Voltage glitching is a method where faults are created when the systems voltage is being tampered with. The behaviour of operations is manipulated when the voltage is tampered with at specific times. This technique is a low-cost technique, because it doesn't require many additional hardware. However, the generated faults might not always be predictable, therefore attackers cannot tell when an injected fault leads to information leakage. A quite well known Fault Injection Attack called [[Plundervolt]] uses this technique.<ref name="FI2"/>

	=== Electromagnetic Glitch ===		=== Electromagnetic Glitch ===

			Electromagnetic glitching is another technique that is commonly used in Fault Injection Attacks. It is also one of the most used methods, because it not invasive. Attackers use EM probes with precisely placed X-Y tables above the EM probe. Researchers have already released information about various flaws in ESP32. <ref name="FI2"/>

	=== Optical Injection ===		=== Optical Injection ===

			Optical injection uses illumination of transistors to make a conduct in a system and to inject faults. Attackers use a laser or high energy light source such as UV lamps combined with decapsulation of the system chip. This attack results in resets of microcontroller’s internal protection fuses and results in breaking cryptographic implementation to steal secrets. <ref name="FI2"/>

	==~~= Others =~~==		== Examples ==


	== ~~Examples~~ ==		=== Espressif ESP32: Bypassing Secure Boot <ref name="FI2"/> ===

			Also known as CVE-2019-15894, is a Fault Injection Attack which bypasses the Secure Boot verification when starting a ESP32 CPU. When faults are generated. unverified code is being executed from flash. Researchers found out, that the flash encryption mitigates this attack, as unverified code cannot be executed then.<ref name="FI2"/>

			Reference: [https://www.espressif.com/en/news/Espressif_Security_Advisory_Concerning_Fault_Injection_and_Secure_Boot Espressif Advisory], [https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-15894 CVE Mitre]

			=== Espressif ESP32: Bypassing Flash Encryption <ref name="FI2"/> ===

	~~===~~ CVE-~~2019~~-~~15894 ==~~=		Also known as CVE-2020-15048, is a Fault Injection Attack which bypasses the Flash Encryption and the Secure Boot verification. When faults are generated. unverified code is being executed from flash.<ref name="FI2"/>

			Reference: [https://www.espressif.com/sites/default/files/advisory_downloads/Security%20Advisory%20CVE-2020-15048%2C%2013629%20EN%26CN.pdf Espressif Advisory], [https://raelize.com/posts/espressif-systems-esp32-bypassing-flash-encryption/ Raelize]

	=== ~~CVE-2020-15048~~ ===		=== Gigadevice GD32F130 devices: Debug interface permissions escalation <ref name="FI2"/> ===

			Also known as CVE-2020-13468, is a Fault Injection Attack which exploits the insufficiently physically protected inter-IC bonding wires. When this exploit is exploited, the debug interface permissions of the device escalate. This leads to extraction of firmware even thought there is debugging protection implemented. Attackers can also read the protected flash memory and perform random modifications on the device.<ref name="FI2"/>

	=== CVE-2020-13468 ~~===~~		Reference: [https://www.usenix.org/system/files/woot20-paper-obermaier.pdf Research Paper], [https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-13468 CVE Mitre]

			=== STM32 USB Device Library: Buffer overflow vulnerability exploit <ref name="FI2"/> ===

	~~===~~ CVE-2020-15808 ===		Also known as CVE-2020-15808, is a Fault Injection Attack which uses the buffer overflow vulnerability in the CDC communicaation interface code. When this exploit is exploited, attackers can access sensitive information, keys, secrets or obtain firmware.<ref name="FI2"/>

			Reference: [https://i.blackhat.com/asia-20/Friday/asia-20-Wypych-Raiden-Glitching-Framework.pdf Black Hat Asia 2020], [https://twitter.com/horac341/status/1311911734572208129 Grzegorz Wypych] [https://github.com/IBM/raiden Raiden]

	== Countermeasures ==		== Countermeasures ==