{{Header}} {{Title|title= Evil Maid Attack }} {{#seo: |description=Evil Maid Attack, Notes on Anti Evil Maid (AEM); adversary capabilities, AEM alternatives, security issues. |image=Evilaem123123.jpg }} {{intro| Evil Maid Attack, Notes on Anti Evil Maid (AEM); adversary capabilities, AEM alternatives, security issues. }} [[File:Evilaem123123.jpg|thumb]] = Introduction = An evil maid attack is: https://en.wikipedia.org/wiki/Evil_Maid_attack
...an attack on an unattended device, in which an attacker with physical access alters it in some undetectable way so that they can later access the device, or the data on it. The name refers to the scenario where a maid could subvert a device left unattended in a hotel room – but the concept itself also applies to situations such as a device being intercepted while in transit, or taken away temporarily by airport or law enforcement personnel.
There are two main attack methods. The 'classic' evil maid attack involves a device being left unattended and then being tampered with by the attacker. If the system is not password-protected or does not require authentication, it is simply turned on and information is accessed. If the device is password-protected -- as is the case with [[Full_Disk_Encryption|Full Disk Encryption]] -- the device firmware is compromised so a false password prompt later appears. When the victim inputs the password, it is sent to the attacker and the compromised firmware removes itself. Afterwards, the attacker returns to the unattended device in order to steal data. https://en.wikipedia.org/wiki/Evil_Maid_attack#Methods_of_attack Information can also be stolen via Direct Memory Access (DMA) attacks using hardware devices that connect directly to the physical address space. The second method is known as a network evil maid. In this case the victim's device is replaced with an identical device. If the original device only has a bootloader password, then a attacker substitutes a device with an identical bootloader password input screen. If the device has a lock screen, the attacker must also recreate the background lock screen picture to mimic the original device. After the victim inputs their password on the false device, the password is sent to the attacker who then accesses data on the original device. In 2009, security researcher Joanna Rutkowska (who coined the term "evil maid attack") demonstrated a technique against a TrueCrypt encrypted system using a small bootable USB stick image, In short the process has two steps https://www.schneier.com/blog/archives/2009/10/evil_maid_attac.html : # After accessing the shutdown computer, the attacker boots it from a separate volume. A hacked bootloader is written to the system, then shut down. # Later on the owner boots the computer and enters their encryption key. Once the disk is unlocked, the malicious bootloader can capture the key and send it over the internet, store it in a secret location and so on. An advanced adversary is likely to return again and remove any evidence of the hack. see [https://theinvisiblethings.blogspot.com/2009/10/evil-maid-goes-after-truecrypt.html here] for further details and a discussion about possible solutions. Vulnerable interfaces include: https://en.wikipedia.org/wiki/Evil_Maid_attack#Vulnerable_interfaces * Legacy BIOS: This architecture is vulnerable because the configuration is unprotected, updates and ROMs are unsigned, and secure boot is unsupported. Attackers can compromise the firmware by booting from an external drive, allowing keystrokes to be sent to remote attackers. * Unified Extensible Firmware Interface (UEFI): UEFI can mitigate evil maid attacks because a secure boot, authenticated framework is available, along with availability of Trusted Platform Module (TPM) initialization security. However, these features may be unused by platform manufacturers or the end-user, allowing exploitation. * Full disk encryption systems: Full disk encryption systems like LUKS in Debian are vulnerable because they are unable to authenticate themselves to the user. The disk contents of powered off and encrypted systems can be modified by attackers so the system's bootloader codes can steal passwords. * Thunderbolt: Many Intel Thunderbolt ports are vulnerable to DMA attacks that allow full access and the bypassing of all security features. * Any unattended devices: As noted earlier, network evil maids can replace the device with an identical model that is configured to steal the password and send it to a remote attacker. = Mitigation = In general it is inadvisable to provide potential adversaries with physical access to a device since they could remove the disk, reflash the BIOS and exfiltrate the TPM. Obviously the safest way to protect against evil maid attacks is to always have the device(s) in your possession. If this is not possible, then placing the device in a safe or lockbox might be feasible. Also consider possible scenarios where the device can be temporarily removed for inspection, like during airport security screening or by law enforcement personnel. Simpler measures that provide some protection include keeping firmware up-to-date and always shutting down unattended devices. == Detection == Various methods can be used to detect whether an unattended device has been potentially exposed or handled by nearby persons, including: https://en.wikipedia.org/wiki/Evil_maid_attack#Detection * proximity alarms * motion detectors * wireless cameras * [https://guardianproject.github.io/haven/ Haven Android application]
It is an Android application that leverages on-device sensors to provide monitoring and protection of physical areas. Haven turns any Android phone into a motion, sound, vibration and light detector, watching for unexpected guests and unwanted intruders.
Event monitoring is transmitted to the user's smartphone. * use of tamper-evident technology or low-cost solutions to detect tampering Such as the use of glitter over screw holes. If tampering is suspected, the device can be checked for possible malware. Unfortunately this is a difficult exercise and it may just be safer to discard the potentially compromised hardware. == Anti Evil Maid == To protect against compromise, it is recommended to utilize hardware with a TPM interface and to configure Anti Evil Maid (AEM) software. AEM authenticates the device to the user since it will only unlock if the correct password is entered and it determines no unauthorized code has been executed on the device. Root of trust systems like Intel's TXT technology are used for this purpose. This can avoid compromise as users are notified if any files in the /boot partition are modified; verification occurs before the password is entered. https://github.com/unman/notes/blob/master/openBSD_as_netvm It should be noted that AEM security is imperfect because it relies upon a closed source TPM. Further, in Intel's case SINIT binary modules are downloaded so that Intel Trusted Execution Technology (Intel TXT) can perform a measured and verified launch of an OS kernel. https://reposcope.com/package/intel-SINIT Although digitally signed, the download step is done without verification and the processor must then correctly verify it and perform initial steps like correct measurements of BIOS/firmware and system settings such as ACPI tables. AEM has several other limitations: Picture support may also have been deprecated. * it authenticates the machine to the user (not the user to the machine) * any BIOS changes require a reseal * full trust is placed in the CPU and BIOS * compatible with legacy boot only (incompatible with (U)EFI boot) * a TPM owner password must be set * incompatible with USB 3.0 Note that AEM has (time-based) one-time password support (OTP, TOTP; "google authenticator") ([[Two-factor authentication 2FA|2FA]]) which is a more secure configuration. It is also possible to use a USB device as the AEM device, but this has strengths and weaknesses: [https://www.qubes-os.org/doc/anti-evil-maid/ Installing and Using Anti Evil Maid (AEM) with Qubes OS]:
Qubes security guidelines dictate that USB devices should never be attached directly to dom0, since this can result in the entire system being compromised. However, in its default configuration, installing and using AEM requires attaching a USB drive (i.e., mass storage device) directly to dom0. (The other option is to install AEM to an internal disk. However, this carries significant security implications, as explained here.) This presents us with a classic security trade-off: each Qubes user must make a choice between protecting dom0 from a potentially malicious USB drive, on the one hand, and protecting the system from Evil Maid attacks, on the other hand.
 * evil maid attacks are easier because BIOS settings do not need changing * AEM on USB can be used as a keyfile (second factor), which provides a stronger yubikey * in Qubes, hiding the USB from dom0 is a more secure configuration; for example it avoids [https://acodez.in/badusb-attack/ BadUSB attacks] Despite these limitations, {{q_project_name_long}} users who have a compatible TPM are recommended to install [https://www.qubes-os.org/doc/anti-evil-maid/ AEM] in dom0. Also refer to the [https://github.com/QubesOS/qubes-antievilmaid qubes-antievilmaid README] for further security notes and information on system requirements. == Anti Evil Maid Alternatives == If AEM is unavailable, then weaker alternatives include: * Utilizing a BIOS password since an attack requires removal of the disk. Note this protection can potentially be circumvented by a master/maintenance BIOS password that might exist. * The /boot partition can also be placed on a USB; adversaries must then attack either the BIOS or USB-persistent modifications. * A cryptographic hash can be calculated for the entire disk so an integrity hash can be recalculated at a later time. This can detect if data has changed, but cannot protect against intentional tampering. https://ctf101.org/forensics/what-is-disk-imaging/ An attacker would need to attack the BIOS in this case to avoid detection. = See Also = * [https://blog.invisiblethings.org/2011/09/07/anti-evil-maid.html Invisible Things Blog: Anti Evil Maid] = Footnotes = {{reflist|close=1}} {{Footer}} [[Category:Documentation]]