From: Aaron Bauman <bman@gentoo.org>
To: gentoo-announce@lists.gentoo.org
Subject: [gentoo-announce] [ GLSA 201711-08 ] LibXfont, LibXfont2: Multiple vulnerabilities
Date: Sat, 11 Nov 2017 10:03:18 -0500 [thread overview]
Message-ID: <3666340.roH9fDyaCM@localhost.localdomain> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2288 bytes --]
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory GLSA 201711-08
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
https://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Severity: Normal
Title: LibXfont, LibXfont2: Multiple vulnerabilities
Date: November 11, 2017
Bugs: #634044
ID: 201711-08
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Synopsis
========
Multiple vulnerabilities have been found in LibXfont and Libxfont2, the
worst of which could allow attackers to cause a Denial of Service
condition.
Background
==========
X.Org Xfont library
Affected packages
=================
-------------------------------------------------------------------
Package / Vulnerable / Unaffected
-------------------------------------------------------------------
1 x11-libs/libXfont2 < 2.0.2 >= 2.0.2
2 x11-libs/libXfont < 1.5.3 >= 1.5.3
-------------------------------------------------------------------
2 affected packages
Description
===========
Multiple vulnerabilities have been discovered in LibXfont and
LibXfont2. Please review the referenced CVE identifiers for details.
Impact
======
Local attackers could obtain sensitive information or possibly cause a
Denial of Service condition.
Workaround
==========
There is no known workaround at this time.
Resolution
==========
All LibXfont2 users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot --verbose ">=x11-libs/libXfont2-2.0.2"
All LibXfont users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot --verbose ">=x11-libs/libXfont-1.5.3"
References
==========
[ 1 ] CVE-2017-13720
https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-13720
[ 2 ] CVE-2017-13722
https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-13722
Availability
============
This GLSA and any updates to it are available for viewing at
the Gentoo Security Website:
https://security.gentoo.org/glsa/201711-08
Concerns?
[-- Attachment #1.2: Type: text/html, Size: 22095 bytes --]
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 484 bytes --]
reply other threads:[~2017-11-11 15:05 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=3666340.roH9fDyaCM@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