CVE-2005-4158

Public Exploit

Description

Sudo before 1.6.8 p12, when the Perl taint flag is off, does not clear the (1) PERLLIB, (2) PERL5LIB, and (3) PERL5OPT environment variables, which allows limited local users to cause a Perl script to include and execute arbitrary library files that have the same name as library files that are included by the script.

4.6

CVSS

Severity: Medium

CVSS 2.0 •

EPSS 0.51%

Vendor Advisory mandriva.com Vendor Advisory trustix.org Vendor Advisory ubuntu.com Vendor Advisory novell.com Vendor Advisory debian.org Vendor Advisory mandriva.com Vendor Advisory secunia.com Vendor Advisory sudo.ws

Affected: n/a n/a

References

Link	Tags
http://www.mandriva.com/security/advisories?name=MDKSA-2005:234	vendor advisory
http://secunia.com/advisories/18549	third party advisory
https://exchange.xforce.ibmcloud.com/vulnerabilities/23102	vdb entry
http://secunia.com/advisories/18558	third party advisory
http://www.trustix.org/errata/2006/0002/	vendor advisory
http://secunia.com/advisories/18463	third party advisory
http://secunia.com/advisories/18308	third party advisory
http://www.vupen.com/english/advisories/2005/2386	vdb entry
http://www.securityfocus.com/bid/15394	exploit vdb entry patch
http://secunia.com/advisories/18156	third party advisory
http://secunia.com/advisories/18102	third party advisory
https://www.ubuntu.com/usn/usn-235-1/	vendor advisory
http://www.novell.com/linux/security/advisories/2006_02_sr.html	vendor advisory
http://www.debian.org/security/2006/dsa-946	vendor advisory
http://securitytracker.com/alerts/2005/Nov/1015192.html	vdb entry patch
http://www.mandriva.com/security/advisories?name=MDKSA-2006:159	vendor advisory
http://secunia.com/advisories/21692	third party advisory
http://www.sudo.ws/sudo/alerts/perl_env.html	patch vendor advisory
http://secunia.com/advisories/17534/	third party advisory patch vendor advisory

Frequently Asked Questions

What is the severity of CVE-2005-4158?: CVE-2005-4158 has been scored as a medium severity vulnerability.
How to fix CVE-2005-4158?: To fix CVE-2005-4158, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2005-4158 being actively exploited in the wild?: It is possible that CVE-2005-4158 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~1% probability that this vulnerability will be exploited by malicious actors in the next 30 days.