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 201701-51 ] DBD::mysql: Multiple vulnerabilities
Date: Mon, 23 Jan 2017 12:20:51 +0900	[thread overview]
Message-ID: <f36ebc6f-a6fa-05f5-e2bf-99cf7ddb38a7@gentoo.org> (raw)


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

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory                           GLSA 201701-51
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                           https://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

 Severity: Normal
    Title: DBD::mysql: Multiple vulnerabilities
     Date: January 23, 2017
     Bugs: #589818, #596424, #600180, #601144
       ID: 201701-51

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

Synopsis
========

Multiple vulnerabilities have been found in DBD::mysql, the worst of
which might allow an attacker to execute arbitrary code.

Background
==========

MySQL driver for the Perl5 Database Interface (DBI)

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

    -------------------------------------------------------------------
     Package              /     Vulnerable     /            Unaffected
    -------------------------------------------------------------------
  1  dev-perl/DBD-mysql           < 4.41.0                  >= 4.41.0

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

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

Impact
======

An attacker could cause a Denial of Service condition, execute
arbitrary code, or have other unspecified impacts.

Workaround
==========

There is no known workaround at this time.

Resolution
==========

All DBD::mysql users should upgrade to the latest version:

  # emerge --sync
  # emerge --ask --oneshot --verbose ">=dev-perl/DBD-mysql-4.41.0"

References
==========

[ 1 ] CVE-2015-8949
      http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-8949
[ 2 ] CVE-2016-1246
      http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1246
[ 3 ] CVE-2016-1249
      http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1249
[ 4 ] CVE-2016-1251
      http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1251

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

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

 https://security.gentoo.org/glsa/201701-51

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 2017 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.

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


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

                 reply	other threads:[~2017-01-23  3:25 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=f36ebc6f-a6fa-05f5-e2bf-99cf7ddb38a7@gentoo.org \
    --to=bman@gentoo.org \
    --cc=gentoo-announce@lists.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