Fcron fcronsighup create and delete files
| fcron-fcronsighup-create-files (18077) |  Medium Risk |
Description:
Fcron could allow a local attacker to delete or create arbitrary files, caused by a vulnerability in the fcronsighup tool, which instructs fcron to reread the fcron tables. By supplying a filename containing multiple forward slash (/) characters, a remote attacker could create or delete an arbitrary file on the vulnerable system.
Platforms Affected:
- FreeBSD, FreeBSD
- Gentoo, Linux
- OpenBSD, OpenBSD
- Thibault Godouet, Fcron 2.0.1
- Thibault Godouet, Fcron 2.9.4
Remedy:
Upgrade to the latest version of Fcron (2.0.2 or 2.9.5.1 or later), available from the Fcron Web site. See References.
For Gentoo Linux:
Upgrade to the latest version of Fcron (2.0.2, >= 2.9.5.1 or later), as listed in GLSA 200411-27. See References.
For other distributions:
Contact your vendor for upgrade or patch information.
Consequences:
File Manipulation
References:
- Fcron Web site, Welcome to Fcron's home page ! at http://fcron.free.fr/.
- iDEFENSE Security Advisory 11.15.04, Multiple Security Vulnerabilities in Fcron at http://www.idefense.com/application/poi/display?id=157&type=vulnerabilities&flashstatus=true.
- BID-11684: Fcron FCronTab/FCronSighUp Multiple Local Vulnerabilities
- CVE-2004-1032: fcronsighup in Fcron 2.0.1, 2.9.4, and possibly earlier versions allows local users to delete arbitrary files or create arbitrary empty files via a target filename with a large number of leading slash (/) characters such that fcronsighup does not properly append the intended fcrontab.sig to the resulting string.
- GLSA-200411-27: Fcron: Multiple vulnerabilities
Reported:
Nov 15, 2004
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