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 201709-27 ] LibTIFF: Multiple vulnerabilities
Date: Tue, 26 Sep 2017 18:11:17 -0400	[thread overview]
Message-ID: <3559947.cqVStVUssH@localhost.localdomain> (raw)

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

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory                           GLSA 201709-27
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                           https://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

 Severity: Normal
    Title: LibTIFF: Multiple vulnerabilities
     Date: September 26, 2017
     Bugs: #610330, #614020, #614022, #617996, #617998, #618610, #624602
       ID: 201709-27

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

Synopsis
========

Multiple vulnerabilities have been found in LibTIFF, the worst of which
could result in the execution of arbitrary code.

Background
==========

The TIFF library contains encoding and decoding routines for the Tag
Image File Format. It is called by numerous programs, including GNOME
and KDE applications, to interpret TIFF images.

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

    -------------------------------------------------------------------
     Package              /     Vulnerable     /            Unaffected
    -------------------------------------------------------------------
  1  media-libs/tiff              < 4.0.8                    >= 4.0.8 

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

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

Impact
======

A remote attacker, by enticing the user to process a specially crafted
TIFF file, could possibly execute arbitrary code with the privileges of
the process, cause a Denial of Service condition, obtain sensitive
information, or have other unspecified impacts.

Workaround
==========

There is no known workaround at this time.

Resolution
==========

All LibTIFF users should upgrade to the latest version:

  # emerge --sync
  # emerge --ask --oneshot --verbose ">=media-libs/tiff-4.0.8"

Packages which depend on this library may need to be recompiled. Tools
such as revdep-rebuild may assist in identifying some of these
packages.

References
==========

[  1 ] CVE-2016-10267
       https://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-10267
[  2 ] CVE-2016-10268
       https://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-10268
[  3 ] CVE-2017-5225
       https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-5225
[  4 ] CVE-2017-5563
       https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-5563
[  5 ] CVE-2017-7592
       https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-7592
[  6 ] CVE-2017-7593
       https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-7593
[  7 ] CVE-2017-7594
       https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-7594
[  8 ] CVE-2017-7595
       https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-7595
[  9 ] CVE-2017-7596
       https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-7596
[ 10 ] CVE-2017-7597
       https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-7597
[ 11 ] CVE-2017-7598
       https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-7598
[ 12 ] CVE-2017-7599
       https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-7599
[ 13 ] CVE-2017-7600
       https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-7600
[ 14 ] CVE-2017-7601
       https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-7601
[ 15 ] CVE-2017-7602
       https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-7602
[ 16 ] CVE-2017-9403
       http://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-9403

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

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

 https://security.gentoo.org/glsa/201709-27

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: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

                 reply	other threads:[~2017-09-26 22:12 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=3559947.cqVStVUssH@localhost.localdomain \
    --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