From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Steve Sakoman <steve@sakoman.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>,
yocto-security@lists.yoctoproject.org
Subject: Re: [OE-core] [yocto-security] OE-core CVE metrics for hardknott on Sun 12 Sep 2021 05:00:01 AM HST
Date: Mon, 13 Sep 2021 18:01:13 +0100 [thread overview]
Message-ID: <5a6a112b92ba3921ba31bc648f37f9cff2687f49.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAOSpxda2cHN3d0WDMLszq8QJD0-Qa37e0NU57Xu21EXR672oFg@mail.gmail.com>
On Mon, 2021-09-13 at 05:19 -1000, Steve Sakoman wrote:
> On Sun, Sep 12, 2021 at 6:05 AM Steve Sakoman via
> lists.openembedded.org <steve=sakoman.com@lists.openembedded.org>
> wrote:
> >
> >
> >
> > On Sun, Sep 12, 2021, 5:57 AM Richard Purdie <richard.purdie@linuxfoundation.org> wrote:
> > >
> > > On Sun, 2021-09-12 at 05:01 -1000, Steve Sakoman wrote:
> > > > Branch: hardknott
> > > >
> > > > New this week: 0 CVEs
> > > >
> > > > Removed this week: 2 CVEs
> > > > CVE-2020-27748: xdg-utils https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-27748 *
> > > > CVE-2021-38185: cpio https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-38185 *
> > >
> > > I'm not sure I believe these numbers as tar CVEs which showed up for dunfell and
> > > master don't show up here. Why? :/
> >
> >
> > Don't know! Will investigate tomorrow.
>
> I re-ran the hardknott report this morning and it now includes the
> missing tar cve's (as well as the libsolv, vim, and inetutils cve's we
> saw in master/dunfell)
>
> No idea why these weren't in yesterday's report since they were
> obviously in the upstream database and appeared in the master and
> dunfell runs (and hardknott runs last)
>
> I've seen this kind of thing once or twice in the past and have never
> been able to figure out what is going on since it is so intermittent.
I'm not sure how we pull the database but is it possible that there are multiple
upstream servers of that data and we pull from different instances which may not
have all updated to the same data? Would there be any way to investigate/prove
that?
I'm a little worried about the inconsistencies. I'm guessing your builds don't
share a DL_DIR so they'd fetch different CVE databases?
Cheers,
Richard
next prev parent reply other threads:[~2021-09-13 17:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-12 15:01 OE-core CVE metrics for hardknott on Sun 12 Sep 2021 05:00:01 AM HST Steve Sakoman
2021-09-12 15:57 ` [yocto-security] " Richard Purdie
2021-09-12 16:04 ` Steve Sakoman
[not found] ` <16A41EB09718E439.21276@lists.openembedded.org>
2021-09-13 15:19 ` [OE-core] " Steve Sakoman
2021-09-13 17:01 ` Richard Purdie [this message]
2021-09-13 17:26 ` Steve Sakoman
2021-09-15 11:08 ` Ross Burton
2021-09-15 14:09 ` Steve Sakoman
2021-09-15 16:58 ` [OE-core] " Anuj Mittal
2021-09-15 17:03 ` Steve Sakoman
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=5a6a112b92ba3921ba31bc648f37f9cff2687f49.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=steve@sakoman.com \
--cc=yocto-security@lists.yoctoproject.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox