Description
sudo before 1.6.8p2 allows local users to execute arbitrary commands by using "()" style environment variables to create functions that have the same name as any program within the bash script that is called without using the program's full pathname.
Product(s):
- MandrakeSoft Mandrake Multi Network Firewall 8.2
- Todd Miller Sudo 1.5.6
- Todd Miller Sudo 1.5.7
- Todd Miller Sudo 1.5.8
- Todd Miller Sudo 1.5.9
- Todd Miller Sudo 1.6.1
- Todd Miller Sudo 1.6.2
- Todd Miller Sudo 1.6.3
- Todd Miller Sudo 1.6.3_p1
- Todd Miller Sudo 1.6.3_p2
- Todd Miller Sudo 1.6.3_p3
- Todd Miller Sudo 1.6.3_p4
- Todd Miller Sudo 1.6.3_p5
- Todd Miller Sudo 1.6.3_p6
- Todd Miller Sudo 1.6.3 p7
- Todd Miller Sudo 1.6.4
- Todd Miller Sudo 1.6.4 Patch 1
- Todd Miller Sudo 1.6.4 Patch 2
- Todd Miller Sudo 1.6.5
- Todd Miller Sudo 1.6.5 Patch 1
- Todd Miller Sudo 1.6.5 Patch 2
- Todd Miller Sudo 1.6.6
- Todd Miller Sudo 1.6.7
- Todd Miller Sudo 1.6.8
- Todd Miller Sudo 1.6.8_p1
- Todd Miller Sudo 1.6
- Debian Linux 3.0 on Alpha
- Debian Linux 3.0 on ARM
- Debian Linux 3.0 on HPPA
- Debian Linux 3.0 on IA-32
- Debian Linux 3.0 on IA-64
- Debian Linux 3.0 on M68k
- Debian Linux 3.0 on MIPS
- Debian Linux 3.0 on MIPSEL
- Debian Linux 3.0 on PPC
- Debian Linux 3.0 on S/390
- Debian Linux 3.0 on SPARC
- MandrakeSoft Mandrake Linux 10.0
- Mandrakesoft Mandrake Linux 10.0 on AMD64
- MandrakeSoft Mandrake Linux 10.1
- Mandrakesoft Mandrake Linux 10.1 on x86_64
- MandrakeSoft Mandrake Linux 9.2
- Mandrakesoft Mandrake Linux 9.2 on AMD64
- MandrakeSoft Mandrake Linux Corporate Server 2.1
- Mandrakesoft Mandrake Linux Corporate Server 2.1 on x86_64
- Trustix Secure Linux 1.5
- Trustix Secure Linux 2.0
- Trustix Secure Linux 2.1
- Trustix Secure Linux 2.2
- Ubuntu Linux 4.1 on IA64
- Ubuntu Linux 4.1 on PPC
Question to Ask Vendors:
- Can you confirm whether your systems are affected by CVE-2004-1051, and if so, what steps are you currently taking to mitigate this vulnerability?
- What is your estimated timeline for fully resolving CVE-2004-1051 in your products or services, and how will you communicate updates on this issue to us as your customer?
Recommended Actions:
- Check out the advisory links provided below.