App - System

Wednesday 23 December 2020, 14:19  #1
App - System Hardened Binary 2 - ch22 no SETUID?
drexx
  • 2 posts

For some reason the SUID bit is not set on the `ch22` binary. The other binaries have it. Is this intentional? I have a shell, but my setuid is failing for obvious reasons.

app-systeme-ch22@challenge03:~$ ls -la
total 36
dr-xr-x---  2 app-systeme-ch22-cracked app-systeme-ch22         4096 août   2  2018 .
drwxr-xr-x 51 root                     root                     4096 avril 10  2020 ..
-r-xr-x---  1 app-systeme-ch22-cracked app-systeme-ch22         6932 avril 29  2011 ch22
-r--------  1 app-systeme-ch22-cracked app-systeme-ch22-cracked  791 avril 16  2013 ch22.c
-r--------  1 root                     root                       46 avril  6  2018 ._firewall
-rw-r-----  1 app-systeme-ch22-cracked app-systeme-ch22          231 août  16  2016 .motd
-r--------  1 app-systeme-ch22-cracked app-systeme-ch22-cracked   17 août   2  2018 .passwd
-rw-r-----  1 root                     root                      458 juil. 20  2018 xinetd.conf
Wednesday 23 December 2020, 14:35  #2
App - System Hardened Binary 2 - ch22 no SETUID?
Shiro
  • 25 posts

Hello, this challenge is meant to be done remotely thanks to the TCP host and port given in the instructions. This is why the binary on his self is not setuid, but you will have the correct rights if you exploit the binary through the TCP connection.

Wednesday 23 December 2020, 15:46  #3
App - System Hardened Binary 2 - ch22 no SETUID?
drexx
  • 2 posts

How embarrassing... you’re 100% correct of course. Thanks

Wednesday 23 December 2020, 16:40  #4
[CLOS] App - System Hardened Binary 2 - ch22 no SETUID?
Th1b4ud
  • 1636 posts

Thanks @shiro