RHSA-2011:0027: Low: python security, bug fix, and enhancement update

Published Jan 13, 2011
·
Updated

Python is an interpreted, interactive, object-oriented programminglanguage.It was found that many applications embedding the Python interpreter didnot specify a valid full path to the script or application when calling thePySysSetArgv API function, which could result in the addition of thecurrent working directory to the module search path (sys.path). A localattacker able to trick a victim into running such an application in anattacker-controlled directory could use this flaw to execute code with thevictim's privileges. This update adds the PySysSetArgvEx API. Developerscan modify their applications to use this new API, which sets sys.argvwithout modifying sys.path. (CVE-2008-5983)Multiple flaws were found in the Python rgbimg module. If an applicationwritten in Python was using the rgbimg module and loaded aspecially-crafted SGI image file, it could cause the application to crashor, possibly, execute arbitrary code with the privileges of the userrunning the application. (CVE-2009-4134, CVE-2010-1449, CVE-2010-1450)Multiple flaws were found in the Python audioop module. Supplying certaininputs could cause the audioop module to crash or, possibly, executearbitrary code. (CVE-2010-1634, CVE-2010-2089)This update also fixes the following bugs: When starting a child process from the subprocess module in Python 2.4, the parent process could leak file descriptors if an error occurred. Thisupdate resolves the issue. (BZ#609017) Prior to Python 2.7, programs that used "ulimit -n" to enable communication with large numbers of subprocesses could still monitor only1024 file descriptors at a time, which caused an exception:ValueError: filedescriptor out of range in select()This was due to the subprocess module using the "select" system call. Themodule now uses the "poll" system call, removing this limitation.(BZ#609020) Prior to Python 2.5, the tarfile module failed to unpack tar files if the path was longer than 100 characters. This update backports the tarfilemodule from Python 2.5 and the issue no longer occurs. (BZ#263401) The email module incorrectly implemented the logic for obtaining attachment file names: the getfilename() fallback for using the deprecated"name" parameter of the "Content-Type" header erroneously used the"Content-Disposition" header. This update backports a fix from Python 2.6,which resolves this issue. (BZ#644147) Prior to version 2.5, Python's optimized memory allocator never released memory back to the system. The memory usage of a long-running Pythonprocess would resemble a "high-water mark". This update backports a fixfrom Python 2.5a1, which frees unused arenas, and adds a non-standardsys.debugmallocstats() function, which prints diagnostic information tostderr. Finally, when running under Valgrind, the optimized allocator isdeactivated, to allow more convenient debugging of Python memory usageissues. (BZ#569093) The urllib and urllib2 modules ignored the noproxy variable, which could lead to programs such as "yum" erroneously accessing a proxy server forURLs covered by a "noproxy" exclusion. This update backports fixes ofurllib and urllib2, which respect the "noproxy" variable, which fixesthese issues. (BZ#549372)As well, this update adds the following enhancements: This update introduces a new python-libs package, subsuming the majority of the content of the core python package. This makes both 32-bit and64-bit Python libraries available on PowerPC systems. (BZ#625372) The python-libs.i386 package is now available for 64-bit Itanium with the 32-bit Itanium compatibility mode. (BZ#644761)All Python users are advised to upgrade to these updated packages, whichcontain backported patches to correct these issues and add theseenhancements.

Affected Software

10 affected componentsFixes available
redhat/python<2.4.3-43.el5
2.4.3-43.el5
redhat/python<2.4.3-43.el5
2.4.3-43.el5
redhat/python-devel<2.4.3-43.el5
2.4.3-43.el5
redhat/python-devel<2.4.3-43.el5
2.4.3-43.el5
redhat/python-libs<2.4.3-43.el5
2.4.3-43.el5
redhat/python-tools<2.4.3-43.el5
2.4.3-43.el5
redhat/tkinter<2.4.3-43.el5
2.4.3-43.el5
redhat/python-libs<2.4.3-43.el5
2.4.3-43.el5
redhat/python-tools<2.4.3-43.el5
2.4.3-43.el5
redhat/tkinter<2.4.3-43.el5
2.4.3-43.el5

Remediation

Event History

Jan 13, 2011
Advisory Published
via Red Hat·12:00 AM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of RHSA-2011:0027?

RHSA-2011:0027 is classified as important due to the potential for unauthorized execution of arbitrary code.

2

How do I fix RHSA-2011:0027?

To address RHSA-2011:0027, upgrade to the fixed version of Python 2.4.3-43.el5.

3

Which packages are affected by RHSA-2011:0027?

The affected packages include python, python-devel, python-libs, python-tools, and tkinter in the specified version.

4

Is RHSA-2011:0027 applicable to all systems?

RHSA-2011:0027 specifically affects Red Hat Enterprise Linux 5 systems running the vulnerable version of Python.

5

What are the risks of not addressing RHSA-2011:0027?

Not addressing RHSA-2011:0027 may lead to security vulnerabilities that can be exploited to execute malicious code.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203