dbcve.org
AndroidOperating system · Google

CVE-2024-25984

MEDIUM · 6.2 CVSS v3.1 Published 2024-03-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
67/100
Remediation priority · Elevated
No privileges Zero-click

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 · unedited
In dumpBatteryDefend of dump_power.cpp, there is a possible out of bounds read due to a heap buffer overflow. This could lead to local information disclosure 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 confidence

A heap buffer overflow exists in the dumpBatteryDefend function within dump_power.cpp, causing an out-of-bounds read. This allows a local attacker to read sensitive information from memory beyond the intended buffer boundaries without requiring any elevated privileges or user interaction.

MitigationImplement proper bounds checking when reading from the heap buffer in the dumpBatteryDefend function to prevent out-of-bounds access. Review memory allocation sizes and ensure buffer accesses are validated against allocated sizes.

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
AndroidOperating system
Affected:= 13.0

CVSS 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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Android version is 13.0
    Go to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shell
    Affected if The installed Android version is exactly 13.0 (matching the affected version = 13.0)
  2. Confirm dump_power.cpp component presence
    Search for the file dump_power.cpp in the system partition or within the power management subsystem binaries. On Android, this may reside in /system/bin or vendor partitions.
    Affected if The dump_power.cpp file containing the dumpBatteryDefend function is present on the device
  3. Identify if battery/power dump interface is accessible
    Check if any debug or diagnostic interfaces related to battery or power management are exposed. Look for entries in /system/bin, /vendor/bin, or examine SELinux policies for dump_power related utilities.
    Affected if A utility or service that invokes the dumpBatteryDefend function is accessible to local unprivileged users
  4. Check for dump battery defend trigger point
    Review logs (logcat) or examine available system diagnostic commands that could invoke the power dump functionality. The function is called from dumpBatteryDefend in dump_power.cpp.
    Affected if The device has an exposed code path that calls dumpBatteryDefend without requiring elevated privileges

The device is affected if it runs Android exactly version 13.0 AND contains the dumpBatteryDefend function from dump_power.cpp with an accessible trigger point for local unprivileged users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper bounds checking when reading from the heap buffer in the dumpBatteryDefend function to prevent out-of-bounds access. Review memory allocation sizes and ensure buffer accesses are validated against allocated sizes.

Recommended fix Moderate confidence
  1. Check your device manufacturer's Android security update documentation for the availability of a patch addressing this vulnerability
  2. Contact your device OEM or carrier for the specific security patch date that includes the fix for CVE-2024-25984
  3. For developers: Apply the patch to the Android framework code in system/core/power/cpp/dump_power.cpp ensuring proper bounds checking is added in the dumpBatteryDefend function
  4. Verify the fix by reviewing the upstream AOSP change that addresses the heap buffer overflow in dumpBatteryDefend
  5. After patching, test to confirm the out of bounds read no longer occurs and no information disclosure is possible
Caveat Android security patches are backward compatible; applying the monthly security update should not break existing functionality

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Android Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-25984 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-25984 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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