CVE-2009-0607
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMultiple 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceInteger overflow vulnerabilities exist in the chk_calloc and leak_calloc functions within Bionic's malloc_leak.c in Android 1.0. These overflows could potentially cause incorrect memory allocation sizes or enable heap corruption, though the specific exploitation mechanics and impact are not detailed in available sources.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/AC:L/Au:N/C:C/I:C/A:C
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Android SDK versionCheck the installed Android SDK version by running 'android list targets' or inspecting the SDK manifest/settings. Look for the SDK platform version number.Affected if The SDK version is exactly 1.0 (the only affected version)
-
Locate Bionic libc librarySearch for the Bionic libc shared library in the Android system image or build artifacts. Common paths include /system/lib/libc.so or within the SDK's system image files.Affected if Bionic libc from Android 1.0 is present in the environment
-
Inspect malloc_leak.c source fileIf source code is available, locate malloc_leak.c in the Bionic source tree and examine the chk_calloc and leak_calloc functions for missing integer overflow checks before size*nmemb calculations.Affected if The malloc_leak.c file contains vulnerable chk_calloc or leak_calloc functions without proper overflow validation
-
Verify calloc usageReview application code or system services that use the calloc function from Bionic. Check if allocations could involve large nmemb or size values that might trigger overflow.Affected if calloc from the vulnerable Bionic library is actively used with potentially large allocation parameters
A system is affected only if it runs the exact Android 1.0 SDK with the vulnerable Bionic malloc_leak.c implementation containing the unpatched chk_calloc and leak_calloc functions.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement proper integer overflow checks in calloc implementations before performing arithmetic on allocation parameters; validate that size*nmemb calculations cannot exceed allocated memory bounds or wrap around.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2009-0607 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2009-0607 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data