Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Peter Korsgaard <peter@korsgaard.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [git commit] package/dmidecode: bump to version 3.5
Date: Mon, 28 Aug 2023 23:59:35 +0200	[thread overview]
Message-ID: <20230828235935.4dcd6b5a@windsurf> (raw)
In-Reply-To: <20230627061104.9EB9285B2A@busybox.osuosl.org>

Hello Peter,

On Tue, 27 Jun 2023 07:48:40 +0200
Peter Korsgaard <peter@korsgaard.com> wrote:

> commit: https://git.buildroot.net/buildroot/commit/?id=c97f27283b36ffc39dfb6223caee6055997b3234
> branch: https://git.buildroot.net/buildroot/commit/?id=refs/heads/master
> 
> For change log, see:
> https://git.savannah.gnu.org/cgit/dmidecode.git/tree/NEWS?h=dmidecode-3-5
> 
> Note: this patch also adds a comment about pgp signature verification in
> the hash file.
> 
> Signed-off-by: Julien Olivain <ju.o@free.fr>
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>

FYI: this is a security bump, as it fixes
https://nvd.nist.gov/vuln/detail/CVE-2023-30630. "Dmidecode before 3.5
allows -dump-bin to overwrite a local file. This has security relevance
because, for example, execution of Dmidecode via Sudo is plausible."

Therefore, it needs to be backported to 2023.02.x and 2023.05.x, or
alternatively:

  https://git.savannah.nongnu.org/cgit/dmidecode.git/commit/?id=d8cfbc808f387e87091c25e7d5b8c2bb348bb206
  https://git.savannah.nongnu.org/cgit/dmidecode.git/commit/?id=6ca381c1247c81f74e1ca4e7706f70bdda72e6f2

need to be backported. However, there are only 20 commits between
dmidecode 3.4 (which is in Buildroot 2023.02.x) and dmidecode 3.5
(which fixes this CVE):

484f8935b0fc768841f43fa388b191196b5e12fd (tag: dmidecode-3-5) Set the version to 3.5
8baf2f508c6eb5359f12c911a0d58b893c12f1ca Fix a build warning when USE_MMAP isn't set
b9ebecc6391c4ad36ce0088b93ca8333c2f05ee7 dmioem: HPE type 242: Fix ID on 32-bit systems
189ca352e9341778c21e95c27817574b2876ede7 Ensure /dev/mem is a character device file
8427888ccf068f2ae1105e0c9276a15191a16ee5 dmidecode: Use the right variable for -s bios-revision/firmware-revision
6ca381c1247c81f74e1ca4e7706f70bdda72e6f2 dmidecode: Do not let --dump-bin overwrite an existing file
d8cfbc808f387e87091c25e7d5b8c2bb348bb206 dmidecode: Write the whole dump file at once
39b2dd7b6ab719b920e96ed832cfb4bdd664e808 dmidecode: Split table fetching from decoding
11b168f206efe5b3ebe2f1e587fb3d816d6c4a6f dmioem: Avoid intermediate buffer (HPE type 216)
9d2bbd5db427b063da137d9016fe6628038334eb dmioem: Decode HPE OEM Record 216
3d6835047f80691678e5db3127f9d573956413f0 dmidecode: Drop the CPUID exception list
c1a2520433a31294fe9a0ccb52136d048f2d76e6 dmidecode: Add a --no-quirks option
67dc0b27d50e3986d5e7cd35ec25cc5901a2e9e9 dmidecode: Fortify entry point length checks
f8016734735486c99eacc1bca975913535905c1f dmioem: Typo fix (Virutal -> Virtual)
90d1323a8d14acbf32154c03074e3caf94b1e7a1 dmioem: Decode HPE OEM Record 242
f50b925c8d43ab2470fe750c49bd33c9a5f3bd1d dmioem: Update HPE OEM Record 238
ac24b672dee81cdbfb35b69b38459a1352dcbe8a dmioem: Decode HPE OEM Record 230
c3357b532941a8df387618e692e522cc7a43b3e8 dmioem: Fix segmentation fault in dmi_hp_240_attr()
a1a2258ffbe450e8561ee833787da9321fa734b0 dmioem: Decode HPE OEM Record 224
fb8766a9d26053b3ad5f6228ffaf09690b7cac90 NEWS: Fix typo

So getting dmidecode 3.5 in Buildroot 2023.02 and 2023.05 is probably OK.

Best regards,

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

  reply	other threads:[~2023-08-28 21:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-27  5:48 [Buildroot] [git commit] package/dmidecode: bump to version 3.5 Peter Korsgaard
2023-08-28 21:59 ` Thomas Petazzoni via buildroot [this message]
2023-08-29  8:55   ` Peter Korsgaard
2023-08-29  9:08     ` Thomas Petazzoni 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=20230828235935.4dcd6b5a@windsurf \
    --to=buildroot@buildroot.org \
    --cc=peter@korsgaard.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