LiveActive security incident?Get immediate response
CVE Record

CVE-2018-9432: In createPhonebookDialogView and createMapDialogView of BluetoothPermissionActivity.java, there is a possib...

In createPhonebookDialogView and createMapDialogView of BluetoothPermissionActivity.java, there is a possible permissions bypass. This could lead to local escalation of privilege due to hiding and bypassing the user's ability to disable access to contacts, 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 issue could let a local app or actor bypass part of a Bluetooth permission flow, preventing the user from effectively denying contact access. The business risk is highest for organizations still operating old Android 6 through 8.1 devices that have not received the July 2018 Android security fixes.

Executive priority

Treat this as a legacy Android fleet risk. It is not presented as actively exploited, but the impact is high where old devices still process contacts or business communications.

Technical view

CVE-2018-9432 is a CWE-276 permissions bypass in Android BluetoothPermissionActivity, specifically createPhonebookDialogView and createMapDialogView. The source describes local privilege escalation through hiding and bypassing the user's ability to disable contacts access. CVSS 3.1 is 7.8 high, but the supplied description and CVSS UI value conflict on user interaction.

Likely exposure

Exposure is most likely on unpatched Android 6, 6.0.1, 7, 8, 8.1, and listed Android development branches. Modern patched Android devices are not indicated as affected in the supplied sources.

Exploitation context

The source bundle does not show CISA KEV listing or cited active exploitation. Exploitation is local, needs low privileges, and the description says user interaction is needed, despite the supplied CVSS vector listing UI:N.

Researcher notes

Evidence is limited to the CVE record and Android July 2018 bulletin reference. The supplied data has an inconsistency: the prose says user interaction is required, while the CVSS vector says UI:N. Do not infer exploit availability from this bundle.

Mitigation direction

  • Apply Android security updates incorporating the July 2018 bulletin fixes.
  • Inventory Android devices still running affected versions.
  • Prioritize vendor-supported devices that still receive security patches.
  • Retire or isolate Android devices that cannot receive vendor fixes.
  • Check device OEM guidance for patch availability and security patch level mapping.

Validation and detection

  • Confirm Android OS versions across managed device inventory.
  • Check each device's Android security patch level against vendor guidance.
  • Identify Bluetooth-enabled workflows involving contact or message access.
  • Review MDM compliance reports for unsupported Android 6 through 8.1 devices.
  • Document exceptions for devices that cannot be patched or retired.
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-9432 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-9432Attack 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
GoogleAndroid6, 6.0.1, 7, 8, 8.1, nyc-mr1-dev, nyc-mr2-devunaffected
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.