[gentoo-commits] gentoo commit in xml/htdocs/security/en/glsa: glsa-201409-09.xml

[Alex Legler (a3li)]

a3li        14/09/24 22:18:13

  Added:                glsa-201409-09.xml
  Log:
  GLSA 201409-09

Revision  Changes    Path
1.1                  xml/htdocs/security/en/glsa/glsa-201409-09.xml

file : 
http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/security/en/glsa/glsa-201409-09.xml?rev=1.1&view=markup
plain: 
http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/security/en/glsa/glsa-201409-09.xml?rev=1.1&content-type=text/plain

Index: glsa-201409-09.xml
===================================================================
<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="/xsl/glsa.xsl" type="text/xsl"?>
<?xml-stylesheet href="/xsl/guide.xsl" type="text/xsl"?>
<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd";>
<glsa id="201409-09">
  <title>Bash: Code Injection</title>
  <synopsis>A parsing flaw related to functions and environments in Bash could
    allow attackers to inject code.
  </synopsis>
  <product type="ebuild">bash</product>
  <announced>September 24, 2014</announced>
  <revised>September 24, 2014: 3</revised>
  <bug>523592</bug>
  <access>local, remote</access>
  <affected>
    <package name="app-shells/bash" auto="yes" arch="*">
      <unaffected range="rge">3.1_p18</unaffected>
      <unaffected range="rge">3.2_p52</unaffected>
      <unaffected range="rge">4.0_p39</unaffected>
      <unaffected range="rge">4.1_p12</unaffected>
      <unaffected range="ge">4.2_p48</unaffected>
      <vulnerable range="lt">4.2_p48</vulnerable>
    </package>
  </affected>
  <background>
    <p>Bash is the standard GNU Bourne Again SHell. </p>
  </background>
  <description>
    <p>Stephane Chazelas reported that Bash incorrectly handles function
      definitions, allowing attackers to inject arbitrary code.
    </p>
  </description>
  <impact type="high">
    <p>A remote attacker could exploit this vulnerability to execute arbitrary
      commands even in restricted environments.
    </p>
  </impact>
  <workaround>
    <p>There is no known workaround at this time.</p>
  </workaround>
  <resolution>
    <p>All Bash 3.1 users should upgrade to the latest version:</p>
    
    <code>
      # emerge --sync
      # emerge --ask --oneshot --verbose "&gt;=app-shells/bash-3.1_p18"
    </code>
    
    <p>All Bash 3.2 users should upgrade to the latest version:</p>
    
    <code>
      # emerge --sync
      # emerge --ask --oneshot --verbose "&gt;=app-shells/bash-3.2_p52"
    </code>
    
    <p>All Bash 4.0 users should upgrade to the latest version:</p>
    
    <code>
      # emerge --sync
      # emerge --ask --oneshot --verbose "&gt;=app-shells/bash-4.0_p39"
    </code>
    
    <p>All Bash 4.1 users should upgrade to the latest version:</p>
    
    <code>
      # emerge --sync
      # emerge --ask --oneshot --verbose "&gt;=app-shells/bash-4.1_p12"
    </code>
    
    <p>All Bash 4.2 users should upgrade to the latest version:</p>
    
    <code>
      # emerge --sync
      # emerge --ask --oneshot --verbose "&gt;=app-shells/bash-4.2_p48"
    </code>
    
  </resolution>
  <references>
    <uri 
link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2014-6271";>CVE-2014-6271</uri>
  </references>
  <metadata tag="requester" timestamp="Wed, 24 Sep 2014 16:00:19 
+0000">a3li</metadata>
  <metadata tag="submitter" timestamp="Wed, 24 Sep 2014 22:06:57 
+0000">a3li</metadata>
</glsa>