From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 13366] New: make pkg-stats: unrelated CVEs linked to linux package
Date: Tue, 08 Dec 2020 12:57:56 +0000 [thread overview]
Message-ID: <bug-13366-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=13366
Bug ID: 13366
Summary: make pkg-stats: unrelated CVEs linked to linux package
Product: buildroot
Version: 2020.11
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: seems.deviant at gmail.com
CC: buildroot at uclibc.org
Target Milestone: ---
Created attachment 8701
--> https://bugs.busybox.net/attachment.cgi?id=8701&action=edit
hypertext
Steps to reproduce:
$ cat <<EOF > .config
> BR2_LINUX_KERNEL=y
> BR2_LINUX_KERNEL_USE_ARCH_DEFAULT_CONFIG=y
> EOF
$ make pkg-stats
In my case, there are 110 CVEs linked to linux package, while most of them or
none at all are related.
The last three entries in CVEs column:
https://security-tracker.debian.org/tracker/CVE-2013-2032 - mediawiki
https://security-tracker.debian.org/tracker/CVE-2014-3250 - puppet
https://security-tracker.debian.org/tracker/CVE-2014-4909 - transmission
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2020-12-08 12:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-08 12:57 bugzilla at busybox.net [this message]
2020-12-08 13:40 ` [Buildroot] [Bug 13366] make pkg-stats: unrelated CVEs linked to linux package bugzilla at busybox.net
2020-12-08 14:47 ` bugzilla at busybox.net
2020-12-08 14:53 ` bugzilla at busybox.net
2020-12-09 9:33 ` bugzilla at busybox.net
2024-06-15 14:55 ` bugzilla
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=bug-13366-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox