oss-sec mailing list archives
Re: Why send bugs embargoed to distros?
From: Igor Seletskiy <i () cloudlinux com>
Date: Sun, 24 Sep 2017 19:35:35 -0700
This pre-disclosure was very useful to CloudLinux. Most of our customers are shared hosting companies and are affected by this bug. The early notification gave us time to thoroughly test the fix, and analyze if it can potentially have any side effects. It also let us deliver the fix to beta channel right after the announcement, and to the main channel a day later. Regards, Igor Seletskiy | CEO CloudLinux OS | KernelCare | Imunify360 Get 24/7 free, exceptionally good support at cloudlinux.zendesk.com Follow us on twitter for technical updates: @CloudLinuxOS On Sat, Sep 23, 2017 at 4:44 AM, Hanno Böck <hanno () hboeck de> wrote:
Hi, A few days have passed since the optionsbleed disclosure. Some interesting things have surfaced, e.g. the fact that it was apparently discovered already in 2014, but nobody noticed it was a security bug. But I'd like to discuss something else: I had informed the distros mailing list one week earlier about the upcoming disclosure with a bug description and links to the already available patch. My understanding is that the purpose of the distros list is that updates can be prepared so after a disclosure the time between "vuln is known" and "patch is available" is short. However from all I can see this largely didn't happen. Debian+Ubuntu took more than a day after disclosure to fix. According to the Debian bug tracker the bug got only opened after the public disclosure[2]. I see no sign that any work on a fix began before the disclosure. If I can trust Red Hat's CVE tracker [3] there still are no fixed packages available. Also I haven't found any info about updated opensuse packages. The only distro I'm aware of that prepared packages and pushed them right after disclosure is Gentoo. All of this makes me wonder if the distros list serves its purpose. I'd be curious to hear: a) if any people felt that pre-disclosure of optionsbleed was helpful to them and in which way (after all - even if it only helps minor distros and major distros ignore it it may still be a good thing). b) if people think that they'd usually prepare a fixed package, however they didn't consider optionsbleed important enough. (Naturally I probably have a bias seeing my findings as more important as other people, but I could live with that.) c) other things? [1] https://arxiv.org/pdf/1405.2330.pdf https://blog.fuzzing-project.org/61-How-Optionsbleed-wasnt-found-in-2014.html [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876109 [3] https://access.redhat.com/security/cve/cve-2017-9798 -- Hanno Böck https://hboeck.de/ mail/jabber: hanno () hboeck de GPG: FE73757FA60E4E21B937579FA5880072BBB51E42
Current thread:
- Why send bugs embargoed to distros? Hanno Böck (Sep 23)
- Re: Why send bugs embargoed to distros? Levente Polyak (Sep 23)
- Re: Why send bugs embargoed to distros? Anthony Liguori (Sep 23)
- Re: Why send bugs embargoed to distros? Simon McVittie (Sep 23)
- Re: Why send bugs embargoed to distros? Marc Deslauriers (Sep 23)
- Re: Why send bugs embargoed to distros? Kurt H Maier (Sep 23)
- Re: Why send bugs embargoed to distros? Till Dörges (Sep 23)
- Re: Why send bugs embargoed to distros? Marcus Meissner (Sep 23)
- Re: Why send bugs embargoed to distros? Ludovic Courtès (Sep 24)
- Re: Why send bugs embargoed to distros? Igor Seletskiy (Sep 24)
- Re: Why send bugs embargoed to distros? John Haxby (Sep 25)
- Re: Why send bugs embargoed to distros? Cliff Perry (Sep 25)
- Re: Why send bugs embargoed to distros? Leo Famulari (Sep 25)
- Re: Why send bugs embargoed to distros? Levente Polyak (Sep 23)