From: Aaron Bauman <bman@gentoo.org>
To: gentoo-announce@lists.gentoo.org
Subject: [gentoo-announce] [ GLSA 201701-21 ] Expat: Multiple vulnerabilities
Date: Wed, 11 Jan 2017 21:13:25 +0900 [thread overview]
Message-ID: <ebe247b4-cba7-256c-1517-86f6c56b816f@gentoo.org> (raw)
[-- Attachment #1.1.1: Type: text/plain, Size: 3082 bytes --]
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory GLSA 201701-21
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
https://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Severity: Normal
Title: Expat: Multiple vulnerabilities
Date: January 11, 2017
Bugs: #458742, #555642, #577928, #583268, #585510
ID: 201701-21
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Synopsis
========
Multiple vulnerabilities have been found in Expat, the worst of which
may allow execution of arbitrary code.
Background
==========
Expat is a set of XML parsing libraries.
Affected packages
=================
-------------------------------------------------------------------
Package / Vulnerable / Unaffected
-------------------------------------------------------------------
1 dev-libs/expat < 2.2.0-r1 >= 2.2.0-r1
Description
===========
Multiple vulnerabilities have been discovered in Expat. Please review
the CVE identifiers referenced below for details.
Impact
======
A remote attacker, by enticing a user to process a specially crafted
XML file, could execute arbitrary code with the privileges of the
process or cause a Denial of Service condition. This attack could also
be used against automated systems that arbitrarily process XML files.
Workaround
==========
There is no known workaround at this time.
Resolution
==========
All Expat users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot --verbose ">=dev-libs/expat-2.2.0-r1"
References
==========
[ 1 ] CVE-2012-6702
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2012-6702
[ 2 ] CVE-2013-0340
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2013-0340
[ 3 ] CVE-2015-1283
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-1283
[ 4 ] CVE-2016-0718
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-0718
[ 5 ] CVE-2016-4472
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-4472
[ 6 ] CVE-2016-5300
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-5300
Availability
============
This GLSA and any updates to it are available for viewing at
the Gentoo Security Website:
https://security.gentoo.org/glsa/201701-21
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 #1.1.2: Type: text/html, Size: 4653 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 949 bytes --]
reply other threads:[~2017-01-11 12:54 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=ebe247b4-cba7-256c-1517-86f6c56b816f@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