Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] samba4: security bump to version 4.4.2
Date: Tue, 12 Apr 2016 23:12:56 +0200	[thread overview]
Message-ID: <878u0imsyv.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1460493290-20164-1-git-send-email-gustavo@zacarias.com.ar> (Gustavo Zacarias's message of "Tue, 12 Apr 2016 17:34:50 -0300")

>>>>> "Gustavo" == Gustavo Zacarias <gustavo@zacarias.com.ar> writes:

 > Fixes:
 > CVE-2016-2118 - A man in the middle can intercept any DCERPC traffic
 > between a client and a server in order toimpersonate the client and get
 > the same privileges as the authenticated user account.

 > CVE-2016-2115 - The protection of DCERPC communication over ncacn_np
 > (which is the default for most the file server related protocols) is
 > inherited from the underlying SMB connection. Samba doesn't enforce SMB
 > signing for this kind of SMB connections by default, which makes man in
 > the middle attacks possible.

 > CVE-2016-2114 - Due to a bug Samba doesn't enforce required smb signing,
 > even if explicitly configured.

 > CVE-2016-2113 - Man in the middle attacks are possible for client
 > triggered LDAP connections (with ldaps://) and ncacn_http connections
 > (with https://).

 > CVE-2016-2112 - A man in the middle is able to downgrade LDAP
 > connections to no integrity protection. It's possible to attack client
 > and server with this.

 > CVE-2016-2111 - When Samba is configured as Domain Controller it allows
 > remote attackers to spoof the computer name of a secure channel's
 > endpoints, and obtain sensitive session information, by running a
 > crafted application and leveraging the ability to sniff network traffic.

 > CVE-2016-2110 - The feature negotiation of NTLMSSP is not downgrade
 > protected. A man in the middle is able to clear even required flags,
 > especially NTLMSSP_NEGOTIATE_SIGN and NTLMSSP_NEGOTIATE_SEAL.

 > CVE-2015-5370 - Errors in Samba DCE-RPC code can lead to denial of
 > service (crashes and high cpu consumption) and man in the middle
 > attacks.

 > Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>

Committed, thanks.

-- 
Bye, Peter Korsgaard

      reply	other threads:[~2016-04-12 21:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-12 20:34 [Buildroot] [PATCH] samba4: security bump to version 4.4.2 Gustavo Zacarias
2016-04-12 21:12 ` 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=878u0imsyv.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