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
SECURITY ISSUE: Escape possible using special keys #149
Comments
|
Hi @Snawoot! Thanks for reporting these major security issues. I am unfortunately away from my PC until tomorrow night. I'll do my best to work on this asap. I also saw your Debian bug reports, as I am the Debian maintainer for lshell. Cheers! |
|
@Snawoot can you confirm that this fixes the issue you reported? Thanks! :) |
|
@ghantoos Fix confirmed, thank you! |
…loses #147, Closes #149) Both issues #148 and #147 use the same vulnerability in the parser, that ignored the quoted strings. Parsing only the rest of the line for security issues. This is a major security bug. This commits also corrects a previous ommited correction regarding the control charaters, that permitted to escape from lshell. Thank you Proskurin Kirill (@Oloremo) and Vladislav Yarmak (@Snawoot) for reporting this!!
|
Reopening as issue is still there, using other control characters. See #148. |
Closes #148, Closes #147, Closes #149) Both issues #148 and #147 use the same vulnerability in the parser, that ignored the quoted strings. Parsing only the rest of the line for security issues. This is a major security bug. This commits also corrects a previous ommited correction regarding the control charaters, that permitted to escape from lshell. Thank you Proskurin Kirill (@Oloremo) and Vladislav Yarmak (@Snawoot) for reporting this!!
Just type
<CTRL+V><CTRL+J>after any allowed command and then type desired restricted command:The text was updated successfully, but these errors were encountered: