eroaster insecure temporary lockfile
| eroaster-tmp-lockfile-insecure (12829) |
Description:
ECLiPt Roaster (eroaster) creates insecure temporary files that are used as lockfiles. This could allow a local attacker to overwrite sensitive files on the system with privileges of the eroaster user.
Platforms Affected:
- Debian, Debian Linux 3.0
- Gentoo, Linux
- MandrakeSoft, Mandrake Linux 9.0
- MandrakeSoft, Mandrake Linux 9.1
- MandrakeSoft, Mandrake Linux Corporate Server 2.1
- Martin Preishuber, eroaster
Remedy:
For Debian GNU/Linux 3.0 (woody):
Upgrade to the latest eroaster package (2.1.0.0.3-2woody1 or later), as listed in DSA 366-1. See References.
For Mandrake Linux:
Upgrade to the latest eroaster package, as listed below. Refer to MandrakeSoft Security Advisory MDKSA-2003:083 : eroaster for more information. See References.
Mandrake Linux 9.0, 9.1, and Corporate Server 2.1: 2.1.0-6.1mdk or later
For Gentoo Linux:
Upgrade to the latest version of eroaster (2.1.0-r2 or later), as listed in Gentoo Linux Security Announcement 200309-04. See References.
For other distributions:
Contact your vendor for upgrade or patch information.
Consequences:
File Manipulation
References:
- Gentoo Linux Security Announcement 200309-04, eroaster at http://www.linuxsecurity.com/content/view/105330/104/. (From LinuxSecurity archive)
- BID-8350: ERoaster Local Insecure Temporary File Creation Vulnerability
- CVE-2003-0656: eroaster before 2.2.0 allows local users to overwrite arbitrary files via a symlink attack on a temporary file that is used as a lockfile.
- DSA-366: eroaster -- insecure temporary file
- MDKSA-2003:083: Updated eroaster packages fix temporary file vulnerability
Reported:
Aug 05, 2003
The information within this database may change without notice. Use of this information constitutes acceptance for use in an AS IS condition. There are NO warranties, implied or otherwise, with regard to this information or its use. Any use of this information is at the user's risk. In no event shall the author/distributor (IBM Internet Security Systems X-Force) be held liable for any damages whatsoever arising out of or in connection with the use or spread of this information.
For corrections or additions please email xforce@iss.net
