Re:Glibc vulnerability allows any user to get root access
by viraptor on Wednesday October 20, 2010 @06:09AM
(#1810622)
Versions are not everything anymore. Distributions have so many patches, that unless you compiled glibc yourself (did you?), you'll get centos-libc-2.6, or debian-libc-2.6, or ...
Re:Glibc vulnerability allows any user to get root access
by VMG on Wednesday October 20, 2010 @06:59AM
(#1810706)
# pacman -Q glibc
glibc 2.12.1-2
archlinux: LD_AUDIT="\$ORIGIN" exec /proc/self/fd/999
Inconsistency detected by ld.so: dl-open.c: 232: dl_open_worker: Assertion `(call_map)->l_name[0] == '\0'' failed!
Re:Glibc vulnerability allows any user to get root access
by kelnos on Wednesday October 20, 2010 @06:11AM
(#1810629)
Doesn't work for me either; I get "Permission denied" at the first exec step. Glibc 2.12.1 here (Gentoo).
Re:Glibc vulnerability allows any user to get root access
by pvxc on Wednesday October 20, 2010 @08:10AM
(#1810831)
Hard link creation can in recent Linux kernels be restricted, by SECURITY_YAMA_HARDLINKS config option which seems active by default at least on Ubuntu 10.10. So that platform is not vulnerable.
Re:Glibc vulnerability allows any user to get root access
by rg3 on Wednesday October 20, 2010 @02:19PM
(#1812188)
That's because, to redirect that file to file descriptor 3 for reading, you need read permission on the file. In my system, for example, /bin/ping cannot be read as a normal user (permissions 4711) and I get that same error.
You'll have to find another binary that has the SUID bit set and is readable. For example, in my system /bin/mount does the job. Still, in the last step I get the same error as reported by several other users (Inconsistency detected...)
Re:Glibc vulnerability allows any user to get root access
by pyre on Wednesday October 20, 2010 @04:55PM
(#1813050)
There is also a method at the end of the mail (in the Notes section) that details a method of using a SUID binary that you don't have read access to.
TL;DR
1. cause STDERR to block
2. run the SUID binary in the background in a way that triggers ld to try to write to STDERR causing it to block.
3. Replace /tmp/exploit with your binary
4. eliminate the blocking condition on STDERR.
5. ld will continue on using the $ORIGIN value.
Re:Glibc vulnerability allows any user to get root access
by JabavuAdams on Wednesday October 20, 2010 @11:30AM
(#1811580)
I went to try this, and then realized that I don't have gcc installed on my production (-ish) boxes.
Is this sufficient?
Can you foresee me needing to install gcc, and to leave it installed? I.e. should I install it to do whatever compiling I need to do, and then remove it?
Edit: cat -> ping