News for hackers. Stuff that matters.

A comment on CVE-2015-0235 – GHOST: glibc gethostbyname buffer overflow. Parent comment

Re:CVE-2015-0235 – GHOST: glibc gethostbyname buffer overflow by gtrubetskoy on Tuesday January 27, 2015 @12:38PM (#8954438)
There's also a rare chance that a program is statically linked, in which case upgrading glibc won't help, the program would need to be recompiled.
[ Parent | on HN ]
Re:CVE-2015-0235 – GHOST: glibc gethostbyname buffer overflow by JshWright on Tuesday January 27, 2015 @12:45PM (#8954475)
Yeah, that's a good point, and definitely worth mentioning, but obviously rebooting isn't going to help in that case either. The parent was asking about how they would know if they need to reboot or not.
[ Parent | on HN ]
Re:CVE-2015-0235 – GHOST: glibc gethostbyname buffer overflow by aidenn0 on Tuesday January 27, 2015 @01:23PM (#8954690)
It is nearly impossible to statically link glibc.
[ Parent | on HN ]
Re:CVE-2015-0235 – GHOST: glibc gethostbyname buffer overflow by cnvogel on Tuesday January 27, 2015 @02:11PM (#8955023)
... with nss-modules being a major culprit, ironically... (on which gethostbyname relies greatly)...
[ Parent | on HN ]