CVE-2015-1528
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 · uneditedInteger overflow in the native_handle_create function in libcutils/native_handle.c in Android before 5.1.1 LMY48M allows attackers to obtain a different application's privileges or cause a denial of service (Binder heap memory corruption) via a crafted application, aka internal bug 19334482.
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 · high confidenceInteger overflow in native_handle_create in Android's libcutils allows a crafted application to manipulate heap memory allocation sizes, causing heap corruption in the Binder subsystem. This memory corruption can be exploited to obtain elevated privileges of other applications or cause denial of service.
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<= 5.1CVSS 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
- Network
- Complexity
- M
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:M/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 versionCheck the device settings under Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shellAffected if The reported version is 5.1 or lower (5.0, 4.x, etc.)
-
Confirm libcutils is in useVerify that the libcutils library exists on the device at /system/lib/libcutils.so. This library contains the native_handle_create function used by the Binder subsystemAffected if The libcutils library is present and the Android version is 5.1 or below
-
Verify Binder subsystem accessThe Binder IPC mechanism relies on native_handle_create. Check if processes can access Binder via /dev/binder, /dev/hwbinder, or /dev/vndbinderAffected if The Binder device nodes are accessible and the Android version is 5.1 or below, indicating the vulnerable code path could be reached
The environment is affected if the Android device is running version 5.1 or earlier, as the integer overflow in libcutils native_handle_create exists in those versions and can be triggered through the Binder subsystem.
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.
dbcve · scopedUpdate affected Android devices to version 5.1.1 LMY48M or later to patch the integer overflow in libcutils. For devices that cannot receive official updates, consider network segmentation or additional application sandboxing controls.
Android 5.1.1 LMY48M or later
- Identify the Android device(s) running version 5.1 or earlier
- Navigate to Settings > About Phone (or About Tablet) > System Updates on the device
- Check for and apply any available Android 5.1.1 (build LMY48M or later) system update from the device manufacturer or carrier
- If no update is available from the original equipment manufacturer, consider flashing a stock image from the manufacturer's support site that includes the 5.1.1 LMY48M patch
- Verify the update was applied successfully by confirming the Android version shows 5.1.1 or higher in Settings > About Phone
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation2.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,568.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-1528 — 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-2015-1528 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