From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@buildroot.org
Cc: "Yann E . MORIN" <yann.morin.1998@free.fr>,
Vincent Fazio <vfazio@gmail.com>
Subject: Re: [Buildroot] [PATCH 3/4] package/tar: add upstream patch for CVE-2022-48303
Date: Tue, 14 Nov 2023 08:57:29 +0100 [thread overview]
Message-ID: <87pm0cdaxi.fsf@48ers.dk> (raw)
In-Reply-To: <20231112194326.2539029-3-peter@korsgaard.com> (Peter Korsgaard's message of "Sun, 12 Nov 2023 20:43:24 +0100")
>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:
> Fixes CVE-2022-48303: GNU Tar through 1.34 has a one-byte out-of-bounds read
> that results in use of uninitialized memory for a conditional jump.
> Exploitation to change the flow of control has not been demonstrated. The
> issue occurs in from_header in list.c via a V7 archive in which mtime has
> approximately 11 whitespace characters.
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Committed to 2023.02.x and 2023.08.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-11-14 7:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-12 19:43 [Buildroot] [PATCH 1/4] Revert "package/tar: allowing building even on non-Y2038 compliant systems" Peter Korsgaard
2023-11-12 19:43 ` [Buildroot] [PATCH 2/4] Revert "package/tar: security bump to version 1.35" Peter Korsgaard
2023-11-13 21:51 ` Peter Korsgaard
2023-11-14 7:57 ` Peter Korsgaard
2023-11-12 19:43 ` [Buildroot] [PATCH 3/4] package/tar: add upstream patch for CVE-2022-48303 Peter Korsgaard
2023-11-13 21:52 ` Peter Korsgaard
2023-11-14 7:57 ` Peter Korsgaard [this message]
2023-11-12 19:43 ` [Buildroot] [PATCH 4/4] support/dependencies/check-host-tar.sh: blacklist tar 1.35+ Peter Korsgaard
2023-11-13 21:52 ` Peter Korsgaard
2023-11-14 7:57 ` Peter Korsgaard
2023-11-13 21:51 ` [Buildroot] [PATCH 1/4] Revert "package/tar: allowing building even on non-Y2038 compliant systems" 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=87pm0cdaxi.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=vfazio@gmail.com \
--cc=yann.morin.1998@free.fr \
/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.