Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
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 3/3] package/glibc: ignore CVE-2023-0687, disputed
Date: Sat, 23 Dec 2023 11:19:57 +0100	[thread overview]
Message-ID: <ZYa0TdSBU2JrexMt@landeda> (raw)
In-Reply-To: <20231220200110.1819507-3-thomas.petazzoni@bootlin.com>

Thomas, All,

On 2023-12-20 21:01 +0100, Thomas Petazzoni spake thusly:
> According to the glibc maintainers, CVE-2023-0687 is not a security
> issue, and they have sent a rejection request to MITRE, so let's
> ignore it.

This CVE is supposed to be fixed by 801af9fafd46 (gmon: Fix allocated
buffer overflow (bug 29444)) which is in 2.38:

    $ git tag --contains 801af9fafd46
    glibc-2.38
    glibc-2.38.9000

So the CVE DB should be updated to state that glibc >= 2.38 is not
affected.

Regards,
Yann E. MORIN.

> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
> ---
> I have chosen to submit this one separately from the previous patch,
> as it's a much newer one, so the Buildroot community may have a
> different view on how we should handle this particular CVE.
> ---
>  package/glibc/glibc.mk | 5 +++++
>  1 file changed, 5 insertions(+)
> 
> diff --git a/package/glibc/glibc.mk b/package/glibc/glibc.mk
> index 29411c58e2..a485d40f8d 100644
> --- a/package/glibc/glibc.mk
> +++ b/package/glibc/glibc.mk
> @@ -50,6 +50,11 @@ GLIBC_IGNORE_CVES += \
>  	CVE-2019-1010024 \
>  	CVE-2019-1010025
>  
> +# This CVE is disputed, and the glibc maintainers don't consider it to
> +# be a security issue, see
> +# https://sourceware.org/bugzilla/show_bug.cgi?id=29444
> +GLIBC_IGNORE_CVES += CVE-2023-0687
> +
>  # 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

  reply	other threads:[~2023-12-23 10:20 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 [this message]
2024-02-06 14:13     ` Thomas Petazzoni via buildroot
2023-12-23 10:20 ` [Buildroot] [PATCH 1/3] package/glibc: add proper CPE ID version detail Yann E. MORIN
2024-01-07 22:26 ` 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=ZYa0TdSBU2JrexMt@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox