CVE-2008-4864: Multiple integer overflows in imageop.c in the imageop module in Python 1.5.2 through 2.5.1 allow context-dependent attackers to break out…
Noroxi assessment
Priority: Monitor (action score 36/100)
- Public proof-of-concept code exists (Exploit-DB); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 21% (FIRST EPSS); higher than 97.6% of all records.
- No special conditions are required; it is repeatable.
- Fixed version: python (Red Hat:enterprise_linux:3::as) 0:2.2.3-6.11; python-debuginfo (Red Hat:enterprise_linux:3::as) 0:2.2.3-6.11; python-devel (Red Hat:enterprise_linux:3::as) 0:2.2.3-6.11.
Low priority for now. Upgrade to python (Red Hat:enterprise_linux:3::as) 0:2.2.3-6.11; python-debuginfo (Red Hat:enterprise_linux:3::as) 0:2.2.3-6.11; python-devel (Red Hat:enterprise_linux:3::as) 0:2.2.3-6.11 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Multiple integer overflows in imageop.c in the imageop module in Python 1.5.2 through 2.5.1 allow context-dependent attackers to break out of the Python VM and execute arbitrary code via large integer values in certain arguments to the crop function, leading to a buffer overflow, a different vulnerability than CVE-2007-4965 and CVE-2008-1679.
- Published
- Oct 31, 2008
- Updated
- Jun 16, 2026
- EPSS
- 21.0% · 97th percentile
- CWE
- CWE-190
Report tools
Action score
36
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 6 / 30 · 21.0%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| python | python | cpe:2.3:a:python:python |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- python python1.5.2 and later · before 2.4.6
- python python2.5.0 and later · before 2.5.3
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Red Hat:enterprise_linux:3::as | python | before 0:2.2.3-6.11 | 0:2.2.3-6.11 |
| Red Hat:enterprise_linux:3::as | python-debuginfo | before 0:2.2.3-6.11 | 0:2.2.3-6.11 |
| Red Hat:enterprise_linux:3::as | python-devel | before 0:2.2.3-6.11 | 0:2.2.3-6.11 |
| Red Hat:enterprise_linux:3::as | python-tools | before 0:2.2.3-6.11 | 0:2.2.3-6.11 |
| Red Hat:enterprise_linux:3::as | tkinter | before 0:2.2.3-6.11 | 0:2.2.3-6.11 |
| Red Hat:enterprise_linux:4::as | python | before 0:2.3.4-14.7.el4_8.2 | 0:2.3.4-14.7.el4_8.2 |
| Red Hat:enterprise_linux:4::as | python-debuginfo | before 0:2.3.4-14.7.el4_8.2 | 0:2.3.4-14.7.el4_8.2 |
| Red Hat:enterprise_linux:4::as | python-devel | before 0:2.3.4-14.7.el4_8.2 | 0:2.3.4-14.7.el4_8.2 |
| Red Hat:enterprise_linux:4::as | python-docs | before 0:2.3.4-14.7.el4_8.2 | 0:2.3.4-14.7.el4_8.2 |
| Red Hat:enterprise_linux:4::as | python-tools | before 0:2.3.4-14.7.el4_8.2 | 0:2.3.4-14.7.el4_8.2 |
| Red Hat:enterprise_linux:4::as | tkinter | before 0:2.3.4-14.7.el4_8.2 | 0:2.3.4-14.7.el4_8.2 |
| Red Hat:enterprise_linux:5::client | python-tools | before 0:2.4.3-24.el5_3.6 | 0:2.4.3-24.el5_3.6 |
| Red Hat:enterprise_linux:5::client | tkinter | before 0:2.4.3-24.el5_3.6 | 0:2.4.3-24.el5_3.6 |
| Red Hat:enterprise_linux:5::client_workstation | python | before 0:2.4.3-24.el5_3.6 | 0:2.4.3-24.el5_3.6 |
| Red Hat:enterprise_linux:5::client_workstation | python-debuginfo | before 0:2.4.3-24.el5_3.6 | 0:2.4.3-24.el5_3.6 |
| Red Hat:enterprise_linux:5::client_workstation | python-devel | before 0:2.4.3-24.el5_3.6 | 0:2.4.3-24.el5_3.6 |
Same product
python: all recordsOther highest-scoring records for the same primary product.
- CVE-2016-5636Integer overflow in the get_data function in zipimport.c in CPython (aka Python) before 2.7.12, 3.x before 3.4.5, and 3.5.x before 3.5.2…47Plan
- CVE-2007-4559Directory traversal vulnerability in the (1) extract and (2) extractall functions in the tarfile module in Python allows user-assisted…47Plan
- CVE-2021-3177Python 3.x through 3.9.1 has a buffer overflow in PyCArg_repr in _ctypes/callproc.c, which may lead to remote code execution in certain…46Plan
Published before and after this one in the same product
- ← EarlierCVE-2008-3143Aug 1, 2008 · Multiple integer overflows in Python before 2.5.2 might allow context-dependent attackers to have an unknown impact via vectors related to…31Monitor
- ← EarlierCVE-2008-3144Aug 1, 2008 · Multiple integer overflows in the PyOS_vsnprintf function in Python/mysnprintf.c in Python 2.5.2 and earlier allow context-dependent…21Monitor
- Later →CVE-2008-5031Nov 10, 2008 · Multiple integer overflows in Python 2.2.3 through 2.5.1, and 2.6, allow context-dependent attackers to have an unknown impact via a large…41Plan
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| red hat:python | 0:2.4.3-24.el5_3.6 · Red Hat:enterprise_linux:5::client_workstation | Package registry (OSV) |
| red hat:python-debuginfo | 0:2.4.3-24.el5_3.6 · Red Hat:enterprise_linux:5::client_workstation | Package registry (OSV) |
| red hat:python-devel | 0:2.4.3-24.el5_3.6 · Red Hat:enterprise_linux:5::client_workstation | Package registry (OSV) |
| red hat:python-docs | 0:2.3.4-14.7.el4_8.2 · Red Hat:enterprise_linux:4::as | Package registry (OSV) |
| red hat:python-tools | 0:2.4.3-24.el5_3.6 · Red Hat:enterprise_linux:5::client | Package registry (OSV) |
| red hat:tkinter | 0:2.4.3-24.el5_3.6 · Red Hat:enterprise_linux:5::client | Package registry (OSV) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Exploit-DB entry ×2
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Exploit-DB entry | dos | 2009-11-24 |
| Exploit-DB entry | dos | 2008-10-27 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- First PoC-5 d
- Published
- TodayNov 16, 2026+6589 d
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- P · data can be read
- Integrity
- P · data or configuration can be modified
- Availability
- P · the service can be disrupted
- Attack complexity
- Low
- Confidentiality impact
- P
- Integrity impact
- P
- Availability impact
- P
Weakness class (CWE)
CWE-190 · Integer Overflow or WraparoundCVSS vector
AV:N/AC:L/Au:N/C:P/I:P/A:P
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (14 more)Show less
- secunia.com/advisories/33937
- secunia.com/advisories/37471
- support.apple.com/kb/HT3438
- svn.python.org/view/python/trunk/Modules/imageop.c?rev=66689&view=diff&r1=66689&r2=66688&p1=python/trunk/Modules/imageop.c&p2=/python/trunk/Modules/imageop.c
- svn.python.org/view?rev=66689&view=rev
- www.openwall.com/lists/oss-security/2008/10/27/2
- www.openwall.com/lists/oss-security/2008/10/29/3
- www.securityfocus.com/archive/1/507985/100/0/threaded
- www.securityfocus.com/bid/31932
- www.vmware.com/security/advisories/VMSA-2009-0016.html
- www.vupen.com/english/advisories/2009/3316
- exchange.xforce.ibmcloud.com/vulnerabilities/46606
- oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A10702
- oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A8354
Vendor advisories and official records. Exploit/PoC links are deliberately left out.