LiveActive security incident?Get immediate response
CVE Record

CVE-2018-9387: In multiple functions of mnh-sm.c, there is a possible way to trigger a heap overflow due to an integer ove...

In multiple functions of mnh-sm.c, there is a possible way to trigger a heap overflow due to an integer overflow. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2018-9387 is a high-severity Android kernel vulnerability that could let a local attacker gain higher privileges. The flaw involves an integer overflow that may trigger a heap overflow. Public sources do not show remote exploitation or active exploitation evidence.

Executive priority

Treat this as a high-priority legacy mobile kernel issue for Android fleets. Urgency is highest where old or unsupported devices remain in use. There is no provided evidence of active exploitation, but privilege escalation impact is significant.

Technical view

The CVE describes multiple vulnerable functions in mnh-sm.c. An integer overflow can lead to heap overflow and local escalation of privilege. CVSS 3.1 is 7.8 with local attack vector, low complexity, low privileges, no user interaction, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is most relevant to Android devices running affected kernel code referenced by the June 2018 Pixel security bulletin. The provided data does not identify exact device models, kernel branches, or OEM build ranges beyond Android Kernel.

Exploitation context

The source bundle says exploitation requires local access with low privileges and no user interaction. It does not cite CISA KEV listing, public exploitation, exploit availability, or remote attack paths.

Researcher notes

Evidence is limited to the CVE record, CVE List entry, and Android Pixel bulletin reference. The vulnerable file is mnh-sm.c, but the bundle does not provide patch diffs, affected commit ranges, or exploitability details beyond CVSS and description.

Mitigation direction

  • Check the Android Pixel June 2018 bulletin for vendor remediation guidance.
  • Update supported Android devices through OEM or carrier security update channels.
  • Prioritize devices handling sensitive data or used by privileged staff.
  • Retire or restrict unsupported devices that cannot receive kernel security updates.

Validation and detection

  • Inventory Android and Pixel devices in managed fleets.
  • Record OS version, kernel build, and Android security patch level.
  • Compare device status with vendor bulletin applicability.
  • Confirm MDM or vulnerability tooling reflects remediation status.
  • Document exceptions for devices that cannot be updated.
Prepared
Confidence
medium
Sources
3

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-120: 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-9387 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-9387Attack 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
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
GoogleAndroidAndroid Kernelunaffected
Weakness

CWE details

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

CWE-120 · source CWE mapping

Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')

Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.