LiveActive security incident?Get immediate response
CVE Record

CVE-2018-9477: In the development options section of the Settings app, there is a possible authentication bypass due to a...

In the development options section of the Settings app, there is a possible authentication bypass due to a missing permission check. 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

CVE-2018-9477 is a high-severity Android Settings flaw in Developer options. A person with local access and some user interaction could bypass an authentication check and gain elevated privileges on affected Android 8 and 8.1 devices.

Executive priority

Treat as high priority for remaining Android 8 or 8.1 fleets, especially shared, unmanaged, or high-trust devices. Business urgency is lower where those versions are absent or fully patched.

Technical view

The issue is a missing permission check in the Android Settings app Developer options area. The CVSS 3.1 vector is AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, indicating local access, low complexity, no privileges, required user interaction, and high impact.

Likely exposure

Exposure is limited to Google Android 8 and 8.1 according to the provided affected-product data. The bundle does not identify other vendors, device models, or custom Android distributions as affected.

Exploitation context

The source bundle does not show known active exploitation, and CISA KEV status is false. Exploitation is local and requires user interaction; the public data provided does not include exploit details.

Researcher notes

The provided evidence is concise and does not include proof-of-concept details, patch commits, or device-specific advisories. Validate against the Android bulletin and device-vendor update channels before broadening affected-scope claims.

Mitigation direction

  • Identify Android 8 and 8.1 devices in managed inventory.
  • Check Google's September 2018 Android Security Bulletin for vendor patch guidance.
  • Apply applicable Android security updates from the device vendor or carrier.
  • Prioritize replacement or isolation where affected devices cannot receive fixes.

Validation and detection

  • Confirm device Android version and security patch level from inventory or MDM.
  • Review whether Developer options are enabled on affected devices.
  • Verify applicable vendor bulletin coverage for each device build.
  • Document devices that cannot be updated and track 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-294: 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
description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2018-9477 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:N/UI:R/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:N/UI:R/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-9477Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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
GoogleAndroid8, 8.1unaffected
Weakness

CWE details

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

CWE-294 · source CWE mapping

Authentication Bypass by Capture-replay

Authentication Bypass by Capture-replay represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.