Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] package/network-manager: Add upstream patch to fix CVE-2018-15688
Date: Tue, 30 Oct 2018 22:50:51 +0100	[thread overview]
Message-ID: <878t2fcddw.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20181030212053.9833-2-bernd.kuhls@t-online.de> (Bernd Kuhls's message of "Tue, 30 Oct 2018 22:20:53 +0100")

>>>>> "Bernd" == Bernd Kuhls <bernd.kuhls@t-online.de> writes:

 > NetworkManager includes some parts of the systemd-networkd code in its
 > codebase. That can be found at src/systemd/src/libsystemd-networkd.
 > The DHCP implementation provided by systemd-networkd is used when
 > NetworkManager is configured to use the internal implementation,
 > however the default is to use dhclient.

 > When NetworkManager is configured to use the internal dhcp and an
 > interface is setup with ipv6.method=auto (which is the default value)
 > or ipv6.method=dhcp, this flaw can be exploited. When using
 > ipv6.method=auto, the DHCPv6 client can be automatically started with a
 > Router Advertisement packet.

 > Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>

Committed, thanks.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2018-10-30 21:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-30 21:20 [Buildroot] [PATCH 1/2] package/network-manager: bump version to 1.10.8 Bernd Kuhls
2018-10-30 21:20 ` [Buildroot] [PATCH 2/2] package/network-manager: Add upstream patch to fix CVE-2018-15688 Bernd Kuhls
2018-10-30 21:50   ` Peter Korsgaard [this message]
2018-11-14  9:35   ` Peter Korsgaard
2018-10-30 21:24 ` [Buildroot] [PATCH 1/2] package/network-manager: bump version to 1.10.8 Petr Vorel
2018-10-30 21:27   ` Petr Vorel
2018-10-30 21:50 ` 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=878t2fcddw.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