Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Ross Burton <ross.burton@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] iputils: Whitelist CVE-2000-1213 CVE-2000-1214
Date: Tue, 5 Nov 2019 13:01:16 +0200	[thread overview]
Message-ID: <20191105110116.GA20425@localhost> (raw)
In-Reply-To: <aa3aa480-65d5-789c-71c0-3997d742424e@intel.com>

On Tue, Nov 05, 2019 at 10:38:32AM +0000, Ross Burton wrote:
> On 04/11/2019 20:55, Adrian Bunk wrote:
> > +# Fixed in 2000-10-10, but the versioning of iputils
> > +# breaks the version order.
> > +CVE_CHECK_WHITELIST += "CVE-2000-1213 CVE-2000-1214"
> 
> So the problem is that our PV matches the upstream git tags, which don't
> match the naming convention in the CPE entries.
> 
> The tags are of the form s20190709, but the CPE uses 2010-10-10.
> 
> If we assume that the CPE version scheme will remain the same
>...

CVE-2010-2529 had an explicit list of affected versions of the
scheme 20100214.

These 19 year old ones from a time when CVE was new are outliers.
I would expect versions in new CVE to match the OE versioning,
except that the 's' might (or might not) be missing.

> Ross

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed



  reply	other threads:[~2019-11-05 11:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-04 20:55 [PATCH] iputils: Whitelist CVE-2000-1213 CVE-2000-1214 Adrian Bunk
2019-11-05 10:38 ` Ross Burton
2019-11-05 11:01   ` Adrian Bunk [this message]
2019-11-05 11:59     ` Ross Burton
2019-11-11 10:43 ` Adrian Bunk

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=20191105110116.GA20425@localhost \
    --to=bunk@stusta.de \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.com \
    /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