Brutal vulnerability in glibc. FreeBSD is OK, right?

just curious whether this glibc vulnerability which has been there for almost 2 years affects FreeBSD in any way.
FreeBSD has its own implementation of libc, so there's no glibc here. Thus, a glibc specific issue doesn't affect us.

That said, I do wonder about Linux_base. Because that does have a glibc. And this could potentially be leveraged to gain more privileges.
 
I wonder whether it makes sense to just kill all suid bits inside /compat/*. I don't see why I would need them. That would disable this particular issue.
 
Another idea I had is a sysctl that allows you to turn off setui in /compact. That would help here and as I said currently I don't see why I need setuid binaries in /compact.
 
Another idea I had is a sysctl that allows you to turn off setui in /compact. That would help here and as I said currently I don't see why I need setuid binaries in /compact.
Maybe generalize the "nosuid" and other features from mountpoints to maybe any directory to kill bits on the files/directories under it?
That way we not only could lock down /compat, but more places as well.
 
Maybe generalize the "nosuid" and other features from mountpoints to maybe any directory to kill bits on the files/directories under it?
That way we not only could lock down /compat, but more places as well.

Yeah, I discussed this at work and maybe it is better to not do this on a filesystem level at all but lock down all compat functionality, including e.g. 32-bit FreeBSD binaries on 64 bit systems. Who needs those to be setuid?
 
Yeah, I discussed this at work and maybe it is better to not do this on a filesystem level at all but lock down all compat functionality, including e.g. 32-bit FreeBSD binaries on 64 bit systems. Who needs those to be setuid?
I would like an evaluation if it would be better to do a white list feature here. Mark directories which are allowed to contain setuid/setgid binaries and block all the rest. Is there a reason we need to allow this feature all around the place?
 
/usr/bin/sudo would be a setuid example on my machine.

I am not sure why /bin/login doesn't have the setuid bit set, probably some systemd scheenegans.
 
Back
Top