All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1 1/2] package/busybox: udhcp CVE-2018-20679 patch
Date: Thu, 7 Mar 2019 22:10:29 +0100	[thread overview]
Message-ID: <20190307221029.79cb8f09@windsurf> (raw)
In-Reply-To: <20190306142231.23490-1-jared.bents@rockwellcollins.com>

On Wed,  6 Mar 2019 08:22:30 -0600
jared.bents at rockwellcollins.com wrote:

> From: Jared Bents <jared.bents@rockwellcollins.com>
> 
> Patch to resolve CVE-2018-20679 which affects versions prior
> to 1.30.0
> 
> More information can be found at:
> https://nvd.nist.gov/vuln/detail/CVE-2018-20679
> 
> This applies to both master and 2019.02
> 
> Signed-off-by: Jared Bents <jared.bents@rockwellcollins.com>
> ---
>  ...tions-are-indeed-4-byte-closes-11506.patch | 136 ++++++++++++++++++
>  1 file changed, 136 insertions(+)
>  create mode 100644 package/busybox/0004-udhcpc-check-that-4-byte-options-are-indeed-4-byte-closes-11506.patch

I've applied both to master, because it makes them to have them to
backport to 2019.02. However, for master, a followup patch doing an
update to 1.30.1 would be good.

Thanks!

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

  parent reply	other threads:[~2019-03-07 21:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-06 14:22 [Buildroot] [PATCH v1 1/2] package/busybox: udhcp CVE-2018-20679 patch jared.bents at rockwellcollins.com
2019-03-06 14:22 ` [Buildroot] [PATCH v1 2/2] package/busybox: udhcp CVE-2019-5747 patch jared.bents at rockwellcollins.com
2019-03-19 20:22   ` Peter Korsgaard
2019-03-07 21:10 ` Thomas Petazzoni [this message]
2019-03-19 20:22 ` [Buildroot] [PATCH v1 1/2] package/busybox: udhcp CVE-2018-20679 patch 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=20190307221029.79cb8f09@windsurf \
    --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.