blob: 508b29e96f843031ddd829e24279d48f20d2d4e6 [file] [log] [blame]
<?xml version="1.0" encoding="utf-8"?>
<glsa id="200407-01">
<title>Esearch: Insecure temp file handling</title>
The eupdatedb utility in esearch creates a file in /tmp without first
checking for symlinks. This makes it possible for any user to create
arbitrary files.
<product type="ebuild">esearch</product>
<announced>July 01, 2004</announced>
<revised>May 22, 2006: 02</revised>
<package name="app-portage/esearch" auto="yes" arch="*">
<unaffected range="ge">0.6.2</unaffected>
<vulnerable range="le">0.6.1</vulnerable>
Esearch is a replacement for the Portage command "emerge search". It
uses an index to speed up searching of the Portage tree.
The eupdatedb utility uses a temporary file (/tmp/ to
indicate that the eupdatedb process is running. When run, eupdatedb
checks to see if this file exists, but it does not check to see if it
is a broken symlink. In the event that the file is a broken symlink,
the script will create the file pointed to by the symlink, instead of
printing an error and exiting.
<impact type="normal">
An attacker could create a symlink from /tmp/ to a
nonexistent file (such as /etc/nologin), and the file will be created
the next time esearchdb is run.
There is no known workaround at this time. All users should upgrade to
the latest available version of esearch.
All users should upgrade to the latest available version of esearch, as
# emerge sync
# emerge -pv &quot;&gt;=app-portage/esearch-0.6.2&quot;
# emerge &quot;&gt;=app-portage/esearch-0.6.2&quot;</code>
<uri link="">CVE-2004-0655</uri>
<metadata tag="submitter">