-
Notifications
You must be signed in to change notification settings - Fork 317
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
Vulnerability: Command injection #184
Comments
Good find. You obviously have some technical chops since you were able to identify this issue: mind submitting a patch via pull request? |
@ecapson - Just a quick follow-up. Do you have the spare cycles for this or should I go ahead and write a patch? |
Hey, thanks for the follow-up. I should be able create a pull-request this week. |
I’ve merged your pull request and am closing the issue. That said, I think this calls for a standardized, repeatable solution that can be used across the entire project. I’m thinking something like a small standardized library for making system calls and handling input / output, as well as strictly defining types and formats for anything input coming into the application. I’ll add it to the top of the queue. Thanks again. |
When using the module autocrack the input is not sanitized properly and it was possible to inject code as root.
The following addition was made in the crack_locally function for clarity.
print('autocrack start')
print('cmd:',cmd)
Environment is Latest Kali linux with eaphammer v1.13.5.
Eaphammer was started with
eaphammer -i wlan0 --channel 6 --essid test --auth wpa-eap --autocrack --cloaking none
In the screenshot, an EAP authentication was made with the following identity:
|;whoami;#
.The injection is possible due to the
data=data.strip().split('|')
in the run_autocrack function.When the username contains '|', the user identity overrides the channel which is later used in the crack_locally function as an 'asleap' parameter.
The text was updated successfully, but these errors were encountered: