You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

73 lines
2.2 KiB

<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd">
<glsa id="200903-39">
<title>pam_krb5: Privilege escalation</title>
<synopsis>
Two vulnerabilities in pam_krb5 might allow local users to elevate their
privileges or overwrite arbitrary files.
</synopsis>
<product type="ebuild">pam_krb5</product>
<announced>March 25, 2009</announced>
<revised>March 25, 2009: 01</revised>
<bug>257075</bug>
<access>local</access>
<affected>
<package name="sys-auth/pam_krb5" auto="yes" arch="*">
<unaffected range="ge">3.12</unaffected>
<vulnerable range="lt">3.12</vulnerable>
</package>
</affected>
<background>
<p>
pam_krb5 is a a Kerberos v5 PAM module.
</p>
</background>
<description>
<p>
The following vulnerabilities were discovered:
</p>
<ul><li>pam_krb5
does not properly initialize the Kerberos libraries for setuid use
(CVE-2009-0360).</li>
<li>Derek Chan reported that calls to
pam_setcred() are not properly handled when running setuid
(CVE-2009-0361).</li>
</ul>
</description>
<impact type="high">
<p>
A local attacker could set an environment variable to point to a
specially crafted Kerberos configuration file and launch a PAM-based
setuid application to elevate privileges, or change ownership and
overwrite arbitrary files.
</p>
</impact>
<workaround>
<p>
There is no known workaround at this time.
</p>
</workaround>
<resolution>
<p>
All pam_krb5 users should upgrade to the latest version:
</p>
<code>
# emerge --sync
# emerge --ask --oneshot --verbose &quot;&gt;=sys-auth/pam_krb5-3.12&quot;</code>
</resolution>
<references>
<uri link="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0360">CVE-2009-0360</uri>
<uri link="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0361">CVE-2009-0361</uri>
</references>
<metadata tag="requester" timestamp="Thu, 05 Mar 2009 20:23:59 +0000">
keytoaster
</metadata>
<metadata tag="submitter" timestamp="Mon, 09 Mar 2009 12:57:24 +0000">
p-y
</metadata>
<metadata tag="bugReady" timestamp="Mon, 09 Mar 2009 12:57:36 +0000">
p-y
</metadata>
</glsa>