From: Aaron Bauman <bman@gentoo.org>
To: gentoo-announce@lists.gentoo.org
Subject: [gentoo-announce] [ GLSA 201612-37 ] Pixman: Buffer overflow
Date: Tue, 13 Dec 2016 15:51:05 +0900 [thread overview]
Message-ID: <049e6f65-9f2a-f588-4aa3-91b185ae7851@gentoo.org> (raw)
[-- Attachment #1.1.1: Type: text/plain, Size: 2518 bytes --]
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory GLSA 201612-37
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
https://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Severity: Normal
Title: Pixman: Buffer overflow
Date: December 13, 2016
Bugs: #561526
ID: 201612-37
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Synopsis
========
A buffer overflow in Pixman might allow remote attackers to execute
arbitrary code.
Background
==========
Pixman is a pixel manipulation library.
Affected packages
=================
-------------------------------------------------------------------
Package / Vulnerable / Unaffected
-------------------------------------------------------------------
1 x11-libs/pixman < 0.32.8 >= 0.32.8
Description
===========
In pixman-general, careless computations done with the 'dest_buffer'
pointer may overflow, failing the buffer upper limit check.
Impact
======
A remote attacker could possibly cause a Denial of Service condition,
or execute arbitrary code with the privileges of the process.
Workaround
==========
There is no known workaround at this time.
Resolution
==========
All Pixman users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot --verbose ">=x11-libs/pixman-0.32.8"
References
==========
[ 1 ] Pixman 0.32.8 Release Notes
http://lists.x.org/archives/xorg-announce/2015-September/002637.html
Availability
============
This GLSA and any updates to it are available for viewing at
the Gentoo Security Website:
https://security.gentoo.org/glsa/201612-37
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 2016 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: 3638 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 949 bytes --]
reply other threads:[~2016-12-13 7:32 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=049e6f65-9f2a-f588-4aa3-91b185ae7851@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