From: Aaron Bauman <bman@gentoo.org>
To: gentoo-announce@lists.gentoo.org
Subject: [gentoo-announce] [ GLSA 201612-08 ] LinuxCIFS utils: Buffer overflow
Date: Sun, 4 Dec 2016 20:02:55 +0900 [thread overview]
Message-ID: <3a6536f5-3cbb-f86c-20b0-1a51ab1d3c0e@gentoo.org> (raw)
[-- Attachment #1.1.1: Type: text/plain, Size: 2656 bytes --]
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory GLSA 201612-08
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
https://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Severity: Normal
Title: LinuxCIFS utils: Buffer overflow
Date: December 04, 2016
Bugs: #552634
ID: 201612-08
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Synopsis
========
A vulnerability in LinuxCIFS utils' "cifscreds" PAM module might allow
remote attackers to have an unspecified impact via unknown vectors.
Background
==========
The LinuxCIFS utils are a collection of tools for managing Linux CIFS
Client Filesystems.
Affected packages
=================
-------------------------------------------------------------------
Package / Vulnerable / Unaffected
-------------------------------------------------------------------
1 net-fs/cifs-utils < 6.4 >= 6.4
Description
===========
A stack-based buffer overflow was discovered in cifskey.c or
cifscreds.c in LinuxCIFS, as used in "pam_cifscreds."
Impact
======
A remote attacker could exploit this vulnerability to cause an
unspecified impact.
Workaround
==========
Don't use LinuxCIFS utils' "cifscreds" PAM module. In Gentoo, LinuxCIFS
utils' PAM support is disabled by default unless the "pam" USE flag is
enabled.
Resolution
==========
All LinuxCIFS utils users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot --verbose ">=net-fs/cifs-utils-6.4"
References
==========
[ 1 ] CVE-2014-2830
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2014-2830
Availability
============
This GLSA and any updates to it are available for viewing at
the Gentoo Security Website:
https://security.gentoo.org/glsa/201612-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
=======
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: 3757 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 949 bytes --]
reply other threads:[~2016-12-04 11:13 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=3a6536f5-3cbb-f86c-20b0-1a51ab1d3c0e@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