-
Notifications
You must be signed in to change notification settings - Fork 739
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
[Feature Request]: Support custom TCP callback host #80
Open
axel3rd opened this issue
Dec 17, 2021
· 1 comment
· Fixed by axel3rd/log4j-scan#1 · May be fixed by #95
Open
[Feature Request]: Support custom TCP callback host #80
axel3rd opened this issue
Dec 17, 2021
· 1 comment
· Fixed by axel3rd/log4j-scan#1 · May be fixed by #95
Comments
This was referenced Dec 17, 2021
This was referenced Dec 23, 2021
Reopen for merge in original repo. Testable from https://github.com/axel3rd/log4j-scan |
Open
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, using
python log4j-scan.py -u http://locahost --custom-dns-callback-host 10.42.42.42
provides payload:Using a DNS callback server is sometime not trivial on a corporate internal network (could depend of network zones, ...).
Having the capabilities to define a direct TCP host (which host a simple TCP receiver, logging any IP trying to connect) could be very useful.
This parameter could be named:
--custom-tcp-callback-host
and provides the behavior:If considered as relevant, I can provide a PR and the Python receiver.
The text was updated successfully, but these errors were encountered: