Tweet
"make a copy of a shell program (e.g. csh, bash, sh,
ksh, whatever) in your user area. Write some code that figures out where the
inode table (which is usually cached in RAM) entry for that file resides in
memory. Trap into a debugger, and set the suid root bit for that file.
Resume the operating system. Run the shell - you now have a command prompt
with root privileges."
On any OS, use the md5sum binary checker thing, and then use a script to prevent that binary from executing, thats what I have on my system (and no I didnt write it
). That certainly works on linux/bsd and should work in windows.
ksh, whatever) in your user area. Write some code that figures out where the
inode table (which is usually cached in RAM) entry for that file resides in
memory. Trap into a debugger, and set the suid root bit for that file.
Resume the operating system. Run the shell - you now have a command prompt
with root privileges."
On any OS, use the md5sum binary checker thing, and then use a script to prevent that binary from executing, thats what I have on my system (and no I didnt write it
). That certainly works on linux/bsd and should work in windows.
Comment