Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Perale via buildroot <buildroot@buildroot.org>
To: buildroot@buildroot.org
Cc: Thomas Perale <thomas.perale@mind.be>,
	Ricardo Martincoski <ricardo.martincoski@datacom.com.br>
Subject: [Buildroot] [RFC PATCH 05/14] package/sox: add vulnerabilities details
Date: Wed, 24 Jun 2026 16:06:36 +0200	[thread overview]
Message-ID: <20260624140645.185318-6-thomas.perale@mind.be> (raw)
In-Reply-To: <20260624140645.185318-1-thomas.perale@mind.be>

All the vulnerabilities have been already fixed in the upstream used by
Buildroot but no new upstream version have been created. The CPE still
reference the last known version.

Signed-off-by: Thomas Perale <thomas.perale@mind.be>
---
 package/sox/sox.mk | 41 ++++++++++++++++++++++++++++-------------
 1 file changed, 28 insertions(+), 13 deletions(-)

diff --git a/package/sox/sox.mk b/package/sox/sox.mk
index 9fd3f2151c..90121cd02c 100644
--- a/package/sox/sox.mk
+++ b/package/sox/sox.mk
@@ -19,45 +19,60 @@ SOX_AUTORECONF = YES
 SOX_AUTORECONF_OPTS = --include=$(HOST_DIR)/share/autoconf-archive
 SOX_INSTALL_STAGING = YES
 
-# sox-14.4.2-6-g6e177c45
 SOX_IGNORE_CVES += CVE-2017-11332
+SOX_CVE-2017-11332_STATUS = fixed
+SOX_CVE-2017-11332_DETAIL = sox-14.4.2-6-g6e177c45
 
-# sox-14.4.2-7-ge410d00c
 SOX_IGNORE_CVES += CVE-2017-11358
+SOX_CVE-2017-11358_STATUS = fixed
+SOX_CVE-2017-11358_DETAIL = sox-14.4.2-7-ge410d00c
 
-# sox-14.4.2-8-g7b3f30e1
 SOX_IGNORE_CVES += CVE-2017-11359
+SOX_CVE-2017-11359_STATUS = fixed
+SOX_CVE-2017-11359_DETAIL = sox-14.4.2-8-g7b3f30e1
 
-# sox-14.4.2-9-ge076a7ad
 SOX_IGNORE_CVES += CVE-2017-15370
+SOX_CVE-2017-11370_STATUS = fixed
+SOX_CVE-2017-11370_DETAIL = sox-14.4.2-9-ge076a7ad
 
-# sox-14.4.2-10-g968c689a
 SOX_IGNORE_CVES += CVE-2017-15371
+SOX_CVE-2017-11371_STATUS = fixed
+SOX_CVE-2017-11371_DETAIL = sox-14.4.2-10-g968c689a
 
-# sox-14.4.2-11-g515b9861
 SOX_IGNORE_CVES += CVE-2017-15372
+SOX_CVE-2017-11372_STATUS = fixed
+SOX_CVE-2017-11372_DETAIL = sox-14.4.2-11-g515b9861
 
-# sox-14.4.2-12-gf56c0dbc
 SOX_IGNORE_CVES += CVE-2017-15642
+SOX_CVE-2017-15642_STATUS = fixed
+SOX_CVE-2017-15642_DETAIL = sox-14.4.2-12-gf56c0dbc
 
-# sox-14.4.2-13-g09d7388c
 # CVE-2019-1010004 is a duplicate of CVE-2017-18189
 SOX_IGNORE_CVES += CVE-2017-18189 CVE-2019-1010004
+SOX_CVE-2017-18189_STATUS = fixed
+SOX_CVE-2017-18189_DETAIL = sox-14.4.2-13-g09d7388c
+SOX_CVE-2019-1010004_STATUS = fixed
+SOX_CVE-2019-1010004_DETAIL = sox-14.4.2-13-g09d7388c
 
-# sox-14.4.2-38-gf7091126
 SOX_IGNORE_CVES += CVE-2019-8354
+SOX_CVE-2019-8354_STATUS = fixed
+SOX_CVE-2019-8354_DETAIL = sox-14.4.2-38-gf7091126
 
