All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua Kinard <kumba@gentoo.org>
To: buildroot@busybox.net
Subject: [Buildroot] RFC: CVE analysis
Date: Tue, 23 Sep 2014 18:06:05 -0400	[thread overview]
Message-ID: <5421EECD.6050806@gentoo.org> (raw)
In-Reply-To: <542088A8.2080902@zacarias.com.ar>

On 09/22/2014 16:38, Gustavo Zacarias wrote:
> On 09/22/2014 05:21 PM, Matthew Weber wrote:
> 
>> I was curious if anyone has done a script similar to the "make
>> legal-info" that takes a package list and checks it against a CVE
>> database?  We're looking at doing some automated tracking of
>> vulnerabilities with our nightly builds and were at a point of putting
>> something together.
>>
>> It might also be an interesting feature to expose on the Buildroot
>> website.... maybe listing the current vulnerabilities of the last
>> release and the current tip?
> 
> Hi.
> I usually track CVEs and bump/fix when appropiate.
> It's mostly a mix of personal scripts, nothing too fancy that i'd like
> normal people to see in the current state :)
> The problem with actively pursuing security fixes is that it needs some
> regular manpower in patching and testing, and that's without considering
> backports (though the package infra is quite stable lately).
> There are outstanding packages that have some severe vulnerabilities
> like cups where i did a call for volunteers to bump/fix without much
> success, and i can only do so much in my free time, with cups being
> somewhat complicated to test because of varying combinations.
> It's not a task that can really be fully automated either because you
> can get a CVE for say PHP that fixes a vulnerability that only affects
> windows operating systems - there must be some context analysis as well.
> I normally try to maintain some format for my security bumps/fixes but
> that's completely informal, like:
> 
> Subject: Security bump PACKAGE to version x.y
> Fixes:
> CVE-yyyy-nnnn - short description
> 
> But then some other people might catch the bump before myself and there
> goes that.
> 
> Something nicer would probably be like the .hash files for packages
> where we could describe the bumps that affect security and the relevant
> CVEs.

I don't know if these two sites have a formal API that's queryable, but you can
generate RSS feeds based on criteria, so maybe something programmatic can be setup:

http://www.cvedetails.com/
http://www.itsecdb.com/oval/


Also, these deal more with cyber-threat information, but has ties into
vulnerability research and are both developed by the MITRE corporation (who
manages the CVE database):

https://stix.mitre.org/
http://taxii.mitre.org/

-- 
Joshua Kinard
Gentoo/MIPS
kumba at gentoo.org
4096R/D25D95E3 2011-03-28

"The past tempts us, the present confuses us, the future frightens us.  And our
lives slip away, moment by moment, lost in that vast, terrible in-between."

--Emperor Turhan, Centauri Republic

  parent reply	other threads:[~2014-09-23 22:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-22 20:21 [Buildroot] RFC: CVE analysis Matthew Weber
2014-09-22 20:38 ` Gustavo Zacarias
2014-09-22 21:12   ` Matthew Weber
2014-09-23  7:43     ` Thomas Petazzoni
2014-09-23 22:06   ` Joshua Kinard [this message]
2014-09-23 22:50     ` Matthew Weber

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5421EECD.6050806@gentoo.org \
    --to=kumba@gentoo.org \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.