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

cmdscan and consoles potential unitialized variable usages #1435

Open
atcuno opened this issue Dec 18, 2024 · 0 comments
Open

cmdscan and consoles potential unitialized variable usages #1435

atcuno opened this issue Dec 18, 2024 · 0 comments
Assignees

Comments

@atcuno
Copy link
Contributor

atcuno commented Dec 18, 2024

@superponible there is a repeated pattern in cmdscan and consoles where a potential uninitialized variable could be referenced if the loop does not find them. Can you just fix these to set the variables to None before?

command_history:

https://github.com/volatilityfoundation/volatility3/blob/develop/volatility3/framework/plugins/windows/cmdscan.py#L269

Consoles proc_id:

https://github.com/volatilityfoundation/volatility3/blob/develop/volatility3/framework/plugins/windows/consoles.py#L98C36-L98C43

Also console_info:

https://github.com/volatilityfoundation/volatility3/blob/develop/volatility3/framework/plugins/windows/consoles.py#L775

@atcuno atcuno changed the title cmdscan and consoles potential unused variable cmdscan and consoles potential unitialized variable usages Dec 18, 2024
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

2 participants