From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: peter.verbrugge@technolution.nl,
Romain Naour <romain.naour@gmail.com>,
Buildroot List <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH 1/3] package/glibc: add proper CPE ID version detail
Date: Sat, 23 Dec 2023 11:20:52 +0100 [thread overview]
Message-ID: <ZYa0hAkGmnEJFaaa@landeda> (raw)
In-Reply-To: <20231220200110.1819507-1-thomas.petazzoni@bootlin.com>
Thomas, All,
On 2023-12-20 21:01 +0100, Thomas Petazzoni spake thusly:
> As reported in bug 15895, the GLIBC_VERSION field having a value
> looking like 2.38-27-g750a45a783906a19591fb8ff6b7841470f1f5701, it
> prevents the CPE/CVE matching with the NVD database to work correctly.
>
> This commit fixes that by defining GLIBC_CPE_ID_VERSION, derived from
> GLIBC_VERSION, by extracting the base version.
>
> Also, we update GLIBC_IGNORE_CVES to account for the CVEs that have
> clearly been fixed between 2.38 and
> 2.38-27-g750a45a783906a19591fb8ff6b7841470f1f5701. There are a number
> of other CVEs still affecting the glibc package, but they are not
> related to this
> 2.38...2.38-27-g750a45a783906a19591fb8ff6b7841470f1f5701 range.
>
> Fixes: #15895
>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Applied to master, thanks.
Regards,
Yann E. MORIN.
> ---
> package/glibc/glibc.mk | 16 ++++++++++++++++
> 1 file changed, 16 insertions(+)
>
> diff --git a/package/glibc/glibc.mk b/package/glibc/glibc.mk
> index 0b71530310..32e6516c7f 100644
> --- a/package/glibc/glibc.mk
> +++ b/package/glibc/glibc.mk
> @@ -20,6 +20,22 @@ GLIBC_LICENSE = GPL-2.0+ (programs), LGPL-2.1+, BSD-3-Clause, MIT (library)
> GLIBC_LICENSE_FILES = COPYING COPYING.LIB LICENSES
> GLIBC_CPE_ID_VENDOR = gnu
>
> +# Extract the base version (e.g. 2.38) from GLIBC_VERSION) in order to
> +# allow proper matching with the CPE database.
> +GLIBC_CPE_ID_VERSION = $(word 1, $(subst -,$(space),$(GLIBC_VERSION)))
> +
> +# Fixed by b25508dd774b617f99419bdc3cf2ace4560cd2d6, which is between
> +# 2.38 and the version we're really using
> +GLIBC_IGNORE_CVES += CVE-2023-4527
> +
> +# Fixed by 750a45a783906a19591fb8ff6b7841470f1f5710, which is between
> +# 2.38 and the version we're really using.
> +GLIBC_IGNORE_CVES += CVE-2023-4911
> +
> +# Fixed by 5ee59ca371b99984232d7584fe2b1a758b4421d3, which is between
> +# 2.38 and the version we're really using.
> +GLIBC_IGNORE_CVES += CVE-2023-5156
> +
> # glibc is part of the toolchain so disable the toolchain dependency
> GLIBC_ADD_TOOLCHAIN_DEPENDENCY = NO
>
> --
> 2.43.0
>
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-12-23 10:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-20 20:01 [Buildroot] [PATCH 1/3] package/glibc: add proper CPE ID version detail Thomas Petazzoni via buildroot
2023-12-20 20:01 ` [Buildroot] [PATCH 2/3] package/glibc: ignore CVEs not considered as security issues by upstream Thomas Petazzoni via buildroot
2023-12-23 10:22 ` Yann E. MORIN
2024-01-07 22:26 ` Peter Korsgaard
2023-12-20 20:01 ` [Buildroot] [PATCH 3/3] package/glibc: ignore CVE-2023-0687, disputed Thomas Petazzoni via buildroot
2023-12-23 10:19 ` Yann E. MORIN
2024-02-06 14:13 ` Thomas Petazzoni via buildroot
2023-12-23 10:20 ` Yann E. MORIN [this message]
2024-01-07 22:26 ` [Buildroot] [PATCH 1/3] package/glibc: add proper CPE ID version detail Peter Korsgaard
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=ZYa0hAkGmnEJFaaa@landeda \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--cc=peter.verbrugge@technolution.nl \
--cc=romain.naour@gmail.com \
--cc=thomas.petazzoni@bootlin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.