|
Message-ID: <20201114115850.GB5193@suse.de> Date: Sat, 14 Nov 2020 12:58:50 +0100 From: Marcus Meissner <meissner@...e.de> To: oss-security@...ts.openwall.com Subject: Re: Buffer Overflow in raptor widely unfixed in Linux distros Hi, On Fri, Nov 13, 2020 at 01:33:31PM +0100, Hanno Böck wrote: > 3 years ago I reported a heap overflow vulnerability in raptor, an RDF > parsing library: > https://www.openwall.com/lists/oss-security/2017/06/07/1 > > raptor has not created a new release since 2014. > > The most prominent user seems to be libreoffice. This is triggerable > from within an ODT file. Back then I reported this to libreoffice as > well and they patched it in their builds. However on linux systems > libreoffice package usually use the system-provided libraptor, so if > that's not patched it is vulnerable. > > This was unpatched for a long time in many linux distros, in some it > still is. Debian+Ubuntu have released updates in the past few days. > > It may be interesting to discuss how this happened. From my side I feel > I did what I should do - I reported it to the project and later > disclosed it publicly on oss-security. Apparently it seems there is no > reliable process to make sure publicly reported vulns eventually get > patched in distros if there is no active upstream. > Maybe noteworthy is that this didn't get a CVE in 2017. It seems many > distros rely on CVEs to get a process of backporting fixes rolling. > Given the fluctuating reliability of CVE assignments not sure this is > wise. I have now requested a CVE (CVE-2017-18926). I think the only thing you can do additional is to request a CVE. All tracking by everyone is using CVEs, this is the core identifier of the software security world. We distributors fill in as CVE requesters, but as you noticed, we occasionaly miss entries. Ciao, Marcus
Powered by blists - more mailing lists
Please check out the Open Source Software Security Wiki, which is counterpart to this mailing list.
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.