LiveActive security incident?Get immediate response
CVE Record

CVE-2018-9475: In HeadsetInterface::ClccResponse of btif_hf.cc, there is a possible out of bounds stack write due to a mis...

In HeadsetInterface::ClccResponse of btif_hf.cc, there is a possible out of bounds stack write due to a missing bounds check. This could lead to remote escalation of privilege via Bluetooth, if the recipient has enabled SIP calls with no additional execution privileges needed. User interaction is not needed for exploitation.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2018-9475 is an Android Bluetooth flaw that can let a nearby attacker gain elevated privileges on affected devices. The issue requires SIP calls to be enabled, needs no user interaction, and does not require attacker authentication. It is not listed as KEV exploited in the provided sources.

Executive priority

Treat this as high priority for legacy Android fleets and managed mobile devices. The risk is proximity-based and conditional, but successful exploitation could compromise confidentiality, integrity, and availability.

Technical view

The flaw is a missing bounds check in HeadsetInterface::ClccResponse in btif_hf.cc, causing a possible out-of-bounds stack write. The CVE maps to CWE-787 and has CVSS 3.1 score 7.5 with adjacent-network Bluetooth attack vector and high attack complexity.

Likely exposure

Exposure is limited to affected Android 7, 8, 8.1, 9, and listed development branches, especially unpatched devices with SIP calls enabled and Bluetooth reachable by nearby attackers.

Exploitation context

The source states remote privilege escalation via Bluetooth is possible without user interaction or additional privileges, but only if SIP calls are enabled. KEV is false, and no cited source confirms active exploitation.

Researcher notes

Evidence supports an Android Bluetooth stack out-of-bounds stack write in btif_hf.cc. The sources do not provide exploit details, public exploitation evidence, or standalone mitigations beyond the Android security bulletin context.

Mitigation direction

  • Apply Android security updates covering the 2018-09-01 bulletin where available.
  • Check OEM or carrier advisories for device-specific firmware availability.
  • Disable SIP calling on affected devices where it is not required.
  • Reduce Bluetooth exposure on unpatched devices until remediation is confirmed.

Validation and detection

  • Inventory Android versions and security patch levels across managed devices.
  • Identify devices running affected Android versions or listed development branches.
  • Confirm whether SIP calling is enabled on potentially affected devices.
  • Verify remediation against the Android 2018-09-01 security bulletin.
Prepared
Confidence
high
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-787: 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-9475 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.5 (3.1)
Known Exploited
No
Published

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

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:A/AC:H/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
GoogleAndroid7, 8, 8.1, 9, 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-787 · source CWE mapping

Out-of-bounds Write

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