From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] samba4: security bump to version 4.6.11
Date: Wed, 22 Nov 2017 21:30:44 +0100 [thread overview]
Message-ID: <20171122213044.6590d8f4@windsurf.lan> (raw)
In-Reply-To: <20171121224313.26215-1-peter@korsgaard.com>
Hello,
On Tue, 21 Nov 2017 23:43:13 +0100, Peter Korsgaard wrote:
> Fixes the following security issues:
>
> - CVE-2017-14746:
> All versions of Samba from 4.0.0 onwards are vulnerable to a use after
> free vulnerability, where a malicious SMB1 request can be used to
> control the contents of heap memory via a deallocated heap pointer. It
> is possible this may be used to compromise the SMB server.
>
> - CVE-2017-15275:
> All versions of Samba from 3.6.0 onwards are vulnerable to a heap
> memory information leak, where server allocated heap memory may be
> returned to the client without being cleared.
>
> There is no known vulnerability associated with this error, but
> uncleared heap memory may contain previously used data that may help
> an attacker compromise the server via other methods. Uncleared heap
> memory may potentially contain password hashes or other high-value
> data.
>
> For more details, see the release notes:
> https://www.samba.org/samba/history/samba-4.6.11.html
>
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
> ---
> package/samba4/samba4.hash | 2 +-
> package/samba4/samba4.mk | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-11-22 20:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-21 22:43 [Buildroot] [PATCH] samba4: security bump to version 4.6.11 Peter Korsgaard
2017-11-22 20:30 ` Thomas Petazzoni [this message]
2017-11-27 9:46 ` 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=20171122213044.6590d8f4@windsurf.lan \
--to=thomas.petazzoni@free-electrons.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