basic_exploitation_000

I couldn't find a reason why the input was constantly interrupted, but I finally got a hint from Google and finally solved it.. However, there is another point of confusion. Locally, I had to enter the shell by entering the address as it is, but on the DreamHack server, I had to enter the address in reverse. I think it happened because the environment was different from my local one, but if so, how can I get information that the address should be entered in reverse

The problem was solved by putting some value in buf and putting the buf address in ret. At this time, rather than just putting any value into buf, can't we enter garbage values into buf and execute it by putting values directly into ret with bof? Why did everyone solve it by putting buf's address in ret..? I'm curious

section.text Global_start _start: Push 0 mov rax, 0x68732f2f6e69622f push rax; /bin//sh MOV RDI, RSP xor rsi, rsi xor rdx, rdx mov rax, 0x9 add rax, 0x2 int 0x80 If you call rax directly with 0xb, scanf will fill in 0x0b

Does Got EOF while reading in interactive appear because the code is wrong?? The command had to be entered twice, is that an error??

When I analyzed the executable file in the problem file, the return address came after 84, and I put in the shell code and set the return address as a variable address, but the interactive mode error continued to occur (there is no error such as a segmentation fault; even if I just pop up $ and enter a command such as ls, there is no response, and the error occurs) (msfvenom -p Linux/x86/exec cmd='/bin/s

A shell called dquote> comes up, but I can't use any commands... I don't think this is the server shell... but it's probably not the server Ubuntu shell? ! [1.PNG] (https://dreamhack-media.s3.ap-northeast-2.amazonaws.com/attachments/e5b3ced7417f1e38d29d64effc226090b73a25673ea19

So I'm using a socket to solve the problem, but I'm not sure where the problem is. I will attach the code. Remove the code part to solve for others. I think interactive shell connect was the problem. I think it would be better to eventually use pwntools to solve this part. I finally solved it with pwntools.

EOF pops up because whitespace is included in the shell code generated by shellcraft.sh () Maybe there's a way to make shell code without whitespace! (using shellcraft)

This is my first time, so I'm asking a question! Maybe this file doesn't open with 64 debugging,..? What's the reason

The code is the same, but it didn't work on 64-bit Windows, and it worked on 64-bit Linux.