dbcve.org
AndroidOperating system · Google

CVE-2018-9372

HIGH · 7.8 CVSS v3.1 Published 2024-11-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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 cmd_flash_mmc_sparse_img of dl_commands.c, there is a possible out of bounds write due to a missing bounds check. This could lead to a local escalation of privilege in the bootloader 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 · high confidence

An out-of-bounds write vulnerability exists in the cmd_flash_mmc_sparse_img function in dl_commands.c due to a missing bounds check when processing MMC sparse image data. This allows a local attacker to escalate privileges in the bootloader context without requiring additional execution privileges or user interaction.

MitigationAdd proper bounds validation in the cmd_flash_mmc_sparse_img function to ensure buffer writes stay within allocated memory boundaries before performing any write operations.

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:all versions

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
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 checks

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

  1. Identify if the device runs Google Android
    Confirm the device is running Google Android OS (the affected product). This vulnerability exists in the Android bootloader component.
    Affected if The device is running Google Android OS - all versions are affected per the CVE description.
  2. Check if the bootloader exposes MMC sparse image flashing functionality
    Determine if the bootloader has the cmd_flash_mmc_sparse_img command available. This is typically accessible via fastboot or a bootloader console interface.
    Affected if The cmd_flash_mmc_sparse_img function is present and accessible in the bootloader environment.
  3. Verify the bootloader version
    Check the installed bootloader version. On Android devices, this can often be found in the bootloader version string displayed during boot, via 'fastboot getvar all', or in the device's /proc/bootinfo if available.
    Affected if The bootloader version is not patched - the CVE affects all versions of Google Android according to the advisory.
  4. Confirm physical or debug access to bootloader
    Determine if the attacker can access the bootloader interface (fastboot, USB debugging, or serial debug). This vulnerability requires local access to the bootloader context.
    Affected if The bootloader is accessible for command execution (e.g., fastboot mode is unlocked or accessible).

A device is affected if it runs Google Android, has the cmd_flash_mmc_sparse_img command available in its bootloader, and the attacker can access the bootloader interface to trigger the out-of-bounds write.

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

Add proper bounds validation in the cmd_flash_mmc_sparse_img function to ensure buffer writes stay within allocated memory boundaries before performing any write operations.

Recommended fix Moderate confidence

Latest Android Security Patch Level (manufacturers release these monthly; CVE-2018-9372 was addressed in the June 2018 Android Security Bulletin)

  1. Check with your device manufacturer (OEM) for the latest Android Security Bulletin and bootloader update containing the fix for CVE-2018-9372
  2. Apply the OEM-provided security update or bootloader firmware update that addresses this vulnerability
  3. For developers: If you maintain or build custom bootloaders, locate the cmd_flash_mmc_sparse_img function in dl_commands.c and add proper bounds checking before any write operations to prevent out-of-bounds memory access
Caveat Bootloader updates may have strict versioning requirements and could void warranties if modified incorrectly; custom bootloaders may need careful regression testing

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

Fix this in Android Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,120
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-9372 — 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-2018-9372 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