CVE-2006-1542: Stack-based buffer overflow in Python 2.4.2 and earlier, running on Linux 2.6.12.5 under gcc 4.0.3 with libc 2.3.5, allows local users to cause a "sta...

Description

Stack-based buffer overflow in Python 2.4.2 and earlier, running on Linux 2.6.12.5 under gcc 4.0.3 with libc 2.3.5, allows local users to cause a "stack overflow," and possibly gain privileges, by running a script from a current working directory that has a long name, related to the realpath function. NOTE: this might not be a vulnerability. However, the fact that it appears in a programming language interpreter could mean that some applications are affected, although attack scenarios might be limited because the attacker might already need to cross privilege boundaries to cause an exploitable program to be placed in a directory with a long name; or, depending on the method that Python uses to determine the current working directory, setuid applications might be affected.

Metrics

EPSS Probability

0.95%

56.7th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Vendor	Product	Versions
Python	Python	<= 2.4.2

References

http://secunia.com/advisories/31492Broken Link
http://www.gotfault.net/research/exploit/gexp-python.pyExploit
http://www.redhat.com/support/errata/RHSA-2008-0629.htmlThird Party Advisory
https://www.exploit-db.com/exploits/1591Third Party Advisory, VDB Entry
http://secunia.com/advisories/31492Broken Link
http://www.gotfault.net/research/exploit/gexp-python.pyExploit
http://www.redhat.com/support/errata/RHSA-2008-0629.htmlThird Party Advisory
https://www.exploit-db.com/exploits/1591Third Party Advisory, VDB Entry

Timeline

Published: Mar 30, 2006
Last Modified: Jun 16, 2026
Status: Modified

Frequently Asked Questions

What is CVE-2006-1542?

Stack-based buffer overflow in Python 2.4.2 and earlier, running on Linux 2.6.12.5 under gcc 4.0.3 with libc 2.3.5, allows local users to cause a "stack overflow," and possibly gain privileges, by running a script from a current working directory that has a long name, related to the realpath function. NOTE: this might not be a vulnerability. However, the fact that it appears in a programming language interpreter could mean that some applications are affected, although attack scenarios might be limited because the attacker might already need to cross privilege boundaries to cause an exploitable program to be placed in a directory with a long name; or, depending on the method that Python uses to determine the current working directory, setuid applications might be affected.

How severe is CVE-2006-1542?

Severity scoring for CVE-2006-1542 is pending analysis. The EPSS model estimates a 0.95% probability of exploitation in the next 30 days.

How do I fix CVE-2006-1542?

Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2006

View all 2006CVEs →