From: Alex Legler <a3li@gentoo.org>
To: gentoo-announce@lists.gentoo.org
Cc: bugtraq@securityfocus.com, full-disclosure@lists.grok.org.uk,
security-alerts@linuxsecurity.com
Subject: [gentoo-announce] [ GLSA 201009-03 ] sudo: Privilege Escalation
Date: Tue, 7 Sep 2010 14:08:02 +0200 [thread overview]
Message-ID: <20100907140802.1ea2e177@mail.a3li.li> (raw)
[-- Attachment #1: Type: text/plain, Size: 2995 bytes --]
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory GLSA 201009-03
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
http://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Severity: High
Title: sudo: Privilege Escalation
Date: September 07, 2010
Bugs: #322517, #335381
ID: 201009-03
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Synopsis
========
The secure path feature and group handling in sudo allow local
attackers to escalate privileges.
Background
==========
sudo allows a system administrator to give users the ability to run
commands as other users.
Affected packages
=================
-------------------------------------------------------------------
Package / Vulnerable / Unaffected
-------------------------------------------------------------------
1 app-admin/sudo < 1.7.4_p3-r1 >= 1.7.4_p3-r1
Description
===========
Multiple vulnerabilities have been reported in sudo:
* Evan Broder and Anders Kaseorg of Ksplice, Inc. reported that the
sudo 'secure path' feature does not properly handle multiple PATH
variables (CVE-2010-1646).
* Markus Wuethrich of Swiss Post reported that sudo fails to restrict
access when using Runas groups and the group (-g) command line option
(CVE-2010-2956).
Impact
======
A local attacker could exploit these vulnerabilities to gain the
ability to run certain commands with the privileges of other users,
including root, depending on the configuration.
Workaround
==========
There is no known workaround at this time.
Resolution
==========
All sudo users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot --verbose ">=app-admin/sudo-1.7.4_p3-r1"
References
==========
[ 1 ] CVE-2010-1646
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-1646
[ 2 ] CVE-2010-2956
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-2956
Availability
============
This GLSA and any updates to it are available for viewing at
the Gentoo Security Website:
http://security.gentoo.org/glsa/glsa-201009-03.xml
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 2010 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: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
reply other threads:[~2010-09-07 12:20 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=20100907140802.1ea2e177@mail.a3li.li \
--to=a3li@gentoo.org \
--cc=bugtraq@securityfocus.com \
--cc=full-disclosure@lists.grok.org.uk \
--cc=gentoo-announce@lists.gentoo.org \
--cc=security-alerts@linuxsecurity.com \
/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