From: Thomas Deutschmann <whissi@gentoo.org>
To: gentoo-announce@lists.gentoo.org
Subject: [gentoo-announce] [ GLSA 201707-12 ] MAN DB: Privilege escalation
Date: Sun, 9 Jul 2017 22:23:39 +0200 [thread overview]
Message-ID: <9c789c81-9461-f8c4-cbc0-c798e6bf5cbd@gentoo.org> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2494 bytes --]
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory GLSA 201707-12
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
https://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Severity: High
Title: MAN DB: Privilege escalation
Date: July 09, 2017
Bugs: #602588
ID: 201707-12
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Synopsis
========
A vulnerability in MAN DB allows local users to gain root privileges.
Background
==========
MAN DB is a man replacement that utilizes BerkelyDB instead of flat
files.
Affected packages
=================
-------------------------------------------------------------------
Package / Vulnerable / Unaffected
-------------------------------------------------------------------
1 sys-apps/man-db < 2.7.6.1-r2 >= 2.7.6.1-r2
Description
===========
The /var/cache/man directory as part of the MAN DB package has group
permissions set to root.
Impact
======
A local user who does not belong to the root group, but has the ability
to modify the /var/cache/man directory can escalate privileges to the
group root.
Workaround
==========
There is no known workaround at this time.
Resolution
==========
All MAN DB users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot --verbose ">=sys-apps/man-db-2.7.6.1-r2"
References
==========
[ 1 ] CVE-2015-1336
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-1336
Availability
============
This GLSA and any updates to it are available for viewing at
the Gentoo Security Website:
https://security.gentoo.org/glsa/201707-12
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 #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 951 bytes --]
reply other threads:[~2017-07-09 20:26 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=9c789c81-9461-f8c4-cbc0-c798e6bf5cbd@gentoo.org \
--to=whissi@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