# CVE-2008-1679: Integer overflow in n/a

> Integer overflows in Python's imageop module allow attackers to cause crashes or execute arbitrary code via crafted images.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 21 Apr 2008
- **Updated:** 7 Aug 2024
- **Also known as:** AZL-109560, GHSA-v4w5-5ggg-69xc, PSF-2008-1

## What is CVE-2008-1679?

CVE-2008-1679 is a medium-severity vulnerability in Python Python, published on 21 Apr 2008. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Multiple integer overflows in imageop.c in Python before 2.5.3 allow context-dependent attackers to cause a denial of service (crash) and possibly execute arbitrary code via crafted images that trigger heap-based buffer overflows.  NOTE: this issue is due to an incomplete fix for CVE-2007-4965.

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2008-1679?

It affects 1 product.


Products: Python Python.

## How do I fix CVE-2008-1679?

Upgrade to a fixed version.

## Is CVE-2008-1679 being exploited?

There is no known exploitation of CVE-2008-1679 in the wild and no public exploit code.

## Other vulnerabilities in Python Python

- [CVE-2008-5031](https://insights.sbomify.com/CVE-2008-5031/): Integer overflow in n/a (critical 10.0)
- [CVE-2014-4650](https://insights.sbomify.com/CVE-2014-4650/): Path traversal in n/a (critical 9.8)
- [CVE-2016-5636](https://insights.sbomify.com/CVE-2016-5636/): Integer overflow in n/a (critical 9.8)
- [CVE-2007-4559](https://insights.sbomify.com/CVE-2007-4559/): Path traversal in n/a (critical 9.8)
- [CVE-2017-17522](https://insights.sbomify.com/CVE-2017-17522/): Command injection in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-1679 and fix it if it is affected.

What it is: CVE-2008-1679 is a medium-severity vulnerability in Python Python, published on 21 Apr 2008. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2008-1679 in the wild and no public exploit code.

Affected product: Python Python. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2008-1679/ (Markdown: https://insights.sbomify.com/CVE-2008-1679/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2008-1679
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2008-1679
- OSV: https://osv.dev/vulnerability/CVE-2008-1679

---
From sbomify Insights: https://insights.sbomify.com/CVE-2008-1679/
Summaries are generated and may contain mistakes; the official description above is the record.