public inbox for gentoo-announce@lists.gentoo.org
 help / color / mirror / Atom feed
From: Aaron Bauman <bman@gentoo.org>
To: gentoo-announce@lists.gentoo.org
Subject: [gentoo-announce] [ GLSA 201812-07 ] SpamAssassin: Multiple vulnerabilities
Date: Sat, 15 Dec 2018 15:10:50 -0500	[thread overview]
Message-ID: <20181215201050.GB10488@monkey> (raw)

[-- Attachment #1: Type: text/plain, Size: 2698 bytes --]

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory                           GLSA 201812-07
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                           https://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

 Severity: Normal
    Title: SpamAssassin: Multiple vulnerabilities
     Date: December 15, 2018
     Bugs: #666348
       ID: 201812-07

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

Synopsis
========

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

Background
==========

SpamAssassin is an extensible email filter used to identify junk email.

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

    -------------------------------------------------------------------
     Package              /     Vulnerable     /            Unaffected
    -------------------------------------------------------------------
  1  mail-filter/spamassassin
                                 < 3.4.2-r2               >= 3.4.2-r2

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

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

Impact
======

A remote attacker could execute arbitrary code, escalate privileges, or
cause a Denial of Service condition.

Workaround
==========

There is no known workaround at this time.

Resolution
==========

All SpamAssassin users should upgrade to the latest version:

  # emerge --sync
  # emerge --ask --oneshot -v ">=mail-filter/spamassassin-3.4.2-r2"

References
==========

[ 1 ] CVE-2016-1238
      https://nvd.nist.gov/vuln/detail/CVE-2016-1238
[ 2 ] CVE-2017-15705
      https://nvd.nist.gov/vuln/detail/CVE-2017-15705
[ 3 ] CVE-2018-11780
      https://nvd.nist.gov/vuln/detail/CVE-2018-11780
[ 4 ] CVE-2018-11781
      https://nvd.nist.gov/vuln/detail/CVE-2018-11781

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

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

 https://security.gentoo.org/glsa/201812-07

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 2018 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: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

                 reply	other threads:[~2018-12-15 20:16 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=20181215201050.GB10488@monkey \
    --to=bman@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