How to know the profile of a Linux memory dump with Volatility? [on hold]
up vote
1
down vote
favorite
I have a Linux memory dump which I need to analyze in order to discover a suspicious PID, however I don't have a profile or anything outside the dump file and using volatility imageinfo doesn't work.
How can I analyze it?
After an hour or so of volatility imageinfo I got this result:
Volatility Foundation Volatility Framework 2.6
INFO : volatility.debug : Determining profile based on KDBG search...
Suggested Profile(s) : No suggestion (Instantiated with no profile)
AS Layer1 : LimeAddressSpace (Unnamed AS)
AS Layer2 : FileAddressSpace (dump)
PAE type : No PAE
What can I do now to know the profile that I need to work with?
linux memory forensics dump
New contributor
Emiliano Pérez is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
put on hold as unclear what you're asking by Rui F Ribeiro, Jeff Schaller, RalfFriedl, Romeo Ninov, JigglyNaga Nov 16 at 7:58
Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
add a comment |
up vote
1
down vote
favorite
I have a Linux memory dump which I need to analyze in order to discover a suspicious PID, however I don't have a profile or anything outside the dump file and using volatility imageinfo doesn't work.
How can I analyze it?
After an hour or so of volatility imageinfo I got this result:
Volatility Foundation Volatility Framework 2.6
INFO : volatility.debug : Determining profile based on KDBG search...
Suggested Profile(s) : No suggestion (Instantiated with no profile)
AS Layer1 : LimeAddressSpace (Unnamed AS)
AS Layer2 : FileAddressSpace (dump)
PAE type : No PAE
What can I do now to know the profile that I need to work with?
linux memory forensics dump
New contributor
Emiliano Pérez is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
put on hold as unclear what you're asking by Rui F Ribeiro, Jeff Schaller, RalfFriedl, Romeo Ninov, JigglyNaga Nov 16 at 7:58
Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
Welcome to U&L! Your question requires more detail: how did you create the "memory dump" file? What exactly "doesn't work" -- do you get an error message?
– JigglyNaga
Nov 16 at 7:58
Sadly I don't know the memory dump method, since I got only the result file without any context, and after doing the volatility command it keeps searching in the KDBG search like this:volatility imageinfo -f Atenea/dump Volatility Foundation Volatility Framework 2.6 INFO : volatility.debug : Determining profile based on KDBG search...However I never get a result
– Emiliano Pérez
Nov 16 at 16:15
Apparently the dump i'm working with is a Ubuntu 16.04 dump, howevervolatility imageinfodoesn't recognize this kind of image dump, so I'll be searching for another way to solve the problem, anyway, thanks for the help!
– Emiliano Pérez
Nov 16 at 19:03
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I have a Linux memory dump which I need to analyze in order to discover a suspicious PID, however I don't have a profile or anything outside the dump file and using volatility imageinfo doesn't work.
How can I analyze it?
After an hour or so of volatility imageinfo I got this result:
Volatility Foundation Volatility Framework 2.6
INFO : volatility.debug : Determining profile based on KDBG search...
Suggested Profile(s) : No suggestion (Instantiated with no profile)
AS Layer1 : LimeAddressSpace (Unnamed AS)
AS Layer2 : FileAddressSpace (dump)
PAE type : No PAE
What can I do now to know the profile that I need to work with?
linux memory forensics dump
New contributor
Emiliano Pérez is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I have a Linux memory dump which I need to analyze in order to discover a suspicious PID, however I don't have a profile or anything outside the dump file and using volatility imageinfo doesn't work.
How can I analyze it?
After an hour or so of volatility imageinfo I got this result:
Volatility Foundation Volatility Framework 2.6
INFO : volatility.debug : Determining profile based on KDBG search...
Suggested Profile(s) : No suggestion (Instantiated with no profile)
AS Layer1 : LimeAddressSpace (Unnamed AS)
AS Layer2 : FileAddressSpace (dump)
PAE type : No PAE
What can I do now to know the profile that I need to work with?
linux memory forensics dump
linux memory forensics dump
New contributor
Emiliano Pérez is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Emiliano Pérez is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited Nov 16 at 17:00
New contributor
Emiliano Pérez is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Nov 15 at 19:34
Emiliano Pérez
113
113
New contributor
Emiliano Pérez is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Emiliano Pérez is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Emiliano Pérez is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
put on hold as unclear what you're asking by Rui F Ribeiro, Jeff Schaller, RalfFriedl, Romeo Ninov, JigglyNaga Nov 16 at 7:58
Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
put on hold as unclear what you're asking by Rui F Ribeiro, Jeff Schaller, RalfFriedl, Romeo Ninov, JigglyNaga Nov 16 at 7:58
Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
Welcome to U&L! Your question requires more detail: how did you create the "memory dump" file? What exactly "doesn't work" -- do you get an error message?
– JigglyNaga
Nov 16 at 7:58
Sadly I don't know the memory dump method, since I got only the result file without any context, and after doing the volatility command it keeps searching in the KDBG search like this:volatility imageinfo -f Atenea/dump Volatility Foundation Volatility Framework 2.6 INFO : volatility.debug : Determining profile based on KDBG search...However I never get a result
– Emiliano Pérez
Nov 16 at 16:15
Apparently the dump i'm working with is a Ubuntu 16.04 dump, howevervolatility imageinfodoesn't recognize this kind of image dump, so I'll be searching for another way to solve the problem, anyway, thanks for the help!
– Emiliano Pérez
Nov 16 at 19:03
add a comment |
Welcome to U&L! Your question requires more detail: how did you create the "memory dump" file? What exactly "doesn't work" -- do you get an error message?
– JigglyNaga
Nov 16 at 7:58
Sadly I don't know the memory dump method, since I got only the result file without any context, and after doing the volatility command it keeps searching in the KDBG search like this:volatility imageinfo -f Atenea/dump Volatility Foundation Volatility Framework 2.6 INFO : volatility.debug : Determining profile based on KDBG search...However I never get a result
– Emiliano Pérez
Nov 16 at 16:15
Apparently the dump i'm working with is a Ubuntu 16.04 dump, howevervolatility imageinfodoesn't recognize this kind of image dump, so I'll be searching for another way to solve the problem, anyway, thanks for the help!
– Emiliano Pérez
Nov 16 at 19:03
Welcome to U&L! Your question requires more detail: how did you create the "memory dump" file? What exactly "doesn't work" -- do you get an error message?
– JigglyNaga
Nov 16 at 7:58
Welcome to U&L! Your question requires more detail: how did you create the "memory dump" file? What exactly "doesn't work" -- do you get an error message?
– JigglyNaga
Nov 16 at 7:58
Sadly I don't know the memory dump method, since I got only the result file without any context, and after doing the volatility command it keeps searching in the KDBG search like this:
volatility imageinfo -f Atenea/dump Volatility Foundation Volatility Framework 2.6 INFO : volatility.debug : Determining profile based on KDBG search... However I never get a result– Emiliano Pérez
Nov 16 at 16:15
Sadly I don't know the memory dump method, since I got only the result file without any context, and after doing the volatility command it keeps searching in the KDBG search like this:
volatility imageinfo -f Atenea/dump Volatility Foundation Volatility Framework 2.6 INFO : volatility.debug : Determining profile based on KDBG search... However I never get a result– Emiliano Pérez
Nov 16 at 16:15
Apparently the dump i'm working with is a Ubuntu 16.04 dump, however
volatility imageinfo doesn't recognize this kind of image dump, so I'll be searching for another way to solve the problem, anyway, thanks for the help!– Emiliano Pérez
Nov 16 at 19:03
Apparently the dump i'm working with is a Ubuntu 16.04 dump, however
volatility imageinfo doesn't recognize this kind of image dump, so I'll be searching for another way to solve the problem, anyway, thanks for the help!– Emiliano Pérez
Nov 16 at 19:03
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Welcome to U&L! Your question requires more detail: how did you create the "memory dump" file? What exactly "doesn't work" -- do you get an error message?
– JigglyNaga
Nov 16 at 7:58
Sadly I don't know the memory dump method, since I got only the result file without any context, and after doing the volatility command it keeps searching in the KDBG search like this:
volatility imageinfo -f Atenea/dump Volatility Foundation Volatility Framework 2.6 INFO : volatility.debug : Determining profile based on KDBG search...However I never get a result– Emiliano Pérez
Nov 16 at 16:15
Apparently the dump i'm working with is a Ubuntu 16.04 dump, however
volatility imageinfodoesn't recognize this kind of image dump, so I'll be searching for another way to solve the problem, anyway, thanks for the help!– Emiliano Pérez
Nov 16 at 19:03