-
Notifications
You must be signed in to change notification settings - Fork 606
Description
Hello Volatility Team,
I am encountering an issue with Volatility 3 where none of the plugins are working for memory images from AWS Workspaces. The same plugins work fine for similar or identical Linux distributions and kernel versions on non-AWS machines.
Context:
- Volatility Version**: 3.0.2
- Operating Systems Attempted**: Windows 10 and Kali Linux
- Memory Image**: Linux (Ubuntu 22.04, Kernel 6.5.0-1022-aws)
- Symbol Files**: Downloaded from volatility3-symbols
- Command Executed**:
python3 vol.py -vvv -f D:\Collection-U-1ZAHAE0FL5HK6_int_jumio_com-2024-07-26T14_40_00_05_30\uploads\auto\memory.lime linux.pslist.PsList
Issue Summary:
-
The plugins fail with errors indicating that the translation layer and symbol table requirements are not fulfilled, even if the error is not there, no data is shown.

-
This issue is specific to memory images from AWS Workspaces and does not occur with similar Linux distributions and kernel versions on non-AWS machines.

Error Log Excerpt:
INFO volatility3.cli: Volatility plugins path: ['C:\Users\ayadav3\Downloads\volatility3-develop\volatility3\plugins', 'C:\Users\ayadav3\Downloads\volatility3-develop\volatility3\framework\plugins']
INFO volatility3.cli: Volatility symbols path: ['C:\Users\ayadav3\Downloads\volatility3-develop\volatility3\symbols', 'C:\Users\ayadav3\Downloads\volatility3-develop\volatility3\framework\symbols']
INFO volatility3.framework.automagic: Detected a linux category plugin
INFO volatility3.framework.automagic: Running automagic: ConstructionMagic
DETAIL 1 volatility3.framework.configuration.requirements: IndexError - No configuration provided: plugins.PsList.kernel.layer_name
DETAIL 1 volatility3.framework.configuration.requirements: Symbol table requirement not yet fulfilled: plugins.PsList.kernel.symbol_table_name
DETAIL 1 volatility3.framework.configuration.requirements: IndexError - No configuration provided: plugins.PsList.kernel.layer_name
DETAIL 1 volatility3.framework.configuration.requirements: Symbol table requirement not yet fulfilled: plugins.PsList.kernel.symbol_table_name
DETAIL 1 volatility3.framework.automagic.construct_layers: Failed on requirement: plugins.PsList.kernel
DETAIL 1 volatility3.framework.configuration.requirements: IndexError - No configuration provided: plugins.PsList.kernel.layer_name
DETAIL 1 volatility3.framework.automagic.construct_layers: Failed on requirement: plugins.PsList.kernel.layer_name
DETAIL 1 volatility3.framework.configuration.requirements: IndexError - No configuration provided: plugins.PsList.kernel.layer_name
DETAIL 1 volatility3.framework.automagic.construct_layers: Failed on requirement: plugins.PsList.kernel
DETAIL 1 volatility3.framework.configuration.requirements: Symbol table requirement not yet fulfilled: plugins.PsList.kernel.symbol_table_name
DETAIL 1 volatility3.framework.automagic.construct_layers: Failed on requirement: plugins.PsList.kernel.symbol_table_name
DETAIL 1 volatility3.framework.configuration.requirements: Symbol table requirement not yet fulfilled: plugins.PsList.kernel.symbol_table_name
DETAIL 1 volatility3.framework.automagic.construct_layers: Failed on requirement: plugins.PsList.kernel
DETAIL 1 volatility3.framework.configuration.requirements: IndexError - No configuration provided: plugins.PsList.kernel.layer_name
DETAIL 1 volatility3.framework.configuration.requirements: Symbol table requirement not yet fulfilled: plugins.PsList.kernel.symbol_table_name
DETAIL 1 volatility3.framework.automagic.construct_layers: Failed on requirement: plugins.PsList
INFO volatility3.framework.automagic: Running automagic: SymbolCacheMagic
INFO volatility3.framework.automagic: Running automagic: LayerStacker
DETAIL 1 volatility3.framework.configuration.requirements: IndexError - No configuration provided: plugins.PsList.kernel.layer_name
DETAIL 1 volatility3.framework.configuration.requirements: Symbol table requirement not yet fulfilled: plugins.PsList.kernel.symbol_table_name
Questions:
- Is there any additional configuration or setup required to support memory images from AWS Workspaces?
- Could there be an issue with the AWS Workspaces kernel versions that are not fully supported by the current Volatility?
- Are there any known issues or limitations with analyzing memory images from AWS Workspaces using Volatility 3?
- Open for any suggestion.
Any guidance or confirmation on this issue would be greatly appreciated.
Thank you for your assistance.