Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.security > #4626
| From | Salvatore Bonaccorso <carnil@debian.org> |
|---|---|
| Newsgroups | linux.debian.security |
| Subject | Re: tracking security issues without CVEs |
| Date | 2016-03-06 19:00 +0100 |
| Message-ID | <r9L8d-8ix-15@gated-at.bofh.it> (permalink) |
| References | <r9yE2-8rb-13@gated-at.bofh.it> <r9JpL-7i6-9@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Hi Brian, hi Paul, On Sun, Mar 06, 2016 at 04:59:43PM +0100, Salvatore Bonaccorso wrote: > Hi, > > On Sun, Mar 06, 2016 at 03:33:16PM +1100, Brian May wrote: > > Just wondering if there is some other way we can track security issues > > for when CVEs are not available. > > > > Thinking of imagemagick here, it has a lot of security issues, and > > requests for CVEs are not getting any responses. > > Creating individual bugs in the Debian BTS, including more details > like fixing commits would be a great start, since we use either CVEs > or references to the Debian BTS in DSAs (and DLAs). Furthermore the > security-tracker handles both (you can actually search items there via > either CVE id, bug number or package name). > > The original CVE request at > http://www.openwall.com/lists/oss-security/2014/12/24/1 was IMHO not > fully optimal, since it just pasted a collection of items. Adding > references to fixing commits would have helped to get CVEs assigned to > issues. The original request at least makes it really hard to > identify the issues and make sure the CVEs are assigned correctly. Just one comment which I forgot to address in the previous mail, regarding the OVE identifiers. The question about the CVE assignments were just re-raised yesterday on oss-security. The whole might look promissing indeed. But I think as well that is right now to early to start adopting these for not yet assigned issues. Instead follow the current discussion on oss-security and let's see if across distributions there is going to be some consensus/approach for this issue. For the record, the thread is starting at http://www.openwall.com/lists/oss-security/2016/03/04/4 where Kurt Seifried from Red Hat raised the concern. Regards, Salvatore
Back to linux.debian.security | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
tracking security issues without CVEs Brian May <brian@linuxpenguins.xyz> - 2016-03-06 05:40 +0100
Re: tracking security issues without CVEs Paul Wise <pabs@debian.org> - 2016-03-06 16:10 +0100
Re: tracking security issues without CVEs Salvatore Bonaccorso <carnil@debian.org> - 2016-03-06 17:10 +0100
Re: tracking security issues without CVEs Salvatore Bonaccorso <carnil@debian.org> - 2016-03-06 19:00 +0100
Re: tracking security issues without CVEs Brian May <bam@debian.org> - 2016-03-06 23:40 +0100
Re: tracking security issues without CVEs Moritz Mühlenhoff <jmm@inutil.org> - 2016-03-10 21:00 +0100
Re: tracking security issues without CVEs Paul Wise <pabs@debian.org> - 2016-03-11 01:30 +0100
Re: tracking security issues without CVEs Brian May <bam@debian.org> - 2016-03-06 23:40 +0100
Re: tracking security issues without CVEs Kurt Roeckx <kurt@roeckx.be> - 2016-03-12 16:00 +0100
Re: tracking security issues without CVEs Paul Wise <pabs@debian.org> - 2016-03-13 14:00 +0100
Re: tracking security issues without CVEs Antoine Beaupré <anarcat@orangeseeds.org> - 2016-03-22 15:30 +0100
Re: tracking security issues without CVEs Paul Wise <pabs@debian.org> - 2016-03-23 04:10 +0100
Re: tracking security issues without CVEs Michael Stone <mstone@debian.org> - 2016-03-23 20:10 +0100
Re: tracking security issues without CVEs Andrew Deck <andrew.hastings.deck@gmail.com> - 2016-03-28 16:40 +0200
Re: tracking security issues without CVEs Paul Wise <pabs@debian.org> - 2016-04-28 08:30 +0200
csiph-web