First published: Tue Aug 14 2012(Updated: )
Last updated 24 July 2024
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
debian/python3.1 | ||
Python 2.7 | >=2.7.0<2.7.4 | |
Python 2.7 | >=3.2.0<3.2.4 | |
Python 2.7 | >=3.3.0<3.3.3 | |
Ubuntu | =10.04 | |
Ubuntu | =11.04 | |
Ubuntu | =11.10 | |
Ubuntu | =12.04 | |
Ubuntu | =12.10 | |
Debian Linux | =6.0 | |
>=2.7.0<2.7.4 | ||
>=3.2.0<3.2.4 | ||
>=3.3.0<3.3.3 | ||
=10.04 | ||
=11.04 | ||
=11.10 | ||
=12.04 | ||
=12.10 | ||
=6.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2012-2135 is medium.
Python versions 3.1 through 3.3 are affected, as well as certain versions of Ubuntu Linux and Debian Linux.
Remote attackers can exploit CVE-2012-2135 to obtain sensitive information or cause a denial of service through memory corruption and crash.
Yes, there are fixes available for CVE-2012-2135. It is recommended to update to the latest patched version of Python 3 or apply the security updates provided by Ubuntu Linux and Debian Linux.
More information about CVE-2012-2135 can be found on the Debian Bug Tracker, Python Bug Tracker, and Secunia advisory websites.