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

> Integer overflows in Android Bionic malloc functions have unknown impact and attack vectors, requiring further investigation for potential memory corruption risks.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 17 Feb 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-cv5g-5rc7-m952

## What is CVE-2009-0607?

CVE-2009-0607 is a high-severity vulnerability in n/a, published on 17 Feb 2009. 

### Official description

Multiple integer overflows in malloc_leak.c in Bionic in Open Handset Alliance Android 1.0 have unknown impact and attack vectors, related to the (1) chk_calloc and (2) leak_calloc functions.

Weakness: CWE-189

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

It affects 1 product.


Products: Openhandsetalliance Android Sdk.

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

No fix has been published for CVE-2009-0607 yet. Limit exposure of the affected software until one is available.

## Is CVE-2009-0607 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-0606](https://insights.sbomify.com/CVE-2009-0606/): Privilege escalation in n/a (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2009-0607 is a high-severity vulnerability in n/a, published on 17 Feb 2009. 
Exploitation: There is no known exploitation of CVE-2009-0607 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-2009-0607/ (Markdown: https://insights.sbomify.com/CVE-2009-0607/index.md)
```

## Sources

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

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