From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: Pierre-Jean Texier <texier.pj2@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/libarchive: fix CVE-2022-36227
Date: Sat, 3 Dec 2022 15:32:20 +0100 [thread overview]
Message-ID: <20221203153220.4efe9f1e@windsurf> (raw)
In-Reply-To: <20221202215905.7800-1-fontaine.fabrice@gmail.com>
On Fri, 2 Dec 2022 22:59:05 +0100
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> In libarchive 3.6.1, the software does not check for an error after
> calling calloc function that can return with a NULL pointer if the
> function fails, which leads to a resultant NULL pointer dereference.
> NOTE: the discoverer cites this CWE-476 remark but third parties dispute
> the code-execution impact: "In rare circumstances, when NULL is
> equivalent to the 0x0 memory address and privileged code can access it,
> then writing or reading memory is possible, which may lead to code
> execution."
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
> ...chive-Handle-a-calloc-returning-NULL.patch | 38 +++++++++++++++++++
> package/libarchive/libarchive.mk | 3 ++
> 2 files changed, 41 insertions(+)
> create mode 100644 package/libarchive/0001-libarchive-Handle-a-calloc-returning-NULL.patch
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-12-03 14:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 21:59 [Buildroot] [PATCH 1/1] package/libarchive: fix CVE-2022-36227 Fabrice Fontaine
2022-12-03 14:32 ` Thomas Petazzoni via buildroot [this message]
2022-12-07 13:36 ` 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=20221203153220.4efe9f1e@windsurf \
--to=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.com \
--cc=texier.pj2@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.