LiveActive security incident?Get immediate response
CVE Record

CVE-2018-9364: In the LG LAF component, there is a special command that allowed modification of certain partitions.

In the LG LAF component, there is a special command that allowed modification of certain partitions. This could lead to bypass of secure boot. User interaction is not needed for exploitation.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This vulnerability concerns LG's LAF component, where a special command could modify certain partitions and potentially bypass secure boot. The source says no user interaction is required. The bundle does not show active exploitation or a confirmed affected device list beyond the Android bulletin context.

Executive priority

Treat this as a high-priority legacy mobile platform issue where impacted devices remain in use. Business urgency depends on whether vulnerable LG LAF-based builds are still deployed and patchable.

Technical view

CVE-2018-9364 describes improper handling in LG LAF that allowed modification of selected partitions, creating an integrity impact and possible secure boot bypass. The CVSS 3.1 score is 7.5 with high integrity impact and no privileges or user interaction required. Evidence in the bundle is limited on exact affected builds.

Likely exposure

Exposure is most likely limited to Android devices or builds that include the vulnerable LG LAF component. The provided affected record is sparse and lists Android with version value “SoCVersion,” so organizations need vendor patch-level mapping before declaring exposure.

Exploitation context

The source bundle does not identify public exploitation, and KEV status is false. The risk comes from unauthenticated, no-user-interaction partition modification that could undermine secure boot protections if a vulnerable implementation is present.

Researcher notes

The public bundle gives the vulnerability condition and impact but not detailed affected model lists, patches, or exploitation evidence. Avoid assuming all Android or all LG devices are affected without OEM bulletin correlation.

Mitigation direction

  • Check the Android June 2018 security bulletin and relevant OEM guidance.
  • Apply vendor-supported firmware or security updates for affected devices.
  • Prioritize devices with unknown patch levels for inventory review.
  • Retire or isolate devices that cannot receive applicable vendor updates.

Validation and detection

  • Inventory Android devices that may include the LG LAF component.
  • Compare device patch levels against the June 2018 Android bulletin.
  • Check OEM release notes for CVE-2018-9364 coverage.
  • Document devices with unknown firmware lineage as unresolved exposure.
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 · medium confidence lookup

CWE-203: Information exposure and cloud metadata lookup

Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. 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-9364 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.5 (3.1)
Known Exploited
No
Published

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

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.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N3.93.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

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

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-203 · source CWE mapping

Observable Discrepancy

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