-# sox-14.4.2-39-gf8587e2d
 SOX_IGNORE_CVES += CVE-2019-8355
+SOX_CVE-2019-8355_STATUS = fixed
+SOX_CVE-2019-8355_DETAIL = sox-14.4.2-39-gf8587e2d
 
-# sox-14.4.2-40-gb7883ae1
 SOX_IGNORE_CVES += CVE-2019-8356
+SOX_CVE-2019-8356_STATUS = fixed
+SOX_CVE-2019-8356_DETAIL = sox-14.4.2-40-gb7883ae1
 
-# sox-14.4.2-41-g2ce02fea
 SOX_IGNORE_CVES += CVE-2019-8357
+SOX_CVE-2019-8357_STATUS = fixed
+SOX_CVE-2019-8357_DETAIL = sox-14.4.2-41-g2ce02fea
 
-# sox-14.4.2-44-g7b6a8892
 SOX_IGNORE_CVES += CVE-2019-13590
+SOX_CVE-2019-13590_STATUS = fixed
+SOX_CVE-2019-13590_DETAIL = sox-14.4.2-44-g7b6a8892
 
 # 0006-voc-word-width-should-never-be-0-to-avoid-division-b.patch
 # This entry is NOT stale, those CVEs are not reported by pkg-stats
-- 
2.54.0

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2026-06-24 14:07 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-24 14:06 [Buildroot] [RFC PATCH 00/14] Add exportable vulnerability informations Thomas Perale via buildroot
2026-06-24 14:06 ` [Buildroot] [RFC PATCH 01/14] docs/manual: add vulnerability status and justification Thomas Perale via buildroot
2026-06-24 14:06 ` [Buildroot] [RFC PATCH 02/14] utils/checkpackagelib/lib_mk.py: check _STATUS value is supported Thomas Perale via buildroot
2026-06-24 14:06 ` [Buildroot] [RFC PATCH 03/14] package/pkg-utils: show-info expose vuln details Thomas Perale via buildroot
2026-06-24 14:06 ` [Buildroot] [RFC PATCH 04/14] utils/generate-cyclonedx: support vulnerability details Thomas Perale via buildroot
2026-06-25 18:01   ` Fiona Klute via buildroot
2026-06-24 14:06 ` Thomas Perale via buildroot [this message]
2026-06-24 14:06 ` [Buildroot] [RFC PATCH 06/14] package/php: add " Thomas Perale via buildroot
2026-06-24 14:06 ` [Buildroot] [RFC PATCH 07/14] package/mupdf: add vulnerabilities details Thomas Perale via buildroot
2026-06-24 14:06 ` [Buildroot] [RFC PATCH 08/14] package/python-pip: add detail to vulnerability Thomas Perale via buildroot
2026-06-25 17:57   ` Fiona Klute via buildroot
2026-06-26  7:25     ` Thomas Perale via buildroot
2026-06-24 14:06 ` [Buildroot] [RFC PATCH 09/14] package/luajit: add details to vulnerabilities Thomas Perale via buildroot
2026-06-24 14:06 ` [Buildroot] [RFC PATCH 10/14] package/libuci: add vulnerability details Thomas Perale via buildroot
2026-06-24 14:06 ` [Buildroot] [RFC PATCH 11/14] package/glibc: " Thomas Perale via buildroot
2026-06-24 14:45   ` Romain Naour via buildroot
2026-06-24 15:06     ` Thomas Perale via buildroot
2026-06-24 14:06 ` [Buildroot] [RFC PATCH 12/14] package/freeradius-server: add vulnerabilities details Thomas Perale via buildroot
2026-06-24 14:06 ` [Buildroot] [RFC PATCH 13/14] package/flex: add vulnerability details Thomas Perale via buildroot
2026-06-24 14:06 ` [Buildroot] [RFC PATCH 14/14] package/clamav: " Thomas Perale 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=20260624140645.185318-6-thomas.perale@mind.be \
    --to=buildroot@buildroot.org \
    --cc=ricardo.martincoski@datacom.com.br \
    --cc=thomas.perale@mind.be \
    /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