SeLLeRoNe
Super Moderator
Ok, thank you
Regards
Regards
Is the reboot required after the update?
So am I correct nobody's vulnarable, as long as they upgraded their OS everytime (like doing a weekly yum update and update kernels and glibc etc. etc.)?We identified a number of factors that mitigate the impact of this
bug. In particular, we discovered that it was fixed on May 21, 2013
(between the releases of glibc-2.17 and glibc-2.18).
I was just wondering.
It was said this security flaw was already present since 2010 and fixed with a glibc update later on. Only thing was they did not know there was an issue they fixed.
You can also read this in the statements:
So am I correct nobody's vulnarable, as long as they upgraded their OS everytime (like doing a weekly yum update and update kernels and glibc etc. etc.)?
Unfortunately, it
was not recognized as a security threat; as a result, most stable and
long-term-support distributions were left exposed (and still are):
Debian 7 (wheezy), Red Hat Enterprise Linux 6 & 7, CentOS 6 & 7,
Ubuntu 12.04, for example.