All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] package/zziplib: fix CVE-2018-16548
Date: Tue, 3 Mar 2020 22:54:40 +0100	[thread overview]
Message-ID: <20200303225440.05c016f3@windsurf.home> (raw)
In-Reply-To: <20200303201622.283957-1-fontaine.fabrice@gmail.com>

On Tue,  3 Mar 2020 21:16:21 +0100
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:

> An issue was discovered in ZZIPlib through 0.13.69. There is a memory
> leak triggered in the function __zzip_parse_root_directory in zip.c,
> which will lead to a denial of service attack.
> 
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
>  ...eak-from-__zzip_parse_root_directory.patch | 74 +++++++++++++++++++
>  ...k-from-__zzip_parse_root_directory-2.patch | 53 +++++++++++++
>  ...3-One-more-free-to-avoid-memory-leak.patch | 25 +++++++
>  package/zziplib/zziplib.mk                    |  5 ++
>  4 files changed, 157 insertions(+)
>  create mode 100644 package/zziplib/0001-Avoid-memory-leak-from-__zzip_parse_root_directory.patch
>  create mode 100644 package/zziplib/0002-Avoid-memory-leak-from-__zzip_parse_root_directory-2.patch
>  create mode 100644 package/zziplib/0003-One-more-free-to-avoid-memory-leak.patch

Both applied to master. Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  parent reply	other threads:[~2020-03-03 21:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-03 20:16 [Buildroot] [PATCH 1/2] package/zziplib: fix CVE-2018-16548 Fabrice Fontaine
2020-03-03 20:16 ` [Buildroot] [PATCH 2/2] package/zziplib: fix CVE-2018-17828 Fabrice Fontaine
2020-03-15 10:15   ` Peter Korsgaard
2020-03-03 21:54 ` Thomas Petazzoni [this message]
2020-03-15 10:15 ` [Buildroot] [PATCH 1/2] package/zziplib: fix CVE-2018-16548 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=20200303225440.05c016f3@windsurf.home \
    --to=thomas.petazzoni@bootlin.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 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.