public inbox for gentoo-announce@lists.gentoo.org
 help / color / mirror / Atom feed
From: Thomas Deutschmann <whissi@gentoo.org>
To: gentoo-announce@lists.gentoo.org
Subject: [gentoo-announce] [ GLSA 202003-52 ] Samba: Multiple vulnerabilities
Date: Wed, 25 Mar 2020 17:34:50 +0100	[thread overview]
Message-ID: <cac2ee3a-323d-5248-8203-979df9f36443@gentoo.org> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 4379 bytes --]

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory                           GLSA 202003-52
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                           https://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

 Severity: Normal
    Title: Samba: Multiple vulnerabilities
     Date: March 25, 2020
     Bugs: #664316, #672140, #686036, #693558, #702928, #706144
       ID: 202003-52

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Synopsis
========

Multiple vulnerabilities have been found in Samba, the worst of which
could lead to remote code execution.

Background
==========

Samba is a suite of SMB and CIFS client/server programs.

Affected packages
=================

    -------------------------------------------------------------------
     Package              /     Vulnerable     /            Unaffected
    -------------------------------------------------------------------
  1  net-fs/samba                 < 4.11.6                 *>= 4.9.18
                                                          *>= 4.10.13
                                                           *>= 4.11.6

Description
===========

Multiple vulnerabilities have been discovered in Samba. Please review
the CVE identifiers referenced below for details.

Impact
======

A remote attacker could possibly execute arbitrary code, cause a Denial
of Service condition, conduct a man-in-the-middle attack, or obtain
sensitive information.

Workaround
==========

There is no known workaround at this time.

Resolution
==========

All Samba 4.9.x users should upgrade to the latest version:

  # emerge --sync
  # emerge --ask --oneshot --verbose ">=net-fs/samba-4.9.18"

All Samba 4.10.x users should upgrade to the latest version:

  # emerge --sync
  # emerge --ask --oneshot --verbose ">=net-fs/samba-4.10.13"

All Samba 4.11.x users should upgrade to the latest version:

  # emerge --sync
  # emerge --ask --oneshot --verbose ">=net-fs/samba-4.11.6"

References
==========

[  1 ] CVE-2018-10858
       https://nvd.nist.gov/vuln/detail/CVE-2018-10858
[  2 ] CVE-2018-10918
       https://nvd.nist.gov/vuln/detail/CVE-2018-10918
[  3 ] CVE-2018-10919
       https://nvd.nist.gov/vuln/detail/CVE-2018-10919
[  4 ] CVE-2018-1139
       https://nvd.nist.gov/vuln/detail/CVE-2018-1139
[  5 ] CVE-2018-1140
       https://nvd.nist.gov/vuln/detail/CVE-2018-1140
[  6 ] CVE-2018-14629
       https://nvd.nist.gov/vuln/detail/CVE-2018-14629
[  7 ] CVE-2018-16841
       https://nvd.nist.gov/vuln/detail/CVE-2018-16841
[  8 ] CVE-2018-16851
       https://nvd.nist.gov/vuln/detail/CVE-2018-16851
[  9 ] CVE-2018-16852
       https://nvd.nist.gov/vuln/detail/CVE-2018-16852
[ 10 ] CVE-2018-16853
       https://nvd.nist.gov/vuln/detail/CVE-2018-16853
[ 11 ] CVE-2018-16857
       https://nvd.nist.gov/vuln/detail/CVE-2018-16857
[ 12 ] CVE-2018-16860
       https://nvd.nist.gov/vuln/detail/CVE-2018-16860
[ 13 ] CVE-2019-10197
       https://nvd.nist.gov/vuln/detail/CVE-2019-10197
[ 14 ] CVE-2019-14861
       https://nvd.nist.gov/vuln/detail/CVE-2019-14861
[ 15 ] CVE-2019-14870
       https://nvd.nist.gov/vuln/detail/CVE-2019-14870
[ 16 ] CVE-2019-14902
       https://nvd.nist.gov/vuln/detail/CVE-2019-14902
[ 17 ] CVE-2019-14907
       https://nvd.nist.gov/vuln/detail/CVE-2019-14907
[ 18 ] CVE-2019-19344
       https://nvd.nist.gov/vuln/detail/CVE-2019-19344

Availability
============

This GLSA and any updates to it are available for viewing at
the Gentoo Security Website:

 https://security.gentoo.org/glsa/202003-52

Concerns?
=========

Security is a primary focus of Gentoo Linux and ensuring the
confidentiality and security of our users' machines is of utmost
importance to us. Any security concerns should be addressed to
security@gentoo.org or alternatively, you may file a bug at
https://bugs.gentoo.org.

License
=======

Copyright 2020 Gentoo Foundation, Inc; referenced text
belongs to its owner(s).

The contents of this document are licensed under the
Creative Commons - Attribution / Share Alike license.

https://creativecommons.org/licenses/by-sa/2.5



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 618 bytes --]

                 reply	other threads:[~2020-03-25 16:36 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=cac2ee3a-323d-5248-8203-979df9f36443@gentoo.org \
    --to=whissi@gentoo.org \
    --cc=gentoo-announce@lists.gentoo.org \
    --cc=security@gentoo.org \
    /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