LiveActive security incident?Get immediate response
CVE Record

CVE-2018-9384: In multiple locations, there is a possible way to bypass KASLR due to an unusual root cause.

In multiple locations, there is a possible way to bypass KASLR due to an unusual root cause. This could lead to local information disclosure with System execution privileges needed. User interaction is not needed for exploitation.

MediumCVSS 4.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This Android Kernel issue could let a highly privileged local attacker learn information that weakens kernel address randomization. It is not reported as remotely exploitable and requires no user interaction, but it can reduce defenses that protect Android devices from deeper compromise.

Executive priority

Treat this as moderate priority. It is not a standalone remote takeover in the provided evidence, but it weakens a kernel protection and matters more on devices with broader privilege exposure or delayed Android patching.

Technical view

CVE-2018-9384 is a CWE-200 information disclosure issue in the Android Kernel. The CVSS vector is local, low complexity, high privileges required, no user interaction, unchanged scope, and high confidentiality impact. The described result is a possible KASLR bypass.

Likely exposure

Exposure is most relevant to Android devices using affected kernel code referenced by Google's Pixel June 2018 security bulletin. The source bundle does not identify specific device models, kernel branches, or downstream vendor status.

Exploitation context

The source bundle does not cite active exploitation, and KEV status is false. Exploitation is local and requires System-level privileges, so it is mainly a defense-in-depth concern or a potential helper for chained attacks.

Researcher notes

Evidence is sparse. The CVE record names multiple locations and an unusual root cause but does not provide technical locations, commits, affected branches, or proof-of-concept details in the supplied bundle.

Mitigation direction

  • Apply vendor updates associated with the Pixel Security Bulletin 2018-06-01.
  • Check OEM or carrier guidance for affected Android device patch availability.
  • Prioritize devices that run sensitive workloads or permit elevated local code execution.
  • Restrict paths that allow untrusted code to obtain high local privileges.

Validation and detection

  • Confirm Android security patch level against vendor guidance for June 2018 fixes.
  • Inventory Android devices and map OEM patch status where available.
  • Review mobile EDR or MDM telemetry for local privilege escalation indicators.
  • Document any unsupported devices that cannot receive vendor kernel updates.
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-200: 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-9384 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
Medium
CVSS
4.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/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
4.4CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N0.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.4Medium
CVSS 3.1 vector shape for CVE-2018-9384Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/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
GoogleAndroidAndroid Kernelunaffected
Weakness

CWE details

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

CWE-200 · source CWE mapping

Exposure of Sensitive Information to an Unauthorized Actor

Exposure of Sensitive Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.