# CVE-2010-1513: Integer overflow in n/a

> Remote attackers can execute arbitrary code by sending large JPG or PNG images to Ziproxy, exploiting integer overflows leading to heap buffer overflows.

- **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:** Not needed
- **Fix available:** Yes
- **Published:** 26 May 2010
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2010-1513, GHSA-8fr7-79w9-7h79

## What is CVE-2010-1513?

CVE-2010-1513 is a medium-severity vulnerability in n/a, published on 26 May 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple integer overflows in src/image.c in Ziproxy before 3.0.1 allow remote attackers to execute arbitrary code via (1) a large JPG image, related to the jpg2bitmap function or (2) a large PNG image, related to the png2bitmap function, leading to heap-based buffer overflows.

Weakness: CWE-189

## Which versions are affected by CVE-2010-1513?

It affects 1 product.


Products: Daniel Mealha Cabrita Ziproxy.

## How do I fix CVE-2010-1513?

Upgrade to a fixed version.

## Is CVE-2010-1513 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2010-2350](https://insights.sbomify.com/CVE-2010-2350/): Memory corruption in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-1513 and fix it if it is affected.

What it is: CVE-2010-1513 is a medium-severity vulnerability in n/a, published on 26 May 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2010-1513 in the wild and no public exploit code.

Affected product: n/a. 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-2010-1513/ (Markdown: https://insights.sbomify.com/CVE-2010-1513/index.md)
```

## Sources

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

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