LiveActive security incident?Get immediate response
CVE Record

CVE-2018-9377: In getIntentForIntentSender of ActivityManagerService.java, there is a possible way to access user metadata...

In getIntentForIntentSender of ActivityManagerService.java, there is a possible way to access user metadata due to a pending intent. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

HighCVSS 8.4Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2018-9377 is a high-severity Android flaw that could let a local attacker gain elevated privileges and access user metadata without user interaction. The listed exposure is Android 6 through 8.1. The provided sources do not show active exploitation, but unsupported legacy devices should be treated as business risk.

Executive priority

Prioritize remediation for legacy Android devices with access to corporate data, especially unmanaged or unsupported endpoints. This is high severity, but the provided evidence does not support an active-exploitation claim.

Technical view

The flaw is in ActivityManagerService.java, getIntentForIntentSender, involving pending intent handling and user metadata exposure. CVSS 3.1 is 8.4 with local attack vector, low complexity, no privileges, and no user interaction. Impact is rated high across confidentiality, integrity, and availability.

Likely exposure

Exposure appears limited to Google Android versions 6, 6.0.1, 7, 7.1.1, 7.1.2, 8, and 8.1 that lack the relevant June 2018 vendor security update or OEM equivalent.

Exploitation context

Sources describe local privilege escalation with no additional execution privileges and no user interaction. The bundle marks KEV as false and provides no cited evidence of active exploitation or public weaponization.

Researcher notes

Evidence is limited to the CVE record and Google Pixel bulletin reference. Treat the root issue as pending-intent metadata exposure in ActivityManagerService. Do not infer affected versions beyond the listed Android releases.

Mitigation direction

  • Apply the June 2018 Pixel security update or OEM equivalent where supported.
  • Retire or isolate Android 6 through 8.1 devices that cannot receive fixes.
  • Use MDM controls to restrict unsupported legacy Android devices from sensitive systems.
  • Check Google and device-vendor guidance for model-specific update availability.

Validation and detection

  • Inventory Android device OS versions across managed and unmanaged fleets.
  • Verify each affected device has the relevant June 2018 security update or later.
  • Flag Android 6 through 8.1 devices without vendor patch confirmation.
  • Confirm unsupported devices are removed, isolated, or access-restricted.
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-908: 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-9377 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
8.4 (3.1)
Known Exploited
No
Published

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

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:L/AC:L/PR:N/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
GoogleAndroid6, 6.0.1, 7, 7.1.1, 7.1.2, 8, 8.1unaffected
Weakness

CWE details

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

CWE-908 · source CWE mapping

Use of Uninitialized Resource

Use of Uninitialized Resource represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.