From: Aaron Bauman <bman@gentoo.org>
To: gentoo-announce@lists.gentoo.org
Subject: [gentoo-announce] [ GLSA 201801-08 ] MiniUPnPc: Arbitrary code execution
Date: Sun, 07 Jan 2018 18:51:37 -0500 [thread overview]
Message-ID: <3703746.ED79X6X1tF@localhost.localdomain> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2296 bytes --]
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory GLSA 201801-08
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
https://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Severity: Normal
Title: MiniUPnPc: Arbitrary code execution
Date: January 07, 2018
Bugs: #562684
ID: 201801-08
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Synopsis
========
A vulnerability in MiniUPnPc might allow remote attackers to execute
arbitrary code.
Background
==========
The client library, enabling applications to access the services
provided by an UPnP "Internet Gateway Device" present on the network.
Affected packages
=================
-------------------------------------------------------------------
Package / Vulnerable / Unaffected
-------------------------------------------------------------------
1 net-libs/miniupnpc < 2.0.20170509 >= 2.0.20170509
Description
===========
An exploitable buffer overflow vulnerability exists in the XML parser
functionality of the MiniUPnP library.
Impact
======
A remote attacker, by enticing a user to connect to a malicious server,
could cause the execution of arbitrary code with the privileges of the
user running a MiniUPnPc linked application.
Workaround
==========
There is no known workaround at this time.
Resolution
==========
All MiniUPnPc users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot -v ">=net-libs/miniupnpc-2.0.20170509"
References
==========
[ 1 ] CVE-2015-6031
https://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-6031
Availability
============
This GLSA and any updates to it are available for viewing at
the Gentoo Security Website:
https://security.gentoo.org/glsa/201801-08
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
[-- Attachment #1.2: Type: text/html, Size: 20104 bytes --]
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
reply other threads:[~2018-01-07 23:58 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=3703746.ED79X6X1tF@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