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

Event logger is broken when WebSockets are used for comms #1570

Closed
bcoles opened this issue Jun 4, 2018 · 1 comment · Fixed by #2806
Closed

Event logger is broken when WebSockets are used for comms #1570

bcoles opened this issue Jun 4, 2018 · 1 comment · Fixed by #2806

Comments

@bcoles
Copy link
Collaborator

bcoles commented Jun 4, 2018

No keystrokes or mouse events are returned to BeEF when websockets are used for command and control.

Tested on Iceweasel, Kali 1.0.6

Edit: This is probably also true for any part of the API that makes callbacks to any endpoints which aren't purely for the hook C&C, such as /xssrays.

Edit 2 Nope, xssrays and requester have hard coded custom callbacks in the WebSocket code. This needs to be removed and the WebSocket code updated to automatically fire the appropriate post_hook API handler.

@bcoles bcoles added the Defect label Jun 4, 2018
@bcoles bcoles changed the title Event logger is broken when WebSockers are used for comms Event logger is broken when WebSockets are used for comms Jun 4, 2018
@bcoles
Copy link
Collaborator Author

bcoles commented Jun 11, 2018

Added warning in 21af0ae

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants