bugtraq - Re: FreeBSD kernel buffer overflow

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <Pine.BSI.4.58.0409171215410.23430@malasada.lava.net>
Date: Fri, 17 Sep 2004 12:21:08 -1000 (HST)
From: Tim Newsham <newsham@...a.net>
To: gerarra@....it
Cc: bugtraq@...urityfocus.com
Subject: Re: FreeBSD kernel buffer overflow

This is a non-issue.

On Thu, 16 Sep 2004 gerarra@....it wrote:
> 	narg = callp->sy_narg & SYF_ARGMASK;  (<- you can see it's the only one
> check)

At this point, callp points to the sysent entry for a particular
system call that is to be called.  These entries are not under
the control of the attacker (unless, as you point out, you
are root and you add a new system call to the system).

If there's an entry in the system call table with a sy_narg
field greater than 8, then yes, there will be a buffer overflow.
However, the programmers who wrote the kernel don't provide
you with any such system calls.

> It's exploitable, but the only one way I discovered is to link a new syscall
> to the sysent
> array and to do this you need to be root; I've no time to work on this vulnerability,
> but i think another way could be found. However it could give serious problems
> (e.g. kernel
> crashes).

> rookie

Tim N.