LiveActive security incident?Get immediate response
CVE Record

CVE-2018-9430: In prop2cfg of btif_storage.cc, there is a possible out of bounds write due to an incorrect bounds check.

In prop2cfg of btif_storage.cc, there is a possible out of bounds write due to an incorrect bounds check. This could lead to remote code execution with no additional execution privileges needed. User interaction is not needed for exploitation.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2018-9430 is a critical Android memory corruption issue. A faulty bounds check in prop2cfg of btif_storage.cc may allow remote code execution without user interaction or privileges. Business risk is highest for unmanaged or legacy Android 6 through 8.1 devices that have not received vendor security updates.

Executive priority

Treat as urgent for legacy Android fleets because the impact is full device compromise and exploitation requires no user action. Priority depends on whether affected versions remain in service.

Technical view

The source describes a possible out-of-bounds write in Android’s prop2cfg function in btif_storage.cc caused by incorrect bounds checking. CVSS 3.1 is 9.8, with network attack vector, low complexity, no privileges, no user interaction, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure appears limited to listed Android versions 6, 6.0.1, 7, 7.1.1, 7.1.2, 8, and 8.1, especially devices missing relevant vendor security updates.

Exploitation context

The record states remote code execution is possible without privileges or user interaction. The bundle does not show CISA KEV listing or cited evidence of active exploitation, so active exploitation should not be assumed.

Researcher notes

Evidence is limited to the CVE description, affected version list, CVSS vector, and Android Pixel bulletin reference. The CWE entry lists CWE-125, but the description says out-of-bounds write; report that inconsistency when tracking remediation.

Mitigation direction

  • Apply the relevant Android or Pixel vendor security update where available.
  • Check OEM guidance for device-specific firmware and security patch availability.
  • Retire or isolate Android 6 through 8.1 devices that cannot be updated.
  • Prioritize managed-device compliance for minimum Android security patch levels.

Validation and detection

  • Inventory Android devices and record OS version and security patch level.
  • Identify devices running Android 6 through 8.1.
  • Confirm vendor advisories or patch notes cover CVE-2018-9430.
  • Flag unsupported devices for replacement, isolation, or 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-125: 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

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. 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-9430 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
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/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
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2018-9430Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/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-125 · source CWE mapping

Out-of-bounds Read

Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.