Date: Sat, 31 Jul 2010 17:39:47 +0200 From: Chris Walker <chris.walker@velocitum.com> To: =?iso-8859-1?Q?Istv=E1n?= <leccine@gmail.com> Cc: Kostik Belousov <kostikbel@gmail.com>, freebsd-security <freebsd-security@freebsd.org>, Selphie Keller <selphie.keller@gmail.com> Subject: Re: kernel module for chmod restrictions while in securelevel one or higher Message-ID: <BD26B28B-8418-44FE-BC7D-88BA50BE26AE@velocitum.com> In-Reply-To: <AANLkTi=6e1ZkCEYEJS%2B74DHK8QxfaFjYHDP8JJoJE4n-@mail.gmail.com> References: <235BB726E71747BA980A0EF60F76ED37@2WIRE304> <20100731124136.GN22295@deviant.kiev.zoral.com.ua> <AANLkTi=6e1ZkCEYEJS%2B74DHK8QxfaFjYHDP8JJoJE4n-@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi list #1 Not same exploit referenced in URL. #2 Not same bug, although you had the function right, sort of. #3 That kernel module is useless: The exploit in the wild has already = changed to bypass such restriction. #4 The bug is already patched, upgrade your kernel. #5 If you intend on introducing a kernel module that potentially makes = your system unstable, make sure it actually fixes the bug. This = workaround merely made the exploit grow more lethal, and provides a = FALSE sense of a security, and as such I would *STRONGLY* discourage use = of this kernel module. This is a perfect example of why software developers never ever will be = able to fight blackhat hackers: Ignorance. Thanks. On Jul 31, 2010, at 2:59 PM, Istv=E1n wrote: > http://www.securiteam.com/exploits/6P00C00EKO.html >=20 > <http://www.securiteam.com/exploits/6P00C00EKO.html>HTH >=20 > On Sat, Jul 31, 2010 at 1:41 PM, Kostik Belousov = <kostikbel@gmail.com>wrote: >=20 >> On Fri, Jul 30, 2010 at 11:18:39PM -0700, Selphie Keller wrote: >>> Kernel module for chmod restrictions while in securelevel one or = higher: >>> http://gist.github.com/501800 (fbsd 8.x) >>>=20 >>> Was looking at the new recent sendfile/mbuf exploit and it was using = a >>> shellcode that calls chmod syscall to make a setuid/setgid binary. >> However >> Can you point to the exploit (code) ? >>=20 >=20 >=20 >=20 > --=20 > the sun shines for all >=20 > http://l1xl1x.blogspot.com > _______________________________________________ > freebsd-security@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-security > To unsubscribe, send any mail to = "freebsd-security-unsubscribe@freebsd.org" >=20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BD26B28B-8418-44FE-BC7D-88BA50BE26AE>