[SPOILERS ALERT!] Hello! Newbie here trying to learn some pentest tools with the academy. First post
I am stuck in the exercise of the Phishing section. I have managed to set up the PHP server and the payload that connects to the server. The resultant URL is
with SERVER-IP being the HTB machineās, and MY-IP being my tun0 IP. When I open the link and fill the forms and press enter, my PHP server successfully receives the login details and everything behaves as expected.
The problem is that when I go to https://SERVER-IP/phishing/send.php, paste the mentioned link and press āSendā, the page shows āIssue in sending URL!ā and nothing reaches my PHP server.
I ran into the same issue, but mine had a different cause/solution.
For anyone in the future that gets the āIssue in sending URL!ā, double check to make sure the payload you send is exactly what the material provides. Seems a little obvious in hindsight, but I wasted a good bit of time over a ālab-ismā that wouldnāt have mattered in a āreal-worldā instance; hopefully I can save someone else some trouble.
Has anyone done the skills assessment for that same module? If you have please dm me I can use some help. Also to the question on top try resetting the target IP. Thatās the only thing I can think of.
My I tested the URL it worked my problem is setting up the server. I canāt connect to 0.0.0.0:80 because its already listening. I trying 8080, 8000, and 81, no of them gets a response. Did everyone use the 0.0.0.0:80 for the address?
My script worked, and as everyone here, Iāve stumble upon the āIssue in sending URL!ā error.
This what Iāve tried:
Using ZAP browser.
Installing and using Chrome browser.
Using the payload of xlandrexl1 as CyberSecN00b said, as Iāve created a different script than the original.
Encoding both payloads in 6 websites in case the issue was the server didnāt like the format.
As my PHP server used port 8080 (couldnāt close 80, already in use by HTBās pwnbox), so tried both payloads with :8080 removed from the URL in case the website didnāt like and although it made no sense.
Finally, and this was the solution, Iāve noticed that the website might not like the encoding of the URL in only some parts (the ones related to the āusefulā URL) sos it didnāt realize it was a valid URL. So using the payload from xlandrexl1 as an example, it ended up like this: http://target.ip/phishing/index.php?url= http:/my.php.server.ip:8080
This scenario is really starting to bother me, and surely there is a better way HTB could check for correct solutions. Like most people above I have a working solution that is as far as I can tell EXACTLY what the material provided.
Naturally, port 80 is in use so the php server is running on port 88, other than that I cant see any difference. Iāve tried encoding in different ways, using different ports, using burp to send the link in more specific ways like wrapping the address in HTML hyperlink tags.
Could someone please just post a working link so I can understand the awful specific formatting?
UPDATE: My solution is correct, it now inexplicably works, HTB is just garbage.
Thnx, that helped a lot. Iām really soldiering through and get most of it myself and donāt mind spending hours/days searching for answers but having a working scenario/link and having it rated incorrect because of encoding issues of parts of the URL is really too much imo of what can be expected. Thanks a heap :).
Itās just shitty but in my case you musnāt encode all, just parts. The way it is written (and the way you executed it) is according to the wording I guess. But @Patoman19 also mentions that you ONLY have to encode the query parts and that meant for me starting encoding later in the link http://ā¦snippetā¦=ā>document.write(ā ENCODED URL PART etc. Hope this helps.
Never mind, I solved the issue (sort of). Seems to be some sort of issue with the connection between my machine and HTB servers. When I jumped on their Pwnbox I submitted the exact same url and it worked. Have no idea what the problem is with the connection. This is the first time this issue has popped up. Havenāt had to use the pwnbox before (itās so slow, I hate it so much).
Is anyone else having issues with their servers going down regularly? You submit a form and it tells you that the connection timed out? Happens to me every 30 seconds or so.