THE DFIR BLOG
Menu

Memory Forensics

2019 Unofficial Defcon DFIR CTF - Memory Forensics

8/11/2019

 
Thanks for Champlian Collage Digital Forensic Association to put up unofficial DFIR 2019 CTF for us. You can download the image from this dropbox link:
https://www.dropbox.com/sh/4qfk1miauqbvqst/AAAVCI1G8Sc8xMoqK_TtmSbia?dl=0
CTF Link: https://defcon2019.ctfd.io/ 
In this post, I am only covering the "Memory Forensics Section" of the Defcon DFIR 2019 CTF. I'll be doing other posts for the other parts of the Defcon DFIR 2019 CTF. ​I am using Volatility to do this challenge but feel free to use the tool of your choice. Some of the questions are complex, please try it and feel free to contact me if you have any questions, Happy to help!
Picture
Picture
Picture
Picture
Picture
Picture
Picture
Picture
Picture
Picture
Picture
Picture
Picture
Picture
Picture
Picture
Picture
Picture
Picture
Picture
Picture
Picture
Picture
Picture
Picture
flag<EMPLOY~1.LNK>
Picture
Picture
Picture

What Memory (RAM) can Tell us? (Top 4 Things)

7/7/2019

 
Running process information: Rogue processes such as rootkits-based malware can be detected via memory forensics.
Passwords: It's easy to find the password (clear text) in memory 
Contents of open windows: This is a piece of crucial information to learn about the user's current state.
Network Connection Information: Finding Exfiltration & C2 (Command and control) can be found here. We are all aware of things like TLS etc. The best way to get the decrypted version of the information is in memory.

Why Memory Forensics?

7/7/2019

 
Memory images can contain the contents of many processes, activity and files; including Internet Chat History.  BIOS settings and VSS files (stored on user's hard drive) are not present in the memory image!Pretty much everything in the Operating system goes through Random Access Memory (RAM). Data available in the RAM is of immense value.
  • Processes
  • Threads
  • Malware
  • Rootkits
  • Network URL, Sockets, IP Addresses
  • Passwords, Caches, Clipboard data
  • Encryption Keys
  • Hardware Configuration
  • Software configuration 
  • Registry Keys & Event logs in Windows
Think of memory as a vast park. To make the best use of your time and find the most relevant information, you'll need a map and a path. Memory images can contain the contents of many processes, activity and files; including Internet Chat History.  BIOS settings and VSS files (stored on user's hard drive) are not present in the memory image!
​


Memory Process Analysis

7/6/2019

 
In order to understand a memory process, we need to understand the following terms:
1) DLL's: Dynamic Linked Libraries, this will define the capabilities of the process. Modern day malware uses it's own DLL's to take control of the process.
2) Handles: A pointer to resource . There are many pointers like file pointer, directory handles, Registry handles, Mutex, Event handles.
3) Threads: This of process as a box that will have all the items to do the work. Many threads will run to get things done within a process.
4) Sockets: Network connections endpoints. Helps us in tracking back the network activity of a process.
# Analyzing DLL's
By analyzing the loaded dlls in a process we can answer questions like - what process was doing? You can use another plugin called dlldump to carve out dll's for more analysis. use ldrmodules for more detailed analysis of the dll's

DLLLIST

Picture

getSIDS - Security Identifiers

This will give the information about the about the processing spawning and permissions. Every processes in spawned by an account and every account has some permissions. Most system processes are spawned by system account itself. This will help in identifying malicious process.
Picture
Link:https://support.microsoft.com/en-us/help/243330/well-known-security-identifiers-in-windows-operating-systems

Handles

Each process can have multiple types of handles. use -t flag to find specific type of handles.
Picture

-t Mutant

Modern Malware uses Mutant to tag a processes as captured. Excellent IOC. Look for keywork "Mtx"

Svcscan

Mainly used by malware to maintain 'Persistance' (ability to survive reboot)
Picture

Otter Memory CTF - Question 1: What is the password?

3/31/2019

 
In this blog post, I'll be solving the Otter2018 Memory Forensics CTF Challenge. Alongside the challenge, I'll be share the key concept of memory forensics as well. The blog post will be an excellent start for the beginners. Lets start:

1) What is the password? The first question is for 100 Points:
You got a sample of rick's PC's memory. can you get his user password? format: CTF{...}
Image download link:
https://mega.nz/#!sh8wmCIL!b4tpech4wzc3QQ6YgQ2uZnOmctRZ2duQxDqxbkWYipQ



Solution: I'll be using "Volatility Foundation Volatility Framework 2.6" for the analysis of the memory image. Couple of things we need to do as soon as we get a memory image is to identify the profile of the image.

You can do it by simply running the following command:
vol.py  -f  '/home/ace/Documents/CTF/memory/OtterCTF.vmem'  imageinfo
Picture
Picture
 Investigation Tips: Lot of useful information here:
1) Suggested Image Profile: We'll use Win7SP1x64 for this case
2) Image Date and Time in UTC:  2018-08-04 19:34:22 UTC+0000

The first place to look for is lsasecrents use this command
vol.py -f OtterCTF.vmem --profile=Win7SP1x64 lsadump

Another cool plugin is mimikatz

Picture
Volatility offer an amazing plugin called 'clipboard' clipboard - Extract the contents of the windows clipboard. We'll use this plugin to see the content present in the clipboard.

Picture
This might be useful for future questions.



    Archives

    August 2019
    July 2019
    April 2019
    March 2019

    Categories

    All
    Ctf
    Defcon
    DFIR
    Forensics
    Memory
    Memory Forensics

    RSS Feed

  • Infosec
  • Mac Forensics
  • Windows Forensics
  • Linux Forensics
  • Memory Forensics
  • Incident Response
  • Blog
  • About Me
  • Infosec
  • Mac Forensics
  • Windows Forensics
  • Linux Forensics
  • Memory Forensics
  • Incident Response
  • Blog
  • About Me