3 ms·
The Qualys link (elsewhere on this page) contains sample code to test if you are vulnerable. Also, you can check your glibc version with this tiny code: #
by danielweber 12y ago
The Qualys link (elsewhere on this page) contains sample code to test if you are vulnerable.
Also, you can check your glibc version with this tiny code:
#include <stdio.h>
#include <gnu/libc-version.h>
int main (void) { puts (gnu_get_libc_version ()); return 0; }
(taken from a forum that I've since closed the page on, sorry for lack of attribution)
<= 2.17 is unsafe, >= 2.18 is safe.
ldd --version might also do the trick.
- arielby 12y agoYou can check your libc version by running libc - e.g. `/lib/x86_64-linux-gnu/libc.so.6`
- verelo 12y agoThanks, super helpful!
- caf 12y agoChecking the libc version doesn't really tell you if you've fixed the problem, since most vulnerable distributions will be fixing it by patching their older version of libc, so the version number will remain the same.
- deleted 12y ago[deleted]