First published: Thu Feb 14 2008(Updated: )
Description of problem: Added checks for integer overflows, contributed by Google. Some are only available if asserts are left in the code, in cases where they can't be triggered from Python code. Proposed upstream patch: <a href="http://svn.python.org/view?rev=60793&view=rev">http://svn.python.org/view?rev=60793&view=rev</a>
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/python | <0:2.3.4-14.7.el4_8.2 | 0:2.3.4-14.7.el4_8.2 |
redhat/python | <0:2.4.3-24.el5_3.6 | 0:2.4.3-24.el5_3.6 |
CPython | =2.0.1 | |
CPython | =2.3.7 | |
CPython | =2.4.5 | |
CPython | =1.5.2 | |
CPython | <=2.5.1 | |
CPython | =1.6.1 | |
CPython | =2.1.3 | |
CPython | =2.2.3 | |
Python Babel Localedata | <2.5.12 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
(Appears in the following advisories)
CVE-2008-3143 has been classified as a moderate severity vulnerability due to potential integer overflow issues.
To mitigate CVE-2008-3143, upgrade to a patched version of Python above the specified vulnerable versions as indicated in security advisories.
CVE-2008-3143 affects Python versions including 1.5.2, 1.6.1, 2.0.1, 2.1.3, 2.2.3, 2.3.4 up to 2.3.7, 2.4.3 up to 2.4.5, and up to 2.5.1.
The potential impacts of CVE-2008-3143 include the risk of unexpected behavior or crashes in applications using the affected versions of Python.
Yes, there are proposed upstream patches available to fix CVE-2008-3143, which should be applied to the affected Python versions.