LiveActive security incident?Get immediate response
CVE Record

CVE-2018-9381: In gatts_process_read_by_type_req of gatt_sr.c, there is a possible information disclosure due to uninitial...

In gatts_process_read_by_type_req of gatt_sr.c, there is a possible information disclosure due to uninitialized data. This could lead to remote information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.

HighCVSS 7.5Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2018-9381 is a high-severity Android 8.1 issue where uninitialized data may be exposed remotely. The provided evidence says no privileges or user interaction are needed. Treat affected Android 8.1 devices as information-disclosure risk, especially where sensitive data exposure would matter.

Executive priority

Prioritize remediation for any Android 8.1 fleet still in use. The risk is confidentiality-focused, but remote, unauthenticated, no-click characteristics make lingering exposure unacceptable for sensitive environments.

Technical view

The flaw is in gatts_process_read_by_type_req in gatt_sr.c and is classified as CWE-908, use of uninitialized resource. CVSS 3.1 is 7.5 with AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N, indicating remotely reachable, low-complexity confidentiality impact only.

Likely exposure

Provided affected scope is Google Android 8.1. The source bundle lists other versions as unaffected by default, and does not provide device-model-specific exposure beyond the Pixel bulletin reference.

Exploitation context

No KEV listing is present, and the provided sources do not cite active exploitation. The scoring indicates remote exploitation without privileges or user interaction, but the bundle does not include exploit details or observed campaign evidence.

Researcher notes

Evidence is concise and incomplete on patch mapping. Analysis should stay tied to Android 8.1, CWE-908, the named gatt_sr.c function, and Google’s Pixel security bulletin until vendor or OEM advisories provide more detail.

Mitigation direction

  • Identify Android 8.1 devices in managed and unmanaged inventories.
  • Check Google Pixel and OEM security guidance for CVE-2018-9381 fixes.
  • Prioritize security updates for affected Android 8.1 devices.
  • Retire or isolate devices that cannot receive applicable vendor updates.

Validation and detection

  • Confirm OS version and security patch level on Android 8.1 devices.
  • Map device models to vendor bulletins referencing CVE-2018-9381.
  • Verify update deployment through MDM, EDR, or device inventory records.
  • Document exceptions for devices without available vendor fixes.
Prepared
Confidence
medium
Sources
3

Public sources used

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-908: 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-9381 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:N/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
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
GoogleAndroid8.1unaffected
Weakness

CWE details

CWE-908

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

CWE-908 · source CWE mapping

Use of Uninitialized Resource

Use of Uninitialized Resource represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs