Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Anuj Mittal" <anuj.mittal@intel.com>
To: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>,
	"steve@sakoman.com" <steve@sakoman.com>,
	"yocto-security@lists.yoctoproject.org"
	<yocto-security@lists.yoctoproject.org>
Subject: Re: [OE-core] OE-core CVE metrics for hardknott on Sun 12 Sep 2021 05:00:01 AM HST
Date: Wed, 15 Sep 2021 16:58:56 +0000	[thread overview]
Message-ID: <643057cf221a41e13ae92c496ad6358a2a6db265.camel@intel.com> (raw)
In-Reply-To: <20210912150121.8237296032A@nuc.router0800d9.com>

Can we also set commercial flag while generating this list so recipes
like ffmpeg are also picked up?

Thanks,

Anuj

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 *
> 
> Full list:  Found 27 unpatched CVEs
> CVE-2013-0340: expat:expat-native
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2013-0340 *
> CVE-2019-12067: qemu:qemu-native:qemu-system-native
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-12067 *
> CVE-2019-6293: flex:flex-native
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-6293 *
> CVE-2019-6470: bind
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-6470 *
> CVE-2020-18974: nasm:nasm-native
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-18974 *
> CVE-2020-29623: webkitgtk
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-29623 *
> CVE-2020-35503: qemu:qemu-native:qemu-system-native
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-35503 *
> CVE-2021-0129: bluez5
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-0129 *
> CVE-2021-1765: webkitgtk
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-1765 *
> CVE-2021-1789: webkitgtk
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-1789 *
> CVE-2021-1799: webkitgtk
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-1799 *
> CVE-2021-1801: webkitgtk
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-1801 *
> CVE-2021-1870: webkitgtk
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-1870 *
> CVE-2021-20196: qemu:qemu-native:qemu-system-native
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-20196 *
> CVE-2021-20255: qemu:qemu-native:qemu-system-native
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-20255 *
> CVE-2021-22922: curl:curl-native
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-22922 *
> CVE-2021-22923: curl:curl-native
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-22923 *
> CVE-2021-29923: go
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-29923 *
> CVE-2021-31810: ruby:ruby-native
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-31810 *
> CVE-2021-31879: wget
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-31879 *
> CVE-2021-32066: ruby:ruby-native
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-32066 *
> CVE-2021-3445: libdnf
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3445 *
> CVE-2021-3507: qemu:qemu-native:qemu-system-native
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3507 *
> CVE-2021-35331: tcl:tcl-native
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-35331 *
> CVE-2021-3682: qemu:qemu-native:qemu-system-native
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3682 *
> CVE-2021-36976: libarchive
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-36976 *
> CVE-2021-3713: qemu:qemu-native:qemu-system-native
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3713 *
> 
> 
> 


  parent reply	other threads:[~2021-09-15 16:58 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
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 ` Anuj Mittal [this message]
2021-09-15 17:03   ` [OE-core] " 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=643057cf221a41e13ae92c496ad6358a2a6db265.camel@intel.com \
    --to=anuj.mittal@intel.com \
    --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