/LeechCore-plugins

Plugins related to LeechCore

Primary LanguageCGNU General Public License v3.0GPL-3.0

LeechCore Plugins

This repository contains various plugins for LeechCore - Physical Memory Acquisition Library.

Plugins are related to various kinds of device drivers allowing for modular extensive memory acquisition in various scenarios.

Table of Contents

leechcore_ft601_driver_linux

Authors:

  • Ulf Frisk
  • Jérémie Boutoille from Synacktiv - www.synacktiv.com
  • Based on PCIeScreamer kernel driver from LambdaConcept.

Supported Platforms:

  • Linux

Overview:

The leechcore_ft601_driver_linux library allows applications access to a limited version of API calls the FT601 FTD3XX.dll Windows library from ftdichip provided. This allows applications to use a limited FTD3XX.dll compatible application library on Linux. This library does not require LeechCore to function and may be used in other applications as well.

The library requires libusb (apt-get install libusb-1.0-0) and access to the usb device (permission change or run as root may be required) alternatively a Kernel Driver provided by LambdaConcept. LeechCore will automatically attempt to locate the kernel driver before using libusb as fallback.

Installation instructions:

Place leechcore_ft601_driver_linux.so alongside leechcore.so.

leechcore_device_hvsavedstate

Authors:

Supported Platforms:

  • Windows

Overview:

The leechcore_device_hvsavedstate library allows applications access to a access the memory of Hyper-V saved state files (.vmrs). The library depends on the vmsavedstatedumpprovider.dll library from Microsoft. It must be placed in the same folder as the LeechCore. The library exists in the most recent Windows SDK and is usually found in the location: C:\Program Files (x86)\Windows Kits\10\bin\10.0.17763.0\x64\vmsavedstatedumpprovider.dll.

Installation instructions:

Place leechcore_device_hvsavedstate.dll and vmsavedstatedumpprovider.dll alongside leechcore.dll.

leechcore_device_rawtcp

Authors:

Supported Platforms:

  • Windows, Linux

Overview:

Allows LeechCore to connect to a "raw tcp" server which may be used to perform DMA attacks against a compromised iLO interface as described in the blog entry by Synacktiv amongst other things.

Installation instructions:

Place leechcore_device_rawtcp.[so|dll] alongside leechcore.[so|dll].

leechcore_device_microvmi

Authors

Supported Platforms

  • Linux

Overview

Allows LeechCore to peek into the live physical memory of virtual machines supported by libmicrovmi

Requirements

Plugin documentation

  • URL device syntax: microvmi://param1=value1&param2=value2
  • Debugging: export RUST_LOG=debug
Xen

Parameters:

  • vm_name: name of the VM
sudo -E ./memprocfs -mount xxx -device 'microvmi://vm_name=win10'
KVM

Parameters:

  • vm_name: name of the VM
  • kvm_unix_socket: KVMi UNIX socket (see KVM-VMI project)
./memprocfs -mount xxx -device 'microvmi://vm_name=win10&kvm_unix_socket=/tmp/introspector'
VirtualBox (IceBox)

Parameters:

  • vm_name: name of the VM
./memprocfs -mount xxx -device 'microvmi://vm_name=win10'
QEMU

Parameters:

  • memflow_connector_name: qemu_procfs
  • vm_name (optional): name of the VM
sudo -E ./memprocfs -mount xxx -device 'microvmi://memflow_connector_name=qemu_procfs'

leechcore_device_qemu

Authors:

Supported Platforms:

  • Linux

Overview:

Parameters:

  • shm: filename of shared memory file in /dev/shm/xxxx (if shared memory acquisition method is used).
  • hugepage-pid=: libvirt / QEMU process to target (if hugepage acquisition method is used).
  • qmp: path to optional qmp socket (used to query vm memory ranges, optional).
  • delay-latency-ns: Delay in ns to be applied once each read request (optional).
  • delay-readpage-ns: Delay in ns to be applied per read page (optional).
QEMU Virtual machine setup

Also see the more extensive QEMU documentation in the LeechCore Wiki.

To enable the memory backend on our virtual machine, we need to add the memory-backend-object to our command line.

  1. Add the memory-backend-object to the command line
 memory-backend-file,id=mem,size=512M,mem-path=/dev/shm/qemu-ram,share=on
  1. Launch the virtual machine
 qemu-system-x86_64 -kernel vmlinuz.x86_64 -m 512  -drive format=raw,file=debian.img,if=virtio,aio=native,cache.direct=on, \
                    -enable-kvm -append "root=/dev/mapper/cl-root console=ttyS0 earlyprintk=serial,ttyS0,115200 nokaslr"   \ 
                    -initrd initramfs.x86_64.img \
                    -object memory-backend-file,id=mem,size=512M,mem-path=/dev/shm/qemu-ram,share=on \
                    -qmp unix:/tmp/qmp.sock,server,nowait
PCILeech
./pcileech -device 'qemu://shm=qemu-ram' write -min 0x12345678 -in 0xdeadcafe
Memprocfs
sudo -E ./memprocfs -mount xxx -device 'qemu://shm=qemu-ram,qmp=/tmp/qmp.sock'