public inbox for gentoo-announce@lists.gentoo.org
 help / color / mirror / Atom feed
From: Kristian Fiskerstrand <k_f@gentoo.org>
To: gentoo-announce@gentoo.org
Subject: [gentoo-announce] [ GLSA 201502-11 ] GNU cpio: Multiple vulnerabilities
Date: Sun, 15 Feb 2015 15:37:56 +0100	[thread overview]
Message-ID: <54E0AF44.5000403@gentoo.org> (raw)

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

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory                           GLSA 201502-11
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                            http://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

 Severity: Normal
    Title: GNU cpio: Multiple vulnerabilities
     Date: February 15, 2015
     Bugs: #530512, #536010
       ID: 201502-11

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

Synopsis
========

Two vulnerabilities have been found in GNU cpio, the worst of which
could result in execution of arbitrary code.

Background
==========

GNU cpio copies files into or out of a cpio or tar archive.

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

    -------------------------------------------------------------------
     Package              /     Vulnerable     /            Unaffected
    -------------------------------------------------------------------
  1  app-arch/cpio               < 2.11-r3                 >= 2.11-r3

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

Two vulnerabilities have been discovered in GNU cpio:

* The list_file function in GNU cpio contains a heap-based buffer
  overflow vulnerability (CVE-2014-9112)
* A directory traversal vulnerability has been found in GNU cpio
  (CVE-2015-1197)

Impact
======

A remote attacker may be able to entice a user to open a specially
crafted archive using GNU cpio, possibly resulting in execution of
arbitrary code, a Denial of Service condition, or overwriting arbitrary
files.

Workaround
==========

There is no known workaround at this time.

Resolution
==========

All GNU cpio users should upgrade to the latest version:

  # emerge --sync
  # emerge --ask --oneshot --verbose ">=app-arch/cpio-2.11-r3"

References
==========

[ 1 ] CVE-2014-9112
      http://nvd.nist.gov/nvd.cfm?cvename=CVE-2014-9112
[ 2 ] CVE-2015-1197
      http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-1197

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

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

 http://security.gentoo.org/glsa/glsa-201502-11.xml

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 2015 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: 455 bytes --]

                 reply	other threads:[~2015-02-15 14:53 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=54E0AF44.5000403@gentoo.org \
    --to=k_f@gentoo.org \
    --cc=gentoo-announce@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