Dad. Husband. Akamai. @harmoniumllc
for research work.
AI. Food. Coffee. Bourbon. Sarcasm / dark humor. Certs prep.
All opinions are my own.
I was thinking something like:
% wget 'http://127.0.0.1/[insert filename here]'
...but when you said above that you weren't interested in what commands I might run, I decided not to demonstrate syntax.
In the meantime, someone else already posted similar solutions.
Since the topic of SMS TFA has arisen on the bird site, does this seem like a problem for anyone else, if you've opted for app-based or key-based TFA?
I mean, it would be nice to be able to get account notifications via text, but I don't want to introduce an SMS vulnerability just to be able to receive those notifications.
I see similar preferences presented in many companies' threat models, and considering what seems like common knowledge within the infosec community, I have to wonder why this is still a discussion. If a better TFA option has been chosen, why not use it first?
@oj
Ahh, you're gonna make me dust it off. LOL... OK.
1. Attempt to determine OS from banners.
2. Determine valid path and most-likely binary available in target OS to establish command exec. Or host a binary matching your target OS on the attacking machine.
3. Select and execute the chosen binary with no parameters/args.
Remote Code Execution would probably be preferable, to grant you further control over the target binary.
Does this answer your question?