https://feed.craftedsignal.io/tags/efi/Trending threats, MITRE ATT&CK coverage, and detection metadata — refreshed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioFri, 26 Jan 2024 12:00:00 +0000https://feed.craftedsignal.io/briefs/2024-01-efi-bootloader-modification/Fri, 26 Jan 2024 12:00:00 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2024-01-efi-bootloader-modification/A process writing to critical EFI bootloader files (bootmgfw.efi or bootx64.efi) within the \EFI\Boot\ directory may indicate a bootkit installation, malicious code persistence at the firmware level, or tampering with the system boot process.This detection identifies suspicious activity related to the modification of EFI bootloader files on Windows systems. The EFI bootloader files, specifically bootmgfw.efi and bootx64.efi located in the \EFI\Boot\ directory, are critical components responsible for initializing the Windows Boot Manager during system startup. Modification or replacement of these files is highly unusual under normal circumstances. Such activity may indicate an attacker’s attempt to install a bootkit, establish persistence for malicious code at the firmware level, or otherwise compromise the integrity of the system’s boot process. The referenced HybridPetya ransomware and CVE-2024-7344 highlight the real-world threat of bootloader modification for malicious purposes.

Attack Chain

1. Initial access is gained through an existing vulnerability or compromised account.
2. The attacker escalates privileges to obtain necessary permissions to modify system files.
3. The attacker locates the EFI bootloader files (bootmgfw.efi or bootx64.efi) in the \EFI\Boot\ directory.
4. The attacker modifies the bootloader file, potentially injecting malicious code or replacing it with a compromised version.
5. The system is rebooted, and the modified bootloader executes, initiating the malicious payload.
6. The malicious payload gains control early in the boot process, bypassing security measures.
7. The attacker achieves persistence, allowing them to maintain control over the system even after reboots.

Impact

Successful modification of the EFI bootloader can result in a complete compromise of the affected system. Attackers can use this technique to install persistent malware, bypass security measures, and potentially gain control over the entire network. This can lead to data theft, system disruption, and other malicious activities. While specific victim numbers are unavailable, the criticality of the boot process means any successful attack can have severe consequences.

Recommendation

• Enable Sysmon Event ID 11 logging to monitor file creation events and activate the provided Sigma rule.
• Deploy the Sigma rule Windows EFI Bootloader File Modification to your SIEM and tune it for your environment to detect bootloader modifications.
• Review the references provided, including the Bleeping Computer article and the ESET research on CVE-2024-7344, for additional context on bootloader attacks.
• Investigate any alerts generated by this rule immediately, as they could indicate a serious compromise.

]]>highadvisorybootkitpersistenceefibootloaderwindowshttps://feed.craftedsignal.io/briefs/2024-01-03-efi-volume-mount/Wed, 03 Jan 2024 15:00:00 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2024-01-03-efi-volume-mount/Detection of attempts to mount the EFI volume on Windows systems using mountvol.exe, potentially leading to system compromise.This detection identifies attempts to mount the EFI volume on Windows systems using the mountvol.exe utility. The EFI system partition (ESP) is a special partition crucial for system booting. Unauthorized modification of the ESP can compromise system integrity, allowing attackers to modify the system on boot. This technique is associated with attacks like PKFail. The scope of this threat involves potential compromise of Windows systems and the ability to modify the boot process for malicious purposes, affecting system integrity and security. The detection leverages process monitoring to identify suspicious use of mountvol.exe.

Attack Chain

1. An attacker gains initial access to the system, potentially through social engineering or exploitation of a vulnerability.
2. The attacker executes mountvol.exe with the -S or /S parameter to mount the EFI volume.
3. The attacker gains write access to the EFI system partition.
4. The attacker modifies bootloaders or other EFI executables.
5. The attacker may install malicious drivers or backdoors into the EFI partition.
6. The system is rebooted, triggering the malicious code within the EFI partition.
7. The malicious code compromises the operating system during the boot process.
8. The attacker achieves persistence and control over the system.

Impact

Successful exploitation can lead to persistent malware installation, allowing attackers to maintain control over the compromised system even after reboots or OS reinstalls. The impact includes potential data theft, system corruption, and the ability to install rootkits that are difficult to detect. If successful, the attacker can gain complete control over the system.

Recommendation

• Deploy the Sigma rule Detect EFI Volume Mount via Mountvol to your SIEM and tune for your environment.
• Monitor process execution logs for instances of mountvol.exe being executed with the -S or /S parameters.
• Investigate any alerts generated by the Sigma rule, paying close attention to the parent processes and user accounts involved.
• Implement strict access controls on the EFI system partition to prevent unauthorized modifications.
• Regularly scan systems for signs of EFI-based rootkits or other malicious modifications.

]]>highadvisoryefimountvolwindowspersistencedefense-evasion