LiveActive security incident?Get immediate response
CVE Record

CVE-2018-9481: In bta_hd_set_report_act of bta_hd_act.cc, there is a possible out-of-bounds read due to an integer overflow.

In bta_hd_set_report_act of bta_hd_act.cc, there is a possible out-of-bounds read due to an integer overflow. This could lead to remote information disclosure in the Bluetooth service with no additional execution privileges needed. User interaction is not needed for exploitation.

MediumCVSS 6.2Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2018-9481 is an Android Bluetooth service flaw that could expose information without user interaction or extra privileges. The provided data rates it medium severity and lists Android 8, 8.1, and 9 as affected. There is no supplied evidence of active exploitation.

Executive priority

Treat this as a moderate mobile fleet hygiene issue, not an emergency based on the provided evidence. Focus on finding legacy Android devices, confirming patch status, and retiring unsupported assets.

Technical view

The issue is an out-of-bounds read in bta_hd_set_report_act of bta_hd_act.cc, caused by integer overflow. The source maps it to CWE-125 and CWE-190. CVSS 3.1 is 6.2 with high confidentiality impact, no integrity or availability impact, and no privileges or user interaction required.

Likely exposure

Organizations may be exposed where Android 8, 8.1, or 9 devices remain in use with the vulnerable Bluetooth service. The source bundle does not identify specific device models, patch levels, or OEM distributions.

Exploitation context

The CVE description says exploitation needs no user interaction and no additional execution privileges. KEV status is false, and the provided sources do not show public active exploitation. The CVSS vector lists local attack vector, so operational range and exact preconditions need vendor confirmation.

Researcher notes

The supplied reference set is sparse and includes an Apache mailing-list URL that is not clearly tied to Android Bluetooth. Confidence is limited to the CVE record fields: affected versions, weakness classes, CVSS vector, and no KEV listing.

Mitigation direction

  • Inventory Android 8, 8.1, and 9 devices in managed and unmanaged fleets.
  • Check Google and device-OEM guidance for patch availability and security bulletin mapping.
  • Prioritize upgrade or replacement for unsupported Android 8, 8.1, and 9 devices.
  • Restrict Bluetooth use where operationally feasible until vendor patch status is confirmed.

Validation and detection

  • Confirm Android version and security patch level on in-scope mobile assets.
  • Review MDM inventory for Android 8, 8.1, and 9 devices.
  • Map each device model to OEM security bulletin status for CVE-2018-9481.
  • Check whether Bluetooth is required, enabled, or policy-controlled on exposed devices.
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
cwe · low confidence lookup

CWE-190: 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-9481 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
Medium
CVSS
6.2 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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
6.2CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N2.53.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.2Medium
CVSS 3.1 vector shape for CVE-2018-9481Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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.1, 9unaffected
Weakness

CWE details

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