From: glsamaker@gentoo.org
To: gentoo-announce@lists.gentoo.org
Subject: [gentoo-announce] [ GLSA 202209-10 ] Logcheck: Root privilege escalation
Date: Sun, 25 Sep 2022 13:35:02 -0000 [thread overview]
Message-ID: <166411290230.9.8040128598883786569@90bb6a0775af> (raw)
[-- Attachment #1: Type: text/plain, Size: 2552 bytes --]
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory GLSA 202209-10
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
https://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Severity: Normal
Title: Logcheck: Root privilege escalation
Date: September 25, 2022
Bugs: #630752
ID: 202209-10
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Synopsis
========
A vulnerability has been discovered in Logcheck's ebuilds which could
allow for root privilege escalation.
Background
==========
Logcheck mails anomalies in the system logfiles to the administrator.
Affected packages
=================
-------------------------------------------------------------------
Package / Vulnerable / Unaffected
-------------------------------------------------------------------
1 app-admin/logcheck <= 1.3.23 Vulnerable!
Description
===========
The pkg_postinst phase of the Logcheck ebuilds recursively chown the
/etc/logcheck and /var/lib/logcheck directories. If the logcheck adds
hardlinks to other files in these directories, the chown call will
follow the link and transfer ownership of any file to the logcheck user.
Impact
======
A local attacker with access to the logcheck user could escalate to root
privileges.
Workaround
==========
There is no known workaround at this time.
Resolution
==========
Gentoo has discontinued support for Logcheck. We recommend that users
remove it:
# emerge --ask --depclean "app-admin/logcheck"
References
==========
[ 1 ] CVE-2017-20148
https://nvd.nist.gov/vuln/detail/CVE-2017-20148
Availability
============
This GLSA and any updates to it are available for viewing at
the Gentoo Security Website:
https://security.gentoo.org/glsa/202209-10
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 2022 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.
https://creativecommons.org/licenses/by-sa/2.5
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
reply other threads:[~2022-09-25 13:50 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=166411290230.9.8040128598883786569@90bb6a0775af \
--to=glsamaker@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