3 ms·
Did centos 2.6.32-279.22.1.el6 address this on Feb 6th or is this something new? Oh wait, nope, not addressed: https://rhn.redhat.com/errata/RHSA-2013-0223.htm
by ck2 14y ago
Did centos 2.6.32-279.22.1.el6 address this on Feb 6th or is this something new?
Oh wait, nope, not addressed:
https://rhn.redhat.com/errata/RHSA-2013-0223.html https://rhn.redhat.com/errata/RHSA-2013-0223.html
I thought the responsible thing to do was not announce it until there was some headstart time?
Strangely it's not in the redhat db yet at all
https://access.redhat.com/security/cve/CVE-2013-0871 https://access.redhat.com/security/cve/CVE-2013-0871
- rbanffy 14y ago> I thought the responsible thing to do was not announce it until there was some headstart time? I may be wrong, but from the report, it seems to be a somewhat difficult local exploit that can lead to privilege escalation. While it's serious in that it allows arbitrary code to run in kernel space, it also seems to pose a low risk due to how hard it is to put all the required pieces in place. Also, there are already corrections available.
- X-Istence 14y agoThere is responsible disclosure, full disclosure and no disclosure. I'll take the first two over the last any day of the week. It may be responsible, but there certainly isn't a requirement to do responsible disclosure.