CVE-2024-49745
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 · uneditedIn growData of Parcel.cpp, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
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 confidenceA bounds check error in the growData function of Parcel.cpp allows an out-of-bounds memory write, which can be exploited to achieve local privilege escalation. The vulnerability requires no user interaction or additional execution privileges.
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= 12.0= 12.1= 13.0= 14.0= 15.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
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 versionOn the device, go to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADBAffected if Version is exactly 12.0, 12.1, 13.0, 14.0, or 15.0
-
Locate Parcel.cpp in Android systemSearch for Parcel.cpp in /system/core/libutils/ or within framework binaries on the deviceAffected if The vulnerable Parcel.cpp file exists in the system image
-
Verify growData function is presentInspect the Parcel.cpp binary or decompiled code for the growData function implementationAffected if The growData function exists and contains the bounds check logic being exploited
-
Check for privilege escalation indicatorsReview system logs or audit logs for unexpected local privilege escalation eventsAffected if Unexplained privilege escalation has occurred and Android version matches affected versions
A user is affected if their Android device runs version 12.0, 12.1, 13.0, 14.0, or 15.0 and contains the vulnerable Parcel.cpp growData function.
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 · scopedApply the vendor patch for CVE-2024-49745 which corrects the bounds check logic in the Parcel.cpp growData function to prevent out-of-bounds writes.
Android 15 or latest monthly security patch (2024-11-01 or later)
- 1. Check the current Android version on the device by going to Settings > About Phone > Android version
- 2. Navigate to Settings > System > Software Update (or Settings > About Phone > Software Update)
- 3. Check for available updates and download the latest security patch update
- 4. Ensure the device is connected to Wi-Fi and has sufficient battery (or connect to charger)
- 5. Install the update and restart the device
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-49745 — 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-2024-49745 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