From: Aaron Bauman <bman@gentoo.org>
To: gentoo-announce@lists.gentoo.org
Subject: [gentoo-announce] [ GLSA 201612-25 ] CrackLib: Buffer overflow
Date: Thu, 8 Dec 2016 22:55:33 +0900 [thread overview]
Message-ID: <9f024c3d-043a-474c-d977-0a57101a8ee1@gentoo.org> (raw)
[-- Attachment #1.1.1: Type: text/plain, Size: 2642 bytes --]
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory GLSA 201612-25
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
https://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Severity: Normal
Title: CrackLib: Buffer overflow
Date: December 08, 2016
Bugs: #591456
ID: 201612-25
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Synopsis
========
A vulnerability in CrackLib could lead to the execution of arbitrary
code.
Background
==========
CrackLib is a library used to enforce strong passwords by comparing
user selected passwords to words in chosen word lists.
Affected packages
=================
-------------------------------------------------------------------
Package / Vulnerable / Unaffected
-------------------------------------------------------------------
1 sys-libs/cracklib < 2.9.6-r1 >= 2.9.6-r1
Description
===========
A stack-based buffer overflow was discovered in the FascistGecosUser
function of lib/fascist.c.
Impact
======
A local attacker could set a specially crafted GECOS field value in
"/etc/passwd"; possibly resulting in the execution of arbitrary code
with the privileges of the process, a Denial of Service condition, or
the escalation of privileges.
Workaround
==========
There is no known workaround at this time.
Resolution
==========
All CrackLib users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot --verbose ">=sys-libs/cracklib-2.9.6-r1"
References
==========
[ 1 ] CVE-2016-6318
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-6318
Availability
============
This GLSA and any updates to it are available for viewing at
the Gentoo Security Website:
https://security.gentoo.org/glsa/201612-25
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: 3743 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 949 bytes --]
reply other threads:[~2016-12-08 13: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=9f024c3d-043a-474c-d977-0a57101a8ee1@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