-
Notifications
You must be signed in to change notification settings - Fork 484
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
Intermittent errors with linux plugins (~50% of memory acquisitions from the same machine have errors) #1534
Comments
Hello, Thank you for filing thia report! To start the feedback:
|
Passing pslist with -vvv
|
Failing pslist with -vvv
|
Thank you for the updated information. The pslist crash will be fixed by #1518 psaux will get its own pull request this week to fix it. I will close this ticket once both fixes are merged |
The second issue reported here with the |
Hello, We have validated with the latest dev branch and found that the pslist plugin is no longer crashing! Appreciate the updates that resolved this. However, now we are seeing some memory acquisitions that show ~75% less processes than a memory acquisition taken a minute earlier. We understand that the number of processes shown will fluctuate, but are curious: How can we validate that a memory capture is "complete" from a volatility3 perspective. We are running AVML and volatility3 as a part of automation, and would like to be able to evaluate memory acquisition completeness. For example, if a memory sample has 50% of the total processes in a smeared state that is unreadable by volatility3 plugins, we would want the automation to take a new capture. Is there a way to validate the amount of smearing or unreadable tasks detected in a pslist run? |
Are you comfortable with changing to previous commits instead of just branches? If so, for the samples losing that many processes (from pslist I assume), can you checkout the code base before this commit: And 1) see how many processes come back 2) if they actually look valid. |
Describe the bug
Started with post in community slack and was told to open issue here.
Example Errors (Full -vvv stacktraces included in comment)
python3.8 volatility3/vol.py -f output.lime linux.pslist
python3.8 volatility3/vol.py -f output.lime linux.psaux
Context
To Reproduce
./avml output.lime
python3.8 volatility3/vol.py -f output.lime linux.pslist
Note on Reproducing
Expected behavior
Additional information
linux.ps_aux
andlinux.pslist
doesn't cause errors inlinux.check_syscall
The text was updated successfully, but these errors were encountered: