All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Adam Duskett <aduskett@gmail.com>
Cc: Tudor Holton <buildroot@tudorholton.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/openjdk{-bin}: security bump versions to 11.0.20+8 and 17.0.8+7
Date: Wed, 30 Aug 2023 23:58:03 +0200	[thread overview]
Message-ID: <20230830235803.2de7c788@windsurf> (raw)
In-Reply-To: <20230830155926.2831345-1-aduskett@gmail.com>

Hello Adam,

On Wed, 30 Aug 2023 09:59:26 -0600
Adam Duskett <aduskett@gmail.com> wrote:

> Fixed the following security issues:
> 
> * CVEs
>   - CVE-2023-22006
>   - CVE-2023-22036
>   - CVE-2023-22041
>   - CVE-2023-22044
>   - CVE-2023-22045
>   - CVE-2023-22049
>   - CVE-2023-25193

One thing that bothers me is that none of these CVEs were identified by our pkg-stats script:

  http://autobuild.buildroot.net/stats/master.html

https://nvd.nist.gov/vuln/detail/CVE-2023-25193 is reported against
harfbuzz, not openjdk. Are we using a vendored version of harfbuzz in
openjdk?

Could you check the other CVEs and figure out why pkg-stats doesn't find them?

Thanks!

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

  parent reply	other threads:[~2023-08-30 21:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-30 15:59 [Buildroot] [PATCH 1/1] package/openjdk{-bin}: security bump versions to 11.0.20+8 and 17.0.8+7 Adam Duskett
2023-08-30 19:41 ` Arnout Vandecappelle via buildroot
2023-08-30 20:02 ` Arnout Vandecappelle via buildroot
2023-08-30 21:58 ` Thomas Petazzoni via buildroot [this message]
2023-09-13 20:09 ` 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=20230830235803.2de7c788@windsurf \
    --to=buildroot@buildroot.org \
    --cc=aduskett@gmail.com \
    --cc=buildroot@tudorholton.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.