LiveActive security incident?Get immediate response
CVE Record

CVE-2018-9372: In cmd_flash_mmc_sparse_img of dl_commands.c, there is a possible out of bounds write due to a missing boun...

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.

HighCVSS 7.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2018-9372 is an Android bootloader flaw that can let someone with local access escalate privileges. The bug is an out-of-bounds write in sparse MMC image flashing logic. It is not described as remotely exploitable and no user interaction is needed.

Executive priority

Treat this as a high-priority mobile firmware hygiene issue for Android fleets, especially unmanaged or older devices. Business urgency is lower than internet-facing remote code execution, but impact is severe if affected devices remain unpatched.

Technical view

The issue is in cmd_flash_mmc_sparse_img in dl_commands.c. A missing bounds check can cause CWE-787 out-of-bounds write behavior in the bootloader, with CVSS 3.1 score 7.8 and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure appears limited to Android devices or SoC bootloader implementations containing the vulnerable flashing code. The source bundle does not identify specific device models, chipset families, or OEM firmware versions, so asset matching requires vendor and device-specific confirmation.

Exploitation context

The CVE describes local privilege escalation with low privileges, no user interaction, and local attack vector. The bundle marks KEV false and provides no cited evidence of active exploitation, public exploit availability, or remote exploitation.

Researcher notes

The affected entry lists Google Android with version value SoCVersion, but the bundle lacks specific CPEs or device identifiers. Avoid assuming all Android devices are affected. Validation should focus on OEM firmware provenance and whether the vulnerable bootloader component shipped on managed assets.

Mitigation direction

  • Check OEM and Google Android guidance for CVE-2018-9372 applicability.
  • Apply vendor firmware or security updates covering the June 2018 Android bulletin.
  • Prioritize devices with exposed bootloader, repair, or flashing workflows.
  • Restrict physical and local administrative access to managed Android devices.

Validation and detection

  • Inventory Android device models, SoC details, bootloader versions, and patch levels.
  • Map devices against OEM advisories referencing CVE-2018-9372.
  • Confirm whether the June 2018 Android bulletin fixes are present.
  • Track exceptions where OEM support status or firmware lineage is unclear.
Prepared
Confidence
medium
Sources
3

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-787: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2018-9372 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2018-9372Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
GoogleAndroidSoCVersionunaffected
Weakness

CWE details

CWE-787

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-787 · source CWE mapping

Out-of-bounds Write

Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs