From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2, 1/3] package/libarchive: security bump to version 3.4.2
Date: Sat, 14 Mar 2020 18:39:16 +0100 [thread overview]
Message-ID: <87pndeu98b.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20200228221236.1982482-1-fontaine.fabrice@gmail.com> (Fabrice Fontaine's message of "Fri, 28 Feb 2020 23:12:34 +0100")
>>>>> "Fabrice" == Fabrice Fontaine <fontaine.fabrice@gmail.com> writes:
> - Fix CVE-2020-9308: archive_read_support_format_rar5.c in libarchive
> before 3.4.2 attempts to unpack a RAR5 file with an invalid or
> corrupted header (such as a header size of zero), leading to a SIGSEGV
> or possibly unspecified other impact.
> - Add new mbedtls optional dependency and use --with-nettle to enable
> nettle support, see
> https://github.com/libarchive/libarchive/commit/f96a71144b7725ca4a94d84bd27d7dca8c2f58d2
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
> Changes v1 -> v2:
> - Add --without-mbedtls to host variant
Committed to 2019.11.x, thanks.
According to https://security-tracker.debian.org/tracker/CVE-2020-9308,
the rar5 support was only added in 3.4.0, so the 3.3.3 version we have
in 2019.02.x is not affected.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2020-03-14 17:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-28 22:12 [Buildroot] [PATCH v2, 1/3] package/libarchive: security bump to version 3.4.2 Fabrice Fontaine
2020-02-28 22:12 ` [Buildroot] [PATCH v2, 2/3] package/libarchive: add lz4 optional dependency Fabrice Fontaine
2020-04-25 19:56 ` Thomas Petazzoni
2020-05-08 10:06 ` Peter Korsgaard
2020-02-28 22:12 ` [Buildroot] [PATCH v2, 3/3] package/libarchive: add zstd " Fabrice Fontaine
2020-04-25 19:56 ` Thomas Petazzoni
2020-05-08 10:07 ` Peter Korsgaard
2020-02-29 16:47 ` [Buildroot] [PATCH v2, 1/3] package/libarchive: security bump to version 3.4.2 Yann E. MORIN
2020-03-14 17:39 ` Peter Korsgaard [this message]
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=87pndeu98b.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/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