Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AFF4 Memory Image for RHEL 7.9 - No Suitable Address Space Mapping Found #797

Open
jonnythefox opened this issue May 26, 2021 · 3 comments

Comments

@jonnythefox
Copy link

Hello,

As part of some testing, I used Tanium Collection for Linux (memory) to recover memory from a RHEL 7.9 instance. Tanium uses pmem under the hood to dump an image in AFF4 format. I subsequently used this image to generate a profile, using the recovered boot/system.map-* and dwarfdump. I then cloned the most recent aff4 python plugin I could locate, added repo to PYTHONPATH, and then passed both parameters explicitly into the Vol command:

vol.py --plugins=/usr/local/lib/python2.7/pyaff4/pyaff4/aff4.py -f /home/user/Downloads/linux_mem_collection_test/memory_results/memory.zip --profile=Linuxrhel_79_maipo_profilex64 linux_pslist

Resultant output error - No suitable address space mapping found

Can anyone provide assistance - I'm not sure if this is a kernel issue, an image issue, or my command screw up for the plugin.

Thank you!

@gleeda
Copy link
Member

gleeda commented Jun 2, 2021

Have you tried extracting the memory sample from the zip file and running Volatility against that?

@jonnythefox
Copy link
Author

Thanks Gleeda. I did try to extract the physical memory stream to a raw file using linpmem but this also threw an error. Is that what you mean?

@jcv-
Copy link

jcv- commented Jun 2, 2021

Running into the exact same issue. I basically followed the following instructions: https://schatzforensic.com/insideout/2018/06/how-to-analyse-aff4-linux-memory-images/ but running into the "No suitable address space mapping found."

I have tried extracting /proc/kcore from the AFF4 container and running volatility against that, but get the same error message.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants