| 1 |
rbu 08/10/09 17:35:27 |
| 2 |
|
| 3 |
Added: glsa-200810-02.xml |
| 4 |
Log: |
| 5 |
GLSA 200810-02 |
| 6 |
|
| 7 |
Revision Changes Path |
| 8 |
1.1 xml/htdocs/security/en/glsa/glsa-200810-02.xml |
| 9 |
|
| 10 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/security/en/glsa/glsa-200810-02.xml?rev=1.1&view=markup |
| 11 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/security/en/glsa/glsa-200810-02.xml?rev=1.1&content-type=text/plain |
| 12 |
|
| 13 |
Index: glsa-200810-02.xml |
| 14 |
=================================================================== |
| 15 |
<?xml version="1.0" encoding="utf-8"?> |
| 16 |
<?xml-stylesheet href="/xsl/glsa.xsl" type="text/xsl"?> |
| 17 |
<?xml-stylesheet href="/xsl/guide.xsl" type="text/xsl"?> |
| 18 |
<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd"> |
| 19 |
|
| 20 |
<glsa id="200810-02"> |
| 21 |
<title>Portage: Untrusted search path local root vulnerability</title> |
| 22 |
<synopsis> |
| 23 |
A search path vulnerability in Portage allows local attackers to execute |
| 24 |
commands with root privileges if emerge is called from untrusted |
| 25 |
directories. |
| 26 |
</synopsis> |
| 27 |
<product type="ebuild">portage</product> |
| 28 |
<announced>October 09, 2008</announced> |
| 29 |
<revised>October 09, 2008: 01</revised> |
| 30 |
<bug>239560</bug> |
| 31 |
<access>local</access> |
| 32 |
<affected> |
| 33 |
<package name="sys-apps/portage" auto="yes" arch="*"> |
| 34 |
<unaffected range="ge">2.1.4.5</unaffected> |
| 35 |
<vulnerable range="lt">2.1.4.5</vulnerable> |
| 36 |
</package> |
| 37 |
</affected> |
| 38 |
<background> |
| 39 |
<p> |
| 40 |
Portage is Gentoo's package manager which is responsible for |
| 41 |
installing, compiling and updating all packages on the system through |
| 42 |
the Gentoo rsync tree. |
| 43 |
</p> |
| 44 |
</background> |
| 45 |
<description> |
| 46 |
<p> |
| 47 |
The Gentoo Security Team discovered that several ebuilds, such as |
| 48 |
sys-apps/portage, net-mail/fetchmail or app-editors/leo execute Python |
| 49 |
code using "python -c", which includes the current working directory in |
| 50 |
Python's module search path. For several ebuild functions, Portage did |
| 51 |
not change the working directory from emerge's working directory. |
| 52 |
</p> |
| 53 |
</description> |
| 54 |
<impact type="high"> |
| 55 |
<p> |
| 56 |
A local attacker could place a specially crafted Python module in a |
| 57 |
directory (such as /tmp) and entice the root user to run commands such |
| 58 |
as "emerge sys-apps/portage" from that directory, resulting in the |
| 59 |
execution of arbitrary Python code with root privileges. |
| 60 |
</p> |
| 61 |
</impact> |
| 62 |
<workaround> |
| 63 |
<p> |
| 64 |
Do not run "emerge" from untrusted working directories. |
| 65 |
</p> |
| 66 |
</workaround> |
| 67 |
<resolution> |
| 68 |
<p> |
| 69 |
All Portage users should upgrade to the latest version: |
| 70 |
</p> |
| 71 |
<code> |
| 72 |
# cd /root |
| 73 |
# emerge --sync |
| 74 |
# emerge --ask --oneshot --verbose ">=sys-apps/portage-2.1.4.5"</code> |
| 75 |
<p> |
| 76 |
NOTE: To upgrade to Portage 2.1.4.5 using 2.1.4.4 or prior, you must |
| 77 |
run emerge from a trusted working directory, such as "/root". |
| 78 |
</p> |
| 79 |
</resolution> |
| 80 |
<references> |
| 81 |
<uri link="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-4394">CVE-2008-4394</uri> |
| 82 |
</references> |
| 83 |
<metadata tag="submitter" timestamp="Wed, 08 Oct 2008 16:50:57 +0000"> |
| 84 |
rbu |
| 85 |
</metadata> |
| 86 |
<metadata tag="bugReady" timestamp="Wed, 08 Oct 2008 16:58:04 +0000"> |
| 87 |
rbu |
| 88 |
</metadata> |
| 89 |
</glsa> |
Archives