LiveActive security incident?Get immediate response
CVE Record

CVE-2018-9369: In bootloader there is fastboot command allowing user specified kernel command line arguments.

In bootloader there is fastboot command allowing user specified kernel command line arguments. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is needed for exploitation.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This Android bootloader issue lets a local attacker influence kernel startup arguments through a fastboot command. If exploitable on a device, it can lead to full privilege escalation and compromise confidentiality, integrity, and availability. The public bundle does not show active exploitation.

Executive priority

Treat as high priority for managed Android fleets with older or unsupported devices. Business urgency is greatest where devices process sensitive data, are physically accessible, or cannot receive vendor firmware updates.

Technical view

CVE-2018-9369 is a bootloader fastboot command weakness involving user-specified kernel command line arguments. The CVSS 3.1 score is 7.8, with local attack vector, low complexity, low privileges, and high impact across CIA. The affected entry names Google Android SoCVersion.

Likely exposure

Exposure appears limited to Android devices using the affected SoC/bootloader implementation referenced by the Android June 2018 security bulletin. The issue is local rather than remotely network-exploitable based on the supplied CVSS vector.

Exploitation context

The source says exploitation can cause local privilege escalation and requires user interaction, though the CVSS vector lists UI:N. KEV is false, and no provided source claims known active exploitation or public exploit availability.

Researcher notes

Evidence is sparse in the supplied bundle. The affected product is broad, listed as Google Android SoCVersion, and applicability likely depends on OEM/SoC bootloader implementation. Note the inconsistency between the description requiring user interaction and CVSS UI:N.

Mitigation direction

  • Check Google and OEM guidance for the June 2018 Android security bulletin.
  • Apply relevant Android security updates or bootloader firmware updates where available.
  • Prioritize unsupported affected devices for retirement, replacement, or risk acceptance.
  • Limit access to devices where bootloader or fastboot misuse is plausible.

Validation and detection

  • Inventory Android devices by OEM, SoC, bootloader version, and security patch level.
  • Confirm whether devices received the June 2018 Android security bulletin fixes.
  • Review vendor advisories for model-specific applicability and firmware availability.
  • Document any devices that cannot be patched and their compensating controls.
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-276: 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-9369 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-9369Attack 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
GoogleAndroidSoCVersionunaffected
Weakness

CWE details

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

CWE-276 · source CWE mapping

Incorrect Default Permissions

Incorrect Default Permissions represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.