# CVE-2009-4413: Integer overflow in n/a

> Remote attackers can crash the Polipo proxy server by sending a request with a large Content-Length value, causing an integer overflow and segmentation fault.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/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:** 24 Dec 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-739g-q9wv-464j

## What is CVE-2009-4413?

CVE-2009-4413 is a medium-severity vulnerability in n/a, published on 24 Dec 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The httpClientDiscardBody function in client.c in Polipo 0.9.8, 0.9.12, 1.0.4, and possibly other versions, allows remote attackers to cause a denial of service (crash) via a request with a large Content-Length value, which triggers an integer overflow, a signed-to-unsigned conversion error with a negative value, and a segmentation fault.

Weakness: CWE-189

## Which versions are affected by CVE-2009-4413?

It affects 1 product.


Products: Pps.jussieu Polipo.

## How do I fix CVE-2009-4413?

Upgrade to a fixed version.

## Is CVE-2009-4413 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-4413 exists.

Public exploit code:

- Polipo 1.0.4 - Remote Memory Corruption (PoC) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2009-3305](https://insights.sbomify.com/CVE-2009-3305/): Denial of service in n/a (medium 5.0)
- [CVE-2008-7191](https://insights.sbomify.com/CVE-2008-7191/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-4413 and fix it if it is affected.

What it is: CVE-2009-4413 is a medium-severity vulnerability in n/a, published on 24 Dec 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-4413 exists.

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-2009-4413/ (Markdown: https://insights.sbomify.com/CVE-2009-4413/index.md)
```

## Sources

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

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