gentoo-overlay/metadata/glsa/glsa-201206-31.xml

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd">
<glsa id="201206-31">
  <title>Linux-PAM: Multiple vulnerabilities</title>
  <synopsis>Multiple vulnerabilities have been found in Linux-PAM, allowing
    local attackers to possibly gain escalated privileges, cause a Denial of
    Service, corrupt data, or obtain sensitive information.
  </synopsis>
  <product type="ebuild">pam</product>
  <announced>2012-06-25</announced>
  <revised count="1">2012-06-25</revised>
  <bug>343399</bug>
  <bug>386273</bug>
  <bug>388431</bug>
  <access>local</access>
  <affected>
    <package name="sys-libs/pam" auto="yes" arch="*">
      <unaffected range="ge">1.1.5</unaffected>
      <vulnerable range="lt">1.1.5</vulnerable>
    </package>
  </affected>
  <background>
    <p>Linux-PAM (Pluggable Authentication Modules) is an architecture allowing
      the separation of the development of privilege granting software from the
      development of secure and appropriate authentication schemes.
    </p>
  </background>
  <description>
    <p>Multiple vulnerabilities have been discovered in Linux-PAM. Please
      review the CVE identifiers referenced below for details.
    </p>
  </description>
  <impact type="high">
    <p>A local attacker could use specially crafted files to cause a buffer
      overflow, possibly resulting in privilege escalation or Denial of
      Service. Furthermore, a local attacker could execute specially crafted
      programs or symlink attacks, possibly resulting in data loss or
      disclosure of sensitive information.
    </p>
  </impact>
  <workaround>
    <p>There is no known workaround at this time.</p>
  </workaround>
  <resolution>
    <p>All Linux-PAM users should upgrade to the latest version:</p>
    
    <code>
      # emerge --sync
      # emerge --ask --oneshot --verbose "&gt;=sys-libs/pam-1.1.5"
    </code>
    
    <p>NOTE: This is a legacy GLSA. Updates for all affected architectures are
      available since November 25, 2011. It is likely that your system is
      already no longer affected by this issue.
    </p>
  </resolution>
  <references>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2010-3316">CVE-2010-3316</uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2010-3430">CVE-2010-3430</uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2010-3431">CVE-2010-3431</uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2010-3435">CVE-2010-3435</uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2010-3853">CVE-2010-3853</uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2010-4706">CVE-2010-4706</uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2010-4707">CVE-2010-4707</uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2010-4708">CVE-2010-4708</uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2011-3148">CVE-2011-3148</uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2011-3149">CVE-2011-3149</uri>
  </references>
  <metadata timestamp="2011-10-07T23:37:20Z" tag="requester">
    underling
  </metadata>
  <metadata timestamp="2012-06-25T18:51:25Z" tag="submitter">craig</metadata>
</glsa>