Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Matthew Weber <matthew.weber@collins.com>
Cc: "buildroot@uclibc.org" <buildroot@uclibc.org>,
	"Yann E. MORIN" <yann.morin.1998@free.fr>
Subject: [Buildroot] Adding new products in the CPE database ?
Date: Mon, 4 Oct 2021 09:49:15 +0200	[thread overview]
Message-ID: <20211004094915.516ef395@windsurf> (raw)

Hello Matt,

I was wondering what was the process to add a new product in the CPE
database.

Indeed, I was investigating
https://security-tracker.debian.org/tracker/CVE-2011-3332, which is
affecting our "argus" package.

However CVE-2011-3332 affects the Argus product from Iceni, a PDF
extracting tool at https://www.iceni.com/legacy.htm.

This is completely different than the Argus package we have, which is
https://openargus.org/.

The NVD CPE database has several Argus products known:
https://nvd.nist.gov/products/cpe/search/results?namingFormat=2.3&keyword=argus.
From Iceni, from Oracle, from Litronic. But none of them correspond to
the Argus that we have packaged.

So I guess we need to tell the NVD people to add an entry in the CPE
database for this other Argus product, so that we can then amend our
argus.mk package with the appropriate CPE ID information.

Thanks for your feedback!

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

             reply	other threads:[~2021-10-04  7:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-04  7:49 Thomas Petazzoni [this message]
2021-10-05 19:01 ` [Buildroot] Adding new products in the CPE database ? Arnout Vandecappelle
2021-10-05 19:12   ` [Buildroot] [External] " Weber, Matthew L Collins via buildroot

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=20211004094915.516ef395@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@uclibc.org \
    --cc=matthew.weber@collins.com \
    --cc=yann.morin.1998@free.fr \
    /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