public inbox for gentoo-announce@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mikle Kolyada <zlogene@gentoo.org>
To: gentoo-announce@gentoo.org
Subject: [gentoo-announce] [ GLSA 201403-06 ] libupnp: Arbitrary code execution
Date: Wed, 26 Mar 2014 14:36:45 +0400	[thread overview]
Message-ID: <5332ADBD.1010704@gentoo.org> (raw)

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

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory                           GLSA 201403-06
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                            http://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

 Severity: High
    Title: libupnp: Arbitrary code execution
     Date: March 26, 2014
     Bugs: #454570
       ID: 201403-06

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

Synopsis
========

Multiple buffer overflow flaws in libupnp may allow execution of
arbitrary code.

Background
==========

libupnp is a portable, open source, UPnP development kit.

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

    -------------------------------------------------------------------
     Package              /     Vulnerable     /            Unaffected
    -------------------------------------------------------------------
  1  net-libs/libupnp             < 1.6.18                  >= 1.6.18 

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

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

Impact
======

A remote attacker could possibly execute arbitrary code with the
privileges of the process or cause a Denial of Service condition.

Workaround
==========

There is no known workaround at this time.

Resolution
==========

All libupnp users should upgrade to the latest version:

  # emerge --sync
  # emerge --ask --oneshot --verbose ">=net-libs/libupnp-1.6.18"

References
==========

[ 1 ] CVE-2012-5958
      http://nvd.nist.gov/nvd.cfm?cvename=CVE-2012-5958
[ 2 ] CVE-2012-5959
      http://nvd.nist.gov/nvd.cfm?cvename=CVE-2012-5959
[ 3 ] CVE-2012-5960
      http://nvd.nist.gov/nvd.cfm?cvename=CVE-2012-5960

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

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

 http://security.gentoo.org/glsa/glsa-201403-06.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 2014 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

-- 
Mikle Kolyada
Gentoo Linux Developer



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

                 reply	other threads:[~2014-03-26 10:47 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=5332ADBD.1010704@gentoo.org \
    --to=zlogene@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