LuxMan maped binary file could be used to read memory
|luxman-maped-read-memory (10549)||Medium Risk|
LuxMan could allow a local attacker to read or possibly write to memory. A local attacker could create a malicious gzip file and cause the LuxMan maped binary to execute this file by modifying the PATH environment variable to cause /dev/mem to be copied to /dev/tmp. This would allow the attacker to gain read and write access to /dev/mem. An attacker could possibly exploit this vulnerability to gain root privileges on the system.
For Debian GNU/Linux 3.0 (woody):
Upgrade to the latest luxman package (0.41-17.1 or later), as listed in DSA 189-1. See References.
- iDEFENSE Security Advisory 11.06.02: Non-Explicit Path Vulnerability in LuxMan.
- BID-6113: Frank McIngvale LuxMan Memory File Descriptor Leakage Vulnerability
- CVE-2002-1245: Maped in LuxMan 0.41 uses the user-provided search path to find and execute the gzip program, which allows local users to modify /dev/mem and gain privileges via a modified PATH environment variable that points to a Trojan horse gzip program.
- DSA-189: luxman -- local root exploit
- OSVDB ID: 11870: LuxMan Maped PATH Subversion Privilege Escalation
- Debian Debian Linux 3.0
- Frank McIngvale's LuxMan 0.41
Nov 06, 2002
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 ignore thisxforceignore this@ignore thisus.ignore thisibm.comignore this